[asterisk-users] SIP_HEADER() read-only

[Eric "ManxPower" Wieling]

I don't understand what the problem is.  If you want to pass a variable 
set the variable, but prefix it with __ (2 underscores)

Set(__DNID=${DNID})

Douglas Garstang wrote:
> Oh... That's real nice. I was considering using SIP instead of IAX to trunk calls between Asterisk boxes as IAX has some severe limitations in regards to passing variables. A few people said 'use SIP!' because you can set the SIP headers. Looks like that isn't an option!
> 
>> -----Original Message-----
>> From: Vincent Regnard [mailto:devel at regnard.org]
>> Sent: Thursday, August 03, 2006 4:29 AM
>> To: Asterisk Users Mailing List - Non-Commercial Discussion
>> Subject: Re: [asterisk-users] SIP_HEADER() read-only
>>
>>
>>
>>
>> There is presently no .write member in the structure declaration for 
>> this function in channels/app_sip.c:
>>
>> static struct ast_custom_function sip_header_function = {
>>          .name = "SIP_HEADER",
>>          .synopsis = "Gets or sets the specified SIP header",
>>          .syntax = "SIP_HEADER(<name>)",
>>          .read = func_header_read,
>> };
>>
>> So I imagine the answer to my question is yes SIP_HEADER is a 
>> read-only 
>> function. There is no implementation equivalent to SipAddHeader() for 
>> SIP_HEADER().
>>
>>
>>
>> _______________________________________________
>> --Bandwidth and Colocation provided by Easynews.com --
>>
>> asterisk-users mailing list
>> To UNSUBSCRIBE or update options visit:
>>    http://lists.digium.com/mailman/listinfo/asterisk-users
>>
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
> 
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
> 


-- 
Now accepting new clients in Birmingham, Atlanta, Huntsville, 
Chattanooga, and Montgomery.