Re: [Linphone-users] realm and sip proxy

[Simon Morlat]

Hello,

Linphone-1.0.1 allows what you want to do ! You can configure as many 
proxy/registrar settings as you want, setting them as outbound proxy, and 
setting the default one for your calls.
In order to use a proxy as an outbound proxy, you just need to set the 
"route:" parameter of the proxy config box to the sip url of your proxy. Then 
choose this proxy as your default proxy.

You're right about the -R flag. However the usal way is to have libraries with 
different soname, maybe this was not the case for libosip-2.0 and libosip-2.2

Simon

Le Dimanche 17 Avril 2005 22:58, Daniel Freedman a écrit :
> <Please cc: me on replies>
>
> Hi Simon,
>
> I'm following up on this thread since I encountered the same issue, so
> maybe I can explain it further.  I'm using LinPhone 0.12.2 as packaged
> for Debian Sarge.  It's working perfectly for me, but only because I'm
> lucky in the configuration that my VoIP provider chose (in that they
> selected to have the same IP address point to both SIP registrar and
> SIP outbound proxy).
>
> Anyway, when I go to configure LinPhone via the 'Preferences' dialog
> box, and the 'SIP' configuration tab, I'm presented with some choices
> regarding the 'Remote services'.  I select to use a 'SIP Registrar'
> and enter the server address for this registrar, as well as my
> password and my address of record.  So far, so good.  The problem now
> lies with the fact that Linphone only allows me the option of using
> *THIS* 'SIP Registrar' as my outbound proxy.  It does not allow me to
> utilize a different upstream server for outbound proxy.  I happened to
> luck out, as my VoIP provider has their outbound proxy as simply a DNS
> CNAME alias for their SIP registrar, so my packets went to the right
> place.  However, other VoIP providers might use different setups, in
> which case this would fail.  Just FYI, in contrast, you might want to
> examine Kphone which allows independent configuration of SIP
> registrars and Outbound proxies.  (However, I should compliment
> LinPhone as it really worked with the Digest Authentication of my VoIP
> provider, while KPhone could successfully register, but couldn't
> properly authenticate its INVITEs, so it would just hang and I never
> got it to complete a call...)
>
> In other similar feature requests, I'm wondering if you're considering
> adding STUN support, rather than the more basic 'NAT traversal
> options' that are currently available (but require user to know
> his/her NAT WAN address).
>
> Finally, I compiled LinPhone 1.0.1 from source, and still had the
> above issues.  In addition, I ran into a few other things you might
> want to note: I thought you might want to include an 'autoconf'd test
> in the 'configure' script to check for a recent-enough version of
> libosip2.  When I tried to compile the eXosip library included with
> LinPhone 1.0.1 against my Debian sarge libosip2 dev files (version
> 2.0.6), the compile balked. However, the upstream source libosip2
> version 2.2.1-pre2 worked fine with the included eXosip. Further, the
> '--with-osip=/path/to/source/osip" correctly finds the specified
> libosip2 libraries for linking, but then the resulting binaries don't
> find them for runtime linking, and instead invoke the older Debian
> packaged libosip2.  I'm a little rusty with my link options, but I
> believe this is the difference between passing the osip libraries as
> '-L' options versus '-R'/'-rpath' options.  I'm not knowledgable about
> 'automake', but I imagine this behavior could be fixed through it, if
> desired.  In the end, though I could compile and run linphone 1.0.1, I
> could never get it to successfully complete a SIP call as I could with
> 0.12.2 (at least with my configuration).
>
> Hope these comments help, and thank you, Simon, for a great linux SIP
> softphone...
>
> Take care,
> Daniel
>
> On 12 Apr 2005, Simon Morlat wrote:
> > Hi,
> >
> > I don't fully understand what you mean. Linphone normally
> > allows to have proxy and realm different. What's going wrong
> > exactly ? The server rejects your authentication ? Please
> > clarify.
> >
> > Simon