You are on page 1of 12

OpenScape Voice V8

Start with the right platform.


The leading software-based voice communications system

OpenScape Voice is a native SIP-based OpenScape Voice is a carrier-grade en- a survivable branch office solution for
real-time Voice over IP system scalable terprise voice solution meaning OpenScape Voice. OpenScape Branch
up to 100,000 users per system and a 99.999% reliability – that translates to not only offers survivability, but it in-
virtually unlimited number of users less than 5 1/2 minutes of downtime cludes a media server, firewall, Session
when OpenScape Voice systems are per year! The server nodes are de- Border Controller, and integrated
networked. It runs on highly reliable, signed so that if one fails, the other PSTN gateway, all in a single appliance
redundant and fault-tolerant hard- server node is capable of supporting form factor. The value of OpenScape
ware. It provides a complete and fea- 100% of the call load. The server nodes Branch goes beyond survivability, its
ture-rich set of business class features can operate with 100% call failover activity contributes to lower the over-
and can be deployed on premise, in a support even when they are geograph- all deployment, bandwidth and service
data center (as a private cloud), or as a ically separated, greatly reducing the costs.
multi-tenant hosted/public cloud solu- costs, and the amount of time imple- OpenScape Voice can be deployed in a
tion. menting a disaster recovery strategy. virtualized architecture, and can be de-
And remote offices can be protected livered as a virtual appliance (vApp).
with an OpenScape Branch solution –

OpenScape UC Suite Data center

OpenScape OpenScape OpenScape OpenScape OpenScape OpenScape Media Common Deployment


Contact Center Video Mobility Xpressions Voice Server Management Service
UC Portal

OpenScape
Session Border
Controller Main office
Attendant OpenScape
OpenScape Console Mobility
Network SIP Branch
operation center Carrier

OpenScape OpenStage phones OpenScape


WAN Desktop Client Personal Edition

Remote user

Enterprise Edition
Softphone
PSTN
OpenScape OpenStage
Desktop Client phones
OpenScape
Branch 500i

Unified Communications Architecture Overview


Comprehensive Unified Public cloud / Hosted edition OpenScape Voice Duplex
OpenScape Voice is the cornerstone This deployment model illustrates how
Communications application for public cloud/hosted the OpenScape Voice can be operated
OpenScape Voice is always part of a so- edition solutions. It supports multi- as a more robust and scalable duplex
lution landscape. The most basic solu- tenancy (up to 6,000 business groups) system. It provides carrier-grade reli-
tion includes: allowing service providers to "build ability by running two platforms in a
• OpenScape Voice as a SIP-based their own cloud". redundant two-node cluster that exe-
Voice over IP software application cutes in an active-active mode. Should
• OpenScape Media Server for tones
Private cloud one of the nodes fail, then the remain-
ing partner node would assume the
and announcements For large enterprise customers (1,000
call load of the failed partner (and
• OpenScape Branch 500i for a to 100,000 users) with multi-site loca-
would handle 100% of the call traffic)
survivable trunk gateway tions that span over a region or the
and would continue to provide unin-
globe, OpenScape Voice can deploy as
• OpenScape Branch (50, 250, 500i, terrupted call processing. No calls
a private cloud solution. The key char-
1000, 6000) for survivable remote would be dropped due to the failover
acteristic of a private cloud is central-
offices from duplex to simplex operation, or
ized deployment of voice (and UC) ser-
• OpenScape Session Border when the system reestablishes duplex
vice from the customer's data center.
Controller operation. The duplex mode also al-
lows for the possibility of maintaining
• OpenStage SIP phones for IP end- Configurations call processing operation while an
points for user access OpenScape Voice upgrade is per-
• OpenScape Personal Edition for a OpenScape Voice Integrated formed.
soft client
Simplex Currently a mix of physical nodes and
• OpenScape Common Management virtual nodes is not supported. A clus-
• This configuration consists of a sys-
Platform (CMP) with OpenScape ter of 2 physical nodes or a cluster of 2
tem that provides the medium sized
User Management virtual nodes are the only scenarios
voice solution (with or without UC)
• OpenScape Deployment Service supported.
in a single server. The OpenScape
For advanced scenarios, Unified Com- Voice and UC applications are de- This model is appropriate for larger
munication applications are added. ployed as a single node platform; as customers (up to 100,000 users) as well
such there is no carrier-grade reli- as customers that want carrier-grade
reliability.
Deployment scenarios ability due to the lack of redundan-
cy. Additionally, the following de- • Multiple instances of the OpenScape
OpenScape Voice is designed to cover ployment highlights provide the Deployment Service may be de-
multiple customers and target market ability to run on the same physical ployed to scale with the number of
deployment scenarios. The key de- platform: users. Running the OpenScape De-
ployment scenarios are: ployment Service upon the same
• OpenScape Voice application
platform as the CMP is only recom-
OpenScape Exchange • OpenScape Voice Assistant
mended in very small deployments.
• OpenScape Media Server
OpenScape Exchange is an overlay so- • A multi-node configuration for
lution for multi-vendor networks, • Common Management Platform OpenScape Deployment Service is
where there is TDM legacy, or con- (CMP) also supported. This allows an in-
verged IP systems. It allows for central- • OpenScape Deployment Service stallation of two to four OpenScape
ized deployment of Unified • OpenScape UC Deployment Service servers to ap-
Communications services. In the over- pear as a single computer to clients.
lay deployment, OpenScape Voice acts This model represents an offering that
would be of interest to a customer that • The OpenScape Media Server scales
as a SIP-based central routing and ad- (up to as many as 3,000) to meet the
ministration solution for multi-site, wants a medium size VoIP business so-
lution (up to 5,000 users) at a low cost, increased media service needs of
multi-vendor networks, allowing cus- large/increasing numbers of sub-
tomers a "migrate at your own pace" and therefore is willing to accept some
risk of downtime (due to no redundan- scribers. One instance of the
solution. OpenScape Media Server may reside
cy). This is also a configuration that is
prevalent in the "try-and-buy" pro- upon the CMP platform; multiple in-
gram. stances are also possible for redun-
dancy, scalability and optimized
bandwidth utilization reasons.
• A single Common Management
Platform is used to support the en-
tire solution.
OpenScape Voice virtualized Application and server Hardware redundancy and
architecture platform cluster connectivity
The most important features provided OpenScape Voice controls and super-
by virtualization are the reduced num- At the heart of the OpenScape Unified vises call setup; the actual media pay-
ber of servers and the capability of our Communications is the OpenScape load (voice and/or video) is carried
solution to be hardware-agnostic. Voice real-time, SIP-based, Voice over over the LAN/WAN between end-
IP application that provides the carri- points. The administration, call con-
Therefore, OpenScape UC Suite opera-
er-grade level of redundancy, reliabili- trol, and billing traffic are carried over
tion in a virtual environment enables
ty and scalability required for mission- redundant pairs of network interface
the following capabilities:
critical deployments. OpenScape Voice cards through redundant, intercon-
operates on commercial servers over nected L2/L3 switches that provide re-
Server consolidation
QoS managed networks. dundant networking.
The applications and virtual machines
The OpenScape Voice VoIP system pro- The OpenScape Voice redundant con-
deployed onto a VMware host can use
vides the following key features: figuration can be deployed as follows:
different guest operating systems, i. e.
OpenScape Voice (Linux) and • SIP proxy (supplied by external • Co-located cluster nodes
OpenScape Concierge (Windows) can equipment)
• Geographically separated with the
both be deployed onto the same VM- • Enterprise telephony features cluster nodes in the same VLANs/
ware host and share its physical re- • User management and address subnets with the interconnect link
sources. translation functions served by a layer-2 connection
Hardware independence • Interface to monitor and control • Geographically separated with the
media transactions including pure cluster nodes in different VLANs/
Having many hardware server vendors
telephony subnets with the interconnect link
and models in a data center environ-
• Interface for advanced services, served by a layer-2 connection
ment adds complexity and cost to the
operation, therefore customers often such as presence services, billing • Geographically separated with the
look to standardize their IT hardware services, collaboration services, etc. cluster nodes where the intercon-
infrastructure. Virtualization allows • Gateway selection and hunting nect link is a layer-3 connection
customers to deploy applications onto • Routing and translation functions
any hardware platform, assuming it comparable to a carrier-grade
has been certified by VMware and it solution
meets the resource requirements of
OpenScape Voice is designed as an
the application, as described in this
open standards platform that runs on
document.
standard rack-mountable commuting
hardware.
The base system software runs on the
SUSE Linux Enterprise Server operat-
ing system – SLES11 64 bit. This is com-
bined with cluster control software to
run all parts of the system as a redun-
dant unit. The system runs on a single
server or a dual server cluster, depend-
ing on the number of users and cus-
tomer requirements.
Security SRTP requires a secure signaling con-
nection to be used between the media
Security: IPSec
OpenScape Voice supports SRTP for OpenScape Voice supports optional
device and the OpenScape Voice serv-
media encryption. SRTP secures voice use of IPSec for protecting the
er. For SIP devices, TLS is used, and for
communication by encrypting the me- OpenScape Voice SOAP and SNMP
the OpenScape Media Server, IPSec is
dia packets between media devices management interfaces to the external
used to secure the signaling connec-
that support SRTP. OpenScape Voice Assistant and CMP,
tion.
as well as for protecting the MGCP sig-
End-to-end media encryption is imple- All Session Border Controllers (SBCs) naling interface to a media server.
mented using a "best effort" mecha- that are approved for use with
nism that is dependent on SRTP sup- OpenScape Voice V8 support SRTP me-
port from the media devices that are
Security: Event logging
dia encryption using transparent me-
involved in the connection. An en- dia relay, or "pass-through". In addi- Security event logging can be provided
crypted SRTP connection is estab- tion, OpenScape SBC (V2 and later) can using the standard Syslog mechanisms
lished when both media endpoints support SRTP termination of MIKEY0 for both platform and application or
support SRTP and use a common key and SDES key management, which al- optionally be using the Linux Audit OS
management protocol (e. g., MIKEY0 lows for SRTP to RTP termination and module.
or SDES); if an SRTP connection cannot also SRTP mediation between MIKEY0
be established, the call will still be and SDES key exchange methods for OpenScape Software
completed but with an unencrypted media connections routed via the SBC.
RTP. This interworking is useful, for exam- Assurance
SRTP MIKEY (Profile 0) is supported on ple, to maintain maximum media OpenScape Software Assurance as-
connections between nearly all media stream security within the enterprise sures that customers are kept on the
endpoints of the OpenScape Unified network when using SIP trunks to a latest software version of OpenScape
Communications. service provider that does not support products. Continuous software up-
SRTP, or to ensure security for remote grades guarantee long-term software
With OpenScape Voice V8, SRTP SDES
subscribers (e. g., home workers) that stability, up-to-date security features,
(Profile 1) is supported on connections
access OpenScape Voice via an un- and improve the OpenScape Unified
between nearly all media endpoints of
secure network. Communication interfaces towards
the OpenScape Unified
Communications solution, and is the other products and solutions.
preferred SRTP key management pro- Security: TLS
tocol to use. OpenScape Voice provides Transport Upgrade/conversion to
Layer Security (TLS) for protecting sig-
OpenScape Voice also supports media
encryption for connections that are naling communications on SIP end- OpenScape Voice V8
signaled over the SIP-Q interface point, SIP server, and SIP-Q server in- Upgrades require an upgrade license
between itself and: terfaces. per user license purchased in the pre-
• Another OpenScape Voice system OpenScape Voice also supports optio- vious release.
nal use of TLS to secure the transport The currently available migration de-
• HiPath 4000 V6 and later
of XML messages on the SOAP server ployment options are:
• HiPath 3000 V9 and later management interface. This feature
• IBM x3550 M4 server
Solution media devices that do not also provides for client user authenti-
support SRTP or do not support a com- cation and role-based authorization • Fujitsu RX200 S7
patible key management protocol for controlling access to OpenScape • Virtualized environment on VM-
should negotiate down to RTP. Voice management functions. ware ESXi V5/ V5.5
OpenScape Voice supports enhanced The system's static capacity for TLS is Current IBM X346 simplex or duplex
SDP backward compatibility for best 50,000 endpoints. Dynamic capacity customers who wish to upgrade to
effort SRTP that allows for support of depends on customer feature configu- OpenScape Voice V8 software will be
third-party SIP endpoints that do not ration and call rate. required to change out their platform
support SRTP and do not properly han- to a supported IBM or Fujitsu server:
dle SRTP to RTP fallback which might • IBM x3550 M4
otherwise have resulted in call failures.
• Fujitsu RX200 S7
Management
Network element management pro- • Perform image installations and up- OpenScape Voice and all supported
vides the capability to operation, ad- grades on OpenScape Voice and its features and applications.
ministration, maintenance and provi- applications
sioning (OAM&P) tasks. OAM&P tasks • Implement rolling upgrades on Mass Provisioning
are performed by deploying user-ori- OpenScape Voice Mass Provisioning provides the follow-
ented application components that
• Implement split-mode upgrades on ing:
provide the capability to:
OpenScape Voice and its applica- • Expert-mode CLI commands to pop-
• Perform service management provi- tions ulate and configure the OpenScape
sioning through the Command Line
• Backup and restore the system Voice databases
Interface (CLI) and OpenScape Voice
Assistant The Common Management Platform, • SOAP mass provisioning commands
the OpenScape Voice Assistant and the to simplify the creation of large
• Perform mass provisioning
CLI provide the element management numbers of subscribers
• Generate call detail records (CDRs) interfaces. Additionally, external ap-
plications can provide the interface to
perform network management for

Network connectivity
Supported gateways
Number of users PSTN interface Without With survivability Other options
(up to estimated) survivability
8 Analog (4 x FXO) OSB 50i – A84 OSB 50i – A84 Mediatrix 12041
8 Two BRIs (2 x S0) Mediatrix 4402 #, OSB 50i – D44 Mediatrix 44021
OSB 50i – D44
25 Analog (8 x FXO) OSB 50i – A84 OSB 50i – A84 2 x Mediatrix 12041
25 Four BRI (2 x S0) OSB 50i – D44 OSB 50i – D44 Mediatrix 44041
50 Single PRI (1 x E1/T1) Mediatrix 3631 #, OSB 50i – DP14 E/T RG8350a1, HiPath 40001,
OSB 50i – DP14 E/T Mediatrix 36311
100 Two PRIs (2 x E1/T1) OSB 500i DP2 OSB 500i DP2 RG8350a1, HiPath 40001,
Mediatrix 36321
250 Three PRIs (3 x E1/T1) OSB 500i DP4 OSB 500i DP4 RG8350a1, HiPath 40001 or
Mediatrix 36321
500 Four PRIs (4 x E1/T1) OSB 500i DP4 OSB 500i DP4 RG 8350a1 or HiPath 40001
1000 Eight PRIs (8 x E1/T1) OSB 500i DP8 OSB 500i DP81 RG 8350a1 or HiPath 40001
2000 Sixteen PRIs (16 x E1/T1) 2 x OSB 500i DP8 2 x OSB 500i DP81 RG 8350a1 or HiPath 40001
1 One additional OSB unit is needed to provide survivability to all users.

SIP Private Networking SIP trunking to service These enterprises realize a solid return
on investment (ROI) by lowering ad-
SIP Private Networking replaces the providers ministrative costs and the costs associ-
SIP-Q protocol currently used for Many enterprises are already using ated with calls made within the com-
OpenScape Voice-to-OpenScape Voice VoIP; however, many use it only for pany. With SIP trunking, however, the
connections. This eliminates the need communication on the enterprise LAN. potential for ROI is far greater because
to convert between SIP and SIP-Q pro- In this scenario, VoIP is used as a one- SIP trunking takes the VoIP concept
tocol for a station-to-station call be- to-one replacement for traditional beyond this LAN application. The full
tween two OpenScape Voice systems. wireline telephony. For all calls made to potential for IP communications can
SIP Private Networking is sometimes the outside of the LAN, a PSTN gateway be realized only when the communica-
also referred to as Enterprise SIP on the enterprise edge is required. tion is taken outside of the corporate
Trunking or Enterprise SIP Peering.
LAN.
Call Admission Control features all access links that exist between the QSIG tunneling features
two communicating endpoints. The
The integrated Call Admission Control QSIG tunneling features support SIP-Q,
following are examples of the func-
(CAC) features provide for manage- which permits OpenScape Voice to in-
tionality the call admission control fea-
ment of the bandwidth used for the terwork with another OpenScape
ture provides:
transport of media traffic (such as RTP Voice system, the HiPath 4000, the
audio, T.38 fax, and video) through the • CAC rerouting to SIP subscribers or HiPath 3000, or a QSIG PBX connected
bottleneck links that may exist in an alternate SIP gateways via the RG 8700 gateway.
enterprise network. This feature en- • Call denial
sures that real-time media calls are • Dynamic handling of link failures
only established when the necessary
bandwidth resources are available on

Features
Keyset telephony user features • Station call forwarding – time-of- • Feature status notification
Keyset telephone user features pro- day • Intercom Calls
vide multiple line capability, and other • Station call forwarding – fixed • Last incoming number redial (LINR)
associated functions, for a SIP end- • Station call forwarding – remote call • Last outgoing number redial (LONR)
point configured as a keyset. Keysets forwarding
are sometimes known as multiline • Multiple contacts
• Station call forwarding – voice mail
telephones. • Music on hold
• System call forwarding, internal/
Any of the following OpenStage 40/60 • One Number Service
external – all calls (CFSIE-all)
phones can be configured as keysets. • One-Way Paging Broadcast
• System call forwarding, internal/
• Audible ringing on rollover lines • OS Mobility
external – busy (CFSIE-busy)
• Delayed ringing • Screening list editing
• System call forwarding, internal/ex-
• Direct station select ternal – do not disturb (CFSIE-DND) • Selective call acceptance
• Line focus preview • System call forwarding, internal/ • Selective call forwarding
• Line key operation modes external – don't answer (CFSIE-DA) • Selective call rejection
• Line reservation manual hold • Serial ringing
Other user features
• Multiline appearance • Simultaneous ringing
Other OpenScape Voice user features
• Multiline origination and transfer provide such capabilities as calling • Station dialing
• Multiline preference keyset opera- identity delivery and suppression, ab- • Station speed calling
tion modes breviated dialing, redial, and call re-
• System speed calling
• Phantom lines turn features. The following are the
other user features provided by • Toll and call restrictions
• Visual indicators for line and feature
OpenScape Voice: • Transfer
key status
• Anonymous call rejection • Transfer security
• Privacy
• Call completion on busy subscriber/ • Virtual DN
OpenScape Voice-based call no reply (CCBS/NR)
forwarding user features • Call pickup-directed
OpenScape Voice-based call forward- • Caller identity service
ing user features provide a means to
• Calling identity delivery and sup-
customize the handling of calls when a
pression (CIDS)
subscriber is unavailable to answer
them. The following are the • Calling name delivery (CNAM)
OpenScape Voice-based call forward- • Calling name delivery blocking
ing user features: (CNAB)
• Call forwarding – return • Calling number delivery (CND)
• Call forwarding – unreachable • Calling number delivery blocking
• Station call forwarding – all calls (CNDB)
• Station call forwarding – busy line • Click to answer
(CFBL) • Conference, station-controlled
• Station call forwarding – don't an- • Customer-originated trace
swer (CFDA) • Deployment service mobility
• Station call forwarding – remote • Do not disturb (DND)
activation
• Executive override
Business group features Routing and translation features Security features
The business group concept provides Routing and translation features pro- Security features provide security for
the basic capabilities for handling a vide such capabilities as public num- various aspects of the system, such as
group of subscribers associated with a bering plan compliance and routing billing records, data files, and adminis-
single enterprise. It also permits that varies depending upon such fac- tration interfaces. The following are
OpenScape Voice to recognize the as- tors as origin, traffic, and time of day. the security features:
sociations of the subscribers the group The following are the routing and • Account and password management
contains. Business group features sim- translation features: security
plify such tasks as dialing plan admin- • A-side signaling-based routing • Billing records security
istration, intra-group communication,
• Alternate routing • Data file security
and traffic measurements. The follow-
ing are the business group features: • Alternate routing with overflow • Defending denial of service attacks
among route types
• Attendant answering position (AAP) • Event logging
• Call diversion for invalid destina-
• Business group access codes • File transfer security
tions
• Business group account codes • Hypertext transfer protocol over
• Cost-effective routing
• Business group authorization codes SSL
• Digit modification for digit outpuls-
• Business group billing • IPsec baseline
ing
• Business group department names • Login categories
• E.164 compliance
• Business group main number • Media stream security
• Intercept treatment
• Business group numbering plan • OpenScape Voice Assistant security
• International translation support
• Business group traffic measure- • Provisioning and security logging
• Leading digit and most-matched
ments digit translation • Secure CLI
• Business group web portal • Media server digit map manage- • Secure Shell on the OpenScape
• Direct inward dialing (DID) ment Voice Assistant interface
• Direct outward dialing (DOD) • North American Numbering Plan • Secure storage of CDR password
• Distinctive ringing compliance • SIP privacy mechanism
• Extension dialing • Numbering plans, business group • TLS support – network connections
• Group-level feature administration • Origin-dependent routing • TLS support – subscriber access
• Message detail recording • Rerouting based on SIP response • Virus protection
codes and WAN outages • VLAN provisioning
• Night bell call pickup
• Source-based IP routing
• Station restrictions
• Subscriber routing options ENUM
Other group features (electronic number mapping)
Other group features pertain to pickup • Time-of-day routing
groups, which allows users to answer • Vertical service codes
calls on behalf of one another; hunt • Voice VPN
groups, which permit calls to be routed
to an idle line within a group of speci- CDR features
fied lines. The following are the other
CDR features simplify call tracking and
group features:
billing for OpenScape Voice.
• Call pickup – group
The following are the CDR features:
• Feature profiles
• Call detail record generation
• Hunt group
• Intermediate long duration records
• Hunt group – make busy
• Message detail recording
• Hunt group – music on hold
• Usage reporting
• Hunt group – night service
• Hunt group – no answer advance
• Hunt group – overflow
• Hunt group – queuing
• Hunt group – stop hunt
• Hunt group – traffic measurements
• Uniform call distribution (UCD)
Serviceability features SIP signaling features CSTA support features
These features provide mechanisms to These features support SIP signaling OpenScape Voice provides a standard
improve serviceability, such as diag- and the interworking with other ele- European Computer Manufacturers'
nostics and debug tools, code controls, ments such as application servers, Association (ECMA) Computer Sup-
and administrator controls. The fol- voice conferencing applications, and ported Telecommunications Applica-
lowing are the serviceability features: voice mail systems. The following are tions (CSTA) protocol interface to ex-
• Administrator identification and au- the SIP signaling features: ternal CTI applications. The following
thentication • Application-provided billing party are examples of the functionality the
CSTA support features provide:
• Backup and restore • Application-provided call correla-
tion • CSTA services support
• Basic traffic tool
• HTTP digest authentication • Application-provided caller identifi-
• Call trace
cation
• Continuous trace • Integration with OpenScape call
ticket • Flexible digit processing
• Database versioning
• Integration with Microsoft • Integration with Fault Management
• Log file retrieval tool
Exchange 12 unified messaging • Message waiting indicator
• Maintenance manager server • One Number Service
• Mass provisioning • Integration with • OpenScape Voice-provided calling
• On-demand audits OpenScape ComAssistant name
• Process debug tool • Integration with • Private network number support
• Query of subscriber transient OpenScape Contact Center System functions and features
operational status • Integration with These features support such tasks as
• RapidStat OpenScape Xpressions alarm reporting, message waiting indi-
• Real-time trace • Integration with OpenScape cator control, and recovery handling.
• Integration with OpenScape UC Ap- The following are the system functions
• Remote patching and features:
plication
• Remote restart • Agent for OAM&P
• Integration with OpenScape Voice-
• Software installation Link • Alarm reporting
• System software and • Interworking with Microsoft OCS • Announcements
patch level status mediation server • Data synchronization
• System upgrade • Interworking with RG 8700 • Display number modification
• Interworking with SIP service pro- • Emergency calling
viders
• Feature execution for unreachable
• Interworking with unified messag- subscribers
ing systems
• Internal audits
• Interworking with voice mail sys-
• Interworking with automated atten-
tems
dant systems
• SIP over TCP/TLS support
• Local management
• SIP privacy mechanism
• T.38 fax support
• SIP REFER method support
• Media server support
• SIP session timing
• Message waiting indicator
• SIP UA registration renewal during
• Multiple language announcements
WAN outage
• Multiple time zone support
• Interworking with application serv-
ers • Overload handling
• Recovery handling
• SDP transparency
• Silence suppression disabling
• SOAP interface
• System history log
System capacities
Parameter1 OpenScape Voice OpenScape Voice
Standard Duplex Integrated Simplex
TCP Connections 327681 5000
TLS sockets 50000 5000
Unique keyset DNs 100000 5000
Average keyset line appearances 2 2
Maximum simultaneous line appearances on a keyset phone 10 10
Business Groups 6000 600
Numbering Plans 5999 600
Total trunks (SIP and SIP-Q) Standard PBX 2 60000 5000
Total trunks (SIP and SIP-Q) Tandem 2 60000 5000
Total SIP-Q trunks 2 20000 5000
Prefix Access Codes 35000 18000
Destination Code table entries 200000 10000
Destinations (two routes per destination average) 54000 27000
Route Lists 54000 27000
Routing Areas 30000 15000
Classes of Service 30000 15000
Number of Hunt Groups 25000 1250
Hunt Group size 2048 200
Hunt Group memberships per subscriber 32 32
Number of Pickup Groups 10000 1000
Pickup Group size 64 64
Pickup Group memberships per subscriber 1 1
Maximum Station Controlled Conference participants 16 16
Feature Profile per subscriber 1 1
Simultaneous SIP-Q calls half calls (max.) 20000 5000
Simultaneous SIP-Q calls tandem (max.) 10000 5000
Simultaneous SIP-Q calls (SIP + SIP-Q) 60000 5000
1 Some of the numbers are extrapolated from Standard installation
2 Recommended limits, not enforced
Supported RFCs
Supported SIP-related RFCs Supported SDP-related RFCs
• RFC 3261 – SIP • RFC 2327 – SDP
• RFC 2976 – SIP INFO method (e. g. for • RFC 3266 – Support for IPv6
SIP-Q • RFC 3605 – RTCP attribute in SDP
• RFC 3262 – PRACK method, 100rel • RFC 3890 – Transport-independent
• RFC 3263 – Server location bandwidth modifier
• RFC 3264 – Offer-answer model for • RFC 4091 – Alternative Network Ad-
SDP dress Types (ANAT)
• RFC 3265 – SUBSCRIBE/NOTIFY • RFC 4566 – SDP-new
method, Events • RFC 4567 – Key management exten-
• RFC 3311 – UPDATE method sions
• RFC 3323 – Privacy header field • RFC 4568 – Security descriptions
• RFC 3325 – P-asserted identity head- (SDescriptions)
er field
Supported event-package RFCs
• RFC 3326 – Reason header field
• RFC 3842 – Message waiting indica-
• RFC 3515 – SIP REFER method tion
• RFC 3891 – Replaces header field • RFC 4235 – INVITE-initiated dialog
• RFC 3892 – Referred-by header field event package
• RFC 3903 – PUBLISH method • RFC 4575 – Conference event pack-
• RFC 3911 – Join header field age
• RFC 4028 – SIP session timers • RFC 6035 – RTCP summary event
package
• RFC 4092 – ANAT in SIP
• RFC 5630 – SIP-SIPS
• RFC 5806 – Diversion header field
• RFC 5876 – Updates to Asserted
Identity
• RFC 5923 – Connection reuse
• RFC 5954 – Essential correction for
IPv6 ABNF and URI comparison
rules
• RFC 6086 – SIP INFO packages
Copyright © Unify GmbH & Co. KG 07/2014
Hofmannstr. 51, 81379 Munich/Germany
All rights reserved.
Reference No.: A31002-H8070-D100-5-7629
The information provided in this document contains merely general descriptions or
characteristics of performance which in case of actual use do not always apply as
described or which may change as a result of further development of the products. An
obligation to provide the respective characteristics shall only exist if expressly agreed
in the terms of contract.
Availability and technical specifications are subject to change without notice.
Unify, OpenScape, OpenStage and HiPath are registered trademarks of
Unify GmbH & Co. KG. All other company, brand, product and service names are
trademarks or registered trademarks of their respective holders.

unify.com