[cisco-voip] ISDN call disconnect reason -- how to obtain...

[Wes Sisk]

Agreed:

http://www.cisco.com/en/US/tech/tk1077/technologies_tech_note09186a0080094e72.shtml

This works well with POTS to SIP or POTS to H.323.  If you're using MGCP 
controlled digital circuits then get the cause codes from CDR reports on 
CUCM. The digital channel on the gateway is controlled by CUCM.

Regards,
Wes

On 8/14/2011 10:27 PM, Nicholas Samios wrote:
>
> AAA/radius logs the cause code in AVPair, so you query historical 
> without enabling q931.
>
> e.g. we stuff it into a SQL db so can query on disconnect causes by 
> count, etc.
>
> Aug 15 10:24:08.758 WST: RADIUS:   Cisco AVpair       [1]   43 
> *"disconnect-text=normal call clearing (16)"***
>
> Aug 15 10:24:08.758 WST: RADIUS:  Vendor, Cisco       [26]  31
>
> Aug 15 10:24:08.758 WST: RADIUS:   Cisco AVpair       [1]   25  
> "peer-address=xxxxxxx"
>
> Aug 15 10:24:08.758 WST: RADIUS:  Vendor, Cisco       [26]  24
>
> Aug 15 10:24:08.758 WST: RADIUS:   Cisco AVpair       [1]   18  
> "info-type=speech"
>
> <snip>
>
> Aug 15 10:24:08.758 WST: RADIUS:  Acct-Status-Type    [40]  6   
> Stop                      [2]
>
> Aug 15 10:24:08.758 WST: RADIUS:  NAS-Port-Type       [61]  6   
> Async                     [0]
>
> Aug 15 10:24:08.758 WST: RADIUS:  NAS-Port            [5]   6   0
>
> Aug 15 10:24:08.758 WST: RADIUS:  NAS-Port-Id         [87]  14  "ISDN 
> 7/6:D:5"
>
> *From:*cisco-voip-bounces at puck.nether.net 
> [mailto:cisco-voip-bounces at puck.nether.net] *On Behalf Of *Tim Reimers
> *Sent:* Monday, August 15, 2011 4:28 AM
> *To:* cisco-voip at puck.nether.net
> *Subject:* [cisco-voip] ISDN call disconnect reason -- how to obtain...
>
> Hi all --
>
> Question about logging ISDN call disconnect reasons -
>
> I know that you can see the call disconnect reason in ISDN Q.931
>
> http://www.cisco.com/en/US/tech/tk801/tk379/technologies_tech_note09186a008012e95f.shtml
>
> Does anyone know if there's an IOS that supports using SNMP traps or 
> something to obtain the disconnect info and log it?
>
> I'm tracking down a random abandoned call issue in IPCC, and I want to 
> rule out any bad channels on the associated PRI.
>
> But I don't want to run in ISDN q.931 debug mode for days on end 
> logging all of that just so I can see what all the reported disconnect 
> reasons are.
>
> thanks, Tim
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110815/0bb65337/attachment.html>