Import and export of DID's

[seantp]

I've searched the forums and the previous conversations basically went, you have DID's they need to route. This is the logic for placing DID import/export in Rules instead of the DID page under the trunk. Where I think the conversation fell short, and is what I'm running into is that I'll bulk buy DID's for a company that I know will grow. When I add those I don't need to route them and I have been adding them when I setup the trunk.

Now I'm finding that I can only export DID's that are configured with a route.

Now it sounds like a great idea to have all this figured out before hand, and I'm sure I could just route them all to a general mailbox and problem solved. I guess my only issue with this is that it's forcing me to spend time on that process when I don't really need to. It would add flexibility for workflows if you could import and export DID's at the trunk as well.

If you're thinking that this belongs in idea's, it does but I'm not cool enough to post there. On that topic, I get why 3CX wants to limit ideas to customers that move the needle, but I can't even search that forum. I'm hoping that's just an oversight.

 

[seantp]

oh, wow the export in rules won't even work as an import unless the number are already setup in the sip trunk provider and exporting the trunk config doesn't even include the DID's either.

 

[JohnS_3CX]

Hi Sean,

Have you read this document? https://www.3cx.com/blog/docs/importing-dids/

You can bulk import a large number of DIDs to be added under a specific trunk and decide what you want to do with them later.

Avoid adding existing numbers, those will not be overwritten and will produce an import error (although the rest should import)

 

[JohnS_3CX]

Note: If you then delete all the inbound rules, the DIDs will still remain in the trunk in an oprhaned state, but they should automatically go to the destination of your main number as set in the trunk's General tab

 

[seantp]

So I exported from the inbound rules, deleted the trunk, then tried to import that same file after a new fresh trunk with the same name was created. It failed, until I manually added the numbers to the DID page under the sip trunk. After that the rules imported just fine. Not sure what I'm missing. Seems like what you export should be able to import.

 

[JohnS_3CX]

Don't delete your trunk, leave it as is. Just make an inbound rule and then export the inbound rules to have a template. We are not working in the trunks tab now, only in the Inbound Rules page:

Then edit the exportDID.csv and copy paste to create new entries:

My Export:


My Import:

(note i removed my original number that was in the export, because it already exists in the PBX)

 

[seantp]

In this case I am doing two things that necessitate deleting the trunk. One I had setup a Twilio trunk as a generic SIP provider and the red "unsupported provider" indicator was bugging me. I had to delete it and I wanted to set it up correctly. I'm also migrating a trunk to another system and it was a similar deal. My CSV looked exactly like that, and it errored out with each line [Mask],[Port]. That didn't make sense to me, but like I said after adding the numbers to the Trunk then that same file imported.

 

[JohnS_3CX]

Please note that as per the link I mentioned above: " Any PORTS that the administrator declares must be pre-created before DID import "

For example If you go to my trunks and type 100000 in the search bar you will see my trunk appear because its internal port number is 100000.


The reason i suggested you export first, is so that your port number will automatically be populated for that trunk in the file you were to use as a template.

In your case it failed, and from what I gather it was because your port number in the file did not match the one that existed in the PBX hence the import instructions were referring to a non existent trunk port number.

 

[seantp]

I see. Well I understand that now. Still would like to see DID import/export functionality separated from rules (or in addition to) so getting them in and out of the system is easy and unburdened by routing knowledge. Especially when setting up a new system and you don't really know how you'll be dedicating numbers and you just want them in the system without dealing with putting together a perfect CSV import.