31 May
2006
31 May
'06
3:57 a.m.
I'm unclear on how multiple domains should be handled in sip/openser,
etc. The scope of my confusion may be broader than just with openser,
and this is more of a "concept" problem, but I'm hoping someone here
can point me in the right direction.
I've read the "domain" module documentation at openser.org.
I'm using a Linksys SPA942 IP phone for this experiment with
my openser 1.0.1 server.
The SPA942 appears to do the following:
a) sends "sip:$PROXY" for the REGISTER request-uri.
Here $PROXY is the actual entry typed in by the user,
as opposed to something looked up by using DNS SRV.
b) appends "@$PROXY" to the "User ID:" entry in the "From:"
field
and appends @IP:PORT for "Contact:"
That is, as the person who configures the phone, I can view the
proxy setting as declaring the domain of the user.
But it seems more natural to me to put the actual host name of the
proxy in that setting. That is, if I run a service on sip.foo.net and
have customers in domains bif.net and baz.net then each of them
listing sip.foo.net as their sip proxy is reasonable.
But, if I go that route, then it seems the only way for the user to
send the sip server their domain is as part of the userID:
john(a)baz.net and if they do that then I get "From:" fields like
john@baz.net@sip.foo.net, and similar "Contact:" settings.
Now, I can strip off the trailing domain but the clumsiness of that
uri (sip:john@baz.net@sip.foo.net) gives me the feeling that this is
the wrong approach. Looking at the "Contact:" pretty much convinces
me of this: sip:john@baz.net@192.168.168.214:5060
But that takes me back to using the Proxy field as dual-duty:
specifying the proxy and also the user's domain.
I just looked at a cisco 7905 and it too does not appear to have
a way to set the user domain.
I can see how I could use unique AuthIDs to look up domains at
registration time, but that seems misguided too.
What am I missing?
Thanks,
-mark
31 May
31 May
12:50 p.m.
Hi Mark,
if you have a different proxy name (as server name) than the domain
name, you need to use the outbound proxy (OBP) feature on the client:
- set as domain the SIP domain you want (like bif.net or baz.net)
- set OBP the address of the server (like sip.foo.net).
By this, the requests will have in FROM/RURI the SIP domain, but they
will be sent to the OBP server.
regards,
bogdan
Mark Kent wrote:
I'm unclear on how multiple domains should be
handled in sip/openser,
etc. The scope of my confusion may be broader than just with openser,
and this is more of a "concept" problem, but I'm hoping someone here
can point me in the right direction.
I've read the "domain" module documentation at openser.org.
I'm using a Linksys SPA942 IP phone for this experiment with
my openser 1.0.1 server.
The SPA942 appears to do the following:
a) sends "sip:$PROXY" for the REGISTER request-uri.
Here $PROXY is the actual entry typed in by the user,
as opposed to something looked up by using DNS SRV.
b) appends "@$PROXY" to the "User ID:" entry in the "From:"
field
and appends @IP:PORT for "Contact:"
That is, as the person who configures the phone, I can view the
proxy setting as declaring the domain of the user.
But it seems more natural to me to put the actual host name of the
proxy in that setting. That is, if I run a service on sip.foo.net and
have customers in domains bif.net and baz.net then each of them
listing sip.foo.net as their sip proxy is reasonable.
But, if I go that route, then it seems the only way for the user to
send the sip server their domain is as part of the userID:
john(a)baz.net and if they do that then I get "From:" fields like
john@baz.net@sip.foo.net, and similar "Contact:" settings.
Now, I can strip off the trailing domain but the clumsiness of that
uri (sip:john@baz.net@sip.foo.net) gives me the feeling that this is
the wrong approach. Looking at the "Contact:" pretty much convinces
me of this: sip:john@baz.net@192.168.168.214:5060
But that takes me back to using the Proxy field as dual-duty:
specifying the proxy and also the user's domain.
I just looked at a cisco 7905 and it too does not appear to have
a way to set the user domain.
I can see how I could use unique AuthIDs to look up domains at
registration time, but that seems misguided too.
What am I missing?
Thanks,
-mark
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
6:59 p.m.
> if you have a different proxy name (as server
name) than the domain
> name, you need to use the outbound proxy (OBP) feature on the client:
> - set as domain the SIP domain you want (like bif.net or baz.net)
> - set OBP the address of the server (like sip.foo.net).
>
> By this, the requests will have in FROM/RURI the SIP domain, but they
> will be sent to the OBP server.
OK, so I guess my view of how things work has been tainted by the
SIP UA I have (Linksys SPA942 and SPA3000).
There is no domain setting, at least not one that affects the user
domain in sip transactions. The OBP setting in these devices appears
to play double-duty as both the SIP user domain and also where to send
requests. However, there are 684 things that can be tweaked on the
box, so I may have missed it... but I don't think so.
Thanks,
-mark
11:11 p.m.
When setting up Line 1 on the SPA3000 check out the 'Proxy'
setting. That's the domain. If you like, you can set Proxy to
'foo.bar' and you
can set 'Outbound Proxy' to 'proxy.foo.bar', then you can tell SIPURA to
use the outbound proxy with 'Use Outbound Proxy'.
Anyway, I think this is the domain you are looking for... I don't have
a 3000, but, that's
the way it looks on my old 2xxx sipura.
SIPURA is really an awesome device, you can do just about anything.
-g
On 5/31/06, Mark Kent <mark(a)noc.mainstreet.net> wrote:
--
Greg Fausak
greg(a)thursday.com
> if you
have a different proxy name (as server name) than the domain
> name, you need to use the outbound proxy (OBP) feature on the client:
> - set as domain the SIP domain you want (like bif.net or baz.net)
> - set OBP the address of the server (like sip.foo.net).
>
> By this, the requests will have in FROM/RURI the SIP domain, but they
> will be sent to the OBP server.
OK, so I guess my view of how things work has been tainted by the
SIP UA I have (Linksys SPA942 and SPA3000).
There is no domain setting, at least not one that affects the user
domain in sip transactions. The OBP setting in these devices appears
to play double-duty as both the SIP user domain and also where to send
requests. However, there are 684 things that can be tweaked on the
box, so I may have missed it... but I don't think so.
Thanks,
-mark
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
1 Jun
1 Jun
12:21 a.m.
> SIPURA is really an awesome device, you can do
just about anything.
It is awesome, but I think in a different way than you suggest :-)
For example, the documentation for "Proxy" says it is the
"SIP Proxy Server for all outbound requests"... which would be fine,
except that it isn't that.
It does appear to be the Domain, as you suggest (Thanks!). Well... if
it is specified alone then it is both the domain and the proxy server.
If Outbound Proxy is specified, then it is just the Domain, it no
longer appears to function as the proxy.
OK, so if you specify the Proxy, and the "Outbound Proxy", together
with "Use Outbound Proxy" and "Use OB Proxy in Dialog", where the
documentation strongly suggests that the OB will be used for *all*
outbound requests (they use the words "force" and "all"), then
you're
pretty sure that either your Proxy or your Outbound Proxy will get
set-up packets... right?
Ooops! The reality is that if you have "use DNS SRV" set (under
"Proxy and Registration"), and then dial foo(a)baz.net then the box
will use DNS SRV for baz.net and send the INVITE *directly* to the
returned server... no packets will make it to the proxies we set
(the ones we just *forced* such packets to).
Note that not only is "use DNS SRV" only under the "Proxy and
Registration" section, but the documentation strongly suggests that it
affects only the Proxy and OB Proxy lookups.
So, Yes, it is awesome. I find myself constantly in awe
when working with the SPA3000 and SPA942 :-)
-mark
6756
days inactive
6756
days old
4 comments
4 participants
participants (4)
-
Bogdan-Andrei Iancu -
Greg Fausak -
Mark Kent -
Mark Kent