[OpenSIPS-Devel] [opensips] B2B GUIDs too short (#783)

[Alex Balashov]

In `b2b_entities/dlg.c:b2b_generate_key()`, the use of this format:

`<B2B prefix>.<hash index>.<local index>`

leads to very short Call-IDs like this:

`Call-ID: B2B.27572.17705`

This is impractically short, and is certain to lead to collisions in a high-volume environment with millions of calls daily. There are many database systems etc. that rely on all calls being identifiable by a unique GUID. I don't think it conforms to the RFC 3261 prescription that GUIDs be good GUIDs.

Unfortunately, it's not possible to simply append additional random data to the key string, since the Call-ID has specific meaning that is extracted in sequential requests, as per `b2b_entities/dlg.c:b2b_parse_key()`. This function also foresees the length of the GUID and the positioning of the delimiters to be rather static in nature.

Some sort of solution to increase overall Call-ID length and combinatorial complexity is needed, such as appending time-based data into the string. 

Much appreciated!

---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/783
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/devel/attachments/20160206/76cebc2e/attachment.htm>