session management in an enterprise comunication ... - Genband

SESSION MANAGEMENT IN AN ENTERPRISE COMUNICATION NETWORK
Operation Expenditure Benefits:
• Enables lower carrier access and feature rates
• Network-wide least cost routing reduces telephony
expenses
• Provides evidence for SLAs with service provider (loss
recovery)
• Reduces labor required to support configuration and
maintenance of dial plans across PBXs
• Reduces cost of SDR collection/aggregation
• Enables carrier bypass through enterprise-to-enterprise
VoIP peering
Capital Expenditure Benefits:
• Leverages existing investments through protocol and
vendor interworking
• Avoids over-provisioning to ensure network supports realtime
data
As previously discussed, GENBAND’s intelligent session management
system complements IP-PBX offerings and delivers
significant customer benefits that are unique in the industry.
Session management differentiates an enterprise bid from
competitive bids.
GENView Real-Time Session Management (RSM)
The GENView RSM complements the GENBAND S3 SBC by
providing automatic feedback of network behavior, SLA or
threshold checking and the dynamic adjustment of session
devices and interconnects. The feedback provides enterprises
with a highly predictive, scalable service architecture for session
based applications. In addition, the RSM is designed to
provide the network administrators with a single point from
which they control and assess the performance of sessions
traversing the GENBAND SBC.
RSM Architecture
The RSM runs on a standards-based Intel hardware platform
hosting a carrier-grade Linux-based operating system. The
GENView RSM architecture is illustrated in Figure 3. The RSM
and SBC run on separate hardware platforms.
An RSM Agent component runs on the SBC platform, which
provides the required information and interface to the RSM.
The RSM Agent implements several logical modules including
Figure 3 - Architecture illustrates the interaction between the GENBAND
Real-time SessionManager (RSM) and the S-Series SBC
the SDR server, J server Interface and logPP in the SBC. The
SDR server reads the SDRS files created by the SBC and
delivers them to the RSM server using standard HTTP or
HTTPS. The delivery of SDRs is via POST mechanisms with
up to 2500 SDRs per second supported. Optionally, the SBC
can be configured to stream SDRs to third-party databases.
Similarly, log files gathered at the SBC may be forwarded
to the RSM server using logPP agent component, for further
analysis. This enables service operators to react to alarms
and events indicating threshold crossings in either the session
performance or health of the session elements. The RSM may
be set up to dynamically update route tables at the SBC when
reacting to session status and health.
The RSM is supported by a web-based RSM client. Additionally,
the RSM web-services API provides northbound interface
for programmatic flow-through provisioning. Service operators
and NOC personnel can use their browsers to remotely
manage the GENBAND entities or integrate with existing
management tools via the web services API.
The GENBAND RSM supports these session management
tasks:
• Policy and route management for Call Admission Control
(CAC)
• Quality of Service and Service Level Management
• Service visibility and performance records
7