using ""%" HEX HEX" mechanism for escaping from RFC 2396
doc/
subfolder, the README file is autogenerated)I consider it non breaking because with the existing a field containing an ASCII vertical bar '|' would break the separator count and result in broken CDRs, etc. in this case changing the default behavior is probably recommended, someone could abuse this flaw.
Test: consider the following message, the '|' character in the call-id will break the accounting event.
INVITE sip:+11231234567@127.0.0.101 SIP/2.0
Via: SIP/2.0/UDP 1.1.69.51:5070;rport;branch=z9hG4bKPjpM.BvWCQzoS0BJ7TgnuLF9YtmHQTlDgd
Max-Forwards: 70
Call-ID: fG8qa5Xc-iNDLhIAnuLZP|njL1sojRRD
With the encoding it is replaced with '%7C', no modifications should be required to systems processing the ACC events since different behavior will only take place when there is an invalid ACC event:
cat /var/log/acc/acc_129.log
INVITE|upDPn89PCIq7SLTssEGoLoSbC-jDRnfj||fG8qa5Xc-iNDLhIAnuLZP%7CnjL1sojRRD.|403|Forbidden
Extra comments:
I corrected the documentation on the command 'flatstore.rotate', since it was not working, but this one is 'flatstore.k_rotate'
If I understand correctly this module was never migrated from SER to Kamailio completely ...
This change may be the only important one for operation, so I am not proposing any extra refactoring.
https://github.com/kamailio/kamailio/pull/1262
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.