session management in an enterprise comunication ... - Genband

SESSION MANAGEMENT IN AN ENTERPRISE COMUNICATION NETWORK
However, different than a basic SIP proxy or Gatekeeper, the
S3 SBC supports a multitude of enhanced routing and hunting
features that give network administrators superior control
of IP sessions. Some of those features include:
Many of these features offered by GENBAND are unique in
the industry. The S3 SBC is also used as a probe point to
generate SDRs containing session statistics such as session call
hold times and post dial delay times.
Routing Engine features:
• Port and Trunk Group level granularity for routing allows
the establishment of routing policies on an endpoint
basis down to the port level or Trunk Group level
• Flexible policy enforcement can be applied for both
incoming and outgoing calls
• GENBAND calling plans facilitate a large variety of routing
policies including time of day routing, route priority
by route or endpoint and route hunting
• Sophisticated call treatment of the called and calling
numbers enables applications such as permissive dialing
and adapt call requests to the unique requirements of
terminating gateways
• Support for over 2 million routes per system
• Comprehensive SDRs that capture over ninety (90) per
session performance statistics
Dynamic Call Hunting features
• On a failed egress call attempt, the next destination
endpoint to be selected is one which is the best of the
remaining set of endpoints which can route that call.
• Up to 16 route hunts or route advances can be set up on
the system.
• Call hunting is enabled globally for the system or on
a per source endpoint basis. The configuration on the
source endpoint overrides the global system setting.
• Call hunting is dynamically disabled whenever the destination
endpoint sends media in its Progress Message
indication.
• Both SIP and H.323 calls are subject to hunting. Whenever
the S3 SBC forwards media, hunting is disabled for
that call. Every route hunt generates a SDR. The SDRs
are linked by a common callid.
• The S3 SBC is compliant with the Internet Draft on SIP to
ISDN/Q.931 release cause mappings.
Finally, there is the application layer session manager known
as the GENView RSM. The RSM collects statistics from the
SBC(s), for example packet delays, jitter, lost packets, MOS
score, session call hold times, post dial delay times, and
malformed SIP message statistics. The RSM pulls these statistics
from SDRs and first reports them to the network operator to
help them manage their network. Second, the RSM analyzes
the data against metrics defined per subscriber, per session
and per application to determine if there are network problems,
for example MOS metrics drop below acceptable levels
or call duration drops below thresholds - both indicators that
there are session problems. Third, if problems are found, the
RSM immediately notifies an operator via email or page.
Finally, the GENView RSM will automatically correct problems
by generating new route paths and updating SBCs with the
new policy
information. This patent-pending feedback loop, known as the
Dynamic Policy Management (DPM), between the RSM and
the SBCs completes the session management solution; the RSM
capitalizes on the SBC session insight to dynamically control
sessions depending upon current network conditions.
GENiUS IMS VoLTE Solution
The GENBAND intelligent session management system complements
other IP-PBX offerings by addressing, for example,
multi-vendor issues, multi-protocol issues, QoS, security, and
reliability concerns. Figure 2 depicts a typical large distributed
IP-based enterprise communication network consisting
of IP-PBXs from multiple vendors, both TDM and IP gateways
to thes service provider and multiple IP- based applications
such as conferencing and unified messaging. Also included
are GENBAND session management components including a
standalone SBC, collocated SBC and a RSM:
5