Avaya IP Office Programming

[P12ash]

Hi Guys

I know people have asked this question before but I’m really stuck.

I have a client who has an old lucent index phone system and wants to replace the system with an Avaya IP Office V2.

The customer current system servers all users and also rents office out and provides them with a Phone extension

Customer office extension range starts from 200 – 290

Rented Offices Extension range start from 600 – 700

The customer would like the following

1. Block Extension range 200 to call 600 and vice versa.
2. Hide extension range 600 from the directory which I know can be done via Ex-directory
3. Extension Range 200 will Not be Ex-directory as they would like to see all 200 range in the list but Block 600 range to call from the contacts directory.

Hope somebody can help

Many thanks

Prash

 

[IPGuru]

Release 9.0.2.0 build 860. The dummy ARS table method works just fine.

I cannot say it 'Works Just Fine' you are exploiting a bug that may get corrected in a future update. Avaya will of course simply refer you to the documentation if you then try to raise it as a fault.

A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[AACon]

Trying it on the latest 9.0.3 build, and it does not work. Just dials the user as normal.

-Austin
ACE: Implement IP Office

 

[AACon]

There is a way of doing this, but it requires a bit of trickery with vmpro, DND, and some magical wizard type stuff in user vm options. It would be a pain to deploy to a ton of users.

Maybe tenant partitioning should be a feature request...again.



-Austin
ACE: Implement IP Office

 

[montyzummer]

Austin i just know you are dying for someone to ask , so go on share the vmpro magic you have created.

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[Pepp77]

IPGuru

I have just configured as per hbsurfn so my dial delay time was 1, my dial delay count was 1 (even though my extension length is 4, so this should be 4 as good practice) and the shortcode on my extension was 4N/dial/N/ARS:58 (a blank ARS). And because the dial delay count was below the extension length it matched it after the 1 digit, so before an extension could be matched).

I also tried it with a shortcode of 4N/barred/./0 and this also stopped me dialling other extensions. So the important factor to make this work is the dial delay count being lower than the extension length I think.

But then I was trained to set the dial delay count to the extension length so wouldn't have come across this in normal usage.

| ACSS SME |

 

[hbsurfn]

I didn't change any of the dial delay counts or timers. Just the 4N and 3N short codes to the fake ARS table. I basically create a new ARS, name it, and delete anything in the window....like the 911 dial code. The "N" shortcode is always going to win because now the system thinks its an outbound call to a trunk. You are basically routing the call to junk ARS so you will always get an wave off.

ACIS
ACSS
APSS
CompTIA Convergence+
CCNA
CCVP
I'm also ShoreTel certified

 

[AACon]

Well, if you can get it to work, more power to ya. Seems it doesn't work for any of us, c'est la vie.

-Austin
ACE: Implement IP Office

 

[amriddle01]

hbsurfn, your based in Illinois I believe, US systems don't use dial delay count so it will work if you allow the dial delay timer to elapse. The OP is based in the UK where dial delay count is 4, this means we don't need a prefix to dial out. You can get it to work for somebody manual dialling on an IP/Dig set by lowering that to 1 or 0 (like US systems) but this doesn't stop SIP phones, someone using en bloc dialling on DIg/IP phones, redials to the extn or calls from the directory matching and going to the extn... not a working solution. Also, while you were posting the "common guys, you started it" stuff it was 03:00 here, so we were asleep

 

[amriddle01]

if you allow the dial delay timer to elapse

That's irrelevant actually, but the rest stands

 

[jamie77]

Things can maybe be played with and rules broken/bent. This will never work like it should.

The INDeX supported multiple tennants as part of it's software and could be split up. The IP Office does not. Simple as that.

You either need to look at another system for this customer or explain he will not get the features he wants if he really wants to go down the IPO route. You will spend your life messing with this and end up with an unhappy end user.

Square pegs don't really fit in round holes. They can be forced in with a hammer though!

Jamie Green

[bold]A[/bold]vaya [bold]R[/bold]egistered [bold]S[/bold]pecialist [bold]E[/bold]ngineer