[OpenSER-Devel] [ openser-Bugs-1864152 ] dialog module causes OpenSER to stop processing requests

Mon Jan 7 14:31:10 UTC 2008

Bugs item #1864152, was opened at 2008-01-04 14:42
Message generated for change (Comment added) made by intralanman
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1864152&group_id=139143

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: modules
Group: ver 1.3.x
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: intralanman (intralanman)
Assigned to: Bogdan-Andrei Iancu (bogdan_iancu)
Summary: dialog module causes OpenSER to stop processing requests

Initial Comment:
OpenSER sends a packet with a Record-Route as follows:
Record-Route: <sip:10.15.202.10:6080;lr;ftag=8621dc6d6281aa64o0;nat=yes;did=a16.4d576bc3>.

The other end sends a Record-Route as follows:
Record-Route: <sip:10.15.202.10:6080;lr;ftag=8621dc6d6281aa64o0;nat=yes;did=a16.4d576bc3>,<0 ap..

Upon receiving that packet, I see the following lines in the log file and OpenSER fails to respond to future requests until restarted:

Jan  3 09:13:56 p1 oser[18407]: ERROR:core:parse_nameaddr: no > found
Jan  3 09:13:56 p1 oser[18407]: ERROR:core:do_parse_rr_body: failed to parse name-addr
Jan  3 09:13:56 p1 oser[18407]: ERROR:core:print_rr_body: failed to parse RR
Jan  3 09:13:56 p1 oser[18407]: ERROR:dialog:populate_leg_info: failed to print route records
Jan  3 09:13:56 p1 oser[18407]: ERROR:dialog:dlg_onreply: could not add further info to the dialog
Jan  3 09:13:56 p1 oser[18431]: CRITICAL:core:receive_fd: EOF on 11

----------------------------------------------------------------------

>Comment By: intralanman (intralanman)
Date: 2008-01-07 09:31

Message:
Logged In: YES 
user_id=1973783
Originator: YES

That was the entire RR. I'm guessing that's the parsing problem.

The entire INVITE I send is thus: (ip/domain changed)
U 2008/01/03 09:13:48.017423 10.15.202.10:6080 -> 10.25.48.83:5060
INVITE sip:15555558550 at sip.example.com:5060;transport=udp SIP/2.0.
Record-Route:
<sip:10.15.202.10:6080;lr;ftag=8621dc6d6281aa64o0;nat=yes;did=a16.4d576bc3>.
Via: SIP/2.0/UDP 10.15.202.10:6080;branch=z9hG4bK6eeb.ec9b8ef7.0.
Via: SIP/2.0/UDP
192.168.1.1:10321;received=10.174.144.114;branch=z9hG4bK-2fdc3e94;rport=10321.
From: <sip:5555550023 at sip.example.com>;tag=8621dc6d6281aa64o0.
To: <sip:15555558550 at sip.example.com>.
Call-ID: fedb97e1-1adc0580 at 192.168.1.1.
CSeq: 102 INVITE.
Max-Forwards: 69.
Contact: <sip:15555550023 at 10.174.144.114:10321>.
Expires: 240.
User-Agent: Linksys/SPA2100-3.3.9.
Content-Length: 223.
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER.
Supported: x-sipura, replaces.
Content-Type: application/sdp.
.
v=0.
o=- 323950 323950 IN IP4 192.168.1.1.
s=-.
c=IN IP4 10.15.202.10.
t=0 0.
m=audio 38762 RTP/AVP 0 101.
a=rtpmap:0 PCMU/8000.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-15.
a=ptime:20.
a=sendrecv.
a=nortpproxy:yes.

The OK that they eventually send in return is:
U 2008/01/03 09:13:56.571997 10.25.48.83:5060 -> 10.15.202.10:6080
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 10.15.202.10:6080;branch=z9hG4bK6eeb.ec9b8ef7.0.
Via: SIP/2.0/UDP
192.168.1.1:10321;received=10.174.144.114;branch=z9hG4bK-2fdc3e94;rport=10321.
From: <sip:5555550023 at sip.example.com>;tag=8621dc6d6281aa64o0.
To: <sip:15555558550 at sip.example.com>;tag=cba-74b2-477cfbcc.
Call-ID: fedb97e1-1adc0580 at 192.168.1.1.
CSeq: 102 INVITE.
Contact: <sip:15555558550 at 10.25.48.83>.
Date: Thu, 03 Jan 2008 15:14:29 GMT.
Server: BRSIP v2.0.1.2.
Record-Route:
<sip:10.15.202.10:6080;lr;ftag=8621dc6d6281aa64o0;nat=yes;did=a16.4d576bc3>,<0
ap..
Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, INFO, SUBSCRIBE, NOTIFY.
Allow-Events: keep-alive, message-summary.
Supported: timer.
Content-Type: application/sdp.
Content-Length: 214.
.
v=0.
o=BRSDP 1011421 1011421 IN IP4 10.249.3.164.
s=BRSDP Session.
c=IN IP4 10.249.3.164.
t=0 0.
m=audio 25704 RTP/AVP 0 101.
a=ptime:20.
a=rtpmap:0 PCMU/8000.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-15.

Obviously the BRSIP device has a problem with sending malformed
packets.... but I think we can agree that OpenSER should just tell the
remote end..... ummmm..... "have a nice day"

----------------------------------------------------------------------

Comment By: Bogdan-Andrei Iancu (bogdan_iancu)
Date: 2008-01-05 04:38

Message:
Logged In: YES 
user_id=1275325
Originator: NO

Hi,

please post the complete RR header (multi body) returned in the reply. It
looks like openser reports some syntax error on this RR hdr.

Thanks and regards,
Bogdan

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1864152&group_id=139143