I assume you're doing a bridge? FreeSWITCH is a b2bua... meaning the call going into FreeSWITCH is a separate call from the one going out (it just links the media on the 2 calls together to bridge them). That's why the variable's not being copied across by default. It is however possible to tell FreeSWITCH to copy a variable from the A-leg to the B-leg, and any non-standard SIP headers can be read and written using the sip_h_ variable prefix. Try this: <extension name="..."> <condition ...> ... <action application="export" data="sip_h_Subject" /> <action application="bridge" data="..." /> ... </condition> </extension> The subject should be in the sip_h_Subject variable on the A-leg, the above will export (copy) that variable onto the B-leg and it should then appear in the outgoing invite. -Steve On 22 December 2010 15:45, Kane, Michael (mkane02) <mkane02@harris.com> wrote:
Hello all, we are developing a custom app that will require sending a Subject: header (with a specific value) with the initial invite to trigger additional calling features and behavior. What we’re finding when we send the Invite, is that FS is dropping the Subject: header and continues normal call processing. Is there a configuration parameter that allows the header to pass through FS?
I submitted a SIP trace in pastbin and the reference number is 14853.
Mike
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org