Sponsor: VoiceMeUp - Corporate & Wholesale VoIP Services

VoIP Mailing List Archives
Mailing list archives for the VoIP community
 SearchSearch 

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


 
Post new topic   Reply to topic    VoIP Mailing List Archives Forum Index -> Asterisk Users
View previous topic :: View next topic  
Author Message
amaniyar at velankani.com
Guest





PostPosted: Wed Apr 30, 2008 12:43 am    Post subject: [asterisk-users] Asterisk sends 486 Busy Here instead of 600 Reply with quote

Thanks Olle and Jared for your reply. This clears a lot of my doubts.

Thanks once again.

Regards,
Aadil

-----Original Message-----
From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Johansson
Olle E
Sent: Wednesday, April 23, 2008 8:01 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Cc: 'Vinod Kumar Singh'
Subject: Re: [asterisk-users] Asterisk sends 486 Busy Here instead of
600Busy Everywhere
22 apr 2008 kl. 14.41 skrev Aadilkhan Maniyar:

Quote:
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

_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Back to top
Display posts from previous:   
Post new topic   Reply to topic    VoIP Mailing List Archives Forum Index -> Asterisk Users All times are GMT - 5 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group

VoiceMeUp - Corporate & Wholesale VoIP Services