linphone-users
[Top][All Lists]
Advanced

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

Re: [Linphone-users] Fwd: Re: [redhat.com #1263208] Linphone on the inte


From: Simon Morlat
Subject: Re: [Linphone-users] Fwd: Re: [redhat.com #1263208] Linphone on the internal RH SIP
Date: Wed, 2 Sep 2009 11:55:56 +0200
User-agent: KMail/1.11.4 (Linux/2.6.30-1-amd64; KDE/4.2.4; x86_64; ; )

Excellent news. My original bugfix was incorrect, but I just pushed a few 
minutes ago another correction.

Simon

Le mardi 1 septembre 2009 22:42:20, Christian Schäfer a écrit :
> Hi Simon,
>
> it sends:
>
> SIP/2.0 479 Please don't use private IP addresses
>
> so your bugfix should work. I'll give it a try as soon as you'll release
> the next version.
>
> Chris
>
> Simon Morlat wrote:
> > Hi Christian,
> >
> > If the registrar sends back an error ( 4xx response, not remain silent) ,
> > then the bugfix I just commited (see the email to Matej) should solve
> > your problem.
> >
> > Simon
> >
> > Le mardi 1 septembre 2009 15:46:04, Christian Schäfer a écrit :
> >> Hi,
> >>
> >> this sounds like the problem I have too with linphone. I posted it
> >> around 7/19 to this list ('Problem with private IP address and picky
> >> registrars').
> >> The problem seems to be that some registrars don't like the private IP
> >> address that gets transmitted to them along with the public one. For me
> >> this is also a show-stopper when using linphone from behind a NAT
> >> router. In this scenario I also have to switch to twinkle which seems to
> >> be the only SIP client under Linux that doesn't send the private IP
> >> address (Ekiga actually sends it too).
> >> Beside that, I really like Linphone. It's stable and reliable. It would
> >> be great if some workaround for those registrars could be implemented,
> >> e.g. a second connection attempt in case the first wasn't successful,
> >> without transmitting the private address.
> >>
> >> Chris
> >>
> >> Matěj Cepl wrote:
> >>> Hi, this is the result of my dialog with our SIP support guys.
> >>> Apparently, linphone gets confused and offers my internal LAN address
> >>> (192.168.1.*) instead of VPN one. The result is that it the
> >>> registration to the internal SIP server fails (Not Found) and when
> >>> calling the contact inside of RH VPN I get "Service Unavailable". It
> >>> doesn't matter whether I use an internal STUN server or use my IP
> >>> address directly (this VPN connection is not NATed).
> >>>
> >>> This is the only showstopper for using linphone as my main SIP client
> >>> (the only other working SIP client for me is Twinkle, and I really
> >>> don't like KDE apps on my machine). There are some other problems
> >>> (e.g., for many users STUN/direct IP/etc. setting should be
> >>> per-account, not per-program preference, many UI glitches), but
> >>> fortunately non other is a showstopper for me.
> >>>
> >>> What do you think?
> >>>
> >>> Matěj
> >>>
> >>> -------- Původní zpráva --------
> >>> Předmět:  Re: [redhat.com #1263208] Linphone on the internal RH SIP
> >>> Datum:    Mon, 31 Aug 2009 16:23:14 -0400
> >>> Od:       Joe Micciche via RT <address@hidden>
> >>> Přeposláno - Komu:        address@hidden
> >>> Komu:     address@hidden
> >>>
> >>> On 08/31/2009 03:24 PM, Matej Cepl via RT wrote:
> >>>> Dne 31.8.2009 20:39, Joe Micciche via RT napsal(a):
> >>>>> Hi Matej, is it possible to get a tcpdump from your machine from when
> >>>>> you start Linphone through to attempting a call? The txt file doesn't
> >>>>> give me the depth of information I'd like to have in order to analyze
> >>>>> this.
> >>>>
> >>>> Is this what you want?
> >>>>
> >>>> Matěj
> >>>
> >>> Matej, many thanks for capturing this, the dump is quite helpful.
> >>>
> >>> I have extracted only the packets relevant to your client attempt to
> >>> register to and call from our internal systems - this file is attached.
> >>>
> >>> In short, the dialog begins between your client, 10.36.4.214 on vpn,
> >>> and our registrar, 10.32.8.32, at Packet #75.
> >>>
> >>> The client sends the REGISTER request, but the client SIP stack is
> >>> setting your Via: and Contact: address to 192.168.1.2:5060. This is the
> >>> core problem, obviously 192. is neither valid nor routable.
> >>>
> >>> Linphone's exosip stack should set your request IP's to the vpn IP, not
> >>> to the un-NAT-ed IP of your machine.
> >>>
> >>> Please let me know if you need more detail or would like to do more
> >>> troubleshooting.
> >>>
> >>> --
> >>> ==================================================================
> >>>
> >>>
> >>> -----------------------------------------------------------------------
> >>>-
> >>>
> >>> _______________________________________________
> >>> Linphone-users mailing list
> >>> address@hidden
> >>> http://lists.nongnu.org/mailman/listinfo/linphone-users
> >>
> >> _______________________________________________
> >> Linphone-users mailing list
> >> address@hidden
> >> http://lists.nongnu.org/mailman/listinfo/linphone-users
>
> _______________________________________________
> Linphone-users mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/linphone-users





reply via email to

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