- Range Programming
Add a device, and in the form you can specify you want to add 100 records.
You can specify the increment on the extension number for example.
Only usefull if the numbers you are configuring are sequencial.
or
- Import / Export spreadsheet
Use the import / export sheets to bulk add the extensions you want.
or a combination of both.
eg. You could use range programming to configure the basic extensions (1001 - 1750)
Then use the import sheets to configure the COS / COR, teldir etc
You can combine this with excel formula to use vlookups (or index / match) to match extension numbers to COS/COR, teldir etc from a master spreadsheet.
If you go to a form (User and Services Configuration) then click on import you should see a link to download a copy of the import spreadsheet.
There is a readme.txt in the archive, but extract the 'spreadsheets' folder somewhere. Open the 3300ICPImportSpreadsheet.xls. Select your platform, and add the forms you want to work on to the sheet from the list. There are already a few tabs selected (users and services, keys, teldir).
Add your data, check the data (checks for errors) then save for import - will export your data to a .csv. Then import the csv to the MiVB.
Or you can export and import direct from most forms without the 3300ICPImportSpreadsheet.xls - but you need to know more about the form structure.
I don't recommend range programming in the Analog telephone forms.
However, program the first one in the User and Device form.
Export that one.
Open the CSV file in Excel.
add all the programming you want through there.
Be sure to include the following at a minimum:
First and Last names
Extension numbers
PLID - be sure that this will match up to what you have on programmed ASU cards.
COS/COR
Save the file as needed and then import it to the system.
750 analog lines on one system... that's impressive!
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.