Binding to IPv4 address

[lasersailing]

Hi

 

I have been setting up a new snomONE PBX today on a debian server. The server has multiple addresses mapped onto alias interfaces within the operating system. I have been in and configured Settings > ports > Bind to specific IP address (IPv4): 192.168.0.2

 

Im running 4.5.0.1075 Delta Aurigids

 

192.168.0.2 is one of the aliased IP's on the server but not the primary IP.

 

192.168.0.1 is the main IP of the server.

 

From looking at traffic flows the RTP traffic is being bound to the 192.168.0.2 address but any other traffic originating from the PBX is being originated at 192.168.0.1

 

I need all traffic to be originating from 192.168.0.2 and not just the RTP traffic.

 

Is there any way of doing this?

 

Thanks in advance

 

Richard

[Vodia PBX]

Binding to IP addresses is a good way to use multiple cores and at the same time allowing users to use the same port 5060 on different IP addresses. For TCP this is relatively easy, because TCP sticks to the local address that was used when connecting to the socket. This does solve a big problem as long as users can use TCP or TLS for SIP.

 

With SIP/UDP, things are more complicated. If you bind a socket to an IP address, the outbound traffic should actually also come from that IP address. Here it is important that the routing table (operating system level) has the necessary entries for that.

 

For media, the PBX does not bind to a specific IP address by default. However there is a settings called "Bind to specific IP address (IPv4)" where you can specify what IP address the PBX should bind RTP ports to.

The other workaround is to use different ports than 5060 for each instance. Ports can be "advertised" by DNS SRV if you use domain names. Then you don't even need multiple IP addresses.

[lasersailing]

Hi

 

Yes I have set the Bind to specific IP address but this only does it for the RTP traffic and not anything else. I need to be able to bind all of the other traffic to the same IP as well

 

Thanks

[Vodia PBX]

Oh other ports are much more flexible than rtp. you can use a list of space-separated addresses like "192.168.1.2:5060 12.23.34.45:5060 [::1]:5050" on SIP UDP, TCP, TLS and HTTP TCP, TLS and also on TFTP ports. It would read as "bind a socket to address 192.168.1.2 on port 5060, then another one on 12.23.34.45 port 5060 and another one on ::1 (the IPv6 loopback address) on port 5050. See http://wiki.snomone.com/index.php?title=Ports for some more information.