| Summary: | ASTERISK-10204: Wrong timestamp in IAX2 packets | ||
| Reporter: | Michel Belleau (malaiwah) | Labels: | |
| Date Opened: | 2007-08-30 09:27:50 | Date Closed: | 2007-08-30 09:37:40 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_iax2 |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) wrong-timestamp-exibit-a.dump ( 1) wrong-timestamp-exibit-b.dump ( 2) wrong-timestamp-exibit-c.dump | |
| 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. ****** ADDITIONAL INFORMATION ****** I'll attach the three mentionned files shortly. | ||
| Comments: | By: Russell Bryant (russell) 2007-08-30 09:37:40 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 | ||