Thanks so much Bogdan!
I do appreciate all your hard work!
Bill W
On 11/30/10 3:12 PM, Bogdan-Andrei Iancu wrote:
Hi Bill,
you can use t_local_replied(last) in failure route to see if the 408
was locally generated or was received. See:
http://www.opensips.org/html/docs/modules/1.6.x
, as they are coming from a port
other than 5060.
Hope this helps,
Bill
On 11/24/10 6:10 AM, Bogdan-Andrei Iancu wrote:
Bill W. wrote:
Hello Bogdan,
Okay I've been researching this more. I am not a programmer, but it
looks like get_out_socket and find_si in forward.c and socket_info.c are
just comparing
use the port= directive because I've got other services
running on 5060.
Thoughts? Thanks!
Bill
On 11/12/10 8:27 PM, Bill W wrote:
Hi Bogdan,
Thanks so much for explaining how interface selection works.
Unfortunately the other interfaces all have daemons listening on port
5060
doing the same, but 10.0.10.3
is used by default by kernel for reaching 10.0.10.xx network, simply use
10.0.10.3 for opensips also.
Regards,
Bogdan
Bill W wrote:
Hey Bogdan,
I think we're confusing two issues.
The first issue was when mhomed=0, it was trying to options ping the
internal interface
interface for reaching a private
IP.does look sane to me :)
Regards,
Bogdan
Bill W wrote:
Ahhh, I see what's going on.
Opensips is trying to probe from a different IP on that interface
instead of the IP alias opensips bound to.
For example, on the public interface I have IP 66.180.205.11
/10/2010 5:38 AM, Bogdan-Andrei Iancu wrote:
Hi Bill,
is your opensips actually listening (configured as listener in .cfg) on
a interface in the private network (where the probing needs to be done) ??
Regards,
Bogdan
Bill W wrote:
Hey Bogdan,
I enabled the mhomed=1 parameter, and now I'm
is the probing interval you configured ?
http://www.opensips.org/html/docs/modules/1.6.x/load_balancer.html#id250040
Could you test the attached patch ? (same as revision 7356 on trunk).
Regards,
Bogdan
Bill W. wrote:
Hello Bogdan,
This is how I mark the destination down:
failure_route[1
On 11/8/2010 6:05 AM, Bogdan-Andrei Iancu wrote:
Hi Bill,
as you have a multi interface system, have you tried to enable the
mhomed global parameter?
http://www.opensips.org/Resources/DocsCoreFcn16#toc60
Regards,
Bogdan
Bill W. wrote:
As an update, the load balancer probe appears
Hello everyone,
I've got an opensips-1.6.3-tls installation using multiple interfaces
and load balancing.
My internal interface is rfc1918 space and my external interface has
public IPs.
listen=udp:10.0.10.3:5060
listen=udp:66.180.205.3:5060
I have the following load_balancer configuration:
As an update, the load balancer probe appears to use the ip address
specified by the first listen= directive.
If I list the public IP first, then the probe tries to talk to the
internal IP from the external interface IP.
On 11/7/10 6:18 PM, Bill W. wrote:
Hello everyone,
I've got
and with this flag set, no more
pings are sent.
Regards,
Bogdan
Bill W wrote:
Hello Bogdan,
I'm experiencing the same problem as I did before, with the load
balancer not re-enabling a device marked down.
If I go into the database and set probe_mode = 2, it re-enables the device.
I'm currently
!
Bill
Bogdan-Andrei Iancu wrote:
Super! I uploaded the fix on SVN.
Thanks and regards,
Bogdan
Bill W wrote:
Hey Bogdan,
It looks like that fixed it. Thanks so much!
Bill
Bogdan-Andrei Iancu wrote:
Hi Bill,
Could you please try the attached patch? It seams
Hey Bogdan,
It looks like that fixed it. Thanks so much!
Bill
Bogdan-Andrei Iancu wrote:
Hi Bill,
Could you please try the attached patch? It seams that there was an
issue with the the probing values in the code. Let me know if the patch
does solves your problem and I will upload it
Many thanks!
Bogdan-Andrei Iancu wrote:
Hi Bill,
The Load Balancer module works only for calls; it does not work for
REGISTER request; for this , use the dispatcher module with the Round
Robin alg.
Regards,
Bogdan
___
Users mailing list
Greetings everyone,
What is the best way to do round robin load balancing with failover
for certain resource (message) types? Like REGISTER for example.
I am using opensips-1.6 in front of a cluster, so the only thing I
really need to keep track of are calls. I don't want to keep track of
15 matches
Mail list logo
