Hey Duane, Yes, I tried using force_send_socket, but it still sends the request as UDP instead of the original TCP. I noticed in the documentation it says that if the protocol doesn't match, the closest socket of the same protocol is used:
"If the protocol doesn't match (e.g. UDP message "forced" to a TCP socket) the closest socket of the same protocol is used. " Regards, William On Tue, Jan 24, 2012 at 4:14 PM, <[email protected]> wrote: > What about force_send_socket > http://www.opensips.org/Resources/DocsCoreFcn#toc111 > > Have you tried that yet. > > force_send_socket(udp:192.168.1.10:5060); > > > > > On , William Edwards <[email protected]> wrote: > > 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 ( > http://openser.org/pipermail/users/2010-March/011638.html), it was > suggested to rewrite the $du instead, however I don't believe it is > possible to specify the protocol in the $du. > > > > > > > > > > > > Regards, > > William > > > > > > On Tue, Jan 24, 2012 at 3:12 PM, [email protected]> wrote: > > > > > > > > > > I did a search for "tcp" on Nabble's OpenSIPS section and just found > this > > > > > http://opensips-open-sip-server.1449251.n2.nabble.com/How-to-change-transport-protocol-of-R-URI-td6376471.html > > > > > > > > > > > > I would say you need to use t_relay() with parameters. > > > > Hope that helps. > > > > > > On , William Edwards [email protected]> wrote: > > > > > > > > > > > Hi, > > > > > > 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? > > > > > > > > > > > > > > > > > > > > Regards, > > > William > > > > > > > > > On Tue, Jan 24, 2012 at 10:26 AM, [email protected]> wrote: > > > > > > > > > > > > > > > > > Perhaps you need this somewhere in your script > > > > > > $fs Forced socket: > http://www.opensips.org/Resources/DocsCoreVar16#toc38 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On , William Edwards [email protected]> wrote: > > > > Hi, > > > > > > > > We currently have two Freeswitch boxes behind OpenSIPS which > > > > > > > > > > > > > > > > > > is acting as a SIP proxy/load balancer. Right now we're facing a > problem > > > > where OpenSIPS is rewriting incoming INVITE messages from our > > > > Freeswitch servers from TCP to UDP. This, of course, is causing a > > > > > > > > > > > > > > > > > > problem because the client has registered using TCP, and incoming > calls > > > > are being sent to it over UDP. > > > > > > > > > > > > This is an overview of what is happening: > > > > > > > > > > > > Freeswitch -TCP-> OpenSIPS -UDP-> Client UA (listening on TCP) > > > > > > > > > > > > > > We would like OpenSIPS to retain the original protocol that the > message was received. Is there any way this is possible? > > > > > > > > > > > > > > > > > > > > > > > > > > > > My current OpenSIPS configuration can be found here: > > > > > > > > > > http://pastebin.com/DSU1f2VS > > > > > > > > > > > > > > > > Regards, > > > > William > > > > > > > > > > > > > _______________________________________________ > > > > > > Users mailing list > > > > > > [email protected] > > > > > > > > > > > > > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Users mailing list > > > > > > [email protected] > > > > > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > > > > > > > > > > > > > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > >
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
