Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Auto Attendant Message looping

Status
Not open for further replies.

czinck

IS-IT--Management
Oct 30, 2003
17
CA
Hi,

Has anyone seen a circumstance where the auto attendant message will stop playing in the middle and then restart from the beginning? This problem happens intermittantly and once it loops for an incoming call it will continue looping in the same way until a selection is entered. And when it loops, it always stops and loops in the same place in the message.

We're running 2.1.24 with VM Pro 2.1.10

Thanks in advance for the help,
Chris Zinck
Zinck Computer Group


 
Update:

It turns out the message does not always loop forever once it starts looping. I've had it stop looping after 2 loops and once after 4 loops.

Since the attendant script in VM is set to allow selections while the message is playing AND it stops at exactly the same spot when it loops AND it acts exactly the same as if an invalid selection was made, could this be an example of the freq of the voice coming close to a touch tone?

Thanks in advance,
Chris Zinck
 
Yes, I've been fighting EXACTLY this same problem for the last week, also running 2.1.24 with VM Pro 2.1.10. At least in my case, it's definitely the voice in the prompt begin interpreted as a DTMF tone (it's always the digit 5 in my case). If I turn off "tones can interrupt prompt" then it doesn't happen. The really curious thing is that if I restart the VMPro service, the first time the autoattendant is played is does NOT behave this way, but it does for all subsequent tries -- hence, I'm beginning to think it's a bug somewhere in VMPro. I tried filtering the .wav file for different frequencies, and it helped in some situations, but still breaks for cell phone users, etc.

I wish I could be more help here, but at least you know you're not alone :)
 
Sounds like the reason is 2.1.24, once again

Soopa Doopa Intergalactic IP Office installation mechanic and configuration corruptor from way back.
 
We have re-recorded the message and so far it seems to be much better. Although, with the way it was so intermittant I won't be convinced until we've run it for a bunch of days.

I was strange because I upgraded the system to 2.1.10 VM and 2.1.24 early last week and we didn't really see the problem until Monday this week.

Anyway, crossing fingers, re-recording seems to have fixed it.

Thanks for your help,
Chris Zinck
 
I had that problem and I figured out in my case it was a bleed over problem caused by me using internal lines to call out on an analog trunk to the PSTN and back into the IP Office. The problem would worsen if we tried this from multiple phones at the same time. We were using ATM 16 modules which have all sorts of Grimlins in them. As soon as we started using a T1 the problem went away. Also if we only used our cell phones to test the auto-attendant the issue would go away. Also check to make sure you dont have any bleeps or stray tones in your AA recording. Using a call flow to record your recordings rather than the recording application in VM Pro seemed to cause problems.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top