You are right.<br>SIPp fails to add CRLF.<br>Thank you.<br><br>Regards,<br>Takeshi.<br><br><div class="gmail_quote">On Thu, Jun 26, 2008 at 12:00 AM, Klaus Darilion <<a href="mailto:klaus.mailinglists@pernau.at">klaus.mailinglists@pernau.at</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I suspect that the SDP does not contain CRLF at the end of the last line.<br>
<br>
If this is the case, the SDP is not correct:<br>
<br>
>From RFC 4566:<br>
<br>
Text fields such as the session name and information are octet<br>
strings that may contain any octet with the exceptions of 0x00 (Nul),<br>
0x0a (ASCII newline), and 0x0d (ASCII carriage return). The sequence<br>
CRLF (0x0d0a) is used to end a record, although parsers SHOULD be<br>
tolerant and also accept records terminated with a single newline<br>
character.<br>
<br>
Nevertheless openser should be tolerant and add the CRLF itself.<br>
<br>
regards<br>
klaus<br>
<br>
<br>
mayamatakeshi schrieb:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">
Hello,<br>
<br>
I'm testing with OpenSER 1.3.x revision 4393 with RTPProxy.<br>
I'm trying to make a call from a Nokia E51 to a SIPp instance started with:<br>
sipp -sn uas -p 6060 -mp 4000<br>
<br>
The INVITE goes thru OpenSER to SIPp and then, SIPp replies with this:<br>
<br>
SIPp to OpenSER:<br>
SIP/2.0 200 OK<br></div>
Via: SIP/2.0/UDP <a href="http://210.126.5.158" target="_blank">210.126.5.158</a> <<a href="http://210.126.5.158" target="_blank">http://210.126.5.158</a>>;branch=z9hG4bK9c1e.f06224f3.0, SIP/2.0/UDP 192.168.0.4:5060;received=<a href="http://123.224.149.169" target="_blank">123.224.149.169</a> <<a href="http://123.224.149.169" target="_blank">http://123.224.149.169</a>>;branch=z9hG4bK5j85u8aa6jpebhelr55b8bj;rport=64351<br>
From: <<a href="mailto:sip%3A1000@210.126.5.158" target="_blank">sip:1000@210.126.5.158</a> <mailto:<a href="mailto:sip%253A1000@210.126.5.158" target="_blank">sip%3A1000@210.126.5.158</a>>>;tag=r5hbkuj8mlhc6o184cms<br>
To: <<a href="mailto:sip%3A22222222@210.126.5.158" target="_blank">sip:22222222@210.126.5.158</a> <mailto:<a href="mailto:sip%253A22222222@210.126.5.158" target="_blank">sip%3A22222222@210.126.5.158</a>>;user=phone>;tag=28909SIPpTag013<div class="Ih2E3d">
<br>
Call-ID: nLPxHi_hoIf-POcJ7OKojntw2wgQle<br>
CSeq: 7342 INVITE<br>
Contact: <sip:192.168.88.16:6060;transport=UDP><br>
Content-Type: application/sdp<br>
Content-Length: 135<br>
<br>
v=0<br></div>
o=user1 53655765 2353687637 IN IP4 <a href="http://192.168.88.16" target="_blank">192.168.88.16</a> <<a href="http://192.168.88.16" target="_blank">http://192.168.88.16</a>><br>
s=-<br>
c=IN IP4 <a href="http://192.168.88.16" target="_blank">192.168.88.16</a> <<a href="http://192.168.88.16" target="_blank">http://192.168.88.16</a>><div class="Ih2E3d"><br>
t=0 0<br>
m=audio 4000 RTP/AVP 0<br>
a=rtpmap:0 PCMU/8000<br>
<br>
<br>
But when OpenSER relays this to E51, I can see it is adding "a=nortpproxy:yes" immediatelly after the the last characters in the SDP instead of prepending a CRLF.<br>
<br>
OpenSER to Caller<br>
SIP/2.0 200 OK<br></div>
Via: SIP/2.0/UDP 192.168.0.4:5060;received=<a href="http://123.224.149.169" target="_blank">123.224.149.169</a> <<a href="http://123.224.149.169" target="_blank">http://123.224.149.169</a>>;branch=z9hG4bK5j85u8aa6jpebhelr55b8bj;rport=64351<br>
From: <<a href="mailto:sip%3A1000@210.126.5.158" target="_blank">sip:1000@210.126.5.158</a> <mailto:<a href="mailto:sip%253A1000@210.126.5.158" target="_blank">sip%3A1000@210.126.5.158</a>>>;tag=r5hbkuj8mlhc6o184cms<br>
To: <<a href="mailto:sip%3A22222222@210.126.5.158" target="_blank">sip:22222222@210.126.5.158</a> <mailto:<a href="mailto:sip%253A22222222@210.126.5.158" target="_blank">sip%3A22222222@210.126.5.158</a>>;user=phone>;tag=28909SIPpTag013<div class="Ih2E3d">
<br>
Call-ID: nLPxHi_hoIf-POcJ7OKojntw2wgQle<br>
CSeq: 7342 INVITE<br>
Contact: <sip:210.126.5.158:6060;transport=UDP;nat=yes><br>
Content-Type: application/sdp<br>
Content-Length: 154<br>
<br>
v=0<br></div>
o=user1 53655765 2353687637 IN IP4 <a href="http://192.168.88.16" target="_blank">192.168.88.16</a> <<a href="http://192.168.88.16" target="_blank">http://192.168.88.16</a>><br>
s=-<br>
c=IN IP4 <a href="http://210.126.5.158" target="_blank">210.126.5.158</a> <<a href="http://210.126.5.158" target="_blank">http://210.126.5.158</a>><div class="Ih2E3d"><br>
t=0 0<br>
m=audio 36740 RTP/AVP 0<br>
a=rtpmap:0 PCMU/8000a=nortpproxy:yes<br>
<br>
Because of this, E51 ignores the message and doesn't send ACK.<br>
I believe this is a bug in OpenSER.<br>
<br>
Thanks,<br>
Takeshi<br>
<br>
<br></div>
------------------------------------------------------------------------<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.openser.org" target="_blank">Users@lists.openser.org</a><br>
<a href="http://lists.openser.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.openser.org/cgi-bin/mailman/listinfo/users</a><br>
</blockquote>
</blockquote></div><br>