11 Apr
2006
11 Apr
'06
6:16 p.m.
Hello,
Classic situation, overgrown asterisk and need to go openser for
load-balancing and failover reasons.
We want to do an incremental upgrade to openser, and for the moment we are
trying to use openser as a fancy router in front of asterisk.
I'm having a little problem with load-balancing the registration.
Clients are mostly behind NAT sending registration to openser. I'm using the
dispatcher module to load-balance it.
The registration is going from the client to the openser, openser is
forwarding it to asterisk. Asterisk replies to openser, and that's where I'm
stuck.
I want openser to forward the "TRYING" and "OK" response (and
obviously all
other responses) to the client, but can't seem to figure out how.
Can anybody point me in the right direction?
thanks
11 Apr
11 Apr
6:34 p.m.
Hi,
you do not have to do anything special for this - all replies will be
backward forwarded by openser by default.
regards,
bogdan
Benjamin Lawetz wrote:
Hello,
Classic situation, overgrown asterisk and need to go openser for
load-balancing and failover reasons.
We want to do an incremental upgrade to openser, and for the moment we are
trying to use openser as a fancy router in front of asterisk.
I'm having a little problem with load-balancing the registration.
Clients are mostly behind NAT sending registration to openser. I'm using the
dispatcher module to load-balance it.
The registration is going from the client to the openser, openser is
forwarding it to asterisk. Asterisk replies to openser, and that's where I'm
stuck.
I want openser to forward the "TRYING" and "OK" response (and
obviously all
other responses) to the client, but can't seem to figure out how.
Can anybody point me in the right direction?
thanks
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
9:10 p.m.
Well then I must be doing something really wrong :-)
Because the packet sniffer shows me the packet getting back to the SER, but
not leaving it afterwards.
Unless my logic is not working properly. Here's my route section (very
simple, still in the learning stage)it should do the trick or am I way off
in left field?
route{
if (loose_route()) {
t_relay();
return;
}
xlog("SIP Request: method [$rm] from [$fu] to [$tu]\n");
record_route();
if (method == "REGISTER") {
xlog("SIP REGISTER: method [$rm] from [$fu] to [$tu]\n");
fix_nated_contact();
ds_select_dst("1","0");
xlog("REWROTE TO: [$du]");
forward(uri:host, uri:port);
}
t_relay();
}
Thanks for your help
Benjamin
-----Original Message-----
From: Bogdan-Andrei Iancu
Sent: April 11, 2006 12:34 PM
To: Benjamin
Cc: users(a)openser.org
Subject: Re: [Users] Forward response
Hi,
you do not have to do anything special for this - all replies will be
backward forwarded by openser by default.
regards,
bogdan
Benjamin Lawetz wrote:
Hello,
Classic situation, overgrown asterisk and need to go openser for
load-balancing and failover reasons.
We want to do an incremental upgrade to openser, and for the moment we
are trying to use openser as a fancy router in front of asterisk.
I'm having a little problem with load-balancing the registration.
Clients are mostly behind NAT sending registration to openser. I'm
using the dispatcher module to load-balance it.
The registration is going from the client to the openser, openser is
forwarding it to asterisk. Asterisk replies to openser, and that's
where I'm stuck.
I want openser to forward the "TRYING" and "OK" response (and
obviously
all other responses) to the client, but can't seem to figure out how.
Can anybody point me in the right direction?
thanks
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
9:30 p.m.
on a first look, see you do double forwarding - once stateless, via
forward, and second statefull via t_relay().
either place an exit after forward (and process statelessly the
REGISTERs), either remove the forward() and process statefully
everything via t_relay.
regards,
bogdan
Benjamin Lawetz wrote:
Well then I must be doing something really wrong :-)
Because the packet sniffer shows me the packet getting back to the SER, but
not leaving it afterwards.
Unless my logic is not working properly. Here's my route section (very
simple, still in the learning stage)it should do the trick or am I way off
in left field?
route{
if (loose_route()) {
t_relay();
return;
}
xlog("SIP Request: method [$rm] from [$fu] to [$tu]\n");
record_route();
if (method == "REGISTER") {
xlog("SIP REGISTER: method [$rm] from [$fu] to [$tu]\n");
fix_nated_contact();
ds_select_dst("1","0");
xlog("REWROTE TO: [$du]");
forward(uri:host, uri:port);
}
t_relay();
}
Thanks for your help
Benjamin
-----Original Message-----
From: Bogdan-Andrei Iancu
Sent: April 11, 2006 12:34 PM
To: Benjamin
Cc: users(a)openser.org
Subject: Re: [Users] Forward response
Hi,
you do not have to do anything special for this - all replies will be
backward forwarded by openser by default.
regards,
bogdan
Benjamin Lawetz wrote:
Hello,
Classic situation, overgrown asterisk and need to go openser for
load-balancing and failover reasons.
We want to do an incremental upgrade to openser, and for the moment we
are trying to use openser as a fancy router in front of asterisk.
I'm having a little problem with load-balancing the registration.
Clients are mostly behind NAT sending registration to openser. I'm
using the dispatcher module to load-balance it.
The registration is going from the client to the openser, openser is
forwarding it to asterisk. Asterisk replies to openser, and that's
where I'm stuck.
I want openser to forward the "TRYING" and "OK" response (and
obviously
all other responses) to the client, but can't seem to figure out how.
Can anybody point me in the right direction?
thanks
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
6811
days inactive
6811
days old
3 comments
2 participants
participants (2)
-
Benjamin Lawetz -
Bogdan-Andrei Iancu