VoiceGuide IVR Software Main Page
Jump to content

Not Responding To # Key

Recommended Posts

Our system is no longer responding to the pound key.

We give the option to press a key for a department or press # for the voicemail system.

I have included the event trace file from a test.

I pressed # serveral times and then pressed 1 to show a working transfer.

0330vgm.txt

Share this post


Link to post

The trace shows that VG was advised while playing a message in module [store Open] that the # key was pressed by the caller:

 

142420.00 6 [store Open] Playing

...

142430.26 6 dtmf # (65997,35,2)

...

142431.79 6 dtmf # (65997,35,2)

 

We see in module [store Open] that the "on {#} ..." path points to a module named [VoiceMail 200] :

 

on {#} goto [VoiceMail 200]

 

could you please try naming the module something else - eg: "[VM 200]" the word "Voicemail" at the start of module name may be getting confused with the VoiceGuide Voicemail system destination paths - which are all beginning with a word "Voicemail"...

Share this post


Link to post

Thank you,

 

Changing it from "VoiceMail 200" to "VM 200" corrected it.

Must be a current version issue, this did work before.

 

Thanks

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×