I gave this a try, the message is not decoded properly in wireshark it
sees the \x as plain text. I think the message body (you're right
about that i called it an sdp) has to be binary.
-----Original Message-----From: Luis Rojas G. <luis.ro...@sixbell.com>
To: "Ormsbee, Trey" <trey.orms...@interoptechnologies.com>,
sipp-users@lists.sourceforge.net <sipp-users@lists.sourceforge.net>
Subject: Re: [Sipp-users] Unable to get binary data into sdp
Date: Mon, 30 Jan 2017 17:39:56 -0500
On 01/30/2017 06:42 PM, Trey Ormsbee wrote:
>
> Hello All-
>
> Im trying to stick some binary data in the sdp of a sip message and am
> having a problem doing so. Here is the message in the scenario:
>
> <send retrans="500">
> <![CDATA[
>
> MESSAGE sip:+1111111111@[field1] SIP/2.0
> Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=[branch]
> From: <sip:[field0]@[field1]>;tag=[call_number]
> To: <sip:+11111111111@[field1]>
> Call-ID: [call_id]
> CSeq: 1 MESSAGE
> Contact: sip:[field0]@[local_ip]:[local_port]
> Max-Forwards: 70
> Content-Type: application/vnd.3gpp.sms
> Content-Length: [len]
>
> [field3]
>
> ]]>
> </send>
>
>
> I have tried putting the binary data in [feild3] in the csv file, but
> that does not seem to work. The binary data is generated by a perl
> script so that is an option as well. What is the best way to put that
> data into the scenario?
>
> Also if it helps here is a hexdump of the content:
>
> 00000000 00 01 00 06 91 11 11 11 11 11 18 11 01 0a 81 22
> |..............."|
> 00000010 22 22 22 22 00 00 aa 80 d4 f2 9c 9e 76 9f 01
> |""""........v..|
> 0000001f
>
>
> Any help would be appreciated.
>
> Thanks
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>
>
>
>
> _______________________________________________
> Sipp-users mailing list
> Sipp-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sipp-users
Hello,
You mean to stick binary data in the body of a SIP message, which is not
an SDP body, but an "application/vnd.3gpp.sms" body.
This is very similar to transport ISUP using SIP-I. In my scripts I use
something like :
Content-Type: application/isup;base=itu-t92+;version=itu
Content-Disposition: session;handling=optional
Content-Length: [len]
\x0c\x02\x00\x02\x87\x90
]]>
So you may write that binary data as a sequence of hexadecimal numbers.
Best regards,
Luis
--
Luis Rojas
Software Architect
Sixbell Nekotec Solutions
Los Leones 1200
Providencia
Santiago, Chile
Phone: (+56-2) 22001288
mailto:luis.ro...@sixbell.com
http://www.sixbell.com
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users
