[asterisk-dev] 302 redirects ocassionally ignored; hypothesis: later queued busy preferred to earlier early media frame

[Dave WOOLLEY]

David wrote:
> 
> Richard wrote:
> 
> > Without looking into the code, queueing a busy frame to wake up the
> > read thread and look at the call-forward string seems wrong.  The null
> > frame should be queued instead.
> 
> This is the code from branch 11 SVN (branch 12 seems to be the same).
> Whilst it is done as a drop through, part of the logic may be to provide and
> appropriate behaviour if redirects have been disabled at a higher level.
> change_redirecting_information eventually sets the field containing the
> address information that Dial uses to detect the redirection.

Sending a null frame followed by the busy might be a safer way of making the change.
-- 
David Woolley
BTS Holdings Plc
Tel: +44 (0)20 8401 9000 Fax: +44 (0)20 8401 9100
http://www.bts.co.uk

BTS Holdings PLC - Registered office: BTS House, Manor Road, Wallington, SM6 0DD - Registered in England: 1517630