[Home]

Summary:ASTERISK-17349: calls not routing to polycom handset after transfer using softkeys
Reporter:Vic Kullin (vipkilla)Labels:
Date Opened:2011-02-03 15:53:38.000-0600Date Closed:2011-06-07 14:05:20
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Resources/res_agi
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) asterisk.trace.txt
Description:We are running asterisk 1.6 and AGI scripts for call flow. Because Polycom handset handles most of transfer when using soft keys, the AGI script is never notified of the handset hanging up after transfer is complete. Therefore AGI script believes handset is busy (487 Busy Here is sent) until the transferred call is terminated
Comments:By: David Woolley (davidw) 2011-02-04 05:53:39.000-0600

Your log is missing most of its newlines, and should have been an attachment.  However, it looks to me as though both Asterisk and the phone are sending BYE for the old leg.

By the way, by soft keys, what you mean is that it is doing a SIP attended transfer, rather than an Asterisk features one.
By: Vic Kullin (vipkilla) 2011-02-04 08:37:15.000-0600

Yes I mean the softkeys. Would you like me to attach a new trace?
By: David Woolley (davidw) 2011-02-04 08:42:45.000-0600

I imagine that other readers will find it much easier to read if you set up logger.conf to log to a file in sufficient detail, and then add the file as an attachment.  Do not zip it!

However, it is not clear to me what evidence you are providing that anything has gone wrong - the SIP trace looks correct.  It looks like a valid Refer/replaces transfer.
By: Vic Kullin (vipkilla) 2011-02-04 13:18:53.000-0600

Apologies, that was an inaccurate trace. Here is another one. Thank you
By: Vic Kullin (vipkilla) 2011-02-06 15:31:32.000-0600

Problem is Asterisk informs the AGI script of a new outbound call over the AGI connection, it doesn't tell the AGI script whether this call is going to be a transfer (and which call it's going to be a transfer for) or a plain outbound call. This is because both:

1. Asterisk probably doesn't know that this is going to be a transfer, as it has not yet received the REFER packet from the handset.

2. Asterisk's AGI mechanism was never designed with complex call flows in mind.
By: Leif Madsen (lmadsen) 2011-02-07 10:21:05.000-0600

This is not a bug:

<leifmadsen> how is asterisk supposed to know your call is a transfer or just another call?
<leifmadsen> the answer is, it can't -- if you need asterisk to know this is a transfer, you have to use the built in transfers