licensing limits...

Status
Not open for further replies.

narrington

Trial User
Joined
Mar 14, 2019
Messages
44
Reaction score
8
So I'm not sure if this is a licensing issue, or just an incorrect setting somewhere, but we have an enterprise license (16SC) I expect the call limit of 16 calls, but we have hit that limit every day with only 11 people calling into a meeting...

this is the message I see in the activity log:
Code:
03/26/2020 9:32:32 AM - [CM101006]: License Limit: Number of simultaneous calls covered by current license has been exceeded. Call(C:999) from Line:10000<<4405196716 has been rejected. Active calls: [974,975,976,977,978,979,980,981,982,983,984,985,986,987,988,989,999]

and like I said, there's only 11 people in the meeting! what the heck?!?

I don't know if it's pertinent but all 11 people are on remote phones (quarantine) with SBCs (just cloned a bunch of raspberry pi's per this guide). all 11 SBCs are connected and appear to be working as desired...
 
The log shows the active calls, have you gone back through the log, to get more details, of each of the listed calls?
 
The log shows the active calls, have you gone back through the log, to get more details, of each of the listed calls?

that lead me down a rabbit hole... yeah. found the issue. people aren't calling the extension, they're calling the DID for the conference line.

each one eats up two seats.

I can't facepalm hard enough.
 
  • Like
Reactions: Evolute IT
So, in your outbound rules (if people keep doing this after being told NOT to), block the DID number.
 
  • Like
Reactions: CentrexJ
facepalm for sure.

Do a generic sip trunk with an ip of 127.0.0.1 and send outbound calls to the DID to the Generic Sip Trunk which directs to ext 70 (or whatever the conf. ext. is).
 
  • Like
Reactions: AlexanderReichert
I am glad I am not the only facing this issues that people dialing DID instead of extension. I went the route to block the DID on outbound
 
facepalm for sure.

Do a generic sip trunk with an ip of 127.0.0.1 and send outbound calls to the DID to the Generic Sip Trunk which directs to ext 70 (or whatever the conf. ext. is).
This is a slick solution. The only reason that I didn't go with that it promotes bad behavior. They should just learn what an extension is in my opinion.
Alexander
 
can't fix stupid... but your way works better...
rethinking it through - I think it will use 2 licenses... it just doesn't cost you any money... the way it was happening now - each person calling in from the DID was an outbound call and an inbound call - twice the expense...
I've often thought the system should evaluate inbound rules for outbound calls, before evaluating outbound rules... so if a number is in the inbound list - follow the route.
 
I've often thought the system should evaluate inbound rules for outbound calls, before evaluating outbound rules... so if a number is in the inbound list - follow the route.
The outbound rules should include the option, of sending a number, or range, to an internal extension number, be it a ring group, queue, or actual extension. It would then count as one call, rather than the two you would use, going through a " loop trunk".
 
  • Like
Reactions: AlexanderReichert
Maybe good to post that in the ideas forum, if that is not already in there
 
Unfortunately, with the restrictions put in place on the Ideas Forum, some time back, I, like a number of other forum members, are unable to do that any longer.
 
I wound up putting in an outbound rule to block calls to that DID. It would be nice to have a rule for each DID that if that number is dialed, the pbx redirects to the extension (this is how cisco, Hitachi, and NEC do it)... but as stated somewhere, that's just accounting for bad/wasteful behavior. I'll just stick with the DID call blocking.
 
Status
Not open for further replies.

Forum statistics

Threads
111,941
Messages
589,854
Members
164,832
Latest member
Boblatino