Hangup cause gives ISDN cause codes. 

Its easier with sip 4xx or 5xx as there are only 2 to check. So, looking to
get sip reason.

 

From: asterisk-users-boun...@lists.digium.com
[mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Robert Thomas
Sent: 03 March 2011 02:28
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] Failover Routing

 

What value do you get from the hangup cause, are they different?

 

I think  can you use a gotoif checking the hangup cause.

On Wed, Mar 2, 2011 at 12:43 PM, Tilghman Lesher <tilgh...@meg.abyt.es>
wrote:

On Wednesday 02 March 2011 07:06:31 Andrew Thomas wrote:
> It seems like it is a v1.8 only function at present (unless a backport
> is released).
>
> From http://www.voip-info.org/wiki/view/Asterisk+variable+hangupcause
>
> -----
> Asterisk 1.8 will allow to read SIP response codes in the dialplan via
>
>  ${HASH(SIP_CAUSE,<channel-name>)}
>
> Asterisk 1.8 also comes with a 'use_q850_reason' configuration option
> for generating and parsing, if available: -----
>
> That will give you what you want if you consider upgrading to v1.8.

A backport on this is not possible.  It depends upon some core
functionality introduced in the 1.8 branch.

--
Tilghman

--

_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
              http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users




-- 
Robert

--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
               http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to