asterisk users - Sep 2005 - Working example of ALERT_INFO with Cisco ATAs?

I am wondering if there are any tricks getting the Cisco ATAs to do 
"distinctive rings" via the ALERT_INFO variable?

I have seen some contradictory information in the Wiki, and I tried the 
example there.  I then sniffed the connection between the server and the 
ATA and didn't see the header sent like it is "supposed" to be.

If someone out there has a handle on this and would be willing to help, 
I'd sure appreciate it.

I'm doing this right now with ARA; the table entry in question looks 
like this (sorry about linewrap):

  exten  | priority |      app       |         appdata
--------+----------+----------------+-------------------------
  brianc | 1        | SetMusicOnHold | native-random
  brianc | 2        | SetVar         | ALERT_INFO=Bellcore-dr2
  brianc | 3        | NoOp           | ${ALERT_INFO}
  brianc | 4        | Dial           | SIP/ata1|23|t

At priority 3 I can see that the variable has been set correctly, but 
nothing ever gets sent out.  Everything else (e.g. the MOH) works just fine.

I'm much obliged for any help that might be lurking out there.

Thanks.

B.

I always use _ALERT_INFO
> -----Original Message-----
> From: asterisk-users-bounces@lists.digium.com 
> [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of 
> Brian Capouch
> Sent: Wednesday, September 07, 2005 12:37 AM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: [Asterisk-Users] Working example of ALERT_INFO with 
> Cisco ATAs?
> 
> I am wondering if there are any tricks getting the Cisco ATAs 
> to do "distinctive rings" via the ALERT_INFO variable?
> 
> I have seen some contradictory information in the Wiki, and I 
> tried the example there.  I then sniffed the connection 
> between the server and the ATA and didn't see the header sent 
> like it is "supposed" to be.
> 
> If someone out there has a handle on this and would be 
> willing to help, I'd sure appreciate it.
> 
> I'm doing this right now with ARA; the table entry in 
> question looks like this (sorry about linewrap):
> 
>   exten  | priority |      app       |         appdata
> --------+----------+----------------+-------------------------
>   brianc | 1        | SetMusicOnHold | native-random
>   brianc | 2        | SetVar         | ALERT_INFO=Bellcore-dr2
>   brianc | 3        | NoOp           | ${ALERT_INFO}
>   brianc | 4        | Dial           | SIP/ata1|23|t
> 
> At priority 3 I can see that the variable has been set 
> correctly, but nothing ever gets sent out.  Everything else 
> (e.g. the MOH) works just fine.
> 
> I'm much obliged for any help that might be lurking out there.
> 
> Thanks.
> 
> B.
> _______________________________________________
> --Bandwidth and Colocation sponsored by Easynews.com --
> 
> Asterisk-Users mailing list
> Asterisk-Users@lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
> 
>

Brian Capouch wrote:
> I am wondering if there are any tricks getting the Cisco ATAs to do
> "distinctive rings" via the ALERT_INFO variable?
> 
> I have seen some contradictory information in the Wiki, and I tried the
> example there.  I then sniffed the connection between the server and the
> ATA and didn't see the header sent like it is "supposed" to
be.
> 
> If someone out there has a handle on this and would be willing to help,
> I'd sure appreciate it.
> 
> I'm doing this right now with ARA; the table entry in question looks
> like this (sorry about linewrap):
> 
>  exten  | priority |      app       |         appdata
> --------+----------+----------------+-------------------------
>  brianc | 1        | SetMusicOnHold | native-random
>  brianc | 2        | SetVar         | ALERT_INFO=Bellcore-dr2
>  brianc | 3        | NoOp           | ${ALERT_INFO}
>  brianc | 4        | Dial           | SIP/ata1|23|t
> 
> At priority 3 I can see that the variable has been set correctly, but
> nothing ever gets sent out.  Everything else (e.g. the MOH) works just
> fine.
> 
> I'm much obliged for any help that might be lurking out there.
Try setting _ALERT_INFO

/Olle

Olle E. Johansson wrote:
> 
> Try setting _ALERT_INFO
> 
Worked perfectly, thanks.

B.

Brian Capouch wrote:
> Olle E. Johansson wrote:
> 
>>
>> Try setting _ALERT_INFO
>>
> 
The reason for this is that if you set *any* variable with one
underscore prefixing the name, that variable will be copied to the new
channel created by dial() - without the underscore. If you create a
variable called ALERT_INFO in the current channel, where the dial plan
is executed, it will not be reachable from the new channel.

This is the function used by the function that adds new SIP headers.
Basically, chan_sip creates a variable called _SIPADDHEADER01 in the
current channel and reads that later on in the new channel.

Regards,
/Olle

---
Astricon - where you will learn more about channel variables!
...and much more
http://www.astricon.net/2005/ - October 12-14, Anaheim, CA