| Summary: | ASTERISK-21792: chan_sip.c: Autodestruct on dialog X with owner X in place (Method: BYE). Rescheduling destruction for X | ||
| Reporter: | Antony prakash (prakasan) | Labels: | |
| Date Opened: | 2013-05-20 04:26:41 | Date Closed: | 2013-05-21 18:17:05 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | . I did not set the category correctly. |
| Versions: | 1.8.20.1 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | PROD | Attachments: | |
| Description: | Hi Team,
We are getting exception in the messages logs "WARNING[7337] chan_sip.c: Autodestruct on dialog '01B25BF11F2800B0001DAD17@x.x.x.x' with owner SIP/x.x.x.x-00000e2a in place (Method: BYE). Rescheduling destruction for 10000" after Upgrading Asterisk version from 1.4.42 to 1.8.20.1 Could you please advise, how to fix this issue Due to this issue, calls were automatically initiating from the host server to the service provider for every 10 secs Note:while roll back to previous version 1.4.42..there is no issue.. | ||
| Comments: | By: Antony prakash (prakasan) 2013-05-20 23:05:16.716-0500 Could you please advise on this ASAP. By: Rusty Newton (rnewton) 2013-05-21 18:17:05.760-0500 Hi! This WARNING message is not a bug. In fact it's not an ERROR either. {quote} WARNING[7337] chan_sip.c: Autodestruct on dialog '01B25BF11F2800B0001DAD17@x.x.x.x' with owner SIP/x.x.x.x-00000e2a in place (Method: BYE). Rescheduling destruction for 10000" {quote} An upgrade from 1.4.X to 1.8.X is a major upgrade. There are numerous differences all over Asterisk in how things operate. Most likely you have some misconfiguration for the new environment. Unfortunately this one WARNING message won't tell you what is wrong. issues.asterisk.org is a place for bug reports and is not a support forum for troubleshooting. Using Google I found some helpful information for you on that message: * http://forums.asterisk.org/viewtopic.php?f=1&t=86221 * http://stackoverflow.com/questions/7599934/asterisk-issue-autodestruct-on-dialog-with-owner-in-place-method-bye Reading through that should give you some clues to help locate the issue. If you need further help then you may want to post and ask for help on the users list. http://www.asterisk.org/community/discuss The users on the list won't be able to help you by looking at that one log message. You'll need to provide them Asterisk logs showing the actual problem. https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information I'll go ahead and close this out since this is not a bug report. Thanks! | ||