[OpenSIPS-Users] Another possible bug in b2bua
Jeff Kronlage
jeff at data102.com
Sat Nov 21 05:51:11 CET 2009
Anca,
I'm having the b2b crash at different moments now. While the system
seems relatively stable if I can get past the initial OK/ACKs, I'm
having what appears to be a problem generated by a to-tag with dashes in
it. For instance:
(IPs/hostnames have been replaced by either (proxy) for our front-end
server or (b2bua) for the back-end b2b or (sip gateway) for our Cisco
gear)
15:16:00.217293 IP (tos 0xb8, ttl 64, id 0, offset 0, flags [DF], proto
UDP (17), length 974) (proxy).5060 > (b2bua).5060: SIP, length: 946
SIP/2.0 200 OK
Via: SIP/2.0/UDP (b2bua);branch=z9hG4bKc4d.78cf4eb3.0
From:
<sip:719xxx0449@(proxy)>;tag=9e0f6f7cd33d08ad3fd7dcf243da9165-d4dc
To: sip:719xxx1095@(proxy):5060;tag=2E32D030-2CB
Date: Sat, 21 Nov 2009 04:05:21 GMT
Call-ID: B2B.144.0.1258755349
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 2 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER,
SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER
Supported: replaces
Allow-Events: telephone-event
Contact: <sip:719xxx1095@(pstn gateway):5060>
Record-Route:
<sip:(proxy);lr=on;ftag=9e0f6f7cd33d08ad3fd7dcf243da9165-d4dc;did=81d.b6
260723>
Content-Type: application/sdp
Content-Length: 244
v=0
o=CiscoSystemsSIP-GW-UserAgent 2487 1889 IN IP4 (pstn gateway)
s=SIP Call
c=IN IP4 (pstn gateway)
t=0 0
m=audio 18922 RTP/AVP 0 101
c=IN IP4 (pstn gateway)
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
15:16:00.217949 IP (tos 0x10, ttl 64, id 0, offset 0, flags [DF], proto
UDP (17), length 1015) (b2bua).5060 > (proxy).5060: SIP, length: 987
SIP/2.0 200 OK
Record-Route:
<sip:(proxy);lr=on;ftag=a31385f8c7bc6888o0;did=e25.e1d15c16;NAT=true>
Via: SIP/2.0/UDP (proxy);branch=z9hG4bKef3.ffc40151.0
Via: SIP/2.0/UDP
192.168.0.101:5060;rport=52434;received=174.22.143.40;branch=z9hG4bK-c02
4968
From: "719xxx0449"
<sip:719xxx0449@(proxy)>;tag=a31385f8c7bc6888o0
To: <sip:xxx1095@(proxy)>;tag=B2B.60.0.1258755349
Call-ID: 175b26b8-7cb3ec8 at 192.168.0.101
CSeq: 102 INVITE
Content-Type: application/sdp
Supported: replaces
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER,
SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER
Contact: <sip:opensips@(b2bua):5060>
Server: OpenSIPS (1.6.1-notls (i386/linux))
Content-Length: 244
v=0
o=CiscoSystemsSIP-GW-UserAgent 2487 1889 IN IP4 (pstn gateway)
s=SIP Call
c=IN IP4 (pstn gateway)
t=0 0
m=audio 18922 RTP/AVP 0 101
c=IN IP4 (pstn gateway)
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
15:16:00.299687 IP (tos 0xb8, ttl 64, id 0, offset 0, flags [DF], proto
UDP (17), length 798) (proxy).5060 > (b2bua).5060: SIP, length: 770
ACK sip:opensips@(b2bua):5060 SIP/2.0
Via: SIP/2.0/UDP (proxy);branch=z9hG4bK-13770017
Via: SIP/2.0/UDP
192.168.0.101:5060;rport=52434;received=174.22.143.40;branch=z9hG4bK-137
70017
From: "719xxx0449"
<sip:719xxx0449@(proxy)>;tag=a31385f8c7bc6888o0
To: <sip:xxxx1095@(proxy)>;tag=B2B.60.0.1258755349
Call-ID: 175b26b8-7cb3ec8 at 192.168.0.101
CSeq: 102 ACK
Max-Forwards: 69
User-Agent: Linksys/SPA942-5.1.15(a)
Content-Length: 0
** OUTBOUND PACKET GENERATED BY B2B (note the From: tag, and how it has
a piece of the To: tag stuck in it,repeatedly.) **
15:16:00.299860 IP (tos 0x10, ttl 64, id 0, offset 0, flags [DF], proto
UDP (17), length 543) (b2bua).5060 > (proxy).5060: SIP, length: 515
ACK sip:719xxx1095@(pstn gateway):5060 SIP/2.0
Via: SIP/2.0/UDP (b2bua);branch=z9hG4bKc4d.88cf4eb3.0
To: <sip:719xxx1095@(proxy):5060>;tag=2E32D030-2CB
From: <-2CB
From: <-2CB
From: <-2CB
From>;tag=9e0f6f7cd33d08ad3fd7dcf243da9165-d4dc
CSeq: 2 ACK
Call-ID: m:5060>;tag=2E32D030
Route:
<sip:(proxy);lr=on;ftag=9e0f6f7cd33d08ad3fd7dcf243da9165-d4dc;did=81d.b6
260723>
Content-Length: 0
User-Agent: OpenSIPS (1.6.1-notls (i386/linux))
Contact: <sip:opensips@(b2bua).5060>
** The B2BUA Opensips instance crashes here **
I honestly don't have a big enough sampling of gear to confirm this. I
have some softphones, a few handsets, Asterisk, a bunch of Cisco kit and
a Covergence SBC I can talk to. The softphones and Asterisk work great.
The Cisco kit and Covergence both place dashes in their tags and while
speaking to this gear, the B2B crashes and produces the packet you see
above.
Your thoughts?
As always, I sure appreciate it.
Jeff K
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opensips.org/pipermail/users/attachments/20091120/4731f341/attachment-0001.htm
More information about the Users
mailing list