[Freeswitch-users] Transport parameters when using RFC3327 Path and fs_path

[Richard Brady]

Hi folks

I have FreeSWITCH running behind Kamailio, which acts as a TCP (client
side) to UDP (FreeSWITCH side) bridge.

The client registers with a binding like:

Contact: <sip:1010 at 192.168.1.228:32204;transport=tcp>

and the Kamailio server is adding a Path header as follows:

Path: <sip:10.1.1.1;lr>

FreeSWITCH stores this as:

Contact:<sip:1010 at 192.168.1.228:32204;transport=tcp;fs_path=%3Csip%3A10.1.1.1%3Blr%3E>

But then when originating /bridging a call to this user, I get:

[DEBUG] sofia_glue.c:2055 sip:10.1.1.1;lr;transport=tcp Setting proxy
route to sofia/internal/sip:1010 at 192.168.1.228:32204

which indicates that the wrong transport is being used.

If I add transport=udp to the Path header generated by Kamailio, the
correct transport is used. However the Path URI, by not including a
transport parameter, implicitly specifies UDP.

Am I doing something wrong or could this possibly be a bug?

Regards,
Richard