Since FS-6075 was commited, there is a setting to get all SIP headers, so this should already work on master.<div><br></div><div>/Peter<br><br>torsdagen den 10:e april 2014 skrev Brian West <<a href="mailto:brian@freeswitch.org">brian@freeswitch.org</a>>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Well know headers can be dealt with, Its the ones that aren’t, and getting all headers would be problematic and time consuming and probably a performance hit.<br>
<br>
sofia.c<br>
/* Loop thru unknown Headers Here so we can do something with them */<br>
for (un = sip->sip_unknown; un; un = un->un_next) {<br>
<br>
It can be done, its just someone needs to write the additional if statement to gather the headers they care about.<br>
<br>
Patches welcome.<br>
<br>
--<br>
Brian West<br>
<a href="javascript:;" onclick="_e(event, 'cvml', 'brian@freeswitch.org')">brian@freeswitch.org</a><br>
FreeSWITCH Solutions, LLC<br>
PO BOX 2531<br>
Brookfield, WI 53008-2531<br>
Twitter: @FreeSWITCH , @briankwest<br>
<a href="http://www.freeswitchbook.com" target="_blank">http://www.freeswitchbook.com</a><br>
<a href="http://www.freeswitchcookbook.com" target="_blank">http://www.freeswitchcookbook.com</a><br>
<br>
T: +1.918.420.9001 | F: +1.918.420.9002 | M: +1.918.424.WEST<br>
iNUM: +883 5100 1420 9001<br>
ISN: 410*543<br>
Skype:briankwest<br>
PGP Key: <a href="http://www.bkw.org/key.txt" target="_blank">http://www.bkw.org/key.txt</a> (AB93356707C76CED)<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
On Apr 10, 2014, at 2:45 AM, Dahlberg, David <<a href="javascript:;" onclick="_e(event, 'cvml', 'david.dahlberg@fkie.fraunhofer.de')">david.dahlberg@fkie.fraunhofer.de</a>> wrote:<br>
<br>
> Am Mittwoch, den 09.04.2014, 18:42 -0500 schrieb Brian West:<br>
><br>
>> It it does then we need an NDLB flag (for those not in the know NDLB is No Device Left Behind)<br>
><br>
> Sorry, considering that /any/ header that are not recognised by a<br>
> particular software solution and that does not begin with "X-" or<br>
> "P-" to be of any use is what IMHO requires a NDLB flag.<br>
><br>
> X-Headers are a RFC 822 (from 1982!) legacy. By now, considering only<br>
> "X-" headers as potentially meaningful would require FS to implement<br>
> /every possible/ standardized extension to the SIP RFCs, which is<br>
> virtually impossible today. E.g. I am quite certain, that you do /not/<br>
> implement RFC 4412 ("Resource-Priority") nor was FS able to support a<br>
> custom extension with the necessary data do process it.<br>
><br>
> For that reason (or more for the problem of migrating a "well known"<br>
> X-Header to a "standards" header) the IETF finally deprecated the usage<br>
> of "X-" and "P-" prefixes in RFC 6648/BCP 178 and RFC 5727/BCP 67.<br>
><br>
> Until recently one could write but not read non-X-, non-P- and not known<br>
> headers. Fortunately, now there seems to be a patch (FS-6075) in HEAD,<br>
> which allows the parsing of arbitrary headers at least for SIP invites.<br>
> So please have a look at the most recent git version of FS, Ido.<br>
><br>
><br>
> Cheers,<br>
> David<br>
<br>
</blockquote></div>