Oracle Session Monitoring Installation – Probe Mediation Engine Connection (Version 4.1.0.3.0)

Oracle Session Monitoring Installation

– Probe to Mediation Engine Connection (Version 4.1.0.3.0)

The Operations Monitor Probe can connect to one or more Mediation Engines, using TLS encryption, 
or with some configurations, also cleartext. Likewise, a Mediation Engine can connect to more than one Operations Monitor Probe (as well as Session Border Controller Probes).

The probes send meta-data for each of the signaling messages to the Mediation Engine layer and analyze
 the RTP streams locally, sending the results of this analysis to the Mediation Engine layer.

Figure 1-1 Session Monitor System Architecture

Oracle Linux : 7.5 (V975367-01.iso)

Session Monitor RPM file:  p29473233_41000_Acme_Packet.zip

Enterprise edition of MySQL in version 5.7.10: p22322140_570_Linux-x86-64_mysql5.7.10.zip

Login to iLom and lunch Remote Console

Mount Linux 7.5

Reboot

 

Boot from Remote ISO

 

Configure IP address and tick automatic connect

Make reasonable partition

Conigure Yum.conf proxy (optional)

proxy=http://HTTP_PROXY:PORT

proxy_username=USERNAME

proxy_password=PASSWORD

sslverify=false

Export http proxy variable(optional)

export http_proxy=http://USERNMAE:PASSWORD@PROXY_HOST:PORT

export https_proxy=$http_proxy

Download latest Repo file

curl -Ok https://yum.oracle.com/public-yum-ol7.repo

mv public-yum-ol7.repo /etc/yum.repos.d/public-yum-ol7.repo

yum install -y yum-utils

yum-config-manager --enable ol7_latest ol7_UEKR4 ol7_developer_EPEL ol7_optional_latest ol7_addons ol7_UEKR3 ol7_UEKR5

Install latest Enterprise edition of MySQL in version 5.7.10 .

yum install -y mysql-commercial*.rpm

yum-config-manager --enable ol7_latest ol7_UEKR4 ol7_developer_EPEL ol7_optional_latest ol7_addons ol7_UEKR3 ol7_UEKR5

Install the Session Monitor RPM file

yum install ocsm-4.1.0.3.0.x86_64.rpm

Find installation logs

[root@HOSTNAME]# pwd

/var/log/ocsm

[root@HOSTNAMEocsm]# ls

ocsm_installed_XXXXDATE_MDT.log  ocsm_preinstall_XXXXXDATE_MDT.log

Turning VSI to handle the additional traffic 

Added the following to the file /opt/oracle/ocsm/etc/iptego/vsi.local.conf: 

[ip]
table_bits = 16 # default is 10
expires = 30

[storage]
parallel_blocks=20
prealloc_blocks=40
startup_blocks=8

[users]
xmlrpc_search_minimum_results=0
xmlrpc_search_timeout=2
table_bits=24

[tm]
table_bits = 24 

Adjust the firewall

   firewall-cmd --permanent --zone=public --add-service=https

  firewall-cmd --permanent --zone=public --add-port=4739/tcp

  firewall-cmd --permanent --zone=public --add-port=4740/tcp

  firewall-cmd --permanent --zone=public --add-port=4741/tcp

  firewall-cmd --permanent --zone=public --add-port=4742/tcp

  firewall-cmd –reload

login to Session Monitor

https://HOSTNAME/setup/license_agreement/

username: sysadmin

password: oracle

Configure Platform Setup Application

Choose Probe as Machine type

Add new ME connection

Enable capture

Install

Check packets are growing

Login to ME node and see Probes detected automatically

Cisco CMS Clustering and Redundancy

Cisco CMS Clustering and Redundancy

Create Database Master on CMS1

Enter the command: database cluster localnode a

Then enter the command: database cluster initialize

Confirm enter: Y

Connect Second and third CMS to Master

Enter the command: database cluster localnode a

Then enter the command: database cluster join CMS1_IP

Confirm join by entering: Y

Run command: database cluster upgrade_schema

Verify cluster status

Create Call Bridge Cluster

Three Callbridges

Create CallbridgeGroups

Assign callBridgeGrou “HO” to each callBridge

callBridgeGroup loadbanance

Extension Mobility / Extension Mobility Cross Cluster (EM/EMCC)

Extension Mobility / Extension Mobility Cross Cluster

(EM/EMCC)

Prior to certificate consolidation, start with the cluster ID naming and Certificate export/consolidate/import is already in place for two clusters

EMCC devices available per cluster is already set to 100. Assumption is that no more than 100 EMCC users will be concurrently visiting the same cluster and use EMCC, if this is the case, it’s safe to increase the limit to 500 EMCC device. This change from 100 to 500 will not cause any IP Phone interruption.

1. Add EMCC IP Phone Service:

Service URL is: http://X.X.X.X:8080/emapp/EMAppServlet?device=#DEVICENAME#&EMCC=#EMCC#

Where X.X.X.X represents the IP Address of the CUCM node where EM service is activated/started.

Make sure to enable “Enterprise Subscription”, this check box will appear once only when a new service is added.

Enable EM on IP Phones:

2. Create one partition and create one calling search space, assign the created partition to the created calling search space for emergency calling.

3. Create extension mobility User Device Profile for end users. On the Device Profile Configuration page, for the “Extension Mobility Cross Cluster CSS” assign the CSS created in step 3.

4. On the end user page assign the EM profile and enable EMCC

And

5. Add emergency route pattern(s). Partition accessible by the calling search space assigned to UDP “Extension Mobility Cross Cluster CSS”. The Gateway/Route List MUST point to a Standard Local Route Group.

6. Add Geo location filter to match:

7. add/update GEO Location configuration. Example of GEO Location:

8. On all IP Phone Device Pools, add the GEO Location Configuration created. Do not apply any GEO Location filter here.

9. Add Roaming GEO Location configuration that will match the GEO Location configuration set on the visiting phone. This is necessary to place the visiting IP Phone in the correct Roaming device pool.

10. Add Roaming Device Pool and apply the filter. Roaming device pool must reflect the correct time zone of the visiting cluster. Apply the GEO Location filter here. On the same Roaming device pool, make sure the correct Media Resource Group list is selected.

11. Create EMCC SIP Trunk. Critical: the Trunk’s Inbound CSS MUST have access the emergency Route Pattern(s) partition used by the users on the visiting cluster.

12. EMCC Feature Configuration. EMCC Region Max Audio Bit Rate value must be the same on all cluster participating in the EMCC network.

13. EMCC Inter-cluster Service Profile. Validation must be successful.

14. Configure Cluster View. EMCC/TFTP enabled.

VCS For Video Lync Gateway

Video Lync Gateway VCS

The VCS acts as a gateway between Skype for business and Cisco Video conferencing endpoints

The VCS communications server manages the dial-plan and call signaling for the Cisco Video conferencing environment. However it connects to a session management layer for overall dial-plan and routing decisions.

It also facilitates calls to the Microsoft SKYPE environment, B2B external calls & multi-conference calls.  The VCS delivers these features with different software workloads

OVERVIEW

VCS – Option Keys

There are multiple AD domains associated with Skype for business users, so these search rules accommodate calling to employees in example.com, example2.com, example3.com and example4.com

Zones

B2BUA configuration

Microsoft Lync B2BUA trusted hosts

Trusted CA certificates

SME - Global Dial Plan Replication(GDPR)

Session Management Edition  -- Global Dial Plan Replication(GDPR)

A Global Cisco Unified Communications Session Management Edition (Unified CM SME) which is a trunk and dial plan aggregation component for multi-site distributed call processing deployments. The Global SME is essentially a Cisco Unified Call Manager Cluster with trunk interfaces and no IP endpoints. It enables aggregation of multiple Cisco communications telephony systems, known as leaf clusters.

Centralized routing diagram

Main purpose

• Centralize dial plan
• Connectivity to 3rd party session management
• Dial Patterns dynamics (automation)

Server Function for CUCM will fit into one or more of the following feature sets:

• Publisher
• Subscriber

Publisher Service Activation

Servers	Service Name	Activation Status
Publisher This server is responsible for all of the administration updates to the other servers in the cluster. It must communicate with all other servers. Additionally this server is used for the following functions: AXL-based communications Remote monitoring(SNMP) directory synchronization with the AD environment using Cisco DirSync (if enabled) Bulk updates using the Cisco Bulk Provisioning Service Due to the administration overhead, Call control (Cisco CallManager), TFTP (Cisco TFTP) and media resource (Cisco IP Voice Media Streaming Application) functionality has been disabled, as to prevent CPU over-utilization. Encryption services are also disabled, as this feature is not being deployed.	Cisco CallManager	Deactivated
	Cisco Messaging Interface	Deactivated
	Cisco Unified Mobile Voice Access Service	Deactivated
	Cisco IP Voice Media Streaming App	Deactivated
	Cisco CTIManager	Deactivated
	Cisco Extension Mobility	Deactivated
	Cisco Extended Functions	Deactivated
	Cisco DHCP Monitor Service	Deactivated
	Cisco Intercluster Lookup Service	Activated
	Cisco Dialed Number Analyzer Server	Activated
	Cisco Dialed Number Analyzer	Activated
	Cisco TFTP	Deactivated
	Cisco IP Manager Assistant	Deactivated
	Cisco WebDialer Web Service	Deactivated
	Cisco SOAP - CDRonDemand Service	Deactivated
	Cisco CAR Web Service	Deactivated
	Platform SOAP Services	Activated
	Cisco AXL Web Service	Activated
	Cisco UXL Web Service	Activated
	Cisco Bulk Provisioning Service	Activated
	Cisco TAPS Service	Deactivated
	Cisco Serviceability Reporter	Activated
	Cisco CallManager SNMP Service	Activated
	Cisco CTL Provider Activated	Deactivated
	Cisco Certificate Authority Proxy Function	Deactivated
	Cisco DirSync	Activated

Subscriber Service Activation

Servers	Service Name	Activation Status
Subscribers ** Cisco AXL Web Service  will only be enabled for Sub1 and Sub2 on each cluster All Subscribers Cisco CallManager service is enabled Cisco CallManager SNMP Service is enabled Cisco Web Dialler Web Service is enabled Cisco Extended Functions are enabled	Cisco CallManager	Activated
	Cisco Messaging Interface	Deactivated
	Cisco IP Voice Media Streaming App	Deactivated
	Cisco CTIManager	Deactivated
	Cisco Extension Mobility	Deactivated
	Cisco Extended Functions	Activated
	Cisco DHCP Monitor Service	Deactivated
	Cisco Dialed Number Analyzer Server	Deactivated
	Cisco Dialed Number Analyzer	Deactivated
	Cisco TFTP	Deactivated
	Cisco IP Manager Assistant	Deactivated
	Cisco WebDialer Web Service	Deactivated
	Cisco SOAP Services	Deactivated
	Cisco AXL Web Service	Activated**
	Cisco UXL Web Service	Deactivated
	Cisco TAPS Service	Deactivated
	Cisco Serviceability Reporter	Deactivated
	Cisco CallManager SNMP Service	Activated
	Cisco CTL Provider	Deactivated

To ensure that the endpoints’ codec preferences are trusted as calls pass through SME, enable the SIP Profile feature “Accept Audio Codec Preferences in Received Offer” on all SIP Trunks.

Global Dial Plan Replication – GDPR and ILS

Intercluster lookup Service (ILS)

The Intercluster Lookup Service (ILS) feature is used to interconnect multiple clusters together.  With the ILS cluster discovery service it provides clusters to dynamically learn about remote clusters within the ILS network.  ILS also supports the Global Dial Plan Replication (GDPR) feature. ILS and GDRP work together to dynamically share the global dial plan with all clusters within the ILS network.

Global Dial Plan Replication (GDPR)

The Global Dial Plan Replication (GDPR) feature uses the ILS feature to share dial plan information between clusters within the ILS network.  The information is captured by a centralized hub cluster which then propagates to all connected spoke clusters.

Menu: Advance Features > ILS Configurations; Select Role: For SME: ‘Hub Cluster’

Leaf clusters: ‘Spoke Cluster’

In the ‘ILS Cluster Registration’ pop up window, input in ‘Registration Server’: For SME: leave blank and click OK; For Leaf: Enter IP of Publisher node of hub cluster and click OK

Input check for ‘Exchange Global Dial Plan Replication Data with remote Clusters’

Enter route string for Cluster, which will populate, to all clusters within the ILS network.  Keep default of 10 minutes for ‘Synchronize Clusters Every’ field. Route string naming convention:The route string will be a combination of Cluster ID + ‘.ils’.  Example: ClusterXXX.ils

For ILS Authentication there are two options to choose from, via TLS certificates or by password.  The Password would be the same entered on all clusters.

ILS network Verification

Once you have the first two networks configured, Hub and a spoke, verify connectivity at top of page.  You may need to click on refresh button a few times. You can also temporary reduce ‘Synchronize Clusters Every’ to 1 minute.  The screen capture below indicates there is 1 hub and 1 spoke.

View from Hub:

View from Spoke:

Partitions for Learned Numbers and Patterns

Configure SIP route patterns

Call Routing > SIP Route Pattern

For SME:  create a SIP Pattern for each cluster it is connected to and assign the associated trunk for that clusters.  

For Leafs: You only need to create one SIP Pattern in each leaf.

ILS Service Parameter configuration

Determine the required max number of learned objects.  

ILS advertises locally configured enterprise alternate numbers and +E.164 alternate numbers to the ILS network where the Advertise globally via ILS option has been selected.

Click:  Add Enterprise Alternate Number