Antonio,
I checked out VoIP-info. The only thing is, I've seen a lot
of mention about
PRI/ISDN and our setup is all over IP. We use VoIP carriers,
and our
Asterisk connects over IP, not any TDM/BRI, etc. Which is
what is making it
hard for me to get a real cause in $.
Do you think your patch can help out?
Thank you,
Mark.
-----Original Message-----
From: asterisk-dev-bounces lists.digium.com
[mailto:asterisk-dev-bounceslists.digium.com] On Behalf
Of Antonio Gallo
Sent: March 20, 2008 3:27 AM
To: Asterisk Developers Mailing List
Subject: Re: [asterisk-dev] SIP error codes interpreted by
Asterisk as?
Johansson Olle E ha scritto:
>> Because when a call is made through Asterisk, and
let's say it's a
>> disconnected number, Asterisk returns "Call
failed, reason 0" or a
>> reason number from 1-10. What makes Asterisk decide
what reason is a
>> SIP error code classified as?
> In chan_sip we translate those error codes to the ISDN
hangup causes
> we use internally in Asterisk, which you can reach
> in the HANGUPCAUSE dialplan variable. We follow the
IETF standards
> where available, or the Cisco implementation.
If you go to voip-info.org there is a really nice page about
it.
I've an unofficial patch for chan_misdn to break a DIAL()
with the
option "Q" after the ISDN DISCONNECT message has
been returned that can
be used by telemarketing for quickly classify the dialed
number without
messing around with the Telco post-call audio (like, the
number does not
exists, the mobile is shutted off now, etc.)
_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.c
om--
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.c
om--
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
|
