Thank you, David, Hmm... but I don't know about a stale connection. We were using it to talk across the country -- I love Allstar! I was on the web transceiver, that in hindsight I should have mentioned, and talking with a user connected to me and talking through a repeater. There were no extended idle times. I was watching and noted that they seem to throw the errors whenever I would key up through the web transceiver. I was reported as having clean audio while the party I was talking to was choppy and would sometimes disappear altogether. Does this new information clarify or alter your position any? Can IAX be upgraded? R. Wayne -----Original Message----- From: David McGough Sent: Saturday, June 20, 2015 3:34 AM To: R. Wayne Cc: app_rpt-users@ohnosec.org Subject: Re: [App_rpt-users] Connection Errors Hi, This is a known deficiency in the 1.4.x version of the IAX2 code, unfortunately. This problem shows up after a link becomes "stale" (idle for an extended period of time). The simple work-around is to kerchunk the link once before you start to talk on it, otherwise the first transmission over the stale link will have choppy audio. After the first transmission, this issue temporarily resolves itself (until the link becomes stale again). I'm not sure of a better work-around (anyone got any idea???)...Note this was a problem with IAX2 tunneling with Asterisk in general back in the 1.4.x days, it is NOT specific to AllStar. More recent versions of Asterisk greatly improve (maybe even fully resolve?) this issue.... 73, David KB4FXC On Sat, 20 Jun 2015, R. Wayne wrote:
I have a new server that is being fed by Charter Communications. It is connected directly to the Internet (at the moment) and is kicking off errors Audible packet loss is heard although using PingPlotter, a networking application that graphically shows a combination of PING and TRACEROUTE. This is showing that I have a 15ms route to the Allstar. Here is what I am seeing by tailing the messages log file:
[root@ROTW-ARC asterisk]# tail -f messages [Jun 20 01:58:14] WARNING[18794] chan_iax2.c: Resyncing the jb. last_delay -4, this delay -131072, threshold 1018, new offset -32 [Jun 20 02:00:22] WARNING[18790] chan_iax2.c: Resyncing the jb. last_delay -3, this delay 65535, threshold 1018, new offset -65567 [Jun 20 02:00:25] WARNING[18792] chan_iax2.c: Resyncing the jb. last_delay -1, this delay -65536, threshold 1020, new offset -31 [Jun 20 02:01:38] WARNING[18794] chan_iax2.c: Resyncing the jb. last_delay 2, this delay 65536, threshold 1020, new offset -65567 [Jun 20 02:02:36] WARNING[18789] chan_iax2.c: Resyncing the jb. last_delay 2, this delay -65534, threshold 1020, new offset -33 [Jun 20 02:06:14] WARNING[18786] chan_iax2.c: Resyncing the jb. last_delay 0, this delay 131075, threshold 1020, new offset -131108 [Jun 20 02:07:54] WARNING[18790] chan_iax2.c: Resyncing the jb. last_delay 6, this delay 65538, threshold 1020, new offset -196646 [Jun 20 02:08:04] WARNING[18790] chan_iax2.c: Resyncing the jb. last_delay 1, this delay -196606, threshold 1020, new offset -40 [Jun 20 02:11:50] WARNING[18789] chan_iax2.c: Resyncing the jb. last_delay 7, this delay 65539, threshold 1018, new offset -65579 [Jun 20 02:12:26] WARNING[18788] chan_iax2.c: Resyncing the jb. last_delay -3, this delay -65533, threshold 1018, new offset -46 [Jun 20 02:15:36] WARNING[18790] chan_iax2.c: Resyncing the jb. last_delay 5, this delay 65541, threshold 1020, new offset -65587 [Jun 20 02:15:43] WARNING[18793] chan_iax2.c: Resyncing the jb. last_delay -4, this delay -65542, threshold 1020, new offset –45
I am new to this but have had help from an exexperienced user.