VCS SIP Call Ends in 16 minutes due to timeout TTL issue

John Faltys · ‎07-09-2013

While in a call, Example 1 below, the registration timed out and was removed by the VCS. Once that happened, the SIP to SIP call ended abruptly at 16 minutes.

2013-07-08T19:14:34-07:00 tvcs: Event="Call Disconnected" Service="SIP" Src-ip="xxx.yyy.149.50" Src-port="49233" Src-alias-type="SIP" Src-alias="sip:UserA.movi@acme.com" Dst-alias-type="SIP" Dst-alias="sip:EP1.exam1@acme.com" Call-serial-number="0f203e62-e83b-11e2-b4c7-0010f3207b24" Tag="0f204006-e83b-11e2-9697-0010f3207b24" Protocol="TLS" Level="1" UTCTime="2013-07-09 02:14:34,096"

2013-07-08T19:14:11-07:00 tvcs: Event="Registration Removed" Reason="Endpoint unresponsive" Service="SIP" Src-ip="xxx.yyy.236.41" Src-port="49152" Protocol="TLS" AOR="EP1.exam1@acme.com" Contact="sip:EP1.exam1@172.23.0.2:5061;transport\=tls" Level="1" UTCTime="2013-07-09 02:14:11,475"

2013-07-08T19:13:51-07:00 tvcs: Event="Registration Removed" Reason="Endpoint unresponsive" Service="H323" Dst-ip="xxx.yyy.236.41" Dst-port="45502" Dst-alias-type="H323" Dst-alias="EP1.exam1@med-rt.com" Dst-alias-type="E164" Dst-alias="9991233263" Detail="Registration was not refreshed in time and endpoint failed to respond to IRQ" Protocol="UDP" Level="1" UTCTime="2013-07-09 02:13:51,475"

The message only happens when specific users (User A in this case) are in a SIP to SIP call with EP1.

User A: Jabber 4.5 from location A

User B: Jabber 4.5 from location B

EP1: Tandberg Edge 95 9.3.1

Example1: User A on Jabber calling EP1 using SIP URI. Call continues for exactly 16 minutes and then disconnects with the error

"Registration was not refreshed in time and endpoint failed to respond to IRQ"

Obviously the endpoint is not responding to the VCS or the response is getting blocked.

After this error happens, authentication gets rejected for "Received from unauthenticated source" for 5 times before it requests new registration and is accepted.

Example2: User B on Jabber calling EP1 using SIP URI. Call continues eternally with no errors in the log.

So it only seems this endpoint is ignoring the VCS requests with specific calls.

Example3: User A on Jabber calling EP1 using H323 ID. Call continues eternally without any error.

I have the log, but do not want to post in public.

MK: I apologize for not making this a new message originally.

dferrie · ‎07-09-2013

I had the same issue a while back. sounds like you are hitting the same bug. What version of VCS following bug was fixed in 7.2.2

CSCub76176

Symptoms

: Calls from unregistered endpoints, behind a NAT, into a VCS Expressway may

be dropped at 15 minutes.

Conditions

:

SIP Session Refresh when set to 1800 seconds or

greater (where it will refresh

after approximately 900 seconds) will fail if the unregistered endpoint is behind a NAT, and

so the VCS Expressway cannot connect back to it in order to refresh the session, after the

initial TCP session has been torn down.

Workaround

:

Set the SIP Session Refresh (VCS configuration > Protocols > SIP >

Configuration) to be less than 1800 seconds, for example 1200 seconds (so it will refresh

after approximately 600 seconds).

John Faltys · ‎07-11-2013

Thank you for the reply.

I upgraded the VCS to 7.2.2. The problem still exists.

I also tested by changing the SIP Session Refresh to 1200. What happened is instead of the call disconnecting at 16 minutes, it disconnects at 11 minutes.

What is odd, is the registration is removed by the VCS only when the specific EP is in a call with a specific Jabber user.

This same Jabber user can be in a call with the same EP using interop (SIP to H323) and the VCS does not remove the registration.

BTW: Both the EP and the Jabber user are VCSE registered.