[SR-Users] Fwd: IMS Third party Register issue

2020-02-14 Thread Lanvin ADON
Hi all, Anyone who can help on this issue. Kamailio stuff may already worked it out. Please share with me the solution or any workaround. Regards Lanvin ADON -- Forwarded message - From: Lanvin ADON Date: Thu, Feb 6, 2020 at 7:58 AM Subject: [SR-Users] IMS Third party Register

Re: [SR-Users] Call-ID Uniqueness and safety?

2020-02-14 Thread Daniel-Constantin Mierla
Hello, to add a few more from my past experiences ... I have a couple of deployments where I check the call-id not to be duplicate in active transactions because of some other constraints (customer requirements) specific for the respective services -- for example, not allowing parallel forking fro

[SR-Users] ds_is_from_list doesn't accept groupid from a variable?

2020-02-14 Thread Björn Bylander
Hi, According to https://kamailio.org/docs/modules/5.3.x/modules/dispatcher.html#dispatcher.f.ds_is_from_list, ds_is_from_list should accept an integer variable for the group id parameter. The following simple example doesn¹t work however: $var(foo) = 5; ds_is_from_list($var(fo

Re: [SR-Users] ds_is_from_list doesn't accept groupid from a variable?

2020-02-14 Thread Yuriy Gorlichenko
You have to Put variable in "" as I remember. This is usual rool for all function calling in a config file. On Fri, 14 Feb 2020, 14:54 Björn Bylander, wrote: > Hi, > > According to > https://kamailio.org/docs/modules/5.3.x/modules/dispatcher.html#dispatcher.f.ds_is_from_list, > ds_is_from_list

Re: [SR-Users] Fwd: IMS Third party Register issue

2020-02-14 Thread Valentin Christoph
Hi, Did not have a look to your attachments, but it probably sounds like a wrong service configuration at the HSS. All the best Christoph From: sr-users On Behalf Of Lanvin ADON Sent: Friday, February 14, 2020 11:26 AM To: sr-users@lists.kamailio.org Subject: [SR-Users] Fwd: IMS Third party Re

[SR-Users] xlog() format change from 5.3 to 5.4-nightly

2020-02-14 Thread Joel Serrano
Hello, I've noticed that the output format of xlog() changes from 5.3 to 5.4-nightly. v5.3 xlog(): Feb 13 11:56:35 csbc01 csbc[27333]: NOTICE: {1 24727 REGISTER b1d374f6-9b8c53ff@A.B.C.D}

Re: [SR-Users] xlog() format change from 5.3 to 5.4-nightly

2020-02-14 Thread Henning Westerholt
Hi Joel, It might be a regression introduced recently from the logging infrastructure refactoring. I agree, it should not change without reason. Cheers, Henning -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://skalatan.de/services