Forward message in voicemail returns extension not valid 1

[Geneapi]

Hi Everyone,
I have come across an issue where we tried to forward a message from a voicemail box to our other facility and what I get in an "Extension not Valid" response. We have 2 facilities with the same Avaya equipment (IP406DS- Ver 5.0 (15))with 4 digit extension #'s (5XXX here & 4XXX there) and I can forward the message to any phone in our facility but not to any in the other, I am not sure if this can be done any help would be appreciated. I have spent over 3 hours combing thru FAQ's with no match, unless someone else knows where I can look I would again appreciate for your input.

Thanks in advance

 

[yankblan]

If the voicemail is embedded (which I guess it is), no you can't.

Embedded can't be networked, you need VM Pro.

ACSS-SME

http://interconnexionsld.ca/

 

[Geneapi]

Sorry I forgot to mention that we are using Voicemail pro on each site

 

[yankblan]

Then use email. You should use centralized VM Pro, instead of two independant entities.

ACSS-SME

http://interconnexionsld.ca/

 

[Geneapi]

Hello Yankblan,

The decision for each site was done before me, by higher ups so stuck with it, I am not sure what you mean by use email, how would that work? if you don't mind helping me out.​

 

[yankblan]

I mean, use vmail to email, and then transfer the email.

Having two VM Pros is the same as having two embedded; they do not interact. VM Pro A has no idea who extension 5XXX as he looks at his own system. In fact, it does not look up the extension, but the user. So even if you do a SC 5XXX that transfers over SCN trunk X to the real 5XXX, it won't work.

ACSS-SME

http://interconnexionsld.ca/

 

[Geneapi]

OK, Thanks, I'll give that a try, again thanks for your input.

 

[smokinjoe2938]

Maybe because of this issue you may now be able to convince upper management to centralize the voicemail pro for site B, this will save you a ton of headaches going forward, and if your voicemail pro ever crashes you will have a spare voicemail pro on site.

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.

 

[Albus2]

406DS and Rel 5.0 is old, not supported and lacks new features, in addition, you have to get 'new' phones from second market suppliers. Why not think about upgrading your systems?
Get new IP500v2 units, swap the existing license to a new SD-Card and add Essential Edition licenses plusa few SCN-Licenses.
Now you can setup the systems to backup each others for extension, users, groups and voice mail. Its possible to roam (hot-desk) between facility's. Regarding voice mail with two VMPro's one is the central voice mail and the other is the backup (or distributed VM, depending on how it is desired).
This brings you a supported system with support for the latest phone types and features plus a nice redundancy.

 

[amriddle01]

406DS and Rel 5.0 is old, not supported and lacks new features

A brand new 500v2 bought through official channels (by a registered Avaya BP that has paid for training and renewing certifications etc) loaded with the latest R9 isn't supported by Avaya at all anyway.... so no loss there, but the new features/handsets may be worth it