Daniel-Constantin Mierla writes:
> That's why backtrace would help to see where the processes are stuck.
Thanks for your comments. Backtrace will be taken during next freeze.
-- Juha
___
Kamailio (SER) - Users Mailing List
On 29.08.19 13:02, Juha Heinanen wrote:
> Daniel-Constantin Mierla writes:
>
>> Being reply processing, one potential operation that can be slow is
>> writing the acc record to the database. Any external tool blocking the
>> acc tables?
> I'm not sure about that. Unfortunately there was no SIP
Hello David,
haven't looked in detail on the specific errors that you observed. But if you
are still in the implementation of this project, you might want to give the
upcoming 5.3 version IMC module as try. It was extended considerably and also
refactored/optimzed:
Hello Bill,
(please keep the list in CC)
yes, this seems to be the case. Just looked briefly to the code, it does
an assignment in some cases. E.g. if no Presentity* data is given it
will just use the From* information. And then it should later output an
error from
Hello Laurent,
(you might want to anonymize your msg dumps bit on this public list)
You probably did already this steps, but nevertheless some debugging ideas:
- capture a longer network trace and compare the network data of a working
against non-working case
- try to see to find a pattern
Normally it should report an error (if the database supports it):
https://www.kamailio.org/docs/modules/5.2.x/modules/db_mysql.html#idm1051351308
For library reasons this is in the seconds time range.
Cheers,
Henning
Am 29.08.19 um 13:02 schrieb Juha Heinanen:
> Daniel-Constantin Mierla
Daniel-Constantin Mierla writes:
> What is the version? Practically kamctl trap is wrapping around gdb
> batch commands to get the backtrace of all kamailio processes.
I found it.
-- Juha
___
Kamailio (SER) - Users Mailing List
Daniel-Constantin Mierla writes:
> Being reply processing, one potential operation that can be slow is
> writing the acc record to the database. Any external tool blocking the
> acc tables?
I'm not sure about that. Unfortunately there was no SIP over TCP calls
during the UDP freeze so that
Hello,
I try to get some log,
I only see that password seems wrong but he was not changed and registration of
this user was ok just before ☹
Any idea how to debug this ?
Aug 29 10:21:38 de5029 kamailio[22615]: DEBUG: auth [api.c:288]:
auth_check_response(): check_response: Our result =
On 29.08.19 10:36, Juha Heinanen wrote:
> Daniel-Constantin Mierla writes:
>
>> If you have access to the system when that blocks in this way during
>> that interval, take the output of 'kamctl trap' or the backtrace with
>> gdb for a sip udp worker process.
> Didn't find 'kamctl trap', will try
Being reply processing, one potential operation that can be slow is
writing the acc record to the database. Any external tool blocking the
acc tables?
Cheers,
Daniel
On 29.08.19 10:26, Juha Heinanen wrote:
> Daniel-Constantin Mierla writes:
>
>> Can you see what is the next debug message
On Wed, Aug 28, 2019 at 05:01:28PM -0400, Aingaran Thirunadarajah wrote:
> Hello,
> Newbie here!
> Have Kamailio set up on a 512MB VPS. Created a couple of users, registered
> with Zoiper and can call between them.
>
> I am looking for documentation to connect the server to other VoIP
> providers
Daniel-Constantin Mierla writes:
> If you have access to the system when that blocks in this way during
> that interval, take the output of 'kamctl trap' or the backtrace with
> gdb for a sip udp worker process.
Didn't find 'kamctl trap', will try gdb.
-- Juha
Daniel-Constantin Mierla writes:
> Can you see what is the next debug message printed by pid 19674?
Below is a few lines of the process before the freeze and a few after
(freeze took this time about 13 minutes). Looks like the process
resumed processing of the same sip request.
> If you have
Hello Daniel, Henning,
I'd be interested, but if I'm the only one... Otherwise I can indeed remove
this patch as Henning suggests, but it embarrasses me to have a different
source code.
Tell me if it's possible to make it customizable. Otherwise I will consider
either removing the patch or
Hi Alex,
sounds strange indeed. 4.3.5 is from March 2016, a lot happened since then..
One idea to investigate further - have you tried already to get more
debugging information from dialog? With debugger module you could
restrict it to dialog, if this is a loaded production instance.
Another
Can you see what is the next debug message printed by pid 19674?
If you have access to the system when that blocks in this way during
that interval, take the output of 'kamctl trap' or the backtrace with
gdb for a sip udp worker process.
Cheers,
Daniel
On 29.08.19 08:50, Juha Heinanen wrote:
>
During the UDP freeze, ss shows:
udp UNCONN 429312 0 x.x.x.x:5060 *:*
tcp LISTEN 0 128 x.x.x.x:5060 *:*
i.e., there is lots of bytes in UDP receive queue, which K has not
picked up.
I don't see anything special in debug log when the udp freeze started at
about
Hello,
Newbie here!
Have Kamailio set up on a 512MB VPS. Created a couple of users, registered
with Zoiper and can call between them.
I am looking for documentation to connect the server to other VoIP
providers (Signalwire, Anveo, VOIP.ms etc.) to make & receive calls from
the external network
19 matches
Mail list logo
