ESL + BYE SIP reason code
25 Aug
2016
25 Aug
'16
3:15 a.m.
Hi guys,
I'm getting the following BYE reason code from my Service Provider:
recv 740 bytes from udp/[177.71.206.193]:5060 at 02:57:50.740042:
------------------------------------------------------------------------
BYE sip:gw+twilio@52.1.1.1:5090;transport=udp;gw=twilio SIP/2.0
CSeq: 1 BYE
From: <sip:+551121174769@turn2data-telephonist.pstn.br1.twilio.com
>;tag=76430350_6772d868_ebbbd5d1-d9b1-49db-981e-ec4b3e238564
To: "" <sip:+55114XXXYYYY@172.31.3.166>;tag=mjZyjF9Ute8DD
Call-ID: 7d8a1944-e512-1234-4eaf-02d310a86cb3
Max-Forwards: 68
Via: SIP/2.0/UDP 177.71.206.193:5060;branch=z9hG4bKfaa.6c72ded1.0
Via: SIP/2.0/UDP 172.19.147.73:5060
;rport=5060;received=177.71.206.215;branch=z9hG4bKebbbd5d1-d9b1-49db-981e-ec4b3e238564_6772d868_205642673073712
* Reason: MVTSLocal;cause=10;text="BYE
received",SIP;cause=406;text="Service Unavailable"*
User-Agent: Twilio Gateway
X-Twilio-CallSid: CA5411d5015d3df04541c6e14e9fb41719
Content-Length: 0
When placing call via ESL I get reported NORMAL_CLEARING vs 406
I don't see 406 Listed in Wiki:
https://freeswitch.org/confluence/display/FREESWITCH/Hangup+Cause+Code+Table
According to RFC seems to be valid https://tools.ietf.org/html/rfc3326
Examples are:
Reason: SIP ;cause=200 ;text="Call completed elsewhere"
Reason: Q.850 ;cause=16 ;text="Terminated"
Reason: SIP ;cause=600 ;text="Busy Everywhere"
Reason: SIP ;cause=580 ;text="Precondition Failure"
Can we add support to handle these type of reasons to a common one ? Like
Unknown?
I will talk to my SP to see if they can change it to 503.
Any suggestions?
25 Aug
25 Aug
4:01 a.m.
This is how I originate my calls with originate:
originate
{sip_h_X-UUID=5c35e46e-ygoe-xdk4-upt2-2db3-5c35eefa6a,sip_h_X-Campaign=OYWS8285XR,ignore_early_media=false,bridge_early_media=false,originate_timeout=24,call_timeout=24,leg_timeout=30,execute_on_answer_1='sched_hangup
18
ALLOTTED_TIMEOUT',origination_uuid=5c35e46e-ygoe-xdk4-upt2-2db3-5c35eefa6a,origination_caller_id_number=+55214042XXYY}sofia/gateway/twilio/+55213497ZZWW
handle_calls
<extension name="telephonist">
<condition field="destination_number" expression="^handle_calls$">
<action application="answer"/>
<action application="log" data="INFO handle_calls
application match"/>
<action application="set" data=
"transfer_ringback=${us-ring}"/>
<action application="spandsp_start_fax_detect" data="transfer
'fax' 10 ced"/>
<action application="spandsp_start_tone_detect" data="55"/>
<action application="playback" data="silence_stream://20000"
/>
<action application="spandsp_stop_tone_detect"/>
</condition>
</extension>
On Wed, Aug 24, 2016 at 8:15 PM, Gonzalo Gasca Meza <gascagonzalo@gmail.com>
wrote:
> Hi guys,
>
> I'm getting the following BYE reason code from my Service Provider:
>
> recv 740 bytes from udp/[177.71.206.193]:5060 at 02:57:50.740042:
> -----------------------------------------------------------
> -------------
> BYE sip:gw+twilio@52.1.1.1:5090;transport=udp;gw=twilio SIP/2.0
> CSeq: 1 BYE
> From: <sip:+551121174769@turn2data-telephonist.pstn.br1.twilio.com
> >;tag=76430350_6772d868_ebbbd5d1-d9b1-49db-981e-ec4b3e238564
> To: "" <sip:+55114XXXYYYY@172.31.3.166>;tag=mjZyjF9Ute8DD
> Call-ID: 7d8a1944-e512-1234-4eaf-02d310a86cb3
> Max-Forwards: 68
> Via: SIP/2.0/UDP 177.71.206.193:5060;branch=z9hG4bKfaa.6c72ded1.0
> Via: SIP/2.0/UDP 172.19.147.73:5060;rport=5060;received=177.71.206.215;
> branch=z9hG4bKebbbd5d1-d9b1-49db-981e-ec4b3e238564_
> 6772d868_205642673073712
> * Reason: MVTSLocal;cause=10;text="BYE
> received",SIP;cause=406;text="Service Unavailable"*
> User-Agent: Twilio Gateway
> X-Twilio-CallSid: CA5411d5015d3df04541c6e14e9fb41719
> Content-Length: 0
>
> When placing call via ESL I get reported NORMAL_CLEARING vs 406
>
> I don't see 406 Listed in Wiki:
>
> https://freeswitch.org/confluence/display/FREESWITCH/
> Hangup+Cause+Code+Table
>
> According to RFC seems to be valid https://tools.ietf.org/html/rfc3326
>
> Examples are:
>
> Reason: SIP ;cause=200 ;text="Call completed elsewhere"
> Reason: Q.850 ;cause=16 ;text="Terminated"
> Reason: SIP ;cause=600 ;text="Busy Everywhere"
> Reason: SIP ;cause=580 ;text="Precondition Failure"
>
>
> Can we add support to handle these type of reasons to a common one ? Like
> Unknown?
> I will talk to my SP to see if they can change it to 503.
>
> Any suggestions?
>
3:28 p.m.
406 is currently mapped to SWITCH_CAUSE_SERVICE_NOT_IMPLEMENTED which appears correct to me. What are you suggesting we change exactly?
On Aug 24, 2016, at 11:15 PM, Gonzalo Gasca Meza <gascagonzalo@gmail.com> wrote:
Hi guys,
I'm getting the following BYE reason code from my Service Provider:
recv 740 bytes from udp/[177.71.206.193]:5060 at 02:57:50.740042: ------------------------------------------------------------------------ BYE sip:gw+twilio@52.1.1.1:5090;transport=udp;gw=twilio SIP/2.0 CSeq: 1 BYE From: <sip:+551121174769@turn2data-telephonist.pstn.br1.twilio.com <mailto:sip%3A%2B551121174769@turn2data-telephonist.pstn.br1.twilio.com>>;tag=76430350_6772d868_ebbbd5d1-d9b1-49db-981e-ec4b3e238564 To: "" <sip:+55114XXXYYYY@172.31.3.166 <mailto:sip%3A%2B55114XXXYYYY@172.31.3.166>>;tag=mjZyjF9Ute8DD Call-ID: 7d8a1944-e512-1234-4eaf-02d310a86cb3 Max-Forwards: 68 Via: SIP/2.0/UDP 177.71.206.193:5060;branch=z9hG4bKfaa.6c72ded1.0 Via: SIP/2.0/UDP 172.19.147.73:5060;rport=5060;received=177.71.206.215;branch=z9hG4bKebbbd5d1-d9b1-49db-981e-ec4b3e238564_6772d868_205642673073712 Reason: MVTSLocal;cause=10;text="BYE received",SIP;cause=406;text="Service Unavailable" User-Agent: Twilio Gateway X-Twilio-CallSid: CA5411d5015d3df04541c6e14e9fb41719 Content-Length: 0
When placing call via ESL I get reported NORMAL_CLEARING vs 406
I don't see 406 Listed in Wiki:
https://freeswitch.org/confluence/display/FREESWITCH/Hangup+Cause+Code+Table <https://freeswitch.org/confluence/display/FREESWITCH/Hangup+Cause+Code+Table>
According to RFC seems to be valid https://tools.ietf.org/html/rfc3326 <https://tools.ietf.org/html/rfc3326>
Examples are:
Reason: SIP ;cause=200 ;text="Call completed elsewhere" Reason: Q.850 ;cause=16 ;text="Terminated" Reason: SIP ;cause=600 ;text="Busy Everywhere" Reason: SIP ;cause=580 ;text="Precondition Failure"
Can we add support to handle these type of reasons to a common one ? Like Unknown? I will talk to my SP to see if they can change it to 503.
Any suggestions? <ESL_ERROR>_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.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
26 Aug
26 Aug
12:13 a.m.
That still differs from the NORMAL_CLEARING he's saying he's getting. Gonzalo, check what other variables exist in case the 406 appears in a variable. proto_specific_cause often would but might not given that this was a BYE for a successful call. On 25 August 2016 at 16:28, Michael Jerris <mike@jerris.com> wrote: > 406 is currently mapped to SWITCH_CAUSE_SERVICE_NOT_IMPLEMENTED which > appears correct to me. What are you suggesting we change exactly? > > > On Aug 24, 2016, at 11:15 PM, Gonzalo Gasca Meza <gascagonzalo@gmail.com> > wrote: > > Hi guys, > > I'm getting the following BYE reason code from my Service Provider: > > recv 740 bytes from udp/[177.71.206.193]:5060 at 02:57:50.740042: > ----------------------------------------------------------- > ------------- > BYE sip:gw+twilio@52.1.1.1:5090;transport=udp;gw=twilio SIP/2.0 > CSeq: 1 BYE > From: <sip:+551121174769@turn2data-telephonist.pstn.br1.twilio.com > >;tag=76430350_6772d868_ebbbd5d1-d9b1-49db-981e-ec4b3e238564 > To: "" <sip:+55114XXXYYYY@172.31.3.166>;tag=mjZyjF9Ute8DD > Call-ID: 7d8a1944-e512-1234-4eaf-02d310a86cb3 > Max-Forwards: 68 > Via: SIP/2.0/UDP 177.71.206.193:5060;branch=z9hG4bKfaa.6c72ded1.0 > Via: SIP/2.0/UDP 172.19.147.73:5060;rport=5060;received=177.71.206.215; > branch=z9hG4bKebbbd5d1-d9b1-49db-981e-ec4b3e238564_ > 6772d868_205642673073712 > * Reason: MVTSLocal;cause=10;text="BYE > received",SIP;cause=406;text="Service Unavailable"* > User-Agent: Twilio Gateway > X-Twilio-CallSid: CA5411d5015d3df04541c6e14e9fb41719 > Content-Length: 0 > > When placing call via ESL I get reported NORMAL_CLEARING vs 406 > > I don't see 406 Listed in Wiki: > > https://freeswitch.org/confluence/display/FREESWITCH/ > Hangup+Cause+Code+Table > > According to RFC seems to be valid https://tools.ietf.org/html/rfc3326 > > Examples are: > > Reason: SIP ;cause=200 ;text="Call completed elsewhere" > Reason: Q.850 ;cause=16 ;text="Terminated" > Reason: SIP ;cause=600 ;text="Busy Everywhere" > Reason: SIP ;cause=580 ;text="Precondition Failure" > > > Can we add support to handle these type of reasons to a common one ? Like > Unknown? > I will talk to my SP to see if they can change it to 503. > > Any suggestions? > <ESL_ERROR>_________________________________________________ > ________________________ > Professional FreeSWITCH Consulting Services: > consulting@freeswitch.org > http://www.freeswitchsolutions.com > > Official FreeSWITCH Sites > http://www.freeswitch.org > http://confluence.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 > > > > _________________________________________________________________________ > Professional FreeSWITCH Consulting Services: > consulting@freeswitch.org > http://www.freeswitchsolutions.com > > Official FreeSWITCH Sites > http://www.freeswitch.org > http://confluence.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 >
12:31 a.m.
You can follow the fun on FS-9460. Short story is we don't support multiple reason headers On Thursday, August 25, 2016, Steven Ayre <steveayre@gmail.com> wrote: > That still differs from the NORMAL_CLEARING he's saying he's getting. > > Gonzalo, check what other variables exist in case the 406 appears in a > variable. proto_specific_cause often would but might not given that this > was a BYE for a successful call. > > On 25 August 2016 at 16:28, Michael Jerris <mike@jerris.com > <javascript:_e(%7B%7D,'cvml','mike@jerris.com');>> wrote: > >> 406 is currently mapped to SWITCH_CAUSE_SERVICE_NOT_IMPLEMENTED which >> appears correct to me. What are you suggesting we change exactly? >> >> >> On Aug 24, 2016, at 11:15 PM, Gonzalo Gasca Meza <gascagonzalo@gmail.com >> <javascript:_e(%7B%7D,'cvml','gascagonzalo@gmail.com');>> wrote: >> >> Hi guys, >> >> I'm getting the following BYE reason code from my Service Provider: >> >> recv 740 bytes from udp/[177.71.206.193]:5060 at 02:57:50.740042: >> ----------------------------------------------------------- >> ------------- >> BYE sip:gw+twilio@52.1.1.1:5090;transport=udp;gw=twilio SIP/2.0 >> CSeq: 1 BYE >> From: <sip:+551121174769@turn2data-telephonist.pstn.br1.twilio.com >> <javascript:_e(%7B%7D,'cvml','sip:%2B551121174769@turn2data-telephonist.pstn.br1.twilio.com');> >> >;tag=76430350_6772d868_ebbbd5d1-d9b1-49db-981e-ec4b3e238564 >> To: "" <sip:+55114XXXYYYY@172.31.3.166 >> <javascript:_e(%7B%7D,'cvml','sip:%2B55114XXXYYYY@172.31.3.166');> >> >;tag=mjZyjF9Ute8DD >> Call-ID: 7d8a1944-e512-1234-4eaf-02d310a86cb3 >> Max-Forwards: 68 >> Via: SIP/2.0/UDP 177.71.206.193:5060;branch=z9hG4bKfaa.6c72ded1.0 >> Via: SIP/2.0/UDP 172.19.147.73:5060;rport=5060; >> received=177.71.206.215;branch=z9hG4bKebbbd5d1-d9b1-49db- >> 981e-ec4b3e238564_6772d868_205642673073712 >> * Reason: MVTSLocal;cause=10;text="BYE >> received",SIP;cause=406;text="Service Unavailable"* >> User-Agent: Twilio Gateway >> X-Twilio-CallSid: CA5411d5015d3df04541c6e14e9fb41719 >> Content-Length: 0 >> >> When placing call via ESL I get reported NORMAL_CLEARING vs 406 >> >> I don't see 406 Listed in Wiki: >> >> https://freeswitch.org/confluence/display/FREESWITCH/Hangup+ >> Cause+Code+Table >> >> According to RFC seems to be valid https://tools.ietf.org/html/rfc3326 >> >> Examples are: >> >> Reason: SIP ;cause=200 ;text="Call completed elsewhere" >> Reason: Q.850 ;cause=16 ;text="Terminated" >> Reason: SIP ;cause=600 ;text="Busy Everywhere" >> Reason: SIP ;cause=580 ;text="Precondition Failure" >> >> >> Can we add support to handle these type of reasons to a common one ? Like >> Unknown? >> I will talk to my SP to see if they can change it to 503. >> >> Any suggestions? >> <ESL_ERROR>_________________________________________________ >> ________________________ >> Professional FreeSWITCH Consulting Services: >> consulting@freeswitch.org >> <javascript:_e(%7B%7D,'cvml','consulting@freeswitch.org');> >> http://www.freeswitchsolutions.com >> >> Official FreeSWITCH Sites >> http://www.freeswitch.org >> http://confluence.freeswitch.org >> http://www.cluecon.com >> >> FreeSWITCH-users mailing list >> FreeSWITCH-users@lists.freeswitch.org >> <javascript:_e(%7B%7D,'cvml','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 >> >> >> >> _________________________________________________________________________ >> Professional FreeSWITCH Consulting Services: >> consulting@freeswitch.org >> <javascript:_e(%7B%7D,'cvml','consulting@freeswitch.org');> >> http://www.freeswitchsolutions.com >> >> Official FreeSWITCH Sites >> http://www.freeswitch.org >> http://confluence.freeswitch.org >> http://www.cluecon.com >> >> FreeSWITCH-users mailing list >> FreeSWITCH-users@lists.freeswitch.org >> <javascript:_e(%7B%7D,'cvml','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 >> > >
3722
Age (days ago)
3723
Last active (days ago)
4 comments
3 participants
participants (3)
-
Gonzalo Gasca Meza
-
Michael Jerris
-
Steven Ayre