The RFC3323 states those values in that specific header are colon separated. 

/b


On Wed, Apr 26, 2017 at 12:03 PM, Markus Bönke <mbodbg@gmx.net> wrote:
Hello,

I try to set a sip_header to a comma separated value. If I set a X-Header like:

 {sip_h_X-My-Header=one\,two\,three,leg_time_out=10,process_cdr=b_only}

as described on the wiki, it works.

But if I try to set a regular Header like:

{sip_h_Privacy=header\,user\,id}

the values are separated by semicolon instead of comma

Privacy: header;user;id

Is this by design? Is it possible to set comma separated values on regular headers?

Thanks and regards

Markus
_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.cluecon.com

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



--

Brian West
brian@freeswitch.org

Twitter: @FreeSWITCH , @briankwest

http://www.freeswitchbook.com 
http://www.freeswitchcookbook.com

Book a phone call (CST)

Allison prompts for FreeSWITCH:

https://www.gofundme.com/allison-prompts-for-freeswitch

Got Bugs? Report them here! | Reddit: /r/freeswitch

T:+19184209001 | F:+19184209002 | M:+1918424WEST (9378)
Skype:briankwest