cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
525
Views
0
Helpful
1
Replies

Calls are getting Stuck on DNs - CME Issue

Gokul Dev
Level 1
Level 1

Hi there,

Good Day to you..

I am facing a strange issue..I am using Cisco 2851 CME with 7.1 version.

The setup is  running for 1 year now.. For the last 1-2 months, the calls are getting  stuck in the router.. The exact issue is as follows..The calls are  transferred from an extension and on the router the call is still  active, so that the user cannot receive any more calls.. The case is  open with Cisco for 2 months without any solutions. They asked to do No call-park sys app and update the IOS. Both didnt help..

Calls are stuck  in particular dn. The below mentioned calls were disconnected by the  user long time back and are still showing in the router  as active. when  we check with the "show call active voice brief" command.

The only solution we found that to restart the router.

The extension  198 is the number in which the IVR is configured. Also we had found that  the calls are getting stuck in some of the other dn's which are doing  the call transfers frequently. We have upgraded the IOS to the latest  version and there is no luck.

The issue is mainly hapening on reception DN, Customer Service, etc. who always tranfer the calls.

Below is one of the log..


Telephony call-legs: 4
SIP call-legs: 2
H323 call-legs: 0
Call agent controlled call-legs: 0
SCCP call-legs: 0
Multicast call-legs: 0
Total call-legs: 6
120D : 6121 65757510ms.1 +50 pid:123 Answer 39116236 active
dur 03:41:21 tx:2883/484344 rx:388/62080
Tele 0/0/0:15 (6121) [0/0/0.3] tx:13280420/13226430/0ms g711ulaw noise:-84 acom
:45  i/0:-27/-59 dBm

120D : 6122 65757520ms.1 +30 pid:40005 Originate 198 active
dur 03:41:21 tx:388/62080 rx:2883/461280
IP 10.10.10.3:28812 SRTP: off rtt:0ms pl:57660/150ms lost:0/1/0 delay:55/55/75m
s g711ulaw 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

1210 : 6146 65920180ms.1 +40 pid:123 Answer 39116236 active
dur 03:38:38 tx:2231/374808 rx:92/14720
Tele 0/0/0:15 (6146) [0/0/0.6] tx:13117760/13075910/0ms g711ulaw noise:-84 acom
:45  i/0:-26/-61 dBm

1210 : 6147 65920190ms.1 +30 pid:40005 Originate 198 active
dur 03:38:38 tx:92/14720 rx:2231/356960
IP 10.10.10.3:28824 SRTP: off rtt:0ms pl:44620/70ms lost:0/1/0 delay:55/55/75ms
g711ulaw 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


1 Reply 1

paolo bevilacqua
Hall of Fame
Hall of Fame

Sorry, but nobody except Cisco can help with your problem.

To try have your problem solved you must:

  1. formally escalate TAC case to P2, and request escalation
  2. formally ask TAC escalation team to re-produce in house
  3. once is reproduce, a bug can be filed. You will be given the bug ID, and your P2 case to be linked to ID.
  4. then hopefully Cisco engineering will be able to identify and solve the problem in a reasonable timeframe.

The most importat thing is that you are adamant in keeping P2 and give TAC all the information requested.

You must also make sure you case status is always cisco pending, providinig the infromation requested or asking escalation.