VMPro DialByName bug when leaving Voicemail 3

[Richard10d]

I have a customer with a 500v2 and Voicemail Pro. They have always been on 11.1.x, currently on 11.1.2.4. Occasionally someone would leave a voicemail and the user could not listen to it using Visual Voicemail. It used to cause the phone to say "Busy" when pressing Visual Voicemail, now it just shows nothing next to listen instead of something like "1/0/0".

Today I figured out that when the caller gets to the users extension via "DialByName" is when it breaks. I see in the header "DialByName ($)" where it should show the caller id inside the WAV file (I converted them from OPUS to WAV wondering if that was the issue). When I leave a voicemail without DialByName it works as expected. The only fix is for them to dial *17 and delete the offending voicemail via the TUI.

Anyone else run into this?

I do have a SR open with Avaya and I expect a fix for this at some point.

 

[Richard10d]

Ah, the power of borrowing. So the module that was doing the final transfer after dial by name literally said "DialByName ($)" in the source of transfer. I suspect IP Office was getting hung up on the $ in the header of the audio file and that's how it choked. I changed it to $CLID and they don't have an issue anymore. Hope that helps someone else in the future.

 

[sizbut]

Cheers for sharing the issue resolution.

Stuck in a never ending cycle of file copying.