SBC address cannot be edited?

[SlawekGL]

Hi,
our SBC has 2 network interfaces with static ip addresses. One in management network, and another one in the subnet, where the phones (yealink 4Xs) are. The dropdown field has only one option, which is pointing to the management network interface. Provisioning the phones is not possible anymore. Is there any option to override this parameter manually?

Best regards
Slawek Gluszczynski

 

[alanjmcfL]

Which SBC platform? Windows, Linux?

(Not that I know the answer, but it appeared to me at a very quick glance at netstat alone that the Windows SBC server listens on all interfaces.)

 

[SlawekGL]

Both 3CX and SBC are on Debian. Even if SBC listens on all interfaces, the phones can reach only the interface in phone subnet. We keep the networks separated. It is our security policy.

 

[bitn2]

You need to put the sbc in the same subnet like the phones.

 

[SlawekGL]

You need to put the sbc in the same subnet like the phones.

It is in the same subnet. And in another one also. Unfortunately the phones are getting as proxy the SBC NIC address from the other subnet.

 

[bitn2]

It is in the same subnet. And in another one also. Unfortunately the phones are getting as proxy the SBC NIC address from the other subnet.

That doesnt work as you allready said. The main Interface need to be in the same subnet.

 

[SlawekGL]

That doesnt work as you allready said. The main Interface need to be in the same subnet.

What is a definition of "main interface"? Why is it not possible to either choose from available interfaces, or just overwrite the settings e.g. with "Parameters" menu?

 

[SweetAction]

It's likely following whatever the OS sees as the first adapter.

In Windows it uses the interface metric. Debian has a binding order, but defaults to eth0.

 

[SlawekGL]

It's likely following whatever the OS sees as the first adapter.

Either this, or what NIC is used communicating with 3CX server (which means: what NIC is the default gateway for the OS). Both cases are not working for us.

In Windows it uses the interface metric. Debian has a binding order, but defaults to eth0.

I never heard about "binding order" in Debian. Could you please provide a link to any documentation?

 

[SweetAction]

Binding Order may be the wrong term. It's been a while that I had to do something like this, but here is some material for Debian 6 (I know, but it still applied on Debian 8) https://unix.stackexchange.com/ques...order-of-the-network-cards-eth1-eth0-on-linux

 

[SlawekGL]

Binding Order may be the wrong term. It's been a while that I had to do something like this, but here is some material for Debian 6 (I know, but it still applied on Debian 8) https://unix.stackexchange.com/ques...order-of-the-network-cards-eth1-eth0-on-linux

Thank you for the advice. I will try this way. It is very disappointing to have a software running flawless for years and becoming unuseful after regular update from the vendor.

 

[alanjmcfL]

The Windows' SBC config file has this line:

LocalSipAddr=0.0.0.0    # 0.0.0.0 to auto detect on start

I haven't tested it, nor whether the Linux SBC has that line... But hopefully setting that would influence the Listening address for the SBC...