6.6
Restrictions/Useful Information
In order to decouple the release cycles of OS-SBC/OSB from the OpenScape 4000 releases, because the OS-SBC image delivered with the OpenScape 4000 will be outdated quickly with respect to the latest version, the stock OS-SBC image, starting with V8R2, has been removed. Another reason for that is to have the future possibility to upload OpenScape Branch (OSB) images as well.
The "Revert to stock SBC image" function has been withdrawn because the revert will mean to upload another OS-SBC version. It is no longer supported to install V8R2 with enabled SBC (SBC data in xml) as there is no more Stock image included in the ISO.
OS4K platform keeps of course the ability to import/ update the (.bz2) images of OS-SBC (and for the future also the OSB) via Portal->OpenScape SBC Software Management, therefore the 'SBC Software Management' link will always be shown. The first step is to upload an OS-SBC image. Only then the "Enable SBC" switch from LAN Configuration will be active.
The Hosted OS-SBC uses Native Locking ID as it does not run on a VMware machine. The Native Locking ID can be retrieved as in usual OS-SBC installations via the OS-SBC WBM -> License. (Hit Refresh and request a license using Locking ID as usual from CLS for the OS-SBC)
The OS-SBC WAN Ethernet port (access side) must be assigned to an unused IP interface of the OS4K.
The OS-SBC Customer LAN IP (core side) used for Administration and internal SIP communication has to be from the same network as OS4K Customer LAN and the IP interface is internally assigned.
In case of Standalone EntGW where there is no Assistant, after RISO restore, the hSBC will have the default configuration inside. This is caused by the missing backup restore step of the RISO process, which creates also the BEER backup, which in turn holds the inside hSBC configuration. So before RISO restore, It necessary to manually save/export the hSBC xml configuration file.
By default „Message Rate Control” is disabled in OS-SBC. It is strongly recommended to keep it disabled, otherwise Circuit conference calls (ATC configured with local conference media server in OS SBC) will be dropped after 4-5 seconds. Moreover Rapid stat log download is influenced and OS-SBC restarts due to performance issue.
With V8R1 the OS-SBC will provide a new image (.bz2 file) via SWS OS-SBC releases especially created for Hosted OS-SBC OS4K installations.
UDP mode on Core side is not supported.
Following features are disabled by OS-SBC for Hosted OS-SBC Deployments
(please see OpenScape SBC Administrator Documentation):
Interface Bonding, Single armed, Active-Active, Active-Standby, SIP Load Balancer, Backup, Upgrade, Restart, Watchdog, Core realm (is not configurable), Redundancy, NTP, TURN Server, Ganglia Monitoring Daemon, THIG, Border Control Function (BCF).
The network interface configuration has a customized functionality for hosted environment in the OpenScape 4000 system.
Support of hosted SBC on Standalone SoftGate on OpenScape 4000 Branch/OpenScape EcoBranch is not supported due to technical software limitation of the Standalone SoftGate. It is however possible to install Survivable SoftGate deployment instead, which supports hosted SBC.
The hosted SBC supports a maximum of 120 channels, see below for details:
Deployment Scenario
OpenScape 4000 EcoServer/Branch
(Note 1)
Metric
Max. registered SIP Remote Users (Note 2), eg, home workers (without Digest Authentication, Throttling, or TLS)
120
Max. simultaneous SIP signaling calls / SBC sessions (Note 4)
120
Max. simultaneous RTP media streams (full-calls) anchored through OpenScape SBC (without Media Transcoding)
120
Max. simultaneous RTP media streams (full-calls) anchored through OpenScape SBC (with Media Transcoding)
60
Max. simultaneous SRTP secure media streams (either MIKEY0 or SDES) terminated/mediated by SBC (without Media Transcoding)
100
Number of simultaneous SIP Service Providers (SSP)
10
Busy Hour Call Attempts (full calls) (Note 9)
1800
Max. peak half-calls (Note 9) per second (without Digest Authentication, Throttling, or TLS)
1 (Note 10)
Registration refresh requests per second
1
(randomized registration steady state condition)
Steady state call completion rate
99.99%
Time to recover to steady state operation (99.99% call completion) following simultaneous restart of all endpoint devices (Note 11)
<15 min.
NOTES
1.
Network interface switch speed is set to 1 Gigabit Ethernet.
2.
For keysets, each keyset line appearance is counted as one registered user.
3.
Subscriber registration interval 3600 seconds. Add the following penalty (or penalties*) to get the actual registered SIP users limit. To get new numbers, apply penalty1 and on the new numbers apply penalty2.
•
Digest Authentication penalty: 25%
•
Throttling Penalty (600 seconds - reducing this value introduces more penalty): 60%
•
To determine cumulative penalties apply penalty1 and on the new number apply penalty2.
4.
An OpenScape SBC Session is defined as a SIP signaled call with an access-side signaling leg and a core-side signaling leg. A typical voice call between a local OpenScape Voice user and a Remote User registered via the OpenScape SBC, or to a SIP Trunk connected via the SBC requires one SBC session.
5.
A "half call" is a call from either Access side (WAN) to core-side (LAN) or from core-side (LAN) to access-side (WAN). A "full call" consists of two half call legs. i.e. a call being initiated by the Access side (WAN) going to core-side (LAN) and then coming back to the Access side (WAN).
6.
Apply the following penalty (or penalties*) to determine the actual OpenScape SBC maximum calls per second limit when the following functions are enabled:
•
Digest Authentication penalty: 30%
•
Throttling penalty** (600 seconds throttling interval): 40%
•
TLS penalty** (600 seconds keep alive interval; no throttling): 50%
* To determine cumulative penalties apply penalty1 and on the new number apply penalty2
7.
When restarting, SIP endpoint devices are required to comply with procedures specified in RFC3261 and OSCAR Chapter 11: Best Practices. With a simultaneous restart of all endpoint devices, when a user becomes successfully registered, that user shall immediately be able to originate and receive calls with a call completion rate of at least 99.99%.
OpenScape SBC/UTC (Universal Telephony Connector):
Deployment
Performance limit with G.711 (30% DTLS+ICE penalty compared to SRTP)
OpenScape 4000
~60 concurrent DTLS sessions
Please see
OpenScape 4000 Feature Description, Section Hosted SBC, Restrictions
for further information.
Platform Administration (Portal)
, ID:
P31003-H31A0-M101-03-76A9
Copyright ©
Unify Software and Solutions GmbH & Co. KG
07/2020
- All rights reserved.