The question is whether that DMQ synchronization for dialog data is sending
all dialogs or only delta/incremental data. Some SBCs I've worked with only
synchronize new dialog data, leaving standby nodes only aware of dialogs
established since restarting or joining the cluster, not existing
harneet singh writes:
> "A gateway matches a request if user part of Request-URI matches "prefix",
> caller URI matches "from_uri" pattern,* caller URI userpart matches mtree
> with "mt_value"*, and callee URI matches "request_uri" pattern in a tuple
> that is associated with the gateway."
>
>
Hi Experts,
We wished to used the LCR Module to be able to select the Gateway(s) to
send the calls to based on the From(Caller) Username.
Based on the LCR Documentation, the usage of other fields like request URI
or prefix etc is pretty clear. But for the From Usename I am having certain
trouble
Hi Alex
> If profile membership is synchronised, does that mean it is possible
> to get a count of dialogs in a given profile on any node?
Correct. I'm using this to implement a channel limit per trunk or per
customer on two dialog DMQ synced nodes.
--
Mit freundlichen Grüssen
-Benoît
Henning,
If profile membership is synchronised, does that mean it is possible to get a
count of dialogs in a given profile on any node?
-- Alex
> On Jun 9, 2023, at 4:31 AM, Henning Westerholt wrote:
>
> Hi Alex,
>
> according to docs only basic dialog (profile) information is synchronized.
Hi Alex,
according to docs only basic dialog (profile) information is synchronized. I
quickly checked the code, and its synchronizing profiles as well. But some
functionality will work only on the original node, like sending in-dialog
requests.
Cheers,
Henning
--
Henning Westerholt –
Hello,
as I can see you use KEMI and the out of pkg could be because you define
too many pseudo-variables.
Does your kemi script set/get pseudo-variables with different name each
time processing a sip message? Like $avp(x) or $var(z) where x or z are
different for each sip message?
Cheers,
