Missed Packets in RL Logs
If you're having issues with a SIP VRTX or a Port Mirror not associating calls in the Recording Library logs as shown below, 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 the network, or (if using SIP VRTX), switch to port mirror. Also ensure you are using a supported Codec shown below.
Supported Codecs
- G.711 alaw (Europe and South America standard)
- G.711 ulaw (North American standard)
- G.729 (low bitrate codec commonly used for cell phones)
- G.722 (high quality audio codec common on Cisco phones)
- If on IP Office and using a non-SIP VRTX, another step you can take is increasing the Haul Length on the trunk in IPO Office Manager or moving the VRTX closer to the IPO.
- If on IP Office and a port-mirror, instead of increasing the Haul Length, you would increase the SIP provider bandwidth.
-
Also with IP Office, you can verify the codecs the trunks are using here under Line > VOIP.
