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

 

[ronromano]

You recently connected the sites? Are all the names unique for both sites? No match name on a and b?

 

[gknight1]

same thing with hunt group and extension numbers, all need to be unique

 

[danielwestendorf]

Everything is unique. No matching numbers or anything. The two sites are not connected, they are on different networks and communicate via a VPN that is NOT configured through IPO.

Like I said before, this was a problem BEFORE we added the connectivity of the two sites, so we can pretty much rule out that as the cause.

If you need clarification as to what the problem is, you can call each phone system.

Site A (the one with the problem)
Toll Free - 800.292.5874
Opt. 9

Site B (the one that works fine)
801.394.0865
Opt. 8

Thanks again for the help guys!

 

[ronromano]

If I gotta call in I gotta get paid.

 

[danielwestendorf]

I was providing an option, not asking anyone to work for free. It just seem that this post is working it's way from the original problem.

 

[ronromano]

relax

 

[aarenot]

First thing is that you should upgrade the VMPRO to a supported release for your IPO.

Second is for you to anwer gknights question, so we can procede.
the upgrade can wait, but we need the answer to gknights question

 

[danielwestendorf]

No the SCN box is not checked on either system.
Thanks again guys,

Daniel

 

[ProviderReborn]

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.

Its suprising how versions differ. Whilst I am guilty of posting up a thread before upgading a site the other day. I would advice you be belt and braces and have the VM of this site upgraded to the version which matches the GA release of your IP Office, To be even more thorough I would possibly think about getting another Avaya BP to come in and upgrade to the latest 3.2 build (I say another as if the guys that came in and run half an upgrade I personally would be looking else where) At least then if its still not working they can raise it direct with Avaya or with their distribution network.

One thing I havent seen any one ask is does this site have names recorded for their VM Boxes?

ACA - IP Office Implement
ACA - IP Telephony
ACS - IP Office Implement
CCNA - Working towards.

 

[danielwestendorf]

Yes, everyone does have their names recorded, so no easy save there.

If no one has any other insight into the problem other than the mismatching version numbers, then I guess I will go the upgrade route (with someone else for sure).

Thanks again,

Daniel

 

[aarenot]

Daniel,
I would suggest if you did not check on both IPO's the SCN box in all the VOIP lines on both systems. Just making sure, you know how it goes if you do support, you have to be a little anal.

With the IPO 101 errors you have mentioned from your previous service providor, I would not be suprised if the VMPRO was not installed properly as the issue here. If the upgrade the new vendor does doesn't fix it, they may need to default your VMPRO, and start over programming it. If they do not know better than what you have said, they may have corrupted the VMPRO config, or even the IPO config which it serves.

If you want to drop me an email, same name at msn dot com. I can probably know a good tech in your area. I have installed, serviced, or programmed systems in about 20 states so I know a few techs around North America.

 

[gknight1]

like i said before, have you tried deleting someones account folder and then let it recreate it and re-record the name and try again.

 

[danielwestendorf]

Thanks for the offer aarenot, I might hit you up on that. I'm out in Sun Valley, Idaho. The nearest Avaya BP is in Boise, almost 3 hours away.

gknight1: I thought I had tried it before, but I did it again just to make sure. No magic.

Daniel

 

[danielwestendorf]

I upgraded everything to 3.2 and that still didn't fix it.

BUT, with the new Manager alerting me to errors, I was able to fix the issue.

All of the User's Names included a period after last initial. (i.e. Daniel W.)

I removed the period and what do ya know?!? It worked. I had to rename all of the greeting recordings and what not, which was a pain, but I got it all fixed up.

Daniel

 

[aarenot]

THIS IS A MISTAKE THAT EVEN MOST ROOKIES DO NOT MAKE! I WOULD NOT LET THAT VENDOR ON YOUR PROPERTY EVER AGAIN.