Originate Resulted in Error Cause: 100 [INVALID_IE_CONTENTS]
I have a problem with a provider where the call are dropped by Freeswitch after receiving a 183 + SDP. I think that the problem is in SDP but I don't know where. The SDP that Freeswitch sends in INVITE is: v=0 o=FreeSWITCH 1324273767 1324273768 IN IP4 62.196.58.2 s=FreeSWITCH c=IN IP4 62.196.58.2 t=0 0 m=audio 52062 RTP/AVP 18 101 13 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 where the SDP that Freeswitch receives from the provider is: v=0 o=sansay-VSX 10 10 IN IP4 206.172.44.229 s=session controller c=IN IP4 206.172.44.229 t=0 0 m=audio 28364 RTP/AVP 18 150 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:150 telephone-event/8000 a=fmtp:150 0-15 a=ptime:20 After this SDP I see in the log: 2011-12-19 21:17:11.567017 [DEBUG] switch_ivr_originate.c:3364 Originate Resulted in Error Cause: 100 [INVALID_IE_CONTENTS] Can anyone give me an advice to solve this issue? Stephen
Export verbose_sdp=true before you bridge: http://wiki.freeswitch.org/wiki/Variable_verbose_sdp ...and set supress-cng to true on the profile. On Mon, Dec 19, 2011 at 3:30 PM, Stephen Wilde <wstephen80@gmail.com> wrote:
I have a problem with a provider where the call are dropped by Freeswitch after receiving a 183 + SDP. I think that the problem is in SDP but I don't know where. The SDP that Freeswitch sends in INVITE is:
v=0 o=FreeSWITCH 1324273767 1324273768 IN IP4 62.196.58.2 s=FreeSWITCH c=IN IP4 62.196.58.2 t=0 0 m=audio 52062 RTP/AVP 18 101 13 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20
where the SDP that Freeswitch receives from the provider is:
v=0 o=sansay-VSX 10 10 IN IP4 206.172.44.229 s=session controller c=IN IP4 206.172.44.229 t=0 0 m=audio 28364 RTP/AVP 18 150 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:150 telephone-event/8000 a=fmtp:150 0-15 a=ptime:20
After this SDP I see in the log:
2011-12-19 21:17:11.567017 [DEBUG] switch_ivr_originate.c:3364 Originate Resulted in Error Cause: 100 [INVALID_IE_CONTENTS]
Can anyone give me an advice to solve this issue?
Stephen
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Kristian Kielhofner
Ok, I solved this issue: the problem was the payload used by my provider for telephone-event that was 150 instead of 101. When the provider fixed this payload number all calls works fine. Stephen On Mon, Dec 19, 2011 at 9:30 PM, Stephen Wilde <wstephen80@gmail.com> wrote:
I have a problem with a provider where the call are dropped by Freeswitch after receiving a 183 + SDP. I think that the problem is in SDP but I don't know where. The SDP that Freeswitch sends in INVITE is:
v=0 o=FreeSWITCH 1324273767 1324273768 IN IP4 62.196.58.2 s=FreeSWITCH c=IN IP4 62.196.58.2 t=0 0 m=audio 52062 RTP/AVP 18 101 13 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20
where the SDP that Freeswitch receives from the provider is:
v=0 o=sansay-VSX 10 10 IN IP4 206.172.44.229 s=session controller c=IN IP4 206.172.44.229 t=0 0 m=audio 28364 RTP/AVP 18 150 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:150 telephone-event/8000 a=fmtp:150 0-15 a=ptime:20
After this SDP I see in the log:
2011-12-19 21:17:11.567017 [DEBUG] switch_ivr_originate.c:3364 Originate Resulted in Error Cause: 100 [INVALID_IE_CONTENTS]
Can anyone give me an advice to solve this issue?
Stephen
Wow, I'm sorry I missed that first time around. I hope your provider otherwise pays more attention to standards... RTP dynamic payload type 150 is completely invalid and out of range: http://www.iana.org/assignments/rtp-parameters The topend for dynamic payload types is 127. On Tue, Dec 20, 2011 at 9:33 AM, Stephen Wilde <wstephen80@gmail.com> wrote:
Ok, I solved this issue: the problem was the payload used by my provider for telephone-event that was 150 instead of 101. When the provider fixed this payload number all calls works fine.
Stephen
-- Kristian Kielhofner
participants (2)
-
Kristian Kielhofner
-
Stephen Wilde