Built a few separate conference bridges with secure pin for a customer per Kyle Holliday's original tek tips for building both the bridge with prompt for secure pin and another module for changing the pin.
Now, this works well. However, the customer then requested Name Announcement for conference participants and this is when I discovered the problem with entering the PIN, followed by the pressing of any key. Before, whether you entered the pin or the pin followed by any key, you entered the bridge with no announcement, it worked and was secure.
For the name announcement, I added a Voice Question, followed by a Whisper Action with auto accept transfer to the short code for the bridge. This works but only if the caller only enters the PIN (not followed by any other key). Furthermore, the whole process is a little slow even though I reduced the timing for the name recording and the timeout to the bridge to as short as possible. What is happening is when callers are dialing in they are sometimes entering the # sign after being prompted for the PIN (they are used to hitting # key with old conference service) and this is bypassing parts of the call flow. It's messy and bypasses the Voice question. They get a single conference beep, followed by a hold tone, then they eventually timeout to the bridge without a name announcement.
How can I keep my bridges and secure pin but add a name announcement that works and doesn't get bypassed in the call flow should the caller enter the PIN followed by any key ?
Now, this works well. However, the customer then requested Name Announcement for conference participants and this is when I discovered the problem with entering the PIN, followed by the pressing of any key. Before, whether you entered the pin or the pin followed by any key, you entered the bridge with no announcement, it worked and was secure.
For the name announcement, I added a Voice Question, followed by a Whisper Action with auto accept transfer to the short code for the bridge. This works but only if the caller only enters the PIN (not followed by any other key). Furthermore, the whole process is a little slow even though I reduced the timing for the name recording and the timeout to the bridge to as short as possible. What is happening is when callers are dialing in they are sometimes entering the # sign after being prompted for the PIN (they are used to hitting # key with old conference service) and this is bypassing parts of the call flow. It's messy and bypasses the Voice question. They get a single conference beep, followed by a hold tone, then they eventually timeout to the bridge without a name announcement.
How can I keep my bridges and secure pin but add a name announcement that works and doesn't get bypassed in the call flow should the caller enter the PIN followed by any key ?
