Recent content by jessejdavis

Jim, Sorry that I haven't been able to answer this yet... 1. Go to Advanced, Import 2. Make sure that "station" is selected under "Select an Object" 3. Select "Change Extension Operation" (on the bottom) and click "Ok" 4. On the spreadsheet-like form, just fill in the original extension and...

Thanks! I missed it myself after staring at the screen more than once. When I did find it at 1:00 AM I felt a little dumb (like, "I can't believe I just entered all of those by hand!"). Fortunately, I at least had several stations to go back and clean up, so I used it then. These were the...

One other update... It turns out that the export/import function of ASA can do a mass run of the "change user extension" wizard. Unfortunately, I didn't realize this until near the end (kind of a "doh!" moment). One other word of caution, the ASA wizard doesn't handle the abbrv dialing list...

Thanks again for all of the advice. In the end, we have decided to use ASA's "Change User Extension" wizard. It turns out that this not only changes the extension, but any references to that extension, including hunt groups, coverage paths, pickup groups, message lamps, etc. We're not using...

We're ok on the RTU. We have about 250 available and I will be duplicating less ports than that. The old ones will get blown away if I can figure out how to route any incoming calls to 3xxx (old) to a single extension. I was going to use Incoming Call Handling to look for 3xxx and replace...

Hmmm, I like the alias idea (for Octel). Thanks.

Ok, I see what you mean... All swap station does is change the ports, so not much help there.

We are still working through the planning stages and thus far we've focused on the Definity side of things, but I would imagine that we will use the brute force method. In other words, we'll step through "Change Mailbox Number" for all of the mailboxes. I was thinking... We may actually do...

We will definitely proceed with caution! Everything gets checked and double-checked. Thanks.

That should work. I was looking into some sort of combination of export/import, find/replace, etc, but I couldn't figure out how to put it all together. Thanks! Jesse

We do have someone helping us (they actually handle our Avaya maintenance agreement), but they're not cheap either and I do not know how long it will take them to do this (as far as I know, they're not using Provision). As for voicemail, we have an Octel Aria 250.

We are getting ready to move all of our DID extensions to a new range (long story on why... but basically changing from an old tie-line based service provider in a different geographical location to a local provider). Specifically, we are moving the 3000-3299 DID block to 4000-4299. Is there...

You're right. That should work (yes, the extensions will match, thankfully!). In fact, that would probably be the easiest solution to implement. Although, I was hoping to have a message played for the caller (leaving it up to the end user to tell every caller might be asking too much)...

Also, I do not have an announcement board.

Ok, here's the situation (oh, and I'm relatively new to all of this)... We currently have DID's in the 412-256-3000 to 3299 range. I won't go into details on why, but we are changing our DIDs to the 724-459-4000 to 4299 range. We are using a Definity G3 (v11) PBX with an Octel Aria 250...