<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
yes, you're right. I am trying to take request from instance (5061) and send them out as if they came from instance (5060).<br>
I've tried using force_send_socket( ) and/or rewriteport( ) functions and still unable to resolve it.<br>
<br>
####### Global Parameters #########<br>
listen=udp:192.168.1.1:5060<br>
listen=udp:192.168.1.1:5061<br>
<br>
####### Routing Logic ########<br>
force_send_socket(192.168.1.1:5060);<br>
("5060")<br><br>
Thanks,<br>
R<br><br><br><br>> Date: Tue, 27 Jul 2010 17:32:15 -0400<br>> Subject: Re: [SR-Users] multiple instances on different ports<br>> From: geoffreymina@gmail.com<br>> To: uriel.rozenbaum@gmail.com; alex-rsm@hotmail.com; users@lists.kamailio.org<br>> <br>> I believe the issue is that he is trying to take requests on one<br>> kamailio instance (5061) and send them out as if they came from the<br>> other kamailio instance (5060) to 'normalize' the responses back<br>> through just 5060.<br>> <br>> Either I am not interprting correctly or there is a major design flaw here.<br>> <br>> On 7/27/10, Uriel Rozenbaum <uriel.rozenbaum@gmail.com> wrote:<br>> > Hi,<br>> ><br>> > As it is stated on the documentation, force_send_socket() can only<br>> > take a listening interface as an argument.<br>> ><br>> > Try adding<br>> > listen=udp:192.168.1.111:5060<br>> ><br>> > Cheers,<br>> > Uriel<br>> ><br>> > On Tue, Jul 27, 2010 at 10:51 AM, Alex rsm <alex-rsm@hotmail.com> wrote:<br>> >> Hi,<br>> >><br>> >> Thanks for your response: When using the function you suggested:<br>> >><br>> >> listen=udp:192.168.1.111:5061<br>> >> listen=udp:192.168.1.111:5062<br>> >> .....<br>> >><br>> >> force_send_socket(192.168.1.111:5060);<br>> >> ...<br>> >><br>> >> I am getting the following error message:<br>> >><br>> >> Jul 27 09:45:07 lab-openser01 /usr/sbin/openser[8861]:<br>> >> ERROR:core:fix_actions: bad force_send_socket argument:<br>> >> 209.16.123.111:5060<br>> >> (ser doesn't listen on it)<br>> >> Jul 27 09:45:07 lab-openser01 /usr/sbin/openser[8861]:<br>> >> ERROR:core:fix_actions: fixing failed (code=-476) at cfg line 332<br>> >> Jul 27 09:45:07 lab-openser01 /usr/sbin/openser[8861]: ERROR:core:main:<br>> >> failed to fix configuration with err code -476<br>> >><br>> >><br>> >> As I mentioned I am trying to run multiple instances of openser with diff<br>> >> ports and proxy all traffic coming from diff ports to a fix port 5060.<br>> >> Domains are set within a perl script.<br>> >><br>> >><br>> >> PS: I am using openser 1.3 release within ubuntu OS.<br>> >><br>> >> Thanks,<br>> >> R<br>> >><br>> >><br>> >><br>> >>> Date: Mon, 26 Jul 2010 17:55:54 -0300<br>> >>> From: uriel.rozenbaum@gmail.com<br>> >>> To: rob1485@gmail.com<br>> >>> CC: users@lists.kamailio.org<br>> >>> Subject: Re: [SR-Users] multiple instances on different ports<br>> >>><br>> >>> Hi,<br>> >>><br>> >>> try using force_send_socket but you'll have to declare the socket with<br>> >>> 5060 as well<br>> >>><br>> >>><br>> >>> http://www.kamailio.org/dokuwiki/doku.php/core-cookbook:3.0.x#force_send_socket<br>> >>><br>> >>> Cheers,<br>> >>> Uriel<br>> >>><br>> >>> On Mon, Jul 26, 2010 at 5:38 PM, Robert R <rob1485@gmail.com> wrote:<br>> >>> > Hi,<br>> >>> ><br>> >>> > I am trying to run multiple different instances of openser on the same<br>> >>> > server using different ports.<br>> >>> > Regardless of receiving INVITE on any of the ports (5061, 5062, ...) I<br>> >>> > want<br>> >>> > openser always to proxy the message to port 5060.<br>> >>> ><br>> >>> > invite:5061 ---> openser --> invite:5060<br>> >>> > invite:5062 ---> openser --> invite:5060<br>> >>> ><br>> >>> > By adding two listen ports as follow, openser sends the traffic to the<br>> >>> > same<br>> >>> > outgoing port as the incoming port:<br>> >>> ><br>> >>> > listen=udp:209.16.123.160:5061<br>> >>> > listen=udp:209.16.123.160:5062<br>> >>> ><br>> >>> > Is there a way to hard code the outgoing port? or I should overwrite<br>> >>> > the<br>> >>> > port?<br>> >>> ><br>> >>> > Thanks,<br>> >>> > R<br>> >>> ><br>> >>> ><br>> >>> ><br>> >>> > _______________________________________________<br>> >>> > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>> >>> > sr-users@lists.sip-router.org<br>> >>> > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users<br>> >>> ><br>> >>> ><br>> >>><br>> >>> _______________________________________________<br>> >>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>> >>> sr-users@lists.sip-router.org<br>> >>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users<br>> >><br>> >> ________________________________<br>> >> Hotmail has tools for the New Busy. Search, chat and e-mail from your<br>> >> inbox.<br>> >> Learn more.<br>> ><br>> > _______________________________________________<br>> > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>> > sr-users@lists.sip-router.org<br>> > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users<br>> ><br>> <br>> -- <br>> Sent from my mobile device<br> <br /><hr />Hotmail is redefining busy with tools for the New Busy. Get more from your inbox. <a href='http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_2' target='_new'>See how.</a></body>
</html>