[Spce-user] Peer registration comming from wrong interface
Matthew Reading
mr at vobi.com.au
Tue May 15 07:22:34 EDT 2018
If I have understood you correctly...
Just add a static route on the OS for that network address to go out the right NIC.
Two routes.
No default gateway on voice nic.
Default gateway on public internet nic.
Sent from BlueMail
On May 15, 2018, 7:07 PM, at 7:07 PM, Henk <henk at voipdigit.nl> 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
>> <mailto: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 list
>>> Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
>>> https://lists.sipwise.com/listinfo/spce-user
>>> <https://lists.sipwise.com/listinfo/spce-user>
>>
>>
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
>> https://lists.sipwise.com/listinfo/spce-user
>> <https://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/pipermail/spce-user_lists.sipwise.com/attachments/20180515/b27ce061/attachment-0001.html>
More information about the Spce-user
mailing list