Octavio Ruiz (Ta^3)
2007-Mar-12 11:12 UTC
[asterisk-users] deprecated ALERT_INFO var andAMI's Originate command
Since 1.4 ALERT_INFO variable has been deprecated. I used to send this via AMI: Action: Originate Channel: Sip/1234 Application: AgentLogin Data: 1234 Variable: _ALERT_INFO=info=alert-autoanswer Callerid: AutoLogin[1234] In order to send an autologin and autoanswer call to the agent 1234 on an Aastra phone at extension 1234. (just for example). Now in * 1.4 with ALERT_INFO deprecated I don't have that option, rather than calling a Local/ channel to SetSIPheaders() and Dial(). I don't want to do it in that fashion 'cos I like (and have) to have completely separated dial plan logic (extensions.conf) and external applications via AMI. Regards, -- I'm having a MID-WEEK CRISIS!
Olle E Johansson
2007-Mar-12 14:03 UTC
[asterisk-users] deprecated ALERT_INFO var andAMI's Originate command
12 mar 2007 kl. 19.16 skrev Octavio Ruiz (Ta^3):> Since 1.4 ALERT_INFO variable has been deprecated. I used to send this > via AMI: > > Action: Originate > Channel: Sip/1234 > Application: AgentLogin > Data: 1234 > Variable: _ALERT_INFO=info=alert-autoanswer > Callerid: AutoLogin[1234] > > In order to send an autologin and autoanswer call to the agent 1234 > on an > Aastra phone at extension 1234. (just for example). > > Now in * 1.4 with ALERT_INFO deprecated I don't have that option, > rather > than calling a Local/ channel to SetSIPheaders() and Dial(). I > don't want > to do it in that fashion 'cos I like (and have) to have completely > separated > dial plan logic (extensions.conf) and external applications via AMI. >You can still add a variable like that, since sipaddheader is based on using channel variables. If you add _SIPADDHEADER55 it will be used. Feel free to replace "55" with any two-digit number, as long as it's unique. This is how the SIP addheader functionality works on the inside. /O