sippy / go-b2bua

The GO port of the Sippy B2BUA
BSD 2-Clause "Simplified" License
61 stars 16 forks source link

INVITE Parse Failure using Linphone #7

Closed kingster closed 4 years ago

kingster commented 4 years ago

Hi

I have an invite which causes b2bua to crash the sip call

Error Info

2019-12-26 07:12:50+00 ERROR: UasStateIdle::RecvRequest: #1: ParseSipAddress #1"

I did a little debugging and found that ParseSipAddress function gets input lime", which means something breaks in the Contact line.

The sip-client this happens is with LinPhone

Full Invite

INVITE sip:12345@domain.de:5060 SIP/2.0
Record-Route: <sip:192.168.0.150;transport=udp;r2=on;ftag=NBzRt6-Ol;lr=on;did=fa5.17f1;nat=yes>
Record-Route: <sip:192.168.0.150;transport=tcp;r2=on;ftag=NBzRt6-Ol;lr=on;did=fa5.17f1;nat=yes>
Via: SIP/2.0/UDP 192.168.0.150;branch=z9hG4bKe2a5.4a122eb8a4f73d90907b65cd4ddab597.0;i=2
Via: SIP/2.0/TCP 54.37.202.229;received=54.37.202.229;rport=42863;branch=z9hG4bK.aBayv28r73FXHeNXN1X33tZN5F
Record-Route: <sip:54.37.202.229:5060;lr>
Record-Route: <sips:sip6.linphone.org:5223;lr>
Via: SIP/2.0/TLS 172.29.148.147:42373;branch=z9hG4bK.ohnMpy4y~;rport=8040;received=115.110.204.52
From: <sip:kinshuk@domain.de>;tag=NBzRt6-Ol
To: <sip:12345@domain.de>
CSeq: 20 INVITE
Call-ID: 0QHP26cRix
Max-Forwards: 68
Supported: replaces, outbound, gruu
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO, UPDATE
Content-Type: application/sdp
Content-Length: 722
Contact: <sip:kinshuk@sip.linphone.org;gr=urn:uuid:3bc8f96e-2c58-00b7-9fb0-dcd54de6ce7d>;+org.linphone.specs="groupchat,lime"
User-Agent: LinphoneAndroid/4.2 (OnePlus 5T) LinphoneSDK/4.3 (tags/4.3^0)
P-hint: inbound

v=0
o=kinshuk 3627 2526 IN IP4 192.168.0.150
s=Talk
c=IN IP4 192.168.0.150
t=0 0
a=rtcp-xr:rcvr-rtt=all:10000 stat-summary=loss,dup,jitt,TTL voip-metrics
a=Ik:ZosOr+k8Y7VBT11EiuY/yFdNV0shWmlX+6AW0d/Qifc=
a=rtpengine:35ce461d2b76
m=audio 37574 RTP/AVPF 96 97 98 0 8 18 101 99 100
c=IN IP4 192.168.0.150
a=rtcp-fb:* trr-int 1000
a=rtcp-fb:* ccm tmmbr
a=rtpmap:96 opus/48000/2
a=rtpmap:97 speex/16000
a=rtpmap:98 speex/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/48000
a=rtpmap:99 telephone-event/16000
a=rtpmap:100 telephone-event/8000
a=fmtp:96 useinbandfec=1
a=fmtp:97 vbr=on
a=fmtp:98 vbr=on
a=fmtp:18 annexb=yes
a=sendrecv
a=rtcp:37575
bambyster commented 4 years ago

Hi,

The issue has been fixed. Thank you for your report!