[sr-dev] Forking and Call-ID Hiding in TOPOS
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:cars...@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
[sr-dev] [kamailio/kamailio] erlang: allow user to set ERLANG_xxxDIR (#1037)
If erl is not installed on the system or can not be used (for example when cross-compiling), then erlang module will use the values set by the user in ERLANG_INCDIR and ERLANG_LIBDIR instead of returning en error Signed-off-by: Fabrice Fontaine You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/1037 -- Commit Summary -- * erlang: allow user to set ERLANG_xxxDIR -- File Changes -- M src/modules/erlang/Makefile (5) -- Patch Links -- https://github.com/kamailio/kamailio/pull/1037.patch https://github.com/kamailio/kamailio/pull/1037.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/1037 ___ sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Re: [sr-dev] [kamailio/kamailio] Kamailio 5 coredump 11 (SEGV) upcon receiving MESSAGE via jsonrpcs (#1030)
After applying f81c128, no coredump, but I get `jsonrpcs [jsonrpcs_mod.c:1174]: jsonrpc_dispatch(): jsonrpc over http not initialized - check transport param` FYI, The request is sent in via 127.0.0.1:5060 TCP, with nexthop set as 127.0.0.1:5060 so the request will route through the script and eventually gets looked up by lookup_branches--finding the contact which is a SIP/TLS endpoint. Attached log. [kamailio-coredump-jsonrpcs-message_3.txt](https://github.com/kamailio/kamailio/files/852183/kamailio-coredump-jsonrpcs-message_3.txt) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1030#issuecomment-287517348___ sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Re: [sr-dev] [kamailio/kamailio] Kamailio 5 coredump 11 (SEGV) upcon receiving MESSAGE via jsonrpcs (#1030)
Closed #1030. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1030#event-1005402855___ sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Re: [sr-dev] [kamailio/kamailio] Kamailio 5 coredump 11 (SEGV) upcon receiving MESSAGE via jsonrpcs (#1030)
Well, I'll be damned. Your log message gave me the clue. I was simply missing
`modparam("jsonrpcs", "transport", 1)`. I must have missed that in the upgrade.
Maybe that parameter should be added to the default kamailio.cfg since the
`Default value is '6' (fifo and datagram transport).`
Sorry @miconda. But I guess it shouldn't segfault either ;) Thanks again.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1030#issuecomment-287517767___
sr-dev mailing list
sr-dev@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
