Hello Alex,
Thank you for the clarification. Now I understand this behavior.
пт, 24 трав. 2019 о 22:07 Alex Balashov пише:
> Branches are a creature of transactions. It follows that “branch flags”
> are transaction-persistent flags at the branch level, rather than scoped to
> the transaction
Branches are a creature of transactions. It follows that “branch flags” are
transaction-persistent flags at the branch level, rather than scoped to the
transaction as a whole.
ACKs constitute a separate transaction.
—
Sent from mobile, with due apologies for brevity and errors.
> On May 24,
Then.. I don't know, lol
But the fact that ACKs belong or not to even different transactions
(depending on whether positive or negative reply) must be playing a role
here.
Good luck.
On Fri, May 24, 2019, 12:11 PM Володимир Іванець,
wrote:
> Hello Sergiu,
>
> We allow multiple contacts to
Hello Sergiu,
We allow multiple contacts to register on single account. They can have
different properties. On step 1 I'm looking for something specific which
can be different for different contacts. If I understood correctly
*setbflag* and *isbflagset* can set and check flags for different
I might be wrong, but isn't ACK part of a transaction? If so, you'd need to
use *setflag*/*isflagset*
Cheers.
On Fri, May 24, 2019 at 10:03 AM Володимир Іванець
wrote:
> Hello everyone!
>
> I'm not sure if I correctly understood the description of functions
> *isbflagset* and *isbflagset* so
Hello everyone!
I'm not sure if I correctly understood the description of functions
*isbflagset* and *isbflagset* so once again I'm asking for help :)
Here is what I do:
1. Asterisk sends INVITE to Kamailio. Kamailio performs lookup of available
contacts and then few checks in branch_route. I'm
