Great. That'll be perfect.
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/438#issuecomment-205661512___
sr-dev mailing list
sr-dev@lists
Hi. Just tested and this helps and works as required.
Just to be technically correct, the implementation disconnects the call when
kamailio misses the keep-alive response to the number defined in the modparam
in the entire call.
But to better meet the use-case it should disconnect the call when
the ka_failed_limit should be a modparam in the dialog module?
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/438#issuecomment-205201517
Yes. A configurable option to decide on how many timeouts should the dialog
end, will do the trick. Thanks. It would be great if this is possible.
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/
I use it over UDP and the SIP transaction setup does the job perfectly. The
problem is when you use it over mobile networks and do network switching (eg.
from WiFi to LTE) and at that instance when an OPTIONS message goes out; it
goes out to the WiFi IP Address from where the request is bound to
Any chance of handling this or making this configurable in the near future.
Thanks !!
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/438#issuecomment-202789223
after this commit one of my function to match the registered contact stopped
working as expected. Here's the code snippet:
```
$xavp(reg=>match_callid) = $avp(callid);
#---match existing record based on callid---
if(registered("location", "$tu", 1)) {
xlog("L_INFO"
