[Spce-user] Peer registration comming from wrong ipaddress

[Chris Hoffmann]

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

On Wed, 16 May 2018, 7:37 PM Daniel Grotti, <dgrotti at sipwise.com> wrote:

> please reply to the mailing list.
> Which version are you running?
>
> --
> Daniel Grotti
> Head of Customer Support
> Sipwise GmbH, Campus 21/Europaring F15
> AT-2345 Brunn am Gebirge
>
> Office: +43(0)130120332
> Email: dgrotti at sipwise.com
> Website: https://www.sipwise.com
>
> On 05/15/2018 10:26 PM, Chris Hoffmann wrote:
>
> Morning Daniel,
>
> Yes I have done this and when sipwise trys to send a call to this peer it
> goes to the correct interface with the correct source address. Its just the
> sip registration which goes to the correct interface but with the wrong IP
> on source of the UDP packet. hope that makes sence.
>
> On Tue, May 15, 2018 at 11:24 PM, Daniel Grotti <dgrotti at sipwise.com>
> wrote:
>
>> Hi Chris,
>> have you added the "extra_socket:" in the config.yml, and then selected
>> the "outbound_socket" in the peer's preferences?
>> Please have a look at:
>> https://www.sipwise.com/doc/mr5.5.4/spce/ar01s12.html#extra-sip-rtp
>>
>> Cheers,
>>
>> --
>> Daniel Grotti
>> Head of Customer Support
>> Sipwise GmbH, Campus 21/Europaring F15
>> AT-2345 Brunn am Gebirge
>>
>> Office: +43(0)130120332
>> Email: dgrotti at sipwise.com
>> Website: https://www.sipwise.com
>>
>> On 05/15/2018 01:07 PM, Henk wrote:
>>
>> Hi Chris,
>> I didn't know you had multiple interfaces, so it seems you need an SPCE
>> expert on this (I'm just a normal user:-)).
>> You can check the generated configuration in
>> /etc/kamailio/lb/kamailio.cfg under *external interfaces* and *advertised
>> addresses* and see if it matches what you expected. Also not sure if
>> multiple interfaces are supported in SPCE.
>>
>> Best regards,
>>
>> Henk Plessius
>>
>> On 15-5-2018 12:48, Chris Hoffmann wrote:
>>
>> So after running:
>>
>>  ngcp-network --set-interface=eth3 --advertised-ip=x.x.x.94
>>
>> I then ran ngcpcfg apply 'made a change'
>>
>> Checking the captures this does not appear to have changed anything. The
>> registration is still showing the address of eth1 :(
>>
>> Have i missed anything?
>>
>>
>> Here is my network.yml
>>
>>
>> hosts:
>>   self:
>>     dbnode: '1'
>>     eth0:
>>       hwaddr: 00:50:56:92:xx:xx
>>       ip: 192.168.152.30
>>       netmask: 255.255.255.0
>>       type:
>>       - web_ext
>>       - ssh_ext
>>       - web_int
>>       - rtp_int_eth0
>>       - sip_ext_incoming
>>     eth1:
>>       ip: y.y.y.211
>>       netmask: 255.255.255.240
>>       type:
>>       - sip_ext
>>       - rtp_ext
>>       - web_ext
>>     eth2:
>>       ip: z.z.z.42
>>       netmask: 255.255.255.252
>>       type:
>>       - rtp_int_eth2
>>       - sip_ext_incoming
>>     eth3:
>>       advertised_ip:
>>       - x.x.x.94
>>       ip: x.x.x.94
>>       netmask: 255.255.255.252
>>       type:
>>       - rtp_int_eth3
>>       - sip_ext_incoming
>>     interfaces:
>>     - lo
>>     - eth0
>>     - eth1
>>     - eth2
>>     - eth3
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On Tue, May 15, 2018 at 6:49 PM, Henk <henk at voipdigit.nl> wrote:
>>
>>> Hi Chris,
>>>
>>> You can set-up an alias address for Kamailio like this:
>>>
>>> ngcp-network --set-interface=eth0 --advertised-ip=x.y.z.t
>>>
>>> After that just generate the configs again and it should work.
>>>
>>> Best regards,
>>>
>>> Henk Plessius
>>>
>>> VoipDigit
>>>
>>> On 14-5-2018 23:32, Chris Hoffmann wrote:
>>>
>>> Hi All,
>>>
>>> I have a new VoIP provider on a new pysical interface that requres me to
>>> do SIP registration. I have configured the details on the peer and set the
>>> details in reg_agent.conf.tt2.
>>>
>>> When i do a packet capture, i see the registration being sent out the
>>> correct interface, but from the wrong IP address (my primary interface IP
>>> is used). Is there any way i can set the socket for the registration?
>>>
>>> Thanks,
>>>
>>> Chris.
>>>
>>>
>>> _______________________________________________
>>> Spce-user mailing listSpce-user at lists.sipwise.comhttps://lists.sipwise.com/listinfo/spce-user
>>>
>>>
>>>
>>> _______________________________________________
>>> Spce-user mailing list
>>> Spce-user at lists.sipwise.com
>>> https://lists.sipwise.com/listinfo/spce-user
>>>
>>>
>>
>>
>>
>> _______________________________________________
>> Spce-user mailing listSpce-user at lists.sipwise.comhttps://lists.sipwise.com/listinfo/spce-user
>>
>>
>>
>> _______________________________________________
>> 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/mailman/private/spce-user_lists.sipwise.com/attachments/20180516/39e8bfb8/attachment.html>