Creating and Importing DIDs In 3CX Phone System 14

How can I import DID’s into the 3CX Phone System?

3CX administrators need to plan ahead on how to setup their 3CX Phone System. Businesses now utilize multiple trunks and VoIP providers with multiple DID numbers and it can be very time consuming to create DID rules manually for each DID number. With 3CX Phone System 12 you can create your DID Inbound Rules in minutes in a .csv file and import it into 3CX Phone System 14.

Here is a sample .csv DID import file that you can download.

Create DID Import File Using the Sample

Download the above sample file and create your PBX configuration to your specifications. Each column is hard-coded in the 3CX Import DID function and the position of the column must remain as is. The comma delimited file provides the structure of the columns and how they should be named in Row 1, 2, 3, 4 and 5 contain examples which will create DIDs in your 3CX Phone System 14. Open the sample file in Excel and then modify it according to your specifications and needs. You may then import the DID file back into 3CX Phone System by:

  1. Logging into the 3CX Management Console.
  2. Click on the Inbound Rules node.
  3. Click on Import and then browse for the DID import file.
  4. Click Open and the DID rules will be imported into your 3CX Phone system 14.

Creating the import file Without Using the Sample

To create the DID import file from scratch use Excel and the values shown at the at the template table below, without any errors. If errors are made, the the import will fail. Any PORTS that the administrator declares must be pre-created before DID import. Any extensions and queues declared must also be present on the 3CX Phone System before the DID import. Also if declarations are wrong such as specifying as queue the number 100 while 100 is an extension and not a queue, this will cause errors. Declaring a time which is not correct,  will also cause the import to skip the whole rule, so the administrator needs to be extremely careful when creating the DID import file from scratch.

The table below explains the field requirements and options for 3CX Phone System Version 12 DID import.

Description Values Notes
PRIORITY Priority of rule in numeric format 1,2,3,4 Rule priority (numeric)
NAME Inbound Rule Name Sales,German Support (Alphanumeric) Name of the inbound rule
TYPE Inbound Rule Type 1, 2 1=DID MASK
2=CID MASK
MASK DID/DDI/CID Mask *200
*201
alphanumeric
PORTS INSERT THE PORTS that you want to create DID’s for in [ ] [10000][10013]] [PORT NUMBER aka VIRTUAL EXTENSION NUMBER
INOFFICE_DEST_TYPE Destination where in office calls will be forwarded to 1, 2, 3, 4, 5, 6, 7 0=END CALL
1=CONNECT TO VOICEMAIL
2=CONNECT TO EXTENSION
3=CONNECT TO QUEUE
4=CONNECT TO RING GROUP
5=CONNECT TO IVR
6=CONNECT TO EXTERNAL NUMBERr
7=CONNECT TO FA
INOFFICE_DEST_NUMBER Destination routing – depends on in office type EXTENSION NUMBER FOR EXAMPLE: 100 or 1000
EXTENSION NUMBER
QUEUE NUMBER
RING GROUP NUMBER
IVR NUMBER
EXTERNAL NUMBER
FAX EXTENSION NUMBER
SAME_DEST_AS_INOFFICE Apply same routing logic outside of office hours 0=UNCHECKED
1=CHECKED
IF SAME_DEST_AS_INOFFICE = 1, SKIP IMPORTING OF “OUTOFOFFICE_DEST_TYPE” + “OUTOFOFFICE_DEST_NUMBER” + “SPECIFIC_HOURS” + “SPECIFIC_HOURS_TIME” + “INCLUDE_HOLIDAYS”
SPECIFIC_HOURS Specific office hours 0=UNCHECKED
1=CHECKED
IF SAME AS OUT OF OFFICE IS UNCHECKED WE CAN CONFIGURE SPECIFIC OFFICE HOURS

If SPECIFIC_HOURS = 1, YOU CAN ALLOW IMPORTING OF “INCLUDE_HOLIDAYS” ELSE (IF SPECIFIC_HOURS = 0, SKIP”INCLUDE_HOLIDAYS”

SPECIFIC_HOURS_TIME DATE:TIME in 24 hour format with each time entry in [ ] [MON:08:00-10:00][MON:13:00-13:30][MON:16:00-17:30][WED:08:00-17.30] [DDD:HH:MM-HH:MM]
INCLUDE_HOLIDAYS Include holidays option 0=UNCHECKED
1=CHECKED
IF INCLUDE_HOLIDAYS = 1, SKIP IMPORTING OF “PLAY_HOLIDAY_PROMPT”
OUTOFOFFICE_DEST_TYPE Destination where out of office calls will be forwarded to Depends on “Same as out of office” IF “SAME_DEST_AS_INOFFICE” = 1 (checked) then you skip importing “OUTOFOFFICE_DEST_TYPE” + “OUTOFOFFICE_DEST_NUMBER”
OUTOFOFFICE_DEST_NUMBER Same as IN OFFICE DESTINATION NUMBER QUEUE NUMBER
RING GROUP NUMBER
IVR NUMBER
EXTERNAL NUMBER
FAX EXTENSION NUMBER
PLAY_HOLIDAY_PROMPT Play Holiday prompt on public holiday 0=UNCHECKED
1=CHECKED

Important: the import file needs to be a .CSV file. Any other file format (.doc, .txt etc) will not be accepted for import.

 

Liked this article?


Get notified of new articles
or share
You might also be interested in:
  1. Craig

    This feature was a huge help when I migrated from 1 provider to another.
    I was able to export the DID’s from one provider and import as the new.
    Thank you for this timesaving feature.

    May 16, 2014 at 9:08 pm
  2. toddy

    lovely – what a timesaver – since when is this working? I didn’t see that.

    May 17, 2014 at 9:54 am
  3. Brian Mills

    Hi

    This is very useful, thanks. Can I ask if this can also be used to change the operating hours or other parameters of an existing DID? So does it overwrite the configuration of the DID already exists? This would be useful for us as we have lots of different DID’s for marketing and it is a pain when the hours change due to different coverage over bank holidays etc.

    May 19, 2014 at 11:52 am
  4. Craig

    Brian,
    An individual DID doesn’t have Office Hours – it uses Global Office Hours if I recall. This would be an enhancement.

    May 19, 2014 at 7:53 pm
    • PJ

      Hi Craig and Brian,

      A DID can indeed have its specic office hours, you need first to untick option ‘Apply the same routing logic Outside of office hours’, then tick ‘Set up Specific Office Hours’ and use the button next to set them.

      Regarding import it will not update, it will give an error that matching rows exists already. You will then have to first delete existing inbound rule to be able to import the file saved.

      May 21, 2014 at 10:23 am
    • Craig

      I guess I never looked that far down… Thanks for the clarification…

      May 24, 2014 at 2:01 am