[Freeswitch-users] Confusion about sip hangup cause Q850 hangup cause and long struggles with a provider.

[Sias Mey]

Actually Anthony your wiki and code are accurate .. the rfc maps the translations different depending on direction.

Q.850 18 = sip 408
sip 408 = Q.850 102

sip 480 = Q.850 18

Is there a way for me to access the reason header from the sip message?

----- Original Message -----
From: "Steven Ayre" <steveayre at gmail.com>
To: "FreeSWITCH Users Help" <freeswitch-users at lists.freeswitch.org>
Sent: Sunday, 9 September, 2012 5:59:22 PM
Subject: Re: [Freeswitch-users] Confusion about sip hangup cause Q850 hangup cause and long struggles with a provider.

Shouldn't the presence of a Reason header in the 408 from the callee
override the default rfc mapping though?

-Steve



On 8 September 2012 22:27, Anthony Minessale
<anthony.minessale at gmail.com> wrote:
> I think our wiki is less accurate than our code:  Our cause mappings are
> straight from RFC 4497 http://tools.ietf.org/html/rfc4497
>
> Here is an excerpt:
>
>  408 Request timeout                 102 Recovery on timer expiry
>
>  504 Gateway time-out                102 Recovery on timer expiry
>
>
>
>
>
> On Fri, Sep 7, 2012 at 3:39 AM, Sias Mey <sias at cpdata.co.za> wrote:
>>
>> Hi, Im sure this subject has been beaten to death .. but many googles and
>> many email searches hasent really managed to find me something.
>>
>> Im a dev for a small company that writes call center software. Freeswitch
>> was a godsend, thank you.
>>
>> Now .. the confusion.
>>
>> We are getting a lot of what seem to be strange hangup codes from a new
>> provider big fights about loads of failled calls ensued blah blah.. much sip
>> packet logging and manual inspection later.. I found the following.
>>
>> from xmlcdr.
>>
>>
>>     <sip_hangup_disposition>recv_refuse</sip_hangup_disposition>
>>     <sip_term_status>408</sip_term_status>
>>     <proto_specific_hangup_cause>sip%3A408</proto_specific_hangup_cause>
>>     <sip_term_cause>102</sip_term_cause>
>>     <hangup_cause>RECOVERY_ON_TIMER_EXPIRE</hangup_cause>
>>     <hangup_cause_q850>102</hangup_cause_q850>
>>
>> this just to show its the same call
>>     <sip_call_id>0d4d4e76-735a-1230-d2ac-000423b5571b</sip_call_id>
>>
>> and from the sip messages.
>>
>> SIP/2.0 408 Request Timeout
>> Call-ID: 0d4d4e76-735a-1230-d2ac-000423b5571b
>> Reason: Q.850;cause=18;text="no user responding"
>>
>> And according to the very useful wiki page on Q.850 codes 408 should = 18
>> like it does in the providers response.
>>
>> Why then is the q850 hangup cause in the CDR 102? and where does that
>> translation come from.
>>
>> This is a single example but I also have loads and loads where the CDR
>> claims q850 code 18 but the sip messages provide 31 or a range of other
>> codes.
>> I can understand if the q850 code from the sip message is not being read
>> by FS since FS has to be a bit more agnostic than that and in the pas I have
>> almost exclusively worked with direct connections to TDM hardware so my
>> knowledge and understanding of the sip messages is rather limited. But even
>> in that case, shouldent the q850 code in the cdr at least conform to the
>> translation from the wiki page?
>>
>> Oh I am not currently running the latest git release, having some libtiff
>> issues on ubuntu to compile. I will respond to this again if I manage that
>> and it helps matters.
>>
>> Thank you for your time and help,
>> Regards
>> Sias
>>
>> _________________________________________________________________________
>> Professional FreeSWITCH Consulting Services:
>> consulting at freeswitch.org
>> http://www.freeswitchsolutions.com
>>
>> 
>> 
>>
>> Official FreeSWITCH Sites
>> http://www.freeswitch.org
>> http://wiki.freeswitch.org
>> http://www.cluecon.com
>>
>> FreeSWITCH-users mailing list
>> FreeSWITCH-users at lists.freeswitch.org
>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
>> http://www.freeswitch.org
>>
>
>
>
> --
> Anthony Minessale II
>
> FreeSWITCH http://www.freeswitch.org/
> ClueCon http://www.cluecon.com/
> Twitter: http://twitter.com/FreeSWITCH_wire
>
> AIM: anthm
> MSN:anthony_minessale at hotmail.com
> GTALK/JABBER/PAYPAL:anthony.minessale at gmail.com
> IRC: irc.freenode.net #freeswitch
>
> FreeSWITCH Developer Conference
> sip:888 at conference.freeswitch.org
> googletalk:conf+888 at conference.freeswitch.org
> pstn:+19193869900
>
> _________________________________________________________________________
> Professional FreeSWITCH Consulting Services:
> consulting at freeswitch.org
> http://www.freeswitchsolutions.com
>
> 
> 
>
> Official FreeSWITCH Sites
> http://www.freeswitch.org
> http://wiki.freeswitch.org
> http://www.cluecon.com
>
> FreeSWITCH-users mailing list
> FreeSWITCH-users at 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 at freeswitch.org
http://www.freeswitchsolutions.com




Official FreeSWITCH Sites
http://www.freeswitch.org
http://wiki.freeswitch.org
http://www.cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users at lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org