| < Previous by Date | Date Index | Next by Date > |
| < Previous in Thread | Thread Index | Next in Thread > |
Hello,
I built our app with the latest reSIProcate 1.8.14 and tested it
(instead of original 1.8.5). Unfortunately the problem of dropped TCP
connections STILL HAPPENS without noticeable change.
In the attached zipped _SipEngine_DroppedConnection.log we can see
failure events around 21:14:10, lines 7362~7364, 9428~9430, 9966~9968,
11740.
Also in a quick overview I could not find in TcpConnection.cxx,
TcpTransport.cxx, Transport.cxx, TcpBaseTransport.cxx changes that suggest
some effective new handling of that issue.
The tests suggest that the rapid sucessive emission of many long SIP
NOTIFYs is probably overloading internal buffers capacity or other essential
resource.
It looks as if the default settings for TCP protocol that are in use
aren't tuned to such a regime of bursty high bandwidth usage.
What can be done on that issue ?
I can provide a corresponding Wireshark capture if wanted.
Many thanks,
Julio.
Attachment:
_SipEngine_DroppedConnection.zip
Description: Binary data