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? -------------------------- 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." 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. -------------------------------- Regards, Jonas
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
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.
Ok. I got two aliases for the default profile, my domain name and freeswitchs ip address. This is since not all phones have different fields for domain and proxy address, and I can't use the domain name as proxy address. this means that some phones are registered as username@mydomain.com and some as username@192.168.1.124. This makes it difficult, since I need to keep track of which domain name they used when registering. (I need to use for instance "originate sofia/mydomain.com/username number" for some, and "originate sofia/192.168.1.124/username number" for others, even if they are in the same domain. It would be a lot easier if I just could use "sofia/<myprofilename>/username", since they all belong to the same profile. But maybe I'm missing something? regards, Jonas
On Feb 7, 2008, at 8:58 AM, Jonas Gauffin wrote:
Ok. I got two aliases for the default profile, my domain name and freeswitchs ip address. This is since not all phones have different fields for domain and proxy address, and I can't use the domain name as proxy address.
In these cases you just enter the domain in the registrar. Polycom has two settings for this ... one under network and one under SIP lines.
this means that some phones are registered as username@mydomain.com and some as username@192.168.1.124.
Is this the ip for the profile? You can use <param name="force- register-domain" value="mydomain.com"/> on the profile to force everything to the domain on the backend.
This makes it difficult, since I need to keep track of which domain name they used when registering. (I need to use for instance "originate sofia/mydomain.com/username number" for some, and "originate sofia/192.168.1.124/username number" for others, even if they are in the same domain.
SIP is just like email you don't use IP's in email addresses these days. And you should never do so in SIP addresses either. Asterisk doesn't do this via names because they don't want the extra hit of DNS lookups but that is how SIP was designed. user@domain.com and not user@1.2.3.4 .
It would be a lot easier if I just could use "sofia/<myprofilename>/username", since they all belong to the same profile.
But maybe I'm missing something?
regards, Jonas
You should always use domains and not IP's as that allows you to use SRV records and failover registrars and such. /b
Hi all - I've got the following scenario: - call comes in, connects to a call control app of mine using an async outbound socket from FS; - answer call, play "we are trying to connect you" prompt - start playback of cheesy jingle music thing while (caller_not_killed_by_cheese) { - bridge to specified number using outbound gateway - if successful, let them chat and exit - if not, wait 10 seconds } The outbound call attempts cause short (some hundreds of ms) gaps in the audio if they fail - number being busy or unobtainable are my two failure cases that I've tested. Whilst the caller might view this as a blessing, I need to fix it. Any ideas? Cheers -- Dave
participants (3)
-
Brian West
-
David Knell
-
Jonas Gauffin