[Freeswitch-users] FS_PATH for Gateways
shakumarsoftware at gmail.com
Tue Oct 24 17:04:27 UTC 2017
Well, that is an option but I found out that the SIP Authentication breaks
with certain providers while using the Proxy param.
- The Request URI in the REG/INV will reflect the Proxy param.
- The Proxy-Auth headers has a URI parameter that will now have the Request
URI ( Proxy param).
Some SIP providers have the Realm/Domain different from the Proxy. So they
end up rejecting the request since the domain in the proxy is not in their
white list of authenticated hosts.
Eg. Proxy - sip10.voip.xyz.com
Realm - xyz.com
The REG/INV will have the Req URI = sip:sip10.voip.xyz.com and the Proxy
Auth header will also have the same URI. The Providers I know are unwilling
to add the Proxy domain sip10.voip.xyz.com into their white-list of
authenticated hosts. They require the Proxy-Auth to have xyz.com.
I am not sure if I made myself clear ?
Anyway, I managed to set the sip_invite_route_uri as the Proxy. That seemed
to work even for gateways.
On Sat, Oct 21, 2017 at 8:05 AM, Aqs Younas <aqsyounas at gmail.com> wrote:
> Why not use proxy param in gateway?
> On 19 Oct 2017 3:11 am, "Sharath Kumar" <shakumarsoftware at gmail.com>
>> Can we add an fs_path when dialing out via a gateway ? I know this has
>> been asked before and in the archives it has been said to support and also
>> not support fs_path in a gateway. Just wanted to confirm.
>> thank you,
>> Professional FreeSWITCH Consulting Services:
>> consulting at freeswitch.org
>> Official FreeSWITCH Sites
>> FreeSWITCH-users mailing list
>> FreeSWITCH-users at lists.freeswitch.org
> Professional FreeSWITCH Consulting Services:
> consulting at freeswitch.org
> Official FreeSWITCH Sites
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the FreeSWITCH-users