Thanks Daniel,
Please, could you help with this information, in Kamailio which DB tables
hold the information for CDR so that we can use for monitoring and charging
purpose?
Thanks and regards,
Jack.
On Thu, Sep 26, 2019 at 11:54 AM Daniel-Constantin Mierla
wrote:
> Hello,
>
> are you
Hello,
there can be NOTIFY requests with no body, as the one below has
Content-Length 0 -- a matter of what is the call state, it can be a
valid one.
Regarding the fact that the NOTIFY is not delivered, have you done nat
traversal for SUBSCRIBE? I see private address in the R-URI, so the
On 30.09.19 14:55, Daniel Tryba wrote:
> On Sun, Sep 29, 2019 at 11:03:47AM +0300, Olli Attila wrote:
>> modparam("dialog", "profiles_with_value", "concurrent_calls")
>> modparam("dialog", "dlg_flag", 4)
>> modparam("dialog", "db_url", DBURL)
>> modparam("dialog", "db_mode", 1)
>
> Have you
Thanks for your response Daniel.
Kamailio is installed on a cloud server (not AWS) and therefore has an internet
facing IP address. The phone is in my office so there is NAT happening at that
end. I would have thought the NAT traversal would only apply if the
server/Kamailio was behind a
Daniel
Adding in the set_contact_alias() for SUBSCRIBE meant that the NOTIFY now gets
a "200 OK", but the light on the phone does not light up even though the
extension being monitored is registered.
I notice that after the SUBSCRIBE request, the return message is a "202 OK"
instead of a "202
Just a note, I would suggest to use htable+dmq to do such limits,
dialog+dmq has some issues when handling dialog expiration when a node for
whatever reason is restarted.. (search GH issues and you will find one with
a long thread where Charles explains the reasons: TL;DR: You could end up
Hi Joel,
Thank you, I was reading it yesterday. See this issue
https://github.com/kamailio/kamailio/issues/2080#issue-499544483 – in my tests
the proxies will expire the dialogs even after a restart. I just tested it
again even restarting both proxies a few times.
Cheers,
Henning
--
Henning
Found it:
https://github.com/kamailio/kamailio/issues/1591#issuecomment-409205552
On Tue, Oct 1, 2019 at 07:15 Joel Serrano wrote:
> Just a note, I would suggest to use htable+dmq to do such limits,
> dialog+dmq has some issues when handling dialog expiration when a node for
> whatever reason
Hello Joel,
I did some research yesterday for a customer, and only found open tickets
related to the dialog statistics issue (#1692). The module README also stats
that the DMQ will synchronize profiles. If there are some issues related to
dialog inconsistencies, then they should (preferable)
This is great news!! I will repeat the tests that failed for me just to be
sure, but from reading your comments it seems promising!! Thanks for
pointing me to it.
Joel.
On Tue, Oct 1, 2019 at 08:15 Henning Westerholt wrote:
> Hi Joel,
>
>
>
> Thank you, I was reading it yesterday. See this
10 matches
Mail list logo
