View Single Post
Posts: 161 | Thanked: 99 times | Joined on Jan 2008
#10
Originally Posted by Moonshine View Post
I actually gave Linphone a try last week and it worked very well for me on a Ubuntu machine. (via my own Asterisk server setup for h.263/h.263+) So just to let you know it's possible. I don't remember doing anything special, except possibly disabling any other video codec options Linphone had maybe? Other then that, Asterisk does have a few quirks to get around if that's what you're using.
Thanks for the information. I'm not using Asterisk, but an external SIP provider.

My main problem with Linphone is, that Linphone is automatically choosing the SIP realm based on the SIP username/sip server, which is not always correct.

When using a SIP provider where SIP server address = SIP realm this is no problem. But for my SIP provider the realm is dus.net, but the server adress is voip.dus.net.

So with Ekiga or any other SIP client where I can manually specify a realm a (successfull) logon looks like
Code:
> Request-Line: REGISTER sip:dus.net SIP/2.0
< Status-Line: SIP/2.0 100 Trying
< Status-Line: SIP/2.0 401 Unauthorized
> Request-Line: REGISTER sip:dus.net SIP/2.0
> Request-Line: SUBSCRIBE sip:123456789@dus.net SIP/2.0
< Status-Line: SIP/2.0 100 Trying
< Status-Line: SIP/2.0 200 OK
With Linphone it's always
Code:
> Request-Line: REGISTER sip:voip.dus.net SIP/2.0
< Status-Line: SIP/2.0 100 Trying
< Status-Line: SIP/2.0 401 Unauthorized
> Request-Line: REGISTER sip:voip.dus.net SIP/2.0
< Status-Line: SIP/2.0 100 Trying
< Status-Line: SIP/2.0 401 Unauthorized
There seems to be no way to specify a different realm in the Linphone configuration.

Actually I got Linphone working with another SIP provider where server = realm. But this other provider doesn't support H.263.