Multipart SDP bodies

The program can send multipart bodies. There is an example in the scenarios folder: HexBody_client.txt. The main point is to create a boundary marker and use it to separate the bodies:

INVITE sip:[toUsername]@[remote_ip]:[remote_port];transport=[transport] SIP/2.0
Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=[branch]ab
From: <sip:[fromUsername]@[remote_ip]:[remote_port]>;tag=[call_number]
To: <sip:[toUsername]@[remote_ip]:[remote_port]>
Call-ID: [call_number]@[local_ip]
CSeq: [cseq+1] INVITE
Max-Forwards: 70
Content-Type: multipart/mixed;boundary=level-0
Content-Length: [len]

--level-0
Content-Type: application/sdp
Content-Length: 324

v=0
o=MxSIP 131077 501465461 IN IP4 192.168.111.173
s=SIP Call
c=IN IP4 192.168.111.173
...

--level-0
Content-Disposition: signal; handling=required
Content-Type: application/qsig;version=iso
Content-Length: 324

v=0
...
--level-0--[no_\r\n]

The last delimiter ends with ‘--’, which makes it the final one. For SIP Inspector not to add \r\n after the last delimiter, [no_\r\n] must be used.