Snom Phone Book

[Rmn3]

Hi There,

we are using Snom Phones and of course, the 3cx.

After i´ve changed a extension in the 3cx, i´ve changed the name, it wont update the name of this extension in the snom global phonebook.

What can i do?

Best Regards

 

[VasilisV_3CX]

Hi @Rmn3,

Have you tried reprovisioning the phone via the Phones section? It will update the phonebook.

 

[Rmn3]

Hi,

i´ve set the option reprovision the phone when start and i´ve started my phone again, but it stays the same.

 

[VasilisV_3CX]

Hi again @Rmn3,

What model Snom IP phone are you using?

What version of the PBX are you running?

If you try manually reprovisioning the phone, does anything change?

 

[Rmn3]

Hi,

the snom M65,

we are using the 16.0.9

No, unfournately not, manually reprovisioning wont change anything.

 

[VasilisV_3CX]

Hi @Rmn3,

Ah okay, it's a DECT device, what base are you using?

 

[Rmn3]

the global phonebook ist locally saved, according to the snom master counter

 

[VasilisV_3CX]

Hi @Rmn3,

What base are you using?

 

[Rmn3]

How can i found out, which based is used in our company?

 

[Rmn3]

Base

 

[VasilisV_3CX]

Hi @Rmn3,

It'll be a device that looks similar to this. You can look at the model number on the back:

 

[Rmn3]

the global phonebook ist locally saved, according to the snom master counter

 

[Rmn3]

We are using a DECT-Chain. What do you need of it?

 

[JohnS_3CX]

Hi @Rmn3

- The M65 is a DECT handset.

- The handset is paired with a Base Station (or multiple if you have a multicell chain).

- The Base Station receives the phonebook from 3CX, and then gives it to the M65.

We need to learn what model of Base Station your chain is made of, and this will help us understand why the phonebook does not update. So please collect the following information, and when you come back with this we can see how we can help you:

- Model of Snom Base Station(s)
- Firmware version currently installed on the Base Stations
- Method of provisioning (3CX Mgmt. Console >> Advanced >> FXS/DECT page)
- Do you use a 3CX FQDN or a custom one?