[SIPForum-discussion] Call Failed with SIP 486 Busy for G.723 codec

[Sam]

Hi Amit,

It happens that the cause code mapping is wrong for different carrier and
they dont follow the standard mapping,
mapping can be changed for instance the for SIP 503 i have see providers
returing with cause code 480, all this possibilities happens because of grey
market.

Some providers initiate 180/183 when call reaches their gateway to cut down
the PDD and if the call is failing with no channels it should now return the
code 503 ; in such situation you will receive ring for some duration and the
503.

Codec has nothing to do with cause code 486 ( only if the provider's cause
code mapping is wrong !)

Regds
Sam



On Tue, Oct 5, 2010 at 6:44 PM, amit salunkhe <amitsalunkhe21 at gmail.com>wrote:

> Hi All
>
> Can anybody tell me is this possible if we orginate call with G723 codec
> for PLMN/PSTN mobile number, then that call will failed from destination
> side within 1/2 ring with SIP response 486 Busy?
>
> Here call flow is described below.
>
> USEE A---->SBC1----->SBC2------>TDM g/w1-------->mobile MSC--------->USER B
>
>
> Please lte me know what aree the different reasons for such call failure
> within 1 or 1/2 ring
>
>
> Regards
> Amit--
>
>
> _______________________________________________
> This is the SIP Forum discussion mailing list
> TO UNSUBSCRIBE, or edit your delivery options, please visit
> http://sipforum.org/mailman/listinfo/discussion
> Post to the list at discussion at sipforum.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20101007/7bdfa719/attachment-0002.html>