Re: [Asterisk-Users] problems with'#' transfer after hold...
Hi, (please be gentle - still learning :)) This may be similar to a problem I had today... Calling an automated phone system wanted me to press # to confirm a number - obviously * treats this a transfer - and relevant prompts were played... If you wait for this to 'time out' (or do an invalid extension) no more DTMF tones are sent down to the called number (I did a test calling to a mobile afterwards) - even a # doesn't provoke the correct response. A thought that came to mind on this was - how do you actually send down a # when requested by an automated service as * treats this as its own. But - looks like the question has been answered by Chris' reply with this ## patch :) - still - I dont know if that would fix the 'if you time out a transfer and then try to send DTMF tones they dont actually get sent' problem. So in answer to Chris question - I dont have this patch installed. Thanks Wayne. Stephen Hon wrote: Hi.. Has anybody been experiencing any problems with transfers using # to transfer after taking a call off of hold? Transfers using the # and music on hold work fine by themselves. However, when we place somebody on hold we can no longer use the # to transfer. This is a problem since we use the # button to park calls. So, say a call comes in, the operator is on a call already, places call on hold and answers the new call, places new call on hold, resumes old call and tries to transfer using the # button it wont work, itll just play the DTMF tone for the # button. At first, I thought somewhere along the line the Tt options must be messed up in a dial command somewhere.. but I double checked everywhere and ensured that I was enabling transfers. Does anybody have any suggestions? Thanks, Steve ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] problems with'#' transfer after hold...
The patch presents a dtmftimeout option in features.conf that deals with this issue. It defaults to half a second, but can be set to longer than that if necessary... If the length of time between # presses is longer than this value, then * assumes that it's NOT a transfer and sends the DTMF tone to the other end... if however the length is less then you hear Allison say Transfer and everything goes as you'd expect... -Chris - Original Message - From: Wayne [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, August 04, 2004 11:40 AM Subject: Re: [Asterisk-Users] problems with'#' transfer after hold... Hi, (please be gentle - still learning :)) This may be similar to a problem I had today... Calling an automated phone system wanted me to press # to confirm a number - obviously * treats this a transfer - and relevant prompts were played... If you wait for this to 'time out' (or do an invalid extension) no more DTMF tones are sent down to the called number (I did a test calling to a mobile afterwards) - even a # doesn't provoke the correct response. A thought that came to mind on this was - how do you actually send down a # when requested by an automated service as * treats this as its own. But - looks like the question has been answered by Chris' reply with this ## patch :) - still - I dont know if that would fix the 'if you time out a transfer and then try to send DTMF tones they dont actually get sent' problem. So in answer to Chris question - I dont have this patch installed. Thanks Wayne. Stephen Hon wrote: Hi.. Has anybody been experiencing any problems with transfers using # to transfer after taking a call off of hold? Transfers using the # and music on hold work fine by themselves. However, when we place somebody on hold we can no longer use the # to transfer. This is a problem since we use the # button to park calls. So, say a call comes in, the operator is on a call already, places call on hold and answers the new call, places new call on hold, resumes old call and tries to transfer using the # button it wont work, itll just play the DTMF tone for the # button. At first, I thought somewhere along the line the Tt options must be messed up in a dial command somewhere.. but I double checked everywhere and ensured that I was enabling transfers. Does anybody have any suggestions? Thanks, Steve ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[Asterisk-Users] problems with'#' transfer after hold...
Hi.. Has anybody been experiencing any problems with transfers using # to transfer after taking a call off of hold? Transfers using the # and music on hold work fine by themselves. However, when we place somebody on hold we can no longer use the # to transfer. This is a problem since we use the # button to park calls. So, say a call comes in, the operator is on a call already, places call on hold and answers the new call, places new call on hold, resumes old call and tries to transfer using the # button it wont work, itll just play the DTMF tone for the # button. At first, I thought somewhere along the line the Tt options must be messed up in a dial command somewhere.. but I double checked everywhere and ensured that I was enabling transfers. Does anybody have any suggestions? Thanks, Steve
Re: [Asterisk-Users] problems with'#' transfer after hold...
- Original Message - From: Stephen Hon To: [EMAIL PROTECTED] Sent: Tuesday, August 03, 2004 3:48 PM Subject: [Asterisk-Users] problems with'#' transfer after hold... Hi.. Has anybody been experiencing any problems with transfers using # to transfer after taking a call off of hold? Transfers using the # and music on hold work fine by themselves. However, when we place somebody on hold we can no longer use the # to transfer. This is a problem since we use the # button to park calls. So, say a call comes in, the operator is on a call already, places call on hold and answers the new call, places new call on hold, resumes old call and tries to transfer using the # button. it won't work, it'll just play the DTMF tone for the # button. At first, I thought somewhere along the line the 'Tt' options must be messed up in a dial command somewhere.. but I double checked everywhere and ensured that I was enabling transfers. Does anybody have any suggestions? Thanks, Steve Are you using the double ## transfer patch or just the regular single # that comes with CVS? -Chris ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
