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