[asterisk-bugs] [JIRA] (ASTERISK-21328) ISDN PRI Release Delay

[Richard Mudgett (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-21328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=204737#comment-204737 ] 

Richard Mudgett commented on ASTERISK-21328:
--------------------------------------------

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.
                
> ISDN PRI Release Delay
> ----------------------
>
>                 Key: ASTERISK-21328
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21328
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Channels/chan_dahdi
>    Affects Versions: 1.8.11.1
>         Environment: CentOS 5.9 64bit on Dell 2950 with 4xPRI Digium
>            Reporter: Antonis Psaras
>            Severity: Minor
>
> 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?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira