[Freeswitch-users] outbound proxy and port

[Steven Ayre]

Just got it working by using the format "sip:a.b.c.d:port" or
"sips:a.b.c.d:port"

It looks like there's a difference in the handling of outbound-proxy for a
gateway compared to a profile. A gateway prepends sip: if it's missing,
while a profile does not. So it seems both the documentation could be
improved, and the code could be patched so they use the value consistently
as ip:port would presumably work ok for a gateway. That's from a reading of
the source code in master, so I would expect 1.6 should have the same
behaviour as 1.4.26.




On 4 January 2016 at 21:03, Michael Jerris <mike at jerris.com> wrote:

> I haven't seen anyone working on this but id be happy to review patches
> that address the issue.  I wouldn't expect a difference in 1.6 behavior on
> this issue
>
>
> On Monday, January 4, 2016, Steven Ayre <steveayre at gmail.com> wrote:
>
>> Sorry for resurrecting a very old thread. Has anyone got this working?
>>
>> I've just tried this on 1.4.26 and seem to be seeing the same result.
>> With a outbound-proxy value of "a.b.c.d:port" sofia's log (sofia loglevel
>> all 9) shows sofia is trying the DNS lookup itself apparently without
>> sending anything to the proxy, which fails as this side of proxy can't
>> resolve the address. With the :port removed so its value is just "a.b.c.d"
>> it shows a different output of trying to send to the proxy which fails with
>> an ICMP error (tport_udp_error) - expected since it tries 5060 instead of
>> the proxy's actual port.
>>
>> If no-one has it working, I'll try to reproduce on 1.6 and file a Jira.
>>
>>
>> On 30 September 2013 at 08:58, Cal Leeming [Simplicity Media Ltd] <
>> cal.leeming at simplicitymedialtd.co.uk> wrote:
>>
>>> Hi Chris,
>>>
>>> From what I can tell, the value from profile->outbound-proxy is
>>> passed into sofia NTATAG_DEFAULT_PROXY() and accepts a url_t structure [1],
>>> which clearly allows for a port to be specified [2]. However, I was unable
>>> to find any working examples from others on setting a port value inside
>>> outbound-proxy, nor did the documentation reference this.
>>>
>>> Can you please tell us;
>>>
>>> * Are you running against the latest stable version of FS?
>>> * Have you tried this against the most recent master?
>>> * Can you please pastebin the logs of what happens when you try
>>> including a port?
>>>
>>> Once you've sent this through, we can determine if it's a bug or not.
>>>
>>> Hope this helps
>>>
>>> Cal
>>>
>>> [1]
>>> http://sofia-sip.sourcearchive.com/documentation/1.12.7/nta__tag_8h_470c3d7c598ed2d4514836d3bb916fc7.html#470c3d7c598ed2d4514836d3bb916fc7
>>> [2]
>>> http://sofia-sip.sourcearchive.com/documentation/1.12.7/structurl__t.html
>>>
>>>
>>>
>>> On Thu, Sep 26, 2013 at 8:23 PM, Chris B. Ware <chrisbware at yahoo.it>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> I need to send registrations and calls from external profile to a si
>>>> provider, passing through an outbound proxy, port 5080.
>>>>
>>>> I I set on sofia:
>>>>
>>>>  <param name="outbound-proxy" value="10.24.4.151"/>
>>>>
>>>> Registrations pass through the OB Proxy, but using, of course, standard
>>>> 5060 port.
>>>>
>>>> I I set on sofia:
>>>>
>>>>  <param name="outbound-proxy" value="10.24.4.151:5080"/>
>>>>
>>>> Param seems to be not understood and registrations go directly to the
>>>> sip provider.
>>>>
>>>> How can I set outbound proxy port?
>>>>
>>>> Thanks
>>>>
>>>>
>>>> _________________________________________________________________________
>>>> Professional FreeSWITCH Consulting Services:
>>>> consulting at freeswitch.org
>>>> http://www.freeswitchsolutions.com
>>>>
>>>> FreeSWITCH-powered IP PBX: The CudaTel Communication Server
>>>> http://www.cudatel.com
>>>>
>>>> Official FreeSWITCH Sites
>>>> http://www.freeswitch.org
>>>> http://wiki.freeswitch.org
>>>> http://www.cluecon.com
>>>>
>>>> FreeSWITCH-users mailing list
>>>> FreeSWITCH-users at lists.freeswitch.org
>>>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>>>> UNSUBSCRIBE:
>>>> http://lists.freeswitch.org/mailman/options/freeswitch-users
>>>> http://www.freeswitch.org
>>>>
>>>>
>>>
>>> _________________________________________________________________________
>>> Professional FreeSWITCH Consulting Services:
>>> consulting at freeswitch.org
>>> http://www.freeswitchsolutions.com
>>>
>>> FreeSWITCH-powered IP PBX: The CudaTel Communication Server
>>> http://www.cudatel.com
>>>
>>> Official FreeSWITCH Sites
>>> http://www.freeswitch.org
>>> http://wiki.freeswitch.org
>>> http://www.cluecon.com
>>>
>>> FreeSWITCH-users mailing list
>>> FreeSWITCH-users at lists.freeswitch.org
>>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>>> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
>>> http://www.freeswitch.org
>>>
>>>
>>
> _________________________________________________________________________
> Professional FreeSWITCH Consulting Services:
> consulting at freeswitch.org
> http://www.freeswitchsolutions.com
>
> Official FreeSWITCH Sites
> http://www.freeswitch.org
> http://confluence.freeswitch.org
> http://www.cluecon.com
>
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20160104/c5dabe2d/attachment-0001.html