2 Network Cards Settings in 3cx web interface

[sammykoolsys]

Hello everyone,

I just got this new sip connection from my ISP on a Fibre link.

I am having trouble getting it to work on my PBX.

Before I plugged it on my PBX I configured the IP on my pc and did a windows route and also used xlite to make and receive calls.

Now on my Debian PBX, I configured a Second nic and I can ping my proxy and I can ping the network it's on.

All that I do to configure 3cx to make or receive a call it just doesn't work. These are my settings

(below is an example of what I did

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
auto eth0
iface eth0 inet static
address 10.40.0.10 #default IP address of 3CX, can't be changed after installation
netmask 255.255.255.0
gateway 10.40.0.1
dns-nameservers 8.8.8.8

# second interface to SIP provider
allow-hotplug eth1
auto eth1
iface eth1 inet static
address 10.250.250.2 #IP address of LAN card, used for SIP provider (private LAN)
netmask 255.255.255.252

#static route to provider
up route add -net 213.226.61.0/24 gw 10.250.250.1 dev eth1

I am not sure what is it I am missing.
Registrar/Server/Gateway Hostname or IP is proxy IP provided by ISP
outbound Proxy same IP as gateway
IP base registration

under options
I have Select which IP to use in 'Contact' (SIP) and 'Connection'(SDP) fields I specify the ISP ip given to me.
I am not sure what else to try.

 

[cobaltit]

https://www.3cx.com/blog/docs/network-configurations-supported-3cx-phone-system/

 

[JohnS_3CX]

as @cobaltit notes above, that is a good article to get you started, especially the section:

Multiple internet gateways (used by ISPs that offer VoIP Services)

 

[sammykoolsys]

I've gone through most of the documents attached above. However, what I've noticed using Wireshark is that the traffic is been sent but nothing received.

 

[cobaltit]

Well that's not a 3CX issue then. You'd want to talk to your provider then as to why

 

[leejor]

Do you register with the provider? If so, could the IP, 3CX is sending, be the IP of the other Interface? Wireshark, or the Activity Log, may shed some light on what is happening.

 

[sammykoolsys]

What I've noticed is that there is no Audio gateway. So that can be my issue but is there a reason why I shouldn't put a gateway in my Debian server?

 

[JohnS_3CX]

The 2nd NIC must not have a network gateway, having 2 networks gateways on the same machine will cause a conflict for the purposes of a PBX.

As for audio gateways, that's something different. Let's refer to them as media servers instead (the machine that transfers RTP audio). Depending on the provider, you may not see one at all if they happen to use the same IP for registration and RTP audio.

As to whether one should appear, this will be seen in the SDP section of an invite sequence, the part responsible for telling each other where to send audio to/from. However, even if they do use a separate media server, you won't see it in the screenshot above because you never even got a reply to your invite.

The IPs in the screenshot do not appear to match the ones you defined earlier no?

 

[sammykoolsys]

See SIP Trunk details inline:

• Connect your SIP Gateway to Port 3/1 on the TMARC
• Address info:
  • IP: 10.236.27.42
  • SM: 255.255.255.252
  • GW: 10.236.27.41
  • SIP Proxy Address: 10.235.125.237
• 10 digit routing, e.g. 473xxxyyyy

The above shows the info from ISP.
There is no router after the TMARC. From the Tmarc it going directly to my PBX.

Below shows ip config & Route:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether ac:1f:6b:77:1e:14 brd ff:ff:ff:ff:ff:ff
inet 10.40.0.254/24 brd 10.40.0.255 scope global eno1
valid_lft forever preferred_lft forever
inet6 fe80::ae1f:6bff:fe77:1e14/64 scope link
valid_lft forever preferred_lft forever
3: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether ac:1f:6b:77:1e:15 brd ff:ff:ff:ff:ff:ff
inet 10.236.27.42/30 brd 10.236.27.43 scope global eno2
valid_lft forever preferred_lft forever
inet6 fe80::ae1f:6bff:fe77:1e15/64 scope link
valid_lft forever preferred_lft forever

Route:
default via 10.40.0.1 dev eno1 onlink
10.40.0.0/24 dev eno1 proto kernel scope link src 10.40.0.254
10.235.125.0/24 via 10.236.27.41 dev eno2

10.236.27.40/30 dev eno2 proto kernel scope link src 10.236.27.42

 

[sammykoolsys]

See attached screen with config inside 3cx