Question in regards to Viking phone setup and ports...

[Erik Nathe]

Here are the details:
We have 3cx running on a dedicated google cloud server instance. My boss has VIKING VOIP phone (the problem phone) and 2 other phones that we are trying to get to work consistently. When the VIKING is registered, none of the phones work.. when it is not registered, the other 2 phones work fine.

Here is what I am thinking:
The Viking's default local SIP port is 5060... Unfortunately I cannot change it from the 3CX portal, and have to do it from the phones gui... My boss has been trying to change the port by adding to the end of the 3cx servers public IP (IE:In the phons settings "Server: 123.456.12:5066"). Though shouldn't we be associated the port with the phones static IP and not the 3cx server?

 

[AWS2P]

Hi;
perhaps you should start here
https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

Sorry what is viking ? a sip deskphone?

 

[leejor]

I'm going to assume that all the phones are using STUN, behind the same router...correct? That being the case, each will have to be assigned a unique LOCAL port number, as a start. Even then, depending on the local router, there can be audio issues unless you dedicate (and forward), a range of audio ports to each set.

 

[Erik Nathe]

My apologies, here you are.

3CX Version: 16.0.910
Server OS: Debian 9
Is the 3CX Server Hosted and where? Google Cloud server
IP Phone Make/Model/Firmware: Unfortunately the only info I have is that it is a VOIP gate phone manufactured by Viking… I REALLY wish I could provide more info than that.
Provisioning Method: STUN Direct
Trunk Provider: Nexvortex
Has the Firewall Checker passed: YES
Are custom Phone Templates being used: NO


Also the devices at his house are NOT being provision by 3cx... which makes this all a bigger pain.

@leejor so he would need to forward the audio ports on his gateway? I cannot assign audio ports to his phones because they are not provisioned by 3CX and the Viking has no settings for audio ports...

 

[AWS2P]

Sorry i'm not positive, but in your case, unsupported device + unknown model and features+ stun mode = very very poor chances it works

take a lot of aspirin to prevent headaches if you have time to spend on this

What can be worst scenario to hope this to work ?

 

[Erik Nathe]

Sorry i'm not positive, but in your case, unsupported device + unknown model and features+ stun mode = very very poor chances it works

take a lot of aspirin to prevent headaches if you have time to spend on this

What can be worst scenario to hope this to work ?

I would agree... unfortunately my boss will not accept that as an answer, as it worked just fine on 3cx V15...

 

[leejor]

You may want to condsider using a Raspberry Pi SBC at that location. It isn't expensive, and you can manually provision the sets to "point to' the IP of the SBC, then let it handle all the dirty work. All sets can then use the same local port (5060) and audio ports shouldn't be an issue.

 

[AWS2P]

So do i need to understand PBX has recently been upgraded to V16 and since your Viking is not working ?
Nothing else changed else than upgrade to V16?