×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

how to clear the hung calls in CUBE?

Unanswered Question
Feb 12th, 2014
User Badges:
  • Gold, 750 points or more
  • Community Spotlight Award,

    Mobile User, October 2015

I'm installing a new CUBE as SIP-SIP gateway in Cisco 2921, IOS: 15.1(4)M3. When i tried few test calls, I saw couple of hung calls in it.


I tried clearing them manually with the below command but it didn't help.


clear call voice causecode identifier{id identifier | media-inactive | calling-number number | called-number number}


>> https://supportforums.cisco.com/docs/DOC-34379


The call legs are still in connecting status.


2    : 2152 13:36:28.319 CET Tue Feb 11 2014.1 +-1 pid:200 Answer 222022029 connecting

dur 00:00:00 tx:0/0 rx:0/0

IP X.X.X.97:24578 SRTP: off rtt:0ms pl:0/0ms lost:0/0/0 delay:0/0/0ms 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


2    : 2157 13:38:54.589 CET Tue Feb 11 2014.1 +-1 pid:200 Answer 222022029 connecting

dur 00:00:00 tx:0/0 rx:0/0

IP X.X.X.97:24582 SRTP: off rtt:0ms pl:0/0ms lost:0/0/0 delay:0/0/0ms 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


Also, I tried enabling media inactivity timer but it would clear only the calls in 'Connected' status If I understand correctly.


how to clear those hung calls? and what could be the cause of it?


Any help would be much appreciated.


Thanks in advance

Suresh

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Kevin Monteiro Wed, 02/12/2014 - 01:11
User Badges:
  • Silver, 250 points or more

Hi Suresh,


Step no 6 in the following link:

The Media Inactivity Timer enables the Active/Standby router pair to monitor and disconnect calls if no Real-Time Protocol (RTP) packets are received within a configurable time period.

When RTP packets for a call are not received by the Active/Standby router, the SIP Media Inactivity Timer releases the session. This is used to guard against any hung sessions that might have resulted from the failover in the event that a normal call disconnect does not clear the call.

The same duration for the Media Inactivity Timer should be configured on both routers. The default value is 28 seconds. This timer is configured as follows:

ip rtcp report interval 3000 gateway media-inactivity-criteria all timer receive-rtp 86400 timer receive-rtcp 5




http://www.cisco.com/c/en/us/support/docs/voice-unified-communications/u...

Kindly rate the post accordingly.

Sent from Cisco Technical Support Android App

Suresh Subramanian Wed, 02/12/2014 - 01:49
User Badges:
  • Gold, 750 points or more
  • Community Spotlight Award,

    Mobile User, October 2015

Hi Kevin,


Yes I did try that feature but no luck, the calls are not yet cleared. but I enabled that feature after I saw the call hanging. and when I executed 'show call active voice brief' I still see 'media inactivity detected=No'.

Ayodeji Okanlawon Wed, 02/12/2014 - 01:51
User Badges:
  • Super Bronze, 10000 points or more
  • Cisco Designated VIP,

    2017 IP Telephony

Suresh have you tried this:

ip rtcp report interval 5000

gateway

timer media-inactive 5

The challenge you may face is that the media inactivity was not configured before this call started, hence it cant activate the time for this particular call...

Give it a go, lets know if it works. Even if it doesnt I suggest you enable this on your CUBE going forward, so you dont haver hung calls in the future

example: You can use the debug ccsip events to see the media inactivity timer kicking in for a call...

Router# debug ccsip events





00:04:29: sipSPICreateAndStartRtpTimer: Valid RTP/RTCP session found and CLI ena 


bled to create and start the inactivity timer 


00:04:29: sipSPICreateAndStartRtpTimer:Media Inactivity timer created for call. 


Mfactor(from CLI): 5 RTCP bandwidth: 500 


RTCP Interval(in ms): 5000 


Normalized RTCP interval (in ms):25000 



Please rate all useful posts

"The essence of christianity is not the enthronement but the obliteration of self --William Barclay"

Suresh Subramanian Wed, 02/12/2014 - 02:12
User Badges:
  • Gold, 750 points or more
  • Community Spotlight Award,

    Mobile User, October 2015

Hello Deji,

As I enabled the inactivity timer after the calls, it seems they are not detecting and clearing those hung calls.


I tried the below


      ip rtcp report interval 9000

      gateway

      media-inactivity-criteria rtcp

      timer receive-rtcp 5



Also, I'm just wondering what could be the cause for these sessions hanging? could it be the IOS or configurations or Provider side? any idea?


Please rate all the useful posts

Ayodeji Okanlawon Wed, 02/12/2014 - 02:17
User Badges:
  • Super Bronze, 10000 points or more
  • Cisco Designated VIP,

    2017 IP Telephony

I have seen them on our CUBE(s) too and I honestly dont know why. It may be IOS related. This is why its good prractice to have media inactivity configured. Its not something to worry about though.



Please rate all useful posts

"The essence of christianity is not the enthronement but the obliteration of self --William Barclay"

Suresh Subramanian Wed, 02/12/2014 - 10:07
User Badges:
  • Gold, 750 points or more
  • Community Spotlight Award,

    Mobile User, October 2015

one of my friends from tac said, only reboot would clear those calls. did the reboot and the hung calls were cleared.


thanks everyone for your suggestions.



Please rate all the useful posts

Kevin Monteiro Wed, 02/12/2014 - 11:14
User Badges:
  • Silver, 250 points or more

Suresh,


The basic thing would be resseting the TRUNK or the  "clear call voice causecode 17 called-number 2126315001"

. This to be honest looks like a IOS based issue.


Could you let us know whats the ios your running?


Regards,

Kevin

Suresh Subramanian Wed, 02/12/2014 - 11:33
User Badges:
  • Gold, 750 points or more
  • Community Spotlight Award,

    Mobile User, October 2015

Kevin, it's Cisco 2921, IOS: 15.1(4)M3

Actions

This Discussion