Fixing Dial By Name

[PhoneNewbie]

Hi,

I have two sites (not linked) running Avaya IP Office systems. One site has version 3.1.21 of the Voicemail Pro and the other has version 3.0.13.

At the site running 3.1.21, when I use the dial by name and enter the name... I get the person's name when I get a match. IE: Press 1 for John Doe. At the site running 3.0.13, I get "Press 1 for extension 1234". On both sites, I have a name recorded in the users' voicemails for the ones I'm trying.

Is there a config option I'm missing somewhere to announce the name? If not, what is involved with upgrading to the newer version to add the functionality?

Thanks,

db

 

[gknight1]

are you sure there name is recorded, may be try re-recording that persons name?

 

[PhoneNewbie]

I've tried re-recording (VM -> Option 5, Option 5)...maybe my problem is the recordings aren't saving? How can I check to see if the name recorded actual saved?

 

[gknight1]

you can look in the name folder.

C:\Program Files\Avaya\IP Office\Voicemail Pro\VM\Names

 

[PhoneNewbie]

Well, the names are recorded and play correctly from the wav files in that dir. Any ideas why the autoattendant doesn't use them when you select a name?

 

[ronromano]

Are you using the directory for both first an last names? Make sure each path is set for the proper name i.e. first or last.

 

[PhoneNewbie]

Hi,

Thanks for the comments all. The phone system does correctly transfer to the right person by both first and last so that part is good. What is not good is that if you have multiple matches, I get "Press 1 for ext 1234. Press 2 for ext 1235". The customer won't know who those extensions are attached to.

At our other site, everything works correctly with "Press 1 for John Doe (recorded name). Press 2 for Jane Doe.". I'm just trying to figure out if I have a misconfiguration (both look the same) or if it's an issue with the version of VM Pro I'm using. Thanks again for the help,

db

 

[ronromano]

I just dialed in and tried minr and its not working at all 3.2.28.4 Very odd. Now I have another thing to figure out.

Thanks.

 

[ronromano]

Sorry not 3.2.28.4, its 3.2.15 don't want to scare the hell out of anyone out there Sorry.

 

[ronromano]

just upgraded to 3.2.28.4 no problems now. Sorry I'm of no help.