This document describes the definition of different CUSP license states and what needs to be done when you identify CUSP license states. CUSP uses Cisco Smart Manager to register and authorize license.
You must have a valid account in Cisco Smart Manager to configure smart licensing for Cisco Unified SIP Proxy.
There are different states with CUSP's lisence, and each state causes CUSP to handle calls differently. Enforcement modes are as below:
Enforcement modes determines the mode of license usage once entitlement (license count) is requested.
Eval When CUSP is undentified state or registered state, enforcement mode is eval.
Evaluation period is for 90 days by default. Calls will be allowed in this state. Evaluation period starts the moment smart lciense is enabled. If registration or authorization requests fail, CUSP moves to Eval. mode.
InComplaince license count requested to ther server is within the purchased limits.
OutOfcomplaince license count requested is more than what is avialable/purchased in Cisco Smart Manage.
Request is honored here and calls are allowed. There is no impact on call handling.
EvalExpried Evaluation period has expired. Calls is not be allowed in this mode.
AuthorizationExpired Authorization period has expired. Calls is not be allowed in this mode.
Image below, summerizes CUSP state's license and the result of each state.
License States diagram
From this image Check License Usage state is based on adding all CUSP server's configured counts and it compares with purchased license count. Check License Usage state is NOT the real time Call Per Second (CPS) count.
You must check license purchased and usage from Cisco Smart License website:
This image shows where to check current CUSP license state from CUSP admin GUI page.
Unlike license usage check, in CPS checking if this is over the configured license count, prior to vCUSP 9.1.5 CUSP rejects calls immediately due to license limit. The response messages are 500 or 503 error messages.
CUSP keeps count of the calls and records a snapshot every 30 seconds for a window time of 5 minutes. The average CPS for these 5 minutes records must be well under the license's limit. If the average goes higher than the limit, then CUSP starts rejecting the calls. If the call volume stays consistently high, then CUSP does not resume service until the CPS drops to the limit.
You must enable failed call logging to see rejected calls.
This image shows where to enable Failed Call Log.
Enable Failed Call logging
Message Flow and contents
Token [ hash generated for the customer account in samrt manager ]
Software Tag Identifier ( CUSP software ID)
[UDI|SN#*] (CUSP will generated 11 char random string for SN)