IP Office/VM Pro Dial By Name

[danielwestendorf]

Hey all,

I've got two IP Office/VM Pro setups. Both have the Dial by Name feature set up in the AA. One of them works as expected, you dial the users first name, then it plays back the user's RECORDED name. On the other system, you dial their name, but then the extension number is recited instead of the recorded name. I have double and triple check that all valid extensions have a name recorded for it. Anyone have and ideas why it lists the extension instead of playing back the recorded name? I can't seem to find many configurable options on this, so I don't know why they would be different...

Thanks for the help!

Daniel

 

[gknight1]

i have you tried stopping and restarting the voicemail services? what about deleting that users account folder and starting from scratch for that user?

 

[danielwestendorf]

Yes, I have rebooted the VMPro server several times. It does this for every user under this IP Office system. It never plays a User's recorded name, ever. It just says the extension.

Thanks,

Daniel

 

[gknight1]

what version of voicemail and in what mode are you running?

 

[kwing112000]

What release are these systems. I think there is something new in 4.1 that allows you to change this.

 

[danielwestendorf]

Voicemail Pro version 3.0.13
What do you mean by mode?

 

[danielwestendorf]

IP Office is 3.1 also.

 

[gknight1]

open voicemail pro client,

its under Administration, Preferences, General

What is your Default Telephony Interface?

 

[danielwestendorf]

The Default Telephony Interface is set to Intuity. The system that does work properly also has this same setting.

 

[aarenot]

Do the IPO releases, and the VMPRO releases match?

 

[aarenot]

In manager, got to file, advanced, upgrade, may have to select the system to upgrade. You can cancel before selecting modules to upgrade, and hitting OK, and it will not do any upgrading so dont worry about it.


The current release should be listed there. let us know what it is. Sounds like your VM never got upgraded when your IPO did, and that is a big NO NO. That is technical term for unsupported.

 

[intrigrant]

Does both VM Pro services start with a user account or with the system account. I have seen strange behaviour if the service starts with with the system account.

NIHIL NOVI SUB SOLE

 

[danielwestendorf]

aarenot: I checked, and the version is listed as 3.1[65].

We recently connected the two sites using voice compression modules. This was all outsourced through a local Avaya Telecom company. When we upgraded our IPO, I asked the tech about upgrading the VM Pro, he said that it is never done.

Back to the topic though, this was happening when all the versions where the same.

intrigrant: both systems are running their services under the system account.

Any other ideas would be great!

Thanks,

Daniel

 

[aarenot]

daniel,
Basic IPO 101, all the software releases on all system components should be of the same release. This would include, but not be limited to IPO, VMPRO, CCC, Delta, and all user software( soft console, phone manager), as well as admin software( manager, VMPRO client).

There is no excuse for the tech not upgrading the VMPRO from 3.0 to 3.1 when they upgraded the IPO from 3.0 to 3.1

Is it the mismatched IPO, and VMPRO which are displaying this issue? Also, am I to understand you have two VMPROS running in an SCN?

 

[Sorpio]

hey daniel, be aware of aarenot´s last question!

 

[danielwestendorf]

I don't think it is the version mismatch that is causing the problem, as it has always been this way (since purchase and set up). I will make sure to upgrade the VMPRO though.

I have two completely independent IPO(2) and VMPRO(2) systems at two different sites. The only connectivity they have is for site to site calls via voice compression modules.

Both IPO systems are at 3.1

 

[danielwestendorf]

I didn't fully answer that last question.

Yes, the system with the mismatched versions is the one with the problem.

 

[gknight1]

if you look in the voip line tab, is the scn box checked? if the scn box is checked that where your problem might be coming from? you are not supposed to have 2 voicemail pros on 1 scn. some people might say it will work, but it is not supported. make sure those scn boxes are not checked.

 

[danielwestendorf]

These two systems are not networked together. They do not talk or exchange information. The only communication between AT ALL is via an occasional VOIP call. Nothing else.

 

[aarenot]

daniel,
Check out gknights last post , and respond it will tell us if the systems are configured as part of a small community network in regard to the IPO settings. This could be the case if the LAN's are connected physicaly, or virtualy, VPN.

Also, from your phone dial the user number of another user at the other site, and have system status open telling us what it showed.