License Limit Reached with Paging Group

[kkinnear]

Does each handset within a paging group count towards the concurrent call license limit? I have a client with a 16 sim call license and they can't seem to page more than 15 handsets via paging ring group.

Is this normal behavior? I assumed it would be considered 1, maybe 2 calls towards the license limit.

 

[eddv123]

A paging group should not have an effect on your simultaneous call count (unless thingshave changed recently).

I would enable the voicemail notification for SC count reach to confirm this but I still don't think it should be an issue.

 

[leejor]

Does the Activity Log show any reason for this (error message?) when it happens?

 

[eddv123]

In the activity log I've seen it before record the limit reach but not a reason why.

The way ive always detected this would be - the simultaneous call counter on the PBX dashboard, email notification or when you make the call which puts you over the limit a recording is played.

 

[kkinnear]

I have the email notification setup for license limit but don't receive one. I do however see it spike on the dashboard as a single call to each paged handset and a call from my handset

Is there anyway around this limit the customer has roughly 30 phones and definitely doesn't need or want to pay for the 32 sim call license

 

[eddv123]

If you don't receive an email then it wont be a licence limit issue.

What you are seeing on the main dashboard (the spike) is most likely due to resources. Ensure that your 3CX machine has enough allocated: https://www.3cx.com/docs/recommended-hardware-specifications-for-3cx/

You could try the following benchmarking tool on your server (Outside of working hours of course).
http://ssd.userbenchmark.com/

It'll tell you in a nutshell how well most components on your machine are running thus helping you identify whether this is a hardware issue or not.

 

[CentrexJ]

Switch to multicast paging. Much more efficient than sip paging.

 

[YiannisH_3CX]

Hello @kkinnear

Please note that paging only uses 1 simultaneous call so i would not think the client is reaching the simultaneous call limit. In the number of active calls is use on the dashboard you will see 16 call legs but that does not reflect to the licence limit counter.
What version PBX are you using?

 

[kkinnear]

Hello @kkinnear

Please note that paging only uses 1 simultaneous call so i would not think the client is reaching the simultaneous call limit. In the number of active calls is use on the dashboard you will see 16 call legs but that does not reflect to the licence limit counter.
What version PBX are you using?

The spike is not resources. It is the Number of Calls in Use. When I open that page to see active calls and place a page, it shows one call for the user placing the call and then a call for each handset receiving the page.

The PBX is currently running the latest version of 15.5

 

[YiannisH_3CX]

The spike is not resources. It is the Number of Calls in Use. When I open that page to see active calls and place a page, it shows one call for the user placing the call and then a call for each handset receiving the page.

The number of the active calls tab reflects the number of call legs that is not the same as Simultaneous calls. It correctly shows that a call leg is active for each extension but that is actually one call.
The call legs count can actually be larger than the number of simultaneous calls. For example 20/16.

Try the following. Make a paging call to all extensions to replicate the issue. While the call is active try a call between 2 extensions and see if that works.