Hi Daniel, Actually I see I need to go to 4.3 to use the ds_default_socket parameter. Will go to 4.3 and see how it goes. Thanks Jon modparam("dispatcher", "ds_default_socket", "udp:192.168.0.125:5060") From: hunter...@hotmail.com To: mico...@gmail.com; sr-users@lists.sip-router.org Date: Mon, 14 Mar 2016 15:59:51 +0000 Subject: Re: [SR-Users] Kamailio and UCARP with Multiple VIPs defined
Hi Daniel, Thanks for the reply, sorry I keep missing you ! :) I have added force_send_socket in the correct places now , and I can now make inbound/outbound calls are required. However with dispatcher, when Im trying to send SIP options pings to gateways defined, I see these errors; RROR: dispatcher [dispatch.c:2564]: ds_check_timer(): unable to ping [sip:10.70.0.72:5080]Mar 14 15:56:25 bt1proxy1 /usr/sbin/kamailio[26708]: ERROR: <core> [forward.c:218]: get_out_socket(): no socket foundMar 14 15:56:25 bt1proxy1 /usr/sbin/kamailio[26708]: ERROR: <core> [forward.c:220]: get_out_socket(): no corresponding socket found for(udp:10.70.0.72:5080)Mar 14 15:56:25 bt1proxy1 /usr/sbin/kamailio[26708]: ERROR: tm [ut.h:345]: uri2dst2(): no corresponding socket found for "10.70.0.72" af 2 (udp:10.70.0.72:5080)Mar 14 15:56:25 bt1proxy1 /usr/sbin/kamailio[26708]: ERROR: tm [uac.c:307]: t_uac_prepare(): t_uac: no socket found However this is only when the listening socket is the VIP, if I define the true private local address to listen on, dispatcher works nicely. Can you set force socket for dispatcher module when using probing? Thanks Jon Subject: Re: [SR-Users] Kamailio and UCARP with Multiple VIPs defined To: hunter...@hotmail.com; sr-users@lists.sip-router.org From: mico...@gmail.com Date: Tue, 8 Mar 2016 16:55:52 +0100 Hello, oh, forgot to follow up, as I read your response at some point. Are you doing force_send_socket() or $fs = ...? If yes, what is the socket value you are forcing? The log message said: Mar 1 20:04:35 bt1proxy1 /usr/sbin/kamailio[20372]: ERROR: <core> [forward.c:220]: get_out_socket(): no corresponding socket found for(udp:10.70.0.72:5080) The socket listen in the rpc command output is udp:10.70.0.75:5060. Cheers, Daniel On 08/03/16 11:29, Jonathan Hunter wrote: Hi Daniel, Did you have any thoughts on this or is it more ip routing related or ucarp configuration on the server itself? Looks like kamailio has it as a listening socket. Thanks Jon From: hunter...@hotmail.com To: mico...@gmail.com; sr-users@lists.sip-router.org Date: Fri, 4 Mar 2016 12:31:29 +0000 Subject: Re: [SR-Users] Kamailio and UCARP with Multiple VIPs defined Hi Daniel, Thanks for the reply. Yes its listed, however I see mhomed set to no? however I have defined as on. socket: { proto: udp address: 10.70.0.75 ipaddress: 10.70.0.75 proto: 5060 mcast: no mhomed: no } ERROR: tm [ut.h:345]: uri2dst2(): no corresponding socket found for "10.70.0.73" af 2 (udp:10.70.0.73:5080) Mar 4 12:28:43 bt1proxy1 /usr/sbin/kamailio[7264]: ERROR: tm [t_fwd.c:522]: prepare_new_uac(): ERROR: can't fwd to af 2, proto 1 (no corresponding listening socket) Mar 4 12:28:43 bt1proxy1 /usr/sbin/kamailio[7264]: ERROR: tm [t_fwd.c:1779]: t_forward_nonack(): ERROR: t_forward_nonack: failure to add branches Mar 4 12:28:43 bt1proxy1 /usr/sbin/kamailio[7264]: ERROR: sl [sl_funcs.c:387]: sl_reply_error(): ERROR: sl_reply_error used: I'm terribly sorry, server error occurred (1/SL) Am I missing something? Thanks Jon To: sr-users@lists.sip-router.org From: mico...@gmail.com Date: Wed, 2 Mar 2016 12:10:32 +0100 Subject: Re: [SR-Users] Kamailio and UCARP with Multiple VIPs defined Hello, can you see if the socket lists includes the IP address giving problems? Use the command: kamcmd core.sockets_list Cheers, Daniel On 02/03/16 10:14, Jonathan Hunter wrote: Hi Guys, Using Centos 6.7, kamailio 4.2 and Ucarp I am testing multiple VIPs on the same server and having some issues. I have ucarp running, with 1 Public and 1 Private VIP defined, and both are pingable and failover in a cluster. The Public is for Subscribers to Register with, and the Private for Communication to the Asterisk media servers behind it. My problem is kamailio when started states its listening on both the VIPS, however when I try and force_socket over the Private IP address, it states ERROR: <core> [forward.c:218]: get_out_socket(): no socket found Mar 1 20:04:35 bt1proxy1 /usr/sbin/kamailio[20372]: ERROR: <core> [forward.c:220]: get_out_socket(): no corresponding socket found for(udp:10.70.0.72:5080) Mar 1 20:04:35 bt1proxy1 /usr/sbin/kamailio[20372]: ERROR: tm [t_fwd.c:520]: prepare_new_uac(): ERROR: can't fwd to af 2, proto 1 (no corresponding listening socket) This is when listening on the VIP which is 10.70.0.75 and I also look to force_socket out of this IP. It just doesnt work, however if I use the physical interface on the server, that being 10.70.0.70, it works fine and forwards requests on the Private LAN. I have added net.ipv4.ip_nonlocal_bind = 1 to sysctl.conf as well but no joy. If 1 VIP is defined I have no issue, its just with 2, has anyone had this issue before ? Any help would be great. Many thanks Jon _______________________________________________ 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 -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Berlin, March 7-9, 2016 - http://www.asipto.com _______________________________________________ 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 -- Daniel-Constantin Mierla http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com _______________________________________________ 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