06-27-2014, 10:53 PM
(06-27-2014 05:16 PM)Yealink Support Wrote: [ -> ]Hi blistovmhz,
I should tell you my email address. Could you please send it again to wilson@yealink.com? It is my email address.
thanks in advance.
emailed.
Pages: 1 2
06-27-2014, 10:53 PM
06-28-2014, 11:20 AM
Ok, thanks
07-18-2014, 12:03 PM
Turns out the issue is with Asterisk. There is a hard coded limit in Asterisk for the number of subscribe notifies a single ext can request. I believe it's somewhere around 100/minute. When you have >100 ext's being monitored, and you try to page them all simultaneously, they first ring (that's 100 notifies) and then they go busy (another 100 notifies).
I gave up and just used multicast paging instead. Uses tonnes less resources, and doesn't affect BLF status at all.
I gave up and just used multicast paging instead. Uses tonnes less resources, and doesn't affect BLF status at all.
07-19-2014, 11:27 AM
OK, thanks for your reply.
Do you mean this issue doesn't exsit in the other PBX server? Right?
Our R&D suggestion is that set the Asterisk server T1 timer value too less, more than 500ms.
If it still fail, please register your account use UDP transmission mode. And try again.
Hope it can help you.
Do you mean this issue doesn't exsit in the other PBX server? Right?
Our R&D suggestion is that set the Asterisk server T1 timer value too less, more than 500ms.
If it still fail, please register your account use UDP transmission mode. And try again.
Hope it can help you.
Pages: 1 2