| Summary: | ASTERISK-02679: Asterisk sending PRI restarts every hour | ||
| Reporter: | mshearer (mshearer) | Labels: | |
| Date Opened: | 2004-10-25 23:26:54 | Date Closed: | 2011-06-07 14:10:14 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | chan_zap is restarting every IDLE channel every hour. This appears to be design intent. However, I don't believe this is in accordance to the Q.931 specs. Here's an excerpt: 5.5 Restart procedure The restart procedure is used to return calls to the Null state or the interface to an idle condition. The procedure is usually invoked when the other side of the interface does not respond to other call control messages or a failure has occurred (e.g. following a data link failure, when a backup D-channel can be used, or following the expiry of timer T308 due to the absence of response to a clearing message). It may also be initiated as a result of local failure, maintenance action or mis-operation. This is causing some headaches for us because some of the adjacent switches we interconnect to are recording invalid Operational Measurements (OMs) with respect to the state of the PRI. | ||
| Comments: | By: Mark Spencer (markster) 2004-10-25 23:52:53 This is a maintenance action and thus in accordance with the spec. By: Mark Spencer (markster) 2004-10-25 23:55:00 I will however entertain a properly disclaimed patch to make the feature optional. | ||