Aadilkhan Maniyar
2008-Apr-22 12:41 UTC
[asterisk-users] Asterisk sends 486 Busy Here instead of 600 Busy Everywhere
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. Thanks in Advance. Regards, Aadil -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20080422/77993bda/attachment.htm
Jared Smith
2008-Apr-22 14:39 UTC
[asterisk-users] Asterisk sends 486 Busy Here instead of 600 Busy Everywhere
On Tue, 2008-04-22 at 18:11 +0530, Aadilkhan Maniyar wrote:> Ideally Asterisk should be relaying the 600 response. What I fail to > get is, why does Asterisk need to send 486 instead of 600. >Asterisk is a back-to-back user agent (not a proxy!), and as such, it doesn't always relay the exact same SIP responses back to the first leg of the call.> > Is there any configuration that needs to be done in order to achieve > this or is this a default behavior of Asterisk.Right now, I don't know of any configuration that can be done with Asterisk that can achieve that behavior. Somebody smarter than I am will have to answer the question of how hard it would be to change the Asterisk source code to do that (and whether or not that's the right thing for Asterisk to do). -- Jared Smith Community Relations Manager Digium, Inc.
Johansson Olle E
2008-Apr-23 14:30 UTC
[asterisk-users] Asterisk sends 486 Busy Here instead of 600 Busy Everywhere
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