[asterisk-bugs] [JIRA] (ASTERISK-26881) bridge_channel.c:989 ast_bridge_channel_queue_frame: We couldn't write alert pipe for Local/XXXXXXX at dialpeer. something is VERY wrong

[Rusty Newton (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-26881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rusty Newton updated ASTERISK-26881:
------------------------------------

    Assignee: Private Name
      Status: Waiting for Feedback  (was: Triage)

In addition to a debug log demonstrating the error, and the events happening before and after it, you should attach the dialplan in use within the extension called.

At what rate does this error occur, and on how many calls out of your 600?

>  bridge_channel.c:989 ast_bridge_channel_queue_frame: We couldn't write alert pipe for Local/XXXXXXX at dialpeer. something is VERY wrong
> --------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-26881
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26881
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_local
>    Affects Versions: 14.3.0
>         Environment: Linux 64
>            Reporter: Private Name
>            Assignee: Private Name
>            Severity: Critical
>
> After 600 calls, all of them achieved by 
> Originate Local/XXXXXXXXXX at dialpeer application MusicOnHold default
> Note: all calls are dialed with PJSIP inside the context.
> I get this error:
> [Mar 18 00:18:01] ERROR[40175][C-000004cb]: bridge_channel.c:989 ast_bridge_channel_queue_frame: We couldn't write alert pipe for 0x7ff39000fd90(Local/XXXXXXX at dialpeer-000004cc;2)... something is VERY wrong
> Please let me know where to start looking for the culprit.



--
This message was sent by Atlassian JIRA
(v6.2#6252)