Pro...SCN, not centralized, any issues with this?

[Gibsonic]

Ok i have a customer that has bought a VM pro license for each of their 15 locations. each location will have it's own VM Pro server and they do not need there to be any voicemail networking but they do want extension dialing and likely toll-bypass/LCR across the IP trunks. Their extension ranges are unique but barely. They are all over the place. I plan on just enabling SCN for all IP links even though they aren't configured for centralized VM.

Any issues with doing it this way?

 

[Gibsonic]

btw...this is on 3.1(65) with VM Pro 3.1(21)

 

[janni78]

Using multiple Voicemail and SCN is not supported by Avaya as there was some issues with this.
Can't remember what it was though

Otherwise you can always use shortcodes to call between sites instead of using SCN, although you will not get user status updates this way.

 

[kwing112000]

I have a customer that we have taken over and they have all kinds of issues with a set up like this. They gets sites crashing. Configs swapping all kinds of little things.

 

[Gibsonic]

hrm... it sounds like it could be troublesome...it does seem odd though that the SCN function can't work properly in this environment.

Anyone with a positive experience doing this or is it pretty much a bad deal for everyone?

 

[tlpeter]

did i read it right 15 vmpro licences ???
why not just one vmpro ???


______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[Gibsonic]

heh...i asked the same thing.

it's a law firm and they will be doing a lot of call recording at each location and didn't want to have to pay for the bandwidth

*shrug*

 

[Gibsonic]

every location needed an auto attendant with DBN and the like as well...

 

[tlpeter]

then you can forget scn andyou have to work with shortcodes for extensions and huntgroup
and you said the dialplan wasn't al to good

so i wish you good luck and a lot of cups of coffee


______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[ThePhoneMn]

I did this and we ended up with a CVM because of the issues we had... I even removed "Voice Networking" and we still had issues. Dial by name was the biggest problem I can think of, some users were not picked up on the local machine, but users on the remote VM Pro's were announced to callers when using dial by name... MWI's not going on was another.
We offered them the option of VPNM, removing IP trunks or CVM.

 

[Gibsonic]

that's not good to hear thephonemn...

ive set the main site with routes to all the remote sites, each ip line has "Voice Networking" disabled. I created all the necessary shortcodes to get extension dialing to each location.

We are still in the "rolling out" phase of this so i won't know for a little while if it's going to work or not.

btw...what software version were you running when you had so many problems with your setup?

 

[ThePhoneMn]

3.2.53 and 3.2.54. You should know very quickly if you are having issues.

 

[Gibsonic]

the first site is rolling out now (see my other thread about dual pri's) and the 2nd site will probably be in another week or two...so we have a quiet before the storm i guess.

 

[Gibsonic]

bump...

anyone got a link to some avaya provided documentation that says multiple VM Pro servers are not supported in a SCN? I'm going through the knowledge base and not finding any documenatation stating that.

much thanks...

 

[tlpeter]

it is in there

IP Office VoiceMail Pro 4.0 - Installation and Maintenance
| Back | Print | Feedback |


Restrictions
Only one Voicemail Pro server can be installed on a single Small Community Network (SCN).

Centralized Voicemail Pro is the only type of voicemail service that can run on a Small Community Network (SCN).

The number of simultaneous voicemail users is restricted by the Voicemail Pro license on the central system, up to the maximum number of data channels for voicemail supported by the central system's control unit.

For extensions on the remote system, access is also restricted by the number of available VoIP and VCM channels on that system.

Voicemail Lite and Embedded Voicemail cannot be used with Centralized Voicemail Pro.

Supported Remote IP Office Voicemail Features:
Not all Voicemail Pro features are available on the remote IP Office systems, for example hunt group queuing messages are not supported. Currently, the only features supported for remote sites are:

Automated Attendant.

Voice Messaging (leaving and collecting messages).

Call Recording.

Dial by Name Directory.






ACA - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[Shine52]

Look in the knowledge base. I looked under R3.2. It's under:

Voicemail/VM Pro Installation/Installing Centralized VM PRO/Restrictions

It says:
"IP Office Voicemail Pro 3.2 Installation and Maintenance Guide
| Back | Print | Feedback |


Restrictions
Only one Voicemail Pro server can be installed on a single Small Community Network (SCN).

Centralized Voicemail Pro is the only type of voicemail service that can run on a Small Community Network (SCN.

The number of simultaneous voicemail users is restricted by the Voicemail Pro license on the central system, up to the maximum number of data channels for voicemail supported by the central system's control unit.

For extensions on the remote system, access is also restricted by the number of available VoIP and VCM channels on that system.

Voicemail Lite and Embedded Voicemail cannot be used with Centralized Voicemail Pro.

Supported Remote IP Office Voicemail Features:
Not all Voicemail Pro features are available on the remote IP Office systems, for example hunt group queuing messages are not supported. Currently, the only features supported for remote sites are:

Automated Attendant.

Voice Messaging (leaving and collecting messages).

Call Recording.

Dial by Name Directory."




Figure it out damn-it!

 

[Gibsonic]

thanks guys, we are still deploying 3.1 so i was only looking in the 3.1 section of the knowledgebase...

3.1 doesn't have the 'Restrictions' layed out quite as nicely as 3.2 and 4.0.

duh! i should have looked at the other versions!

 

[jslewis]

I did this without scn, used qsig with a meshed routes from all sites, and shortcodes for extensions. Version 3.0.x, works great for 4 digit dialing, very robust.