Solved 3CX Deployment

[amir_]

As we are starting our migration from Cisco to 3CX - I've got a TEST 3CX and a PROD 3CX system. We build all phones / extensions in TEST to confirm correct functionality.

Is there an easy way to then EXPORT the phone / extension data from TEST and IMPORT them into PROD? I see an EXPORT button in EXTENSIONS - does that literally EXPORT every configuration element associated with the EXTENSION and PHONE so that all I have to do is IMPORT it into PROD?

TIA,

Amir

 

[Evolute IT]

As we are starting our migration from Cisco to 3CX - I've got a TEST 3CX and a PROD 3CX system. We build all phones / extensions in TEST to confirm correct functionality.

Is there an easy way to then EXPORT the phone / extension data from TEST and IMPORT them into PROD? I see an EXPORT button in EXTENSIONS - does that literally EXPORT every configuration element associated with the EXTENSION and PHONE so that all I have to do is IMPORT it into PROD?

TIA,

Amir

Yes, basically it will import everything, including the first deskphone of the user and all options.

 

[hkennedy]

Yes, basically it will import everything, including the first deskphone of the user and all options.

Thanks for the reply. The issue we're seeing is when we try and import the file after changing the interface IP from the test server to the production servers IP we receive a MAC_0 error.
-H

 

[Evolute IT]

Thanks for the reply. The issue we're seeing is when we try and import the file after changing the interface IP from the test server to the production servers IP we receive a MAC_0 error.
-H

You would need to go into the csv and search and replace the interface IP.

it's in the PhoneOptions column if my memory is correct or the Interface_0 column. I don't remember exactly.

 

[amir_]

Here is the column name of the export file we are modifing. But we then attempt to IMPORT into PROD 3CX Server and get a "MAC_0" error.

InterfaceIP_0

 

[hkennedy]

You would need to go into the csv and search and replace the interface IP.

it's in the PhoneOptions column if my memory is correct or the Interface_0 column. I don't remember exactly.

Correct, InterfaceIP_0 is where we make the change. Save the file and when we try and import we receive the error. I've tried using the 3cx template, verifying the MAC_0 column is formatted as text, etc.

 

[Evolute IT]

Best thing would be to remove the interface ip and mac and phone options from the columns (leave the columns there empty tho).

Then you'll just have to readd phones, much simpler I think.

I am unsure why the new IP isn't taking effect.

 

[amir_]

Best thing would be to remove the interface ip and mac and phone options from the columns (leave the columns there empty tho).

Then you'll just have to readd phones, much simpler I think.

I am unsure why the new IP isn't taking effect.

When folks modify the CSV file - do you do it in Excel or a text editor?

 

[Evolute IT]

When folks modify the CSV file - do you do it in Excel or a text editor?

Usually a notepad++, excel can help but it's a pain with numbers and mac address if you miss a 0 at the beginning of one. That kind of things.

 

[hkennedy]

I figured it out… I used an unboxed yealink for testing. I did a factory reset on the phone and searched for traces of the MAC address in both 3CX servers (Test and Prod). It allowed me to set it up in test, however I think it may have been joined to prod at one point.

I pulled a new phone out and set it up and was able to export and import into prod. I started thinking about the error MAC_0 and it occurred to me maybe somewhere in the DB on prod it held on to something, maybe the MAC address.

Thanks for the assistance team!

-H

 

[ChrisC_3CX]

@hkennedy
@amir_
Glad to see you got this resolved!

Please feel free to start a new thread should you need anything else.