Do not take my explanation as a "no" - I just wanted to point the
obstacles ; and work around the statefull part may be encoding some
user/contact ID in the callid or from tag, so when you receive back the
reply, you do not need a transaction to find out the corresponding
contact you pinged - y
Thank you for the solid explanation.
--- Jayesh
On Mar 14, 2013 10:37 PM, "Bogdan-Andrei Iancu" wrote:
> **
> Hi Jayesh,
>
> Firing an event is not a problem - the problem is in NAT pinging, there is
> no state for the tractions. Basically the modules doing NAT do not care of
> the replies (as f
Hi Jayesh,
Firing an event is not a problem - the problem is in NAT pinging, there
is no state for the tractions. Basically the modules doing NAT do not
care of the replies (as for pining is not relevant), so you do not know
which ping and for what contact it failed, in order to trigger the ev
Hi All,
The 1.9 has an awesome event interface and I really appreciate the great
work by the developers. I was looking at an option to raise an event when a
registered user becomes unreachable.
Say, for eg: I use keep-alive method as OPTIONS in the nat_traversal module
and if I do not get a respons
