[Spce-user] Multiple SIP Interfaces Peering Problem

[Andrew Pogrebennyk]

1) RTFM:) I sent you the link, did you check it:
https://www.sipwise.org/doc/mr3.8.4/spce/ar01s05.html#_extra_sip_listening_ports
?
2) Please keep the list address in cc, private emails will be ignored.

On 12/02/2015 03:09 PM, afshin afzali wrote:
> Hi Andrew,
> 
> Thanks for your reply. This is my network configuration:
> 
> ---
> hosts:
>   self:
>     dbnode: 1
>     eth0:
>       ip: 10.200.251.178
>       netmask: 255.255.255.224
>       type:
>         - web_ext
>         - sip_ext
>         - rtp_ext
>         - ssh_ext
>         - web_int
>     eth1:
>       ip: 10.200.253.57
>       netmask: 255.255.255.192
>       type:
>         - sip_ext
>     eth2:
>       ip: 10.200.253.121
>       netmask: 255.255.255.192
>       type:
>         - rtp_ext
>     interfaces:
>       - lo
>       - eth0
>       - eth1
>       - eth2
>     lo:
>       cluster_sets:
>         - default
>       ip: 127.0.0.1
>       netmask: 255.255.255.0
>       shared_ip: []
>       shared_v6ip: []
>       type:
>         - sip_int
>         - ha_int
>         - aux_ext
>       v6ip: '::1'
>     role:
>       - proxy
>       - lb
>       - mgmt
>       - rtp
>       - db
> 
> 
> On Wed, Dec 2, 2015 at 5:16 PM, Andrew Pogrebennyk
> <apogrebennyk at sipwise.com <mailto:apogrebennyk at sipwise.com>> wrote:
> 
>     Hi,
>     have you configured kamailio to listen on eth1 yet?
>     Have you set the outbound_socket peer preference?
>     Check the CE handbook:
>     https://www.sipwise.org/doc/mr3.8.4/spce/ar01s05.html#_extra_sip_listening_ports
> 
>     Regards,
>     Andrew
> 
>     On 12/02/2015 10:04 AM, afshin afzali wrote:
>     > Hi Everyone,
>     > Actually I've already done SIP peering in NGCP with just one SIP
>     > interface (eth0). Today I am struggling with this in a new topology in
>     > which I have two different SIP interfaces from two different subnet
>     > (eth0 & eth1). My client connects to SIP interface on eth0 and my SIP
>     > peer server is accessible via eth1. I have configured IP routing
>     > properly as I can ping the peer server. When I call a number which
>     > matches the peer group matching rule, system tries to route the
>     call to
>     > the peer server. Seems that instead of using second SIP interface
>     (eth1)
>     > it uses first SIP interface (eth0) to reach the peer server. I have
>     > attached kamailio log files. It seems something missing in my
>     > configuration. Appreciate all comments.
>     >
>     > Cheers,
>     > - Afshin
> 
>