In my attempt to resolve this problem I have also already come across that article. Unfortunately the t_relay function does not support variables as parameters, so I am not able to put in the full uri (e.g. tcp:70.232.x.x:55085) in the function. From this article (<a href="http://openser.org/pipermail/users/2010-March/011638.html">http://openser.org/pipermail/users/2010-March/011638.html</a>), it was suggested to rewrite the $du instead, however I don't believe it is possible to specify the protocol in the $du. <br>
<br>Regards,<br>William<br><br><br><div class="gmail_quote">On Tue, Jan 24, 2012 at 3:12 PM, <span dir="ltr"><<a href="mailto:duane.larson@gmail.com">duane.larson@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I did a search for "tcp" on Nabble's OpenSIPS section and just found this<br><br><a href="http://opensips-open-sip-server.1449251.n2.nabble.com/How-to-change-transport-protocol-of-R-URI-td6376471.html" target="_blank">http://opensips-open-sip-server.1449251.n2.nabble.com/How-to-change-transport-protocol-of-R-URI-td6376471.html</a><br>
<br>I would say you need to use t_relay() with parameters.<br><br>Hope that helps.<div class="HOEnZb"><div class="h5"><br><br><br>On , William Edwards <<a href="mailto:shadowapex@gmail.com" target="_blank">shadowapex@gmail.com</a>> wrote:<br>
> Hi,<br>> <br>> Thanks for your reply. I've looked into $fs, but I haven't been able to find any concise documentation about how I can use it to force the protocol to TCP. It's really unclear as to why OpenSIPS would be rewritting the TCP message to UDP in the first place. Is there no way to configure OpenSIPS to relay the message using the same protocol that it was received?<br>
> <br>> <br>> <br>> Regards,<br>> William<br>> <br>> <br>> On Tue, Jan 24, 2012 at 10:26 AM, <a href="mailto:duane.larson@gmail.com" target="_blank">duane.larson@gmail.com</a>> wrote:<br>> <br>
> <br>> Perhaps you need this somewhere in your script<br>> <br>> $fs Forced socket: <a href="http://www.opensips.org/Resources/DocsCoreVar16#toc38" target="_blank">http://www.opensips.org/Resources/DocsCoreVar16#toc38</a><br>
> <br>> <br>> <br>> <br>> <br>> <br>> On , William Edwards <a href="mailto:shadowapex@gmail.com" target="_blank">shadowapex@gmail.com</a>> wrote:<br>> > Hi,<br>> > <br>> > We currently have two Freeswitch boxes behind OpenSIPS which <br>
> <br>> <br>> > is acting as a SIP proxy/load balancer. Right now we're facing a problem<br>> > where OpenSIPS is rewriting incoming INVITE messages from our <br>> > Freeswitch servers from TCP to UDP. This, of course, is causing a <br>
> <br>> <br>> > problem because the client has registered using TCP, and incoming calls <br>> > are being sent to it over UDP.<br>> > <br>> > <br>> > This is an overview of what is happening:<br>
> > Freeswitch -TCP-> OpenSIPS -UDP-> Client UA (listening on TCP)<br>> <br>> <br>> > <br>> > We would like OpenSIPS to retain the original protocol that the message was received. Is there any way this is possible?<br>
> > <br>> > <br>> > <br>> > <br>> > My current OpenSIPS configuration can be found here:<br>> <br>> <br>> > <a href="http://pastebin.com/DSU1f2VS" target="_blank">http://pastebin.com/DSU1f2VS</a><br>
> > <br>> > Regards,<br>> > William<br>> ><br>> <br>> <br>> _______________________________________________<br>> <br>> Users mailing list<br>> <br>> <a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
> <br>> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>> <br>> <br>> <br>> <br>> <br>></div></div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br>