Dial Extension - No Name

[Snap.]

Dear All,

I have a new customer and have configured 8 extensions (100-108).

All extensions have an assigned Snom D715 handset with supported firmware of 10.1.46.16.

When dialling an extension internally, the name does not show of said extension - it just shows as the extension.

I couldn't find much on this other than the phone didn't have a phonebook on it, but was wondering how the phone would get this?

Thanks,

Alex.

 

[HRMNY]

Are the phones local, SBC, DirectSIP?
How did you provision the phones?

 

[Snap.]

Hi HRMNY, they are on Local LAN with the Interface of the Google Cloud (3CX URL).

The receiving call user sees the extension and name, but when the originating caller dials the extension and calls it does not show the name.

 

[JohnS_3CX]

Hi @Snap.

Exactly how did you provision these phones?

 

[Snap.]

Hi @JohnS_3CX,

Added phone via 3CX Admin Console, logged into the phone (Snom D715) and provisioned it with the URL - provisioning link.

Provisioning Method: Local LAN
Interface: xxx.3cx.co.uk (hosted in Google Cloud)

 

[JohnS_3CX]

Normally this device should be on firmware 10.1.46.16 and should also populate its own directory automatically if it was correctly provisioned.

Since you have a cloud PBX and these are essentially STUN phones, you will need to factory reset them and provision them according to our guide, because I think they are not properly configured at the moment

Please follow this guide here: https://www.3cx.com/sip-phones/snom-710-720-760/

 

[Snap.]

Okay thanks @JohnS_3CX, I guess they should be set-up as Direct SIP STUN - Remote?

So follow this part of it: Remote phones: Provision via RPS server

 

[JohnS_3CX]

Yes correct. Once you configure the extension, and press ok, you will see the Event log on the management console show that RPS was successfully sent for extension XXX.

You must now factory reset the phone and it will boot up and ask you for your user/pass which is the extension number and voicemail pin number.

Remeber to give unique, non-overlapping SIP and RTP ports to each phone (if you have more than 1 device) and also forward those ports on your office router/firewall so the phone can always reach the PBX reliably.

How many phones in total?

 

[Snap.]

Thank you, 8 phones in total.

 

[Snap.]

Just to clarify with the non-overlapping ports.

Phone 1:
Local SIP:5060
RTP S/E: 14000-14019

Phone 2:
Local SIP:5061
RTP S/E: 14020-14039

Are the RTP ports too wide?

 

[JohnS_3CX]

Looks good, they are not too wide. You can follow the same pattern for the rest of the phones.

By the way, since you have 8 phones, it will become a bit laborious to open ports for each and every device on the office firewall, so I would recommend to install a 3CX SBC which would remove the need for port management both on the extension settings and the office firewall. The SBC will also provide you with encryption, and you can easily provision the devices straight from the management console (you just select a new phone from the phones tab, and assign it to its extension. The rest is automatic)

Let me know if interested and I can assist you.

 

[Snap.]

Okay, cool thanks John.

SBC I knew we needed but things got changed very quickly and I was hoping to use the DirectSIP until this came a problem. Bad way to do it I know.

Do you suggest any particular device to be an SBC? Would like to hear more about it!

I really do appreciate your help so much.

 

[Saqqara]

Do you suggest any particular device to be an SBC? Would like to hear more about it!

Any windows 10 machine that is not being used for anything , else the cheapest option is Rasberry PI 3B+ (note the model number, cannot be PI 4)

https://www.3cx.com/docs/installing-pbx-raspberry-pi/

https://www.3cx.com/docs/3cx-tunnel-session-border-controller/#h.wrvwnh8912cq

 

[JohnS_3CX]

You can use a Raspberry Pi 3B+ model which can handle up to 50 extensions. It's small, affordable and easy to maintain https://www.3cx.com/docs/recommended-hardware-specifications-for-3cx/#h.az536dlhkp52

Alternatively, you can use an old laptop, or pc, or even run it on a VM if you have a local server that can run VMs. Small form factor PCs can also be used, the requirements are quite low.

Avoid using an office PC that belongs to a user though, you want a device that is on 24/7 and independent to ensure stability. It can run on both Debian and Windows (with Debian being the most stable/efficient solution)