I am attempting to implement Nerdvittle's Call Reminders on my * 1.2.12.1 PBX. It has 8 Zaptel trunks provided by 2 Digium TDM400P cards. If I use the call reminders internally, it works flawlessly. The problem happens when I set the call-back number to an external number so that the call goes out the Zaptel trunk. The reminder message starts playing before the person being called picks up the phone. As a result, the person picks up the phone and either hears only part of the message or just gets the menu prompt. What appears to be happening is that the reminder script simply waits for a connected call, then starts playing it's message, but * reports a connected call when it connects to the trunk, not when the other party picks up. The result is the message starts playing while the remote phone is still ringing. I was wondering if anyone had any suggestions on how to work around this problem. The only thing I can think of that is within my ability is to repeatedly play a prompt to press a number to hear the message. However, this is not a good solution since this system is going to be used to automate patient appointment reminders, and I don't want it sounding like a sales call that will cause people to just hang up without listening first. My other thought is to perhaps wait until it hears a word spoken, but I don't know how to do that and have the system distinguish between a spoken word and the sound of the ring indicator. Of course, I'm open to any other suggestions as well. John
John McCollough wrote:> I was wondering if anyone had any suggestions on how to work around this > problem. The only thing I can think of that is within my ability is to >The common work around for analog lines it to loop a message asking the caller to press 1 to accept the call. Loop it long enough that the caller has time to respond. I used to loop 5 times before hanging. After I moved to a PRI, it was no longer necessary. Doug -- Ben Franklin quote: "Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety."
On Wednesday 25 October 2006 09:20, John McCollough wrote:> What appears to be happening is that the reminder script simply waits > for a connected call, then starts playing it's message, but * reports a > connected call when it connects to the trunk, not when the other party > picks up. The result is the message starts playing while the remote > phone is still ringing.If you're playing out of a POTS interface, that's about as good as you can get... You can Wait() but POTS has no real answer supervision. As soon as the line is dialed it is considered answered.> I was wondering if anyone had any suggestions on how to work around this > problem. The only thing I can think of that is within my ability is to > repeatedly play a prompt to press a number to hear the message. > However, this is not a good solution since this system is going to be > used to automate patient appointment reminders, and I don't want it > sounding like a sales call that will cause people to just hang up > without listening first. My other thought is to perhaps wait until it > hears a word spoken, but I don't know how to do that and have the system > distinguish between a spoken word and the sound of the ring indicator. > Of course, I'm open to any other suggestions as well.There is an app called amd - answering machine detection. You could modify this app to listen for voice energy and only continue after the person on the other end stops talking (person or machine). -A.