creating redundant DIDs 1

[RINGINnBLINGIN]

Anyone know of a way to import the DID list twice so it can be exported, modified and re-imported? We're about to cut to an enterprise, redundant trunk that will require two sip lines with the same DIDs. There are over 1000 DIDs so any streamlining of this process would be great.

 

[TouchToneTommy]

Use the MSN tool to create enough DID entries for all of the numbers. Use a placeholder range of numbers, such as 1234567890

Export the config as a csv, open in Excel
Remove everything up to IncallRoute_Info_Start and everything after IncallRoute_Info_End
Size the columns so they are not scientific notation
Column A holds the Line Group ID
Column C is the Incoming Number
Column F is the Destination
Column I is the Fallback
Column S is |destination|fallback destination~ (pipe destination pipe fallback tilde)
DO NOT MESS WITH COLUMN P, THE ICR_GUID. Do not add entries, do not delete entries.

Make changes, save as .csv, open in notepad and remove all commas after IncallRoute_Info_Start and after IcallRoute_Info_End, save text file as .csv and import into IPO.

Check everything for validity before merging

 

[RINGINnBLINGIN]

You're never going to believe this, but I tried that already. When you import duplicate ICRs, and merge, it appears it takes. When you reopen manager, you're left with the one set.

I've tried to export as binary. Then export as CSV, modify the CSV as you stated above. Then, in order, import the CSV (new), import the binary (old), merge. Same thing.

The one thing I haven't tried is creating an offline config and attempting to push that in.

 

[TouchToneTommy]

It works for me - are you finishing by opening in notepad and removing the extra commas?

 

[RINGINnBLINGIN]

What version are you running?

 

[IPGuru]

simply use the same incoming group ID on both trunks, then you only need to configure the ICR once.
all so more maintainable as no chance of someone forgetting when changes are made


Do things on the cheap & it will cost you dear