SBC raspberry, port 5001, FQDN, local host name.

[hansmarc]

Hi,

i am preparing a SBC with a raspberry pi.
Installationon the raspberry no problem but i can not connect on port 5001 on the remote pbx of my client to register the SBC with the key generated by 3CX.
I am using V16 patch 2 and the latest download of the raspberry iso image.

First i tought that it was a firewall or port forwarding problem on the pbx site. But everything is correct.
Because i still can not connect i used the cport program from nirsoft on the 3CX server and discovered a strange thing.
A lot of local address 127.0.0.1 entries in the cport table have as host local name with a FQDN from another client of us.

Example the FQDN in 3CX of our client is AAAA.3CX.BE, we verified ii in the management console.
What we see is that a lot of ports points to by example BBBB.3CX.BE that we used for another pbx of another client..
Both pbx servers use a different ip address and i confirm that the FQDN defined in 3CX of our client is AAAA.3CX.BE.

I suppose that the SBC can not connect because the FQDN is not the correct one on the pbx, it search for AAAA but the local port on the pbx is BBBB.

I searched on the pbx server with different tools if there is any trace of BBBB... even the registry but if found nothing.

Can someone explain this please.

(AAAA and BBBB are nicknames)

Bye
Hans

 

[cobaltit]

Having trouble fully understanding the issue so lets start with the basics. If you try pinging your 3CX FQDN from another location other than where the PBX is installed does it resolve correctly?

 

[Saqqara]

As above,

can you login 3cx management console remotely ?

have you tried to update the sbc software https://www.3cx.com/docs/3cx-tunnel-session-border-controller/#h.g5p2fzbi6onx

 

[JohnS_3CX]

Check your hosts file