[Spce-user] Peer registration comming from wrong ipaddress

[Daniel Grotti]

Hi,
what are your extra_sockets? and what is the outbound_socket you have 
set in your peer preferences?

Daniel


On 05/28/2018 10:29 PM, Chris Hoffmann wrote:
> Hi Andrew,
>
> this is my reg_agent.conf.customtt.tt2:
>
> domain=218.101.10.135
> user=039413170
> pwd=xxxxxxxx
> proxy=sip:[% sip_lb_ips.0 %]:[% kamailio.lb.port %]
> [% IF sip_adv_ips.size -%]
> contact=sip:[% sip_adv_ips.0 %]:[% kamailio.lb.port %]
> [% ELSE -%]
> contact=sip:[% sip_ext_ips.0 %]:[% kamailio.lb.port %]
> [% END %]
>
> I have not made any changes to specify the interface.
>
> I have changed sems.db_reg_agent.fetch_extra_sockets_from_peer is set 
> to 'yes'. and run ngcpcfg apply ',change sems option' then rebooted. 
> no change.
>
> The registration message is going out the correct interface, with the 
> wrong source address.
>
> My interfaces:
>
>
> eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
>         inet 192.168.x.30  netmask 255.255.255.0 broadcast 192.168.152.255
>         inet6 fe80::250:56ff:fe92:11c4  prefixlen 64 scopeid 0x20<link>
>         ether 00:x:x:92:11:c4  txqueuelen 1000 (Ethernet)
>
> eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
>         inet 103.37.37.211  netmask 255.255.255.240 broadcast 
> 103.242.37.223
>         inet6 fe80::250:56ff:fe92:7da5  prefixlen 64 scopeid 0x20<link>
>         ether 00:x:x:92:7d:a5  txqueuelen 1000 (Ethernet)
>
> eth2: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
>         inet 203.x.180.42  netmask 255.255.255.252 broadcast 
> 203.167.180.43
>         ether 00:xx:56:92:06:c1  txqueuelen 1000 (Ethernet)
>
> eth3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
>         inet 203.x.154.94  netmask 255.255.255.252 broadcast 
> 203.167.154.95
>         inet6 fe80::250:56ff:fe92:4ff3  prefixlen 64 scopeid 0x20<link>
>         ether 00:xx:56:92:4f:f3  txqueuelen 1000 (Ethernet)
>
> lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
>         inet 127.0.0.1  netmask 255.0.0.0
>         inet6 ::1  prefixlen 128  scopeid 0x10<host>
>         loop  txqueuelen 1  (Local Loopback)
>
>
> My routes:
>
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    
> Use Iface
> default         103.242.37.209  0.0.0.0         UG    0     0        0 
> eth1
> 103.242.37.208  0.0.0.0         255.255.255.240 U     0     0        0 
> eth1
> 192.168.x.0   0.0.0.0         255.255.255.0   U     0   0        0 eth0
> 203.167.x.92  0.0.0.0         255.255.255.252 U     0   0        0 eth3
> 203.167.x.40  0.0.0.0         255.255.255.252 U     0   0        0 eth2
> 218.101.10.135  203-167-154-93. 255.255.255.255 UGH   0     0        0 
> eth3
>
> The traffic departs the correct interace, eth3 but has a source 
> addresss of eth1.
>
>
>
>
> Any help would be much appricated.
>
>
> On Tue, May 29, 2018 at 12:49 AM, Andrew Pogrebennyk 
> <apogrebennyk at sipwise.com <mailto:apogrebennyk at sipwise.com>> wrote:
>
>     On 05/16/2018 10:13 AM, Chris Hoffmann wrote:
>     > Hi,
>     >
>     > Version 6.1.
>     >
>     > I have also updated my misleading subject line. To clarify, the
>     > registration comes out the correct interface, but the capture
>     shows it
>     > coming from the wrong ip address. It shows it coming from my main
>     > external interface eth1.
>     >
>     > Thanks,
>     >
>     > Chris
>
>     Hi, check that the contact in your reg_agent.conf.customtt.tt2 is
>     pointing to the correct interface.
>     Also you should check that the config.yml key
>     sems.db_reg_agent.fetch_extra_sockets_from_peer is set to 'yes'.
>     This will make the kamailio-lb forward the registration from the
>     interface taken from contact header.
>
>     BR,
>     Andrew
>
>
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20180528/68e72cd3/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 42205 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20180528/68e72cd3/attachment-0001.png>