phonebook.xml not updating

[proboscis]

Hi all, we're running v16 update 5. I've noticed that I've deleted extensions over the last few months and saw that they're still in the phonebook. We're running Grandstream phones. I see that the phonebook.xml and gs_phonebook.xml haven't updated since 6/13/2020, which is the last time the server was restarted. Anyone have any idea what could be happening? I'm hoping I don't have to to restart the server just for the update. Thanks

 

[proboscis]

Yes, adding a contact is kept by the pbx. Do you know if the xml file should be updated as well? Thanks

 

[AWS2P]

ok so now you succeeded in adding a contact, then, can you force a provisioning on a phone and see if you retrieve the new added contact ?

 

[proboscis]

ok, still no good. forced a provision and also re-downloaded phonebook, nothing new. thanks

 

[AWS2P]

Are you sure provisioning is really done? did you factory reset one phone and provisioned ?

 

[JohnS_3CX]

I'm confirming that if you add a new contact or extension, the xml should be updated immediately.

In Windows based installations it is found here:

C:\ProgramData\3CX\Instance1\Data\Http\Interface\provisioning\xxxxxxxx\gs_phonebook.xml

(where xxxxxx is your unique provisioning folder id)

 

[proboscis]

Are you sure provisioning is really done? did you factory reset one phone and provisioned ?

Yes, I did a factory reset and provision and it didn't update. Thanks

 

[proboscis]

I'm confirming that if you add a new contact or extension, the xml should be updated immediately.

In Windows based installations it is found here:

C:\ProgramData\3CX\Instance1\Data\Http\Interface\provisioning\xxxxxxxx\gs_phonebook.xml

(where xxxxxx is your unique provisioning folder id)

Thanks for confirming! This is where I think the problem is. The file only seems to update when the server is restarted, and even then, only the "modified date" is changed, not the contents of the file. New contacts are not added and old contacts are not removed from the file. Thanks

 

[AWS2P]

Sorry, I have no more idea for helping you trying to fix this.

 

[proboscis]

Sorry, I have no more idea for helping you trying to fix this.

That's OK, thanks for all your help anyway!

 

[JohnS_3CX]

In your Windows server, is there anything else running other than 3CX, or is it purely dedicated?

Do you run an antivirus for example or anything else that can control the permissions of programs to write to the disk?

 

[proboscis]

Hi John, the server is purely dedicated to 3CX. I disabled the anti-virus but no help. What I did notice, is that I could not edit the file without taking ownership of the file and giving my ID full control. Even though my ID already full control through inherited access. Thanks

 

[JohnS_3CX]

Ok make sure that no antivirus is running or anything else that can lock the file and prevent the system from using it.

Shut down all the 3CX service, then move the file outside of the 3CX folder.

Restart the services and see if the file is recreated by the PBX and if it will contain the correct info.

Do not try to take ownership of the file, this may mess with the ability of the PBX to update it, instead copy it out of the folder and read the contents there (or use Notepad++ in read-only mode)

 

[proboscis]

Ok, I'll have to find a time to take down the system. I added an extension and ran process monitor on it and saw a few things, it looks like (if I'm reading it right) 3cxmanagementconsole.exe did update the file successfully. But, the phonebook.xml file still doesn't show the new ext. I'm including screen shots. Thanks

 

[proboscis]

And now, looking at the log that I see in the process monitor, I'm seeing this:

 

[proboscis]

But now, also this:


Although I don't know what that .xml file is, or if it's even related. Thanks

 

[JohnS_3CX]

That's the main phonebook, and it appears like the system is denied full access to write.

If the file path you see there is indeed correct and exists (confirm please), then I would conclude that something is still preventing the system from writing. In this case you can either:

a) look further into what may be causing your machine to not give the write access (the logs will not tell you what blocks you) and prevent it from happening

b) or alternatively you can take a full backup, uninstall and clear your folders, then reinstall to allow the folders to be re-created from scratch with correct rights and ownership

 

[proboscis]

Ok, I found out that the path that process monitor is complaining about, is NOT the path to the original phonebook.xml file, which is located in "C:\ProgramData\3CX\Instance1\Data\Http\Interface\provisioning"

The path where the error is generated is "C:\ProgramData\3CX\Data\Http\wwwroot\provisioning". I copied the file to that location and the log is not complaining anymore.

But, the the phonebook is still not updating. So that may have been a superficial error. Thanks

 

[AWS2P]

As John advised previously, time for Plan B is now your road to follow

 

[proboscis]

Yeah I guess that's the only thing left. I'll try it out! Thanks all