On 04/25/2012 07:08 AM, Bryant Zimmerman wrote:
I can log the ISDN cause code using ${HANGUPCAUSE} but I also need to
track the actual SIP response code as well. How do I get access to it
durring the hangup?
It's rather hard to answer that question without at least knowing what version of Asterisk you are using. In some versions there is a SIP_CAUSE feature that can be used to extract that information (although this has been reimplemented for Asterisk 11 in a way that doesn't affect performance as much as the old method did).
--
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
Jabber: kfleming@xxxxxxxxxx | SIP: kpfleming@xxxxxxxxxx | Skype: kpfleming
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at www.digium.com & www.asterisk.org
--
_____________________________________________________________________
-- 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
[Gnu Gatekeeper] [IETF Sipping] [Info Cyrus] [ALSA User] [Fedora Linux Users] [DCCP] [Gimp] [100% Free Online Dating] [Yosemite News] [Arts & Crafts] [Yosemite Photos] [Deep Creek Hot Springs] [Yosemite Campsites] [ISDN Cause Codes]
|
|