Hello. The LDAP module is stable version but it does not allow to use LDAPS and
/ or startTLS extension. I think it's really important that the LDAP module can
communicate with an LDAP server using TLS and not just TCP. I will be very
grateful and also willing to participate in the development o
ds_select_domain("101,100", "1,4", "F") gives me this error:
ERROR:dispatcher:w_ds_select: extra set(s)
And with this approach we loose the ability to control the max_results per
dispatching id.
Before, we were able to specify how many results to load from each seitd.
---
Reply to this email di
Try: ds_select_domain("101,100", "1,4", "F")
The flags are per set list and not per set list element.
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/pull/269#issuecomment-57709293___
Devel mailing list
Devel@l
Yes, this only makes sense with CONTACT_ONLY matching mode. That mode, along
with a UAC which changes call IDs when re-registering, will provoke this case.
I observed it in a situation where we added our own custom matching mode which
matched off of a token sent by UACs to better handle multiple
It seems that this commit broke the multi-dispatching list feature.
ds_select_domain("101,100", "1,4", "F,F") is failing with:
ERROR:dispatcher:get_flags_int_value: Invalid flags PV value
ERROR:dispatcher:w_ds_select: Invalid value in flags PV
In 1.11, flags were global and the method signature wa
Yes it is a part of my scenario.
I have a flow of calls to many different DIDs, normally they are dispatched by
a number of primary PBX servers(with possibility to dispatch each call to a
different subsets of servers).
So at first I try to LB calls to this primary location.
I also have to cut ex
For me it is working correctly. Please be advised that now flags are specified
as argument of ds_select_* functions and not as modparam. So for the avps to be
populated you'll need to call: ds_select_dst("$var(set_id)", "$var(alg)", "f")
---
Reply to this email directly or view it on GitHub:
htt
@shripchenko , basically what you want to do is to have in failure route the
possibly to start a new "LB" session (new ID, new resources) instead of doing
continuing (failover) the original "LB" session.
Is that correct ?
---
Reply to this email directly or view it on GitHub:
https://github.com/
After this commit, the AVPs used for failover (dst_avp, grp_avp, cnt_avp,
sock_avp) are no longer visible in the script.
Printing all the AVPs doesn't show the ones used by dispatcher (doesn't matter
if the default AVPs are used or custom ones).
---
Reply to this email directly or view it on Git
What matching mode do you use for USRLOC ? I guess this makes sense only with
CONTACT_ONLY right ?
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/pull/346#issuecomment-57661523___
Devel mailing list
Devel@lis
You can merge this Pull Request by running:
git pull https://github.com/ionutrazvanionita/opensips master
Or you can view, comment on it, or merge it online at:
https://github.com/OpenSIPS/opensips/pull/347
-- Commit Summary --
* changed sync/async to sync/async in route_event config sc
11 matches
Mail list logo
