another switch_ivr_set_user() can't find user
You don't have a default user in domain 192.168.14.10, in the default config I used this so that you can set some vars on every call with
Thanks for pointing it out and explaining the purpose. It looks like the domain is coming from set_domain in default.xml which gets it from sip_auth_realm. I guess the question is if force-register-domain is being used then: a) Should sip_auth_realm be set by FreeSWITCH to the value associated with force-register-domain b) or should set_domain in default.xml simply check for force-register-domain when setting domain? -- John ------------------------------------------------------------------------- | Feith Systems | Voice: 1-215-646-8000 | Email: john@feith.com | | John Wehle | Fax: 1-215-540-5495 | | -------------------------------------------------------------------------
You have to remember the default assumes a lot. You go to changing things you have to then change the way things are assumed. /b On Dec 23, 2008, at 4:51 PM, John Wehle wrote:
You don't have a default user in domain 192.168.14.10, in the default config I used this so that you can set some vars on every call with
Thanks for pointing it out and explaining the purpose.
It looks like the domain is coming from set_domain in default.xml which gets it from sip_auth_realm. I guess the question is if force-register-domain is being used then:
a) Should sip_auth_realm be set by FreeSWITCH to the value associated with force-register-domain
b) or should set_domain in default.xml simply check for force- register-domain when setting domain?
-- John ------------------------------------------------------------------------- | Feith Systems | Voice: 1-215-646-8000 | Email: john@feith.com | | John Wehle | Fax: 1-215-540-5495 | | -------------------------------------------------------------------------
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
On Tue, Dec 23, 2008 at 05:51:38PM -0500, John Wehle wrote:
It looks like the domain is coming from set_domain in default.xml which gets it from sip_auth_realm. I guess the question is if force-register-domain is being used then:
a) Should sip_auth_realm be set by FreeSWITCH to the value associated with force-register-domain
b) or should set_domain in default.xml simply check for force-register-domain
As I understand it, that's a choice you need to make in designing your dial plan. I'm currently confronted with the same issue and, being new to FreeSWITCH, I'm not sure what would be the best solution. In my case, there is a SIP phone that needs to contact FreeSWITCH by its IPv4 address - there's no A record for the FreeSWITCH box, and the address is 192.168.0.2 on the local LAN. The FreeSWITCH machine does have an AAAA record in DNS, so any incoming IPv6 call will address it by its fully-qualified domain name. Not surprisingly, the logic in the supplied external.xml dialplan configuration results in IPv6 incoming calls to local extensions failing, due to the wrong domain name, after the transfer to default.xml when the bridge application is executed. By default, of course, the domain is the IPv4 address, which is fine for IPv4 calls. There are ways around this, of course, but I haven't worked out what would be the best to implement.
The default is just an example that tries to get you started... the key thing you need to remember for ALL calls coming in that aren't authenticated the domain_name variable needs to be set before you transfer into the default context. /b On Dec 23, 2008, at 5:27 PM, Jason White wrote:
There are ways around this, of course, but I haven't worked out what would be the best to implement.
participants (3)
-
Brian West
-
Jason White
-
John Wehle