IPO Networking 5 sites

[Vmail]

I will be implementing a 5 site IPO with 406's 403's and 1 412. Each site wants to keep the existing 4 digit extensions which all overlap. Can I set up a digit for each site, ie. site 1 is 1xxxx, site 2 is 2xxxx, while keeping the same extensions that do overlap? Or is this more like a definity network where none can overlap?

THanks.

VMAIL

 

[intrigrant]

They shouldn't keep overlapping numbers for their own best.
You could implement with access digits, thus keeping equal numbers on some sites but they will have a lot of little irritating things if they work with it.

If they stick to their plans i advise you to build their situation as a demo and show them the lack of functionality, that should convince them not to do this.

 

[IPAlot]

If you have the same ext numbers or names at different sites then you cannot use SCN.Well you can but you have been warned. You can do it without enabling SCN and just dial the sites using short codes but kind of defeats the purpose of networking them as you then dont get the transparency between sites with blf updates etc...Convince the customer to change number plan.

Soopa Doopa Intergalactic IP Office installation mechanic and configuration corruptor from way back.

 

[sizbut]

You could combine both and have SCN and site prefixes but without the need for rerouting shortcodes.

Rather than add the extra dialing digit for each site as an extra routing short code on each system, renumber the system extensions to include the prefix by default. This can be done with a single command on each system.

For example use the File | Advanced | Rebase command at site 1 to add 10000 so their extension numbers change from XXXX to 1XXXX. Do similar at site 2 but add 20000 to change XXXX to 2XXXX. And so on.

It means that user have to remember to dial the extra digit for onsite calls as well as between site calls, but in the end its more consistent and I think you'll find they'll adapt quickly.

In addition you can now use SCN on the links, which means thing like the directories will list other site extension names and numbers, so finding the number of Joe at site 3 will be a whole lot easier.


(Note: The rebase option isn't available if the system locale of the config opened in Manager is enu. So if that is the case, just change the locale temporarily, use the rebase command and then set the locale back to enu.

I'm also not too sure how thorough Rebase is, its really mean for renumbering new systems, so after using it you should manually scan hunt groups and incoming call routes etc and add the extra digit for that site wherever needed).

 

[Morrack]

Fascinating!! Now why the heck would Avaya block enu users from this neat little utility?? This is the first I've even heard of "rebase"

Bizare how they tend to treat north america as insignificant.

Peter

 

[IPOUK]

Rebase is a good function - sometimes you can get confused though when you want to move extension numbers around though!

When is Manager going to be updated so that when you say change a user's extn number, this will be reflected in the Extn tab as well? It's really annoying and can get so confusing!

 

[sizbut]

Thank Avaya USA for the withholding of Rebase, they insisted its what you wanted (or rather didnt want).

 

[IPGuru]

You mean the lack of rebase was deliberate?
it sounds like a bug to me after all if usere dont want a feature no one is forcing them to use it.

as to changing the exnt number isn both user & extn simaltaniously this is a bad idea.

if you want to move "fred" from 1 port to another (say pot to digital) then you change the user number in the extn field.

 

[sizbut]

Deliberate - honest, very silly - yes. Just don't dig too deep in Wizard running on a US PC and a non-US PC.

I agree with IP Guru, the users user number doesn't have to change, just extension with which it is associated by default.

 

[Morrack]

If all you are doing is moving people around, yes (or just swing the patch cord). But if for some reason (say networking to other switches, like the orignal question in this thread) you need to rework your entire numbering plan it would certainly be handy.

Does it keep all existing programming intact and just change the numbering?

 

[sizbut]

I'll have to have a play tomorrow. Manager has got a lot better at tracking things (eg. change a user name and most other feature that refer to that name now update, same for hunt group names, so hopefully ditto for extension numbers).

 

[IPOUK]

Rebase even updates your source numbers!!!

However, you can't choose which extns to rebase - rebase will change ALL extensions by either + or - a particular number.

This kind of comes back to my original question - if you have 5 directors who all want to be on a different extension range, let's say the main range is 200-250, and they all want to be on a 300 extn range - you can't just change each of their extensions in the user properties? You need to go into the physcial extension and change the mapping too as that doesn't get mirrored to the user properies.

Or am I just being v thick here (it's before 9.00 at the moment!!)

 

[sizbut]

Did my play this morning and:-

Rebase updates the:

- User extenson number.
- Extension extension number.
- Hunt group member numbers.
- the Vxxx entries as mentioned.

The area in which it fell down was incoming call routes targetted to a user.

 

[Morrack]

IPOUK to do what you want you need to manually change each one. In the user forms both the actual extension and any sourcenumbers, as well as in the extension form (unless you have all users setup as hotdesk extensions and an arbitrary set of physical extension numbers).

Peter