troubleshoot voice

Answered Question
Oct 11th, 2010

Hello there,

Cisco Unified Communications Manager Express Version 7.0(0).

CME#show call active voice compact
  <callID>  A/O FAX T<sec> Codec       type        Peer Address       IP R<ip>:<udp>
Total call-legs: 111
                52 ANS     T0     g729r8      VOIP        P022224919     172.22.254.5:18208
                92 ANS     T0     g729r8      VOIP        P594     172.22.254.5:19118
              132 ANS     T0     g729r8      VOIP        P594     172.22.254.5:19334
              180 ANS     T0     g729r8      VOIP        P594     172.22.254.5:17142
              224 ANS     T0     g729r8      VOIP        P594     172.22.254.5:18408
              303 ANS     T0     g729r8      VOIP        P594     172.22.254.5:19306
              381 ANS     T0     g729r8      VOIP        P560     172.22.254.5:17840
              417 ANS     T0     g729r8      VOIP        P449     172.22.254.5:17594
              437 ANS     T0     g729r8      VOIP        P449     172.22.254.5:17036
              486 ANS     T0     g729r8      VOIP        P022224919     172.22.254.5:19198
              625 ANS     T0     g729r8      VOIP        P449     172.22.254.5:16412
              694 ANS     T0     g729r8      VOIP        P560     172.22.254.5:18208
              -----------------------------------------------------------------------------

CME#show call active voice brief
<ID>: <CallID> <start>ms.<index>  +<connect> pid:<peer_id> <dir> <addr>  <state> 
    dur hh:mm:ss tx:<packets>/<bytes> rx:<packets>/<bytes>
  IP <ip>:<udp> rtt:<time>ms pl:<play>/<gap>ms lost:<lost>/<early>/<late>
    delay:<last>/<min>/<max>ms <codec>
   
  media inactive detected:<y/n> media cntrl rcvd:<y/n> timestamp:<time>
   
  long duration call detected:<y/n> long duration call duration :<sec> timestamp:<time>
    MODEMPASS <method> buf:<fills>/<drains> loss <overall%> <multipkt>/<corrected>
      last <buf event time>s dur:<Min>/<Max>s
  FR <protocol> [int dlci cid] vad:<y/n> dtmf:<y/n> seq:<y/n>
    <codec> (payload size)
  ATM <protocol> [int vpi/vci cid] vad:<y/n> dtmf:<y/n> seq:<y/n>
    <codec> (payload size)
  Tele <int> (callID) [channel_id]  tx:<tot>/<v>/<fax>ms <codec> noise:<l>  acom:<l> i/o:<l>/<l> dBm
    MODEMRELAY info:<rcvd>/<sent>/<resent>  xid:<rcvd>/<sent>  total:<rcvd>/<sent>/<drops>
                  speeds(bps): local <rx>/<tx> remote <rx>/<tx>
  Proxy <ip>:<audio udp>,<video  udp>,<tcp0>,<tcp1>,<tcp2>,<tcp3> endpt:  <type>/<manf>
  bw: <req>/<act> codec: <audio>/<video>
    tx: <audio pkts>/<audio bytes>,<video pkts>/<video bytes>,<t120 pkts>/<t120 bytes>
  rx: <audio pkts>/<audio bytes>,<video pkts>/<video bytes>,<t120 pkts>/<t120 bytes>

Telephony call-legs: 1
SIP call-legs: 0
H323 call-legs: 110
Call agent controlled call-legs: 0
SCCP call-legs: 0
Multicast call-legs: 0
Total call-legs: 111
11ED : 52 12811500ms.2 +-1 pid:10 Answer 022224919 connected
  dur 00:00:00 tx:0/0 rx:0/0
  IP 172.22.254.5:18208 SRTP: off rtt:0ms pl:0/0ms lost:0/0/0 delay:0/0/0ms g729r8 TextRelay: off
  media inactive detected:n media contrl rcvd:n/a timestamp:n/a
  long duration call detected:n long duration call duration:n/a timestamp:n/a
11F7 : 92 12869080ms.1 +-1 pid:5 Answer 594 connected
  dur 00:00:00 tx:0/0 rx:0/0
  IP 172.22.254.5:19118 SRTP: off rtt:0ms pl:0/0ms lost:0/0/0 delay:0/0/0ms g729r8 TextRelay: off
  media inactive detected:n media contrl rcvd:n/a timestamp:n/a
  long duration call detected:n long duration call duration:n/a timestamp:n/a
1201 : 132 12890890ms.1 +-1 pid:5 Answer 594 connected
  dur 00:00:00 tx:0/0 rx:0/0
  IP 172.22.254.5:19334 SRTP: off rtt:0ms pl:0/0ms lost:0/0/0 delay:0/0/0ms g729r8 TextRelay: off
  media inactive detected:n media contrl rcvd:n/a timestamp:n/a
  long duration call detected:n long duration call duration:n/a timestamp:n/a
120D : 180 12905790ms.1 +-1 pid:5 Answer 594 connected
  dur 00:00:00 tx:0/0 rx:0/0
  IP 172.22.254.5:17142 SRTP: off rtt:0ms pl:0/0ms lost:0/0/0 delay:0/0/0ms g729r8 TextRelay: off
  media inactive detected:n media contrl rcvd:n/a timestamp:n/a
  long duration call detected:n long duration call duration:n/a timestamp:n/a
1217 : 224 13100380ms.1 +-1 pid:5 Answer 594 connected
  dur 00:00:00 tx:0/0 rx:0/0
  IP 172.22.254.5:18408 SRTP: off rtt:0ms pl:0/0ms lost:0/0/0 delay:0/0/0ms g729r8 TextRelay: off
  media inactive detected:n media contrl rcvd:n/a timestamp:n/a
  long duration call detected:n long duration call duration:n/a timestamp:n/a
122C : 303 13293190ms.1 +-1 pid:5 Answer 594 connected
  dur 00:00:00 tx:0/0 rx:0/0
  IP 172.22.254.5:19306 SRTP: off rtt:0ms pl:0/0ms lost:0/0/0 delay:0/0/0ms g729r8 TextRelay: off
  media inactive detected:n media contrl rcvd:n/a timestamp:n/a
  long duration call detected:n long duration call duration:n/a timestamp:n/a
1243 : 381 13448760ms.2 +-1 pid:5 Answer 560 connected
  dur 00:00:00 tx:0/0 rx:0/0
  IP 172.22.254.5:17840 SRTP: off rtt:0ms pl:0/0ms lost:0/0/0 delay:0/0/0ms g729r8 TextRelay: off
  media inactive detected:n media contrl rcvd:n/a timestamp:n/a
  long duration call detected:n long duration call duration:n/a timestamp:n/a
124C : 417 13464640ms.1 +-1 pid:4 Answer 449 connected
  dur 00:00:00 tx:0/0 rx:0/0
  IP 172.22.254.5:17594 SRTP: off rtt:0ms pl:0/0ms lost:0/0/0 delay:0/0/0ms g729r8 TextRelay: off
  media inactive detected:n media contrl rcvd:n/a timestamp:n/a
  long duration call detected:n long duration call duration:n/a timestamp:n/a
1251 : 437 13471580ms.2 +-1 pid:4 Answer 449 connected
  dur 00:00:00 tx:0/0 rx:0/0
  IP 172.22.254.5:17036 SRTP: off rtt:0ms pl:0/0ms lost:0/0/0 delay:0/0/0ms g729r8 TextRelay: off
  media inactive detected:n media contrl rcvd:n/a timestamp:n/a
  long duration call detected:n long duration call duration:n/a timestamp:n/a
125E : 486 13638360ms.1 +-1 pid:10 Answer 022224919 connected
  dur 00:00:00 tx:0/0 rx:0/0
  IP 172.22.254.5:19198 SRTP: off rtt:0ms pl:0/0ms lost:0/0/0 delay:0/0/0ms g729r8 TextRelay: off
  media inactive detected:n media contrl rcvd:n/a timestamp:n/a
  long duration call detected:n long duration call duration:n/a timestamp:n/a
1283 : 625 13808100ms.2 +-1 pid:4 Answer 449 connected
  dur 00:00:00 tx:0/0 rx:0/0
  IP 172.22.254.5:16412 SRTP: off rtt:0ms pl:0/0ms lost:0/0/0 delay:0/0/0ms g729r8 TextRelay: off
  media inactive detected:n media contrl rcvd:n/a timestamp:n/a
  long duration call detected:n long duration call duration:n/a timestamp:n/a
1294 : 694 13953010ms.1 +-1 pid:5 Answer 560 connected
  dur 00:00:00 tx:0/0 rx:0/0
  IP 172.22.254.5:18208 SRTP: off rtt:0ms pl:0/0ms lost:0/0/0 delay:0/0/0ms g729r8 TextRelay: off
  media inactive detected:n media contrl rcvd:n/a timestamp:n/a
  long duration call detected:n long duration call duration:n/a timestamp:n/a

------------------------------------------------------------------------------------------------------------------------------------------------

CME shows 111 call-legs, but actually no active calls are at this moment.

Please help solve the problem.

Thanks a lot.

I have this problem too.
0 votes
Correct Answer by Steven Holl about 3 years 6 months ago

You can clear calls with:

clear call voice causecode 41 id

For example, that first call leg has the call ID of 11ED.

clear call voice causecode 41 id 11ED

Note that if those legs are stuck due to a call loop/high CPU, the state machine may be out of sync for those calls, so this command may not actually clear the call.  I actually anticpate this to be the case, given how you were previously configured.  If this is the case, and 'clear call' doesn't work, then the only recourse at this point is to reload the router.

  • 1
  • 2
  • 3
  • 4
  • 5
Average Rating: 4.3 (5 ratings)
Felipe Garrido Tue, 10/12/2010 - 06:55

Can you provide the current running configuration? Also, what is the exact version of IOS?

-Felipe

eugen.bitca Tue, 10/12/2010 - 07:17

Hello Felipe,

IOS Version: c2800nm-advipservicesk9-mz.124-20.T.bin

Voice part of running-config, not all 'dial-peer voice' are listed.

!
isdn switch-type primary-net5
!
!
voice call carrier capacity active
voice rtp send-recv
!
voice service pots
!
voice service voip
allow-connections h323 to h323
redirect ip2ip
!
!
voice iec syslog
voice cause-code
error-category 128 q850-cause 27
!
voice hunt-group 10 parallel
final 488
list 8201,8202,8203
timeout 20
pilot 000
!
!
voice statistics type iec
voice statistics time-range since-reset
!
voice translation-rule 467
rule 1 /^467$/ /812467/
rule 2 /^489$/ /812489/
rule 3 /^456$/ /812456/
rule 4 /^9001$/ /812555/
rule 5 /^9002$/ /812555/
rule 6 /^9003$/ /812555/
rule 7 /^8201$/ /812000/
rule 8 /^8202$/ /812000/
rule 9 /^8203$/ /812000/
rule 10 /^496$/ /812496/
rule 11 /^371$/ /812371/
rule 12 /^499$/ /812499/
!
!
voice translation-profile mine_out
translate calling 467
!
!
voice-card 0
no dspfarm
!
!
controller E1 0/1/0
pri-group timeslots 1-31
!
!
interface Loopback0
ip address 172.22.254.5 255.255.255.255
h323-gateway voip interface
h323-gateway voip bind srcaddr 172.22.254.5
!
!
interface Serial0/1/0:15
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn protocol-emulate network
isdn incoming-voice voice
isdn send-alerting
isdn negotiate-bchan resend-setup
isdn sending-complete
no cdp enable
!
!        
voice-port 0/1/0:15
bearer-cap Speech
!        
!        
dial-peer voice 2 pots
translation-profile outgoing mine_out
destination-pattern 9.T
direct-inward-dial
port 0/1/0:15
forward-digits all
!        
!        
dial-peer voice 3120 pots
incoming called-number 312
direct-inward-dial
port 0/1/0:15
forward-digits all
!        
dial-peer voice 3130 pots
incoming called-number 313
direct-inward-dial
port 0/1/0:15
forward-digits all
!        
dial-peer voice 311 voip
destination-pattern 311
session target ipv4:10.44.128.1
!        
dial-peer voice 312 voip
destination-pattern 312
session target ipv4:10.44.128.1
!       
!
dial-peer voice 10 voip
destination-pattern 0..
session target ipv4:172.22.254.5
!
dial-peer voice 300 voip
destination-pattern 3..
session target ipv4:172.22.254.5
!
dial-peer voice 990 voip
destination-pattern 990.
session target ipv4:172.22.254.5
!
dial-peer voice 9911 voip
destination-pattern 9911
session target ipv4:172.22.254.5
!
dial-peer voice 9112 voip
destination-pattern 9112
session target ipv4:172.22.254.5
!
dial-peer voice 9079 voip
destination-pattern 9079[0-9].....
session target ipv4:172.22.254.5
!
telephony-service
load 7911 term11.default.loads
load 7960-7940 P00308000500
max-ephones 30
max-dn 30
ip source-address 172.22.254.5 port 2000
auto assign 100 to 140
no service local-directory
system message Cisco
url directories http://172.22.7.101/syslog/xmldirectory.xml
url services http://172.22.7.101/syslog/xmlservices.xml
cnf-file perphone
user-locale 4 RU
network-locale 4 RU
time-format 24
max-conferences 8 gain -6
call-forward pattern .T
moh music-on-hold.au
dn-webedit
time-webedit
transfer-system full-blind
transfer-pattern .T
secondary-dialtone 9
night-service day Mon 12:05 12:20
create cnf-files version-stamp 7960 Jul 16 2010 09:54:29
!

dksingh Tue, 10/12/2010 - 09:24

Those seem to be all 0 duration calls. You can try following command to remove them

if you don't want to reload to clear them...

Also notice following dialpeers pointed to the GW itself...not sure why ?

Remove or shut these down to prevent a call loop.

dial-peer voice 10 voip
dial-peer voice 300 voip
dial-peer voice 990 voip
dial-peer voice 9911 voip
dial-peer voice 9112 voip
dial-peer voice 9079 voip

voice service voip
  allow-connections h323 to h323 <--- remove this if this GW is not set up as a CUBE/IPIPGW

interface Loopback0
   h323-gateway voip interface  <--- remove this

eugen.bitca Wed, 10/13/2010 - 01:01

Hello Dilip,

I made the changes you indicated., dialpeers pointed to the GW itself(old dial-peers)...incorrect IP address.

How to clear active voice calls without reloading the router?

Correct Answer
Steven Holl Wed, 10/13/2010 - 06:32

You can clear calls with:

clear call voice causecode 41 id

For example, that first call leg has the call ID of 11ED.

clear call voice causecode 41 id 11ED

Note that if those legs are stuck due to a call loop/high CPU, the state machine may be out of sync for those calls, so this command may not actually clear the call.  I actually anticpate this to be the case, given how you were previously configured.  If this is the case, and 'clear call' doesn't work, then the only recourse at this point is to reload the router.

dksingh Wed, 10/13/2010 - 07:15

Oops...seems I forgot to mention the CLI in my original reply...

Try following...if it does not work, which is very possible, u would

need to reload the box to clear these call legs.....

2851-1#clear call voice causecode  127 ?
  called-number   clear only call with specific called number pattern
  calling-number  clear only call with specific calling number pattern
  id              clear only call with specific id
  long-dur-call   clear only call with long-duration being detected and notified
  media-inactive  clear only call with media inactive being detected and notified

etmarcof Tue, 12/14/2010 - 07:18

Hi,

Have you manage to solve your problem?

I'm having similar problem with calls stucked and then i have to shut /no shut of interface serial 0/1/0:15 to clean these calls.

The problem is that  calls stucked continues to appear. how can i troubleshoot that?

Thanks.

Best Regards

Steven Holl Tue, 12/14/2010 - 07:31

etmarcof wrote:

Hi,

Have you manage to solve your problem?

I'm having similar problem with calls stucked and then i have to shut /no shut of interface serial 0/1/0:15 to clean these calls.

The problem is that  calls stucked continues to appear. how can i troubleshoot that?

Thanks.

Best Regards

Check for potential call loops in your dialplan, and look at 'sh proc cpu his' to see if you've spiked CPU to 100% anytime around when the call got hung.  Occasionally a hung call is a result of a bug, but 95% of the time it is a result of high CPU on the router and the common reason for this is a misconfiguration in the dialplan that causes an infinite call loop.

etmarcof Tue, 12/14/2010 - 07:59

Hi,

Thanks i will check that.

This E1 connection is from router to a Siemens Pbx. Sometimes Cisco ip phone users complains that they call to Siemens phones and they ear busy tone (but in reality siemens phone are free) so i have added isdn negotiate-bchan resend-setup to configuration and it seems it solved but could that bring these problems of call stucked?

Thanks

Best Regards

Steven Holl Tue, 12/14/2010 - 08:01

etmarcof wrote:

Hi,

Thanks i will check that.

This E1 connection is from router to a Siemens Pbx. Sometimes Cisco ip phone users complains that they call to Siemens phones and they ear busy tone (but in reality siemens phone are free) so i have added isdn negotiate-bchan resend-setup to configuration and it seems it solved but could that bring these problems of call stucked?

Thanks

Best Regards

You would need to run debugs to confirm how IOS is behaving during that scenario.  voip ccapi inout and isdn q931 should suffice.

Paolo Bevilacqua Thu, 12/16/2010 - 08:36

In two cases on this thread I see that perfectly correct and useful replies have been low rated.

I have then re-rated to fairly compensate.

I think the person that is leaving these inappropritae ratings should review his/her usage of the system, otherwise it is normal that top contributors will review their desire to help for free here.

Actions

Login or Register to take actions

This Discussion

Posted October 11, 2010 at 1:38 AM
Stats:
Replies:13 Avg. Rating:4.33333
Views:1088 Votes:0
Shares:0
Tags: No tags.

Discussions Leaderboard

Rank Username Points
1 21,016
2 15,047
3 10,314
4 7,999
5 4,856
Rank Username Points
164
95
75
61
55