Summary: | ASTERISK-13363: Similar to 0013884 but different version - chan_iax2 flood with 'No private structure for packet' | ||
Reporter: | Mikel Lindsaar (raasdnil) | Labels: | |
Date Opened: | 2009-01-14 05:31:23.000-0600 | Date Closed: | 2009-01-14 12:30:41.000-0600 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | Channels/chan_iax2 |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | I am having the same problem as ticket 0013884 but on Asterisk 1.6.0, not on 1.4.22. I am not sure if the chan_iax2 will apply cleanly to 1.6 or not. ****** ADDITIONAL INFORMATION ****** Here is a dump of the log: [Jan 14 22:18:17] WARNING[4696]: chan_iax2.c:4654 iax2_send: No private structure for packet? [Jan 14 22:18:47] WARNING[4696]: chan_iax2.c:4654 iax2_send: No private structure for packet? [Jan 14 22:19:07] WARNING[4701]: chan_iax2.c:4654 iax2_send: No private structure for packet? [Jan 14 22:19:37] WARNING[4704]: chan_iax2.c:4654 iax2_send: No private structure for packet? [Jan 14 22:19:57] WARNING[4699]: chan_iax2.c:4654 iax2_send: No private structure for packet? [Jan 14 22:20:27] WARNING[4699]: chan_iax2.c:4654 iax2_send: No private structure for packet? [Jan 14 22:20:47] WARNING[4697]: chan_iax2.c:4654 iax2_send: No private structure for packet? [Jan 14 22:21:17] WARNING[4702]: chan_iax2.c:4654 iax2_send: No private structure for packet? [Jan 14 22:21:37] WARNING[4696]: chan_iax2.c:4654 iax2_send: No private structure for packet? [Jan 14 22:22:07] WARNING[4698]: chan_iax2.c:4654 iax2_send: No private structure for packet? [Jan 14 22:22:27] WARNING[4699]: chan_iax2.c:4654 iax2_send: No private structure for packet? [Jan 14 22:22:57] WARNING[4700]: chan_iax2.c:4654 iax2_send: No private structure for packet? [Jan 14 22:23:17] WARNING[4704]: chan_iax2.c:4654 iax2_send: No private structure for packet? | ||
Comments: | By: Jason Parker (jparker) 2009-01-14 12:30:41.000-0600 This is a duplicate of ASTERISK-13057, as pointed out by the reporter. Please make any comments you have there, instead of creating a new bug report. |