On Feb 5, 2008, at 8:13 AM, Jonas Gauffin wrote:
Hello
Question 1:
I got the following config: Name Type Data State = = = = = = = = = = = = = = = = = = = = = = = = = = = ====================================================================== outbound profile sip:mod_sofia@MY.PUBLIC.IP:5080 RUNNING (0) nat profile sip:mod_sofia@MY.PUBLIC.IP:5060 RUNNING (0) default profile sip:mod_sofia@192.168.1.124:5070 RUNNING (0) mydomain.com alias default ALIASED = = = = = = = = = = = = = = = = = = = = = = = = = = = ====================================================================== 3 profiles 1 alias
I can't user "originate sofia/default/auser 8888", I get "Cannot locate registered user auser@default". It works if I use "originate sofia/mydomain.com/auser 8888". Shouldn't both work?
No they shouldn't both work. You can have multiple aliases for a profile. If you don't specify a domain it has no way of finding the user in that domain.
--------------------------
Question 2:
Isn't this valid? <X-PRE-PROCESS cmd="set" data="domain=$${local_ip_v4}"/> <X-PRE-PROCESS cmd="set" data="sip_profile=mydomain.com"/>
If not, please change the description: "sip_profile: Must be a domain name if you are being a registry server; otherwise can be any string."
This isn't true. You're confusing sip_profile as depending on domain. If mydomain.com resolves to 192.168.1.124 then you can just set domain=mydomain.com and then you can register as a user@mydomain.com If you notice in the default config I do: <X-PRE-PROCESS cmd="set" data="domain=$${local_ip_v4}"/> <X-PRE-PROCESS cmd="set" data="sip_profile=$${domain}"/> Which would make them be the IP address.
It produces the following config: Name Type Data State = = = = = = = = = = = = = = = = = = = = = = = = = = = ====================================================================== outbound profile sip:mod_sofia@MY.PUBLIC.IP:5080 RUNNING (0) nat profile sip:mod_sofia@MY.PUBLIC.IP:5060 RUNNING (0) default profile sip:mod_sofia@192.168.1.124:5070 RUNNING (0) 192.168.1.124 alias default ALIASED = = = = = = = = = = = = = = = = = = = = = = = = = = = ====================================================================== 3 profiles 1 alias
User's cant register using mydomain.com as domain. I tried by adding $${sip_profile} as an alias for the default profile, but that didn't help.
You can force the reg domain in the sip profile but that kinda defeats the purpose sip and domains. Profile param: <param name="force-register-domain" value="mydomain.com"/> /b