Summary: | ASTERISK-04609: iax predicted timestamp skew | ||
Reporter: | Matthew Simpson (matthewsimpson) | Labels: | |
Date Opened: | 2005-07-17 21:39:41 | Date Closed: | 2011-06-07 14:10:05 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | Core/General |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | Jul 17 21:34:30 DEBUG[20128] chan_iax2.c: predicted timestamp skew (429496731) > max (160), using real ts instead. Jul 17 21:34:30 DEBUG[20250] chan_iax2.c: predicted timestamp skew (429496746) > max (160), using real ts instead. Jul 17 21:34:30 DEBUG[19736] chan_iax2.c: predicted timestamp skew (429496739) > max (160), using real ts instead. Jul 17 21:34:30 DEBUG[19164] chan_iax2.c: predicted timestamp skew (1719993509) > max (160), using real ts instead. Jul 17 21:34:30 DEBUG[19249] chan_iax2.c: predicted timestamp skew (1719866021) > max (160), using real ts instead. Jul 17 21:34:30 DEBUG[20255] chan_iax2.c: predicted timestamp skew (429496745) > max (160), using real ts instead. Jul 17 21:34:30 DEBUG[19310] chan_iax2.c: predicted timestamp skew (1802120) > max (160), using real ts instead. Jul 17 21:34:30 DEBUG[20128] chan_iax2.c: predicted timestamp skew (429496739) > max (160), using real ts instead. Jul 17 21:34:30 DEBUG[20250] chan_iax2.c: predicted timestamp skew (18720) > max (160), using real ts instead. ****** ADDITIONAL INFORMATION ****** * could be related to bug 4730 * running CVS 07-17 * using Asterisk as Media Gateway. Zap channel --> IAX * not using iax trunking * not using jitterbuffer or PLC | ||
Comments: | By: Tilghman Lesher (tilghman) 2005-07-17 22:46:36 What's the version of Asterisk or whatever peer you're using on the remote IAX end? By: Matthew Simpson (matthewsimpson) 2005-07-18 00:26:16 remote end is CVS HEAD 06-11-05 By: Matthew Simpson (matthewsimpson) 2005-07-18 00:48:04 seeing errors in remote CVS 06-11-05 log: Jul 18 00:46:24 DEBUG[22040] chan_iax2.c: predicted timestamp skew (1127) > max (160), using real ts instead. By: twisted (twisted) 2005-07-18 00:58:37 how is that an error? Looks like a debug statement to me.. By: Matthew Simpson (matthewsimpson) 2005-07-18 01:03:03 semantics. By: twisted (twisted) 2005-07-18 01:24:59 actually, it's not semantics. you wouldn't even see those unless you had debug turned on. I'm assuming there was some underlying problem though? If so, what were the symptoms? By: Matthew Simpson (matthewsimpson) 2005-07-18 01:50:11 the "underlying problem" was a 1GB debug file in a manner of hours. there doesn't seem to be any kind of audio issues, but, as I mentioned in the bugnotes, i'm not using JB, trunk, or PLC. By: Tilghman Lesher (tilghman) 2005-07-18 08:43:13 Please turn off debug in your log unless you are diagnosing a specific issue. What it looks like is that you have a problem with a harmless message. By: Tilghman Lesher (tilghman) 2005-07-18 09:20:00 Closing due to lack of specific issue |