[asterisk-bugs] [JIRA] Commented: (ASTERISK-14988) [patch] Not all SIP extensions receive a page

[Matt Jordan (JIRA)]

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

Matt Jordan commented on ASTERISK-14988:
----------------------------------------

Based on aragon's comments, it feels the best answer to this problem is that a work around is available - which is to say, don't page all devices in a single shot.

That being said, in Asterisk 11, app_page has been converted over to use ConfBridge and the bridging layer for mixing internally instead of chan_dahdi.  This should also improve performance of app_page, and let it handle more devices reliably.

As such, I'm going to close this issue out as "workaround available".  If you require higher performance from app_page, you may want to consider Asterisk 11.

> [patch] Not all SIP extensions receive a page
> ---------------------------------------------
>
>                 Key: ASTERISK-14988
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-14988
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Applications/app_page
>            Reporter: aragon
>         Attachments: 16073-1.4.24.1.diff, pagingcontext.txt, pagingtest.txt
>
>
> I have 187 SIP extensions configured to receive a page.
> Dial plan looks correct but when CLI is watched during paging execution only 140 phones receive the paging execution.
> ****** ADDITIONAL INFORMATION ******
> Attaching dial plan configuration.
> Attaching CLI during test page.
> Asterisk 1.4.24.1
> I marked as major priority since paging is used to broadcast emergency paging notification to tenant and not all devices can hear paging.
> Two dual core Pentium 2.8 Xeon
> 4 GB RAM installed.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira