Preview Tool

Cisco Bug: CSCuq17104 - CUBE disconnecting a call after call transfer due to Hold timer

Last Modified

Nov 27, 2020

Products (1)

  • Cisco 2600 Series Multiservice Platforms

Known Affected Releases


Description (partial)

Call drops seen on cube post a  call transfer for a PSTN caller after the call is active for 60 mins.

8471445: *Jul 18 14:23:38.957: //84710/BBEDDF000000/SIP/Info/act_onhold_timeout: Hold Timer Expired, tearing down call
8471446: *Jul 18 14:23:38.957: //84710/BBEDDF000000/SIP/Info/ccsip_set_release_source_for_peer: ownCallId[84710], src[6]

Configuration :-
timers hold 60

Call flow :
ip phone 1 -- sccp --- leaf cucm -- ict trunk -- cucm sme 9.1 -- sip -- cube 3945e -- sip -- acme sbc 
ip phone 2 --  sccp      

The operation of the user is only  the following :- 
-	Call is setup
-	User transfers the call to another internal CUCM IP Phone

Related Community Discussions

Max Call Duration
Hello Pros, I need to run a test call which needs to least at least 8 hours.  It looks like my SBC is terminâting the call after about 60 minutes by seding a Bye message. In CUCM the Max Call Duration is set to 720 mins but the call gets disconnected after 60 mins. This is definitely comming from my Voice Gateway due to a RTP traffic inactivity or a call monitoring duration but I don't seem to be able to find the right command to make the call last a minimum of 8 hours. Any help would be greately ...
Latest activity: Jan 08, 2018
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.