How to import non-continuous extension ranges in 3.2 and up?

[Gibsonic]

Ok. The wizard from 3.1 and older definitely had it's issues but i was able to use it quite well for importing users and extension ranges, even non-continuous ranges from the lovely customers that like to skip all sorts of numbers in their DID range.

i can import the users into 3.2 without a problem but it doesn't impact the extensions...is there a way to do this? I've got a very full 412 with a couple hundred non-continuous users to program and i would also like to know for future reference as this will come up again.

just using the increment tool won't help me b/c that is for continuous extensions.... grrr....

 

[Gibsonic]

to that same idea,

how much of a no-no is it to import .exp files created on 3.1 into 3.2? I use .exp files for common things like dial and deny shortcodes, ip trunks, etc.

 

[tlpeter]

why don't you use the csv option

in exel make the extension with the name like

Extn301,name
Extn302,name2

then select the two and on the bottom of the second fiels you get a little square
click and hold
pull down till you have enough users
delete the users you don't need
save it as a csv

import and ready

ACA - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[Gibsonic]

the export/import via .csv does not cover extension assignments to ports..only extension association with users...

it creates the users with the right extension from my user.csv file with no problem. i have that part done, but now i seem to have to manually change all the extensions in the extension portion of the config.

 

[tlpeter]

i missed the user part

i did once export the whole config and changed the extensions there

there you can see the ports and extension numbers
after the change import it and it is done



ACA - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[Gibsonic]

yeah, was hoping to have to do that...it doesn't take THAT long to just key them but it is annoying to lose feature functionality with a newer release.

 

[kholladay]

If your going to use this method please be careful. There are a LOT of fields in the exported file.

Open your config and use the import/export to export the "Configuration" as a .csv.

Open the configuration.csv in Excel and delete everything before Extension_Info_Start and everything after Extension_Info_End. Modify your extensions to match your desired dial plan and save the .csv file.

Now open that new file in Notepad and remove the series of ,,,,,, that are after the Extension_Info_Start and Extension_Info_End statements. Save the corrected file.

Import this back into your configuration.

Kyle Holladay
Certified: ACACN, ACSCI, ACSCM, TIA-CTP
ACE Implement: IP Office

"If it worked the way it should you wouldn't need me

 

[aarenot]

I like this stuff, I used to take another factories systems from one release to another which was not supported for upgrades by going into the text files to manipulate the data to the new format. Then import the files to the new system. I will have to play with this, muahahahaha

 

[intrigrant]

Do NOT use this kind of importing/exporting stuff if you plan to install a SCN network.
It will ruin the whole SCN, users dissapear on one site and appear in another site, incoming call routes start going their own ( not programmed ) way and more trouble like that.

 

[Gibsonic]

yeah, intrigant, that was kind of my fear.

this is one of three IPO that are/will be networked back to an Communication Manager on an S8500 with centralized Audix.

the IP trunks are QSIG with no SCN but the last thing i need is to be penny wise and pound foolish by using a possibly risky import method.

For this site I went ahead and burned the manhours/minutes to manually key the extensions, but for future sites I may just config on 3.1 then upgrade for sites with a funky extension setup.

 

[kholladay]

That is completely untrue and your fear is based on a completely unrelated method of pushing a config to multiple units. I have used this method for quite some time now without issue. Keep in mind that you are not reusing an existing .cfg file, which is where the known issue comes into play. You are exporting a .csv file which has no unique markers. This is no different than exporting a user.csv or shortcode.csv file and then importing into another switch (which is also perfectly ok).

It is up to you to take this information and use it or not. I can say that I have many SCN networks out there, and 2 of them on 4.0.7 and all were programmed using this method.


Kyle Holladay
Certified: ACACN, ACSCI, ACSCM, TIA-CTP
ACE Implement: IP Office

"If it worked the way it should you wouldn't need me