Oracle E-CZ 7.2.0 Session Border Controller User Guide
Reklamë
Reklamë
Oracle® Enterprise Session Border
Controller
Web GUI User Guide
Release E-CZ7.2.0
Formerly Net-Net Enterprise Session Director
September 2015
Notices
Copyright
©
2014, 2014, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are
"commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.
Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the
AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices.
UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of thirdparty content, products, or services.
Contents
1 Overview......................................................................................... 9
2 Configuration.................................................................................23
Dynamic Access Control List (ACL) Settings for the HTTP Application Layer Gateway (ALG)...... 111
Oracle
®
Enterprise Session Border Controller 3
3 Time Division Multiplexing (TDM)................................................ 119
4 High Availability (HA).................................................................. 127
5 Monitor and Trace Tab................................................................. 139
6 System Tab.................................................................................. 163
4 Oracle
®
Enterprise Session Border Controller
7 Format of Exported Text Files...................................................... 169
Oracle
®
Enterprise Session Border Controller 5
6 Oracle
®
Enterprise Session Border Controller
ECZ720-WGG-About This Guide
This guide provides information about configuring and administering the Oracle Enterprise Session Border Controller from the Web GUI. The topics in this guide contain conceptual, procedural, and reference information.
Documentation Set
The following table describes the documents included in the Oracle Enterprise Session Border Controller E-CZ7.2.0
documentation set.
Document Name
ACLI Configuration Guide
Acme Packet 1100 Hardware
Installation Guide
Web GUI Users Guide
Release Notes
Document Description
Contains information about the installation, configuration, and administration of the Oracle Enterprise Session Border Controller.
Contains information related to the hardware components, features, installation, start-up, operation, and maintenance of the Acme Packet 1100.
Contains information about using the tools and features of the Oracle Enterprise
Session Border Controller Web GUI.
Contains information about this release, including platform support, new features, caveats, known issues, and limitations.
Related Documentation
Document Name
Acme Packet 4500 Hardware
Installation Guide
Document Description
Contains information about the components and installation of the AP4500.
Contains information about the components and installation of the AP 3800.
Acme Packet 3820 Hardware
Installation Guide
Acme Packet 6300 Hardware
Installation Guide
Acme Packet 6100 Hardware
Installation Guide
Release Notes
Contains information about the components and installation of the AP 6300.
Contains information about the components and installation of the AP 6100.
ACLI Configuration Guide
ACLI Reference Guide
Maintenance and
Troubleshooting Guide
MIB Reference Guide
Contains information about the current documentation set release, including new features and management changes.
Contains information about the administration and software configuration of the
Oracle Enterprise Session Border Controller.
Contains explanations of how to use the ACLI, as an alphabetical listings and descriptions of all ACLI commands and configuration parameters.
Contains information about Oracle Enterprise Session Border Controller logs, performance announcements, system management, inventory management, upgrades, working with configurations, and managing backups and archives.
Contains information about Management Information Base (MIBs), Acme
Packet’s enterprise MIBs, general trap information, including specific details about standard traps and enterprise traps, Simple Network Management Protocol
(SNMP) GET query information (including standard and enterprise SNMP GET
Oracle
®
Enterprise Session Border Controller 7
ECZ720-WGG-About This Guide
Document Name
Accounting Guide
HDR Resource Guide
Administrative Security
Essentials
Security Guide
Document Description
query names, object identifier names and numbers, and descriptions), examples of scalar and table objects.
Contains information about the Oracle Enterprise Session Border Controller’s accounting support, including details about RADIUS accounting.
Contains information about the Oracle Enterprise Session Border Controller’s
Historical Data Recording (HDR) feature. This guide includes HDR configuration and system-wide statistical information.
Contains information about the Oracle Enterprise Session Border Controller’s support for its Administrative Security license.
Contains information about security considerations and best practices from a network and application security perspective for the Oracle Enterprise Session
Border Controller family of products.
Revision History
Date
September 2014
March 2015
Revision
1.00
1.01
May 2015
July 2015
September 2015
1.02
1.03
1.04
Description
• Initial Release
• Removes reference to
SMT's ability to trace
LDAP traffic.
• Removes KPML from the
Events section of the table in the "Subscriptions
Report" section.
• Removes KPML from the
"Notable Events Report" section.
• Adds the "Internet Protocol
Version Support" section.
• Adds the note about HA pair behavior to the "Time
Division Multiplexing" topic.
• Replaces the "HA on
VLAN" topic with "HA on the AP1100" topic.
• Updates "Home Tab" topic to clarify that the default widgets are also subject to the SIP configuration requirement for all other dashboard widget displays.
8 Oracle
®
Enterprise Session Border Controller
1
Overview
Getting Started
Oracle
®
recommends that you review the topics in this section before working with the system to ensure successful use of the tools and functions provided.
Browser Support
You can use the following Web browsers to access the Oracle Enterprise Session Border Controller (E-SBC) Web
GUI:
• Internet Explorer versions 9.0 and higher
• Mozilla Firefox versions 12.0 and higher
• Google Chrome versions 19.0.1084.46m and higher
Note: After upgrading the software, clear the browser cache before using the E-SBC Web GUI.
Internet Protocol Version Support
The Web GUI supports only IPv4.
Log On and Log Off
This section provides the concepts and procedures for logging on to and logging off from the Web GUI.
User and Administrator Access
You can logon to the Web GUI using your Web browser. There are two types of user logons:
• User - Allows viewing (read-only) access to the Web GUI.
• Administrator - Allows Superuser access to the Web GUI.
For specific rules that apply to the User and Administrator when using the Web GUI tabs, see the respective topics.
Simultaneous Logons
The Web GUI allows simultaneous logons for both the User and Administrator. Session availability to the User and
Admin depends on which type of user is logged onto the session. The following illustration shows a scenario of a
User and an Administrator logged onto a Web GUI session.
Oracle
®
Enterprise Session Border Controller 9
Overview
10
Up to five users can log onto the same session at the same IP address at the same time. Only one Administrator at a time can have full control of a simultaneous session. If more than five users attempt to log on, the system displays the following error message:
User limit reached. Please try again later.
Radius Server in the Network
The Web GUI supports authentication functionality similar to a user logging on by way of TELNET, Secure Shell
(SSH), and SSH File Transfer Protocol (SFTP).
The Web GUI supports RADIUS authentication. The following table describes the functions available to the
Administrator and User levels.
If
RADIUS server is configured as userclass=admin
RADIUS server is configured as userclass=user
Then
Administrator has full access to all features and functions after logging onto the GUI.
User has the following limited acess to the features and functions after logging onto the
GUI:
Full access to all SIP Monitor and Trace features and functions
Can download the following files in System File Management:
• Backup configuration
• Configuration CSV
• Local subscriber table (LST)
• Log
• Software image
• SPL Plug-in (SPL)
Note: A user with User privilege cannot upload files in System File
Management.
Log On to the Web GUI
The default username for the User level is “user” and the default password is acme. The default username for an
Administrator level is admin, and the default password is packet. If you changed a default password, use that one to log on. For more information about setting passwords, see the Oracle Enterprise Session Border Controller ACLI
Oracle
®
Enterprise Session Border Controller
Overview
Configuration Guide. To change passwords, use the secret command from the ACLI to change the login password for
user and the config password for admin.
To logon to the Web GUI:
1. On a PC, open an Internet Browser.
2. Start the GUI with either the HTTP or HTTPS logon.
http://<Server IP address> https://<Server IP address>
Note: Whether you log on using HTTP or HTTPS depends on the settings for your deployment. Contact your system Administrator for more information.
3. Enter your Web GUI username and password.
4. Click Login.
Log Off the Web GUI
To log off from the Web GUI, click Logout from the <logged-on-username> menu in the upper right corner of the
Web GUI. In the following illustration, Admin is the name of the user who is logged on.
The system logs you off and displays the log on page.
Web GUI Tools
The Web GUI provides tools that apply to the entire GUI and to specific functions within each tab. For example,
"Customizing the Page Display" applies to all pages and "Add widget" applies only to the Home page. Some tools are activated by icons and some are activated by links. The display of icons and links can depend on whether the system displays Expert mode or Basic mode.
About this Product
To view information about this product, select About from the Help menu.
Procedure
1. From the Web GUI, click Help > About.
2. Scroll to view the following information:
• Platform type
• Software version number
• Legal notices
• Copyright information
• Open Source Mailing Address
• Trademark recognition
• Licensing information
Search
From the Web GUI, you can search for a system object with the Search button located on the toolbar and you can search by the attributes of a system object with the Search field located on the page for a system object.
Oracle
®
Enterprise Session Border Controller 11
Overview
On the toolbar, click the Search button and the system displays the system objects in a drop down list. You can select an object from the list or type the object name in the text box. The system displays the search results in a list, where the object name is a link. Click the link to navigate to the object page.
On a system object page, enter an attribute or value for the object in the Search field and click Search. The system displays the results on the system object page.
Note: The system does not support searching or sorting on lists and sub-objects from the Search field on a system object page.
• For example, the realm-config system object page displays a list of Network Interfaces. You cannot search for one of the network interfaces on the list.
• For example, the realm-config system object displays the sub-objects "In realm", In network", and "Same ip" under the "Mm" object. You cannot search for the sub-objects.
Help
The logged on user button on the Web GUI displays the following information:
• Screen Help. Short descriptions of elements on the page.
• Help Topics. Online Help system containing topics about the tasks that you can perform on the Web GUI.
• About. Oracle notices and disclaimers, Oracle terms and restrictions, and third-party notices.
Tabs
The Web GUI displays tabs that you click to display information and where you can perform tasks.
The following table describes the behavior of each Web GUI tab in Basic Mode and in Expert Mode.
Basic Mode
Home Tab Configuration
Tab
Monitor and
Trace Tab
Widgets Tab
The Home tab displays the Web
GUI Dashboard, where SIP statistics are displayed on configurable widgets. On the
Home tab, you can:
• Add a widget
• Specify the widget sampling parameters
• Reset the display to the default
• Refresh the data displaying in the widgets
In Basic Mode the
Configuration tab displays a workspace where you drag and drop icons to configure the border controller in the network.
The toolbar on the
Configuration
Tab contains the following buttons that display task controls:
• Settings.
Configure system settings.
• Network.
Configure the Host
Route and
The Monitor and
Trace tab displays data that the system collects about:
• Sessions
• Registrations
• Subscriptions
• Notable
Events
The page displays a toolbar that you can configure to display particular data for each of the data collection types. For example, you can choose the sort order and column headings.
When data is present, the
The Widgets tab is a portal to statistics about the system.
• Displays a list of objects that provide
Configuration,
SIP, and System statistical data.
Depending on the object selected, you can view the data in list, table, pie chart, bar graph, and line graph form.
• Displays a list of
Favorite widgets.
System Tab
The System tab displays the following management controls:
• File management.
Displays a list of file types and a set of controls to
Refresh,
Upload,
Download,
Backup,
Restore, and
Delete files.
• Force HA
Switchover.
Manually place the system in the standby state.
• Reboot.
Manually reboot the
12 Oracle
®
Enterprise Session Border Controller
Home Tab Configuration
Tab
Monitor and
Trace Tab
• Save. Save and activate
.
the configuration
• Discard.
Delete unsaved configuration changes.
• Wizards. Set boot parameters,
Set initial configuration
, Set time zone, and
Upgrade software.
• Switch to
Expert.
Change from
Basic mode
Network
Interface.
• Security.
Configure a
Certificate
Record, the
SDES profile, and the TLS profile.
• Management.
Configure
Accounting,
SNMP
Community,
Trap
Receiver, and
Web Server.
• Other.
Configure
Media
Profile,
Translation
Rules, SIP
Features, SIP
Manipulation s, and SPL.
following task controls are active:
• Search.
Configure a search filter.
• Show all.
Override the display filter and show all data.
• Ladder diagram.
Displays data in a ladder diagram.
• Export session details. Save the detailed data to an external location.
• Export summary.
Save a summary of the data to an external location.
Widgets Tab
Oracle
®
Enterprise Session Border Controller
Overview
System Tab
system at any time.
• Support information.
Generate a file that displays troubleshooti ng information that you can save and send to
Oracle
Customer
Support.
• Upgrade
Software.
Verify the health of the system software, for example, synchronizati on health, configuration version, and disk usage.
Configure the upload method, browse to the software file to upload, and opt to automatically reboot the system after the upgrade.
13
Overview
Expert Mode
Home Tab Configuration
Tab
Monitor and
Trace Tab
Widgets Tab
to Expert mode.
• Search.
Search for objects and attributes.
Same as in Basic
Mode
In Expert Mode the
Configuration tab displays a list of configuration objects, grouped like those in the
Acme Command
Line Interface
(ACLI). For example:
• Media
Manager
• Security
• Session
Router
• System
Each group contains the same configuration objects as the
ACLI. Each object displays the corresponding configuration dialog.
Same as in Basic
Mode
Same as in Basic
Mode
Monitor and Trace Tools
The Web GUI provides specific tools on the Monitor and Trace tab that you can use to display data.
System Tab
Same as in Basic
Mode
Refresh
Click the at the bottom of any page to update the window with the latest data.
14 Oracle
®
Enterprise Session Border Controller
Overview
Changing Number of Data Items on the Page
By default, 50 data items are shown per page. You can change the number of items that display on a page.
To change the number of data items displayed in Monitor and Trace:
1. At the bottom left corner of the window, click the down arrow next to Size. The drop down list of values appears.
Oracle
®
Enterprise Session Border Controller 15
Overview
2. Click the number of data items you want to display per page. Default is 50. Valid values are 10 to 100 in increments of 10.
Navigating Pages
To navigate through multiple pages in Monitor and Trace:
1. Use the navigation arrows located at the bottom left corner of the window to navigate through the desired pages
(first, previous, next, last). Or enter the page number you want to view in the page box
16
Pop-up Context Menu
All reports support a pop-up context menu that you can use to select a Ladder diagram, Export Session Details, and
Export Session Summary.
To display the pop-up context menu in any report in Monitor and Trace:
1. Click a record on the page, and right-click to display the context menu.
2. Click an option on the menu.
The applicable page displays or the export begins, depending on the option you selected..
Shortcut Keys
The following tables list the shortcut key commands for the Home page and the Configuration page.
Oracle
®
Enterprise Session Border Controller
Overview
Home Page
Add a Widget
Refresh
Shortcut Key Command
Ctrl+Shift+a
Ctrl+Shift+r
Configuration Page
Discard
Save
Search
Shortcut Key Command
Ctrl+Shift+d
Ctrl+Shift+s
Ctrl+Shift+e
Home Tab
The Oracle Enterprise Session Border Controller (E-SBC) provides a web-based dashboard on the Home tab that can display SIP data statistics to help you monitor and manage the system, for example, SIP Media Flows and Current
Memory Usage. The E-SBC collects only SIP data for the dashboard widgets, including the default CPU and Memory widgets. For this reason, you must set up a valid SIP configuration before the E-SBC can display any data on a dashboard widget.
The Dashboard supports up to 18 widgets. Each widget can display up to 100 data samples in intervals of 1 hour, 1 minute, or 1 second. You can select a chart, a graph, a table, a web form, or text for the display. Customize the dashboard by adding, deleting, and moving the widgets. You can refresh the statistics displayed on the dashboard and you can reset the dashboard to its default display. The default display includes:
• Highest CPU Usage
• Current Memory Usage
• Historical Memory Usage
The following table describes the controls that you can use to customize the Home page display.
Button Description
Refresh Updates all of the widgets on the Dashboard.
Add widget Displays a list of widgets that you can add to the Dashboard.
Reset Resets the Dashboard to display the default widgets. All other widgets are removed from the
Dashboard.
Use the icons in the upper right corner of the widget to perform specific tasks. Roll the mouse over the icon for a description of the function.
Oracle
®
Enterprise Session Border Controller 17
Overview
18
Note that the operation of widgets, such as those that require the SIP.Session module, may affect system performance.
The system displays a warning when you add a widget that may affect performance. Oracle recommends adding such widgets at a time when the performance impact will not degrade service.
Types of Widgets
The following tables describe the types of widgets that you can add to the Dashboard to display Command, Session
Initialization Protocol (SIP), and System, statistics.
Command Widget
Show Configuration
Description
Displays either the running configuration or the editing configuration for the selected configuration.
SIP Widget
Message - Requests per second
Message - Response
Session - Answer Seizure Ratio (ASR)
Session- Duration
Session - Established
Description
Displays the number of requests per second.
Displays the number of responses per second.
Displays the percentage of answered calls with respect to the number of calls attempted during a period of time.
Displays the total number of sessions and their durations.
Displays the number of sessions established during a period of time.
System Widget
Alarms
Configuration Inventory
Description
Displays configured alarms and allows the user to clear the alarms.
Displays a list of changes made to configuration elements. The display shows the Running Count and counts for the following types of Changes Not Activated.
• Total
• Added
• Modified
• Deleted
Oracle
®
Enterprise Session Border Controller
System Widget
Configuration Version
CPU Usage
Current Disk
Current Memory
Historical Memory
System Health
User Management
Overview
Description
A selectable filter can change the display from Total count to the difference between the Running Count and the Changes Not Activated Count.
Displays the version number that is configured and the version number that is running.
Displays 5 to 10 tasks with the highest percent of CPU usage during a period of time.
Displays the disk usage for the code directory on the
Oracle Enterprise Session Border Controller. The system uploads data from the Web GUI to the code directory.
Displays the current percentage of free memory.
Displays the number of kilobytes of free and allocated memory over a period of time.
Displays the synchronization health of the following components.
• Collect
• Config
• Media
• Media Gateway Control
• RADIUS Call Detail Record (CDR)
• REC
• Rotated Call Detail Record (CDR)
• Service Health
• SIP
Displays the user's remote IP address, duration, type, state, and user name.
Add a Dashboard Widget
Add a widget to the Web GUI Dashboard to display SIP and System statistics to help you monitor and manage the system.
You can add up to 18 widgets to the Dashboard with the Add widget control on the Web GUI Home page. The system does not require a reboot after adding a widget to the Dashboard.
Note: If the system displays a warning that adding this widget requires the SIP.Message module to be enabled, the system enables the SIP.Message module when you add the widget.
Procedure
1. From the Home page, click Add widget.
2. From the list of Widgets, click the name of the widget to add.
3. Under the Command column header, click Add for the widget to add.
The system displays a success message.
4. Click OK.
5. Click Close.
The system displays the Dashboard with the newly added widget.
See "Configure Data Sampling Settings for a Dashboard Widget."
Oracle
®
Enterprise Session Border Controller 19
Overview
Configure Data Sampling Settings for a Dashboard Widget
To see SIP and System statistics displayed on a Dashboard widget, the system requires a setting for how often to refresh the display. You can use the default interval or select one from the Auto-refresh interval drop-down list on the widget. Some widgets also display the Table Name drop-down list, where you can set the data sampling frequency.
For example, you might configure the widget to refresh the display every 40 seconds and to display the data samples in one minute increments.
Before you begin, confirm that the widget that you want to configure is on the Dashboard. See Add a Widget.
1. On the Dashboard, click the Home tab.
2. On the widget, click the Settings icon.
3. Select a widget display refresh frequency from the Auto-Refresh Interval (seconds) drop down list.
4. If the widget displays the Table Name drop-down list, select a data sampling increment for the widget display.
5. Click OK.
Stats Portal
The Stats Portal is a link on the Web GUI that displays data about SIP traffic and System operations on the Oracle
Enterprise Session Border Controller.
The Oracle Enterprise Session Border Controller captures data about SIP traffic and System operations. The system can display the data on the Web GUI in small Dashboard widgets and in full screen mode. Use the Stats Portal to view the data in full screen mode. From the Stats Portal page, you can use the controls to do the following.
Control
Refresh
Description
Use to update the statistics in the widget.
Settings
Export
Use to configure the following display settings.
• Table Name
• Auto-Refresh Interval
Note: Table Name is applicable to specific widgets only.
Use to export the data from the widget to a .csv file. The data in the .csv file displays in table format.
Use to add the widget to the Dashboard.
Add
Help Use to view a short description of the widget.
From the Stats Portal page, you can return to the Dashboard and you can click another tab on the menu bar.
View System Data Through the Stats Portal
Use the Stats Portal to display data from the SIP and System Dashboard widgets in full-screen mode.
Procedure
1. From the Home page, click Stats Portal.
2. In the navigation pane, click a Dashboard Widget name.
3. In the Object column, click an object to display.
20 Oracle
®
Enterprise Session Border Controller
Overview
Customize the Page Display
You can customize the display of the data on the Web GUI pages by selecting which columns display and the sort order of the data in the columns.
To customize the page display:
1. Position the cursor over a column heading.
The system displays a down arrow in column the heading.
2. Click the down arrow to display the menu. For example:
3. Use the following options to customize the display.
• Sort Ascending. Display the data in the table in ascending order.
• Sort Descending. Display the data in the table in descending order.
• Columns. Display a list of column names, where you can select items to display.
• Group by This Field. Applies only to the System tab. See Group by Field for more information.
Group By Field
To customize the display of the File Management page on the System tab, you can group the elements by column head.
Procedure
1. From the Web GUI, click System.
2. On the System page, under File management, select a file type from the drop-down list to group by field.
3. On the File Management page, click the column title by which you want to group the items.
The system displays an arrow control to the right of the column title.
4. Click the arrow control, and click Group By This Field on the menu.
The system displays the data by the selected group.
Oracle
®
Enterprise Session Border Controller 21
2
Configuration
Introduction
You can configure the necessary basic and advanced parameters from the following modes:
• Basic Mode - Drag and drop icons. Recommended for most deployments.
• Expert Mode - Select objects and elements from a hierarchy. Recommended for complex deployments.
Wizards Button
The Wizards button displays a menu of configuration wizards from which you can perform, save, and activate selected configuration procedures for the Oracle Enterprise Session Border Controller. Configuration wizards are available in the Basic mode and in the Expert mode.
The Wizards button provides access to the following configuration wizards.
Configuration Wizard
Set boot parameters
Set entitlements
Set initial configuration
Set license
Set logon banner
Set time zone
Upgrade Software
Purpose
Specify the boot file and the boot parameters.
Set the number of sessions that a license entitles, and enable advanced features.
Configure a new system and reconfigure an existing system.
Enter the license number for a feature.
Customize the text on the Web GUI logon banner.
Select the time zone for the deployment.
Upload a new version of the software.
Initial Configuration Wizard
Release E-C[xz]6.4.0M3 adds the Initial Configuration wizard to the Web GUI. The Initial Configuration wizard was accessible only from the command line in previous releases. You can use the Initial Configuration wizard to perform the initial configuration on an unconfigured system and to change the configuration on a configured system. During the configuration, you define the boot parameters, select the configuration mode, and select the session border controller mode. A valid license is required to run the Initial Configuration wizard.
Oracle
®
Enterprise Session Border Controller 23
Configuration
• Unconfigured system. The system displays the Web GUI Initial Configuration wizard upon the first logon. When the initial configuration is complete, the system saves the configuration, activates the configuration, and reboots the system. The system does not backup the initial configuration of an unconfigured system.
• Configured system. Launch the Initial Configuration wizard from the Web GUI. When the re-configuration is complete, the system saves a backup of the existing configuration, saves the new configuration, activates the new configuration, and reboots the system. The backup is stored in /code/bkups.
Next Steps
• Configure the system objects.
• Optional. Reconfigure the system.
Configure the System
The system requires an initial configuration of attributes, such as modes and IP addresses, before it can function in the network.
Use the Set initial configuration wizard to define the attributes for the system. The system displays the Set initial configuration wizard upon the first logon.
Procedure
1. Logon to the Oracle Enterprise Session Border Controller.
The system displays the Set initial configuration wizard.
2. Run the Set initial configuration wizard, and click Complete.
The system saves the configuration, activates the configuration, and reboots.
Next Steps
• (Optional) Configure the system objects.
Reconfigure the System
You can reconfigure the system from the Web GUI.
Use the Set initial configuration wizard to change the initial configuration on a configured system, for example, change attributes such as IP addresses and modes.
Procedure
1. Logon to the system.
2. From the Web GUI, go to Configuration > Wizards > Set initial configuration.
3. Run the Set initial configuration wizard and change the attributes, as needed.
4. Click Complete.
The system saves a backup of the existing configuration, saves the new configuration, activates the new configuration, and automatically reboots.
Next Steps
• (Optional) Reconfigure the system objects.
Set the Boot Parameters
The Oracle Enterprise Session Border Controller (E-SBC)requires you to enter the necessary parameters to boot the system in your deployment.
You can set the system boot parameters from the Set boot parameters wizard on the Web GUI in either Basic mode or
Expert mode.
1. From the Web GUI, click Configuration > Wizards > Set boot parameters.
2. In the Set boot parameters dialog, enter the following information:
• Boot File. Name of the image file.
• IP Address.
• VLAN.
• Net Mask.
24 Oracle
®
Enterprise Session Border Controller
Configuration
• Gateway. Internet address of the boot host. Leave blank if the host is on the same network.
• FTP Host IP.
• FTP Username.
• FTP Password. FTP password for the FTP user on the boot host.
• Flags. Hexadecimal. Always starts with 0x. See "Configurable Boot Loader Flags."
• Target Name. Name of the E-SBC, as displayed at the system prompt.
• Console Device.
• Console Baud Rate.
3. Click Complete.
The system displays a success message.
4. Click OK.
Configurable Boot Loader Flags
You may configure the following boot flags in the boot loader:
• 0x04 - disables autoboot timeout (ap3820 and ap4500 only)
• 0x08 - extend autoboot countdown timer to 15 seconds
• 0x40 - use DHCP for wancom0 (VM Edition only)
• 0x80 - network boot using TFTP instead of FTP
Set Time Zone
The system requires a setting for time zone.
You can set the system time from the Set time zone wizard on the Web GUI. You can select a time zone or
Coordinated Universal Time (UTC). The wizard is available in Basic Mode and Expert Mode.
Procedure
1. From the Web GUI Home page, click Configuration > Wizards > Set time zone.
2. From the drop down list, select one of the following:
• Time zone by locale
• UTC
3. Click Complete.
The system displays a success message.
4. Click OK.
User and Administrator Access Rules
Users and Administrators can use the Oracle Enterprise Session Border Controller Web GUI according to the rules for their role.
The following table describes the Web GUI access rules for the User and Administrator roles.
Role
User
Rule
User
• Read-only access only
• View basic and advanced configuration information
• Cannot save and activate a configuration
• Cannot add a configuration
• Cannot edit a configuration
Administrator Administrator
• Add, edit, and view configurations
Oracle
®
Enterprise Session Border Controller 25
Configuration
Role Rule
• Add, edit, and view advanced configurations
• Save and activate a configuration
• Switch between Basic mode and Expert mode
Workspace Tools
The Configuration tab provides specific workspace tools that you can use within the Basic mode and Expert mode pages. These tools can help you manage the items in your workspace, save and activate the configuration, and allow you to search for elements in the configuration.
Basic Mode Configuration Tools
Tool Description
Zoom-in: Used to increase the viewing size of the current window and all its contents.
Zoom-out: Used to decrease the viewing size of the current window and all its contents.
Enterprise Add Menu
Service Provider Add Menu
Actual size: Used to display the current window and all its contents on a one-on-one ratio (actual size).
Print: Provides a view of the image that you can print from your browser.
Add Menus - These menus can be accessed by rightclicking the mouse on the Enterprise side or the Service
Provider side.
Add > PBX/Device/SRS- Allows you to add a PBX, a
Device, or a Session Recording Server (SRS) to your
Enterprise configuration. You can use this menu in lieu of dragging and dropping these elements from the Device tools.
Add > Trunk/Remote Worker Allows you to add a Trunk or a Remote Worker, to your Service Provider configuration. You can use this menu in lieu of dragging and dropping these elements from the Device tools.
You can use the following tools from either menu instead of from the workspace tools in the upper right corner of the screen, if required:
Zoom-in: Allows you to view a workspace and all of its elements in a closer proximity.
Zoom-out: Allows you to view a workspace and all of its elements in a more distant proximity.
Actual Size:: Allows you to view a workspace and all of its elements in its actual size.
26 Oracle
®
Enterprise Session Border Controller
Tool
Oracle
®
Enterprise Session Border Controller
Configuration
Description
Edit/Delete Menu - This menu can be accessed by selecting an element on the screen and then right-clicking the mouse.
Edit: Allows you to edit the configuration of the element on which you right-clicked.
Delete: Allows you to remove the element from the workspace AND the configuration.
Discard - Allows you to discard all configuration changes made in the current session. Only the changes that have not yet been activated are discarded.
Switch to Expert - Switches from Basic Mode to Expert
Mode.
Note: Before you can switch to Expert Mode, you must save and activate your configuration in Basic Mode.
Caution: You can switch to Basic Mode from Expert Mode, if you do not save your changes. If you save your changes and you switch back to Basic Mode, you must run the Set
Initial Configuration wizard again. You will lose all of the configuration changes you made in both modes.
Search - Allows you to perform a search of any configuration element or sub-element on the Oracle
Enterprise Session Border Controller. You perform the search by entering a keyword which is not case sensitive.
Special characters are allowed.
Save - Allows you to verify and save the current configuration in Basic Mode. A prompt also displays giving you a choice of whether or not to activate the configuration.
Note: After clicking <Save>, a notification icon in the upper right corner of the screen indicates the configuration still needs to be activated. You can continue to make changes to the configuration as required. When finished, you can select Notifications > Save changes to save and activate the configuration. The notification icon grays-out after saving and activating.
Show advanced - This button displays in configuration dialog boxes that allow for more advanced parameters to be displayed. Oracle recommends that only Administrators configure these advanced parameters. When clicking this button, the advanced parameters display in italics, and the button toggles to a Hide advanced button.
Hide advanced - This button displays in configuration dialog boxes that allow for more advanced parameters to be hidden. Oracle recommends that only Administrators configure these advanced parameters. When clicking this button, the advanced parameters are hidden from view, and the button toggles to a Show advanced button.
27
Configuration
Expert Mode Configuration tools
Use the following tools to create the configuration in Expert Mode.
Button Description
Save - Allows you to verify and save the current configuration in Expert Mode. A prompt also displays giving you a choice of whether or not to activate the configuration.
Note: After clicking <Save>, a notification icon in the upper right corner of the screen indicates the configuration still needs to be activated. You can continue to make changes to the configuration as required. When finished, you can select Notifications->Save changes to save and activate the configuration. The notification icon grays-out after saving and activating.
Search - Allows you to perform a search of any configuration element or sub-element on the Oracle
Enterprise Session Border Controller. You perform the search by entering a keyword which is not case sensitive.
Special characters are allowed.
Switch to Basic - Switches from Expert Mode to Basic
Mode.
Note: If you save your configuration in Expert Mode, you cannot switch to Basic Mode.
Caution: You can switch to Basic Mode from Expert Mode, if you do not save your changes. If you save your changes and you switch back to Basic Mode, you must run the Set
Initial Configuration wizard again. You will lose all of the configuration changes you made in both modes.
Show advanced - This button displays in configuration dialog boxes that allow for more advanced parameters to be displayed. Oracle recommends that only Administrators configure these advanced parameters. When clicking this button, the advanced parameters display in italics, and the button toggles to a Hide advanced button.
Hide advanced - This button displays in configuration dialog boxes that allow for more advanced parameters to be hidden. Oracle recommends that only Administrators configure these advanced parameters. When clicking this button, the advanced parameters are hidden from view, and the button toggles to a Show advanced button.
Basic Mode
Basic mode is a method for configuring your network for the Oracle Enterprise Session Border Controller (ESBC) by way of a Web-based Graphical User Interface (GUI).
The Basic Mode Web GUI displays a workspace with drag-and-drop icons for the elements required to deploy the E-
SBC between the Enterprise side and the Service Provider side of the network. When you drop an element icon into the workspace, the E-SBC displays the appropriate configuration dialog for the element. No other configuration
28 Oracle
®
Enterprise Session Border Controller
Configuration
parameters are required, but advanced parameters are available in some Basic Mode dialogs. You can group like elements, create local policies between the elements in the workspace, and add new network interfaces to the E-SBC.
Note: The Web GUI does not indicate required fields. You may be able to save the configuration without a required value because the E-SBC ignores the element in the configuration. The system does not display an error message for a missing required parameter.
Accessing Basic Mode
Access the Basic configuration mode on the Web GUI from the Configuration tab.
Log onto the Web GUI, and click on the Configuration tab.
Note: If “Expert Mode” was set as the default during the Installation Setup Wizard in the ACLI, you cannot switch to Basic Mode. If you want to configure in Basic Mode, contact your Administrator.
Oracle
®
Enterprise Session Border Controller 29
Configuration
This page displays the Basic mode for configuring the Net-Net ESD on a workspace that you can use to configure the network. The ESD is centered in the middle between the Enterprise network on the left and the Service
Provider network on the right.
To populate the network, use the Devices tool bar on the left of the page to drag and drop selected elements onto the workspace. Elements in the toolbar are associated specifically with Enterprise or Service Provider. If you drag and drop an element to an incorrect location in the workspace, the system displays the following error message:
"This icon cannot be placed here."
Device Icons Toolbar
The system displays drag-and-drop icons on the Devices tool bar in the Basic mode workspace for configuring the system in the network.
The following table describes each icon on the Devices toolbar.
Element
Elements for Enterprise
Description
When adding any of the Enterprise elements below, a dialog box displays for you to configure the device.
PBX - Drag-and-drop icon
Adds a Private Branch Exchange (PBX) to your Enterprise network.
A PBX is a privately owned telephone switching system for handling multiple telephone lines. Users of the PBX share a certain number of outside lines for making telephone calls external to the PBX.
Device - Drag-and-drop icon
Adds a network device (router, media device, phone, etc.) to your Enterprise network.
A device can be any network device used to setup the Enterprise Local Area
Network (LAN).
Elements for Service Provider
Recording Server - Drag-and-drop icon
Adds a session recording server (SRS) to your Enterprise network.
An SRS is a 3rd party call recorder or the Net-Net ISR’s Record and Store
Server (RSS)). It controls the recording of media transmitted in the context of a communications session between multiple user agents.
SIP Network Interface - Drag-and-drop icon
Adds a Session Initiation Protocol (SIP) network interface to the Enterprise side of the Oracle Enterprise Session Border Controller. You can add up to five (5) SIP interfaces.
Note: You can associate a SIP interface to any configured network interface.
When adding any of the Service Provider elements below, a dialog box displays for you to configure the device.
Trunk - Drag-and-drop icon
Adds a SIP Trunk to the Service Provider network.
A SIP trunk is a service offered to Enterprises by a Service Provider that permits the Enterprises with PBXs installed, to use IP communications
30 Oracle
®
Enterprise Session Border Controller
Element
Configuration
Description
(including Voice over IP (VoIP)) outside of their Enterprise network on an
Internet connection.
Remote Worker - Drag-and-drop icon
Adds a Remote Worker to the Service Provider network.
A Remote Worker is a device that is setup outside the network but is still connected to the Oracle Enterprise Session Border Controller from the remote location.
SIP Network Interface - Drag-and-drop icon
Adds a SIP network interface to the Service Provider side of the Oracle
Enterprise Session Border Controller. You can add up to five (5) SIP interfaces.
Note: You can associate a SIP interface with any configured network interface.
Elements for Both
Selection Tool - Select this then click on any element in your workspace.
This tool allows you to select any element in your network.
Image Mover - Select this then click on the image in your workspace.
This tool allows you to move the entire image of your network around within the workspace.
Two-Way Local Policy - Select this first then click on the center of an icon in your network.
This tool allows you to create a two-way route (local policy) between devices within your local network, or between the devices on the Enterprise side and the Service Provider side.
When adding a two-way route, a dialog box displays for you to configure the route.
One-Way Local Policy - Select this first then click on the center of an icon in your network.
This tool allows you to create a one-way route between devices within your local network, or between the devices on the Enterprise side and the Service
Provider side.
When adding a one-way route, a dialog box displays for you to configure the route.
Grouping Tool - Select the devices in your network that you want to group, then select the grouping tool.
This tool allows you to create a grouping around like devices in your network (i.e., multiple PBXs, multiple routers, etc.).
When creating a group, a dialog box displays for you to configure the group.
Ungrouping Tool - Select the group you want to ungroup first, then select the ungrouping tool to ungroup the devices.
Oracle
®
Enterprise Session Border Controller 31
Configuration
Element Description
This tool allows you to remove a grouping from around like devices in your network (i.e., multiple PBXs, multiple routers, etc.).
When removing a group, the group configuration information is removed
(not the device configurations within the group).
As you place an element in the workspace, the element connects to the SIP interface on the Oracle Enterprise Session
Border Controller automatically, and a configuration dialog box displays allowing you to configure the element for your network.
You can use the workspace tools on the upper right corner of the screen to zoom in, zoom out, display actual size, or print the current screen.
Note: For more information about the workspace tools, see Workspace Tools.
Device Icon Connection Matrix
Before configuring the Oracle Enterprise Session Border Controller (E-SBC) from the Web GUI workspace, you need to know the types of connections that the system supports between device icons.
The Web GUI Basic mode workspace supports connections between Enterprise and Service Provider device icons in two ways. You can configure a one-way route or a two-way route between devices. The configured route is called a local policy. You can also connect certain device icons by way of the Advanced Routing icon located on the E-SBC graphic.
The following matrices show the device icons and their supported connections for a one-way policy, for a two-way policy, and for advanced routing. The Recording Server icon is not included here because you cannot route one by way of local policy.
One-Way Routing Local Policy
From To
32
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
Yes
Yes
Oracle
®
Enterprise Session Border Controller
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
Configuration
Yes
No Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
No
No
No
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
No
Yes
No
No
No
Yes
Two-Way Routing Local Policy
From To
Yes Yes Yes Yes Yes Yes No Yes
Oracle
®
Enterprise Session Border Controller 33
Configuration
Yes Yes Yes Yes Yes Yes No Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
No
No
No
No
Yes
Yes
No No
Yes Yes
No No
Yes Yes
No
Yes
No No
Yes No
No
Yes
Advanced Routing Local Policy
From To
34 Oracle
®
Enterprise Session Border Controller
Configuration
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
Typical Network Configuration
You can configure your network using the Basic Mode method to configure the devices.
The high-level process for a typical network configuration follows:
1. Add a PBX to the Enterprise Side.
2. Add a SIP Trunk to the Service Provider Side.
Oracle
®
Enterprise Session Border Controller 35
Configuration
3. Add a Local Policy (2-way route) between the PBX and the SIP Trunk.
4. Verify the Network Interface on the Oracle Enterprise Session Border Controller is correct on the Enterprise and
Service Provider sides.
Note: Drag-and-drop the icons from the Device tool bar onto the space below the titles of “Enterprise Side” and Service Provider Side. The workspace does not allow you to place icons above the titles.
Add a PBX
To add a PBX to the Enterprise side:
1. Click on the PBX icon in the device tool bar, and drag it to the Enterprise side in the workspace. The following dialog box displays.
36
2. In the PBX name field, enter the name to assign to this PBX in the Enterprise network. For example, PBX1. Valid values are alpha-numeric characters.
3. (optional) In the Description field, enter a description for this PBX. For example, PBX for Enterprise. Valid values are alpha-numeric characters.
4. In the Hostname field, enter the hostname of the Oracle Enterprise Session Border Controller to which this PBX is connected. For example, ESD1. Valid values are alpha-numeric characters.
5. (optional) In the IP address field, enter the IP address of this PBX. Enter the address in dotted decimal format. For example, 1.1.1.1. Default is 0.0.0.0.
Note: By default, the Port on the PBX is 5060. Also, setting all other parameters in this dialog box is optional. If you want to modify the values of the remaining parameters, or if you want to set more advanced parameters, see the Net-Net
®
Enterprise Session Director Configuration Guide for more
information. Oracle recommends that only Administrators add or modify adavanced parameters.
6. Click <OK> to save your settings. The PBX displays in your Enterprise workspace with the name of the PBX displayed beneath the icon. You can edit the PBX configuration anytime if required, by double-clicking the icon and modifying the configuration in the dialog box.
Add a Trunk
To add a SIP Trunk to the Service Provider side:
Oracle
®
Enterprise Session Border Controller
Configuration
1. Click on the Trunk icon in the device tool bar, and drag it to the Service Provider side in the workspace. The following dialog box displays.
2. In the Trunk name field, enter the name to assign to this SIP Trunk in the Service Provider network. For example,
TrunkA. Valid values are alpha-numeric characters.
3. (optional) In the Description field, enter a description for this SIP Trunk. For example, Trunk between SP and Ent.
Valid values are alpha-numeric characters.
4. In the Hostname field, enter the hostname of the Oracle Enterprise Session Border Controller to which this Trunk is connected. For example, ESD1. Valid values are alpha-numeric characters.
5. (optional) In the IP address field, enter the IP address of this SIP Trunk. Enter the address in dotted decimal format. For example, 2.2.2.2. Default is 0.0.0.0.
Note: By default, the IP Port on the SIP Trunk is 5060. Setting all other parameters in this dialog box is optional. If you want to modify the values of the remaining parameters, or if you want to set more advanced parameters, see the Net-Net
®
Enterprise Session Director Configuration Guide for more
information. Oracle recommends that only Administrators add or modify advanced parameters.
6. Click <OK> to save your settings. The Trunk displays in your Enterprise workspace with the name of the Trunk displayed beneath the icon. You can edit the Trunk configuration anytime if required, by double-clicking the icon and modifying the configuration in the dialog box.
Add a Local Policy
To add a Local Policy (2-way route) between the PBX and the SIP Trunk:
1. In the connectors section of the device tool bar, click on the 2-way arrow to select it.
2. Click in the center of the PBX icon in the Enterprise network. A small arrow displays.
Oracle
®
Enterprise Session Border Controller 37
Configuration
3. Holding down the left mouse button, drag the mouse over to the Trunk icon, making sure a green border appears around the Trunk icon.
4. Release the left mouse button. This draws a 2-way arrow (local-policy) between the PBX and the Trunk. A dialog box displays.
38 Oracle
®
Enterprise Session Border Controller
Configuration
5. In the Route name field, enter a name for this route. For example, RouteA.
6. Click <OK>. You can edit the local policy configuration anytime if required, by double-clicking the 2-way arrow and modifying the configuration in the dialog box.
Note: If you want to modify the values of the remaining parameters, or if you want to set more advanced parameters, see the ACLI Configuration Guide for more information.
Modify Enterprise Network Interface
To modify the Enterprise network interface:
1. From the Main Menu, select Network > Network interface. The following dialog box displays.
Oracle
®
Enterprise Session Border Controller 39
Configuration
The list in the above dialog box shows the current default settings.
2. From the list of network interfaces, select ENT (Enterprise) and click <Edit>. The following dialog box displays.
40
3. In the IP address field, enter the IP address of the network interface on the Enterprise side. Enter the address in dotted decimal format. Default is 172.16.1.100.
4. In the Netmask field, enter the netmask address of the network interface on the Enterprise side. Enter the address in dotted decimal format. Default is 255.255.255.0.
5. In the Gateway field, enter the IP address of the gateway associated with the network interface on the Enterprise side. Enter the address in dotted decimal format. Default is 172.16.1.1.
For a High Availibility (HA) environment:
6. In the Pri utility address field, enter the IP address of the primary Oracle Enterprise Session Border Controller.
Enter the address in dotted decimal format. Default is 172.16.1.101.
7. In the Sec utility address field, enter the IP address of the secondary (backup) Oracle Enterprise Session Border
Controller. Enter the address in dotted decimal format. Default is 172.16.1.102.
Oracle
®
Enterprise Session Border Controller
Configuration
Note: If you want to modify the values of the remaining parameters, or if you want to set more advanced parameters, see the Net-Net
®
Enterprise Session Director Configuration Guide for more information.
Oracle recommends that only Administrators add or modify advanced parameters.
8. Click <OK> to save the changes. The following dialog box displays.
9. Modify the Service Provider network address using the procedure in Modify Service Provider Network Interface.
Modify Service Provider Network Interface
To modify the Service Provider network interface:
1. From the Main Menu, select Network > Network interface. The following dialog box displays.
The list in the dialog box shows the current default settings.
2. From the list of network interfaces, select SP (Service Provider) and click <Edit>. The following dialog box displays.
Oracle
®
Enterprise Session Border Controller 41
Configuration
42
3. In the IP address field, enter the IP address of the network interface on the Service Provider side. Enter the address in dotted decimal format. Default is 192.168.1.100.
4. In the Netmask field, enter the netmask address of the network interface on the Service Provider side. Enter the address in dotted decimal format. Default is 255.255.255.0.
5. In the Gateway field, enter the IP address of the gateway associated with the network interface on the Service
Provider side. Enter the address in dotted decimal format. Default is 192.168.1.1.
For a High Availibility (HA) environment:
6. In the Pri utility address field, enter the IP address of the primary Oracle Enterprise Session Border Controller.
Enter the address in dotted decimal format. Default is 192.168.1.101.
7. In the Sec utility address field, enter the IP address of the secondary (backup) Oracle Enterprise Session Border
Controller. Enter the address in dotted decimal format. Default is 192.168.1.102.
Note: If you want to modify the values of the remaining parameters, or if you want to set more advanced parameters, see the Net-Net
®
Enterprise Session Director Configuration Guide for more information.
Oracle recommends that only Administrators add or modify advanced parameters.
8. Click <OK> to save the changes. The following dialog box displays.
Oracle
®
Enterprise Session Border Controller
Configuration
9. Click the x in the upper right corner to close this dialog box.
Note: You can modify additional parameters if required, for the Enterprise and Service Provider network interfaces by clicking on the network interface icons on the Oracle Enterprise Session Border Controller.
For more information on setting advanced parameters, see your Net-Net
®
Enterprise Session Director
Configuration Guide.
Save and Activate Network Configuration
When you finish creating the network, you must save and activate the configuration on the Oracle Enterprise Session
Border Controller.
1. In any configuration dialog, click OK.
The system verifies and saves the current configuration to the last-saved configuration, which is stored in flash memory. This allows you to queue multiple changes during a configuration session before you set them all on the device.
2. Optional. Perform additional configuration, and click OK each time.
3. Click Save.
The system displays the Confirmation dialog, with the Activate button.
4. Click Activate.
The system displays the success dialog.
5. Click OK.
The system moves the changes from the flash memory to the running configuration.
Configuration Error Messages
For both Basic and Expert Mode, if you save a configuration that contains errors, the errors display in a window at the bottom of the screen, and the following message displays:
There were errors! Are you sure you want to activate the configuration?
The following is an example of errors that display for a configuration in Basic Mode.
Oracle
®
Enterprise Session Border Controller 43
Configuration
Click the error link in the Object column to go to the exact location in the configuration where the error exists, and then edit the configuration as applicable.
The following table identifies the columns in the error list.
Column
Severity
Description
Identifies the level of severity that the Oracle Enterprise Session Border Controller assigns to the error. Valid values are:
ERROR - Indicates the issue identified in the "Message" column was not correctly configured or it does not exist. You can still verify, save, and activate the configuration if this severity exists.
WARNING - Indicates the configuration contains invalid information for the element field identified in the "Message" column. You can still verify, save, and activate the configuration if this severity exists.
CRITICAL - Indicates a critical error has occurred in the configuration and you cannot verify, save, or activate until the error is corrected. The "Message" column indicates the element field where the error has occurred.
Message
Object
Attribute
Other Object
Identifies the element field(s) where the error, warning, or critical error has occurred, and identifies the reason for the error.
Identifies the element and the field for that element where the error occurred.
Identifies the attribute within the element where the error occurred.
Identifies the other object when more than one object caused the error.
Basic Mode Configuration Buttons and Dialogs
In Basic mode, the Configuration tab toolbar displays the following buttons that lead to the corresponding sets of configuration dialogs.
Buttons
Wizards
Configuration Dialogs
• Set boot parameters
• Set entitlements
• Set initial configuration
• Set license
• Set time zone
• Upgrade software
44 Oracle
®
Enterprise Session Border Controller
Buttons
Settings
Network
Security
Management
Other
Configuration
Configuration Dialogs
• Hostname and default gateway
• NTP IP address
• Enable restart on critical failure
• Logging settings
• SNMP settings
• SIP settings
• Denial of Service settings
• Communications monitoring probe settings
• High availability settings
• Packet capture settings
• Survivability
• Host route
• Network interface
• Certificate record
• SDES profile
• TLS profile
• Accounting
• SNMP community
• Trap receiver
• Web server
• Media profile
• Translation rules
• SIP features
• SIP manipulations
• SPL
Settings Button
In Basic mode, use the Settings button on the Web GUI to configure the following configuration elements.
• SBC hostname
• Description
• Location
• Default gateway IP address
• Network Time Protocol IP address
• Logging settings
• SNMP settings
• SIP settings
• Denial of service settings
• Communications monitoring probe settings
• High availability settings
• Packet capture settings
• Survivability
Oracle
®
Enterprise Session Border Controller 45
Configuration
Advanced Settings
An Administrator can configure the following advanced parameters:
• Enable restart on critical failure
For more information on this setting, see Initiating Packet Capture in the Oracle
®
Enterprise Session Border
Controller ACLI Configuration Guide.
Additional Global Settings
You can set the following additional global settings on the Oracle Enterprise Session Border Controller if required:
• Logging
• SNMP
• SIP
• Denial of service (DoS)
• Communication Monitor Probe
• High Availability (HA)
Each of these global settings is described in the following paragraphs.
Logging Settings
The Oracle Enterprise Session Border Controller (E-SBC) generates two types of logs - syslogs and process logs.
Syslogs conform to the standard used for logging servers and processes as defined in RFC 3164.
Process logs are Oracle proprietary logs. Process logs are generated on a pertask basis and are used mainly for debugging purposes. Because process logs are more data inclusive than syslogs, their contents usually encompass syslog log data. A special application must be run on a remote server to receive process logs. Please contact your
Oracle sales representative for more information about the process log application.
Syslog and process log servers are both identified by an IPv4 address and port pair.
1. From the Web GUI, click Settings..
2. In the Settings dialog, do the following: a) Click Logging Settings, to display the settings.
b) SysLog server IP address. Enter the IPv4 address of a syslog server.
c) Process log level. Select the starting log level of all processes running on the E-SBC.
3. Click OK..
4. Save and activate the configuration.
Simple Network Management Protocol (SNMP) Settings
SNMP is an Internet-standard protocol for managing devices on IP networks. It consists of a set of standards for network management, including an application layer protocol, a database schema, and a set of data objects.
SNMP is used to support monitoring of network-attached devices for conditions that warrant administrative attention.
SNMP is comprised of three groups of settings on the Oracle Enterprise Session Border Controller (E-SBC). These settings are system-wide configurations including MIB contact information, SNMP community settings, and trap receivers.
For more information, see the SNMP section in the Oracle Enterprise Session Border Controller ACLI Configuration
Guide.
1. From the Web GUI, click Settings.
2. In the Settings dialog, do the following: a) Click SNMP settings to display the settings.
b) MIB system contact. Enter the contact information to use in the E-SBC MIB transactions.
c) MIB system name. Enter the identification of this E-SBC presented in MIB transactions.
d) MIB system location. Enter the physical location of this E-SBC that is reported within MIB transactions.
46 Oracle
®
Enterprise Session Border Controller
Configuration
e) Enable event SNMP traps. Enable the E-SBC to report event SNMP traps.
3. Click OK.
4. Save and activate the configuration.
SIP Settings
Session Initiation Protocol (SIP) is an IETF-defined signaling protocol widely used for controlling communication sessions such as voice and video calls over Internet Protocol (IP). The protocol can be used for creating, modifying and terminating two-party (unicast) or multiparty (multicast) sessions. Sessions may consist of one or several media streams.
Dialog Transparency
Dialog transparency prevents the Oracle Enterprise Session Border Controller (E-SBC) from generating a unique
Call-ID and modifying dialog tags. With dialog transparency enabled, the E-SBC is prevented from generating a unique Call-ID and from modifying the dialog tags. The Oracle Enterprise Session Border Controller passes what it receives. When a call made on one E-SBC is transferred to another UA and crosses a second E-SBC, the second E-
SBC does not note the context of the original dialog, and the original call identifiers are preserved end to end. The signalling presented to each endpoint remains in the appropriate context regardless of how many times a call crosses through a E-SBC or how many E-SBCs a call crosses.
Without dialog transparency enabled, the E-SBC SIP B2BUA rewrites the Call-ID header and inserted dialog cookies into the From and To tags of all messages it processes. These dialog cookies are in the following format:
SDxxxxxNN-. Using these cookies, the E-SBC can recognize the direction of a dialog. However, this behavior makes call transfers problematic because the Call-ID of one E-SBC might not be properly decoded by another E-SBC. The result is asymmetric header manipulation and unsuccdessful call transfers.
IPv6 Reassembly and Fragmentation Support
As it does for IPv4, the E-SBC supports reassembly and fragmentation for large signaling packets when you enable
IPV6 on the system.
The E-SBC takes incoming fragments and stores them until it receives the first fragment containing a Layer 4 header.
With that header information, the E-SBC performs a look-up so it can forward the packets to its application layer.
Then the packets are re-assembled at the applications layer. Media fragments, however, are not reassembled and are instead forwarded to the egress interface.
On the egress side, the E-SBC takes large signaling messages and encodes it into fragment datagrams before it transmits them.
Note that large SIP INVITE messages should be sent over TCP. If you want to modify that behavior, you can use the
SIP interface’s option parameter max-udplength=xx for each SIP interface where you expect to receive large INVITE packets.
Other than enabling IPv6 on your E-SBC, there is no configuration for IPv6 reassembly and fragmentation support. It is enabled automatically.
Configure SIP Features on the (E-SBC)
To set SIP features on the Oracle Enterprise Session Border Controller (E-SBC).
1. From the Web GUI, click Settings.
2. On the Settings page, click SIP settings > Show advanced to display the settings.
3. Under SIP Settings, do the following.
a) Select Enable dialog transparency.
b) Optional. Maximum SIP message length. Change the default 4096 to another value.
c) Select SIP UDP fragmentation.
d) Select Set INVITE expires at 100 responses.
e) Options. Optional. Add SIP options.
Oracle
®
Enterprise Session Border Controller 47
Configuration
4. Click OK.
5. Save and activate the configuration.
Advanced Settings
An Administrator can configure the following more advanced parameters:
• Maximum SIP message length
• SIP options
For more information on these settings, see “Fraud Prevention” and SIP Options Tag Handling in the Net-Net
®
Enterprise Session Director Configuration Guide.
Denial of Service Settings (DoS)
The Oracle Enterprise Session Border Controller (E-SBC) Denial of Service (DoS) protection functionality protects softswitches and gateways with overload protection, dynamic and static access control, and trusted device classification and separation at Layers 3-5. The E-SBC itself is protected from signaling and media overload, but more importantly the feature allows legitimate, trusted devices to continue receiving service even during an attack.
DoS protection prevents the Net-Net ESD host processor from being overwhelmed by a targeted DoS attack from the following:
• IP packets from an untrusted source as defined by provisioned or dynamic ACLs
• IP packets for unsupported or disabled protocols
• Nonconforming/malformed (garbage) packets to signaling ports
• Volume-based attack (flood) of valid or invalid call requests, signaling messages, and so on.
The Server Edition and VM Edition support of Denial of Service (DoS) protection differs from the Oracle Hardware
Platforms Edition because of the absence of Oracle network interface hardware. Consequently DoS protection is implemented in software and consumes CPU cycles when responding to attacks.
In addition, the Server Edition and VM Edition handle media packet fragments differently, processing them in the datapath rather than in the host application code. Protection against fragment attacks is still present by ensuring fragments are never kept more than 5 ms.
1. Click on Settings in the Main Menu. The following dialog box displays.
48
2. Click on Denial of service settings to expand the dialog box. The following displays.
Oracle
®
Enterprise Session Border Controller
Configuration
3. In the Maximum trusted packet rate field, enter the maximum trusted packet rate, in packets per seconds. Valid values are 20 to 200,000. Default is 50,000.
4. In the Maximum untrusted packet rate field, enter the maximum untrusted packet rate, in packets per seconds.
Valid values are 20 to 200,000. Default is 50,000.
5. In the Maximum ARP packet rate field, enter the maximum ARP packet rate, in packets per seconds. Valid values are 20 to 10,000. Default is 1000.
6. Click <OK>.
Communication Monitoring Probe Settings
Palladion is Oracle’s Communication Experience Manager. The manager is powered by the Palladion Mediation
Engine, a platform that collects SIP, DNS, ENUM, and protocol message traffic received from Palladion Probes. The mediation engine stores the traffic in an internal database, and analyzes aggregated data to provide comprehensive multi-level monitoring, troubleshooting, and interoperability information.
Palladion simplifies the operation of software-based Palladion probes by enabling the transmission of Internet
Protocol Flow Information Export (IPFIX) data to one or more Palladion Mediation Engines, possibly on different sub-nets. This enhancement requires a slight change in the ACLI hierarchy -- specifically, the removal of the network-interface parameter from the comm-monitor configuration object, and its transfer to the monitor-collector configuration object.
Note: The Palladion Communications Monitor Probe communicates over the media interface for signaling and Quality of Service (QoS) statistics using IPFIX. QoS reporting is done via Call Detail Records (CDR)
(accounting).
For more information about the Communications Monitoring Probe, see the Communications Monitoroing
Probe chapter in the Net-Net
®
Enterprise Session Director Configuration Guide.
To set Communication Monitoring Probe features on the Oracle Enterprise Session Border Controller:
1. Click on Settings in the Main Menu. The following dialog box displays.
Oracle
®
Enterprise Session Border Controller 49
Configuration
2. Click on Communications monitoring probe settings to expand the dialog box. The following displays.
50
3. In the Enable Monitoring field, place a check mark in the box to enable the Communication Monitor Probe to monitor the network. Uncheck the box to disable monitoring. Default is disabled.
Note: After checking the Enable monitoring box, all remaining fields are enabled for you to edit.
4. In the SBC group id field, enter an integer value to assign to the Net-Net ESD, that indicates its role as an information exporter. Valid values are 0 to 999999999. Defaul is zero (0).
5. In the Collector network interface field, enter the network interface and port whose traffic is exported to the
Palladion Mediation Engine. Valid values are alpha-numeric characters. Default is the Enterprise network interface and port (ENT:0).
6. In the Collector IP address field, enter the IP address monitored by a Palladion Mediation Engine for incoming
IPFIX traffic. Enter the address in dotted decimal format (0.0.0.0). Default is 1.1.1.1.
7. In the Collector port field, enter the port monitored by a Palladion Mediation Engine for incoming IPFIX traffic.
Valid values are 1025 to 65535. Default is 4739.
8. Click <OK>.
High Availability (HA) Settings
You can deploy the Oracle Enterprise Session Border Controller (E-SBC) in pairs to deliver high availability (HA).
Two E-SBCs operating in this way are called an HA node. Over the HA node, call state is shared, keeping sessions and calls from dropping in the event of a service disruption.
Oracle
®
Enterprise Session Border Controller
Configuration
TwoE-SBCs work together in an HA node, one in active mode and one in standby mode.
• The active E-SBC checks itself for internal process and IP connectivity issues. If it detects that it is experiencing certain faults, it hands over its role as the active system to the standby E-SBC in the node.
• The standby E-SBC is the backup system, fully synchronized with the active E-SBCsession status. The standby E-
SBC monitors the status of the active system so that, if needed, it can assume the active role without the active system having to instruct it to do so. If the standby system takes over the active role, it notifies network management using an SNMP trap.
To produce seamless switchovers from one E-SBC to the other, the HA node uses shared virtual MAC and virtual IP addresses for the media interfaces in a way that is similar to VRRP (virtual router redundancy protocol). Sharing addresses eliminates the possibility that the MAC and IPv4 address set on one E-SBC in an HA node will be a single point of failure. The standbyE-SBC sends ARP requests using a utility IPv4 address and its hard-coded MAC addresses to obtain Layer 2 bindings.
When there is a switchover, the standby E-SBC issues gratuitous ARP messages using the virtual MAC address, establishing that MAC on another physical port within the Ethernet switch. To the upstream router, the MAC and IP are still alive, meaning that existing sessions continue uninterrupted.
Within the HA node, the E-SBCs advertise their current state and health to one another in checkpointing messages; each system is apprised of the other’s status. Using Oracle’s HA protocol, the E-SBCs communicate with UDP messages sent out and received on the interfaces carrying "heartbeat" traffic between the active and standby devices.
The standby E-SBCassumes the active role when:
• It has not received a checkpoint message from the active E-SBC for a certain period of time.
• It determines that the active E-SBC’s health score has decreased to an unacceptable level.
• The active E-SBC relinquishes the active role.
To set HA features on the E-SBC:
1. Click Settings in the Main Menu. The following dialog box displays.
2. Click High availability settings to expand the dialog box. The following displays.
Oracle
®
Enterprise Session Border Controller 51
Configuration
3. In the Enable high availability field, place a check mark in the box to enable HA on the E-SBC.
Note: After checking the Enable high availability box, all remaining fields are enabled for you to edit.
4. In the Name of primary peer field, enter the name of the primary E-SBC peer. Valid values are alpha-numeric characters. Default is <primary peer name>.
Note: This field is automatically populated with the primary peer name that you entered when you ran the
Installation Wizard.
5. In the Name of secondary peer field, enter the name of the secondary system you are using for HA purposes to peer with the primary system. Valid values are alpha-numeric characters. Default is blank.
6. In the ENT phy interface virtual MAC field, enter the MAC address of the Enterprise’s physical interface on the
E-SBC.
Note: This field is automatically populated with the Enterprise’s MAC address that was entered when you ran the Installation Wizard.
7. In the SP phy interface virtual MAC field, enter the MAC address of the Service Provider’s physical interface on the E-SBC.
Note: This field is automatically populated with the Service Provider’s MAC address that was entered when you ran the Installation Wizard.
8. Click OK.
Packet Capture Settings (Advance Configuration only)
The Server and VM Edition support of packet tracing differs from the other Oracle platforms. When enabled, packets are captured that meet specific criteria. The packets are logged into a file in the /opt/traces directory in a PCAPformatted format as well as being displayed to the ACLI session from which the capture was executed.
You can enable or disable packet capture on the Oracle Enterprise Session Border Controller. The default filter uses port 5060 on the specified interface to capture both ingress and egress ICMP traffic. This does not support sending the captured packets off the box in RFC2003 IP in IP format. Therefore the capture-receiver element supported by the other platforms has been removed.
Advanced Settings
An Administrator can configure the following more advanced parameters:
• Enable packet capture
• Capture receiver network interface
• Capture receiver IP address
For more information on these settings, see Initiating Packet Capture in the Net-Net
®
Enterprise Session Director
Configuration Guide.
Host Routes
Host routes let you insert entries into the Oracle Enterprise Session Border Controller (E-SBC) routing table. These routes affect traffic that originates at the E-SBC host process. Host routes are used primarily for steering management traffic to the correct network.
52 Oracle
®
Enterprise Session Border Controller
Configuration
When traffic is destined for a network that is not explicitly defined on an E-SBC, the default gateway is used. If you try to route traffic to a specific destination that is not accessible through the default gateway, you need to add a host route. Host routes can be thought of as a default gateway override.
Certain SIP configurations require that the default gateway is located on a front media interface. In this scenario, if management applications are located on a network connected to a rear-interface network, you need to add a host route for management connectivity.
When source-based routing is used, the default gateway must exist on a front media interface. Host routes might be needed to reach management applications connected to a wancom port in this kind of situation.
Add a Host Route
Use the following procedure to add a host route to the configuration.
1. From the Main Menu, click Network > Host routes.
2. On the Host Route page, click Add.
3. In the Add Host Route dialog, do the following.
a) Dest network. Enter the IPv4 address of the destination network that this host route points toward. Enter the address in dotted decimal format. For example, 192.30.1.104.
b) Netmask. Select the netmask from the drop-down list associated with the destination network you entered for the Dest network parameter. For example, 255.255.128.0.
c) Gateway. Enter the gateway for which traffic destined for the address defined in the Dest network parameter, should use as its first hop. Enter the address in dotted decimal format. For example, 192.30.1.1.
d) Description. Enter a description for this host route. Valid values are alpha-numeric characters. For example,
Host Route A.
4. Click OK to save the host route.
The host route you created displays in the Host Routes table.
5. Click Close.
Security Configuration
Oracle Enterprise Session Border Controller (E-SBC) security is designed to provide security for VoIP and other multi-media services. E-SBC security includes access control, DoS attack, and overload protection, which help secure service and protect the network infrastructure. E-SBC security lets legitimate users place a call during attack conditions, protecting the service itself.
E-SBC security includes the Net-SAFE framework’s numerous features and architecture designs. Net-SAFE is a requirements framework for the components required to provide protection for the E-SBC, the service provider’s infrastructure equipment (proxies, gateways, call agents, application servers, and so on), and the service itself.
To configure security in your network, you can configure:
• Certificate record
• SDES Profile (for advanced Administrators only)
• TLS Policy
Adding a Certificate Record
Use the following procedure to add a certificate record to your configuration.
To add a certificate record:
1. From the Main Menu, click Security > Certificate record. The following displays.
Oracle
®
Enterprise Session Border Controller 53
Configuration
2. Click <Add>. The following dialog box displays.
54
3. In the Name field, enter a name for the certificate record. For example, acmepacket. Valid values are alphanumeric characters. Default is blank.
4. In the Country field, enter the name of the country where the certificate is being used. The default is US.
5. In the State field, enter the name of the state where the certificate is being used. The default is MA.
6. In the Locality field, enter the name of the locality within the state where the certificate is being used. Default is
Burlington.
7. In the Organization field, enter the name of the organization holding the certificate. The default is Engineering.
8. In the Unit field, enter the name of the unit that is holding the certificate within the organization. Valid values are alpha-numeric characters. Default is blank.
9. In the Common name field, enter a common name for the certificate record. Valid values are alpha-numeric characters. Default is blank.
10. In the Key size field, enter the size of the encrypted key for the certificate. The default is 1024. Valid values are:
• 512
• 1024
• 2048
11. In the Key usage list field, select the usage extensions you want to use with this certificate record. This parameter can be configured with multiple values. Default is a combination of digitalSignature and keyEncipherment.
Oracle
®
Enterprise Session Border Controller
To add additional usage extensions to the list, click <Add>. The following dialog box displays.
Configuration
In the Key usage list field, select an additional usage extension(s) to add the key usage list. Valid values are:
• dataEncipherment
• decipherOnly
• digitalSiggnature
• encipherOnly
• keyAgreement
• keyEncipherment
• nonRepudiation
Note: For more information on these usage extensions, see Chapter 18, the section, Key Usage
Control, of the Net-Net
®
Enterprise Session Director Configuration Guide.
To add the usage extension to the list and apply another one, click <Apply/Add Another>.
When you have completed adding usage extensions, click <OK>.
12. Click <OK> to save the certificate record. The certificate record you created displays in the Certificate Record table.
13. Click <Close>.
Advanced Settings
An Administrator can configure the following more advanced parameters:
• Alternate name
• Trusted state
• Extended key usage list
• Options
For more information about these settings, see Chapter 18, the section, “Configuring Certificates, in the Net-Net
®
Enterprise Session Director Configuration Guide.
Oracle
®
Enterprise Session Border Controller 55
Configuration
SDES Profile
Session Description Protocol Security Descriptions (SDES) for Media Streams is a way to negotiate the key for
Secure Real-time Transport Protocol (SRTP). It provides confidentiality, message authentication, and replay protection for RTP media and control traffic.
Adding a TLS Policy
Transport Layer Security (TLS) is a cryptographic protocol that provides communication security over the Internet.
TLS encrypts the segments of network connections at the Application Layer for the Transport Layer, using asymmetric cryptography for key exchange, symmetric encryption for confidentiality and message authentication codes for message integrity.
The TLS policy configuration holds the information required to run SIP over TLS. You can configure an end entity certificate and a trusted certification authority (CA) certificate(s) for a TLS policy. CA certificates are certificates that are issued by a CA to itself or to a second CA for the purpose of creating a defined relationship between the two CAs.
A certificate that is issued by a CA to itself is referred to as a trusted root certificate, because it is intended to establish a point of ultimate trust for a CA hierarchy. Once the trusted root has been established, it can be used to authorize subordinate CAs to issue certificates on its behalf.
For more information about TLS, see Chapter 18, the section, Transport Layer Security, in the Net-Net
®
Enterprise
Session Director Configuration Guide.
Use the following procedure to add a TLS policy to your configuration.
To add a TLS policy:
1. From the Main Menu, click Security > TLS policy. The following displays.
2. Click <Add>. The following dialog box displays.
56 Oracle
®
Enterprise Session Border Controller
Configuration
3. In the Name field, enter a name for the TLS profile. For example, TLS1. Valid values are alpha-numeric characters. Default is blank.
4. In the End entity certificate field, enter the name of the entity certification record. Valid values are alpha-numeric characters. Default is blank.
5. In the Trusted ca certificates field, select the names of the trusted CA certificate records.
To add a trusted CA certificate, click <Add>.
The following dialog box displays.
In the Trusted ca certificates field, select the certificate to trust for this TLS profile.
Note: You must add a certificate record to the Net-Net ESD configuration is order to select a value for this field. To add a certificate record, see Adding a Certificate Record.
To add the certificate to the list and apply another one, click <Apply/Add Another>.
When you have completed adding certificates, click <OK>. The following displays.
Oracle
®
Enterprise Session Border Controller 57
Configuration
6. Click <OK>. The profile you created displays in the TLS Profile table.
7. Click <Close>.
Advanced Settings
An Administrator can configure the following more advanced parameters:
• Cipher list
• Verify depth
• Mutual authenticate
• TLS version
• Options
• Certificate status check
• Certificate status profile list
• Enable/disable ignore dead responder
For more information about these settings, see Chapter 18, the section, Transport Layer Security, in the Net-Net
®
Enterprise Session Director Configuration Guide.
Management Settings
Management settings in Basic Mode allow you to configure the following features on the Oracle Enterprise Session
Border Controller:
• Accounting
• SNMP Community
• Trap Receiver
• Web Server
Accounting Configuration
The Oracle Enterprise Session Border Controller (E-SBC) supports RADIUS, an accounting, authentication, and authorization (AAA) system. RADIUS servers are responsible for receiving user connection requests, authenticating users, and returning all configuration information necessary for the client to deliver service to the user.
You can configure the E-SBC to send call accounting information to one or more RADIUS servers. This information can help you to see usage and Quality of Service (QoS) metrics, monitor traffic, and even troubleshoot your system.
For information about how to configure the E-SBC for RADIUS accounting, refer to the Oracle Communications
Session Border Controller Accounting Guide. The Accounting Guide contains all RADIUS information, as well as
information about:
• Accounting for SIP and H.323
• Local CDR storage on the E-SBC, including CSV file format settings
58 Oracle
®
Enterprise Session Border Controller
Configuration
• Ability to send CDRs via FTP to a RADIUS sever (the FTP push feature)
• Per-realm accounting control
• Configurable intermediate period
• RADIUS CDR redundancy
• RADIUS CDR content control
Configuring SNMP Community
A Simple Network Management Protocol (SNMP) community is a name (string) used as a password by the SNMP manager to communicate with the SNMP agent. The SNMP community string allows access to other devices’ statistics. It is used to support monitoring of network-attached devices for conditions that warrant administrative attention. If an SNMP community is configured, the Oracle Enterprise Session Border Controller sends the community string along with all SNMP requests.
Note: SNMP community strings are used only by devices which support SNMPv1 and SNMPv2c protocol.
SNMPv3 uses username/password authentication, along with an encryption key.
For more information about configuring an SNMP community, see Configuring SNMP, in the Net-Net
®
Enterprise
Session Director Configuration Guide.
To configure an SNMP community:
1. From the Main Menu, click Management > SNMP community. The following displays.
2. Click <Add>. The following dialog box displays.
Oracle
®
Enterprise Session Border Controller 59
Configuration
3. In the Community name field, enter an SNMP community name of an active community where this Oracle
Enterprise Session Border Controller can send or receive SNMP information. A community name value can also be used as a password to provide authentication, thereby limiting the NMSs that have access to this Net-Net system. With this field, the SNMP agent provides trivial authentication based on the community name that is exchanged in plain text SNMP messages. For example, public. Valid values are alpha-numeric characters. Default is blank.
4. In the Access mode field, enter the access level for all Network Management Systems (NMSs) defined within this
SNMP community. The access level determines the permissions that other NMS hosts can wield over this Oracle
Enterprise Session Border Controller. Default is READ-ONLY. Valid values are:
• READ-ONLY—allows GET requests.
• READ-WRITE—allows both GET and SET requests.
5. In the IP addresses field, select one or multiple IPv4 addresses that are valid within this SNMP community. These
IPv4 addresses correspond with the IPv4 address of NMS applications that monitor or configure this Oracle
Enterprise Session Border Controller. Include the IPv4 addresses of all servers where NMSs are installed.
To add an IP address, click <Add>. The following dialog box displays.
In the IP addresses field, enter an IPv4 address that is valid within this SNMP community.
To add the address to the list and apply another one, click <Apply/Add Another>.
When you have completed adding IP addresses, click <OK>. The following displays.
60 Oracle
®
Enterprise Session Border Controller
Configuration
6. Click <Close>.
Configure an SNMP Trap Receiver
You can define one or more SNMP trap receivers on an Oracle Enterprise Session Border Controller (E-SBC) for redundancy or to segregate alarms with different severity levels to individual trap receivers.
Before You Begin
• Confirm that SNMP is configured.
• Note the names of users who are allowed to receive secure traps.
• Confirm that the system displays Expert mode.
Oracle recommends that you configure each server with an NMS installed as a trap receiver on each E-SBC managed by an NMS. When configuring the trap-receiver element for use with Network Management Systems, Oracle recommends setting the filter-level parameter to All.
Procedure
1. From the Web GUI, click Configuration > System > Show advanced > trap-receiver.
2. On the trap receiver page, click Add.
3. On the Add trap receiver page, do the following:
Attributes
IP address
Instructions
Filter level
Community name
User list
Enter the IPv4 address and port number of an authorized NMS in dotted decimal format. Default:
0.0.0.0:162.
Select the filter level threshold for the severity level at which a trap is sent to the trap receiver.
Enter the SNMP community name to which this trap receiver belongs.
Create a list of users allowed to receive secure traps.
Click Add, enter the name of a user, and do one of the following:
• Click OK.
• Click Apply/Add another, add another user, and click OK. Repeat, as needed.
Note: If SNMPv3 is enabled on the E-SBC, but no users are listed for this field, a warning message is sent during the verify-config execution.
Oracle
®
Enterprise Session Border Controller 61
Configuration
4. Click OK.
5. Save and activate the configuration.
Configuring a Web Server
The Release E-C[xz]6.4.0 Web server is a software application that helps to deliver Web content that you can access through the Internet. The Web server runs the Enterprise application called the Web GUI.
Every Web server has an IP address and sometimes a domain name. For example, if you enter the URL http:// www.acmepacket.com/index.html in your browser, this sends a request to the Web server whose domain name is acmepacket.com. The server then fetches the page named index.html and sends it to your browser.
If you enter http://132.45.6.5, and this address has been configured by your Administrator to access the Web GUI, the server fetches the page and displays the Web GUI login to your browser.
This section provides a procedure for configuring the Web server in your network. For information about configuring the Web server using TLS, see Chapter 22 of the Net-Net
®
Enterprise Session Director Configuration Guide.
To configure the Web server:
1. From the Main Menu, click Management > Web server . The following displays.
62
2. In the State field, specify whether or not to enable the Web GUI. Default is enabled. A check mark indicates enabled, and a blank box indicates disabled.
3. In the Inactivity timeout field, enter the amount of time, in minutes, that the Web GUI must have remained inactive before it ends the Web session. For example, if this timeout value is set as 5, after 5 minutes of no activity, the Web session disconnects. Default is 10. Valid values are 0 to 20. Zero (0) disables this parameter.
Note: The following HTTP state and HTTPS state parameters may have already been set via the GUI installation wizard on your Oracle Enterprise Session Border Controller. You can edit these parameters if required.
4. In the HTTP state field, specify whether or not to enable HTTP for accessing the Web server. Default is enabled.
A check mark indicates enabled, and a blank box indicates disabled.
5. In the HTTPS state field, specify whether or not to enable HTTPS (secure connection) for accessing the Web server. Default is disabled. A check mark indicates enabled, and a blank box indicates disabled.
Oracle
®
Enterprise Session Border Controller
Configuration
6. In the TLS profile field, enter the Transport Layer Security (TLS) Protocol profile name to use with HTTPS. Valid values are alpha-numeric characters. Default is blank.
Note: To create a TLS profile, see Adding a TLS Policy. If you specify a TLS profile, and HTTP is enabled, the Oracle Enterprise Session Border Controller checks against the TLS profile table for a match.
If there is no match, the applicable errors display during the verification of the configuration.
7. Click <OK>.
Advanced Settings
An Administrator can configure the following more advanced parameters:
• HTTP Port
• HTTPS Port
For more information about these settings, see Appendix D, Manual Web Server Configuration in the Net-Net
®
Enterprise Session Director Configuration Guide.
Configure Advanced Routing
After adding a one-way or two-way local policy route, you can configure the routes with more advanced parameters from the Web GUI.
In the Advanced Routing dialog, configure the advanced routing parameters that you want and add the corresponding
LDAP configuration.
1. Click the Advanced Routing icon on the Oracle Enterprise Session Border Controller.
2. In the local-routing-config dialog, click Add and Show Advanced.
3. In the Add local routing config dialog, do the following:
• Name. Enter a unique name for the local route table. No spaces.
• File name. Enter or select the name for the file from which the database corresponding to this local route table will be created. You should use the .gz format, and the file should be placed in the /code/lrt/ directory.
• Prefix length. Enter a number from 0-999999999.
• String lookup. Optional. Selection.
• Re-target requests. Optional selection.
• Match mode. Select a mode from the drop down list.
4. Click OK.
5. Click Close.
Configure LDAP.
Ldap-config Tab
1. In the Name field, enter a name to assign to this LDAP configuration. This is a unique identifier. Valid values are alpha-numeric characters. Default is blank.
2. In the State field, specify whether or not to enable the operational state of the LDAP configuration. When the state is disabled, ESD does not attempt to establish any connection with the corresponding LDAP Server(s). Default is enabled.
3. In the ldap-servers field, click <Add> and enter the IP address(es) and optionally the port number(s) for each
LDAP Server(s) you want to add to the LDAP configuration. When more than one server is specified, each server address should be separated by a space and the list enclosed within parentheses. The first server listed is considered the primary LDAP Server, and the remaining servers are considered the secondary LDAP Servers. The
HUNT strategy is used to determine the active LDAP Server (where the ESD selects the first LDAP Server; if unreachable, it selects the second LDAP Server; it that is unreachable, it selects the third LDAP Server, etc.).
Default ports used are 389 (for LDAP over TCP) and 636 (LDAP over TLS). IP Address must be entered in dotted decimal format (0.0.0.0). Default is blank.
4. In the SIP Interface field, select the SIP interface from the list that issues an LDAP query. This list contains all of the current SIP interfaces configured on the Oracle Enterprise Session Border Controller. Default values are:
Oracle
®
Enterprise Session Border Controller 63
Configuration
64
• Default ENT - Default Enterprise SIP interface
• Default SP - Default Service Provider SIP interface
5. In the Authentication mode field, select the authentication mode to use in the LDAP bind request. Default is
Simple. Valid value is:
• Simple (default) - No specific password encryption is done when sending the bind request. You can use an
LDAPS connection with the LDAP Server to maintain security (see ldap-sec-type).
6. In the Username field, enter the username that the LDAP bind request uses for authentication before access is granted to the LDAP Server. Valid values are alpha-numeric characters. Default is blank.
7. In the Password field, click <Set>. Then enter the password to be paired with the username attribute, that the
LDAP bind request uses for authentication before access is granted to the LDAP Server. Valid values are alphanumeric characters. Default is blank.
8. In the Confirm password field, re-enter the password you specified in Step 7, and click <OK>.
9. In the Ldap search base field, enter the base Directory Number you can use for LDAP search requests. Valid values are alpha-numeric characters. Default is blank. For example, cn=users, dc=englab, dc=acmepacket, dc=com.
Configure LDAP-transactions
You use the LDAP transactions to configure the application transaction type for LDAP, determine route priority in the route list, and configure the LDAP configuration attributes. You configure this object for LDAP search queries in call routing.
To configure LDAP transactions:
1. In the ldap-transactions sections, click <Add>.
2. In the App trans type field, select the application transaction type to use for LDAP. This value allows the Oracle
Enterprise Session Border Controller (E-SBC) to add call routing updates to the Active Directory. Default is adcall-routing. Valid value is:
• ad-call-routing (default)
3. In the Route mode field, select the route priority that the E-SBC uses in the route list. This parameter determines which routes are created, and the priority of those routes within the route list. Default is exact-match-only. Valid values are:
• exact-match-only (default) - If there is an exact match between the dialed telephone number and an LDAP attribute value in the search response entry, a route is created corresponding to that LDAP attribute. If there is an exact match on multiple attributes, the ordering of LDAP attributes in the LDAP configuration determines the priority for each route. For example, an enterprise that uses the same phone number for both Lync and IP-
PBX phones, if the msRTCSIP-Line attribute is configured first, the corresponding next hop (Lync Server) would be used to create the first route in the route list.
• attribute-order-only - The ordering of LDAP attributes in the LDAP configuration determines the priority for each route. So if the msRTCSIP-Line attribute is configured first, the corresponding next hop (Lync Server) would be used to create the first route in the route list. If there is a valid value present in the search response entry for a LDAP attribute, a route is created corresponding to that LDAP attribute. Note: The LDAP attribute must have a valid value in the response; a match is not necessary for that attribute. If an entry is returned in the search response, there must be a match on at least one other attribute. For example, the dialed telephone number could be +17813284392 (IP-PBX Phone#), and the msRTCSIP-Line in the response could be
+17814307069 (Lync phone#). A route is created for the Lync phone#, even though the dialed telephone number is the PBX Phone#.
• exact-match-first - If there is an exact match between the dialed telephone number and an LDAP attribute value in the search response entry, the corresponding route gets the highest priority in the route list. For the rest of the routes, the ordering of LDAP attributes in the LDAP configuration determines the priority for each route. So if the msRTCSIP-Line attribute is configured first, the corresponding next hop (Lync Server) would be used to create the second highest priority route in the route list. If there is a valid value present in the search
Oracle
®
Enterprise Session Border Controller
Configuration
response entry for an LDAP attribute, a route is created corresponding to that LDAP attribute. Note: The
LDAP attribute must have a valid value in the response; a match is not necessary for that attribute. If an entry is returned in the search response, there must be a match on at least one other attribute. For example, the dialed telephone number could be +17813284392 (IP-PBX Phone#), and the msRTCSIP-Line in the response could be +17814307069 (Lync phone#). A route is created for the Lync phone#, even though the dialed telephone number is the PBX Phone#.
Configure LDAP-config Attributes
You use the LDAP config attributes object to configure the Active Directory attribute name, next hop for routing SIP requests, the realm for the next hop, a regular expression pattern, and a format for the attribute value. You configure this object for LDAP search queries in the Active Directory.
To configure LDAP config attributes:
1. In the ldap-cfg-attributes section, click <Add>.
2. In the Name field, enter the Active Directory attribute name. Default is blank. Valid values are alpha-numeric characters. Some examples of Active Directory attribute names are:
• ipPhone and msRTCSIP-Line for Lync phone number
• telephoneNumber for IP PBX phone number
• mobile for Mobile phone number
3. In the Next hop field, enter the Active Directory’s next hop when routing SIP requests. Default is blank. Valid values are alpha-numeric characters. Some examples of the Active Directory’s next hop are:
• SAG (Session Agent Group) name, specified by entering an sag: prefix
• SA (Sesson Agent) name
• IP Address
4. In the SIP interface field, select the name of the SIP interface associated with the next hop. This value determines the network interface to which to route the SIP request. This list contains all of the current SIP interfaces configured on the Oracle Enterprise Session Border Controller. Default values are:
• Default ENT - Default Enterprise SIP interface
• Default SP - Default Service Provider SIP interface
5. In the Extraction regex field, enter the regular expression pattern used to break down the string of digits in the phone number extracted from the request URI of the SIP request. The variables extracted from the phone number can be used in the attribute-value-format parameter. The default regex is "^\+?1?(\d{2})(\d{3})(\d{4})$". This value assumes that the phone number is a North American phone number specified in the E.164 format. It extracts three variables from the phone number:
• $1 is the area code
• $2 and $3 are the next 3 and 4 digits in the phone number
Valid values are alpha-numeric characters.
6. In the Value format field, enter the format for the attribute value. These format values are extracted from the phone number using the extraction-regex parameter. The default parameter is "tel:+1$1$2$3". This value assumes that the phone number is a North American phone number specified in the E.164 format, and it recreates the phone number in E.164 format.
In addition to the E.164 format, Oracle's Active Directory uses other formats as well to store the phone numbers.
You can customize the value specified for this parameter to enable successful queries for phone numbers in other formats.
Valid values are alpha-numeric characters.
7. Click <OK>.
8. Save and activate the configuration.
Oracle
®
Enterprise Session Border Controller 65
Configuration
Additional Features
Using the Web GUI, an Administrator can perform configuration on other features on the Oracle Enterprise Session
Border Controller. These features include:
• Configuring Media Profile
• Configuring Translation Rules
• Configuring SIP Features
• Configuring SIP Manipulations (including Multipurpose Internet Mail Extensions (MIME), ISDN User Part
(ISUP) and Session Description Protocol (SDP) rules)
• Adding an SPL
This section provides procedures for configuring each of these features.
Configure Media Profile
A Media Profile is a group of parameters that the Oracle Enterprise Session Border Controller uses as a rule when sending/receiving media over the network. You can configure the following parameters for a Media Profile:
• Name
• Subname
• Payload type
• Transport
1. From the Main Menu, click Other > Media profile
2. Click <Add>.
3. In the Name field, enter the name for this media profile. For example, you might set the name of the media profile as PCMU. Valid values are alpha-numeric characters. Default is blank.
4. In the Subname field, enter the subname for this media profile. Valid values are alpha-numeric characters. You must use a combination of alpha and numeric characters. Default is blank.
5. In the Payload type field, enter the payload type number that corresponds to the encoding name you entered in
Step 3. This value identifies the format in the SDP media lines. Valid values are alpha-numeric characters. Default is blank.
Note: The Payload type value must be numeric if you use the RTP/AVP transport method.
The following is a table of standard audio and visual payload encodings defined in H. Schulzrinne, GND Fokus,
RTP Profile for Audio and Visual Conferences with Minimal Control, RFC 1890, and in the RTP Parameters document in IANA’s Directory of Generally Assigned Numbers.
Payload Type
6
7
4
5
8
9
2
3
0
1
Encoding Name
PCMU
1016
G721
GSM
G723
DVI4
DVI4
LPC
PCMA
G722
Audio (A)/Visual (V)
A
A
A
A
A
A
A
A
A
A
Clock Rate (Hz)
8000
8000
8000
8000
8000
8000
16000
8000
8000
8000
66 Oracle
®
Enterprise Session Border Controller
Payload Type
28
29
30
31
32
33
34
35-71
72-76
24
25
26
27 dyn dyn dyn dyn
21
22
23 dyn
17
18
19
20
13
14
15
16
10
11
12
Encoding Name
77-95
96-127
Oracle
®
Enterprise Session Border Controller
Audio (A)/Visual (V)
L16
L16
QCELP reserved
MPA
G728
DVI4
DVI4
G729 reserved unassigned unassigned unassigned unassigned
GSM-HR
GSM-EFR
L8
RED
VDVI unassigned
CelB
JPEG unassigned nv unassigned unassigned
H261
MPV
MP2T
H263 unassigned reserved for RTCP conflict avoidance unassigned dynamic
?
?
V
?
V
AV
N/A
V
V
V
V
V
V
V
V
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
90000
8000
11025
22050
8000
Configuration
Clock Rate (Hz)
44100
44100
8000
8000
8000 var.
var.
90000
90000
90000
90000
90000
90000
90000
N/A
67
Configuration
Payload Type Encoding Name Audio (A)/Visual (V) Clock Rate (Hz)
dyn dyn dyn
BT656
H263-1998
MP1S
V
V
V
90000
90000
90000 dyn dyn
MP2P
BMPEG
V
V
90000
90000
6. In the Transport field, enter the type of transport protocol to specify in the Media Profile. Default is RTP/AVP.
Valid values are:
• RTP/AVP
• UDP
7. Click <OK>.
8. Click <Close>.
Advanced Settings
An Administrator can configure the following more advanced parameters:
• Media type
• Required bandwidth
• Frames per packet
• Parameters
Configure Translation Rules
Oracle Enterprise Session Border Controller number translation is used to change a layer-5 endpoint name according to prescribed rules. Number translations can be performed on both the inbound and the outbound call legs independently, before and after routing occurs.
Number translation is used for SIP, H.323, and SIP/H.323 interworking configurations. Number translation takes place twice for both H.323 and SIP calls. The first number translation is applied to the incoming leg of the call, before the outgoing route is selected. The second number translation is applied to the outgoing leg of the call after the outgoing route is selected.
Number translation can be used to strip address prefixes added by external gateways. It can also be used to add a string tag to an address in order to implement a local policy routing scheme, and then remove the tag upon egress from the Net- Net ESD. The most common use of number translation is to add or remove a “1” or a + from a phone number sent from or addressed to a device.
To configure a Translation Rules:
1. From the Main Menu, click Other > Translation rules.
The Translation rules table displays the default translation rules for the Oracle Enterprise Session Border
Controller. You can select a rule to edit or add a new rule as required.
2. To add new rules, click <Add>.
3. In the Id field, enter a descriptive ID name for this translation rule. Valid values are alpha-numeric characters.
Default is blank.
4. In the Type field, select the type of translation rule you want to configure. Default is none. Valid values are:
• add—Adds a character or string of characters to the address
• delete—Deletes a character or string of characters from the address
• none—Translation rule is disabled
• replace—Replaces a character or string of characters within the address
68 Oracle
®
Enterprise Session Border Controller
Configuration
5. In the Add string field, enter the string to be added during address translation to the original address. The value in this field should always be a real value; i.e., this field should not be populated with at-signs (@) or dollar-signs
($). Valid values are alpha-numeric characters. Default is blank.
6. In the Delete string field, enter the string to be deleted from the original address during address translation.
Unspecified characters are denoted by the at-sign symbol (@).Valid values are alpha-numeric characters. Default is blank.
Note: The @ character only works if the type parameter is set to delete. This parameter supports wildcard characters or digits only. For example, valid entries are: delete-string=@@@@@, or deletestring=123456. An invalid entry is delete-string=123@@@.
When the type is set to replace, this value is used in conjunction with the add-string value. The value specified in the delete-string field is deleted and the value specified in the add-string field is inserted. If no value is specified in the delete-string parameter and the type field is set to replace, then nothing is inserted into the address.
7. Click <OK>.
8. Click <Close>.
Advanced Settings
An Administrator can configure the following more advanced parameters:
• Add Index
• Delete Index
Configure SIP Features
SIP extensions that require specific behavior by UAs or proxies are identified by option tags. Option tags are unique identifiers used to designate new options (for example, extensions) in SIP. These option tags appear in the Require,
Proxy-Require, and Supported headers of SIP messages.
Option tags are compatibility mechanisms for extensions and are used in header fields such as Require, Supported,
Proxy-Require, and Unsupported in support of SIP.
The option tag itself is a string that is associated with a particular SIP option (i.e., an extension). It identifies this option to SIP endpoints.
You configure the SIP feature element to define option tag names and their treatment by the Oracle Enterprise
Session Border Controller when the option tag appears in a Supported header, a Require header, and a Proxy-Require header. If an option tag is encountered that is not configured as a SIP feature, the default treatments apply. You only need to configure option tag handling in the SIP feature element when non-default treatment is required.
For more information about configuring a SIP Options Tag, see the section, SIP Options Tag Handling in the Net-
Net
®
Enterprise Session Director Configuration Guide.
To configure a SIP Options Tag:
1. From the Main Menu, click Other > SIP features.
2. Click <Add>.
3. In the Name field, enter a name for the option tag that appears in the Require, Supported, or Proxy-Require headers of inbound and outbound SIP messages. You must enter a unique value. Valid values are alpha-numeric characters. Default is blank.
Note: Valid option tags are registered with the IANA Protocol Number Assignment Services under
Session Initiation Protocol Parameters. Because option tags are not registered until the SIP extension is published as a RFC, there might be implementations based on Internet-Drafts or proprietary implementations that use unregistered option tags.
4. In the SIP interface field, select the SIP interface for which to apply this SIP feature. Default is blank. Valid values are:
• DefaultENT—Default Enterprise SIP interface.
• DefaultSP—Default Service Provider SIP interface.
Oracle
®
Enterprise Session Border Controller 69
Configuration
Note: The drop-down list for the SIP interface field may contain other SIP interfaces if they have been configured in your network.
5. In the Require mode inbound field, select the require proxy mode to define how the option tag is treated when encountered in an incoming SIP message’s Proxy-Require header. Default is reject. Valid values are:
• pass—Indicates the Back-to-Back User Agent (B2BUA) should include the tag in the corresponding outgoing message.
• reject—Indicates the B2BUA should reject the request with a 420 (Bad Extension) response. The option tag is included in an Unsupported header in the reject response.
6. In the Require mode outbound field, select the require mode to define how the option tag is treated when it is encountered in an outbound SIP message’s Require header. The default value is reject. Valid values are:
• pass—Indicates the B2BUA should include the tag.
• reject—Indicates the B2BUA should reject the request with a 420 (Bad Extension) response. The option tag is included in an Unsupported header in the reject response.
7. Click <OK>.
8. Click <Close>.
Advanced Settings
An Administrator can configure the following more advanced parameters:
• Support mode inbound
• Proxy require mode inbound
• Support mode outbound
• Proxy required mode outbound
Configure SIP Manipulations
SIP Header Manipulation provides the flexibility to add, remove, or modify any attribute in a SIP message on the
Oracle Enterprise Session Border Controller (E-SBC). The most common reason for doing this is to fix an incompatibility problem between two SIP endpoints. This could range from anything such as Softswitch/PSTN incompatibility or an issue between two different IP PBX platforms in a multi-site Enterprise where calls between them fail due to issues in the SIP messaging.
The SIP header and parameter manipulation feature allows you to add, modify, and delete SIP headers and parts of
SIP headers called SIP header elements. SIP header elements are the different subparts of the header, such as the header value, header parameter, URI parameter and so on (excluding the header name).
To enable the SIP header and parameter manipulation functionality, you create header manipulation rule sets in which you specify header manipulation rules, as well as optional header element rules that operate on specified header elements. You then apply the header manipulation ruleset as inbound or outbound for a session agent or SIP interface.
Header manipulation rules operate on the header you specify when you configure the rule. A header manipulation rule can also be configured with a list of element rules, each of which would specify the actions you want performed for a given element of this header.
Header element rules perform operations on the elements of a header. Header elements include all subparts of a header; excluding the header name. For example, header value, header parameter, URI parameter, and so on.
1. From the Main Menu, click Other > SIP manipulation.
The SIP manipulation table displays the default header manipulation rules for the E-SBC. You can select a rule to edit or add a new rule as required.
2. To add a new rule, click <Add>. The following dialog box displays.
3. In the Name field, enter the name of the header to which this rule applies. The name you enter here must match a header name. This is a case-insensitive string that is compared to the header name for matching. You need to create a rule using the long form of the header name and a rule using the compact form of the header name. Valid values are alpha-numeric characters. Default is blank.
70 Oracle
®
Enterprise Session Border Controller
Configuration
Note: The Request-URI header is identified as request-uri.
4. In the Description field, enter a description for this header manipulation rule. Valid values are alpha-numeric characters. Default is blank.
Specify Split Headers
In the Split headers field, enter the elements of the message header that you want the Oracle Enterprise Session
Border Controller to split.
Click <Add>.
In the Split headers field, enter the header element you want to split. For example, $LOCAL_IP.
To add the element to the list and apply another one, click <Apply/Add Another>.
When you have completed adding header elements to the Split header list, click <OK>.
Specify Join Headers
In the Join headers field, enter the header element you want the Oracle Enterprise Session Border Controller to join.
Click <Add>. The following displays.
In the Join headers field, enter the header element you want to join. For example, $REMOTE_IP.
To add the element to the list and apply another one, click <Apply/Add Another>.
When you have completed adding header elements to the Join header list, click <OK>. The following displays.
Specify Configuration Rule
1. In the cfgRules field, enter the rule to use in the Oracle Enterprise Session Border Controller configuration. These rules use the “Split” and Join headers you specified above.
2. Click <Add>, and select header-rule from the drop-down list. The following displays.
Oracle
®
Enterprise Session Border Controller 71
Configuration
72
3. In the Name field, enter a name you want to use for this rule set. Valid values are alpha-numeric characters.
Default is blank.
4. In the Header name field, enter the name of the header to which this rule applies. The name you enter here must match a header name. This is a case-insensitive string that is compared to the header name for matching. You need to create a rule using the long form of the header name and a rule using the compact form of the header name.
Valid values are alpha-numeric characters. Default is blank.
Note: The Request-URI header is identified as request-uri.
5. In the Action field, select an action you want applied to the header specified in the Name parameter. Default is none. Valid values are:
• add—Adds a new header, if that header does not already exist.
• delete—Deletes the header, if it exists.
• find-replace-all—Finds all matching headers and replaces it with the header you specified for “Split” and Join.
• log—Logs the header.
• manipulate—Manipulates the elements of this header to the element rules configured.
• monitor—Monitors the header.
• store—Stores the header.
• none—(default) No action is taken.
• reject—Rejects the header.
• sip-manip—Manipulates the SIP elements of this header to the element rules configured.
• store—Stores the header.
6. In the Comparison type field, select the way that you want SIP headers to be compared. This choice dictates how the Oracle Enterprise Session Border Controller processes the match rules against the SIP header. Default is casesensitive. Valid values are:
• boolean—Header is compared to header rule and must match exactly or it is rejected.
Oracle
®
Enterprise Session Border Controller
Configuration
• case-insensitive—Header is compared to header rule regardless of the case of the header.
• case-sensitive—(default) Header is compared to the header rule and case must be exactly the same or it is rejected.
• pattern-rule—Header is compared to the header rule and the pattern must be exactly the same or it is rejected.
• refer-case-insensitive—Header is compared to the header rule regardless of the case in a REFER message.
• refer-case-sensitive—Header is compared to the header rule and the case must be exactly the same as in the
REFER message or it is rejected.
7. In the Msg type field, select the message type to which this header rule applies. Default is any. Valid values are:
• any—(default) Requests, replies, and out-of-dialog messages
• out-of-dialog—Out of dialog messages only.
• reply—Reply messages only
• request—Request messages only
8. In the Methods field, specify the SIP method names to which you want to apply this header rule.
Click <Add>. The following diplays.
In the Methods field, enter SIP method names to which you want to apply this header rule. For example, INVITE,
ACK, BYE.
Note: This field is empty by default. If you leave the method field empty, the header rule applies to all methods.
To add the method to the list and apply another one, click <Apply/Add Another>.
When you have completed adding methods, click <OK>. The following displays.
9. In the Match value field, enter the value you want to match against the element value for an action to be performed.
10. In the New value field, enter the value for a new element or to replace a value for an existing element. You can enter an expression that includes a combination of absolute values, pre-defined parameters, and operators.
• Absolute values - use double quotes for clarity. You must escape all double quotes and back slashes that are part of an absolute value, and enclose the absolute value in double quotes.
For example: sip:”+$TRUNK_GROUP+”.$TRUNK_GROUP_CONTEXT
• Pre-defined parameters always start with a $. The following table describes the pre-defined parameters.
Pre-defined Parameters Table
Oracle
®
Enterprise Session Border Controller 73
Configuration
Parameter
$ORIGINAL
$LOCAL_IP
$REMOTE_IP
$REMOTE_VIA_HOST
$TRUNK_GROUP
$TRUNK_GROUP_CONTEXT
Description
Original value of the element is used.
IP address of the SIP interface on which the message was received for inbound manipulation; or sent on for outbound manipulation.
IP address the message was received from for inbound manipulation; or being sent to for outbound manipulation.
Host from the top Via header of the message is used.
Trunk group is used.
Trunk group context is used.
The following table describes the Operators.
Operators Table
Operator
+
Description
Append the value to the end. For example: acme”+”packet generates acmepacket
+^
-
Prepends the value. For example: acme”+^”packet generates packetacme
Subtract at the end. For example:
112311”-”11 generates 1123
-^ Subtract at the beginning. For example:
112311”-^”11 generates 2311
Examples of entries for the new-value field.
$ORIGINAL+acme
$ORIGINAL+”my name is john”
$ORIGINAL+”my name is \”john\””
$ORIGINAL-^781+^617
Specify Element Rule
Header element rules perform operations on the elements of a header. Header elements include all subparts of a header; excluding the header name. For example, header value, header parameter, URI parameter, and so on.
1. In the cfgRules field, click <Add>, and then select element-rule from the drop-down list. This allows you to define the element rules you want to use to be performed on the elements of the header specified by the header rule. The following dialog box displays.
74 Oracle
®
Enterprise Session Border Controller
Configuration
2. In the Name field, enter the name of the element to which this rule applies. Valid values are alpha-numeric characters. Default is blank.
3. In the Parameter name field, enter the parameter name to which this rule applies. The parameter name depends on the element name you entered in step 2. For uri-param, uri-user-param, and header-param it is the parameter name to be added, replaced, or deleted. For all other types, it serves to identify the element rule and any name can be used. Valid values are alpha-numeric characters. Default is blank.
4. In the Type field, select the type of element on which to perform the action. Default is blank. Valid values are:
• header-param—Perform the action on the parameter portion of the header.
• header-param-name—Perform the action on the header parameter name.
• header-value—Perform the action on the header value.
• mime—Perform the action on Multipurpose Internet Mail Extensions (MIME).
• reason-phrase—Perform the action on reason phrases.
• status-code—Perform the action on status codes.
• teluri-param—Perform the action on a SIP telephone Uniform Resource Identifier (URI).
• uri-display—Perform the action on the display of the SIP URI.
• uri-header—Perform the action on a header included in a request constructed from the URI.
• uri-header-name—Perform the action on a SIP URI header name.
• uri-host—Perform the action on a Host portion of the SIP URI.
• uri-param—Perform the action on the parameter included in the SIP URI.
• uri-param-name—Perform the action on the name parameter of the SIP URI.
• uri-phone-number-only—Perform the action on a SIP URI phone number only.
• uri-port—Perform the action on the port number portion of the SIP URI.
• uri-user—Perform the action on the user portion of the SIP URI.
• uri-user-only—Perform the action on the user portion only of the SIP URI.
• uri-user-param—Perform the action on the user parameter of the SIP URI.
5. In the Action field, enter the action you want applied to the element specified in the Name parameter, if there is a match value. Default is none. Valid values are:
• add—Adds a new element, if that element does not already exist.
• delete-element—Deletes the element, if it exists.
• delete-header—Delete the header where this element exists.
Oracle
®
Enterprise Session Border Controller 75
Configuration
• find-replace-all—Finds all matching elements and replaces it with the element you specified in this procedure.
• log—Logs the element.
• none—(default) No action is taken.
• reject—Rejects the element.
• replace—Replaces the element
• sip-manip—Manipulates the SIP elements of this header to the element rules configured.
• store—Stores the element.
6. In the Match val type field, select the type of value that needs to be matched to the match-field entry for the action to be performed. Default is any. Valid values are:
• any—(default) Element value in the SIP message is compared with the match-value field entry. If the matchvalue field is empty, all values are considered a match.
• fqdn—Element value in the SIP message must be a valid FQDN to be compared to the match-value field entry.
If the match-value field is empty, any valid FQDN is considered a match. If the element value is not a valid
FQDN, it is not considered a match.
• ip—Element value in the SIP message must be a valid IP address to be compared to the match-value field entry. If the match-value field is empty, any valid IP address is considered a match. If the element value is not a valid IP address, it is not considered a match.
7. In the Comparison type field, select the way that you want SIP elements to be compared. This choice dictates how the Oracle Enterprise Session Border Controller processes the match rules against the SIP header. Default is casesensitive. Valid values are:
• boolean—Header is compared to header rule and must match exactly or it is rejected.
• case-insensitive—Header is compared to header rule regardless of the case of the header.
• case-sensitive—(default) Header is compared to the header rule and case must be exactly the same or it is rejected.
• pattern-rule—Header is compared to the header rule and the pattern must be exactly the same or it is rejected.
• refer-case-insensitive—Header is compared to the header rule regardless of the case in a REFER message.
• refer-case-sensitive—Header is compared to the header rule and the case must be exactly the same as in the
REFER message or it is rejected.
8. In the Match value field, enter the value you want to match against the element value for an action to be performed.
9. In the New value field, enter the value for a new element or to replace a value for an existing element. You can enter an expression that includes a combination of absolute values, pre-defined parameters, and operators.
• Absolute values - use double quotes for clarity. You must escape all double quotes and back slashes that are part of an absolute value, and enclose the absolute value in double quotes.
For example: sip:”+$TRUNK_GROUP+”.$TRUNK_GROUP_CONTEXT
• Pre-defined parameters always start with a $. For valid values, see the Pre-defined Parameters Table.
• Operators parameters - For valid values, see the Operators Table.
Examples of entries for the new-value field.
$ORIGINAL+acme
$ORIGINAL+”my name is john”
$ORIGINAL+”my name is \”john\””
$ORIGINAL-^781+^617
10. Click <OK>. The Header Rule dialog box displays.
76 Oracle
®
Enterprise Session Border Controller
Configuration
11. Click <Close>.
Configuring MIME Rules
Using the SIP Head Manipulation Rule (HMR) feature set, you can manipulate Multipurpose Internet Mail
Extensions (MIME) types in SIP message bodies. While you can manipulate the body of SIP messages or a specific content type using other iterations of SIP HMR, this version gives you the power to change the MIME attachment of a specific type within the body by using regular expressions.
To achieve this, you use the find-replace-all action type, which enables the search for a particular string and the replacement of all matches for that type. Although you use find-replace-all to manipulate MIME attachments, it can also be used to achieve other goals in SIP HMR. Note that using find-replace-all might consume more system resources than other HMR types. Therefore this powerful action type should only be used when another type cannot perform the type of manipulation you require.
For more information about configuring MIME rules, see the section, MIME Support in the Net-Net
®
Session Director Configuration Guide.
Enterprise
To configure MIME rules:
1. After adding a new SIP manipulation rule, go to the SIP Manipulation dialog box.
Oracle
®
Enterprise Session Border Controller 77
Configuration
2. In the cfgrules field, click <Add> and select mime-rules from the drop-down list. This allows you to specify mime rules for the header rules you configured. The following dialog box displays.
78 Oracle
®
Enterprise Session Border Controller
Configuration
3. In the Name field, enter a name you want to use for this MIME rule. Valid values are alpha-numeric characters.
Default is blank.
4. In the Content type field, enter the content type of the MIME. For example, application/sipfrag or application/sdp.
This value is the content type that the Oracle Enterprise Session Border Controller looks for in the MIME. Valid values are alpha-numeric characters. Default is blank.
5. In the Msg type field, specify the type of message to which this MIME rule applies. Default is any. Valid values are:
• any—Both Requests and Reply messages
• out-of-dialog—Out of dialog messages only.
• reply—Reply messages only
• request—Request messages only
6. In the Methods field, specify the SIP method names to which you want to apply this MIME rule.
Click <Add>. The following diplays.
In the Methods field, enter SIP method names to which you want to apply this MIME rule. For example, INVITE,
ACK, BYE.
Note: This field is empty by default. If you leave the method field empty, the MIME rule applies to all methods.
To add the method to the list and apply another one, click <Apply/Add Another>.
Oracle
®
Enterprise Session Border Controller 79
Configuration
When you have completed adding methods, click <OK>. The following displays.
80
7. In the Format field, select the format to apply to this MIME rule. Default is ascii-string. Valid values are:
• ascii-string - a character-encoding scheme that represents text (128 ASCII codes, 7 bits)
• binary-ascii - encoding scheme where each byte of an ASCII character is used; can use up to 256 bit patterns
• hex-ascii - encoding scheme that uses a string of numbers (no spaces) to represent each ASCII character.
8. In the Action field, enter the action you want applied to the MIME rule specified in the Name parameter, if there is a match value. Default is none. Valid values are:
• add—Adds a new element, if that element does not already exist.
• delete—Deletes the element, if it exists.
• find-replace-all—Finds all matching elements and replaces it with the element you specified in this procedure.
• log—Logs the element.
• manipulate—Manipulates the elements of this header to the element rules configured.
• monitor—Monitors the header for this element.
• none—(default) No action is taken.
• reject—Rejects the element.
• sip-manip—Manipulates the SIP elements of this header to the element rules configured.
• store—Stores the element.
9. In the Comparison type field, select the way that you want the MIME to be compared with this MIME rule. This choice dictates how the Oracle Enterprise Session Border Controller processes the match rules against the MIME.
Default is case-sensitive. Valid values are:
• boolean—Header is compared to MIME rule and must match exactly or it is rejected.
• case-insensitive—Header is compared to MIME rule regardless of the case of the header.
• case-sensitive—(default) Header is compared to the MIME rule and case must be exactly the same or it is rejected.
• pattern-rule—Header is compared to the MIME rule and the pattern must be exactly the same or it is rejected.
• refer-case-insensitive—Header is compared to the header rule regardless of the case in a REFER message.
• refer-case-sensitive—Header is compared to the header rule and the case must be exactly the same as in the
REFER message or it is rejected.
10. In the Match value field, enter the value you want to match against the element value for an action to be performed.
11. In the New value field, enter the value for a new element or to replace a value for an existing element. You can enter an expression that includes a combination of absolute values, pre-defined parameters, and operators.
• Absolute values - use double quotes for clarity. You must escape all double quotes and back slashes that are part of an absolute value, and enclose the absolute value in double quotes.
For example: sip:”+$TRUNK_GROUP+”.$TRUNK_GROUP_CONTEXT
• Pre-defined parameters always start with a $. For valid values, see the Pre-defined Parameters Table.
• Operators parameters - For valid values, see the Operators Table.
Examples of entries for the new-value field.
$ORIGINAL+acme
$ORIGINAL+”my name is john”
Oracle
®
Enterprise Session Border Controller
Configuration
$ORIGINAL+”my name is \”john\””
$ORIGINAL-^781+^617
12. Click <OK>. The MIME Rule dialog box displays.
13. Click <OK>. The SIP Manipulation dialog box displays.
14. Click <Close>.
Configuring MIME Header Rule
You can configure MIME header rules within a MIME rule. Use the following procedure to configure a MIME header rule.
To configure a MIME header rule:
1. In the MIME rules dialog box, in the cfgRules field, click <Add>, and then select mime-header-rule from the drop-down list. This allows you to define the MIME rules you want to use to be performed on the elements of the header specified by the MIME rule. The following dialog box displays.
2. In the Name field, enter the name of the element to which this rule applies. Valid values are alpha-numeric characters. Default is blank.
3. In the Mime header name field, enter the parameter name to which this rule applies. The parameter name depends on the element name you entered in step 2. For uri-param, uri-user-param, and header-param it is the parameter
Oracle
®
Enterprise Session Border Controller 81
Configuration
name to be added, replaced, or deleted. For all other types, it serves to identify the element rule and any name can be used. Valid values are alpha-numeric characters. Default is blank.
4. In the Action field, enter the action you want applied to the MIME rule specified in the Name parameter, if there is a match value. Default is none. Valid values are:
• add—Adds a new element, if that element does not already exist.
• delete—Deletes the element, if it exists.
• find-replace-all—Finds all matching elements and replaces it with the element you specified in this procedure.
• log—Logs the element.
• monitor—Monitors the header for this element.
• none—(default) No action is taken.
• reject—Rejects the element.
• replace—Replaces the element.
• sip-manip—Manipulates the SIP elements of this header to the element rules configured.
• store—Stores the element.
5. In the Comparison type field, select the way that you want the MIME to be compared with this MIME rule. This choice dictates how the Oracle Enterprise Session Border Controller processes the match rules against the MIME.
Default is case-sensitive. Valid values are:
• boolean—Header is compared to MIME rule and must match exactly or it is rejected.
• case-insensitive—Header is compared to MIME rule regardless of the case of the header.
• case-sensitive—(default) Header is compared to the MIME rule and case must be exactly the same or it is rejected.
• pattern-rule—Header is compared to the MIME rule and the pattern must be exactly the same or it is rejected.
• refer-case-insensitive—Header is compared to the header rule regardless of the case in a REFER message.
• refer-case-sensitive—Header is compared to the header rule and the case must be exactly the same as in the
REFER message or it is rejected.
6. In the Match value field, enter the value you want to match against the element value for an action to be performed.
7. In the New value field, enter the value for a new element or to replace a value for an existing element. You can enter an expression that includes a combination of absolute values, pre-defined parameters, and operators.
• Absolute values - use double quotes for clarity. You must escape all double quotes and back slashes that are part of an absolute value, and enclose the absolute value in double quotes.
For example: sip:”+$TRUNK_GROUP+”.$TRUNK_GROUP_CONTEXT
• Pre-defined parameters always start with a $. For valid values, see the Pre-defined Parameters Table.
• Operators parameters - For valid values, see the Operators Table.
Examples of entries for the new-value field.
$ORIGINAL+acme
$ORIGINAL+”my name is john”
$ORIGINAL+”my name is \”john\””
$ORIGINAL-^781+^617
8. Click <OK>. The MIME Rule dialog box displays.
9. Click <OK>. The SIP Manipulation dialog box displays.
82 Oracle
®
Enterprise Session Border Controller
Configuration
10. Click <Close>.
Configuring MIME ISUP Rule
You can configure a MIME ISDN User Part (ISUP) rule for a SIP manipulatin rule. Use the following procedure to configure a MIME ISUP rule.
To configure a MIME ISUP rule:
1. In the SIP Manipulation dialog box, in the cfgRules field, click <Add>, and then select mime-isup-rule from the drop-down list. This allows you to define the MIME ISUP rules you want to use to be performed on the elements of the header specified by the MIME rule. The following dialog box displays.
2. In the cfgRules field, click <Add>, and then select mime-header-rule from the drop-down list. The following dialog box displays.
Oracle
®
Enterprise Session Border Controller 83
Configuration
84
3. In the Name field, enter the name of the element to which this rule applies. Valid values are alpha-numeric characters. Default is blank.
4. In the Mime header name field, enter the parameter name to which this rule applies. The parameter name depends on the element name you entered in step 3. For uri-param, uri-user-param, and header-param it is the parameter name to be added, replaced, or deleted. For all other types, it serves to identify the element rule and any name can be used. Valid values are alpha-numeric characters. Default is blank.
5. In the Action field, enter the action you want applied to the MIME rule specified in the Name parameter, if there is a match value. Default is none. Valid values are:
• add—Adds a new element, if that element does not already exist.
• delete—Deletes the element, if it exists.
• find-replace-all—Finds all matching elements and replaces it with the element you specified in this procedure.
• log—Logs the element.
• monitor—Monitors the header for this element.
• none—(default) No action is taken.
• reject—Rejects the element.
• replace—Replaces the element.
• sip-manip—Manipulates the SIP elements of this header to the element rules configured.
• store—Stores the element.
6. In the Comparison type field, select the way that you want the MIME to be compared with this MIME rule. This choice dictates how the Oracle Enterprise Session Border Controller processes the match rules against the MIME.
Default is case-sensitive. Valid values are:
• boolean—Header is compared to MIME rule and must match exactly or it is rejected.
• case-insensitive—Header is compared to MIME rule regardless of the case of the header.
• case-sensitive—(default) Header is compared to the MIME rule and case must be exactly the same or it is rejected.
• pattern-rule—Header is compared to the MIME rule and the pattern must be exactly the same or it is rejected.
• refer-case-insensitive—Header is compared to the header rule regardless of the case in a REFER message.
• refer-case-sensitive—Header is compared to the header rule and the case must be exactly the same as in the
REFER message or it is rejected.
7. In the Match value field, enter the value you want to match against the element value for an action to be performed.
Oracle
®
Enterprise Session Border Controller
Configuration
8. In the New value field, enter the value for a new element or to replace a value for an existing element. You can enter an expression that includes a combination of absolute values, pre-defined parameters, and operators.
• Absolute values - use double quotes for clarity. You must escape all double quotes and back slashes that are part of an absolute value, and enclose the absolute value in double quotes.
For example: sip:”+$TRUNK_GROUP+”.$TRUNK_GROUP_CONTEXT
• Pre-defined parameters always start with a $. For valid values, see the Pre-defined Parameters Table.
• Operators parameters - For valid values, see the Operators Table.
Examples of entries for the new-value field.
$ORIGINAL+acme
$ORIGINAL+”my name is john”
$ORIGINAL+”my name is \”john\””
$ORIGINAL-^781+^617
9. Click <OK>. The MIME ISUP Rule dialog box displays.
10. Click <OK>. The SIP Manipulation dialog box displays.
11. Click <Close>.
Configuring ISUP Param Rules
The ISUP param rules are for advanced users only. This feature configures the following for the ISUP param rules:
• Name
• Type
• Format
• Action
• Comparison Type
• Match Value
• New Value
For more information about configuring ISUP Param Rules, see the section, Regular Experssions and Boolean
Expressions in the Net-Net
®
Enterprise Session Director Configuration Guide.
Configuring MIME SDP Rules
You can configure MIME Session Description Protocol (SDP) rules for SIP Manipulation on the Oracle Enterprise
Session Border Controller if required. Use the following procedure to configure MIME SDP rules.
To configuration MIME SDP rules:
1. From the SIP Manipulation dialog box, in the cfgRules field, click <Add>, and then select mime-sdp-rule from the drop-down list. The following dialog box displays.
Oracle
®
Enterprise Session Border Controller 85
Configuration
2. In the Name field, enter a name you want to use for this MIME SDP rule. Valid values are alpha-numeric characters. Default is blank.
3. In the Msg type field, specify the type of message to which this MIME SDP rule applies. Default is any. Valid values are:
• any—Both Requests and Reply messages
• out-of-dialog—Out of dialog messages only.
• reply—Reply messages only
• request—Request messages only
4. In the Methods field, specify the SIP method names to which you want to apply this MIME SDP rule.
Click <Add>. The following diplays.
86
In the Methods field, enter SIP method names to which you want to apply this MIME SDP rule. For example,
INVITE, ACK, BYE.
Note: This field is empty by default. If you leave the method field empty, the MIME rule applies to all methods.
Oracle
®
Enterprise Session Border Controller
To add the method to the list and apply another one, click <Apply/Add Another>.
When you have completed adding methods, click <OK>. The following displays.
Configuration
5. In the Action field, enter the action you want applied to the MIME SDP rule specified in the Name parameter, if there is a match value. Default is none. Valid values are:
• add—Adds a new element, if that element does not already exist.
• delete—Deletes the element, if it exists.
• find-replace-all—Finds all matching elements and replaces it with the element you specified in this procedure.
• log—Logs the element.
• manipulate—Manipulates the elements of this header to the element rules configured.
• monitor—Monitors the header for this element.
• none—(default) No action is taken.
• reject—Rejects the element.
• sip-manip—Manipulates the SIP elements of this header to the element rules configured.
• store—Stores the element.
6. In the Comparison type field, select the way that you want the MIME to be compared with this MIME SDP rule.
This choice dictates how the Oracle Enterprise Session Border Controller processes the match rules against the
MIME. Default is case-sensitive. Valid values are:
• boolean—Header is compared to MIME rule and must match exactly or it is rejected.
• case-insensitive—Header is compared to MIME rule regardless of the case of the header.
• case-sensitive—(default) Header is compared to the MIME rule and case must be exactly the same or it is rejected.
• pattern-rule—Header is compared to the MIME rule and the pattern must be exactly the same or it is rejected.
• refer-case-insensitive—Header is compared to the header rule regardless of the case in a REFER message.
• refer-case-sensitive—Header is compared to the header rule and the case must be exactly the same as in the
REFER message or it is rejected.
7. In the Match value field, enter the value you want to match against the element value for an action to be performed.
8. In the New value field, enter the value for a new element or to replace a value for an existing element. You can enter an expression that includes a combination of absolute values, pre-defined parameters, and operators.
• Absolute values - use double quotes for clarity. You must escape all double quotes and back slashes that are part of an absolute value, and enclose the absolute value in double quotes.
For example: sip:”+$TRUNK_GROUP+”.$TRUNK_GROUP_CONTEXT
• Pre-defined parameters always start with a $. For valid values, see the Pre-defined Parameters Table.
• Operators parameters - For valid values, see the Operators Table.
Examples of entries for the new-value field.
$ORIGINAL+acme
$ORIGINAL+”my name is john”
$ORIGINAL+”my name is \”john\””
$ORIGINAL-^781+^617
Oracle
®
Enterprise Session Border Controller 87
Configuration
Configuring MIME Header Rule for SDP
You can configure the MIME header rule for the MIME SDP rule if required. Use the procedures in Configuring
MIME Header Rule to configure the MIME header rule fo SDP.
Configuring SDP Session Rule
You can configure the SDP session rules for the MIME SDP rules if required. Use the following procedure to configure SDP Session rules.
To configure SDP session rules:
1. In the MIME SDP Rules dialog box, in the cfgRules field, click <Add>, and then select sdp-session-rule from the drop-down list. This allows you to define the SDP session rules you want to use to be performed on the elements of the header specified by the MIME rule. The following dialog box displays.
88
2. In the Name field, enter the name of the element to which this rule applies. Valid values are alpha-numeric characters. Default is blank.
3. In the Action field, enter the action you want applied to the SDP session rule specified in the Name parameter, if there is a match value. Default is none. Valid values are:
• add—Adds a new element, if that element does not already exist.
• delete—Deletes the element, if it exists.
• find-replace-all—Finds all matching elements and replaces it with the element you specified in this procedure.
• log—Logs the element.
• monitor—Monitors the header for this element.
• none—(default) No action is taken.
• reject—Rejects the element.
• replace—Replaces the element.
• sip-manip—Manipulates the SIP elements of this header to the element rules configured.
• store—Stores the element.
Oracle
®
Enterprise Session Border Controller
Configuration
4. In the Comparison type field, select the way that you want the MIME to be compared with this SDP session rule.
This choice dictates how the Oracle Enterprise Session Border Controller processes the match rules against the
MIME. Default is case-sensitive. Valid values are:
• boolean—Header is compared to MIME rule and must match exactly or it is rejected.
• case-insensitive—Header is compared to MIME rule regardless of the case of the header.
• case-sensitive—(default) Header is compared to the MIME rule and case must be exactly the same or it is rejected.
• pattern-rule—Header is compared to the MIME rule and the pattern must be exactly the same or it is rejected.
• refer-case-insensitive—Header is compared to the header rule regardless of the case in a REFER message.
• refer-case-sensitive—Header is compared to the header rule and the case must be exactly the same as in the
REFER message or it is rejected.
5. In the Match value field, enter the value you want to match against the element value for an action to be performed.
6. In the New value field, enter the value for a new element or to replace a value for an existing element. You can enter an expression that includes a combination of absolute values, pre-defined parameters, and operators.
• Absolute values - use double quotes for clarity. You must escape all double quotes and back slashes that are part of an absolute value, and enclose the absolute value in double quotes.
For example: sip:”+$TRUNK_GROUP+”.$TRUNK_GROUP_CONTEXT
• Pre-defined parameters always start with a $. For valid values, see the Pre-defined Parameters Table.
• Operators parameters - For valid values, see the Operators Table.
Examples of entries for the new-value field.
$ORIGINAL+acme
$ORIGINAL+”my name is john”
$ORIGINAL+”my name is \”john\””
$ORIGINAL-^781+^617
Configuring SDP Line Rules for Sessions
When configuring the SDP session rules, you can also configure the SDP line rules. For more information about configuring SDP line rules, see the section, sdp-line-rule in the Net-Net
®
Enterprise Session Director Configuration
Guide.
Use the following procedure to configure the SDP line rules.
To configure SDP line rules:
1. From the SDP Session Rule dialog box, in the cfgRules field, click <Add>, and then select sdp-line-rules from the drop-down list. This allows you to define the SDP line rules you want to use to be performed on the elements of the header specified by the SDP session rule. The following dialog box displays.
Oracle
®
Enterprise Session Border Controller 89
Configuration
90
2. In the Name field, enter the name of the element to which this rule applies. Valid values are alpha-numeric characters. Default is blank.
3. In the Type field, enter the applicable SDP descriptor for the SDP line rule. SDP descriptors are added to the SDP, adhering to the definitions in RFC 4566. Default is blank. Valid values are: e p i u c b o s
Session Description v Protocol version
Originator and session identifier
Session name
Session information*
URI of description*
Email address*
Phone number*
Connection information - not required if included in all media*
Zero or more bandwidth information lines* One or more time descriptions (“t=” and r= lines; see below) r t z k
Time zone adjustments*
Encryption key* a Zero or more session attribute lines* Zero or more media descriptions (see below)
Time Description
Time the session is active
Zero or more repeat times*
*Indicates an optional descriptor
4. In the Action field, enter the action you want applied to the SDP line rule specified in the Name parameter, if there is a match value. Default is none. Valid values are:
• add—Adds a new element, if that element does not already exist.
Oracle
®
Enterprise Session Border Controller
Configuration
• delete—Deletes the element, if it exists.
• find-replace-all—Finds all matching elements and replaces it with the element you specified in this procedure.
• log—Logs the element.
• monitor—Monitors the header for this element.
• none—(default) No action is taken.
• reject—Rejects the element.
• replace—Replaces the element.
• sip-manip—Manipulates the SIP elements of this header to the element rules configured.
• store—Stores the element.
5. In the Comparison type field, select the way that you want the MIME to be compared with this SDP line rule. This choice dictates how the Oracle Enterprise Session Border Controller processes the match rules against the MIME.
Default is case-sensitive. Valid values are:
• boolean—Header is compared to MIME rule and must match exactly or it is rejected.
• case-insensitive—Header is compared to MIME rule regardless of the case of the header.
• case-sensitive—(default) Header is compared to the MIME rule and case must be exactly the same or it is rejected.
• pattern-rule—Header is compared to the MIME rule and the pattern must be exactly the same or it is rejected.
• refer-case-insensitive—Header is compared to the header rule regardless of the case in a REFER message.
• refer-case-sensitive—Header is compared to the header rule and the case must be exactly the same as in the
REFER message or it is rejected.
6. In the Match value field, enter the value you want to match against the element value for an action to be performed.
7. In the New value field, enter the value for a new element or to replace a value for an existing element. You can enter an expression that includes a combination of absolute values, pre-defined parameters, and operators.
• Absolute values - use double quotes for clarity. You must escape all double quotes and back slashes that are part of an absolute value, and enclose the absolute value in double quotes.
For example: sip:”+$TRUNK_GROUP+”.$TRUNK_GROUP_CONTEXT
• Pre-defined parameters always start with a $. For valid values, see the Pre-defined Parameters Table.
• Operators parameters - For valid values, see the Operators Table.
Examples of entries for the new-value field.
$ORIGINAL+acme
$ORIGINAL+”my name is john”
$ORIGINAL+”my name is \”john\””
$ORIGINAL-^781+^617
8. Click <OK>. The SDP Session Rule dialog box displays.
9. Click <OK>. The SIP Manipulation dialog box displays.
Oracle
®
Enterprise Session Border Controller 91
Configuration
10. Click <Close>.
Configuring SDP Media Rules
When configuring the SDP session rules, you can also configure the SDP media rules. Use the following procedure to configure the SDP media rules.
To configure SDP media rules:
1. From the SDP Session Rule dialog box, in the cfgRules field, click <Add>, and then select sdp-media-rules from the drop-down list. This allows you to define the SDP media rules you want to use to be performed on the elements of the header specified by the SDP session rule. The following dialog box displays.
92
2. In the Name field, enter the name of the element to which this rule applies. Valid values are alpha-numeric characters. Default is blank.
3. In the Media Type field, enter the applicable SDP descriptor for the SDP media rule. SDP descriptors are added to the SDP, adhering to the definitions in RFC 4566. Default is blank. Valid values are:
Media Description (if present) i m Media name and transport address
Media title* k a c b
Connection information - optional if included at session level*
Zero or more bandwidth information lines*
Encryption key*
Zero or more media attribute lines*
Time Description
Oracle
®
Enterprise Session Border Controller
Configuration
r t Time the session is active
Zero or more repeat times*
*Indicates an optional descriptor
4. In the Action field, enter the action you want applied to the SDP media rule specified in the Name parameter, if there is a match value. Default is none. Valid values are:
• add—Adds a new element, if that element does not already exist.
• delete—Deletes the element, if it exists.
• find-replace-all—Finds all matching elements and replaces it with the element you specified in this procedure.
• log—Logs the element.
• monitor—Monitors the header for this element.
• none—(default) No action is taken.
• reject—Rejects the element.
• replace—Replaces the element.
• sip-manip—Manipulates the SIP elements of this header to the element rules configured.
• store—Stores the element.
5. In the Comparison type field, select the way that you want the MIME to be compared with this SDP media rule.
This choice dictates how the Oracle Enterprise Session Border Controller processes the match rules against the
MIME. Default is case-sensitive. Valid values are:
• boolean—Header is compared to MIME rule and must match exactly or it is rejected.
• case-insensitive—Header is compared to MIME rule regardless of the case of the header.
• case-sensitive—(default) Header is compared to the MIME rule and case must be exactly the same or it is rejected.
• pattern-rule—Header is compared to the MIME rule and the pattern must be exactly the same or it is rejected.
• refer-case-insensitive—Header is compared to the header rule regardless of the case in a REFER message.
• refer-case-sensitive—Header is compared to the header rule and the case must be exactly the same as in the
REFER message or it is rejected.
6. In the Match value field, enter the value you want to match against the element value for an action to be performed.
7. In the New value field, enter the value for a new element or to replace a value for an existing element. You can enter an expression that includes a combination of absolute values, pre-defined parameters, and operators.
• Absolute values - use double quotes for clarity. You must escape all double quotes and back slashes that are part of an absolute value, and enclose the absolute value in double quotes.
For example: sip:”+$TRUNK_GROUP+”.$TRUNK_GROUP_CONTEXT
• Pre-defined parameters always start with a $. For valid values, see the Pre-defined Parameters Table.
• Operators parameters - For valid values, see the Operators Table.
Examples of entries for the new-value field.
$ORIGINAL+acme
$ORIGINAL+”my name is john”
$ORIGINAL+”my name is \”john\””
$ORIGINAL-^781+^617
Configuring SDP Line Rules for Media
You can configure SDP Line Rules for Media if required. For more information about configuring SDP line rules, see the section, sdp-line-rule in the Net-Net
®
Enterprise Session Director Configuration Guide.
Use the following procedure to configure SDP line rules for media.
To configure SDP line rules for media:
Oracle
®
Enterprise Session Border Controller 93
Configuration
1. From the SDP Media Rule dialog box, in the cfgRules field, click <Add>, and then select sdp-line-rules from the drop-down list. This allows you to define the SDP line rules you want to use to be performed on the elements of the header specified by the SDP media rule. The following dialog box displays.
94
2. In the Name field, enter the name of the element to which this rule applies. Valid values are alpha-numeric characters. Default is blank.
3. In the Type field, enter the applicable SDP descriptor for the SDP line rule. SDP descriptors are added to the SDP, adhering to the definitions in RFC 4566. Default is blank. Valid values are: e p i u c b o s
Session Description v Protocol version
Originator and session identifier
Session name
Session information*
URI of description*
Email address*
Phone number*
Connection information - not required if included in all media*
Zero or more bandwidth information lines* One or more time descriptions (“t=” and r= lines; see below) r t z k
Time zone adjustments*
Encryption key* a Zero or more session attribute lines* Zero or more media descriptions (see below)
Time Description
Time the session is active
Zero or more repeat times*
Oracle
®
Enterprise Session Border Controller
Configuration
*Indicates an optional descriptor
4. In the Action field, enter the action you want applied to the SDP line rule specified in the Name parameter, if there is a match value. Default is none. Valid values are:
• add—Adds a new element, if that element does not already exist.
• delete—Deletes the element, if it exists.
• find-replace-all—Finds all matching elements and replaces it with the element you specified in this procedure.
• log—Logs the element.
• monitor—Monitors the header for this element.
• none—(default) No action is taken.
• reject—Rejects the element.
• replace—Replaces the element.
• sip-manip—Manipulates the SIP elements of this header to the element rules configured.
• store—Stores the element.
5. In the Comparison type field, select the way that you want the MIME to be compared with this SDP line rule. This choice dictates how the Oracle Enterprise Session Border Controller processes the match rules against the MIME.
Default is case-sensitive. Valid values are:
• boolean—Header is compared to MIME rule and must match exactly or it is rejected.
• case-insensitive—Header is compared to MIME rule regardless of the case of the header.
• case-sensitive—(default) Header is compared to the MIME rule and case must be exactly the same or it is rejected.
• pattern-rule—Header is compared to the MIME rule and the pattern must be exactly the same or it is rejected.
• refer-case-insensitive—Header is compared to the header rule regardless of the case in a REFER message.
• refer-case-sensitive—Header is compared to the header rule and the case must be exactly the same as in the
REFER message or it is rejected.
6. In the Match value field, enter the value you want to match against the element value for an action to be performed.
7. In the New value field, enter the value for a new element or to replace a value for an existing element. You can enter an expression that includes a combination of absolute values, pre-defined parameters, and operators.
• Absolute values - use double quotes for clarity. You must escape all double quotes and back slashes that are part of an absolute value, and enclose the absolute value in double quotes.
For example: sip:”+$TRUNK_GROUP+”.$TRUNK_GROUP_CONTEXT
• Pre-defined parameters always start with a $. For valid values, see the Pre-defined Parameters Table.
• Operators parameters - For valid values, see the Operators Table.
Examples of entries for the new-value field.
$ORIGINAL+acme
$ORIGINAL+”my name is john”
$ORIGINAL+”my name is \”john\””
$ORIGINAL-^781+^617
8. Click <OK>. The SDP Media Rule dialog box displays.
9. Click <OK>. The MIME SDP Rule dialog box displays.
10. Click <OK>. The Modify SIP manipulation dialog box displays.
11. Click <OK>. The SIP Manipulation dialog box displays.
Oracle
®
Enterprise Session Border Controller 95
Configuration
12. Click <Close>.
Add an SPL
Add an SPL plugin, which is a customized script, to quickly implement a feature on the Oracle Enterprise Session
Border Controller (E-SBC). The SPL plugin augments running the software image on the E-SBC, and provides new features when you need them without having to upgrade the software.
Before You Begin
• Confirm the name and location of the SPL plugin that you want to add.
Use the following procedure to integrate an Oracle-signed plug-in with the E-SBC operating system. Note that the E-
SBC) does not load an unsigned SPL or one with invalid signatures.
Procedure
1. From the Web GUI, click Other > SPL.
2. In the Spl config dialog, do the following:
Attributes
Spl options
Plugins
Instructions
Enter the name of SPL option.
Click Add, and do the following:
• Select State to enable the plugin.
• Enter the name of plugin to load.
• Click OK.
The system displays the SPl config page.
3. Click OK.
4. Save and activate the configuration.
Configuration Editing Methods
In Basic mode, you can edit a configuration. After editing a configuration, you must save and activate the configuration for the changes to take affect.
Editing Icon Configuration
For any device or interface that currently exists in your workspace, you can double-click the icon and edit the configuration, or right-click on the icon and select Edit from the drop-down menu. The following shows an example of editing the PBX configuration.
96 Oracle
®
Enterprise Session Border Controller
Configuration
Editing Advanced Configuration
To edit more advanced configurations in your network, you can select the required configuration from the Main
Menu, and edit the configuration item from the list that displays. You can edit an item using either of two methods:
• Selecting the item from the list and clicking the <Edit> button
• Selecting the item from the list, right clicking the mouse, and selecting Edit from the drop-down menu.
The following shows an example of editing a host route configuration.
Oracle
®
Enterprise Session Border Controller 97
Configuration
Editing Parameter Fields
Some dialog boxes in a configuration provide the ability to edit within a parameter field. In the following example, a user list within the trap-receiver configuration is selected for editing.
Copying a Configuration
You can copy configurations, when configuring your network.
Copying Advanced Configuration
To copy more advanced configurations in your network, you can select the required configuration from a list that displays using either of two methods:
• Selecting the item from the list and clicking the <Copy> button
• Selecting the item from the list, right clicking the mouse, and selecting Copy from the drop-down menu.
The following shows host route 192.30.1.105 copied and edited as a new host route of 192.30.1.106.
98 Oracle
®
Enterprise Session Border Controller
Configuration
Deleting a Configuration
In Basic Mode, you can delete configurations as required.
Oracle
®
Enterprise Session Border Controller 99
Configuration
Deleting Icon Configuration
For any device or interface that currently exists in your workspace, you can right-click on the icon and select Delete from the drop-down menu. The following shows an example of deleting a PBX configuration.
The configuration deletes from the workspace and from the Oracle Enterprise Session Border Controller.
Deleting Advanced Configuration
To delete more advanced configurations in your network, you can select the required configuration from the Main
Menu, and delete the configuration item from the list that displays. You can delete an item using either of two methods:
• Selecting the item from the list and clicking the <Delete> button or
• Selecting the item from the list, right clicking the mouse, and selecting Delete from the drop-down menu.
The following shows host route 192.30.1.106 being deleted from the Host route table.
100 Oracle
®
Enterprise Session Border Controller
Configuration
Deleting Parameter Fields
Some dialog boxes in a configuration provide the ability to delete within a parameter field. In the following example, a user list within the trap-receiver configuration is selected for deleting.
Oracle
®
Enterprise Session Border Controller 101
Configuration
Expert Mode
The Expert mode of configuring the Oracle Enterprise Session Border Controller (E-SBC) allows you to set parameters by navigating through a tree structure of objects and attributes. This tree structure matches the Oracle
Command Line Interface (ACLI) view of the
E-SBC.
Note: The Web GUI does not indicate required fields. You may be able to save the configuration without a required value because the E-SBC ignores the element in the configuration. The system does not display an error message for a missing required parameter.
Accessing Expert Mode
You can access the Expert mode of configuration by clicking the Configuration tab in the Web GUI.
To access Expert mode:
1. After logging into the Web GUI, click on the Configuration tab. The following displays.
Note: The “Expert Mode” displays only if your Administrator set this interface as default during the
Installation Wizard setup. If “Basic Mode” is set as the default, click Switch to Expert in the upper right corner of the screen.
The page displays the minimum objects you can set to configure the Oracle Enterprise Session Border Controller.
You can display additional objects to configure by clicking the Show Advanced link at the bottom of the left column.
Oracle recommends advanced parameters be configured by experienced administrators only.
102 Oracle
®
Enterprise Session Border Controller
Configuration
The list of sub-elements in the right column are all the sub-elements associated with the top-level element selected from the left column.
You can select the sub-element you want to configure from the right column if required; or you can expand a toplevel object to show the sub-element of that object.
2. Expand a top-level object in the left column, and then click on a sub-element. Or click on the sub-element in the right column.
Or select the sub-element from here
Select the object and/or sub-element from here
The page associated with the sub-element you select displays. The following illustration is an example of the media-manager page.
Oracle
®
Enterprise Session Border Controller 103
Configuration
Some fields in the configuration windows of Expert Mode identify valid values for a field. For example, in the
Modify media-manager window above, a range of values for each text box is provided.
Expert Mode Configuration Objects
In Expert Mode, you can add, modify, and delete configuration objects and attributes as required.
The system displays the following configuration objects in Expert Mode:
• media-manager
• session-router
• system
• security
The following table lists the sub-elements of each top element in the Oracle Enterprise Session Border Controller.
Media Manager
codec-policy dns-alg-constraints dns-config media-manager media-policy msrp-config playback-config realm-config realm-group* rtcp-policy static-flow* steering-pool
Session Router System
access-control auto-config account-config capture-receiver** allowed-elements-profile* host-route class-profile class-policy enforcement-profile* enum-config* network-interface network-parameters* ntp-config phy-interface filter-config h323 h323-config h323-stack home-subscriber-server http-alg* iwg-config ladp-config local-policy redundancy-config snmp-community spl-config system-access-list* system-config tdm-config trap-receiver web-server-config
Security
auth-params* authentication* ike** dpd-params ipsec** ipsec-global-config security-association security-association security-policy password-policy*
104 Oracle
®
Enterprise Session Border Controller
Configuration
Media Manager Session Router
local-response-map local-routing-config media-profile net-management-control qos-constraints response-map service-health session-agent session-constraints session-group sesson-recording group session-recording-server session-timer-profile session-translation sip-advanced-logging sip-config sip-feature sip-interface sip-manipulation sip-monitoring surrogate-agent survivability translation-rules
System Security
*These advanced parameters are applicable to Virtual Machines (VMs) and Session Director hardware.
**These parameters are applicable to Session Director hardware only.
Function Buttons
Expert Mode displays function buttons on each configuration page to perform tasks such as add, edit, copy, and delete. The system activates the buttons depending on your selection on a page. Some sub-element tables also display these buttons. The following table describes each button.
Button
Add
Edit
Description
Use to add configuration information to the Oracle Enterprise Session Border
Controller.
Use to edit existing configuration information.
Note: Select an item in a list to enable the Edit button.
Oracle
®
Enterprise Session Border Controller 105
Configuration
Button
Copy
Delete
Description
Use to copy existing configuration information, and edit the information to create a new configuration.
Note: Select an item in a list to enable the Copy button.
Use to delete existing configuration information.
Note: Select an item in a list to enable the Delete button.
Use to search for configured objects.
Use to clear the Search field.
Search
Clear
Add a Configuration
The following is an example procedure for adding a configuration to the Oracle Enterprise Session Border Controller.
To add a configuration:
1. Under media-manager, click codec-policy.
Note: In some tables, default information displays if applicable. In the example below, DefaultENT and
DefaultSP are the default codec policies in the Oracle Enterprise Session Border Controller.
2. Click <Add>. The following displays.
3. Enter information in the text box and add information to the list boxes as required. Refer to the Net-Net
®
Enterprise Session Director Configuration Guide for valid values for each field.
4. Click <OK> to save the changes.
Editing a Configuration
The following is an example procedure for editing a configuration in the
Oracle Enterprise Session Border Controller.
To edit a configuration:
1. Under media-manager, click on codec-policy. The following displays.
106
2. In the list box, select the item you want to edit and click <Edit>. The configuration you selected displays.
Oracle
®
Enterprise Session Border Controller
Configuration
3. Edit the configuration as applicable and then click <OK>.
Deleting a Configuration
The following is an example procedure for deleting a configuration in the Oracle Enterprise Session Border
Controller.
To delete a configuration:
1. Under media-manager, click on codec-policy. The following displays.
2. In the list box, select the item you want to delete and click <Delete>. The following prompt displays.
3. Click <Yes> to delete the item from the configuration. Or click <No> to cancel the delete function. If you delete the item, it no longer displays in the list box. You must save and activate the configuration for the change to take affect.
Oracle
®
Enterprise Session Border Controller 107
Configuration
Copying a Configuration
The following is an example procedure for copying a configuration in the
Oracle Enterprise Session Border Controller.
To copy a configuration:
1. Under media-manager, click on codec-policy. The following displays.
2. In the list box, select the item you want to copy and click <Copy>. The configuration you selected displays.
108
3. Edit the configuration as applicable and then click <OK>. The new configuration displays in the list box, and the old configuration is retained. In the example, below, Codec Policy A is retained, and Codec Policy B is a new item in the list.
Oracle
®
Enterprise Session Border Controller
Configuration
Dynamic ACL for the HTTP-ALG
The dynamic Access Control List (ACL) option for HTTP-Application Layer Gateway (ALG) provides Distributed
Denial of Service (DDoS) attack protection for the HTTP port.
When the dynamic ACL option is enabled, the static flow for the public listening socket defined in http-alg > public is created with at trust level set to untrusted. Each listening socket creates and manages its ACL list, which allows the listening socket to keep track of the number of received and invalid messages, the number of connections per endpoint, and so on. You can configure a different setting for each http-alg object.
Dynamic ACL for each endpoint is triggered by Session Initialization Protocol (SIP) registration messages. Upon receiving a SIP registration message, the SIP agent creates a dynamic ACL entry for the endpoint. If the 200 OK response is received, the ACL is promoted, allowing the HTTP message to go through the security domain. If SIP registration is unsuccessful, the ACL entry is removed and HTTP ingress messages are blocked from the endpoint.
The ACL entry is removed upon incomplete registration renewal or telephone disconnect.
The following example describes the criteria and associated configuration item that result in a denied or allowed connection for both low and medium control levels.
Criteria
Exceed total number of connections for allowed
Exceed total connections per peer
ACL not promoted
Exceed maximum number of packets/sec
Exceed maximum number of error packets
Associated Configuration Item
http-alg > max-incoming-conns
Action
Connection denied http-alg > per-src-ip-mas-incoming-conns Connection denied
Dynamically set on SIP registration Connection denied realm-config > maximum-signal-threshold Connection denied and peer is demoted
Realm-config > invalid-signal-threshold Connection denied and peer is demoted
Oracle recommends setting realm-config > access-control-level to medium.
If a peer is promoted to trusted, the system performs DDoS checks on max number of packets/sec and max
number of error packets allowed.
Demotions depend on the realm's ream-config > access-control-trust-level setting. For more information on realm-
config settings, see the ACLI Configuration Guide.
Oracle
®
Enterprise Session Border Controller 109
Configuration
If you want to configure different ACL settings for SIP traffic and for HTTP-ALG traffic, you must configure a realm for each type of traffic.
Enable Dynamic ACL for the HTTP ALG
The Dynamic Access Control List (ACL) for HTTP Application Layer Gateway (ALG) option, which provides
Distributed Denial of Service (DDoS) attack protection for the HTTP port, is an option that you must enable.
Before You Begin
• Confirm that the session manager is mapped to the Oracle Enterprise Session Border Controller.
• Confirm that the system displays the Expert mode.
Two ACL entires are required for each registered telephone, where one entry is used for SIP traffic and one is used for HTTP-ALG traffic.
Note: Enabling dynamic access control for HTTP-ALG traffic reduces the number of available dynamic ACL entries on the session border controller, which may reduce the number of concurrent trusted endpoints that the system can support.
Procedure
1. On the Web GUI, on the Configuration tab, click Objects --> session-router --> http-alg.
2. Click Add.
The system displays the Add http-alg page.
3. On the Add http-alg page, click Show advanced.
4. In the Add http-alg dialog, do the following:
Attributes
Name
State
Description
Realm id
Address
Destination address
Destination port
TLS profile
Realm id
Address
Port
TLS profile
Session-manager-mapping
Dynamic ACL
Max incoming conns
Instructions
Enter a name for this ACL.
Select State to enable this ACL.
Enter a description of this ACL.
Select the private realm to which to apply this ACL from the drop down list.
Enter the IP address of the selected private realm.
Enter the destination IP address.
Enter the destination port. Range:1-65535. Default: 80.
Enter TLS profile to apply from the drop-down list.
Select the public realm identifier from the drop down list.
Enter the IP address of the selected public realm.
Enter the listening port number. Range:1-65535.
Default: 80.
Select a TLS profile to apply from the drop-down list.
Not applicable to this procedure.
Select to enable dynamic ACL creation on SIP messages.
Enter a number for the maximum allowed incoming
HTTP connections. Range: 0-4294967295.
110 Oracle
®
Enterprise Session Border Controller
Configuration
Attributes
Per src IP max incoming conns
Instructions
Enter a number for the maximum allowed incoming connections per registered IP address. Range:
0-4294967295.
5. Click OK.
6. Save and activate the configuration.
Dynamic Access Control List (ACL) Settings for the HTTP Application
Layer Gateway (ALG)
You can set the following parameters for the realm specified in http-alg > public > realm-id.
• access-control-trust-level
• invalid-signal-threshold
• maximum-signal-threshold
• untrusted-signal-threshold
• deny-period
For more information on realm-config settings, see the ACLI Configuration Guide.
Session Manager Mapping
The Oracle Enterprise Session Border Controller (SBC) supports mapping between multiple session managers and multiple SBCs. Such mapping allows the SBC to work in a redundant network configuration where you can map:
• The primary session manager to the primary SBC IP address
• One or more redundant session managers to one or more redundant SBCs
To map a redundant session manager to a redundant SBC, map the private IP address of the redundant session manager to the public SIP IP address configured in HTTP-ALG > Public on the SBC. For instructions, see "Map a
Session Manager to a Session Border Controller."
Map a Session Manager to a Session Border Controller
You can map one or more session managers to an Oracle Enterprise Session Border Controller (E-SBC) to provide redundancy and load balancing.
Before You Begin
• Note the private IP address of the session manager and the public SIP interface IP address of the session border controller that you want to map.
• Confirm that the system displays the Expert mode.
Map the private IP address of the session manager to the public SIP interface IP address of the E-SBC.
Procedure
1. From the Web GUI, go to Configuration > session-router > http-alg.
2. On the http-alg page, click Show advanced > Add.
3. In the Add http-alg dialog, enter the information in the fields and make the selections for the deployment.
4. Click OK.
The system lists the new map on the http-alg page.
5. Save and activate the configuration.
Oracle
®
Enterprise Session Border Controller 111
Configuration
Upgrade Software - Web GUI System Tab
You can upgrade the system software from the System tab on the Web GUI. The system requires a reboot after the upgrade.
1. From the Web GUI, click the System tab.
2. Click Upgrade Software.
3. Click Verification.
4. Verify that system health, synchronization health, current configuration version, and disk usage are appropriate and adequate for the upgrade.
5. From the drop-down list, select Upload method , and select one of the following methods.
• Local. Use to select a file from your system for transfer.
• Flash. Use to select a file already on the device.
• Network. Use to specify parameters for network boot by way of file transfer.
The system displays the Upgrade Software dialog with the fields required for your upgrade.
6. Complete the required fields.
• Software file to upload. (Local) Use Browse to locate the file on your local system.
• Software file. (Flash) The location and name of the file on the device.
• Boot file. (Network) The complete name of the boot file.
• Host IP. (Network) The IP address of the FTP server.
• FTP username. (Network) The user name to log onto the FTP server.
• FTP password. (Network) The password to log onto the FTP server.
7. Optional. Select Reboot after upload.
8. Click Complete.
• If you did not select Reboot after upload, the system displays a message stating that a reboot is required for the changes to take effect.
• If you selected Reboot after upload, the system displays a message stating that it is about to reboot.
9. Click OK.
If you selected Reboot after upload, the system reboots.
Upgrade Software - Wizard
You can upgrade the system software with the Upgrade software wizard on the Web GUI.
Use the Software Upgrade wizard to perform the following tasks:
• Check the system health before the upgrade
• Download new software
• Change boot parameters
• Reboot the system
The system requires a reboot after the upgrade for the changes to take effect.
1. From the Web GUI tool bar, click Wizards.
2. On the Wizards drop down list, click Upgrade software .
3. Optional. In the Software Upgrade dialog, click Verification, and do the following:
• Click View Synchronization Health, and confirm that the system components are synchronized.
• Click View Configuration Version, and note the Current Version and Running Version.
• Click View Disk Usage, and confirm that the system has enough free space.
4. In the Software Upgrade dialog, do the following:
112 Oracle
®
Enterprise Session Border Controller
Configuration
• Select an Upload Method.
• Select a Software File to Upload, if you chose the Local or Flash method.
• Confirm or edit the boot parameters, if you chose the Network method.
• Optional. Select Reboot After Upload.
5. Click Complete.
• If you did not select Reboot After Upload, the system displays a message stating that a reboot is required for the changes to take effect.
• If you selected Reboot After Upload, the system displays a message stating that it is about to reboot.
6. Click OK.
The system performs the file transfer and any boot parameter changes. If you selected Reboot After Update, the system reboots.
Update the Configuration Schema
You can update the configuration parameters in your software with any new parameters included in a subsequent release by updating the schema.
Updating the schema adds any new parameters to each configuration screen in Basic Mode.
After updating your Web GUI software to a subsequent release, the system displays a schema update prompt after first log on to the GUI. If you click Cancel, the update is bypassed and no new parameters are added. The update prompt displays each time you log on to the Web GUI, until you choose to update the configuration schema.
Procedure
1. Log into the Web GUI. The system displays the following prompt.
2. Click Update. The system backs up the current configuration and updates the configuration schema.
Note: If needed, you can reinstall the backed up configuration at a later time from the System tab in the
Web GUI.
3. Click OK.
4. On the Configuration page toolbar, click Save.
Certificate Management
You can perform the following certificate management tasks from the Web GUI in either Basic Mode or Expert
Mode:
• Create a Certificate Record and add it to the system. See Create a Certificate Record.
• Generate a Certificate Request to send to a Certificate Authority. See Generate a Certificate Request.
• Import a Certificate into the system. See Import a Certificate.
Oracle
®
Enterprise Session Border Controller 113
Configuration
Add a Certificate Record
Use the certificate-record element to add certificate records to the Oracle Enterprise Session Border Controller (E-
SBC).
Before You Begin
• Confirm that the system displays the Expert mode.
Procedure
A certificate record represents either the end-entity or the Certificate Authority (CA) certificate on the E-SBC. When you configure a certificate for the E-SBC, the name that you enter must be the same as the name that you use to generate a certificate request. If configuring for an end stations CA certificate for mutual authentication, the certificate name must be the same name used during the import procedure.
• If this certificate record is used to present an end-entity certificate, associate a private key with this certificate record by using a certificate request.
• If this certificate record is created to hold a CA certificate or certificate in pkcs12 format, a private key is not required.
1. From the Web GUI, click Configuration > Security > Certificate record.
2. On the Certificate record page, clickAdd.
3. On the Add certificate record page, click Show advanced, and do the following:
Attributes
Name
Country
State
Locality
Organization
Unit
Common name
Key size
Alternate name
Trusted
Key usage list
Instructions
Enter the name of the certificate record.
Enter a two character country name abbreviation. For example, US for the United States.
Enter a two character state or province name abbreviation. For example, NE for Nebraska.
Enter the name of the locality in the state or province.
For example, a city, a township, or a parish. Range:
1-128 characters.
Enter the name of the organization holding the certificate. For example, a company name. Range: 1-64 characters.
Name of the unit within the organization holding the certificate. For example, a business unit or a department. Range: 1-64 characters.
Common name for the certificate record. For example, your name. Range: 1-64 characters.
Size of the key for the certificate. Supported values:
512, 1024, 2048, and 4096.
Alternate name of the certificate holder.
Select to trust this certificate record.
Click Add and select a key that you want to use with this certificate record from the drop-down list, and do one of the following:
• Click OK.
• Click Apply/Add Another, add another key , and click OK. Repeat as needed.
114 Oracle
®
Enterprise Session Border Controller
Configuration
Attributes
Oracle
®
Enterprise Session Border Controller
Instructions
This parameter defaults to the combination of digitalSignature and keyEncipherment. For a list of other valid values and their descriptions, see the section “Key Usage Control” in the ACLI
Configuration Guide.
Extended key usage list Click Add, select an extended key that you want to use with this certificate record from the drop-down list, and do one of the following:
• Click OK.
• Click Apply/Add Another, add another extended key, and click OK. Repeat as needed.
This parameter defaults to serverAuth. For a list of other valid values and their descriptions, see the section “Key Usage Control” in the ACLI
Configuration Guide.
Options
4. Click OK.
5. Save and activate the configuration.
Next Steps
• Create TLS profiles, using the certificate records to further define the encryption behavior and to provide an entity that you can apply to a SIP interface.
Generate a Certificate Request from the GUI
Use the certificate-record element to select a certificate record and generate a certificate request.
Before You Begin
• Confirm that the certificate record exists.
• Confirm that the system displays the Expert mode.
To get a certificate authorized by a Certificate Authority (CA), you must generate a certificate request from the certificate record on the device and send it to the CA.
Procedure
1. From the Web GUI, click Configuration > security > certificate-record.
The system displays a list of certificate records.
2. Select the certificate record for the device.
3. Click Generate.
The system creates the request and displays it in a dialog.
4. Copy the information from the dialog and send it to your CA as a text file.
Next Steps
• When the CA replies with the certificate, import the certificate to the device with the corresponding certificate record.
Import a Certificate
Use the certificate-record element to import a certificate into the Oracle Enterprise Session Border Controller (E-
SBC).
Before You Begin
115
Configuration
• Confirm that the system displays the Expert mode.
Use this procedure to import either a device certificate or an end-station CA certificate for a mutual authentication deployment. You must import the certificate to the corresponding certificate record for the E-SBC. End-station CA certificates may or may not need to be imported against a pre-configured certificate record.
Procedure
1. From the Web GUI, click Configuration > security > certificate record .
2. Select the certificate record for the device.
3. Click Import.
The system displays a dialog from which you can import the certificate.
4. Select one of the following format types from the Format drop down list:
• pkcs7
• x509
• Try-all. The system tries all possible formats until it can to import the certificate.
5. Browse to the certificate file, and select the certificate to import.
6. Click Import.
The system imports the certificate.
Next Steps
• Apply the corresponding certificate record to the intended SIP interface.
Configuring Remote Site Survivability using the Web GUI
The Oracle Enterprise Session Border Controller Web GUI supports the configuration of Survivability.
Use the following procedure to configure Survivability.
Configure a Service Tag for an IP Interface
Configure a service tag to enable the Oracle Enterprise Session Border Controller to monitor the health of a group of session agents, when survivability is enabled.
• Confirm that survivability is enabled.
• Confirm that the system displays the Expert mode.
To configure a service-tag for an IP interface:
1. From the Web GUI, click Configuration > session-router > sip-interface.
2. On the Modify SIP Interface page, in the Service tag field, enter a character string that identifies a group of session-agents for the current SIP interface.
3. Click OK.
4. Save and activate the configuration.
Configure Remote Site Survivability
You must enable remote site survivability on the Oracle Enterprise Session Border Controller (E-SBC) and set the parameters before the system can enter and exit survival mode.
Before You Begin
• Confirm that at least one session agent is configured.
• Confirm that the system displays the Expert mode.
Procedure
1. From the Web GUI, click Configuration > session-router > survivability.
2. At the bottom of the left pane, click Show advanced.
116 Oracle
®
Enterprise Session Border Controller
Configuration
3. On the Add survivability page, do the following:
Attributes Instructions
State
Reg expires
Select to enable Survivability.
Enter the number of seconds that the Oracle Enterprise
Session Border Controller waits before entering the remote site survivability mode when the registration expires.
Prefix length
Session agent hostname
Enter the maximum number of digits allowed for a phone extension. Range: 0-10.
Select the agent hostname or the session agent group name from the drop down list.
4. Click OK.
5. Save and activate the configuration.
Next Steps
• Configure a ping method on the session agent. See "Configure a Session Agent."
Configure Service Health
To configure the service health for a list of service tags:
1. Select session-router > service-health.
2. In the service-tag-list window, click <Add>.
3. In the service-tag-string field, enter a list of service tags (associated with IP interfaces) on which the Oracle
Enterprise Session Border Controller (E-SBC) checks the service health. Default is blank. For example, intf1, intf2, intf3.
4. In the sa-health-profile box, click <Add>.
5. In the session-agent-hostname field, enter the hostname of the session agent on which the E-SBC monitors the service health.
6. In the session-agent-health field, enter the health score that the E-SBC uses to determine whether or not the health of the session-agent has decremented and gone out of service or incremented and came back into service. Valid values are 0 to 100 percent. Default is 100. For example, if this parameter is set to 100, and if the health score of the session-agent falls beneath 100 percent, Survivability mode begins (if enabled). If the health of the sessionagent comes back up to 100 percent, Survivability mode ends and the system returns to Normal mode.
Note: For cases where there are two session agents, each session agent could have a service health of 50.
7. Click <OK>.
8. Save and activate the configuration.
Configure the Ping Method for a Session Agent
Configure a ping method to confirm that the session agent is in service.
Use the session-agent object to configure the ping-method for a session-agent.
1. Click Configuration > session-router > session-agent.
2. On the Modify Session Agent page, select the session-agent for which you want to configure the ping-method, and click OK.
3. In the Ping method field, enter the SIP message/method to use to ping a session agent. Oracle recommends setting this value to OPTIONS.
4. In the Ping interval field, enter the number of seconds between pings.
Oracle
®
Enterprise Session Border Controller 117
Configuration
5. ClickOK.
6. Save and activate the configuration.
118 Oracle
®
Enterprise Session Border Controller
Time Division Multiplexing (TDM)
The TDM functionality is for companies planning to migrate from TDM to SIP trunks by using a hybrid TDM-SIP infrastructure, rather than adopting VoIP-SIP as their sole means of voice communications. The TDM interface provides failover for egress audio calls, when the primary SIP trunk becomes unavailable.
• The Acme Packet 1100 is the only platform that supports TDM.
• TDM support requires the optional TDM card.
• TDM operations require the configuration of line mode profiles and local policy.
• The available configuration profiles include T1 line mode and E1 line mode.
• The software upgrade procedure supports the TDM configuration.
Note: When the Acme Packet 1100 is deployed in an HA pair, the active system cannot replicate calls between SIP and TDM to the standby system.
For more information, see the Acme Packet 1100 Hardware Installation Guide, the ACLI Configuration Guide, the
Web GUI User Guide, and the Web GUI Help.
3
TDM Configuration
Time Division Multiplexing (TDM) is an option that requires configuration. You must enable TDM on the device, specify the parameters for the TDM interface properties, and configure local policies for inbound and outbound TDM traffic. Two-way TDM call routing requires both inbound and outbound local policies. For inbound-only or outboundonly TDM call routing, the system requires a local policy only for the call direction that you want.
You can configure TDM from either the Acme Command Line Interface (ACLI) or the Web GUI.
• ACLI. Use the tdm-config object from the system group of elements.
• Web GUI - Basic mode. Double-click the TDM icon in the network diagram to display the TDM configuration dialog.
• Web GUI - Expert mode. Use the tdm-config object from the system group of objects.
In addition to configuring the TDM interface properties, you must configure an inbound local policy for traffic entering the TDM interface and an outbound local policy for traffic exiting the TDM interface. In the inbound local policy, you specify tdmRealm for the source realm. In the outbound local policy, you specify the next hop that you want for TDM traffic.
The TDM card always supports bidirectional calls, but TDM call routing can be unidirectional. For example, for inbound-only operations, configure the TDM interface and configure only the inbound TDM policy.
Oracle
®
Enterprise Session Border Controller 119
Time Division Multiplexing (TDM)
If you upgrade from a previous release in which you configured outbound TDM and you want to add inbound TDM, you need only to create the local TDM policy for inbound TDM calls.
You can configure TDM to support either the T1 line mode or the E1 line mode. You can configure all TDM properties, except for line mode, in realtime. For example, changing the default T1 line mode to the E1 line mode requires a system reboot.
After configuring TDM, you must save and activate the configuration. Activating the TDM configuration generates the tdm-config template, which you can view by way of the show running-config generated command. except for line mode
Note: The TDM configuration template includes the media-sec-policy object only when the SRTP license is activated. See "Licensing for Time Division Multiplexing (TDM)."
Configure TDM - Basic
You can configure Time Division Multiplexing (TDM) from the Configuration page on the Web GUI in Basic Mode.
• You must have Superuser permissions.
• Confirm that the optional TDM card is present in the device.
• Confirm that logging is enabled for the system, if you want to enable TDM logging in this procedure.
To activate TDM, you must enable TDM and create a profile that specifies the TDM interface. The following procedure is provided as an example of a typical configuration. In this procedure, some profile parameters are specific to the selected line mode. For example, if you select the T1 line mode, you must select 1-23 for B channel. Configure the remaining settings according to the requirements of your deployment.
For signalling, use one of the following settings:
• pri_net, if you want the TDM card to use the internal clock as the source for timing.
• pri_cpe, if you want the TDM card to use an external clock as the source for timing.
1. From the Web GUI in Basic mode, and click the Configuration tab.
The system displays the TDM icon on the network diagram.
2. Double-click the TDM icon.
The system displays the TDM configuration dialog.
3. Select State to enable TDM.
4. (Optional) Select Logging to enable logging.
5. Click tdm-profile to display the property fields for the TDM profile.
6. Configure values for the following TDM profile parameters: a) Name. Enter a name for this TDM profile.
b) Select T1 or E1.
c) Signaling. Select either pri_net or pri-cpe.
d) Switch type. Select a switch type for this configuration.
e) B channel. For T1, select 1-23. For E1, select 1-15,17-31.
f) D channel. For T1, select 24. For T1, select 16.
g) Span number. Enter 0.
h) Line build out. Enter a number from 0 to133.
i) Framing value. For T1, select ESF. For E1, select CCS.
j) Coding value. For T1, select b8zs. For E1, select hdb3.
k) Tone zone. For T1, select US. For E1, select ES.
l) Rx gain. Optional—Set the TDM Receive channel volume in decibels. Maximum value is 9.9.
m) Tx gain. Optional—Set the TDM Transmit channel volume in decibels. Maximum value is 9.9.
n) Echo cancellation. Select to enable.
7. Click OK.
8. Save and activate the configuration.
120 Oracle
®
Enterprise Session Border Controller
Time Division Multiplexing (TDM)
Configure the inbound and outbound TDM local policies.
Configure TDM for T-carrier (T1) - Expert
You can activate Time Division Multiplexing (TDM) from the Web GUI in Expert Mode by way of the tdm-config object.
• You must have Superuser permissions.
• Confirm that the optional TDM card is present in the device.
• Confirm that logging is enabled for the system, if you want to enable TDM logging in this procedure.
• Confirm that the system displays the Expert mode.
To activate TDM, you must enable TDM and create a profile that specifies the TDM interface. The following procedure is provided as an example of a typical configuration. In this procedure, you must use the profile parameters that correspond to the T1 line mode. Configure the remaining settings according to the requirements of your deployment.
For signalling, use one of the following settings:
• pri_net, if you want the TDM card to use the internal clock as the source for timing.
• pri_cpe, if you want the TDM card to use an external clock as the source for timing.
Note: The Options element is inactive in some releases.
1. From the Web GUI, click Configuration > system > tdm-config.
2. On the Modify tdm-config page, do the following:
• Select State to enable TDM.
• (Optional) Select Logging to enable TDM logging.
• Click tdm-profile to display the property fields for the TDM profile.
3. In the tdm-profile property fields, do the following:
• Name. Enter a name for this TDM profile.
• Line mode. Select T1.
• Signalling. Select either pri_net or pri-cpe form the drop down list.
• Switch type. Select the type of switch to use for TDM.
• B channel. Select 1-23 for T1.
• D channel. Select 24 for T1.
• Span number. Enter 1.
• Line build out. Enter 0.
• Framing value. Select esf for T1.
• Coding value. Select b8zs for T1.
• Tone zone. Select us for T1.
• Rx gain. (Optional). Set the TDM Receive channel volume in decibels. Maximum value is 9.9.
• Tx gain. (Optional). Set the TDM Transmit channel volume in decibels. Maximum value is 9.9.
• Echo cancellation. Select to enable.
• Options.
4. Click OK.
5. Save and activate the configuration.
Configure the next-hop attribute and realm name in the local policy attributes. See "Configure Local Policy - Time
Division Multiplexing (TDM) - Expert."
Configure TDM for E-carrier (E1) - Expert
You can activate Time Division Multiplexing (TDM) from the Web GUI in Expert Mode by way of the tdm-config object.
Oracle
®
Enterprise Session Border Controller 121
Time Division Multiplexing (TDM)
• You must have Superuser permissions.
• Confirm that the optional TDM card is present in the device.
• Confirm that logging is enabled for the system, if you want to enable tdm logging in this procedure.
• Confirm that the system displays the Expert mode.
To activate TDM, you must enable TDM and create a profile that specifies the TDM interface. The following procedure is provided as an example of a typical configuration. In this procedure, you must use the profile parameters that correspond to the E1 line mode. Configure the remaining settings according to the requirements of your deployment.
For signalling, use one of the following settings:
• pri_net, if you want the TDM card to use the internal clock as the source for timing.
• pri_cpe, if you want the TDM card to use an external clock as the source for timing.
Note: The Options element is inactive in some releases.
1. From the Web GUI, click Configuration > system > tdm-config.
2. On the Tdm config page, do the following:
• Select State to enable TDM.
• (Optional) Select Logging to enable TDM logging.
• Click tdm-profile to display the TDM profile configuration fields.
3. In the TDM profile properties fields, do the following:
• Name. Enter a name for this TDM profile.
• Line mode. Select E1.
• Signalling. Select either pri_net or pri-cpe form the drop down list.
• Switch type. Select the type of switch to use for TDM.
• B channel. Select 1-15,17-31 for E1.
• D channel. Select 16 for E1.
• Span number. Enter 1.
• Line build out. Enter 0.
• Framing value. Select CCS for E1.
• Coding value. Select hdb3 for E1.
• Tone zone. Select es for E1.
• Rx gain (Optional). Set the TDM Receive channel volume in decibels. Maximum value is 9.9.
• Tx gain (Optional). Set the TDM Transmit channel volume in decibels. Maximum value is 9.9.
• Echo cancellation. Select to enable.
• Options.
4. Click OK.
5. Save and activate the configuration.
Configure the next-hop attribute and realm name in the local policy attributes. See "Configure Local Policy - Time
Division Multiplexing (TDM) - Expert."
Configure Outbound Local Policy with TDM Backup - Basic
To complete the Time Division Multiplexing (TDM) configuration for redundancy, you must configure the outbound
TDM local routing policy.
• Confirm that a TDM configuration exists.
• Confirm that the system displays the Basic mode.
In the following procedure, you must draw the outbound local routing policy arrow from the PBX icon to the Trunk icon because the system supports TDM operations only from the PBX to the Trunk. If you draw the outbound local routing policy arrow from the Trunk icon to the PBX icon, you cannot configure this policy for TDM.
122 Oracle
®
Enterprise Session Border Controller
Time Division Multiplexing (TDM)
1. From the Web GUI, click Configuration.
2. From the icon toolbar, under Routing, click the unidirectional arrow icon.
3. Click the center of the PBX icon.
The system displays an arrow in the center of the PBX icon.
4. Drag from the arrow in the center of the PBX icon to the Trunk icon.
The system displays the Add One-Way Route Information dialog.
5. In the Add One-Way Route Information dialog, do the following: a) Route name – Enter a name for this policy. For example, TDM Policy.
b) Route cost – Optional. Enter a cost for this routing policy.
c) From address – Enter the PBX address.
d) To address – Enter the address of the Trunk.
e) TDM – Select TDM.
f) TDM profile name – Select the TDM configuration profile from the drop down list.
6. Click OK.
7. Save and activate the configuration.
Configure TDM Outbound Local Policy - Expert
To complete the outbound Time Division Multiplexing (TDM) configuration, you must add TDM to the Next hop attribute in the local policy.
• Configure TDM.
• Confirm that the system displays the Expert mode.
You must select the TDM configuration for the Next hop attribute. You can select any realm for TDM.
1. From the Web GUI, click Configuration > session-router > local-policy.
2. Under Policy-attributes, click Add.
3. In the Add local-policy / policy-attribute dialog, do the following:
• Next hop. Select the tdm configuration from the drop down list.
• Realm. Select the realm that you want for TDM.
4. Click OK.
5. Save and activate the configuration.
Disable TDM - Basic
You can disable Time Division Multiplexing (TDM) from the Configuration page on the Web GUI in Basic Mode.
You must have Superuser permissions.
To disable TDM logging from the Web GUI, deselect the Logging option on the TDM Configuration dialog in Basic mode.
1. From the Web GUI, click the Configuration tab.
The system displays the TDM icon on the network diagram.
2. Double-click the TDM icon.
The system displays the TDM configuration dialog.
3. Deselect State to disable TDM.
4. Click OK.
5. Save and activate the configuration.
Remove tdm from the next-hop and realm attributes in the local policy.
Disable TDM - Expert
You can disable Time Division Multiplexing (TDM) from the Web GUI in Expert mode.
Oracle
®
Enterprise Session Border Controller 123
Time Division Multiplexing (TDM)
• You must have Superuser permissions.
• Confirm that the system displays the Expert mode.
To disable TDM from the Web GUI, use the tdm-config object that is available in the Expert configuration mode.
1. From the Web GUI, click Configuration > system > tdm-config.
2. On the Modify tdm-config page, deselect State.
3. Click OK.
4. Save and activate the configuration.
Remove tdm from the next-hop and realm attributes in the local policy.
Enable TDM Logging - Basic
You can enable Time Division Multiplexing (TDM) logging from the Configuration page on the Web GUI in Basic
Mode.
• You must have Superuser permissions.
• Confirm that logging is enabled for the system.
To enable TDM logging from the Web GUI in Basic mode, select the Logging option on the TDM Configuration dialog.
1. From the Web GUI, click Configuration.
The system displays the TDM icon on the network diagram.
2. Double-click the TDM icon.
The system displays the TDM configuration dialog.
3. Select Logging to enable TDM logging.
4. Click OK.
5. Save and activate the configuration.
Disable TDM Logging - Basic
You can disable Time Division Multiplexing (TDM) logging from the Configuration page on the Web GUI in Basic
Mode.
You must have Superuser permissions.
You disable TDM logging by deselecting the Logging option on the TDM Configuration dialog.
1. From the Web GUI, click Configuration.
The system displays the TDM icon on the network diagram.
2. Double-click the TDM icon.
The system displays the TDM configuration dialog.
3. Deselect Logging to disable TDM logging.
4. Click OK.
5. Save and Activate the configuration.
Enable TDM Logging - Expert
You can enable Time Division Multiplexing (TDM) logging from the Web GUI.
• You must have Superuser permissions.
• Confirm that logging is enabled for the system.
• Confirm that the system displays the Expert mode.
To enable TDM logging from the Web GUI in Expert mode, use the tdm-config object that is available in the Expert configuration mode.
1. From the Web GUI, click Configuration > system > tdm-config.
124 Oracle
®
Enterprise Session Border Controller
Time Division Multiplexing (TDM)
2. On the Modify tdm-config page, select Logging.
3. Click OK.
4. Save and activate the configuration.
Disable TDM Logging - Expert
You can disable Time Division Multiplexing (TDM) logging from the Web GUI.
• You must have Superuser permissions.
• Confirm that the system displays the Expert mode.
To disable TDM logging from the Web GUI, use the tdm-config object that is available in the Expert configuration mode.
1. From the Web GUI, click Configuration > system > tdm-config.
2. On the Modify tdm-config page, deselect Logging.
3. Click OK.
4. Save and activate the configuration.
Edit the TDM Profile - Basic
You can edit the Time Division Multiplexing (TDM) profile from the Configuration page on the Web GUI in Basic
Mode.
You must have Superuser permissions.
To edit the TDM profile from the Web GUI, display the TDM configuration dialog.
1. From the Web GUI, click Configuration.
The system displays the TDM icon on the network diagram.
2. Double-click the TDM icon.
The system displays the TDM configuration dialog.
3. Edit the TDM configuration, as needed.
4. Click OK.
5. Save and activate the configuration.
Edit the TDM Profile - Expert
You can edit the Time Division Multiplexing (TDM) profile from the Web GUI.
• You must have Superuser permissions.
• Confirm that the system displays the Expert mode.
To edit the TDM profile from the Web GUI, use the tdm-config object that is available in the Expert configuration mode.
1. From the Web GUI, click Configuration > system > tdm-config.
2. On the Modify tdm-config page, expand tdm-profile, and edit the profile information.
3. Click OK.
4. Save and activate the configuration.
View the TDM Profile - Basic
You can view the Time Division Multiplexing (TDM) profile from the Configuration page on the Web GUI in Basic
Mode.
To view the TDM configuration from the Web GUI in Basic mode, display the TDM Configuration dialog.
1. From the Web GUI, click Configuration.
The system displays the TDM icon on the network diagram.
Oracle
®
Enterprise Session Border Controller 125
Time Division Multiplexing (TDM)
2. Double-click the TDM icon.
The system displays the TDM configuration dialog.
View the TDM Profile - Expert
You can view the Time Division Multiplexing (TDM) profile from the Web GUI in Expert mode.
Confirm that the system displays the Expert mode.
To view the TDM profile from the Web GUI in Expert mode, use the tdm-config object that displays in the Expert configuration mode.
1. From the Web GUI, click Configuration > system > tdm-config.
2. On the Modify tdm-config page, expand tdm-profile.
126 Oracle
®
Enterprise Session Border Controller
4
High Availability (HA)
High Availability (HA) is a network configuration used to ensure that planned and unplanned outages do not disrupt service. In an HA configuration, Oracle Enterprise Session Border Controllers (E-SBC) are deployed in a pair to deliver continuous high availability for interactive communication services. Two E-SBCs operating in this way are called an HA node. The HA node design ensures that no stable call is dropped in the event of an outage.
In an HA node, one E-SBC operates in the active mode and the other E-SBCoperates in the standby mode.
• Active. The active member of the HA node is the system actively processing signal and media traffic. The active member continuously monitors itself for internal process and IP connectivity health. If the active member detects a condition that can interrupt or degrade service, it hands over its role as the active member of the HA node to the standby member.
• Standby. The standby member of the HA node is the backup system. The standby member is fully synchronized with active member's session status, but it does not actively process signal and media traffic. The standby member monitors the status of the active member and it can assume the active role without the active system having to instruct it to do so. When the standby system assumes the active role, it notifies network management using an
SNMP trap.
To produce a seamless switch over from one E-SBC to the other, the HA node members share their virtual MAC and virtual IP addresses for the media interfaces in a way that is similar to Virtual Router Redundancy Protocol (VRRP).
Sharing these addresses eliminates the possibility that the MAC address and the IPv4 address set on one E-SBC in an
HA node will be a single point of failure. Within the HA node, the E-SBCs advertise their current state and health to one another in checkpointing messages to apprise each one of the other one's status. Using the Oracle HA protocol, theE-SBCs communicate with UDP messages sent out and received on the rear interfaces. During a switch over, the standby E-SBC sends out an ARP request using the virtual MAC address to establish that MAC address on another physical port within the Ethernet switch. To the upstream router, the MAC address and IP address are still alive.
Existing sessions continue uninterrupted.
The E-SBC establishes active and standby roles in the following ways.
• If an E-SBC boots up and is alone in the network, it is automatically the active system. If you pair a second E-
SBC with the first one to form an HA node, the second system automatically establishes itself as the standby.
• If both E-SBCs in the HA node boot up at the same time, they negotiate with each other for the active role. If both systems have perfect health, then the E-SBC with the lowest HA rear interface IPv4 address becomes the active E-
SBC. The E-SBC with the higher HA rear interface IPv4 address becomes the standby E-SBC.
If the rear physical link between the twoE-SBCs is unresponsive during boot up or operation, both will attempt to become the active E-SBC. In this circumstance, processing does not work properly.
Oracle
®
Enterprise Session Border Controller 127
High Availability (HA)
High Availability on the Acme Packet 1100
The Acme Packet 1100 supports High Availability (HA) for all calls on the media interface, but configuration differs from other Oracle Enterprise Session Border Controllers (E-SBC) because it provides 3, rather than 4, interfaces.
The Acme Packet 1100 provides 1 management interface and 2 media interfaces. On E-SBCs with 4 interfaces, you use wancom1 or 2 for name and 0 for thesub-port-id. To configure the Acme Packet 1100 for HA, you create a second management interface object with wancom0 for the name and VLAN for the sub-port-id.
Note: The Acme Packet 1100 E-SBC does not support High Availability (HA) for any call using the Time
Division Multiplexing (TDM) interface.
Configure the Acme Packet 1100 for HA
The details in the procedures for configuring High Availability (HA) on the Acme Packet 1100 differ from configuring HA for other models of the Oracle Enterprise Session Border Controller because the Acme Packet 1100 has a single management interface and it shares the wancom0 port for HA operations.
Use the following Expert mode procedures to configure the Acme Packet 1100 for HA operations. You must perform the physical interface configuration twice. One configuration sets the Management operations the other configuration sets the Media operations.
Procedure
1. Configure the physical interface for management. See "Configure the Physical Interface."
2. Configure the physical interface for media. See "Configure the Physical Interface."
3. Configure the network interface with addresses for the Primary and Secondary devices. See "Configure the
Network Interface."
4. Configure the peers for redundancy. See "Configure Redundancy."
Physical Interface Configuration - Expert
In Expert mode, use the phy-interface object to configure the type of physical interface and the parameters for its operation.
The following table describes the parameters that you can configure on the physical interface. For configuration instructions, see "Configure the Physical Interface for Control - Expert" and "Configure the Physical Interface for
Media - Expert."
Field
Name
Operation type
Description
Enter a unique name for this physical interface, using the name format. The name for Control and Maintenance physical interfaces must begin with “wancom.”
The physical interface performs the following types of operations. You must perform the phy-interface configuration procedure for each type of operation.
Default is Control.
• Media. Front-panel interfaces only. Port: 0-3. Slot: 0 or 1.
• Control. Rear-panel interfaces only. Port 0, 1, or 2
Slot: 0.
• Maintenance. Rear-panel interfaces only. Port 0, 1, or
2 Slot: 0.
128 Oracle
®
Enterprise Session Border Controller
Field
Port
Slot
Virtual mac
Admin state
Auto negotiation
Duplex mode
Speed
Wancom health score
High Availability (HA)
Description
The physical port number on an interface of the phyinterface being configured. Default is zero (0). Valid values are:
• 0-2 for rear-panel interfaces
• 0-1 for two possible GigE ports on front of Oracle
Enterprise Session Border Controller (E-SBC)chassis
• 0-3 for four possible FastE ports on front of E-SBC chassis
The physical slot number on the Oracle Enterprise
Session Border Controller chassis. Default is zero. Valid values are:
• 0 is the motherboard (rear-panel interface) if the name begins with "wancom." 0 is the left Phy media slot on front of Oracle Enterprise Session Border
Controller chassis.
• 1 is the right Phy media slot on front of Oracle
Enterprise Session Border Controller chassis.
Required for High Availability (HA) configuration.
Enter the MAC address identifying a front-panel interface when the E-SBC is in the Active state.
Generate this field value from the unused MAC addresses assigned to a E-SBC.
Media interface, only.
Media interface, only.
The 10/100 Phy card interfaces located on the front panel of the E-SBC can operate in full-duplex mode or halfduplex mode. Default is full.
Media interface, only. The speed in Mbps of the frontpanel 10/100 Phy interfaces. This field is used only if the auto-negotiation field is set to disabled for 10/100 Phy cards. Default is 100.
The amount to subtract from the E-SBC health score if a rear interface link goes down. Default is 50. Valid values are 0-100.
Configure the Physical Interface for Control - Expert
You must configure the physical interface of the Oracle Enterprise Session Border Controller to connect to the network for control operations.
Note the settings that you want for this interface. For information about the configuration settings, see "Physical
Interface Configuration."
In Expert mode, use the phy-interface object to configure the physical interface for the operation type Control.
1. From the Web GUI, go to Configuration > Objects > System > phy-interface.
2. On the phy-interface page, click Add.
3. On the Add phy-interface page, click Show Advanced.
4. In the Add phy-interface dialog, do the following:
Oracle
®
Enterprise Session Border Controller 129
High Availability (HA)
• Name. Enter “wancom0.”
• Operation type. Select Control from the operation type drop down list.
• Port. Enter 0.
• Slot. Enter 0.
5. Click OK.
6. Save and Activate the configuration.
Configure the Media Interface. See "Media Interface Configuration" and "Configure the Physical Interface for Media
- GUI Expert."
Configure the Physical Interface
You must configure the physical interface of the Oracle Enterprise Session Border Controller to connect to the network.
Before You Begin
• Confirm that the system displays the Expert mode.
Use the phy-interface object to configure the physical interface for control, media, and maintenance operations.
Perform this procedure for each operation type, which you will select in step 4.
Procedure
1. From the Web GUI, click Configuration > Objects > System > phy-interface.
2. On the phy-interface page, click Add.
3. On the Add phy-interface page, click Show Advanced.
4. In the Add phy-interface dialog, do the following:
Field
Name
Operation type
Description
Enter a unique name for this physical interface, using the name format. For Control and Maintenance physical interfaces, the name must begin with
“wancom.”
Select the type of operation for this physical interface configuration. You must perform the phy-interface configuration procedure for each type of operation.
Default: Control.
• Media
• Control
• Maintenance
Port
Slot
Enter the physical port number for the operation type.
• Media. Front-panel interfaces only. Port: 0-3.
• Control. Rear-panel interfaces only. Port 0-2.
• Maintenance. Rear-panel interfaces only. Port 0-2.
Enter the physical slot number for the operation type.
• Media. Front-panel interfaces only. Slot: 0 or 1.
• Control. Rear-panel interfaces only. Slot: 0.
• Maintenance. Rear-panel interfaces only. Slot: 0.
• 0 is the motherboard (rear-panel interface), if the name begins with "wancom."
130 Oracle
®
Enterprise Session Border Controller
High Availability (HA)
Field Description
• 0 is the left Phy media slot on the front of the chassis.
• 1 is the right Phy media slot on the front of the chassis.
Virtual mac
Admin state
Auto negotiation
Duplex mode
Enter the virtual MAC address for this interface in hexadecimal format.
Select to enable the administrative state of the Media interface. Not applicable for Control and Maintenance interfaces.
Select to enable auto negotiation on the Media interface. Not applicable for Control and Maintenance interfaces.
Select the duplex mode for the Media interface.
Default: Full.
Speed
Wancom health score
Select the speed for the Media interface. Required only when auto-negotiation is set to disabled for 10/100 Phy cards. Default: 100.
The amount to subtract from the E-SBC health score, if the wancom link goes down. Default: 50. Range:
0-100.
5. Click OK.
6. Save and activate the configuration.
Next Steps
• Configure the Network Interface. See "Configure the Network Interface."
Network Interface Configuration - Expert
In Expert mode, use the network-interface object to configure the parameters for the network interface.
The network interface element specifies a logical network interface over which you can configure one or more application (SIP) interfaces. The Oracle Enterprise Session Border Controller (E-SBC)supports only one network interface.
The following table describes the parameters that you can configure on the network interface. For configuration instructions, see "Configure the Network Interface."
Configuration Element
Name
Sub port ID
Description
The name of the physical interface with which this network-interface element is linked. The name for network-interface elements that correspond to the phyinterface Control and Maintenance operation types must start with “wancom.”
The identification of a specific virtual interface in a physical interface (e.g., a VLAN tag). A value of 0 indicates that this element is not using a virtual interface.
The sub-port-id field value is required only if the operation type is Media. Default is zero (0). Valid values are 0- 4095.
Oracle
®
Enterprise Session Border Controller 131
High Availability (HA)
Configuration Element
Description
Hostname
IP address
Pri utility addr
Sec utility addr
Netmask
Gateway gw heartbeat
DNS IP primary
DNS IP backup1
DNS domain
HIP IP list
Description
A description of this network interface.
Optional. The hostname of this network interface in
Fully Qualified Domain Name (FQDN) format or IP address format.
Required. The IP address of this network interface in the
IP address format.
The utility IP address for the primary peer in an HA pair.
The utility IP address for the secondary peer in an HA pair.
The netmask portion of the IP address for this network interface entered in IP address format. The networkinterface element will not function properly unless this field value is valid.
A description for this host route. Valid values are alphanumeric characters.
• State. Enable or disable front interface link detection and polling functionality on the E-SBC for this network-interface element. Default is enabled.
• Heartbeat. The time interval in seconds between heartbeats for the front interface gateway. Default is zero (0). Valid values are 0-65535.
• Retry count. Enter the number of front interface gateway heartbeat retries before a gateway is considered unreachable. Default is zero (0). Valid values are 0- 65535.
• Retry timeout. The heartbeat retry timeout value in seconds. Default is 1. Valid values are1-65535.
• Health score. The amount to subtract from the health score if the front interface gateway heartbeat stops responding. (i.e. expires) The health score will be decremented by the amount set in this field if the timeout value set in the gw-heartbeat: retry timeout.
Valid values are 0 -100.
The IP address of the primary DNS to be used for this interface.
The IP address of the first backup DNS to be used for this interface.
The default domain name used to populate incomplete hostnames that do not include a domain. Entries must follow the name format.
A list of IP addresses allowed to access signaling and maintenance protocol stacks by way of this front interface using the HIP feature.
132
Configure the Network Interface
You must configure the network interface of the Oracle Enterprise Session Border Controller (E-SBC) to communicate with the physical interface and the network.
Oracle
®
Enterprise Session Border Controller
High Availability (HA)
Before You Begin
• Confirm that the physical interface is configured. For more information, see "Physical Interface Configuration."
• Confirm that the system displays the Expert mode.
Use the network-interface object to configure the parameters for the network interface, which specifies a logical network interface over which you can configure one or more application SIP interfaces. Note that the E-SBC supports only one network interface.
Procedure
1. From the Web GUI, click Configuration > Objects > System > network-interface.
2. On the network-interface page, click Add.
3. On the Add network-interface page, click Show Advanced.
4. In the Add network-interface dialog, do the following:
Attributes
Name
Instructions
Sub port ID
Description
Hostname
IP address
Pri utility addr
Sec utility addr
Netmask
Gateway
Enter the name of the physical interface linked to this network interface. Control and Maintenance operation types must start with “wancom.”
Enter the sub port ID to identify a specific virtual interface in a physical interface (e.g., a VLAN tag). A value of 0 indicates that this element is not using a virtual interface. The sub-port-id field value is required only if the operation type is Media. Default: 0. Range:
0-4095.
Enter a description of this network interface.
Enter the hostname of this network interface in Fully
Qualified Domain Name (FQDN) format or IP address format.
The IP address of this network interface in the IP address format.
Enter the utility IP address of the primary peer in an
HA pair.
Enter the utility IP address of the secondary peer in an
HA pair.
Enter the netmask portion of the IP address for this network interface in IP address format.
Enter a description for this host route. Alpha-numeric characters.
Gw heartbeat
• State. Select to enable front interface link detection and polling functionality on the E-SBC for this network-interface element. Default: enabled.
• Heartbeat. Enter the time interval in seconds between heartbeats for the front interface gateway.
Default: 0. Range: 0-65535.
• Retry count. Enter the number of front interface gateway heartbeat retries before a gateway is considered unreachable. Default: 0. Range: 0-
65535.
Oracle
®
Enterprise Session Border Controller 133
High Availability (HA)
Attributes Instructions
DNS IP primary
DNS IP backup1
DNS IP backup 2
DNS domain
DNS timeout
Signalling mtu
HIP IP list
• Retry timeout. Enter the heartbeat retry timeout value in seconds. Default: 1. Range: 1-65535.
• Health score. Enter the amount to subtract from the health score if the front interface gateway heartbeat expires. Range: 0 -100.
Enter the IP address of the primary DNS to use for this interface.
Enter the IP address of the first backup DNS to use for this interface.
Enter the IP address of the second backup DNS to use for this interface.
Enter the default domain name associated with this interface. Entries must follow the name format.
Enter the maximum waiting time for a DNS response in seconds. Range: 0-4294967295.
Enter the Maximum Transmission Unit (MTU) size for signalling packets. Default: 0. Range: 576-4096.
Create a list of IP addresses allowed to access signaling and maintenance protocol stacks by way of this front interface using the Hosted IP (HIP) feature.
Click Add, enter the HIP IP address, and do one of the following:
• Click OK.
• Click Apply/Add another, add another HIP IP address, and click OK. Repeat, as needed.
Ftp address
ICMP address
Enter the FTP address.
Create a list of Internet Control Message Protocol
(ICMP) addresses.
Click Add, enter the ICMP address, and do one of the following:
• Click OK.
• Click Apply/Add another, add another ICMP address, and click OK. Repeat, as needed.
Telnet address
Ssh address
Enter the Telnet address.
Enter the SSH IP address. The gateway address of this interface must be default gateway.
5. Click OK.
6. Save and Activate the configuration.
Next Steps
• For High Availability (HA), configure redundancy. See "Redundancy Configuration" and "Configure
Redundancy."
134 Oracle
®
Enterprise Session Border Controller
High Availability (HA)
Redundancy Configuration - Expert
In Expert mode, configure redundancy for a High Availability (HA) pair.
The following table describes the parameters that you must configure for HA redundancy. For configuration instructions, see "Configure Redundancy."
Configuration Element
Name
State
Type
Description
The name of the HA node peer as it appears in the target name boot parameter. This is also the name of the system that appears in the system prompt. For example, in the system prompt ACMEPACKET#, ACMEPACKET is the target name for that Oracle Enterprise Session Border
Controller (E-SBC).
Enable or disable HA for the E-SBC. Default is enabled.
These values refer to the primary and secondary utility addresses in the network interface configuration. To determine what utility address to use for configuration checkpointing, set the type of E-SBC to either primary or secondary. You must change this field from unknown, which is the default. Valid values are:
• Primary. Set this type if you want the E-SBC to use the primary utility address.
• Secondary. Set this type if you want the E-SBC to use the secondary utility address.
• Unknown. If you leave this parameter set to this default value, the system cannot perform configuration checkpointing.
Configure Redundancy - Expert
You must configure the parameters to support redundancy for a High Availability (HA) pair of Oracle Enterprise
Session Border Controller (ESBC) devices.
Confirm that the physical interface for Control, the physical interface for Media, and the Network interface on the primary ESBC are configured for HA pairing. See "Physical Interface Configuration" and "Network Interface
Configuration."
In Expert mode, configure redundancy for High Availability (HA) pairing of the primary ESBC and the secondary
ESBC. Perform this procedure for the primary ESBC.
1. From the Web GUI, go to Configuration > Objects > System > redundancy-config.
2. On the Add redundancy config page, click Add.
3. In the Add redundancy config/peer dialog, do the following: a) Name. Enter the name of the HA peer as it appears in the target name boot parameter.
b) State. Select enable.
c) Type. Select primary.
d) Destinations. Click Add.
4. In the Add redundancy-config / peer / destination dialog, do the following: a) Address. Enter the pri-utility address from the network interface.
b) Network interface. Type wancom0:<VLAN>.
5. Click OK.
6. Click Back.
The system displays the Modify redundancy-config page.
Oracle
®
Enterprise Session Border Controller 135
High Availability (HA)
7. In the Modify redundancy-config dialog, do the following: a) Click Add.
b) Name. Enter the name of the secondary peer.
c) State. Select State.
d) Type. Select secondary from the drop down list.
8. Click Show Advanced.
The system displays the destinations dialog.
9. In the destinations dialog, do the following: a) Click Add.
b) Address. Enter the sec-utility address from the network interface.
c) Network interface. Select wancom0:<VLAN> from the drop down list.
10. Click OK.
11. Save and Activate the configuration.
• Reboot the system.
Configure the Acme Packet 1100 Primary for HA - Basic
You can configure the Acme Packet 1100 primary for High Availability (HA) operations from the Web GUI by using the configuration tools in Basic mode.
Confirm that the Oracle Enterprise Session Border Controller software is installed on two separate systems.
You must perform the following procedure on the primary system before configuring the secondary system for HA operations.
1. On the Web GUI, click Configuration > Wizards > Set initial configuration > Run Setup.
The system displays the Set initial configuration dialog.
2. In the Set initial configuration dialog, do the following:
• Select Yes to enable the Web GUI.
• Select Basic Web GUI mode.
• Select high availability SBC mode.
• Select primary.
• Enter the IP address of the management interface on the primary.
• Enter a unique target name for the primary.
• Enter the subnet mask.
• Enter the number of the management interface VLAN. The range is 0-4095.
• Enter the gateway IP address.
• Peer target name. Enter the name of the secondary.
• Redundancy interface switch. Enter the VLAN configured on the management switch.
3. Click Complete.
The system reboots.
Configure the secondary for High Availability. See "Configure the Acme Packet 1100 Secondary for High
Availability (HA) - GUI Basic."
Configure the Acme Packet 1100 Secondary for HA - Basic
You can configure the Acme Packet 1100 secondary for High Availability (HA) operations from the Web GUI by using the configuration tools in Basic mode.
Confirm that the Oracle Enterprise Session Border Controller primary is configured for HA operations.
136 Oracle
®
Enterprise Session Border Controller
High Availability (HA)
When configuring the secondary system, enter the same management interface VLAN that you entered for the primary system.
1. On the Web GUI, click Configuration > Wizards > Set initial configuration > Run Setup.
The system displays the Set initial configuration dialog.
2. In the Set initial configuration dialog, do the following:
• Select Yes to enable the Web GUI.
• Select Basic Web GUI mode.
• Select high availability SBC mode.
• Select secondary.
• Enter the IP address of the management interface on the secondary.
• Enter a unique target name for the secondary.
• Enter the subnet mask.
• Enter the number of the management interface VLAN. The range is 0-4095.
• Enter the gateway IP address.
• Select Yes to acquire the configuration from the primary.
• Redundancy interface switch. Enter the VLAN configured on the management switch.
3. Click Complete
The system reboots.
Oracle
®
Enterprise Session Border Controller 137
5
Monitor and Trace Tab
The Monitor and Trace tab displays the results of filtered SIP session data from the Oracle Enterprise Session Border
Controller. The page displays the results in a common log format for local viewing.
Monitor and Trace supports the following summary reports that you can export to a PC.
• Sessions
• Registrations
• Subscriptions
• Notable events
Each report provides sorting, searching, and paging functionality. You can customize the columns in each report and use the buttons on the page to display additional information or to perform a task.
The SIP Monitor and Trace function can store messages per session and it can store cumulative sessions across all report types. Once the sessions maximum is reached, the system removes the oldest call and adds the newest call.
• On systems with less than 4GB of RAM, the system can store:
• 50 messages
• 2,000 sessions
• On systems with more than 4GB of RAM, the system can store:
• 50 messages
• 4,000 sessions
The call database is not persistent across reboots
The system can perform live paging from Monitor and Trace tables.
The system displays the Realm Configuration when you click a cell in the RealmID column in a table in Expert mode.
Configure SIP Monitoring
You must enable sip-monitoring and configure the options for displaying session data and notable event data on the
Monitor and Trace page.
Before You Begin
• Configure any filters that you want, if you don't want to monitor all SIP traffic. See "Filter Configuration."
• Confirm that the Web GUI is in Expert mode.
Oracle
®
Enterprise Session Border Controller 139
Monitor and Trace Tab
The only required setting is State, which enables sip-monitoring. You can optionally monitor all filters and you can specify one or more filters to monitor. You can specify a time for short session duration monitoring and you can configure interesting events to monitor.
Procedure
1. From the web GUI, click Configuration > Session-Router > SIP-Monitoring.
2. On the Modify sip-monitoring page, click Show advanced, and do the following.
Attributes
Match any filter
State
Short session duration
Monitoring filters
Instructions
Select to monitor all SIP traffic. Default: Disabled.
Select to enable SIP monitoring.
Enter a value, in seconds, for the maximum session duration of a short session. Default: 0. Range
0-999999999.
Create a global list of monitoring filters.
Click Add, enter the name of the filter, and do one of the following:
• Click OK.
• Click Apply/Add another, add another NTP server, and click OK. Repeat, as needed.
Interesting events Create a global list of interesting events to monitor.
Click Add > Show advanced, and do the following:
• Type. Select an event type from the drop-down list.
• Trigger threshold. Enter the number of events required to occur in within the trigger window before the system starts monitoring. Default: 0.
Range: 0-999999999.
• Trigger timeout. Enter the amount of time, in seconds, that the monitoring persists. Default: 0.
Range: 0-999999999,
• Click OK.
The system displays the SIP monitoring page.
3. Click OK.
4. Save and activate the configuration.
Next Steps
• View SIP Session Summary and SIP Notable Event Summary on the Monitor and Trace tab.
Monitor and Trace SIP Messages
The Monitor and Trace page on the Web GUI displays the results of filtered SIP session data from a Oracle Enterprise
Session Border Controller (E-SBC). The page displays the results in a common log format for local viewing.
When the E-SBC filters the data from a SIP message, it captures the message, applies the Header Manipulation Rules
(HMR), and applies the Session Plug-in Language (SPL) to that message. When the message is sent from the E-SBC, it applies the SPL, applies the HMR, and sends the captured SIP message.
Monitor and Trace supports the following summary reports that you can export to a PC.
140 Oracle
®
Enterprise Session Border Controller
Monitor and Trace Tab
• Hairpin call data
• Notable events
• Registrations
• Sessions
• Siprec call data
• Subscriptions
Each type of report provides sorting, searching, and paging functionality. You can customize the columns in each report and use the buttons on the page to display additional information or perform a task.
The SIP Monitor and Trace function can store up to 100 messages per session and it can store up to 2000 cumulative sessions across all report types. Once the 2000 sessions maximum is reached, the system removes the oldest call and adds the newest call. The call database is not persistent across reboots.
Sessions Report
The Sessions Report is a SIP session summary of all logged call sessions on the Oracle Enterprise Session Border
Controller (E-SBC). When Lightweight Directory Access Protocol (LDAP) is enabled on the Active Directory, LDAP session messages may also display.
The columns that display on the Sessions Report page depend on the columns that you specified in the "Customizing the Page Display" procedure.
The following table describes the columns on the SIP Session Summary page.
Heading
Start Time
State
Description
Timestamp of the first SIP message in the call session.
Status of the call or media session. Valid values are:
INITIAL—Session for which an INVITE or SUBSCRIBE was forwarded.
EARLY—Session that received the first provisional response (1xx other than 100).
ESTABLISHED—Session for which a success (2xx) response was received.
TERMINATED—Session that ended by receiving or sending a BYE for an “Established” session or forwarding an error response for an “Initial” or "Early" session. The session remains in the terminated state until all the resources for the session are freed up.
FAILED—Session that failed due to a 4xx or 5xx error code.
Call ID
Request URI
Identification of the call source. Includes the phone number and source IP address.
Uniform Resource Identifier (URI) formatted string that identifies a resource by way of a protocol, name, location, and any other applicable characteristic that is sent by the E-SBC in
REQUEST headers.
Oracle
®
Enterprise Session Border Controller 141
Monitor and Trace Tab
Heading
From URI
To URI
Duration
Notable Event
Session ID
Ingress Src Addr
Egress Dest Addr
Description
URI formatted string that identifies the call source information.
URI formatted string that identifies the call destination information.
Amount of time, in seconds, that the call or media event was active.
Indicates if a notable event has occurred on the call session. Valid values are: short session—Sessions that do not meet a minimum configurable duration threshold.
Session dialogue, captured media information, and termination signalling. Any event flagged as a short session interesting event.
local rejection—Sessions locally rejected at the E-SBC for any reason, for example, Session
Agent (SA) unavailable, no route found, SIP signalling error, and so on. Session dialogue, capture media information, and termination signalling. Any event flagged as a local rejection interesting event.
Identification assigned to the call session.
Source IP address of the incoming call or media event.
Destination IP address of the outgoing call or media event.
The following table describes the buttons on the SIP Session Summary page.
Button Description
Search
Show all
Ladder Diagram
Use to specify parameters for performing a search for specific session summary records within the current report.
Use to display all of the session summary records in the Sessions Report.
Use to display a Ladder Diagram of a specific record in the table. The Ladder Diagram displays detailed information about a call session or media event.
Export Session Details Use to export the SIP messages and media events associated with the selected session to a file in text format on the local machine.
Export Summary Use to export all logged session summary records to a file in text format on the local machine.
Display a Sessions Report
Procedure
1. From the Web GUI, click Monitor and Trace > Sessions.
The system displays the SIP Session Summary page.
2. Use the buttons on the top of the page to find, view, and export information about the records in the report.
Ladder Diagram
Ladder diagrams in the GUI are logical schematics that show the call and media flow of packets on ingress and egress routes via the Oracle Enterprise Session Border Controller.
Ladder diagrams for the Session Report display the following session summary information:
• Quality of Service (QoS) statistics for call sessions
• SIP messages and media events in time sequence
142 Oracle
®
Enterprise Session Border Controller
Monitor and Trace Tab
To display a ladder diagram for a specific record in the Session Report, you can double-click a record in the summary table OR click <Ladder Diagram> on the Session Report page.
Display a Ladder Diagram
To display a ladder diagram:
On the Sessions Report page, click Ladder diagram, or select a record in the table and double-click on that record. The following is an example of the ladder diagram that displays.
Note: The Oracle Enterprise Session Border Controller (E-SBC) captures SIP messages, applies the Header
Manipulation Rules (HMR) configured on the E-SBC , and then applies the Session Plug-in Language (SPL) to that message. When the message is sent out from the E-SBC, it applies the SPL, the HMR, and then sends out the captured SIP message. Therefore, when viewing the session detail on a Ladder Diagram, the HMR and SPL information may be present.
Oracle
®
Enterprise Session Border Controller 143
Monitor and Trace Tab
144
The Session Record Ladder Diagram consists of the following information:
• Session Summary - summary information about the call or media session in focus.
• SIP Message Details - SIP message and call flow information about the call or media session in focus.
• QoS Statistics - Quality of Service (QoS) statistic information about the call or media session in focus.
You can move your mouse over any statistic in the Ladder Diagram to view additional parameters and associated values for the statistic in a pop-up window.
The following table describes the buttons in this Ladder Diagram window.
Button Description
Exports all of the information in the Ladder Diagram (Session Summary, SIP
Message Details, and QoS statistics), to a file in text format on the local machine.
Exports detailed information about the SIP messages and media events associated with the session in focus, to a file in text format on the local machine.
Closes the Ladder Diagram window.
Session Summary
The Session Summary window in the Ladder Diagram displays an overall summary of the call or media session in focus.
Oracle
®
Enterprise Session Border Controller
Monitor and Trace Tab
Display the Session Summary
To display the Session Summary:
1. In the Ladder Diagram, click the [+] next to Session Summary at the top of the Ladder Diagram window. The
Session Summary window expands. This window displays a summary of information about the call or media session in focus. The following table describes each field in the Session Summary window.
Heading
State
Description
Status of the call or media session. Valid values are:
INITIAL Session for which an INVITE or SUBSCRIBE was forwarded.
EARLY Session received the first provisional response (1xx other than 100).
ESTABLISHED Session for which a success (2xx) response was received.
TERMINATED Session that has ended by receiving or sending a BYE for an
“Established” session or forwarding an error response for an “Initial” or Early session.
The session remains in the terminated state until all the resources for the session are freed up.
FAILED Session that has failed due to a 4xx or 5xx error code.
Duration
From URI
To URI
Ingress Src IP:Port
Egress Src IP: Port
Ingress Dest IP:Port
Egress Dest IP: Port
Amount of time, in seconds, that the call or media session was active.
URI formatted string that identifies the call source information.
URI formatted string that identifies the call destination information.
Source IP address and port number of the incoming call or media session.
Source IP address and port number of the outgoing call or media session.
Destination IP address and port number of the incoming call or media session.
Destination IP address and port number of the outgoing call or media session.
Oracle
®
Enterprise Session Border Controller 145
Monitor and Trace Tab
Heading Description
Ingress Realm
Egress Realm
Ingress Network Intf
Incoming realm name.
Outgoing realm name.
Name of the incoming network interface on the Oracle Enterprise Session Border
Controller (E-SBC).
Egress Network Intf
Ingress Transport
Name of the outgoing network interface on the E-SBC.
Protocol type used on the incoming call or media session. Valid values are User
Datagram Protocol (UDP) or Transport Control Protocol (TCP).
Egress Transport Protocol type used on the outgoing call or media session. Valid values are User
Datagram Protocol (UDP) or Transport Control Protocol (TCP).
2. Click [-] to close the Session Summary window.
SIP Message Details
The SIP Message Detail window displays detailed information and data flow (ingress and egress) about the call or media event.
146
When a session is routed using the a Lightweight Directory Access Protocol (LDAP) configuration (Active Directory) for the local policy, the LDAP information displays in the Session Summary window. The next hop value containing
"enum:…" or "dns:…" displays. Similarly, the next hop value "ldap:…" displays for LDAP queries.
Oracle
®
Enterprise Session Border Controller
Monitor and Trace Tab
SIPREC Call Data
The following diagram shows SIP Monitor and Trace output for a call with media forwarded by way of SIPREC.
Oracle
®
Enterprise Session Border Controller 147
Monitor and Trace Tab
Hairpin Call Data
The following diagram shows SIP Monitor and Trace output for a hairpin call. Note the Media Flow Hairpin indication within the display.
148
SIP Monitor & Trace Ingress Egress Messages
The SM&T feature allows SIP sessions on the Oracle Enterprise Session Border Controller in your network to be monitored. Release E-C[xz]6.4.0 M2 includes a change to the way the Oracle Enterprise Session Border Controller handles SM&T data in ingress and egress messages. It processes SM&T data first on incoming messages and sends the data out last on outgoing messages. This allows the Oracle Enterprise Session Border Controller to capture SIP
Monitor and Trace data over the wire for display in the Web GUI.
The Oracle Enterprise Session Border Controller captures SIP messages, applies the Header Manipulation Rules
(HMR) configured on the Oracle Enterprise Session Border Controller, and then applies the Session Plug-in
Language (SPL) to that message. When the message is sent out from the Net-Net ESD, it applies the SPL, then applies the HMR, and then sends out the captured SIP message.
Oracle
®
Enterprise Session Border Controller
Monitor and Trace Tab
Display SIP Message Details
To display SIP Message Details:
On the Sessions Report page, click Ladder diagram, or select a record in the table and double-click on that record. The SIP Message Details window displays. This window displays the messages and status codes that occurred during the active call session or media event. You can use the information to troubleshoot calls and media events that failed or timed out when trying to connect.
QoS Statistics
The Quality of Service (QoS) window displays information about the quality of the service used on the call session or media event when the call or event was active.
Display QoS Statistics
To display QoS Statistics:
1. In the Ladder Diagram, click the [+] next to QoS Stats at the bottom of the Ladder Diagram window. The QoS window expands. This window displays the QoS statistics for the call session or media event in focus. The following table describes each field in the QoS Statistics window.
Heading
Flow ID
Direction
Description
ID number assigned to the call session or media event flow of data.
The direction of the call or media event flow. Valid values are:
CALLING (egress direction)
CALLED (ingress direction)
Total Pkts Received
Total Octets Received
Total number of data packets received on the interface during the active call session or media event.
Total number of octets received on the interface during the active call session or media event. An octet is a unit of digital information that consists of eight bits.
Oracle
®
Enterprise Session Border Controller 149
Monitor and Trace Tab
Heading Description
RTCP
Pkts Lost
Avg Jitter
Max Jitter
Avg Latency
Max Latency
RTP
Real-time Transport Control Protocol - used to send control packets to participants in a call.
Number of RTCP data packets lost on the interface during the active call session or media event.
Average measure of the variability over time of the RTCP packet latency across a network. A network with constant latency has no variation (or jitter). Jitter is referred to as Packet Delay Variation (PDV). It is the difference in the one-way end-to-end delay values for packets of a flow. Jitter is measured in terms of a time deviation from the nominal packet interarrival times for successive packets.
Maximum measure of the variability over time of the RTCP packet latency across a network. A network with constant latency has no variation (or jitter).
Average observed one-way signaling latency during the active window period.
This is the average amount of time the signaling travels in one direction.
Maximum observed one-way signaling latency during the sliding window period.
This is the maximum amount of time the signaling travels in one direction.
Real-Time Transport Protocol - a standard packet format for delivering audio and video over the internet.
Pkts Lost
Avg Jitter
Max Jitter
QoE
Number of RTP data packets lost on the interface during the active call session or media event.
Average measure of the variability over time of the RTP packet latency across a network. A network with constant latency has no variation (or jitter). Jitter is referred to as Packet Delay Variation (PDV). It is the difference in the one-way end-to-end delay values for packets of a flow. Jitter is measured in terms of a time deviation from the nominal packet interarrival times for successive packets.
Maximum measure of the variability over time of the RTP packet latency across a network. A network with constant latency has no variation (or jitter).
Quality of Experience - measurement used to determine how well the network is satisfying the end user's requirements.
R-Factor Average Quality of Service (QoS) factor observed during the active window period. Quality of service shapes traffic to provide different priority and level of performance to different data flows. R-factors are metrics in VoIP, that use a formula to take into account both user perceptions and the cumulative effect of equipment impairments to arrive at a numeric expression of voice quality. This statistic defines the call or transmission quality expressed as an R factor.
MOS Mean Opinion Score (MOS) score. MOS is a measure of voice quality. MOS gives a numerical indication of the perceived quality of the media received after being transmitted and eventually compressed using Codecs.
2. Click [-] to close the QoS Stats window.
Registrations Report
The Registrations Report is a summary of all logged SIP registrations sessions on the Oracle Enterprise Session
Border Controller.
The columns that display on the Registration Report page are dependent on the columns you selected in the
"Customizing the Page Display" procedure.
150 Oracle
®
Enterprise Session Border Controller
Monitor and Trace Tab
The following table describes the columns on this page.
Heading
Start Time
Call ID
To URI
From URI
Local Expires
Remote Expires
Ingress Realm
Egress Realm
Notable Event
Description
Timestamp of the first SIP message in the call session.
Identification of the call source. Includes the phone number and source IP address.
URI formatted string that identifies the call destination information.
URI formatted string that identifies the call source information.
The current setting for the expiration of a registration request sent from the Integrated Media
Gateway (IMG) to a Remote SIP User Agent. The default is 3600 sec.
The current setting for the expiration of a registration request sent from the Remote SIP User
Agent to the Integrated Media Gateway (IMG). The default is 3600 sec.
Incoming realm name.
Outgoing realm name.
Indicates if a notable event has occurred on the call session. Valid value is: local rejection - Sessions locally rejected at the E-SBC for any reason (for example, Session
Agent (SA) unavailable, no route found, SIP signalling error, etc.); Session dialogue, capture media information and termination signalling; Any event flagged as a local rejection interesting event
Session ID
Ingress Src Addr
Egress Dest Addr
Request URI
Identification assigned to the call session.
Source IP address of the incoming call or media event.
Destination IP address of the outgoing call or media event.
Uniform Resource Identifier (URI) formatted string that identifies a resource via a protocol, name, location, and any other applicable characteristic, and is sent by the E-SBC in
REQUEST headers.
The following table describes the buttons on this page.
Button Description
Search Allows you to specify parameters for performing a search for specific session summary records within the current report.
Oracle
®
Enterprise Session Border Controller 151
Monitor and Trace Tab
Button Description
Show all Displays all of the session summary records in the Session Report.
Ladder Diagram Displays a Ladder Diagram of a specific record in the table. The Ladder Diagram displays detailed information about a call session or media event.
Export Session Details Exports the SIP messages and media events associated with the selected session, to a file in text format on the local machine.
Export Summary Exports all logged session summary records to a file in text format on the local machine.
Display a Registrations Report
Procedure
1. From the Web GUI, click Monitor and Trace > Registrations.
2. Use the buttons on the top of the page to view information about the records in this report.
Subscriptions Report
The Subscriptions Report is a summary of all logged SIP subscription sessions on the Oracle Enterprise Session
Border Controller (E-SBC).
The columns that display on the Subscription Report page are dependent on the columns you selected in the procedure, Customizing the Page Display (11).
152
The following table describes the columns on this page.
Heading
Start Time
Call ID
From URI
To URI
Events
Description
Timestamp of the first SIP message in the call session.
Identification of the call source. Includes the phone number and source IP address.
URI formatted string that identifies the call source information.
URI formatted string that identifies the call destination information.
Specific subscribe event package that was sent from an endpoint to the destination endpoint.
Applicable event packages can be: conference - Event package that allows users to subscribe to a conference Uniform Resource
Identifier (URI).
consent-pending additions - Event package used by SIP relays to inform user agents about the consent-related status of the entries to be added to a resource list.
Oracle
®
Enterprise Session Border Controller
Heading
Local Expires
Remote Expires
Ingress Realm
Egress Realm
Notable Event
Session ID
Ingress Src Addr
Egress Dest Addr
Request URI
Monitor and Trace Tab
Description
dialog - Event package that allows users to subscribe to another user, and receive notifications about the changes in the state of the INVITE-initiated dialogs in which the user is involved.
message-summary - Event package that carries message-waiting status and message summaries from a messaging system to an interested User Agent (UA).
presence - Event package that conveys the ability and willingness of a user to communicate across a set of devices. A presence protocol is a protocol for providing a presence service over the Internet or any IP network.
reg - Event package that provides a way to monitor the status of *all* the registrations for a particular Address of Record (AoR).
refer - Event package that provides a mechanism to allow the party sending the REFER to be notified of the outcome of a referenced request.
winfo - Event package for watcher information. It tracks the state of subscriptions to a resource in another package.
vq-rtcpx - Event package that collects and reports the metrics that measure quality for RTP sessions.
The current setting for the expiration of a registration request sent from the Integrated Media
Gateway (IMG) to a Remote SIP User Agent. The default is 3600 sec.
The current setting for the expiration of a registration request sent from the Remote SIP User
Agent to the Integrated Media Gateway (IMG). The default is 3600 sec.
Incoming realm name.
Outgoing realm name.
Indicates if a notable event has occurred on the call session. Valid value is: local rejection - Sessions locally rejected at the E-SBC for any reason (for example, Session
Agent (SA) unavailable, no route found, SIP signalling error, etc.); Session dialogue, capture media information and termination signalling; Any event flagged as a local rejection interesting event
Identification assigned to the call session.
Source IP address of the incoming call or media event.
Destination IP address of the outgoing call or media event.
Uniform Resource Identifier (URI) formatted string that identifies a resource via a protocol, name, location, and any other applicable characteristic, and is sent by the E-SBC in
REQUEST headers.
The following table describes the buttons on this page.
Button Description
Search Allows you to specify parameters for performing a search for specific session summary records within the current report.
Displays all of the session summary records in the Session Report.
Show all
Oracle
®
Enterprise Session Border Controller 153
Monitor and Trace Tab
Button Description
Ladder Diagram Displays a Ladder Diagram of a specific record in the table. The Ladder Diagram displays detailed information about a call session or media event.
Export Session Details Exports the SIP messages and media events associated with the selected session, to a file in text format on the local machine.
Export Summary Exports all logged session summary records to a file in text format on the local machine.
Display a Subscriptions Report
Procedure
1. From the Web GUI, click Monitor and Trace > Subscriptions.
2. Use the buttons on the top of the page to view information about the records in this report.
Notable Events Report
The Notable Events Report contains all logged sessions that have a notable event associated with the session on the
Oracle Enterprise Session Border Controller (E-SBC).
The columns that display on the Notable Events Report page are dependent on the columns you selected in the procedure, Customizing the Page Display.
154
The following table describes the columns on this page.
Heading
Start Time
State
Description
Timestamp of the first SIP message in the call session.
Status of the call or media event session. Valid values are:
INITIAL Session for which an INVITE or SUBSCRIBE was forwarded.
EARLY Session received the first provisional response (1xx other than 100).
ESTABLISHED Session for which a success (2xx) response was received.
TERMINATED Session that has ended by receiving or sending a BYE for an “Established” session or forwarding an error response for an “Initial” or Early session. The session remains in the terminated state until all the resources for the session are freed up.
FAILED Session that has failed due to a 4xx or 5xx error code.
Call ID Identification of the call source. Includes the phone number and source IP address.
Oracle
®
Enterprise Session Border Controller
Heading
Request URI
To URI
From URI
Notable Event
Ingress Realm
Egress Realm
Notable Event
Session ID
Ingress Src Addr
Egress Dest Addr
The following table describes the buttons on this page.
Monitor and Trace Tab
Description
Uniform Resource Identifier (URI) formatted string that identifies a resource via a protocol, name, location, and any other applicable characteristic, and is sent by the E-SBC in
REQUEST headers.
URI formatted string that identifies the call destination information.
URI formatted string that identifies the call source information.
Specific subscribe event package that was sent from an endpoint to the destination endpoint.
Applicable event packages can be: conference - Event package that allows users to subscribe to a conference Uniform Resource
Identifier (URI).
consent-pending additions - Event package used by SIP relays to inform user agents about the consent-related status of the entries to be added to a resource list.
dialog - Event package that allows users to subscribe to another user, and receive notifications about the changes in the state of the INVITE-initiated dialogs in which the user is involved.
message-summary - Event package that carries message-waiting status and message summaries from a messaging system to an interested User Agent (UA).
presence - Event package that conveys the ability and willingness of a user to communicate across a set of devices. A presence protocol is a protocol for providing a presence service over the Internet or any IP network.
reg - Event package that provides a way to monitor the status of *all* the registrations for a particular Address of Record (AoR).
refer - Event package that provides a mechanism to allow the party sending the REFER to be notified of the outcome of a referenced request.
winfo - Event package for watcher information. It tracks the state of subscriptions to a resource in another package.
vq-rtcpx - Event package that collects and reports the metrics that measure quality for RTP sessions.
Incoming realm name.
Outgoing realm name.
Indicates if a notable event has occurred on the call session. Valid values are: short session - Sessions that don’t meet a minimum configurable duration threshold; Session dialogue, captured media information and termination signalling; Any event flagged as a short session interesting event.
local rejection - Sessions locally rejected at the E-SBC for any reason (for example, Session
Agent (SA) unavailable, no route found, SIP signalling error, etc.); Session dialogue, capture media information and termination signalling; Any event flagged as a local rejection interesting event.
Identification assigned to the call session.
Source IP address of the incoming call or media event.
Destination IP address of the outgoing call or media event.
Oracle
®
Enterprise Session Border Controller 155
Monitor and Trace Tab
Button Description
Search
Show all
Ladder Diagram
Allows you to specify parameters for performing a search for specific session summary records within the current report.
Displays all of the session summary records in the Session Report.
Displays a Ladder Diagram of a specific record in the table. The Ladder Diagram displays detailed information about a call session or media event.
Export Session Details Exports the SIP messages and media events associated with the selected session, to a file in text format on the local machine.
Export Summary Exports all logged session summary records to a file in text format on the local machine.
Display a Notable Events Report
Procedure
1. From the Web GUI, click Monitor and Trace > Notable Events.
2. Use the buttons on the top of the page to view information about the records in this report.
Search for a Record
The <Search> button at the top of the report page allows you to perform a search to find a specific record(s) within a report (Sessions, Registrations, Subscriptions, Notable Events). It also allows you to specify criteria on which to perform the search.
After defining a search criteria in the Search Filter dialog box, clicking <Search>, automatically populates the report page with the records that match the criteria you specified. The search performs the filtering process of criteria dependent on the report page from which you are running the search.
For example, performing a search from the Sessions report page displays only the reports pertaining to call sessions.
If you performed a search on the Registration report page, only the reports pertaining to call registrations displays on the report page. The search string containing the criteria on which you performed the search, displays in the top left corner of the page.
156 Oracle
®
Enterprise Session Border Controller
Monitor and Trace Tab
Note: A SIP Monitor and Trace global search can find items in the SIP headers as well.
The search criteria is saved until you click <Reset> in the dialog box, or until you log out of the HTTP session.
Perform a Search
To perform a search:
You can specify a value for any or all of the fields in the Search box. The search process searches for records with all of the values you specify and displays only the records with these values. If you perform a “Global Search”, AND specify values in other fields, the search process searches the other specified fields first and then filters on the “Global
Search” field.
If you specify a “*” in a search string, the search is performed on that exact string. For example, if you search for
“123*45”, the search shows results for all strings containing “123*45”.
You can use quotes (“ “) to specify a search. For example, you can enter Smith and the search finds all of the records that match Smith, such as: John Smithfield<sip:[email protected]:5070>;tag=12260SIPpTag001.
If you enter a space before or after a quotation mark, (for example, “Smith “), the search returns no data.
1. In any reports page, click Search.
2. In the Global Search field, specify a string to search all parameters in all records. Valid values are alpha-numeric characters.
Note: The Global Search option searches all parameters in all the session records stored in memory. All values you specify in other fields are searched before the value specified in the Global Search field is used.
3. In the From URI field, enter the URI formatted string of the call source information you are searching. Valid values are alpha-numeric characters. For example, sipp<sip:[email protected]:5060;tag=24.
4. In the Requested URI field, enter the URI formatted string that contains a protocol, name, location, or any other applicable characteristic, that is sent by the Net-Net ECB in the REQUEST header. Valid values are alphanumeric characters. For example, sip:[email protected]:5060.
5. In the To URI field, enter URI formatted string of the call destination information you are searching. Valid values are alpha-numeric characters. For example, sut<sip:[email protected]:5060;tag=99.
6. In the Start Date/Time (HH mm ss) field, enter a starting date to search on in the first text box in the format
YYYY-MM-DD (where Y =year, M=month, and D=day). or Click on the calendar icon in this field to display a calendar from which you can select a date. Navigate the calendar to find the date you want and click on it to enter it into this field, or click <Today> to enter today’s date. For example, 2012-04-15 would search for all records starting on April 15, 2012. Valid values are numeric characters only. Enter a start time to search on in the last three text boxes in the format HH mm ss (where H=hour, m=minutes, and s=seconds). For example, 01 30 45 would search for all records starting at 1:30 and 45 seconds. Valid value are numeric characters only.
7. In the End Date/Time (HH mm ss) field, repeat the process of entering a date and time as provided in Step 7.
Oracle
®
Enterprise Session Border Controller 157
Monitor and Trace Tab
8. To search on additional parameters, click on the Additional Identifiers down arrow to expand the dialog box.
Specify Additional Identifiers
To specify additional identifiers:
1. In the Session Id field, enter the ID of the call session you want to search. Valid values are alpha-numeric characters. For example, [email protected].
2. In the In Call ID field, enter the ID of the incoming call (phone number and source IP address). Valid values are alpha-numeric characters. For example, [email protected].
3. In the Out Call ID field, enter the ID of the outgoing call (phone number and IP address). Valid values are alphanumeric characters. For example, [email protected].
4. In the State (with result code) field, enter the status of the call session with the result code for which you want to search. Valid values are (case-sensitive):
• INITIAL-<result code>
• EARLY-<result code>
• ESTABLISHED-<result code>
• TERMINATED-<result code>
• FAILED-<result code>
Result codes can range from 1xx to 5xx. For example, terminated-200, or failed-400.
5. In the Notable Event field, select the notable event for which you want to search. Valid values are:
• any-event - search displays any notable event that was stored in memory.
• short-session - search displays only records that indicate a short-session duration has occurred.
• local-rejection - search displays only records that indicate a local-rejection has occurred.
6. To search on additional parameters, click on the Additional Search Options down arrow to expand the dialog box.
Specify Additional Search Options
To specify additional search options:
1. In the “In Realm” field, enter the name of the realm for which the incoming call belongs. Valid values are alphanumeric characters. For example, access.
2. In the “Out Realm” field, enter the name of the realm for which the outgoing call belongs. Valid values are alphanumeric characters. For example, backbone.
3. In the “In SA” field, enter the name of the session agent (SA) on the incoming call session. Valid values are alphanumeric characters. For example, SA1.
4. In the “Out SA” field, enter the name of the session agent (SA) on the outgoing call session. Valid values are alpha-numeric characters. For example, SA2.
5. In the “In Source Addr” field, enter the source IP address of the SA that accepted the incoming call session. IP
Address must be entered in dotted decimal format (0.0.0.0). For example, 172.45.6.7.
6. In the “Out Dest Addr” field, enter the destination IP address of the SA that accepted the outgoing call session. IP
Address must be entered in dotted decimal format (0.0.0.0). For example, 172.64.56.7.
7. In the In Network Interface field, enter the incoming core network interface that connects the Net-Net ECB to your network. IP Address must be entered in dotted decimal format (0.0.0.0). For example, 192.45.6.7.
8. In the Out Network Interface field, enter the outgoing network interface that connects your Net-Net ECB to the outside network. IP Address must be entered in dotted decimal format (0.0.0.0). For example, 192.45.6.8.
9. Click <Search> to perform the search with the values you specified. A list of the records that the search process filtered, display in the window. The GUI saves the search specifications until you click <Reset> in the search dialog box, OR until you log out of the GUI.
158 Oracle
®
Enterprise Session Border Controller
Monitor and Trace Tab
Traceroute Command
The system can trace the route of an IP packet to an Internet host by sending probe packets and listening to responses from gateways along the route. Use the traceroute command to see each host route and the round trip time of packets received from each host in a route for diagnostic purposes.
The traceroute command sends probe packets that start with a maximum time-to-live (TTL) value of one. The system listens for an Internet Control Message Protocol (ICMP) error message in response to the TTL expiry, and records the source that sent the ICMP error message. The system repeats this process and increments the TTL value by 1 for each hop in the route to the final destination.
The traceroute command returns the following information, which allows tracing the packet route to its destination.
• TTL value
• IP address of each host along the route
• Amount of time that it takes for each probe packet to travel to each host in the route
Notes:
• Unless otherwise specified, the system sends three probe packets to each host.
• The traceroute command is only available in software versions of the Oracle Enterprise Session Border Controller, for example, Server Edition (SE) and Virtual Machine Edition (VME). For more information on supported platforms, see "Platform Support."
For traceroute command syntax and arguments, see "Traceroute Command Specifications."
Examples
The following example traces the route to IP address 172.30.0.167, identifying each host in the route and the amount of time that it takes for each of three probe packets to travel to each host. The first three probe packets reach the host at 172.44.0.1 in times ranging from less than one to a little over two milliseconds. The next three probe packets reach the route destination at IP address 172.30.0.167 all in less than one millisecond.
ACMEPACKET# traceroute 172.30.0.167
traceroute to 172.30.0.167
1 172.44.0.1 (0.669003 ms) (2.140045 ms) (2.290964 ms)
2 172.30.0.167 (0.25602 ms) (0.219822 ms) (0.604868 ms)
The following example traces the route to IP address 172.30.0.167 but specifies the use of 4 probe packets instead of the default of 3.
ACMEPACKET traceroute 172.30.0.167 probes 4 traceroute to 172.30.0.167
1 172.44.0.1 (0.549003 ms) (1.180045 ms) (2.920584 ms) (2.48541 ms)
2 172.30.0.167 (0.25802 ms) (0.220822 ms) (0.454868 ms) (0.387574)
The following example specifies that the traceroute command is issued to the IP address over the user-specified network interface private and VLAN 123.
ACMEPACKET traceroute 10.1.2.6 intf-name:vlan private:123 traceroute to 10.1.2.6
1 10.1.2.6 (0.265121 ms) (0.599080 ms) (0.0184195 ms)
The following example specifies that the wait for a response timeout is 4 seconds. The default value is three seconds.
ACMEPACKET traceroute 10.1.2.6 timeout 4 traceroute to 10.1.2.6
1 10.1.2.6 (0.265121 ms) (0.199080 ms) (0.0284195 ms)
The following example specifies that the traceroute starts at a user-specified source IP address of 172.20.22.31 to a destination IP address of 10.25.2.10.
ACMEPACKET traceroute 172.20.22.31 source-ip 10.25.2.10 traceroute to 172.20.22.31
172.20.22.31 (0.284121 ms) (0.499770 ms) (0.084595 ms)
Oracle
®
Enterprise Session Border Controller 159
Monitor and Trace Tab
Export Information to a Text File
Monitor and Trace allows you to export information to a text file from the Sessions, Registrations, Subscriptions and
Notable Events Reports, as well as from a specific ladder diagram, or from a page containing the results of a search.
The data exports to a file that you can open and view as required.
You can export any of the following:
• All information from each report
• Information from a specific record only
• Information from a search result
• Information from a Ladder Diagram
From the Sessions, Registrations, Subscriptions, and Notable Events Reports Page
From the Ladder Diagram Page
160 Oracle
®
Enterprise Session Border Controller
Monitor and Trace Tab
The following table identifies the buttons to use to export specific information from Monitor and Trace. All the export buttons in the GUI export to text files.
Button Description
From the Sessions, Registrations, Subscriptions, and Notable Events Reports:
Exports the SIP messages and media events associated with the selected session, to a file in text format on the local machine.
Exports all logged session summary records to a file in text format on the local machine.
Note: This button exports ALL call session summary records or the records that matched a search criteria to the file.
From the Ladder Diagram:
Exports all of the information in the Ladder Diagram (Session Summary, SIP Message
Details, and QoS statistics), to an HTML file format on the local machine.
Exports detailed information about the SIP messages and media events in the Ladder
Diagram associated with the selected session, to a file in text format on the local machine.
The following procedure is an example of using the export buttons in Monitor and Trace:
Export Report Information to a Text File
To export information from a Monitor and Trac report to a text file:
Oracle
®
Enterprise Session Border Controller 161
Monitor and Trace Tab
Note: The GUI exports Ladder Diagrams as HTML files.
1. From the Web GUI, click the Monitor and Trace tab.
2. On the Monitor and Trace page, select a report type. For example, Subscriptions.
3. On the report Summary page, select a report from the list, and do one of the following:
• Click Export session details.
• Click Export summary.
4. In the SessionDetails.txt or SummaryExport.txt dialog, do one of the following:
• Click Open with, and select the application with which to open the resulting text file.
• Click Save file to save the text file to your local PC.
5. Click OK to export the report information.
162 Oracle
®
Enterprise Session Border Controller
System Tab
The System tab on the Web GUI provides the following ways to manage files on the system:
• File Management. Refresh. Upload, Download, Backup, Restore, and Delete files.
• Force HA Switchover. Force the system to switch from the primary to the secondary.
• Reboot. Reboot the system.
• Support information. Generate a file that displays troubleshooting information.
• Upgrade software. Verify system health, upload software, and reboot the system.
Note: You can activate an LRT file, fraud protection file, or an SPL file dynamically upon an upload, if required. You can also immediately apply a backup configuration file during the upload process.
6
Upload a File
Procedure and conditions for uploading a file to the Oracle Enterprise Session Border Controller.
You can upload any of the following file types from your local server or PC to the Oracle Enterprise Session Border
Controller:
• Local route table (LRT)
• SPL Plug-in (SPL)
• Backup configuration
• Software image
• SIP Trunk Xpress bootstrap
• Playback media
Note: You cannot upload log files.
You can dynamically activate the “Local route table” and “SPL Plug-in”during the upload process. You can also immediately restore a backup configuration file after an upload is complete.
1. (optional) In the “Select the file type” field, select the type of file you want to upload from your local server or PC to the Oracle Enterprise Session Border Controller.
2. In the “Name” column, place a checkmark next to the file you want to upload.
3. Click <Upload>. The following are examples of the dialog box that display, dependant on which file type you chose.
Oracle
®
Enterprise Session Border Controller 163
System Tab
164
4. In the “File to upload” field, click the <Browse> button, and navigate to the location on your server or PC where the file resides.
Note: The file extension on the file must be applicable to the file type you select. For example, an SPL
Plug-in file must have the file format of “<filename>.lua ”. The following table indicates the file formats required for each File Type, and the applicable directory to which the upload process stores the file on the
Oracle Enterprise Session Border Controller.
File Type
Local route table (LRT)
SPL Plug-on (SPL)
Backup Configuration
Software image
Playback media
File Format
.xml, .gz
.lua
.gz
.bz
Any media format valid in an RTP audio stream
Directory
/code/gzConfig
/code/spl
/code/bkups
/code/images
/code/media
If you select a file with an incorrect file extension, the following message displays: “The file name extension doesn’t match the file type. The file should have the extension: <file type extension>” (For example, “.xml.gz).
5. Perform the following, based on your filetype.
For the “Local route table” file type, place a checkmark in the “Activate the LRT file after upload” box, to immediately apply the LRT to the Oracle Enterprise Session Border Controller after upload is complete.
or
For the “SPL Plug-in” file type, place a checkmark in the “Activate the SPL file after upload” box, to immediately apply the SPL file to the Oracle Enterprise Session Border Controller after upload is complete.
Oracle
®
Enterprise Session Border Controller
System Tab
or
For the “Backup configuration” file, place a checkmark in the “Restore the configuration after upload” box, to immediately apply a previous backed up configuration file to the Oracle Enterprise Session Border Controller after upload is complete. Uncheck the box to restore the backup configuration at a later time. You can use the
<Restore> button to restore the configuration to the Oracle Enterprise Session Border Controller when required.
6. Click <Upload> or click <Cancel> to cancel the upload function.
After clicking <Upload>, the Oracle Enterprise Session Border Controller checks if the file you are uploading already exists on the system. If the file exists, the following prompt displays:
“Would you like to replace the current file?”
Click <Yes> to replace the file.
or
Click <No> to cancel the upload function.
Download a File
Procedure and conditions for downloading from the Oracle Enterprise Session Border Controller.
You can download any of the following file types from your local server or PC to the Oracle Enterprise Session
Border Controller:
• Backup configuration
• Local route table (LRT)
• Log
• Playback media
• Software image
• SPL Plug-in (SPL)
1. In the “Select the file type” field, select the type of file you want to download from your local server, PC, or
Oracle Enterprise Session Border Controller.
2. In the “Name” column, select the file you want to download.
For Log file types, you can select multiple log files to download, or place a checkmark in the box to the left of the
“Name” column heading to select all log files to download. When downloading multiple log files, the File
Management GUI compresses the files into one “.tar” file and downloads that file to your local server or PC.
3. Click <Download>. The following is an example dialog box that displays
Oracle
®
Enterprise Session Border Controller 165
System Tab
4. Click “Open with” and select the application for which to open the file type for decompressing and/or editing. Or click “Save File” to save the file type to your local server or PC.
5. Click <OK>. The file type downloads to the folder on your local server or PC where your Browser sends all downloads (typically your “Download” folder) or opens (decompresses) the file type on your local server or PC
(typically in the “Download” folder).
Delete a File
Procedure and conditions for deleting a file from the Oracle Enterprise Session Border Controller (E-SBC).
You can delete any of the following file types from your local server, PC, and E-SBC:
• Backup configuration Software image
• Local route table (LRT)
• Fraud protection table
• Log
• Playback media
• Software image
• SPL Plug-in (SPL)
Note: You can select a single or multiple files to delete.
Procedure
1. On the System tab, in the File type drop down list, select the type of file that you want to delete.
2. In the Name column, select one or more files you want to delete.
Note: For Log file types, place a checkmark in the box to the left of the Name column heading to select all log files to delete.
3. Click Delete. The system displays following message.
Are you sure you want to delete the file?
4. Click Yes.
166 Oracle
®
Enterprise Session Border Controller
System Tab
Back up a File
You can backup a configuration file from the Oracle Enterprise Session Border Controller (E-SBC) to your local server or PC. This allows you to save configurations that you can restore to your E-SBC at a later time.
Procedure
1. From the Web GUI, click System.
2. In the Select the file type field, select Backup configuration.
3. Select one or more configuration files to backup to your server or PC.
4. Click Backup.
5. Click OK to backup the configuration.
The system downloads the file to your server or PC, typically into the download directory.
Restore a File
You can restore a backed up configuration file to the Oracle Enterprise Session Border Controller (E-SBC).
When you select a file to restore, and click Restore, the system restores the selected backup configuration file to the
E-SBC.
Procedure
1. In the Select the file type field, select Backup configuration.
2. Select a backup file to restore to the E-SBC.
Note: Restore activates only when you select a backup file.
3. Click Restore.
4. Click Yes.
The system downloads the backup file to the E-SBC. The E-SBC reboots and restores the configuration from the backup file.
System Reboot
If required, you can manually reboot the Oracle Enterprise Session Border Controller. If you reboot the system, all connectivity is lost. If you have a High Availability (HA) deployment, connectivity to the secondary (backup) Oracle
Enterprise Session Border Controller is lost as well.
When the reboot is complete, the logon screen displays on both the primary and secondary systems. You must manually logon to both systems.
Oracle
®
Enterprise Session Border Controller 167
System Tab
IF THEN
You perform a reboot from the Web GUI
You perform a reboot from the Web GUI, and a reboot is already in progress
You perform a reboot from the Web GUI, and the primary system is currently failing over to the secondary system (HA environment)
The GUI session closes and displays the Logon screen.
You cannot logon to the Web GUI until the reboot is complete on the Oracle Enterprise Session Border
Controller.
A message displays indicating that a reboot cannot occur. The first reboot must complete before another reboot is initiated.
A message displays indicating that a reboot cannot occur. The HA switch over is underway. The secondary system is updating and getting its configuration from the primary server. When the reboot is complete, you can no longer logon to the primary system Web GUI. You need to logon to the secondary system's Web GUI (which is now the primary system).
168 Oracle
®
Enterprise Session Border Controller
7
Format of Exported Text Files
Introduction
This Appendix provides a sample and format of each type of exported file from the Web-based GUI. Sample information in these files are provided as a reference for your convenience.
Exported file examples include:
• Session Summary exported file (text format)
• Session Details exported file (text format)
• Ladder Diagram exported file (HTML format)
Note: Oracle recommends you open an exported text file using an application that provides advanced text formatting to make it easier to read.
Exporting Files
The Web-based GUI allows you to export Monitor and Trace information to a text file from the Sessions,
Registrations, Subscriptions and Notable Events Reports, as well as from a specific ladder diagram, or from a page containing the results of a search. The data exports to a file that you can open and view as required.
You can export any of the following to a file:
From the Sessions, Registrations, Subscriptions, and Notable Events Reports:
• Export session details - Exports the SIP messages and media events associated with the selected session, to a text file.
• Export summary - Exports all logged session summary records, to a text file. (Exports ALL call session summary records or the records that matched a search criteria).
From the Ladder Diagram:
• Export diagram - Exports all of the information in the Ladder Diagram to an HTML file (Session Summary, SIP
Message Details, and QoS statistics).
• Export session details - Exports detailed information about the SIP messages and media events in the Ladder
Diagram associated with the selected session, to a text file.
The following example shows the export of a Ladder Diagram to a file called LadderDiagram.html.
Oracle
®
Enterprise Session Border Controller 169
Format of Exported Text Files
Session Summary Exported Text File
The following is an example of a Session Summary exported text file from the Web-based GUI.
Example
----------Session Summary----------
Startup Time: 2011-09-20 12:58:44.375
State: TERMINATED-200
Duration: 5
From URI: sipp <sip:[email protected]:5060>;tag=1
To URI: sut <sip:[email protected]:5060>;tag=13451
Ingress Src Address: 172.16.34.16
Igress Src Port: 5060
Igress Dest Address: 172.16.34.225
Igress Dest Port: 5060
Egress Source Address: 192.168.34.225
Egress Source Port: 5060
Egress Destination Address: 192.168.34.17
Egress Destination Port: 5060
Igress Realm: access
Egress Realm: backbone
Igress NetworkIf: access
Egress NetworkIf: backbone
----------Session Summary----------
Startup Time: 2011-09-20 12:58:05.340
State: TERMINATED-200
170 Oracle
®
Enterprise Session Border Controller
Format of Exported Text Files
Duration: 5
From URI: sipp <sip:[email protected]:5060>;tag=1
To URI: sut <sip:[email protected]:5060>;tag=13450
Ingress Src Address: 172.16.34.16
Igress Src Port: 5060
Igress Dest Address: 172.16.34.225
Igress Dest Port: 5060
Egress Source Address: 192.168.34.225
Egress Source Port: 5060
Egress Destination Address: 192.168.34.17
Egress Destination Port: 5060
Igress Realm: access
Egress Realm: backbone
Igress NetworkIf: access
Egress NetworkIf: backbone
Session Details Exported Text File
The following is an example of the a Session Details exported text file from the
Web-based GUI.
Example
Session Details:
----------------------------------------
Nov 3 08:50:56.852 On [2:0]172.16.34.225:5060 received from 172.16.34.16:5060
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 172.16.34.16:5060;branch=z9hG4bK-1-0
From: sipp <sip:[email protected]:5060>;tag=1
To: sut <sip:[email protected]:5060>
Call-ID: [email protected]
CSeq: 1 INVITE
Contact: sip:[email protected]:5060
Max-Forwards: 70
Subject: Performance Test
Content-Type: application/sdp
Content-Length: 135 v=0 o=user1 53655765 2353687637 IN IP4 172.16.34.16
s=c=IN IP4 172.16.34.16
t=0 0 m=audio 6000 RTP/AVP 0 a=rtpmap:0 PCMU/8000
----------------------------------------
Nov 3 08:50:56.855 On [2:0]172.16.34.225:5060 sent to 172.16.34.16:5060
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 172.16.34.16:5060;branch=z9hG4bK-1-0
From: sipp <sip:[email protected]:5060>;tag=1
To: sut <sip:[email protected]:5060>
Call-ID: [email protected]
CSeq: 1 INVITE
----MBCD Evt
Nov 3 08:50:56.862 On 127.0.0.1:2945 sent to 127.0.0.1:2944 mbcdEvent=FLOW ADD
FlowCollapsed=enabled
Oracle
®
Enterprise Session Border Controller 171
Format of Exported Text Files
FlowDirection=CALLING
FlowID=65541
MediaFormat=0
MediaReleased=disabled
MediaType=audio/PCMU/
OtherFlowID=0
TOSBits=0
InputSourcev4Addr=
InputSourcePort=0
InputDestv4Addr=172.16.34.225
InputDestPort=10004
OutputSourcev4Addr=192.168.34.225
OutputDestv4Addr=
OutputDestPort=0
InputRealm=access
OutputRealm=backbone
----MBCD Evt
Nov 3 08:50:56.862 On 127.0.0.1:2945 received from 127.0.0.1:2944 mbcdEvent=FLOW ADD
FlowCollapsed=enabled
FlowDirection=CALLED
FlowID=65542
MediaFormat=0
MediaReleased=disabled
MediaType=audio/PCMU/
OtherFlowID=0
TOSBits=0
InputSourcev4Addr=
InputSourcePort=0
InputDestv4Addr=192.168.34.225
InputDestPort=20004
OutputSourcev4Addr=172.16.34.225
OutputDestv4Addr=172.16.34.16
OutputDestPort=6000
InputRealm=backbone
OutputRealm=access
----------------------------------------
Nov 3 08:50:56.865 On [1:0]192.168.34.225:5060 sent to 192.168.34.17:5060
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.34.225:5060;branch=z9hG4bK4od0io20183g8ssv32f1.1
From: sipp <sip:[email protected]:5060>;tag=1
To: sut <sip:[email protected]:5060>
Call-ID: [email protected]
CSeq: 1 INVITE
Contact: <sip:[email protected]:5060;transport=udp>
Max-Forwards: 69
Subject: Performance Test
Content-Type: application/sdp
Content-Length: 140 v=0 o=user1 53655765 2353687637 IN IP4 192.168.34.225
s=c=IN IP4 192.168.34.225
t=0 0 m=audio 20004 RTP/AVP 0 a=rtpmap:0 PCMU/8000
172
----------------------------------------
Nov 3 08:50:56.868 On [1:0]192.168.34.225:5060 received from
192.168.34.17:5060
Oracle
®
Enterprise Session Border Controller
Format of Exported Text Files
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.34.225:5060;branch=z9hG4bK4od0io20183g8ssv32f1.1
From: sipp <sip:[email protected]:5060>;tag=1
To: sut <sip:[email protected]:5060>;tag=2578
Call-ID: [email protected]
CSeq: 1 INVITE
Contact: <sip:192.168.34.17:5060;transport=UDP>
Content-Length: 0
----------------------------------------
Nov 3 08:50:56.872 On [2:0]172.16.34.225:5060 sent to 172.16.34.16:5060
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 172.16.34.16:5060;branch=z9hG4bK-1-0
From: sipp <sip:[email protected]:5060>;tag=1
To: sut <sip:[email protected]:5060>;tag=2578
Call-ID: [email protected]
CSeq: 1 INVITE
Contact: <sip:[email protected]:5060;transport=udp>
Content-Length: 0
----------------------------------------
Nov 3 08:50:56.872 On [1:0]192.168.34.225:5060 received from
192.168.34.17:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.34.225:5060;branch=z9hG4bK4od0io20183g8ssv32f1.1
From: sipp <sip:[email protected]:5060>;tag=1
To: sut <sip:[email protected]:5060>;tag=2578
Call-ID: [email protected]
CSeq: 1 INVITE
Contact: <sip:192.168.34.17:5060;transport=UDP>
Content-Type: application/sdp
Content-Length: 137 v=0 o=user1 53655765 2353687637 IN IP4 192.168.34.17
s=c=IN IP4 192.168.34.17
t=0 0 m=audio 6000 RTP/AVP 0 a=rtpmap:0 PCMU/8000
----MBCD Evt
Nov 3 08:50:56.878 On 127.0.0.1:2945 sent to 127.0.0.1:2944 mbcdEvent=FLOW MODIFY
FlowCollapsed=enabled
FlowDirection=CALLING
FlowID=65541
MediaFormat=0
MediaReleased=disabled
MediaType=audio/PCMU/
OtherFlowID=0
TOSBits=0
InputSourcev4Addr=
InputSourcePort=0
InputDestv4Addr=172.16.34.225
InputDestPort=10004
OutputSourcev4Addr=192.168.34.225
OutputDestv4Addr=192.168.34.17
OutputDestPort=6000
InputRealm=access
OutputRealm=backbone
Oracle
®
Enterprise Session Border Controller 173
Format of Exported Text Files
----------------------------------------
Nov 3 08:50:56.881 On [2:0]172.16.34.225:5060 sent to 172.16.34.16:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.16.34.16:5060;branch=z9hG4bK-1-0
From: sipp <sip:[email protected]:5060>;tag=1
To: sut <sip:[email protected]:5060>;tag=2578
Call-ID: [email protected]
CSeq: 1 INVITE
Contact: <sip:[email protected]:5060;transport=udp>
Content-Type: application/sdp
Content-Length: 138 v=0 o=user1 53655765 2353687637 IN IP4 172.16.34.225
s=c=IN IP4 172.16.34.225
t=0 0 m=audio 10004 RTP/AVP 0 a=rtpmap:0 PCMU/8000
----------------------------------------
Nov 3 08:50:56.883 On [2:0]172.16.34.225:5060 received from 172.16.34.16:5060
ACK sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 172.16.34.16:5060;branch=z9hG4bK-1-5
From: sipp <sip:[email protected]:5060>;tag=1
To: sut <sip:[email protected]:5060>;tag=2578
Call-ID: [email protected]
CSeq: 1 ACK
Contact: sip:[email protected]:5060
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
----------------------------------------
Nov 3 08:50:56.887 On [1:0]192.168.34.225:5060 sent to 192.168.34.17:5060
ACK sip:192.168.34.17:5060;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.34.225:5060;branch=z9hG4bK48k3k1301ot00ssvf1v0.1
From: sipp <sip:[email protected]:5060>;tag=1
To: sut <sip:[email protected]:5060>;tag=2578
Call-ID: [email protected]
CSeq: 1 ACK
Contact: <sip:[email protected]:5060;transport=udp>
Max-Forwards: 69
Subject: Performance Test
Content-Length: 0
----------------------------------------
Nov 3 08:51:01.883 On [2:0]172.16.34.225:5060 received from 172.16.34.16:5060
BYE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 172.16.34.16:5060;branch=z9hG4bK-1-7
From: sipp <sip:[email protected]:5060>;tag=1
To: sut <sip:[email protected]:5060>;tag=2578
Call-ID: [email protected]
CSeq: 2 BYE
Contact: sip:[email protected]:5060
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
----------------------------------------
Nov 3 08:51:01.887 On [1:0]192.168.34.225:5060 sent to 192.168.34.17:5060
174 Oracle
®
Enterprise Session Border Controller
Format of Exported Text Files
BYE sip:192.168.34.17:5060;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.34.225:5060;branch=z9hG4bK5oq46d301gv0dus227f1.1
From: sipp <sip:[email protected]:5060>;tag=1
To: sut <sip:[email protected]:5060>;tag=2578
Call-ID: [email protected]
CSeq: 2 BYE
Contact: <sip:[email protected]:5060;transport=udp>
Max-Forwards: 69
Subject: Performance Test
Content-Length: 0
----------------------------------------
Nov 3 08:51:01.889 On [1:0]192.168.34.225:5060 received from
192.168.34.17:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.34.225:5060;branch=z9hG4bK5oq46d301gv0dus227f1.1
From: sipp <sip:[email protected]:5060>;tag=1
To: sut <sip:[email protected]:5060>;tag=2578
Call-ID: [email protected]
CSeq: 2 BYE
Contact: <sip:192.168.34.17:5060;transport=UDP>
Content-Length: 0
----------------------------------------
Nov 3 08:51:01.892 On [2:0]172.16.34.225:5060 sent to 172.16.34.16:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.16.34.16:5060;branch=z9hG4bK-1-7
From: sipp <sip:[email protected]:5060>;tag=1
To: sut <sip:[email protected]:5060>;tag=2578
Call-ID: [email protected]
CSeq: 2 BYE
Contact: <sip:[email protected]:5060;transport=udp>
Content-Length: 0
----MBCD Evt
Nov 3 08:51:01.891 On 127.0.0.1:2945 sent to 127.0.0.1:2944 mbcdEvent=FLOW DELETE
FlowCollapsed=enabled
FlowDirection=CALLING
FlowID=65541
MediaFormat=0
MediaReleased=disabled
MediaType=audio/PCMU/
OtherFlowID=0
TOSBits=0
InputSourcev4Addr=
InputSourcePort=0
InputDestv4Addr=172.16.34.225
InputDestPort=10004
OutputSourcev4Addr=192.168.34.225
OutputDestv4Addr=192.168.34.17
OutputDestPort=6000
InputRealm=access
OutputRealm=backbone
----MBCD Evt mbcdEvent=FLOW DELETE
FlowCollapsed=enabled
FlowDirection=CALLED
FlowID=65542
MediaFormat=0
MediaReleased=disabled
Oracle
®
Enterprise Session Border Controller 175
Format of Exported Text Files
MediaType=audio/PCMU/
OtherFlowID=65541
TOSBits=0
InputSourcev4Addr=
InputSourcePort=0
InputDestv4Addr=192.168.34.225
InputDestPort=20004
OutputSourcev4Addr=172.16.34.225
OutputDestv4Addr=172.16.34.16
OutputDestPort=6000
InputRealm=backbone
OutputRealm=access
----------Session Summary----------
Startup Time: 2012-01-25 10:28:30.394
State: TERMINATED-200
Duration: 5
From URI: sipp <sip:[email protected]:5060>;tag=1
To URI: sut <sip:[email protected]:5060>;tag=2578
Ingress Src Address: 172.16.34.16
Igress Src Port: 5060
Igress Dest Address: 172.16.34.225
Igress Dest Port: 5060
Egress Source Address: 192.168.34.225
Egress Source Port: 5060
Egress Destination Address: 192.168.34.17
Egress Destination Port: 5060
Igress Realm: access
Egress Realm: backbone
Igress NetworkIf: access
Egress NetworkIf: backbone
Ladder Diagram Exported HTML File
The following is an example of a Ladder Diagram for a session, exported to an HTML file from the Web-based GUI.
Example
176 Oracle
®
Enterprise Session Border Controller
Format of Exported Text Files
Oracle
®
Enterprise Session Border Controller 177
Shkarko
Lidhja publike u përditësua
Lidhja publike për bisedën tuaj është përditësuar. You may view and manage your chat links after registration here.
Lidhja publike e dokumentit
Reklamë