Equivalent to COR, or Nortel's NCOS...

[kristiandg]

The way the IPO works is very odd to me, in terms of programming. I'm used to PBXs and the shortcodes still confuse me.

Whats great about those big PBXs is that if your phone has a COR or NCOS of, say, 3. you can make calls to any route or group of phone numbers (say local calls only) that also have a 3 or lower. Basically, if you have a 1 or higher, you can make local calls. If you try to make an LD call (which would normally require an NCOS or COR of 5), then the fact you have a level of 3 means you get prompted for an AUTH or ACCOUNT code. Your account code is flagged with a higher level so once you enter it, your phone now has a higher level and can make the call.

I'm looking for similar functionality on the IPO, if possible.

Gurus, can you figure out a way to do this?

TIA,

Kris G.

 

[kristiandg]

Sorry, that should read "Basically, if you have a 3 or higher, you can make local calls."

Kris G.

 

[IPGuru]

call restriction on an IPO is not handled in the smae way as most large systems.

You need to creat personal shortcodes withing each user to either bar (feature busy) or allow calls (dial)
usualy you would creat a system short code to bar national & international calls

Short code 00N, feature busy.

& then add a user short code for those useres that are alowed to dial them.

from 2.0 an additional section called User Ristriction where these options can be set once & used for multiple users (dispite the name it can be used to enable features as well as restrict them).

For more info on short codes check the help files - they are actualy quite good.

 

[sizbut]

There is something for this, but the way it was designed, especially with no defaults, means a programming.

Using Manager, look at User Restriction. Create a restriction here such as one called "Local only" and add short codes that would return Busy to any non-local dialing.

Then for the appropriate Users, at the bottom of the User | User tab you should be able to select "Local only" as the user's Restrictions.

You do need to be very on the ball with all the things that users might dial for non-local calls, looking for 0 and 00 prefixes isn't enough, you have to pre-empt alternate carrier perfixes and others as well.

Its not helped by the default being no restrictions what so ever. It would have been helped by at least one default set of user restrictions applied by default to all users when added to the system. Even if that set had been empty it would speed up programming of basic outgoing call control for all users.

 

[IPGuru]

You are right about the lack of a default restriction profile, it would have been usefull.
I suspect Avaya thought we would all use the ofline config wizard as this enables various progiles to be created & applied.

(it is still pos to use the wiz to apply changes to an existing system, hopefully the bugs have been ironed out in 2.1 I havnt dared use it yet)

 

[kristiandg]

Hmm, thanks guys. I'll take a look when I get back in town. I forgot about the wizard being able to edit now.

Its not like Avaya to have a PBX not default to being somewhat secure.

Thx,

Kris

 

[Pepperz]

Well, there you go, the IP Office itself, is "not like Avaya" if you know what I mean.

Pepperz@charter.net

 

[IPGuru]

Short History Lesson

A long time ago in a land far far away (well Watford in the UK) A company called "Network Alchemy" developed a small modular phon sistem with built in data routing capabilitys.

Another company bassed in Welwyn Garden City, called SDX had just launched thier new switch called INDeX & liked whjat they saw at Network Alchemy & bought the company intending to combine the Data capabilitys of the Argent system into the INDeX - this became the IPNC

SDX were eventualy Bought out by Lucent/Avaya, developement continued (on both platforms)& the Argent evolved into the IPO.