linphone-developers
[Top][All Lists]
Advanced
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Linphone-developers] Failed to parse SDP message. What about more p

From: kupchanko
Subject: Re: [Linphone-developers] Failed to parse SDP message. What about more permissive mode for parsing SDP?
Date: Fri, 8 May 2015 10:48:48 +0300
Hello Gautier,
thank you for commits with more verbose debug of SDP parsing.
Below is slice from log, there is an error:
2015-05-08 10:26:28:824 MESSAGE [org.antlr.runtime.MismatchedTokenException] reason [()* loopback of 411:22: ( attribute CR LF )*] at line[18] position[0]
2015-05-08 10:26:28:824 MESSAGE [org.antlr.runtime.MismatchedTokenException] reason [()* loopback of 411:22: ( attribute CR LF )*] at line[18] position[0]
If we calculate from beginning of SIP message (from 0), then line 18 is
o=- 2463225753 2463225753 IN IP4 www.xxx.yyy.zzz
But if start from the beginning of SDP body, then 18th line is blank line after the last SDP line.
So for real i dont understand exactly, is it bug in belle-sip, or in sip server :(
Below is log with replaced sip server ip…
Thank you very much for advise. 

2015-05-08 10:26:28:807 MESSAGE channel [0x5e0ba008]: received [1359] new bytes from [UDP://www.xxx.yyy.zzz:5060]:
INVITE sip:address@hidden SIP/2.0
Via: SIP/2.0/UDP www.xxx.yyy.zzz;branch=z9hG4bK1a4c.868482563bf80aa7c57b036990adbcf0.0
Via: SIP/2.0/UDP www.xxx.yyy.zzz:5069;branch=z9hG4bKbbd0cf1475a1f797190f1cfdcb57deda;rport=5069
Max-Forwards: 69
From: 0845380505259487 <sip:address@hidden>;tag=41d1cff4d2f1778a5ef353cf916021a4
Call-ID: ZDVhMzI5YThkMDk4Yzk1Mjc4ZmZkZTJkZDIyZjdiZjc.-onnet_1-b2b_1
CSeq: 200 INVITE
Contact: Anonymous <sip:address@hidden:5069>
Expires: 300
User-Agent: Sippy Softswitch v4.2-PRODUCTION.0.100
cisco-GUID: 3799553023-1612678695-3521334061-3816748403
h323-conf-id: 3799553023-1612678695-3521334061-3816748403
Content-Length: 507
Content-Type: application/sdp

v=0
o=- 2463225753 2463225753 IN IP4 www.xxx.yyy.zzz
s=CounterPath eyeBeam 1.5
t=0 0
m=audio 45866 RTP/AVP 18 107 0 8 101
a=alt:1 4 : 14rESjRy H3TTsrT2 192.168.56.1 43948
a=alt:2 3 : 1AH6wZGG HxkIQYfT 192.168.52.1 43948
a=alt:3 2 : l5ECiEPE yEZt5L0I 192.168.152.1 43948
a=alt:4 1 : ZElBV2Kz IYZkbYU3 172.22.252.137 43948
a=fmtp:18 annexb=yes
a=fmtp:101 0-15
a=rtpmap:107 BV32/16000
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=sendrecv
a=direction:active


2015-05-08 10:26:28:818 MESSAGE channel [0x5e0ba008] [852] bytes parsed
2015-05-08 10:26:28:818 MESSAGE channel [0x5e0ba008] read [507] bytes of body from [www.xxx.yyy.zzz:5060]
2015-05-08 10:26:28:820 MESSAGE Changing [server] [INVITE] transaction [0x5cfb2dd0], from state [INIT] to [PROCEEDING]
2015-05-08 10:26:28:821 MESSAGE channel [0x5e0ba008]: message sent to [UDP://www.xxx.yyy.zzz:5060], size: [430] bytes
SIP/2.0 100 Trying
Via: SIP/2.0/UDP www.xxx.yyy.zzz;branch=z9hG4bK1a4c.868482563bf80aa7c57b036990adbcf0.0
Via: SIP/2.0/UDP www.xxx.yyy.zzz:5069;branch=z9hG4bKbbd0cf1475a1f797190f1cfdcb57deda;rport=5069
From: "0845380505259487" <sip:address@hidden>;tag=41d1cff4d2f1778a5ef353cf916021a4
Call-ID: ZDVhMzI5YThkMDk4Yzk1Mjc4ZmZkZTJkZDIyZjdiZjc.-onnet_1-b2b_1
CSeq: 200 INVITE


2015-05-08 10:26:28:821 MESSAGE New server dialog [0x5e7bd430] , local tag [], remote tag [41d1cff4d2f1778a5ef353cf916021a4]
2015-05-08 10:26:28:821 MESSAGE op [0x5e7c1f70] : set_or_update_dialog() current=[0x0] new=[0x5e7bd430]
2015-05-08 10:26:28:821 MESSAGE new incoming call from ["0845380505259487" <sip:address@hidden>] to [sip:address@hidden
2015-05-08 10:26:28:824 MESSAGE [org.antlr.runtime.MismatchedTokenException] reason [()* loopback of 411:22: ( attribute CR LF )*] at line[18] position[0]
2015-05-08 10:26:28:824 MESSAGE [org.antlr.runtime.MismatchedTokenException] reason [()* loopback of 411:22: ( attribute CR LF )*] at line[18] position[0]
2015-05-08 10:26:28:825 ERROR session_description parser error for [v=0
o=- 2463225753 2463225753 IN IP4 www.xxx.yyy.zzz
s=CounterPath eyeBeam 1.5
t=0 0
m=audio 45866 RTP/AVP 18 107 0 8 101
a=alt:1 4 : 14rESjRy H3TTsrT2 192.168.56.1 43948
a=alt:2 3 : 1AH6wZGG HxkIQYfT 192.168.52.1 43948
a=alt:3 2 : l5ECiEPE yEZt5L0I 192.168.152.1 43948
a=alt:4 1 : ZElBV2Kz IYZkbYU3 172.22.252.137 43948
a=fmtp:18 annexb=yes
a=fmtp:101 0-15
a=rtpmap:107 BV32/16000
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=sendrecv
a=direction:active

]
2015-05-08 10:26:28:825 ERROR Failed to parse SDP message.
2015-05-08 10:26:28:826 MESSAGE channel [0x5e0ba008]: message sent to [UDP://www.xxx.yyy.zzz:5060], size: [531] bytes
SIP/2.0 488 Not acceptable here
Via: SIP/2.0/UDP www.xxx.yyy.zzz;branch=z9hG4bK1a4c.868482563bf80aa7c57b036990adbcf0.0
Via: SIP/2.0/UDP www.xxx.yyy.zzz:5069;branch=z9hG4bKbbd0cf1475a1f797190f1cfdcb57deda;rport=5069
From: "0845380505259487" <sip:address@hidden>;tag=41d1cff4d2f1778a5ef353cf916021a4
To: <sip:address@hidden>;tag=LGAxXMr
Call-ID: ZDVhMzI5YThkMDk4Yzk1Mjc4ZmZkZTJkZDIyZjdiZjc.-onnet_1-b2b_1
CSeq: 200 INVITE
User-Agent: LinphoneAndroid/2.4.0 (belle-sip/1.4.1)
Supported: outbound


2015-05-08 10:26:28:826 MESSAGE Changing [server] [INVITE] transaction [0x5cfb2dd0], from state [PROCEEDING] to [COMPLETED]
2015-05-08 10:26:28:826 MESSAGE Dialog [0x5e7bd430]: now updated by transaction [0x5cfb2dd0].
2015-05-08 10:26:28:826 MESSAGE dialog [0x5e7bd430] deleted.
2015-05-08 10:26:28:826 MESSAGE channel [0x5e0ba008]: ending recv background task with id=[1ed0093e].
2015-05-08 10:26:28:828 MESSAGE wake_lock_release(): Android wake lock released [ref=0x1ed0093e]
2015-05-08 10:26:28:829 MESSAGE Dialog [0x5e7bd430] terminated for op [0x5e7c1f70]





On May 7, 2015, at 15:40, Gautier Pelloux-Prayer <address@hidden> wrote:

Hi,

Indeed we found an issue in belle-sip code so I did some changes. First, you should now have the error position to ease find the root of the error. In your case, you should now see in logs something like:

2015-05-07 14:37:53:107 belle-sip-message-[org.antlr.runtime.EarlyExitException] reason [Unexpected token] at line[2] position[12]
2015-05-07 14:37:53:107 belle-sip-message-[org.antlr.runtime.EarlyExitException] reason [Unexpected token] at line[2] position[12]
2015-05-07 14:37:53:107 belle-sip-error-session_description parser error for [v=0
o=jehan-mac -1831749426 -1831749426 IN IP4 192.168.0.18

I think that your issue was in line o=- 2463217870 2463217870 IN IP4 xxx.yyy.zzz.www and mainly 2463217870 (session ID) which was misconverted to int.

If you want to confirm the fix please try belle-sip revision 82ac36d.

Thanks,

Gautier Pelloux-Prayer
Software Engineer @ Belledonne Communications

On 07 May 2015, at 09:41, address@hidden wrote:

Hello,
when Sippy SoftSwitch is sending SIP INVITE to linphone (android), it’s rejected with the reason 'Failed to parse SDP message'.
I found advices for similar issue in this maillist:
rtcp_xr_enabled=0
rtcp_xr_rcvr_rtt_mode=all
rtcp_xr_rcvr_rtt_max_size=10000
rtcp_xr_stat_summary_enabled=0
rtcp_xr_voip_metrics_enabled=0
but it’s not working.

BTW, here is log:
session_description parser error for [v=0
o=- 2463217870 2463217870 IN IP4 xxx.yyy.zzz.www
s=CounterPath eyeBeam 1.5
c=IN IP4 xxx.yyy.zzz.www
t=0 0
m=audio 31612 RTP/AVP 18 101
a=alt:1 1 : e2br+9PL Eu1qGlQ9 10.211.55.3 8988
a=fmtp:18 annexb=yes
a=fmtp:101 0-15
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=sendrecv
a=direction:active
]
Failed to parse SDP message.

I suggest the problem is in line
a=alt:1 1 : e2br+9PL Eu1qGlQ9 10.211.55.3 8988
where we have colon with spaces before and after.
Can someone confirm, that the issue is really with that colon?

Is it possible to make SDP parsing more permissive?

Thank you.

—
Regards, Andrii Kupchanko
_______________________________________________
Linphone-developers mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/linphone-developers


reply via email to
[Prev in Thread] Current Thread [Next in Thread]