[Freeswitch-users] Accessing custom SIP headers

Kristian Kielhofner kristian.kielhofner at gmail.com
Mon Nov 30 08:54:42 PST 2009


The correct way to pass non-standard headers is X- not X_ .

<action application="set" data="accountcodec=${sip_h_X-ACCOUNTCODE}" />

On Sat, Nov 28, 2009 at 12:47 PM, Simon Woodhead <simon.woodhead at me.com> wrote:
> Hi folks,
> I'm hoping someone can help me get at custom headers in the dial-plan. I've
> read about X- headers being accessible but need to get at some X_ headers
> passed through from a proxy. Reading the info app docs, the X shouldn't
> actually matter but no matter which way I try I always seem to get a null
> result.
> An example header in an INVITE is:
> X_ACCOUNTCODE: XXXXXX.
> I've tried the following dial-plan structures hoping one might work but none
> do:
> <action application="set"
> data="accountcodea=${variable_sip_h_X_ACCOUNTCODE}" />
> <action application="set" data="accountcodeb=${variable_sip_h_ACCOUNTCODE}"
> />
> <action application="set" data="accountcodec=${sip_h_X_ACCOUNTCODE}" />
> <action application="set" data="accountcoded=${sip_h_ACCOUNTCODE}" />
> Any help would be much appreciated.
> Thanks,
> Simon
> _______________________________________________
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
>
>



-- 
Kristian Kielhofner
http://www.astlinux.org
http://blog.krisk.org
http://www.star2star.com
http://www.submityoursip.com
http://www.voalte.com




More information about the FreeSWITCH-users mailing list