Hi Dave - maybe I'm only failing in the configuration. In the Account
settings, there are the following fields:
login/username: I guess this is the username in the SIP AoR (public SIP URI)
Password: the password
SIP Domain/Realm: I guess this is the domain part in the SIP AoR (public
SIP URI) - which is usually also used as authentication realm
Displayname: the displayname in the From: header
Advanced:
Server:
Proxy: Port
I do not fully understand the meaning of the advanced section. Usually,
the SIP domain should be enough - the client makes SRV lookups and gets
the hostname and port of the SIP proxy.
Sometimes, if a SIP client does not support SRV lookups or you want to
manually route the SIP requests to a certain host/IPaddress you may also
want to configure an "outbound proxy". I guess this is what the
Server/Proxy settings are for. But, sending to an outbound proxy should
not change the domains in the SIP message.
E.g, when I configure my SIP Account (sip:[EMAIL PROTECTED])
and leave the advanced section unchanged, then the SIP request is fine:
REGISTER sip:nic.at43.at SIP/2.0
Via: SIP/2.0/UDP 10.10.0.50:5060;rport;branch=z9hG4bK2311978858
Route: <sip:nic.at43.at:5060;lr>
From: <sip:[EMAIL PROTECTED]>;tag=3773126573
To: <sip:[EMAIL PROTECTED]>
Call-ID: [EMAIL PROTECTED]
CSeq: 3 REGISTER
Contact: <sip:[EMAIL PROTECTED]:5060>
Max-Forwards: 70
User-Agent: wengo/v1/wengophoneng/wengo/rev11668/trunk/
Expires: 0
Content-Length: 0
Then I configure in the advanced section an outbound proxy.
Server: 83.136.32.160
Proxy: 83.136.32.160 Port 5060
In this case Openwengo sends the request to 83.136.32.160 with wrong
headers:
U 2007/07/12 10:55:09.411616 83.136.33.3:5060 -> 83.136.32.160:5060
REGISTER sip:83.136.32.160 SIP/2.0
Via: SIP/2.0/UDP 10.10.0.50:5060;rport;branch=z9hG4bK3412740584
Route: <sip:83.136.32.160:5060;lr>
From: <sip:[EMAIL PROTECTED]>;tag=290849598
To: <sip:[EMAIL PROTECTED]>
Call-ID: [EMAIL PROTECTED]
CSeq: 1 REGISTER
Contact: <sip:[EMAIL PROTECTED]:5060>
Max-Forwards: 70
User-Agent: wengo/v1/wengophoneng/wengo/rev11668/trunk/
Expires: 2940
Content-Length: 0
If the Server/Proxy settings are intended as outbound proxy settings,
then they should only change the destination where the request is sent
to and optional add a route header - but never change the RURI, From-URI
and To-URI.
Further I often see strange requests with user nobody.
This "nobody" stuff is maybe again a proprietary wengo thing which I
have no clue what is it good for.
REGISTER sip:5.6.7.8 SIP/2.0
Via: SIP/2.0/UDP 10.10.0.50:5060;rport;branch=123456789
Route: <sip:5.6.7.8;lr>
From: nobody <sip:[EMAIL PROTECTED]>;tag=123456789
To: <sip:[EMAIL PROTECTED]>
Call-ID: [EMAIL PROTECTED]
Contact: <sip:[EMAIL PROTECTED]>
CSeq: 2 REGISTER
Content-Length: 0
regards
klaus
Dave Neary wrote:
Hi Klaus,
Klaus Darilion wrote:
I configure openwengo for my SIP proxy:
domain/realm: mydomain.foo
Then I activate "advanced" section and set:
server: mydomain.foo
proxy: sip.mydomain.foo port 5060
[x] send via proxy
But the REGISTER sent by openwengo to sip.mydomain.foo also uses
sip.mydomain.foo in the RURI and in From: and To: instead of just using
mydomain.foo.
Just to be sure I understand what you're saying:
You're expecting the REGISTER to use the SIP _server_ in From: and To:
and it's using the proxy? (Not the realm)
I don't know enough about the SIP protocol yet to know if the behaviour
you expect is the correct behaviour - I'll let someone else (Minh?)
comment on that.
Cheers,
Dave.
_______________________________________________
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
