[asterisk-bugs] [JIRA] (PRI-149) Frequent MDL-ERROR (F) messages when over 100 calls

[Tyler Stewart (JIRA)]

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

Tyler Stewart edited comment on PRI-149 at 12/7/12 2:01 PM:
------------------------------------------------------------

Still no update from the customer. I'm closing their case -- it'll reopen if they get back to us, and I'll update this issue as well. In the meantime, it's safe to close it.

Thanks for your help.

Edit: The customer replied back today and said that they were never able to try the patch. Instead they moved from PRI to SIP, and everything is apparently running fine currently.
                
      was (Author: tstewart):
    Still no update from the customer. I'm closing their case -- it'll reopen if they get back to us, and I'll update this issue as well. In the meantime, it's safe to close it.

Thanks for your help.
                  
> Frequent MDL-ERROR (F) messages when over 100 calls
> ---------------------------------------------------
>
>                 Key: PRI-149
>                 URL: https://issues.asterisk.org/jira/browse/PRI-149
>             Project: LibPRI
>          Issue Type: Bug
>      Security Level: None
>         Environment: Asterisk 1.6.2.24
> DAHDI 2.6.1
> TE420 x2
> We are in the process of getting more detailed (autosupport) information from the customer.
>            Reporter: Tyler Stewart
>            Assignee: Richard Mudgett
>         Attachments: jira_pri_149_v1.4.13.patch
>
>
> When the system has more than 100 concurrent PRI calls, the customer is seeing the following error message:
> {noformat}
> Trying to queue MDL-ERROR (F) when MDL-ERROR (F) is already scheduled
> {noformat}
> The customer is concerned about this, and would like to know what it means and if it's anything they should be worried about.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira