This comment from the opensips mailing list archive may help with the redundancy setup.
> 2) Set ip_nonlocal_bind via sysctl, which will allow you to bind to an > interface even if it's not available on that host. You can have a hot > standby host this way (on the virtual address), because it will start > getting messages as soon as you update the routing. Just bind to the > address you want instead of 0.0.0.0. And the message size is probably the result of via headers being added as the messages loop. Are you capturing on the loopback interface as well? Richard On Apr 27, 2010, at 11:10 AM, Bogdan-Andrei Iancu wrote: > Hi Carmelo, > > Carmelo D wrote: >> Hi all, >> >> I'm working with the dialog module, and have a problem with it. >> If I bind Opensips on the physical address it works fine, but if I >> bind it on the 0.0.0.0 address (I use it for redundancy purpose), it >> doesn't work fine. >> > Opensips does not support binding on 0.0.0.0 - it has to know from the > beginning the exact set of interfaces. >> In particular I get a message that the ACK and the BYE messages are >> too big (bigger than 2048 byte), but actually with wireshark I can see >> that they have a size of about 500 byte! >> > UDP ? > > Regards, > Bogdan >> any idea on how can I solve this problem? >> >> Thanks in advance. >> >> _______________________________________________ >> Users mailing list >> Users@lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> > > > -- > Bogdan-Andrei Iancu > www.voice-system.ro > > > _______________________________________________ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users _______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
