-
1
- #1
Richard10d
Systems Engineer
This is an FYI for anyone who may be having the problem my customer did.
When my customer would call their clients who had Comcast and get voicemail, right near the end of the call it was as if the D160 would press #. This would cause the remote voicemail to assume the caller (my client) wanted to remotely administer the mailbox. The problem only showed when calling Comcast people with voicemail. With wireshark I was able to see that there was "echo" being sent by the D100 and that the "#" tone was actually in the end of the VM greeting recording and was being echo'd back to the client. It took awhile to get support to recognize what was happening, finally they passed it to the D100 team who produced a patch (new D100 firmware) for my client. It worked. It will be in 9.1.8.
If this sounds like a problem you have had with the D100/160 I can get you a trouble ticket number so you can open a case with Avaya to acquire the update.
Hope this may be of use to someone.
When my customer would call their clients who had Comcast and get voicemail, right near the end of the call it was as if the D160 would press #. This would cause the remote voicemail to assume the caller (my client) wanted to remotely administer the mailbox. The problem only showed when calling Comcast people with voicemail. With wireshark I was able to see that there was "echo" being sent by the D100 and that the "#" tone was actually in the end of the VM greeting recording and was being echo'd back to the client. It took awhile to get support to recognize what was happening, finally they passed it to the D100 team who produced a patch (new D100 firmware) for my client. It worked. It will be in 9.1.8.
If this sounds like a problem you have had with the D100/160 I can get you a trouble ticket number so you can open a case with Avaya to acquire the update.
Hope this may be of use to someone.