Missed Packets in Recording Library Logs
If you're having issues with a SIP VRTX or a Port Mirror not associating calls, it may be due to missed packets.
You could see errors like this:
18 Sep 2018 12:57:11,580 WARN SipCallInfo:359 - ALAW/ULAW RTP Frames received out of order or lost (192.168.254.41:46584_2517130403_ULAW). lastTimeStamp: 19520 timeStamp: 19360
18 Sep 2018 12:57:21,587 WARN SipCallInfo:359 - ALAW/ULAW RTP Frames received out of order or lost (192.168.254.41:46584_2517130403_ULAW). lastTimeStamp: 99520 timeStamp: 99360
18 Sep 2018 12:57:22,226 WARN SipCallInfo:359 - ALAW/ULAW RTP Frames received out of order or lost (192.168.254.41:46584_2517130403_ULAW). lastTimeStamp: 104320 timeStamp: 320
18 Sep 2018 12:57:38,128 WARN err:43 - Sep 18, 2018 12:57:38 PM com.ftdi.FTDevice getDevices
Resolution
This is something that needs to be fixed in the SIP line itself. You can clean up the trunk signal, increase the packet size on their network, or (if they're using SIP VRTX), switch to port mirror.