[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Linphone-developers] NAT broken-Interop Issue with Cisco MSE 8710 T

From: Kendall Williams
Subject: Re: [Linphone-developers] NAT broken-Interop Issue with Cisco MSE 8710 Telepresence bridges Need Assistance
Date: Thu, 23 Oct 2014 09:11:20 -0700


Yes I have debug files from my VPN connected and Internet connected laptops.  See attached.  Please let me know if you require additional information.


From: Jehan Monnier <address@hidden>
To: Kendall Williams <address@hidden>
Cc: address@hidden
Sent: Thursday, October 23, 2014 4:21 AM
Subject: Re: [Linphone-developers] NAT broken-Interop Issue with Cisco MSE 8710 Telepresence bridges Need Assistance


Do you have Linphone debug traces showing the issue ?


Le 22 oct. 2014 à 19:10, Kendall Williams <address@hidden> a écrit :

I have not received a response yet from the the Developer Community yet.

Can someone please provide a response or assistance?

From: Kendall Williams <address@hidden>
To: "address@hidden" <address@hidden>
Sent: Monday, September 29, 2014 12:47 PM
Subject: NAT broken

Linphone developers and user community,

I am using Linphone to connect to a Open Video Communication/Telepresence (OVC/TPS) bridge from Cisco.  This bridge houseTPS  MSE 8710 blade v3.x.  In this environment I want to make sure that we are able to interop with various SIP clients.  I downloaded Linphone v3.7.0 and configured the client to use TCP/5060 and NAT.  The client is able to connect to the bridge for approximately 50 secs. and then disconnects.  Using UDP/5060 and a STUN server is not an option. Adjusting NAT is also not an option.  I am configured as TCP 5060, behind a NAT firewall.

The bridges sit behind Cisco Video Communication Servers (X7.2.3) which face the internet and use traversal licenses. Linphone had worked prior to the blades being upgraded to v3.x but has since stopped working.  NAT is definitely issue in this case. According to Cisco, when the TPS re-invites for DTLS negotiation (added in 3.x or higher of TPS) this is going to the wrong address because LinPhone is populating incorrectly.  In older versions of TPS we had  a bug where the Contact Header was not properly updating per RFC spec.  Cisco fixed that bug and now Linphone no longer works with OVC correctly.

I am being directed to Linphone for a fix or resolution to this issue.  Is there something I can do here get the Linphone functioning once again?


Linphone-developers mailing list

Attachment: connect_via_vpn.txt
Description: Text document

Attachment: connect_via_Internet.txt
Description: Text document

reply via email to

[Prev in Thread] Current Thread [Next in Thread]