| Summary: | ASTERISK-21328: ISDN PRI Release Delay | ||
| Reporter: | Antonis Psaras (apsaras) | Labels: | |
| Date Opened: | 2013-03-28 06:38:56 | Date Closed: | 2013-03-29 18:08:24 |
| Priority: | Minor | Regression? | |
| Status: | Closed/Complete | Components: | Channels/chan_dahdi |
| Versions: | 1.8.11.1 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | CentOS 5.9 64bit on Dell 2950 with 4xPRI Digium | Attachments: | |
| Description: | Some Carriers are using IMS systems to provide PRI Lines to customers. These IMS systems need to clear the full path of a channel before is actually released and get ready to be used again.
In our situation, we are using Dahdi/R1 to get an idle channel, Asterisk sends the request to the carrier for a channel known to be free, and the carrier switch responds with cause code 34. The reason for that is probably the delay of IMS to release the channel. Is there any parameter on chan_dahdi.conf to introduce a relase delay? Can this be introduced on LibPRI? | ||
| Comments: | By: Richard Mudgett (rmudgett) 2013-03-28 12:12:04.252-0500 Features requests are no longer submitted to or accepted through the issue tracker. Features requests are openly discussed on the mailing lists [1] and Asterisk IRC channels and made note of by Bug Marshals. [1] http://www.asterisk.org/support/mailing-lists There is no delay option like that in chan_dahdi.conf. By: Rusty Newton (rnewton) 2013-03-29 18:08:24.270-0500 If you haven't contacted Digium technical support for the issue (http://www.digium.com/en/support/contact) - you might consider doing that just to have them verify this is not solvable through currently available configuration. They are better equipped to work with you closely and the JIRA issue tracker is not a support forum. We don't accept feature requests on the tracker generally unless they are accompanied by a patch. | ||