Hello,
my (long term) plans were to add a way to obfuscate the Call-ID (more for the cases when it includes an IP address), no plans for the moment to generate new call-id for each branch in B-side. But contributions are welcome, of course...
Cheers, Daniel
On Fri, Mar 17, 2017 at 10:29 AM, Carsten Bock carsten@ng-voice.com wrote:
Hi,
quick question (most likely to Daniel) about Topos.
The documentation on topos says about masking Call-ID:
"Note: this functionality is not implemented yet - the parameter is present in order to be in pair with topoh module."
Two questions:
- Is there a timeline, when masking Call-ID's will be added?
- will it also work for forking scenarios? Is it possible, to get a
different Call-ID per branch?
I'm considering replacing SEMS with FreeSwitch in one of our IMS deployments, so as soon as I have forking, I may have different Requests with the same Call-ID but different Request-URI's. Unfortunately, Forked requests are currently not properly supported on FreeSwitch... :-(
When using Topoh, it would change the Call-ID, but with the same input parameter (old Call-ID) it would always result in the same new call-id.
Thanks, Carsten
-- Carsten Bock CEO (Geschäftsführer)
ng-voice GmbH Millerntorplatz 1 20359 Hamburg / Germany
http://www.ng-voice.com mailto:carsten@ng-voice.com
Office +49 40 5247593-40 Fax +49 40 5247593-99
Sitz der Gesellschaft: Hamburg Registergericht: Amtsgericht Hamburg, HRB 120189 Geschäftsführer: Carsten Bock Ust-ID: DE279344284
Hier finden Sie unsere handelsrechtlichen Pflichtangaben: http://www.ng-voice.com/imprint/
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev