Phones won't register

[webtipster]

Hi guys,

Got started with 3CX today. Install went smooth but ran into an issue registering phones.
Here's what I did: created a new VPS instance over at Vultr. Got my latest 3CX debian iso, ran the install, configurations, etc. Went into my admin console, added new extensions, added my Flowroute SIP trunks, all good.

Now I went to my Yealink T46G phone console and went to change the SIP server and account info and boom "Register Failed".

Went back into 3CX admin, changed provisioning method, tried IP interface, tried 3cx.us interface, nothing, same "register failed" message.

Back to 3CX admin, extension, options, and unchecked the box for " Disallow use of extension outside the LAN", still same "register failed".

Went back to T46G, did a factory reset, downloaded latest firmware, installed, rebooted, tried same things again, again "register failed".

Does anyone have any ideas what am I missing? I might have been starring at this thing too long and don't see it, someone shine some light please .

Thanks in advance guys!

 

[Saqqara]

How many the phones are being installed remotely at the same location, you have a few options which will push you down the correct installation route

1. Create a site to site vpn, and then configure the phones as local.

2. SBC - Install a SBC server locally - this handles all the SIP traffic back to the 3CX server. https://www.3cx.com/docs/3cx-tunnel-session-border-controller/ This is the solution for localations with many remote phones.

3. STUN - This is the more complicated setup as each phone needs a different sip port, range of rtp ports, fixed IP address of phone and port forwarding configured on the router protecting the phones. This solution is OK for a few phones, any more your best solution is installing a SBC server


Here is some reading on setting up the phones - https://www.3cx.com/sip-phones/yealink-t4-series/

 

[webtipster]

Thanks a bunch. I’ll try option 1 and 3 as you recommended being there’s only 3 phones remotely. If all fails I’ll try SBC. Any good guides for reference besides the 3cx one?

Thanks again!

How many the phones are being installed remotely at the same location, you have a few options which will push you down the correct installation route

1. Create a site to site vpn, and then configure the phones as local.

2. SBC - Install a SBC server locally - this handles all the SIP traffic back to the 3CX server. https://www.3cx.com/docs/3cx-tunnel-session-border-controller/ This is the solution for localations with many remote phones.

3. STUN - This is the more complicated setup as each phone needs a different sip port, range of rtp ports, fixed IP address of phone and port forwarding configured on the router protecting the phones. This solution is OK for a few phones, any more your best solution is installing a SBC server


Here is some reading on setting up the phones - https://www.3cx.com/sip-phones/yealink-t4-series/

 

[Alphabetic]

When you provision your phone in STUN you will see a message in 3CX event log saying something on the lines of "RPS successfully sent.."

Get that far so you know 3CX has sent the RPS request.

You shouldnt have to go in the Phone GUI to register this on STUN if the auto prov works (link posted earlier).

Enter your EXT # and Voicemail PIN to register the phone when prompted to.

 

[webtipster]

Boom I got it done using STUN mode and phones have provisioned successfully! Issue was disabling SIP ALG on the router/firewall!

I do have an issue now, when trying to make an outbound call, type in the number and it gives busy signal. If I try to use Chrome extension to make a call, it just hangs up instantly.

Went back to dashboard, under SIP trunks, Flowroute is green.

What am I missing to be able to dial-out? I'm sure I missed something...

Thanks again!

 

[Alphabetic]

Dial *777 to do echo test to confirm internal calls work. If it does, look at your outbound rules.

 

[webtipster]

*777 worked fine. Incoming calls work fine. Outgoing calls fail. Deleted outbound rules, and re-added, boom worked perfect!

Added "prepend" 1 to the outbound calling.

Last question, how do you add company name to the caller ID? Right now it uses the company number only with "unknown caller".

Thanks guys!

 

[AWS2P]

Last question, how do you add company name to the caller ID? Right now it uses the company number only with "unknown caller".

Not on 3CX but if possible on SIP provider side

 

[YiannisH_3CX]

I would recommend registering your number with Flowroute Cnam service so that when you call it will present your company name. It can be achieved through 3CX as well but Flowroute may not pass the name to the called party.