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. This works: Path: sip:a.a.a.a:5070;lr;received="sip:b.b.b.b:5185;transport=tcp";transport=udp
This does not: Path: sip:a.a.a.a:5070;lr;received="sip:b.b.b.b:5185;transport=tcp"
Spencer
On Sep 15, 2012, at 1:18 AM, Juha Heinanen wrote:
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: sip:a.a.a.a:5070;lr;received="sip:b.b.b.b:35430;transport=tcp"
Freeswitch doesn't like the transport protocol inside the quotations and refuses to route a call to the registered user.
Constructing the header manually without the quotes such as: append_hf("Path: sip:$Ri:$Rp;lr;received=sip:$si:$sp;transport=$pr\r\n"); solves the problem.
Is there a reason for the quotes?
without the quotes ;transport=tcp would become param of the path uri.
-- juha
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users