Two IP Office 500v2 - Shared Directory

[dibthree]

We have three 500v2 systems all on release 11.0

We have a VPN WAN connecting all sites. All IPOs can ping one another.

The boss wants the directory of extensions to sync up between sites. In other words, when a user hits the directory hard-key we want all three systems user names and extensions to show in the directory on all three systems.

We have the IP500 Voice Networking Channels (8) at each site.

One of the three systems is a Preferred edition with Voicemail Pro. The other two are using their embedded voicemails.

1. If we setup SCN will the systems pull each others extensions list (name and extension)?

2. We are not using Centralized voicemail - is that a requirement or just a recommendation when networking the systems?

3. Is their any other licensing we would need?

 

[jamie77]

Have a read into pulling directory by http. It should do what you want.

Jamie Green

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

 

[derfloh]

As Jamie said. Http directory is the way to go.

Nö further licenses needed.

Voicemail Pro is very much recommended but you can stay with embedded as well.

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[IPGuru]

One of the three systems is a Preferred edition with Voicemail Pro. The other two are using their embedded voicemails.

You should contact a competent installer

This is an unsupported configuration & will cause problems even if you have not seen them yet!
Avaya documentation states you MUST use centralised VM when sites are configure in an SCN

I also stromngly recomend adminnistering all 3 systems simultaniously usingt he SCN mode of manager (preferences
/discovery) & set the ip address for all 3 systems in the ip search criteria box


Do things on the cheap & it will cost you dear

 

[snowman50]

Agree.
Once you set it to SCN mode the the Main site needs to be set up as voicemail pro
And the other 2 set up as centralised.

That way all the voicemails are on the voicemail pro as advised.

The extension and groups would all have to be different number ranges for each site
Lines would have to be on different line groups so as not to conflict.
Names would all have to be unique including huntgroup.

Stands to reason as you can’t have the same name on 1 site therefore you can’t have the same name on another site

You can’t have” hg Main “on 1 site and” hg Main “ on another.

So just plan it out first before implementation.

If first site is 201 and site 2 is 201, you can see the problem there.
So leave main site 201 ,
Site 2. 301
Site 3. 401

Just some things to think about.

 

[dibthree]

Thanks all for the input. Much appreciated.

I will look into the HTTP Directory.

 

[dibthree]

I have been looking in the Knowledge base and online for the HTTP Directory pull and haven't had much luck.

Can anyone point me to where I can find the documentation or a link with more information?