[Freeswitch-users] 486 Busy Here with Reason: Q.850; cause=16; text="NORMAL_CLEARING"

[Steven Ayre]

Please post a debug-level log of the call.

How are you hanging up the call? If with the 'hangup' app what parameters
do you use?

In particular if you bridge and it fails with 486 then hangup then the SIP
code sent may be from the last bridge cause while the Q.850 cause is the
one given to hangup. If that's the case try setting
sip_ignore_remote_cause=true before the bridge and it'll only send the
Q.850->SIP mapping (https://tools.ietf.org/html/rfc3398).

Note there's no SIP code mapping for 16 though. If hanging up without
answering the call use a different cause.

-Steve



On 13 February 2013 15:17, Yuriy Nasida <nasida at live.ru> wrote:

>  Hi guys,
>
> I see that my FS sends sip message "486 Busy Here" with Reason: Q.850;
> cause=16;text="NORMAL_CLEARING".  Why 16 and "NORMAL_CLEARING ? Probably it
> should be 17 "user busy". One of my carrier play a "fast busy" (number not
> available)  and blames Q.850 field.
>
> Any advice are welcome.
> Thanks.
>
> _________________________________________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20130213/e75f0e31/attachment.html