[asterisk-bugs] [Asterisk 0010608]: Wrong timestamp in IAX2 packets
noreply at bugs.digium.com
noreply at bugs.digium.com
Thu Aug 30 09:37:40 CDT 2007
The following issue has been RESOLVED.
======================================================================
http://bugs.digium.com/view.php?id=10608
======================================================================
Reported By: malaiwah
Assigned To: russell
======================================================================
Project: Asterisk
Issue ID: 10608
Category: Channels/chan_iax2
Reproducibility: random
Severity: major
Priority: normal
Status: resolved
Asterisk Version: 1.2.21.1
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
Resolution: won't fix
Fixed in Version:
======================================================================
Date Submitted: 08-30-2007 09:27 CDT
Last Modified: 08-30-2007 09:37 CDT
======================================================================
Summary: Wrong timestamp in IAX2 packets
Description:
I have an issue where our two 1.2.21.1 asterisk servers are stopping
talking to each other. After many nights of trying to figure out why, I
stumbled upon a packet trace I was doing.
In wireshark, I see that timestamps for source calls 1 and 3 are going
from <100ms to 4294962764 ms and then going back to normal values again. Is
this wireshark acting on me ? (wrong-timestamp-exibit-a.dump)
Some time again, it does the same thing. (wrong-timestamp-exibit-b.dump)
The reason I'm asking this is because when this event happen,
(wrong-timestamp-exibit-c.dump) it sometimes makes our two Asterisk servers
stop talking to each other, just like in the last wireshark dump I'll
attach.
.85 is trying to talk with .87 and receives no answer.
======================================================================
----------------------------------------------------------------------
russell - 08-30-07 09:37
----------------------------------------------------------------------
Asterisk 1.2 is no longer maintained except for security fixes. If you
experience this issue with Asterisk 1.4, feel free to report it. Thanks
Issue History
Date Modified Username Field Change
======================================================================
08-30-07 09:37 russell Status new => resolved
08-30-07 09:37 russell Resolution open => won't fix
08-30-07 09:37 russell Assigned To => russell
08-30-07 09:37 russell Note Added: 0069706
======================================================================
More information about the asterisk-bugs
mailing list