You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

 

In this section:

SBC SWe Lite Call Performance

 

SBC SWe Lite Performance Numbers

Description

Performance Value

100 Sessions (SIP signaling setup rate)

10 cps

Maximum number of SIP ↔ SIP sessions

100 

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 4 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.

SBC SWe Lite Single Instance Capacities

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

Static Routes1,024

Registrar Table entries

600

Registrant Table entries

600

Transformation Table entries

1,000

Media Profiles entries

20

Callback Number Tables80
Callback Numbers (in Callback Numbers List)16

Call Forking

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.

SIP Licensing

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.. 

Exceptions

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:

  • SBC Edge
  • VX
  • Tenor

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.

Burst Behavior

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 (~80%).

  • When the threshold is reached the 
    Unable to show "metadata-from": No such page "_space_variables"
    will reject calls until it reaches a "safe" level (~60% CPU usage).
  • When the "safe" level is reached, the
    Unable to show "metadata-from": No such page "_space_variables"
     will begin accepting new calls.

Turning on the CAC or logs could exacerbate this issue.

Media Services:

  • • Supported codecs (including for transcode operations): G.711, G.722, G.722.2 (AMR-WB), G.723.1 (5.3 kbps, 6.3 kbps), G.726 (32 kbps), G.729A/B (8 kbps)
  • • DTMF/RFC4733; Inband DTMF; SIP INFO/RFC-2833
  • • Voice Activity Detection (VAD)
  • • G.168 Echo Cancellation with standard 128 ms tail length

Definitions

  • Signaling Session: The information exchange concerning the establishment and control of a telecommunication circuit and the management of the network. 
  • Media Session: Bi-driectional RTP/SRTP media flow associated with and under the direct control of a SIP signaling session.
    • 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.
    • Media Services mode: A media session that requires some form of media manipulation such as encryption decryption, transcoding, etc.

  • No labels