| Summary: | ASTERISK-19315: Impossibly High Lagged Value (Asterisk 1.8.8.1) | ||
| Reporter: | Nicholas Blasgen (nblasgen) | Labels: | |
| Date Opened: | 2012-02-08 15:57:41.000-0600 | Date Closed: | 2012-03-13 11:02:46 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Channels/chan_sip/General |
| Versions: | 1.8.8.2 | Frequency of Occurrence | Frequent |
| Related Issues: | |||
| Environment: | CentOS 5.x | Attachments: | |
| Description: | [Feb 8 13:02:45] NOTICE[4482] chan_sip.c: Peer 'vitelity' is now Lagged. (1590071263ms / 0ms) [Feb 8 13:05:15] NOTICE[4482] chan_sip.c: Peer 'vitelity' is now Lagged. (1590221171ms / 0ms) [Feb 8 13:06:06] NOTICE[4482] chan_sip.c: Peer 'vitelity' is now Lagged. (1590271743ms / 0ms) [Feb 8 13:06:25] NOTICE[4482] chan_sip.c: Peer 'vitelity' is now Lagged. (1590291492ms / 0ms) [Feb 8 13:07:04] NOTICE[4482] chan_sip.c: Peer 'vitelity' is now Lagged. (1590329801ms / 0ms) [Feb 8 13:08:28] NOTICE[4482] chan_sip.c: Peer 'vitelity' is now Lagged. (1590414432ms / 0ms) [Feb 8 13:10:46] NOTICE[4482] chan_sip.c: Peer 'vitelity' is now Lagged. (1590551668ms / 0ms) [Feb 8 13:12:32] NOTICE[4482] chan_sip.c: Peer 'vitelity' is now Lagged. (1590657807ms / 0ms) [Feb 8 13:13:04] NOTICE[4482] chan_sip.c: Peer 'vitelity' is now Lagged. (1590689815ms / 0ms) [Feb 8 13:16:38] NOTICE[4482] chan_sip.c: Peer 'vitelity' is now Lagged. (1590903864ms / 0ms) [Feb 8 13:20:15] NOTICE[4482] chan_sip.c: Peer 'vitelity' is now Lagged. (1591121146ms / 0ms) [Feb 8 13:21:06] NOTICE[4482] chan_sip.c: Peer 'vitelity' is now Lagged. (1591171749ms / 0ms) [Feb 8 13:21:25] NOTICE[4482] chan_sip.c: Peer 'vitelity' is now Lagged. (1591191492ms / 0ms) [Feb 8 13:22:04] NOTICE[4482] chan_sip.c: Peer 'vitelity' is now Lagged. (1591229800ms / 0ms) [Feb 8 13:23:26] NOTICE[4482] chan_sip.c: Peer 'vitelity' is now Lagged. (1591311702ms / 0ms) [Feb 8 13:25:46] NOTICE[4482] chan_sip.c: Peer 'vitelity' is now Lagged. (1591451666ms / 0ms) [Feb 8 13:26:28] NOTICE[4482] chan_sip.c: Peer 'vitelity' is now Lagged. (1591494002ms / 0ms) [Feb 8 13:28:34] NOTICE[4482] chan_sip.c: Peer 'vitelity' is now Lagged. (1591620201ms / 0ms) [Feb 8 13:32:22] NOTICE[4482] chan_sip.c: Peer 'vitelity' is now Lagged. (1591848130ms / 0ms) [Feb 8 13:36:06] NOTICE[4482] chan_sip.c: Peer 'vitelity' is now Lagged. (1592071753ms / 0ms) [Feb 8 13:36:18] NOTICE[4482] chan_sip.c: Peer 'vitelity' is now Lagged. (1592084314ms / 0ms) [Feb 8 13:40:46] NOTICE[4482] chan_sip.c: Peer 'vitelity' is now Lagged. (1592351667ms / 0ms) [Feb 8 13:44:29] NOTICE[4482] chan_sip.c: Peer 'vitelity' is now Lagged. (1592575326ms / 0ms) [Feb 8 13:49:49] NOTICE[4482] chan_sip.c: Peer 'vitelity' is now Lagged. (1592894658ms / 0ms) Qualify is turned off: Name/username Host Dyn Forcerport ACL Port Status vitelity 64.2.142.94 N 5060 Unmonitored This is behind a NO-NAT device and there's a suspecion it's somehow related. But the main question is, what in the world is the system monitoring when we have OPTION packets disabled? The host is something like 30ms away from us... no idea where such a large number comes from. | ||
| Comments: | By: Nicholas Blasgen (nblasgen) 2012-02-08 16:28:40.514-0600 One of my techs noticed that the values keep increasing by a fairly large number each time. By the way, I'm having some issues with 1.8.9 and MPLAYER which is why I haven't been able to upgrade. By: Matt Jordan (mjordan) 2012-02-09 16:45:22.443-0600 We require a complete debug log to help triage the issue. This document will provide instructions on how to collect debugging logs from an Asterisk machine for the purpose of helping bug marshals troubleshoot an issue: https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information By: Matt Jordan (mjordan) 2012-03-13 11:02:38.505-0500 Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested. Further information can be found at http://www.asterisk.org/developers/bug-guidelines | ||