linphone-users
[Top][All Lists]
Advanced

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

[Linphone-users] default identity problems


From: Carl Heyendal
Subject: [Linphone-users] default identity problems
Date: Mon, 6 Oct 2014 21:00:56 +0000

Hi,

 

First post to this email group.

 

I’ve installed Linphone on Windows 7 and configured a new identity in Linphone separate from the default identity.

 

When I make a phone-to-phone SIP call (no Proxy) on the same subnet to the Linphone the call sets up correctly except for 2 things:

 

1.       The SDP sent by the Linphone tells the other end to stream its RTP packets to the default identity’s IP address (192.168.55.56) rather than to the new identity’s IP address  that I created.

2.       The Linphone doesn’t stream to the other end but rather it sends STUN request messages instead. I have configured “Direct connection to the Internet” under the ‘Network Settings’ tab. I’m not behind a firewall so this seemed to be the logical choice.

 

Appreciate anyone’s help.

 

 

Regards,

 

Carl

 

Carl Heyendal

Principal Software Development Telephony Engineer

Fortinet - The New Generation of Secure Gateways

326 Moodie Dr, Nepean, ON K2H 8G3
Office: +1 613.725.2980  x.149
Fax: +1 613.725.2898
Toll Free: +1 888.332.9322 x149

http://www.talkswitch.com/images/co_signatures/fortinetSignature.jpg

 



*** Please note that this message and any attachments may contain confidential and proprietary material and information and are intended only for the use of the intended recipient(s). If you are not the intended recipient, you are hereby notified that any review, use, disclosure, dissemination, distribution or copying of this message and any attachments is strictly prohibited. If you have received this email in error, please immediately notify the sender and destroy this e-mail and any attachments and all copies, whether electronic or printed. Please also note that any views, opinions, conclusions or commitments expressed in this message are those of the individual sender and do not necessarily reflect the views of Fortinet, Inc., its affiliates, and emails are not binding on Fortinet and only a writing manually signed by Fortinet's General Counsel can be a binding commitment of Fortinet to Fortinet's customers or partners. Thank you. ***


reply via email to

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