SBC SWe Lite Performance Numbers
| Performance Value |
---|
100 S | 10 cps |
M | |
Maximum number of RTP ↔ RTP media sessions (direct media, RTP proxy, or media services mode) | 100 |
Maximum number of transcode sessions (media services mode) | 25 |
Call Setup – Maximum call setup rate | 10 cps |
Registrations – Maximum number of registered users | 1,000 |
Encryption – Maximum number of RTP ↔ SRTP sessions (media services mode) | 25 |
Call Capacity Limitation with Additional Logging
Call capacity is limited to calls per second when Info level logging is enabled. Additional logging verbosity reduces the call capacity.
Although the call setup rate is 10 calls per second, if Call Admission Control (CAC) is enabled, calls over the rate limit will be rejected with the message 480 Temporary Not Available.
The SBC SWe Lite supports the following maximum configuration.
SBC SWe Lite Maximum Configuration Values
Feature | Maximum supported |
---|
|
---|
Number of Signaling Groups | 100 |
Cumulative number of channels across all the Signaling Groups | 600 |
Call Route Entries (all Call Route Tables combined) | 1,000 |
| 1,024 |
Registrar Table entries | 600 |
Registrant Table entries | 600 |
Transformation Table entries | 1,000 |
Media Profiles entries | 20 |
Callback Number Tables | 80 |
Callback Numbers (in Callback Numbers List) | 16 |
The
Unable to show "metadata-from": No such page "_space_variables"
supports local call forking up to eight separate destinations. Additionally, the
Unable to show "metadata-from": No such page "_space_variables"
supports up to 20 early dialog responses and 20 calls forked downstream.
Any SIP ↔ SIP call consumes a single SIP session, for the life of the call, within the pool of SIP sessions that have been activated through a license submission..
No SIP session is consumed from the pool of licensed SIP sessions when a SIP ↔ SIP call has on any one leg any one of the following devices:
You do not need to purchase a license for these SIP ↔ SIP calls because the
Unable to show "metadata-from": No such page "_space_variables"
will make accommodations.
If multiple calls arrive simultaneously, the
Unable to show "metadata-from": No such page "_space_variables"
will service the calls until it reaches a CPU usage threshold (~%).
on the CAC or logs could exacerbate this issue.
Media Services:
- Signaling Session: The information exchange concerning the establishment and control of a telecommunication circuit and the management of the network.
- RTP Proxy mode: A session that is not subject to DSP services but flows through the
Unable to show "metadata-from": No such page "_space_variables"
for non-media intervention purposes (e.g., IP headers being modified for revised network addressing, etc.) is considered a session running in RTP Proxy mode and does not use any DSP resources. - Direct Media mode: A session that is not subject to, and does not flow through, the
Unable to show "metadata-from": No such page "_space_variables"
is considered a session running in Direct Media mode. Sessions running in Direct Media mode do not use any Unable to show "metadata-from": No such page "_space_variables"
media processing resources including DSP resources. - A media session that requires some form of media manipulation such as encryption decryption, transcoding, etc.