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:
   ------------------------------------------------------------------------
   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:


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