The basic client invite "sipp -sn uac" generates an invite with sdp, the last
two lines of which are:
m=audio [media_port] RTP/AVP 0
a=rtpmap:0 PCMU/8000
If you view the sdp packet in wireshark you see that the m= line is terminated
with CRLF but the a= line is terminated at the "80000". rfc2327 requires that
each
sdp record be terminated with CRLF although on page 8 of the spec it states that
parsers should be flexible enough to handle a single "\n" as the terminator. I
believe the spec requires that the a= line not be terminated with 8000<NULL>.
My SIP
UAS which is parsing with osip/eXosip responds to every SIPP generated invite
with a 400 Invalid, due to the missing line termination.
The seems to be a huge problem, unless everyone else is using a sip parser that
ignores this spec requirement. I am using SIPP version 3.1 and have run the -sn
uac
scenario on XP and Centos 4 variants with the same failure. I have created my
own
scenarios with additional blank lines preceeding the ]]> but sipp strips these
out and does not CRLF terminate the last SDP record.
/robert
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
