Hello
We have seen that in cases when callee sends a callid starting by "!!:", which is also the default callid_prefix value, we do see that when reading the $ci in the onreply routes it's changed for example like this
from Call-ID !!:Y5HfD54-DIKfL56nz5TIYIioYVznLb1ID5TUYf1oz8zBYCl0LCllD9loDbD*
to Call-ID \xA6\xF3\xF1\xFE\xFD:\xFEUq\xCA\xFD\xAB:\xF2\xA5\xA6Wۤ\x83\xABʫe\xFE\xF2\x87\xA7\e[;ã\xA5\xAC\xC1ɬ\xF3\xFD|\xDB\xFE\xAF
in that call we are actually not doing topology hiding, so we are dropping the message on the topoh:msg-outgoing event route
This seems to cause to send that weird callid in the messages.
I guess that change should not be done. Could you please take a look?
thanks and best regards
david escartin
sonoc
--
|
This e-mail is for the exclusive use of its recipients and may contain business secrets or other confidential or privileged information. Any unauthorised use, copying, publication or distribution of this e-mail is strictly prohibited. If you are not the intended recipient, please inform us immediately by replying to this e-mail and delete it, including any attachments or copies on your system.
In accordance with the GDPR (EU) 2016/679 and the LOPDGDD 3/2018, we inform you that this e-mail address and/or any other personal data you have provided us with will be treated by SONOC with absolute confidentiality and with the only purpose of providing you with the requested services, due to your condition as a client, supplier or because you have requested information from us at any time. These data will only be kept for as long as required to comply with legal obligations. You can exercise your rights at any time by sending an e-mail to: dataprotection@sonoc.io.
|
|
|