[Spce-user] Questions about mr4.5.4

William Fulton wfulton at thirdhatch.com
Thu May 25 18:21:43 EDT 2017

As an update, we started getting this message as well just before calls are terminate early before either party hangs up:
WARNING: dialog [dlg_handlers.c:1226]: dlg_onroute(): unable to find dialog for ACK with route param '9a.9cf1' [169:8137]


From: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of William Fulton
Sent: Thursday, May 25, 2017 12:23 PM
To: spce-user at lists.sipwise.com
Subject: [Spce-user] Questions about mr4.5.4

This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing<http://aka.ms/LearnAboutSpoofing>



We have been using mr3.7.1 with very few problems for the past few years. The only minor thing we found is that around 180 days or so we have to perform a reboot or our sip clients lose connectivity at random intervals. This is all manageable and not really an issue for us. However, we want to move to mr4.5.4 LTS version. I have been testing this for a few days with the same sip providers, but am getting some warnings and errors in the proxy log as well as what seems like inconsistent call connectivity. Here are the Notices we are getting:
NOTICE: <core> [action.c:1560]: run_actions(): alert - action [save (25)] cfg [/etc/kamailio/proxy/registrar.cfg:159] took too long [125 ms]
NOTICE: <core> [db_query.c:60]: db_do_submit_query(): alert - query execution too long [125 ms] for [update `location` set `expires`='2017-05-25 12:13:]
NOTICE: <core> [db_query.c:60]: db_do_submit_query(): alert - query execution too long [125 ms] for [update `dialog` set `state`=4,`timeout`=1495782546]

Is it possible that some of these notices are the cause of our inconsistent connectivity? I'm surprised that query executions are taking too long. This is a test server with one subscriber. It also has a lot of processing power with 8 Xeon cores and 4GB of memory with SAS hard drives. Does anyone have any insight in to what could be the cause of these notices? Are they normal? Can I make adjustments to the config.yml to fix them?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20170525/556b257c/attachment-0001.html>

More information about the Spce-user mailing list