Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Scripts for Meridian 1 Opt 81c

Status
Not open for further replies.

Hootman

MIS
Apr 7, 2003
11
US
I have a Meridian 1 Opt81c. I do have Optivity 1.2 and can access ProCOMM if scripts were available for this program.

I have two tasks that will take me forever to run one at a time.

One task is to turn on Internal CDR for all phones on the property.

The other tasks is to disable about 500 two line phones. We are remodeling a building and have removed all of the phones in that building. Now that construction has started, we are receiving a lot of error messages on our switch terminal reporting odd errors for some of the DNs in that building. As a result of how the original installation was performed, this building does not have a different designation. Also the extensions match the room numbers ... ex. room 201 is ext 1201 and 6201.

Does anyone know where I could get some scripts to run either or both of these.
 
Sounds like what you need to do here is transmit a large number of basically repeating transmit commands and wait for some type of acknowledgement from the PBX between commands.

Something like

proc main

transmit "disable line 1201^m"
waitfor "whatever PBX prompt"
(repeat the above for each line)

endproc


An easy way to do this as a one time project is to list out your lines on a spreadsheet and add your transmit commands to the first column. Then cut and paste to aspect.

If you post a sample of what the PBX command is, and what the PBX response is, I can put together something a little more solid for you.

Turning on the Internal CDR for each line would probably be a similar operation.
 
The disable is pretty simple ...
Below is the sample of how the process is done in the switch.

Logi
xxxxxx
LD 20
disu xx xx xx xx
disu xx xx xx xx
disu xx xx xx xx
****
Logo

Each of the xx xx xx xx represents a different terminal number ... This is what I would have to get in a spreadsheet and cut and paste???

Then the change is a little more difficult. But if I knew how this one would be loaded into Procomm, I could create the other script ...


 
The easy way here would be to use a 3 column spread sheet.

The middle column would be the list of the terminals (if they're consecutive that would be really easy.) But between each line you need to leave a blank line.

The first column would be the following:

Transmit "disu "
waitquiet 3 ; 3 seconds pause between commands you can adjust this

And the last column would need to be:

" ^m" ; this is the cr/lf code

Once you build the spreadsheet, copy those 3 columns directly into your Aspect editor. Don't forget proc main at the begining and endproc at the end...


There are way's to have aspect read a text file (which could be your list of terminals), but that's still a little over my head.
 
You can also perform the operation once while recording it, insert the recorded data (without the proc main and endmain) into e.g. MS Word and perform a mail merge.
Export this into the script again and Voila, you have a script in which the TN changes but the procedure remains the same per TN.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top