Can you clarify why you need a gateway? Is the far side going to challenge us and request authentication credentials? So you want us to not resolve the domain of the target at all in any way? That kinda breaks the rules because you should always check the NAPTR's and SRV and resolve to the target in that manner its a requirement. If you want to force things to a proxy and let the proxy on the far side do the work then you do this: sofia/profile/alice@bar.com;fs_path=proxy.foo.com /b On Dec 9, 2008, at 12:06 PM, Erick Johnson wrote:
Hi Brian,
Thanks for the reply, but I still don't think that answers my original question. I'm trying to get FS to act simply as a UAC in this instance, what I want is for FS to proxy ALL outbound calls through my proxy server at foo.com.
So when FS originates a call to alice@bar.com I want the signaling path to be set up as:
FreeSwitch ---> proxy.foo.com ---> alice@bar.com
I found this thread: http://lists.freeswitch.org/pipermail/freeswitch-users/2008-November/008582.... but I still can't seem to get FS to stop resolving domain bar.com on it's own, even when I set the sip_invite_domain variable like so: originate {sip_invite_domain='proxy.foo.com'}sofia/external/alice@bar.com &echo()
That is how I ended up using the "originate sofia/gateway/proxy/alice@bar.com &echo()" command. While I understand that's wrong, I don't know what the right config/ cmd is to accomplish my task.
Any other help is much appreciated.
Thanks,
Erick