[OpenSIPS-Users] opensips - stops responding to some SIP messages

[Maxim V. Maximov]

Thank you all for the answers, the problem has not yet been solved

>>did you take network traces at the time of the fault, does the traffic
get to the server?

Yes, we checked. check when removing the dump on the network interface, we
see that the request goes to our server

RX errors:0 dropped:0 overruns:0 frame:0
TX errors:0 dropped:0 overruns:0 carrier:0


opensipsctl fifo log_level

Process::  PID=2998 Log level=3 Type=attendant
Process::  PID=3009 Log level=3 Type=event-route handler
Process::  PID=3010 Log level=3 Type=RTPP timeout receiver
Process::  PID=3011 Log level=3 Type=MI Datagram
Process::  PID=3012 Log level=3 Type=MI FIFO
Process::  PID=3013 Log level=3 Type=time_keeper
Process::  PID=3014 Log level=3 Type=timer
Process::  PID=3017 Log level=3 Type=SIP receiver udp:x.x.x.x:5060
Process::  PID=3019 Log level=3 Type=SIP receiver udp:x.x.x.x0:5060
Process::  PID=3021 Log level=3 Type=SIP receiver udp:x.x.x.x:5060
Process::  PID=3023 Log level=3 Type=SIP receiver udp:x.x.x.x:5060
Process::  PID=3025 Log level=3 Type=SIP receiver udp:x.x.x.x:5060
Process::  PID=3028 Log level=3 Type=SIP receiver udp:x.x.x.x:5060
Process::  PID=3031 Log level=3 Type=SIP receiver udp:x.x.x.x:5060
Process::  PID=3032 Log level=3 Type=SIP receiver udp:x.x.x.x:5060
Process::  PID=3033 Log level=3 Type=SIP receiver udp:x.x.x.x:5068
Process::  PID=3034 Log level=3 Type=SIP receiver udp:x.x.x.x:5068
Process::  PID=3035 Log level=3 Type=SIP receiver udp:x.x.x.x:5068
Process::  PID=3036 Log level=3 Type=SIP receiver udp:x.x.x.x:5068
Process::  PID=3037 Log level=3 Type=SIP receiver udp:x.x.x.x:5068
Process::  PID=3038 Log level=3 Type=SIP receiver udp:x.x.x.x:5068
Process::  PID=3039 Log level=3 Type=SIP receiver udp:x.x.x.x:5068
Process::  PID=3040 Log level=3 Type=SIP receiver udp:x.x.x.x:5068
Process::  PID=3041 Log level=3 Type=Timer handler


opensipsctl fifo get_statistics shmem:
shmem:total_size:: 6316621824
shmem:used_size:: 248015312
shmem:real_used_size:: 663246088
shmem:max_used_size:: 1204678592
shmem:free_size:: 5653375736
shmem:fragments:: 4312144

>>Also, is OpenSIPS talking to any database, or any other component? The
idea
here being that the component is blocking and this also blocking OpenSIPS.

Yes, open source works with mysql. no problems with database detected
all incoming requests are processed quickly, also checked in real time the
occurrence of the problem

>>Also, how many child threads do you have for how many interfaces? Do you
use TCP/TLS? We have seen that sudden increases in traffic can overload the
sockets and cause backups/blocking with connection-based protocols,
especially if the remote end of a connection simply vanishes (dead peer
scenario).

No, we do not use TCP

for example, made a screenshot from the dump. in which it is clear that the
open-answer responded first to the first shoulder of the call, then created
the second one and did not react to receiving messages on it

https://drive.google.com/file/d/1X3A0Q-7njT-KLu6_7Ed1-eOnIemUULGi/view
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20190409/314c594f/attachment.html>