asterisk users - Aug 2004 - 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

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20040803/c63cfed6/attachment.htm

----- Original Message -----
From: Stephen Hon
To: asterisk-users@lists.digium.com
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

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 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
>