Page History

...

A SIP session for licensing purposes ("SIP session license") is a call (audio/audio+video) under SBC direction. Details are as follows:

• A SIP session license is a SIP transaction that establishes a bi-directional audio/video media exchange (RTP media stream) between two ports on the SBC.
• SIP sessions are established by the SBC when the system has recognized the availability of SIP session license "tokens"  in the SIP session license token pool.
  
• SIP session license tokens are added to the pool when a SIP session license has been successfully applied to the SBC. For example, the SBC-1K-LIC25SIP license adds 25 SIP session license tokens to the SBC SIP session license pool.
• To set up the call, the SBC grabs a license token from the purchased SIP session license pool, sets up the call for the bi-directional RTP media stream, and then releases the license token after the call is taken down.
• The media does not have to actually flow through the SBC; the license token is still grabbed to set up the media flow, whether or not the media physically transits the SBC.
• It is possible to consume more than one SIP session license during a single call between two SIP clients. For example, a call that "hairpins" (i.e. one pair of ports supports one RTP media stream through the SBC, and another pair supports a second media stream through the SBC) will consume two SIP session licenses.

SIP transactions that are not directly related to a call setup/tear down are not licensed through the SIP session licenses. Generally, these transactions are free (e.g. SUBSCRIBE, etc.) except when they fall under a chargeable feature. For example, the SBC supports SUBSCRIBE method pass through related transactions (For example, one SIP client to inform another that a message is waiting, etc.) in a way that is limited by available CPU resources, and not by licenses.

For more information on available SIP session license available for purchase, and the procedure to apply licenses to a given SBC device, please refer to Working with Licenses.

Exceptions

A SIP session license is not consumed from the pool of licensed SIP sessions when a SIP↔SIP call has, on all legs (ingress and egress), any one of the following devices identified as the subtended peer:

...