[Blink] Audio Cut Outs and Dropped Calls
Bryan Miller
bmill at socialserve.com
Tue Dec 10 16:16:25 CET 2013
Hi,
1. I recently upgraded our call center from 2.1.0 to 3.3.0. Right after the upgrade people began reporting issues with call audio quality (audio would pause from 3-6 seconds), and that they were getting dropped calls.
They would also mention that in the call window, they would see a red "packet loss" message occasionally. The one that seems to have the most severe case, I'll see tons of these messages in the sip log:
[Blink Pro 646] (5) 2013-12-10 09:51:00.705 strm0x8cbe18 Jitter buffer starts returning normal frames (after 1 empty/lost)
[Blink Pro 646] (5) 2013-12-10 09:51:00.926 strm0x8cbe18 Frame lost, recovered!
[Blink Pro 646] (5) 2013-12-10 09:51:00.926 strm0x8cbe18 Jitter buffer starts returning normal frames (after 1 empty/lost)
[Blink Pro 646] (5) 2013-12-10 09:51:01.193 strm0x8cbe18 Frame lost, recovered!
[Blink Pro 646] (5) 2013-12-10 09:51:01.204 strm0x8cbe18 Jitter buffer starts returning normal frames (after 1 empty/lost)
[Blink Pro 646] (5) 2013-12-10 09:51:01.506 strm0x8cbe18 Frame lost, recovered!
[Blink Pro 646] (5) 2013-12-10 09:51:01.506 strm0x8cbe18 Jitter buffer starts returning normal frames (after 1 empty/lost)
[Blink Pro 646] (5) 2013-12-10 09:51:01.866 strm0x8cbe18 Frame lost, recovered!
[Blink Pro 646] (5) 2013-12-10 09:51:01.866 strm0x8cbe18 Jitter buffer starts returning normal frames (after 1 empty/lost)
[Blink Pro 646] (5) 2013-12-10 09:51:02.296 strm0x8cbe18 Frame lost, recovered!
[Blink Pro 646] (5) 2013-12-10 09:51:02.307 strm0x8cbe18 Jitter buffer starts returning normal frames (after 1 empty/lost)
[Blink Pro 646] (5) 2013-12-10 09:51:02.853 strm0x8cbe18 Frame lost, recovered!
…Yet, if I run a ping test to the sip server from that workstation, there's no packet loss (ping -i 0.02 -s 270 -c 500).
This is in the log at the beginning of the call before all the jitter buffer log messages:
[Blink Pro 646] (5) 2013-12-10 09:49:39.180 strm0x8cbe18 Jitter buffer is bufferring (prefetch=0), plc invoked
[Blink Pro 646] (5) 2013-12-10 09:49:39.180 strm0x8cbe18 Start talksprut..
[Blink Pro 646] (5) 2013-12-10 09:49:39.180 ec0x53f8b90 Prefetching..
[Blink Pro 646] (5) 2013-12-10 09:49:39.187 ec0x53f8b90 Delay buffer is reset
[Blink Pro 646] (4) 2013-12-10 09:49:39.187 sound_port.c EC reset
[Blink Pro 646] (5) 2013-12-10 09:49:39.204 ec0x53f8b90 Prefetching..
[Blink Pro 646] (5) 2013-12-10 09:49:39.215 ec0x53f8b90 Latency bufferring complete
[Blink Pro 646] (4) 2013-12-10 09:49:39.215 echo_webrtc_ae WebRTC AEC reset succeeded
[Blink Pro 646] (5) 2013-12-10 09:49:39.217 strm0x8cbe18 RTP status: badpt=0, badssrc=0, dup=0, outorder=0, probation=-1, restart=0
[Blink Pro 646] (5) 2013-12-10 09:49:39.238 strm0x8cbe18 Jitter buffer starts returning normal frames (after 3 empty/lost)
[Blink Pro 646] (5) 2013-12-10 09:49:39.679 strm0x8cbe18 Frame lost, recovered!
2. For some reason when I go to preferences to enable logging (sip, engine, notifications), it's only writing the sip log and not the other two.
3. Has anyone reported issues with or do you know of any issues with PTHVolume? http://pth.com/products/pthvolume/ I've seen errors in the system logs on the workstations I'm trying to troubleshoot. I don't know if it's the cause. Removing the app seems to improve the situation, but a couple of users say they continue to get dropped calls and others say no dropped calls. These are the entries, dunno if they help:
system.log:Dec 9 11:46:37 mini-52 [0x0-0x1b01b].com.pth.PTHVolume.app[779]: PTHVolume(779,0xb0218000) malloc: *** auto malloc[779]: error: GC operation on unregistered thread. Thread registered implicitly. Break on auto_zone_thread_registration_error() to debug.
system.log:Dec 9 12:03:15 mini-52 [0x0-0x1b01b].com.pth.PTHVolume.app[779]: PTHVolume(779,0xb0218000) malloc: *** auto malloc[779]: error: GC operation on unregistered thread. Thread registered implicitly. Break on auto_zone_thread_registration_error() to debug.
Regards,
Bryan Miller
More information about the Blink
mailing list