On 26/05/16 17:40, Alex Balashov wrote:
> On 05/26/2016 11:11 AM, Daniel-Constantin Mierla wrote:
>
>> You can use a htable for the rescue, either storing the selected IP
>> within onsend_route or when the replies are coming back. An
>> alternative is to store as a dialog variable.
>
> Okay, so I
On 05/26/2016 11:11 AM, Daniel-Constantin Mierla wrote:
You can use a htable for the rescue, either storing the selected IP
within onsend_route or when the replies are coming back. An
alternative is to store as a dialog variable.
Okay, so I'd need to keep my own state. If I understood correctl
You can use a htable for the rescue, either storing the selected IP
within onsend_route or when the replies are coming back. An alternative
is to store as a dialog variable.
Cheers,
Daniel
On 25/05/16 22:53, Alex Balashov wrote:
> Oh, if only I were personally responsible for the initiative behi
Oh, if only I were personally responsible for the initiative behind this
question... :)
My best guess is that SRV is viewed here as an LB mechanism only and without
any interest in fail over.
-- Alex
--
Principal, Evariste Systems LLC (www.evaristesys.com)
Sent from my Google Nexus.
_
On 05/25/2016 04:32 PM, Alex Balashov wrote:
> Hello,
>
> Sorry if this is a tired, worn question, but I've not dealt much with
> Kamailio's SRV support before:
>
> If a registrant has a contact binding whose domain component is subject
> to an SRV lookup with load-balanced or weighted entries, h
Hello,
Sorry if this is a tired, worn question, but I've not dealt much with
Kamailio's SRV support before:
If a registrant has a contact binding whose domain component is subject
to an SRV lookup with load-balanced or weighted entries, how does one
solve the problem of ensuring that subsequ
