[cisco-voip] Monitoring VoIP activity

[Vincent De Keyzer]

Chris,

 

thanks for your suggestion, but that's precisely my point.

 

With the Cisco debugs, you can get very detailed info, but it's actually too
detailed; and furthermore, it's all debugs, so you can't save that into the
config of the box.

 

The logs below are nice because:

*	you could bill CDRs on them
*	you can trace back problems if you have calling number, called
number and time of call.

 

Maybe I should be looking at some sort of radius accounting?...

 

Vincent

 

  _____  

From: chris donnelly [mailto:c.donnelly at skynetsystems.co.uk] 
Sent: jeudi 27 janvier 2005 18:50
To: Vincent De Keyzer; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Monitoring VoIP activity

 

I guess you've tried debug isdn q931 ?

 

More indepth IPT info can be got by debug voip ccapi inout

 

Chris

 

 

  _____  

From: Vincent De Keyzer [mailto:vincent at dekeyzer.net] 
Sent: 27 January 2005 13:40
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Monitoring VoIP activity

 

Hello,

 

I am used to non-Cisco H.323 GWs (OneAccess) which have a particularly nice
features - they easily produce logs like this:

 

12:10:15  Info VOX VOIP ControlPlan 3 Outgoing call on local port: 5/0,
calling: 02400XXXX, called: 02539XXXX, call-id: 175.

12:10:15  Info VOX VOIP ControlPlan 3 Incoming call on voip id: 0, calling:
02790XXXX, called: 02712XXXX, call-id: 176.

12:10:15  Info VOX VOIP ControlPlan 3 Outgoing call on local port: 5/0,
calling: 02790XXXX, called: 02712XXXX, call-id: 176.

12:10:16  Error VOX VOIP ControlPlan 1 Outgoing call failure on local port:
5/0, cause: (1)[Unallocated (unassigned) number], call-id: 175.

12:10:16  Info VOX VOIP ControlPlan 3 Alert in band received, call-id: 174.

12:10:16  Info VOX VOIP UserPlan 3 VoIP RTP transmission started, coder:
G711 A Law, call-id: 174.

12:10:16  Info VOX VOIP UserPlan 3 VoIP RTP reception started, coder: G711 A
Law, call-id: 174.

12:10:17  Warning VOX VOIP UserPlan 2 2 Voice packets lost on local port
5/0, call-id: 172.

12:10:18  Info VOX VOIP ControlPlan 3 Alert in band received, call-id: 176.

12:10:18  Info VOX VOIP UserPlan 3 VoIP RTP transmission started, coder:
G711 A Law, call-id: 176.

12:10:18  Info VOX VOIP UserPlan 3 VoIP RTP reception started, coder: G711 A
Law, call-id: 176.

12:10:18  Info VOX VOIP ControlPlan 3 Call connected, call-id: 172.

12:10:20  Info VOX VOIP ControlPlan 3 Call connected, call-id: 176.

12:10:22  Info VOX VOIP ControlPlan 3 Call connected, call-id: 174.

12:10:22  Warning VOX VOIP UserPlan 2 1 Excessive Jitter on local port 5/0,
call-id: 176.

12:10:24  Info VOX VOIP UserPlan 3 VoIP RTP transmission stopped, coder:
G711 A Law, call-id: 169.

12:10:24  Info VOX VOIP UserPlan 3 VoIP RTP reception stopped, coder: G711 A
Law, call-id: 169.

12:10:24  Info VOX VOIP ControlPlan 3 Call Disconnection received on voip
id: 0, cause: (16)[Normal call clearing], call-id: 169.

12:10:26  Info VOX VOIP ControlPlan 3 Call Disconnection received on local
port: 5/0, cause: (16)[Normal call clearing], call-id: 162.

12:10:26  Info VOX VOIP UserPlan 3 VoIP RTP transmission stopped, coder:
G711 A Law, call-id: 162.

12:10:26  Info VOX VOIP UserPlan 3 VoIP RTP reception stopped, coder: G711 A
Law, call-id: 162.

12:10:32  Warning VOX VOIP UserPlan 2 1 Voice packets lost on local port
5/0, call-id: 153.

12:10:32  Warning VOX VOIP UserPlan 2 1 Voice packets lost on local port
5/0, call-id: 157.

 

. which I find very helpful.

 

Is there a way to produce something similar on a Cisco box (HW = 2821, SW =
12.3T)?

 

 


_____________________________________________________________________
This message has been checked for all known viruses by the MessageLabs Virus
Control Centre.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20050207/539ea71f/attachment.html