Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

UC500 calls drop after 60 minutes

Hello... is there a default timer on the UC520?

Conf calls users are complaining that the calls drop after 60 minutes. The provider checked their settings and suggests the problem is on the UC520.

Thanks. Vincent

10 REPLIES
New Member

Re: UC500 calls drop after 60 minutes

What version of IOS is the customer running on the UC520? I do know that there are bugs in the IOS versions in the 4.2.0, 7.0.0 (early adopter), 7.0.1 (early adopter), 7.0.2, 7.0.3, 7.1.0 (early adopter), and 7.1.1 (early adopter). I have not tested the 7.1.3 release, and I am not aware of the bugs in that release. The Cisco TAC will not support any outdated early adopter releases. In addition, UC520 units that have been upgraded from a 4.2.x to a 7.x release might be misbehaving because it is incorrectly configured. If you have upgraded your UC520 unit from a 4.2.x release to a 7.x release, please send me the configuration. I will look over it to check for configuration errors that might cause problems in the 7.x releases.

Here are the 9 known officially supported IOS versions on the UC520:

  • 12.4(11)XW (included in the 4.2.0 release)
  • 12.4(11)XW3 (included in the 4.2.3 release)
  • 12.4(11)XW4 (included in the 4.2.4 release)
  • 12.4(11)XW5 (included in the 4.2.5 release)
  • 12.4(11)XW6 (included in the 4.2.6 release)
  • 12.4(11)XW7 (included in the 4.2.7 release)
  • 12.4(11)XW8 (included in the 4.2.8 release)
  • 12.4(11)XW9 (included in the 4.2.9 release)
  • 12.4(20)T2 (included in the 7.0.2 and 7.0.3 releases)

Here are the IOS versions found in UC520 early adopter software packs:

  • 12.4(20)T (in the 7.0.0 release)
  • 12.4(20)T1 (in the 7.0.1 release)
  • 12.4(22)YB (in the 7.1.0 and 7.1.1a early adopter releases)
  • 12.4(22)YB1 (in the 7.1.1 early adopter release)
  • 12.4(22)YB4 (in the 7.1.3 early adopter release, latest early adopter release available)

Here is the only known officially supported IOS release on the UC540 (a new product):

  • 12.4(24)SB
New Member

Re: UC500 calls drop after 60 minutes

Hi John... it's running IOS 12.4(24)T. Thanks.

New Member

Re: UC500 calls drop after 60 minutes

Hello....

I've just noticed the ios is  12.4(24)T with Cisco Unity Express 3.2.1. Does this create a discrepancy? Can I upgrade CUE to the latest version or will that create complications?

Thanks.

New Member

Re: UC500 calls drop after 60 minutes

Yes, you can upgrade from CUE 3.2.1 to 7.0.3. However, you should use the CUE 7.0.3 release included in the 7.0.3, 7.0.4, or 7.1.3 software pack.

Here are the IOS and CUE versions in the 7.0.3 software pack for UC520:

IOS 12.4(20)T2

CUE 7.0.3

Here are the IOS and CUE versions in the 7.0.4 software pack for UC520:

IOS 12.4(20)T4

CUE 7.0.3

Here are the IOS and CUE versions in the 7.1.3 software pack (early adopter) for UC520:

IOS 12.4(22)YB4

CUE 7.0.3

New Member

Re: UC500 calls drop after 60 minutes

John... thank you. I found this link also and am going through the info.

https://supportforums.cisco.com/message/3088430#3088430

Re: UC500 calls drop after 60 minutes

What kind of calls are there?  SIP, PRI, etc.  What kind of conferencing are you using?

New Member

Re: UC500 calls drop after 60 minutes

Sorry for the delayed response. The calls are SIP. Thanks.

ps.. they're dialing an external conference bridge. Thanks.

Bronze

Re: UC500 calls drop after 60 minutes

Can you gather "deb ccsip message" for one such call?

My guess is there is a SIP Session Timer that expires and call drops

New Member

Re: UC500 calls drop after 60 minutes

Sorry.. I'm not getting prompt enough cooperation and responses from the users to work on this issue. I'll have to put it on hold until they get back to me. Thanks for the input.

Re: UC500 calls drop after 60 minutes

Hi Everyone,

I set up a SIP call to a public station and let it stay up for an hour.  I made three calls (one at a time) over the last 3 hours.

I did look suspiciously at the SIP TLS 60 minute timer, but I am not using TLS.

Nonetheless, I did see the following messages at exactly 1 hour.  And the calls stayed up each time.

(My UC is behind an SA540, hence the .104 address for the UC540).

015397: Oct 13 18:34:19.076: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
UPDATE sip:6783979422@192.168.75.104:5060 SIP/2.0
Via: SIP/2.0/UDP 72.16.xx.xx:5060;branch=z9hG4bKkaddpg1018ahces481g0sm7pu68r3.1
From: <>1919392xxxx@sipconnect-fca.atl0.cbeyond.net>;tag=172793151-1255455267190
To: "Seven Eightyfive" <>678397xxxx@sipconnect-fca.atl0.cbeyond.net>;tag=23D9C6FC-247A
Call-ID: 791C865B-B75511DE-82E7DB4D-B721A7D0@sipconnect-fca.atl0.cbeyond.net
CSeq: 662406134 UPDATE
Contact: <1919392XXXX>
Max-Forwards: 9
Content-Length: 0


015398: Oct 13 18:34:19.076: //7786/77D9A37782E2/SIP/State/sipSPIChangeState: 0x87ACCA68 : State change from (STATE_ACTIVE, SUBSTATE_NONE)  to (STATE_MIDCALL_LOCAL_RESP_PENDING, SUBSTATE_NONE)
015399: Oct 13 18:34:19.076: //7786/77D9A37782E2/SIP/State/sipSPIChangeState: 0x87ACCA68 : State change from (STATE_MIDCALL_LOCAL_RESP_PENDING, SUBSTATE_NONE)  to (STATE_ACTIVE, SUBSTATE_NONE)
015400: Oct 13 18:34:19.076: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Date: Tue, 13 Oct 2009 18:34:19 GMT
From: <>1919392xxxx@sipconnect-fca.atl0.cbeyond.net>;tag=172793151-1255455267190
Allow-Events: telephone-event
Content-Length: 0
To: "Seven Eightyfive" <>6783979422@sipconnect-fca.atl0.cbeyond.net>;tag=23D9C6FC-247A
Contact: <678397XXXX>
Call-ID: 791C865B-B75511DE-82E7DB4D-B721A7D0@sipconnect-fca.atl0.cbeyond.net
Via: SIP/2.0/UDP 72.16.223.xx:5060;branch=z9hG4bKkaddpg1018ahces481g0sm7pu68r3.1
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 662406134 UPDATE

3345
Views
0
Helpful
10
Replies
CreatePlease to create content