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

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Jabber Video disconnects from our endpoints after approximately 30 minutes

We are currently having a issue with jabber video where the call disconnects from our endpoints after about 30 minutes.  Our colleagues are using jabber video version 4.6 and our endpoints are running TC6 and TC7.  These calls transverse our VCS expressway.  What we are seeing is that as the call progresses other IP addresses from our network  become a part of the call and send invites to the VCS.

VCS Control log. We receive an Invite from VCS-E and respond with a 100Trying.

2014-04-22T12:52:32-04:00 ny1745-vcsint-2 tvcs: UTCTime="2014-04-22 16:52:32,091" Module="network.sip" Level="INFO":  Src-ip=10.X.X.X.X  Src-port="7001"   Detail="Receive Request Method=INVITE, Request-URI=sip:824485@xxxxxxxxxxxx.com;gr=urn:uuid:3950ef26-a187-5d8b-935f-ad00d63aae19, Call-ID=bfd7b9bb84fd116acfd11dd7d7b61e86@199.19.190.26"

2014-04-22T12:52:32-04:00 ny1745-vcsint-2 tvcs: UTCTime="2014-04-22 16:52:32,092" Module="network.sip" Level="DEBUG":  Src-ip=10.X.X.X.X  Src-port="7001"

|INVITE sip:824485@xxxxxxxxxxxx.com;gr=urn:uuid:3950ef26-a187-5d8b-935f-ad00d63aae19 SIP/2.0

Via: SIP/2.0/TLS 10.X.X.X.X:7001;egress-zone=TZtoVCSc;branch=z9hG4bKb5fe019435cce0ad459cdaa6d2df6b912417759.236b2bfbb37d37994b50e5d24ad7d1a7;proxy-call-id=516732f8-ca3a-11e3-9046-0010f31ecd28;received=10.X.X.X.X ;rport=7001

Via: SIP/2.0/TCP 199.19.190.26:5060;branch=z9hG4bK+e2f84a0357e9c3bb37660e8df95c0e421+sip+1+a668fe98;received=199.19.190.26;ingress-zone=DefaultZone

Call-ID: bfd7b9bb84fd116acfd11dd7d7b61e86@199.19.190.26

From: "xxxxxxx" <sip:xxxxxxx@jabber.com>;tag=199.19.190.26+1+ec1249fa+7ec39250

To: "1745 - Room 501" <sip:824485@xxxxxxxxxxxx.com>;tag=a498019ff5c257c3

Route: <sip:proxy-call-id=516b51f8-ca3a-11e3-b75f-0050568743b6@170.X.X.X.X:7690;transport=tls;lr>

Route: <sip:proxy-call-id=516b51f8-ca3a-11e3-b75f-0050568743b6@170.X.X.X.X:7690;transport=tls;lr>

Route: <sip:proxy-call-id=51760ed6-ca3a-11e3-affa-0010f31ecde8@10.X.X.X.X:51781;transport=tls;lr>

Route: <sip:proxy-call-id=51760ed6-ca3a-11e3-affa-0010f31ecde8@10.X.X.X.X:51781;transport=tls;lr>

Record-Route: <sip:proxy-call-id=516732f8-ca3a-11e3-9046-0010f31ecd28@10.X.X.X.X:7001;transport=tls;lr>

Record-Route: sip:proxy-call-id=516732f8-ca3a-11e3-9046-0010f31ecd28@170.X.X.X.X:5060;transport=tcp;lr

 

2014-04-22T12:52:32-04:00 ny1745-vcsint-2 tvcs: UTCTime="2014-04-22 16:52:32,095" Module="network.sip" Level="INFO":  Dst-ip=10.X.X.X.X  Dst-port="7001"   Detail="Sending Response Code=100, Method=INVITE, To=sip:824485@xxxxxxxxxxxx.com, Call-ID=bfd7b9bb84fd116acfd11dd7d7b61e86@199.19.190.26"

2014-04-22T12:52:32-04:00 ny1745-vcsint-2 tvcs: UTCTime="2014-04-22 16:52:32,095" Module="network.sip" Level="DEBUG":  Dst-ip=10.X.X.X.X  Dst-port="7001"

|SIP/2.0 100 Trying

Via: SIP/2.0/TLS 10.X.X.X.X:7001;egress-zone=TZtoVCSc;branch=z9hG4bKb5fe019435cce0ad459cdaa6d2df6b912417759.236b2bfbb37d37994b50e5d24ad7d1a7;proxy-call-id=516732f8-ca3a-11e3-9046-0010f31ecd28;received=10.X.X.X.X ;rport=7001;ingress-zone=TZtoVCSe

Via: SIP/2.0/TCP 199.19.190.26:5060;branch=z9hG4bK+e2f84a0357e9c3bb37660e8df95c0e421+sip+1+a668fe98;received=199.19.190.26;ingress-zone=DefaultZone

Call-ID: bfd7b9bb84fd116acfd11dd7d7b61e86@199.19.190.26

From: "xxxxxxx" <sip:xxxxxxx@jabber.com>;tag=199.19.190.26+1+ec1249fa+7ec39250

To: "1745 - Room 501" <sip:824485@xxxxxxxxxxxx.com>;tag=a498019ff5c257c3

Then we see how the TCP connection fails to IP 170.X.X.X.X, this IP was specified as a route in the previous Invite message.

 

2014-04-22T12:52:32-04:00 ny1745-vcsint-2 tvcs: UTCTime="2014-04-22 16:52:32,103" Module="network.tcp" Level="DEBUG":  Src-ip=10.X.X.X.X Src-port="25090" Dst-ip=170.X.X.X.X Dst-port="7690" Detail="TCP Connecting"

2014-04-22T12:52:32-04:00 ny1745-vcsint-2 tvcs: UTCTime="2014-04-22 16:52:32,104" Module="network.tcp" Level="ERROR":  Src-ip=10.X.X.X.X Src-port="25090" Dst-ip=170.X.X.X.X Dst-port="7690" Detail="TCP Connection Failed"

VCS-C sends a 408 Request Timeout to the VCS-E and the disconnection process starts.

 

2014-04-22T12:52:32-04:00 ny1745-vcsint-2 tvcs: UTCTime="2014-04-22 16:52:32,107" Module="network.sip" Level="DEBUG":  Dst-ip=10.X.X.X.X  Dst-port="7001"

|SIP/2.0 408 Request Timeout

Via: SIP/2.0/TLS 10.X.X.X.X:7001;egress-zone=TZtoVCSc;branch=z9hG4bKb5fe019435cce0ad459cdaa6d2df6b912417759.236b2bfbb37d37994b50e5d24ad7d1a7;proxy-call-id=516732f8-ca3a-11e3-9046-0010f31ecd28;received=10.X.X.X.X;rport=7001;ingress-zone=TZtoVCSe

Via: SIP/2.0/TCP 199.19.190.26:5060;branch=z9hG4bK+e2f84a0357e9c3bb37660e8df95c0e421+sip+1+a668fe98;received=199.19.190.26;ingress-zone=DefaultZone

Call-ID: bfd7b9bb84fd116acfd11dd7d7b61e86@199.19.190.26

From: "xxxxxxx" <sip:xxxxxxx@jabber.com>;tag=199.19.190.26+1+ec1249fa+7ec39250

To: "1745 - Room 501" <sip:824485@xxxxxxxxxxxx.com>;tag=a498019ff5c257c3

As we can see in the following message the IP 170.X.X.X.X is in the Invite that we received in the VCS-E.

2014-04-22T12:21:48-04:00 ny1745-vcsext tvcs: UTCTime="2014-04-22 16:21:48,743" Module="network.sip" Level="DEBUG":  Src-ip="199.19.190.28"  Src-port="62526"

|INVITE sip:824484@xxxxxxxxxxxx.com SIP/2.0

Via: SIP/2.0/TCP 199.19.190.28:5060;branch=z9hG4bK+0b6ef76e9c13eceb6171fa37264e0ab91+sip+1+a65e8936;received=199.19.190.28

Call-ID: f5d96ab95caaf5ae823c759216ce2bba@199.19.190.28

2014-04-22T12:52:32-04:00 ny1745-vcsext tvcs: UTCTime="2014-04-22 16:52:32,084" Module="network.sip" Level="DEBUG":  Src-ip="199.19.190.26"  Src-port="47730"

|INVITE sip:824485@xxxxxxxxxxxx.com;gr=urn:uuid:3950ef26-a187-5d8b-935f-ad00d63aae19 SIP/2.0

Via: SIP/2.0/TCP 199.19.190.26:5060;branch=z9hG4bK+e2f84a0357e9c3bb37660e8df95c0e421+sip+1+a668fe98;received=199.19.190.26

Call-ID: bfd7b9bb84fd116acfd11dd7d7b61e86@199.19.190.26

Contact: <sip:199.19.190.26:5060;transport=tcp>;sip.ice=TRUE

From: "xxxxxxx" <sip:xxxxxxx@jabber.com>;tag=199.19.190.26+1+ec1249fa+7ec39250

To: "1745 - Room 501" <sip:824485@xxxxxxxxxxxx.com>;tag=a498019ff5c257c3

Route: <sip:proxy-call-id=516732f8-ca3a-11e3-9046-0010f31ecd28@170.X.X.X.X:5060;transport=tcp;lr>

Route: <sip:proxy-call-id=516732f8-ca3a-11e3-9046-0010f31ecd28@10.X.X.X.X:7001;transport=tls;lr>

Route: <sip:proxy-call-id=516b51f8-ca3a-11e3-b75f-0050568743b6@170.X.X.X.X:7690;transport=tls;lr>

Route: <sip:proxy-call-id=516b51f8-ca3a-11e3-b75f-0050568743b6@170.X.X.X.X:7690;transport=tls;lr>

Route: <sip:proxy-call-id=51760ed6-ca3a-11e3-affa-0010f31ecde8@10.X.X.X.X:51781;transport=tls;lr>

Route: <sip:proxy-call-id=51760ed6-ca3a-11e3-affa-0010f31ecde8@10.X.X.X.X:51781;transport=tls;lr>

Please take a look at the logs to see if you can find a reason why random IP addresses become and  part of the call  route. TAC says that this route is added before reaching the VCS expressway and only in the refresher invite.  Why is  this happening  when refresher invites are sent, and what will be a possible fix.

 

Thanks.

1 REPLY

You might be better off

You might be better off posting this in the JabberVideo support forum since it involves the "free" jabber.com version which is hosted and provisioned by Cisco, unless this happens with on-prem (enterprise) version as well?

By the way, current jabber.com version is 4.8.8.

/jens

Please rate replies and mark question(s) as "answered" if applicable.

Please rate replies and mark question(s) as "answered" if applicable.
240
Views
0
Helpful
1
Replies
CreatePlease login to create content