FYI, I have the following setup without any problems (at least no
problems on the server side, just buggy clients ;-)
2 Kamailio in active-active setup. Each Kamailio listens to the
"dedicated" IP address and the "virtual" IP by using ip_nonlocal_bind.
Virtual IP is managed by Pacemaker (I'm not using an OCF resource file
for kamailio, only the init-script).
Communication between Kamailio and back-end servers also uses the
virtual IP address.
Kamailio uses the dedicated IP as default IP (first "listen" directive).
mhomed=0
REGISTERs are replicated between the Kamailios. Is is the only part
where the proxies use their dedicated IP address (so I can easily detect
replicated REGISTERs). Therefore I call
force_send_socket(IPADDRESS_MYSELF:5060); before
forward("IPADDRESS_OTHERNODE");
regards
Klaus
On 29.03.2011 11:31, Asgaroth wrote:
Hi All,
I'm trying to setup an active/passive proxy instance with kamailio
3.1.2. I'm using ucarp (www.ucarp.org) to provide the floating ip
addresses. I have installed and configured ucarp and it appears to be
working as expected.
I have configured kamailio on both systems to be online all the time
(using the net.ipv4.ip_nonlocal_bind kernel parameter on the "standby"
server). I have configured kamailio with the listen parameter to be
listening on the floating ip addresses only.
The problem now is that kamailio uses the inbound interface as the
outbound socket for messages (I think this is the default, expected,
behaviour).
If I enable the "mhomed" parameter then I get the following error:
ERROR:<core> [forward.c:218]: ERROR: get_out_socket: no socket found
ERROR:<core> [forward.c:572]: forward_req: ERROR: cannot forward to af
2, proto 1 no corresponding listening socket ERROR: sl [sl_funcs.c:282]:
ERROR: sl_reply_error used: I'm terribly sorry, server error occurred (7/SL)
I had a look around on the docuwiki and I found $fs. Would I need to
force the outbound socket for each message in this case, or do I have a
simple comfiguration issue?
Any thoughts/comments would be greatly appreciated.
Thanks
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hi All,
I'm trying to setup an active/passive proxy instance with kamailio
3.1.2. I'm using ucarp (www.ucarp.org) to provide the floating ip
addresses. I have installed and configured ucarp and it appears to be
working as expected.
I have configured kamailio on both systems to be online all the time
(using the net.ipv4.ip_nonlocal_bind kernel parameter on the "standby"
server). I have configured kamailio with the listen parameter to be
listening on the floating ip addresses only.
The problem now is that kamailio uses the inbound interface as the
outbound socket for messages (I think this is the default, expected,
behaviour).
If I enable the "mhomed" parameter then I get the following error:
ERROR:<core> [forward.c:218]: ERROR: get_out_socket: no socket found
ERROR:<core> [forward.c:572]: forward_req: ERROR: cannot forward to af
2, proto 1 no corresponding listening socket ERROR: sl [sl_funcs.c:282]:
ERROR: sl_reply_error used: I'm terribly sorry, server error occurred (7/SL)
I had a look around on the docuwiki and I found $fs. Would I need to
force the outbound socket for each message in this case, or do I have a
simple comfiguration issue?
Any thoughts/comments would be greatly appreciated.
Thanks
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
