[SR-Users] Kamailio and UCARP with Multiple VIPs defined

[Jonathan Hunter]

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 branchesMar  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 at lists.sip-router.org
From: miconda at 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 at 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 at lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20160304/c80efdec/attachment.html>