3CX unregistered in Database

[Daandw94]

Hello,

Not sure if this is the right category, if not please move to the right category.

At one of our clients some devices randomly unregister from the 3cx. We have looked into this issue and found that this is a defect in the device.
Rebooting a device registers it again.

We want to automate the process of rebooting the devices. therefore we need a service detecting devices being unregistered.
The idea is to have a service periodically read the database of the 3CX(definitely not modify it) to determine unregistered devices.

The question is, is there a table in the PostgreSQL database that contains this information, other than the eventlog table?

Thank you in advance.

 

[VoIPTools]

Regardless of whether you intend to only read the database, 3CX does not support accessing the database directly. Period.

You can, however, get this information using the 3CX Call Control API. Let's assume then, that you have a list of phones that are no longer registered, how do you propose to reboot them?

 

[Daandw94]

Regardless of whether you intend to only read the database, 3CX does not support accessing the database directly. Period.

Understood.

You can, however, get this information using the 3CX Call Control API.

I cant seem to find any documentation on this API. How is one to aquire this, and is it compatible with 3cx version v12.0.36097.670?

Let's assume then, that you have a list of phones that are no longer registered, how do you propose to reboot them?

They aren't phones, actually. They are nurse call devices that use OAP for alarm messaging and SIP for voice communication. They are PoE powered and can be rebooted using an HTTP command, and are registered on a careserver that is using a mySQL database.

The intent is to use the list of unregistered devices and compare it to the list from the careserver database. Should a sipnumber exist in both, the device shall be pinged to make sure its not just unregistered because of power/network loss, and then send the http command.

 

[VoIPTools]

Ah, that's helpful background. You might be able to find someone who has published the old V12 documentation for the "3CX Call Control API V12". 3CX has, for now, pulled all documentation and staff are not permitted to share the internal documentation outside of 3CX.

We recently released a VoIPTools API which would enable you to get this information, but it is only available for 3CX version 16.

If you are still running 3CX V12, you are at significant risk of it no longer working. For example, if your NIC MAC address were to change (just one of many possibilities) you would need to re-register your 3CX and that is no longer possible. Take my advice -- do whatever you can, as quickly as you can, to get upgraded to V16. You have been warned.

 

[Daandw94]

Ah, that's helpful background. You might be able to find someone who has published the old V12 documentation for the "3CX Call Control API V12". 3CX has, for now, pulled all documentation and staff are not permitted to share the internal documentation outside of 3CX.

I did find what I needed. I reckon it is not appreciated if I share it here, correct?

If you are still running 3CX V12, you are at significant risk of it no longer working. For example, if your NIC MAC address were to change (just one of many possibilities) you would need to re-register your 3CX and that is no longer possible. Take my advice -- do whatever you can, as quickly as you can, to get upgraded to V16. You have been warned.

I have alerted my superiors on the matter. Thank you for pointing this out. Though, the devices are rather ancient, and make use of something called "variable bitrate". To upgrade we must be certain the new 3CX v16 supports this. Do you perhaps know whether it does?