[asterisk-users] Asterisk sends 486 Busy Here instead of 600 Busy Everywhere

[Johansson Olle E]

22 apr 2008 kl. 14.41 skrev Aadilkhan Maniyar:

> Hi,
>
> We have a scenario wherein the endpoint needs to send a 600 Busy  
> Everywhere after receiving an INVITE. I am using SIPp as this end  
> point. SIPp is configured as UE2.
> Now when UE1 calls UE2 (SIPp) receives the INVITE and responds with  
> a 600 Busy Everywhere.
> But when Asterisk receives this 600 response it sends out a 486 Busy  
> Here to UE1.
>
> Ideally Asterisk should be relaying the 600 response. What I fail to  
> get is, why does Asterisk need to send 486 instead of 600.
>
> Is there any configuration that needs to be done in order to achieve  
> this or is this a default behavior of Asterisk.
>
> I am using Asterisk 1.4.17.

As Jared said, we're a multiprotocol PBX. When we receive an error  
code in a signalling channel - a channel driver - we have to translate  
all those codes into some sort of "esperanto" that we handle in the  
sip core. We might have a call that forks to both IAX2, ZAP and SIP  
and need to handle error codes from all those protocols, so we  
translate everything into ISDN cause codes. Now, ISDN haven't got any  
difference between local busy and "busy everywhere". So when we  
translate back, we pick the 486 code.

I hope you now understand why we always send out the same SIP error  
code as get on the outbound channel. We do follow IETF specifications  
for the translations.

Regards,
/Olle