# key problem with some audio elements

[cdnadmin]

This document was generated from CDN thread

Created by: Steve Weber on 10-02-2010 01:34:37 PM
Hi,
 
I have inherited a Call Studio project from a consulting firm. The project was working fine. They I received calls from the QA folks that the # key was not taking them back to the main menu on some menus. The # is working on other menus in the same project. The first thing I thought is that there may be a hotlink with a # key. Nope. Then I turned off the hotlink option on one of the audio elements in question. No good. Then I changed the key from # to 2. That works. Change back to #. No good.
 
Have any of you seen this before? Any ideas as to what's going on? I'm new to Call Studio so I'm sure there are things I'm not aware of.
 
We're using Call Studio 6 with CVP 4.1
 
I'd appreciate any help or suggestions.
 
Thanks.
 
 

Subject: Re: New Message from Steve Weber in Customer Voice Portal (CVP) - CVP - All
Replied by: Janine Graves on 10-02-2010 03:46:55 PM
If the # key works in some elements, but not in others, and if the 2 key
works where the # key doesn't, then it's most likely that the # key is
set as the 'termchar' key by default - which means that the gateway
assumes it's a terminating character and strips it off, so you're not
receiving it into the application.

If the # key works within some elements, but not others, then look in
the Settings tab of the elements where it works. Most likely at the
bottom of the settings tab, where it says VoiceXML Property, they've set
'termchar' to the value '  '   (blank space) or something similar to
disable its use as the terminating character. Then the gateway receives
it as if it's a regular DTMF tone and sends it to the application.

So, I'd recommend that within each element that needs to receive the #,
you set the VoiceXML Property 'termchar'  to  the value ' '  (omit the
single quotes in both cases).

If you want the termchar to ALWAYS be disabled, then you can set it once
in the Project / Properties /  Root Doc Settings.

Janine

Cisco Developer Community Forums wrote:
> Steve Weber has created a new message in the forum "CVP - All Versions":
>
> --------------------------------------------------------------
> Hi,
> Â
> I have inherited a Call Studio project from a consulting firm. The
> project was working fine. They I received calls from the QA folks that
> the # key was not taking them back to the main menu on some menus. The
> # is working on other menus in the same project. The first thing I
> thought is that there may be a hotlink with a # key. Nope. Then I
> turned off the hotlink option on one of the audio elements in
> question. No good. Then I changed the key from # to 2. That works.
> Change back to #. No good.
> Â
> Have any of you seen this before? Any ideas as to what's going
> on? I'm new to Call Studio so I'm sure there are things I'm not aware of.
> Â
> We're using Call Studio 6 with CVP 4.1
> Â
> I'd appreciate any help or suggestions.
> Â
> Thanks.
> Â
> Â
> --
> To respond to this post, please click the following link:
>
> <http://developer.cisco.com/web/cvp/forums/-/message_boards/message/1958584>
>
> or simply reply to this email.

Subject: RE: Re: New Message from Steve Weber in Customer Voice Portal (CVP) - CVP -
Replied by: Steve Weber on 11-02-2010 04:20:20 PM
Sure enough the audio element did not have the termchar VoiceXML property. After I put the property in it worked just fine.
 
Thank you so much for you're help Janine. There is no way I would have figured it out on my own.
 

If the # key works in some elements, but not in others, and if the 2 key
works where the # key doesn't, then it's most likely that the # key is
set as the 'termchar' key by default - which means that the gateway
assumes it's a terminating character and strips it off, so you're not
receiving it into the application.

If the # key works within some elements, but not others, then look in
the Settings tab of the elements where it works. Most likely at the
bottom of the settings tab, where it says VoiceXML Property, they've set
'termchar' to the value ' ' (blank space) or something similar to
disable its use as the terminating character. Then the gateway receives
it as if it's a regular DTMF tone and sends it to the application.

So, I'd recommend that within each element that needs to receive the #,
you set the VoiceXML Property 'termchar' to the value ' ' (omit the
single quotes in both cases).

If you want the termchar to ALWAYS be disabled, then you can set it once
in the Project / Properties / Root Doc Settings.

Janine

Cisco Developer Community Forums wrote:
> Steve Weber has created a new message in the forum "CVP - All Versions":
>
> --------------------------------------------------------------
> Hi,
> Â
> I have inherited a Call Studio project from a consulting firm. The
> project was working fine. They I received calls from the QA folks that
> the # key was not taking them back to the main menu on some menus. The
> # is working on other menus in the same project. The first thing I
> thought is that there may be a hotlink with a # key. Nope. Then I
> turned off the hotlink option on one of the audio elements in
> question. No good. Then I changed the key from # to 2. That works.
> Change back to #. No good.
> Â
> Have any of you seen this before? Any ideas as to what's going
> on? I'm new to Call Studio so I'm sure there are things I'm not aware of.
> Â
> We're using Call Studio 6 with CVP 4.1
> Â
> I'd appreciate any help or suggestions.
> Â
> Thanks.
> Â
> Â
> --
> To respond to this post, please click the following link:
>
> <http://developer.cisco.com/web/cvp/forums/-/message_boards/message/1958584>
>
> or simply reply to this email.