Hello Daniel and Andrew,
Sorry to dig up an old thread, but I'm just now getting around to a more
permanent fix for this. Is there a way to urlencode the received parameter?
See:
http://jira.freeswitch.org/browse/FS-4989
Thanks in advance,
Spencer
On Sep 25, 2012, at 1:23 PM, Daniel-Constanti
Hello,
I cherry-picked the commit to 3.2 branch. Pull the last version and see
if all is ok.
Cheers,
Daniel
On 9/24/12 4:42 PM, Spencer Thomason wrote:
Hello,
Any chance of getting this fix back ported to 3.2 branch?
Thanks,
Spencer
On Sep 16, 2012, at 2:58 AM, Spencer Thomason wrote:
Hi
Hello,
Any chance of getting this fix back ported to 3.2 branch?
Thanks,
Spencer
On Sep 16, 2012, at 2:58 AM, Spencer Thomason wrote:
> Hi Andrew,
>
> Thanks for the info. Yes that seems to fix the problem.
>
> Best regards,
>
> Spencer
>
>
>
> On 15.09.2012 14:42, Andrew Pogrebennyk
Hi Andrew,
Thanks for the info. Yes that seems to fix the
problem.
Best regards,
Spencer
On 15.09.2012 14:42, Andrew
Pogrebennyk wrote:
> Hello Spencer,
>
> actually double quotes are
not allowed in URI parameter. In the BNF
> grammar the allowed chars in
the "unreserved" definition
Hello Spencer,
actually double quotes are not allowed in URI parameter. In the BNF
grammar the allowed chars in the "unreserved" definition are "alphanum"
and "mark", where "mark" is only "-" / "_" / "." / "!" / "~"
/ "*" / "'" / "(" / ")" ).
This is already fixed in 3.3.0 if I am not mistaken, p
I see. FS complains about no transport protocol and gives a 503 with a header
like that. Shouldn't they default to UDP in the absence of a transport
parameter? It seems they are not honoring the quotes.
In this setup Kamailio handles NAT traversal and forwards the registers to
Freeswitch. T
Spencer Thomason writes:
> I'm forwarding registrations to Freeswitch and adding a Path header
> using add_path_received() for endpoints behind NAT. When TCP is used,
> this results in a header like this:
> Path:
>
> Freeswitch doesn't like the transport protocol inside the quotations
> and re
Hello,
I'm forwarding registrations to Freeswitch and adding a Path header using
add_path_received() for endpoints behind NAT. When TCP is used, this results
in a header like this:
Path:
Freeswitch doesn't like the transport protocol inside the quotations and
refuses to route a call to the re
