Copying Call Logs/Data to A Different 3CX Server

[TaylorStevens23]

We are trying to access the 3CX’s Postgres database, using pgAdmin on a free licensed test server we have in Google Cloud. We want to test out this process before we attempt anything in production. Our test server doesn't have much call data at all and we would like to copy some call data from our production server into our test server so we can have a more complete idea of what is in the database.

My original idea was to take a backup of our production server with no additional items. So the backup will include Full System Configuration (Call History, Chat History, Recording History, System Voice Prompts and Audio Files for music on hold). Then restore our test server from that backup. My concern is, what issues will this create? I already can think of if the backup includes extensions then all our extensions will get a welcome email to our test server (which I really don't want). Is there other potential issues I am not considering?

Or does anyone have a more creative solution to get that data into our test server?

 

[cobaltit]

Welcome emails are sent at the creating of a new extension (by default). Restoring a backup is not creating an extension. And if it does, just send an email out to folks ahead of time and tell them to ignore it.

 

[Alphabetic]

For the sake of getting some info in to 3CX for testing, create 2 extensions, set up in mobile or web client and make calls between them.

 

[ChrisC_3CX]

@cobaltit is right, by merely restoring a backup welcome emails will not be sent to the extension's but please be warned that, accessing the 3CX Database automatically voids 3CX Technical Support.

If you wish to proceed anyway, just bear in mind that there are some issues that may arise when restoring the backup so I would recommend using a backup that excludes License Key information and just use a Trial License Key for your test system. Also do note that having Register based SIP Trunks might potentially cause problems since they will register to the SIP Provider from the new test instance.

 

[ChrisC_3CX]

Also, regarding the test system, you could just do what @kieferschild mentioned and avoid restoring altogether, provided of course that having the same exact configuration and data is not a requirement when testing.

 

[VoIPTools]

Perhaps what we SHOULD discuss is WHAT you are trying to achieve, rather than the implementation details (accessing the PostgreSQL database). Perhaps we can find a supported way, or at least a way of accomplishing your goals without voiding your support agreement with 3CX.

Perhaps you can get the needed information via the CDR files, or, if you need to update data in PostgreSQL, perhaps that can be done via the 3CX Call Control API.

A little more information about why you want to access PostgreSQL would be helpful so we can offer alternative approaches to meet your needs.