[asterisk-bugs] [Asterisk 0014266]: [patch] Add the immediate=yes option to chan_iax2

[Asterisk Bug Tracker]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=14266 
====================================================================== 
Reported By:                jcovert
Assigned To:                dvossel
====================================================================== 
Project:                    Asterisk
Issue ID:                   14266
Category:                   Channels/chan_iax2
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.6.0.3 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-01-18 16:21 CST
Last Modified:              2009-02-06 14:12 CST
====================================================================== 
Summary:                    [patch] Add the immediate=yes option to chan_iax2
Description: 
IAX phones and devices (such as the IAXy) are cool.  When you pick up the
phone, a message is sent (even before you dial), and just like on the DAHDI
FSX devices, code gets executed.

DAHDI has "immediate=yes" so that when you pick up the phone, you get
connected directly to the "s" extension.  This is useful for lobby phones,
elevator phones, manual service (number please), etc.

It was nearly trivial to implement in chan_iax2.c.  I made a deliberate
decision to only implement it for users/friends who authenticate (as any
properly connected phone or ATA would).  Simply add "immediate=yes" in the
friend or user definition, and when you pick up the phone, instead of
dialtone, you go right to extension "s" in the appropriate context.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-02-06 14:12 svnbot         Status                   confirmed => assigned
2009-02-06 14:12 svnbot         Status                   assigned => resolved
2009-02-06 14:12 svnbot         Resolution               open => fixed       
======================================================================