Oracle Communications WebRTC Session Controller …...6. Groovy execute script 7-8. Groovy script...

Oracle Communications WebRTC Session Controller: Basic Admin

Student Guide

Edition 1.0

April 2015

Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Disclaimer This document contains proprietary information and is protected by copyright and other intellectual property laws. You may copy and print this document solely for your own use in an Oracle training course. The document may not be modified or altered in any way. Except where your use constitutes "fair use" under copyright law, you may not use, share, download, upload, copy, print, display, perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization of Oracle. The information contained in this document is subject to change without notice. This document is not warranted to be error-free. Restricted Rights Notice If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS The U.S. Government’s rights to use, modify, reproduce, release, perform, display, or disclose these training materials are restricted by the terms of the applicable Oracle license agreement and/or the applicable U.S. Government contract. Trademark Notice Oracle and Java are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

Table of Contents

Architecture ......................................................................................................................................................1-1 WebRTC Session Controller Architecture ......................................................................................................1-3 Agenda ...........................................................................................................................................................1-4 Network Deployment ......................................................................................................................................1-5 Signaling and Media .......................................................................................................................................1-6 Signaling and Media Integration .....................................................................................................................1-7 Signaling and Media Anchored Flow ..............................................................................................................1-8 Signaling and Media Deployment ...................................................................................................................1-9 Agenda ...........................................................................................................................................................1-10 Signaling Engine Technologies ......................................................................................................................1-11 Signaling Engine Feature Highlights ..............................................................................................................1-12 Signaling Engine Components .......................................................................................................................1-13 Signaling Engine Architecture ........................................................................................................................1-14 Signaling Engine Protocols ............................................................................................................................1-15 Signaling Engine APIs and Extensibility .........................................................................................................1-16 Signaling Engine Interfaces ...........................................................................................................................1-17 Signaling Engine Domain ...............................................................................................................................1-18 Signaling Engine JSON-RTC protocol ...........................................................................................................1-19 Signaling Engine Sessions .............................................................................................................................1-20 Signaling Engine Application Concepts ..........................................................................................................1-21 Signaling Engine Message Flow ....................................................................................................................1-22 Signaling Engine Templating .........................................................................................................................1-23 Signaling Engine Templating, Continued .......................................................................................................1-26 Signaling Engine Templating , Continued ......................................................................................................1-27 Signaling Engine Configuration ......................................................................................................................1-28 Signaling Engine High Availability and Load Balancing .................................................................................1-29 Signaling Engine Failover Scenario ...............................................................................................................1-30 Signaling Engine Failover Scenario, Continued .............................................................................................1-31 Signaling Engine Security ..............................................................................................................................1-32 Agenda ...........................................................................................................................................................1-33 Media Engine Technologies ...........................................................................................................................1-34 Media Engine Feature Highlights ...................................................................................................................1-35 Media Engine Components ............................................................................................................................1-36 Media Engine Architecture .............................................................................................................................1-37 Media Engine Protocols .................................................................................................................................1-38 Media Engine Cluster .....................................................................................................................................1-39 Media Engine SDP processing.......................................................................................................................1-41 Media Engine High Availability and Load Balancing ......................................................................................1-42 Media Engine Security ...................................................................................................................................1-43 Media Engine Security – ICE .........................................................................................................................1-44 Media Engine Security – DTLS ......................................................................................................................1-45

Media Engine Installation and Administration ...............................................................................................2-1 WebRTC Session Controller Media Engine Installation and Administration ...................................................2-3 Agenda ...........................................................................................................................................................2-4 Installation Options .........................................................................................................................................2-5 Installation Packages .....................................................................................................................................2-6

Hardware Requirements ................................................................................................................................2-7 Installation Overview ......................................................................................................................................2-8 Hardware Installation Overview ......................................................................................................................2-9 Xen Installation Overview ...............................................................................................................................2-10 Setup Management IP Interface.....................................................................................................................2-11 Shell and Poweroff .........................................................................................................................................2-12 Media Engine Directories ...............................................................................................................................2-13 Agenda ...........................................................................................................................................................2-14 Media Engine Configuration ...........................................................................................................................2-15 Access Configuration .....................................................................................................................................2-16 Cluster Configuration .....................................................................................................................................2-17 Load Factor Application Configuration ...........................................................................................................2-18 Master Services Configuration .......................................................................................................................2-19 Virtual System Partition Configuration ............................................................................................................2-21 Agenda ...........................................................................................................................................................2-22 Media Engine Object Types ...........................................................................................................................2-23 Media Engine Object Types – Configuration ..................................................................................................2-24 Media Engine Object Types – Status .............................................................................................................2-25 Media Engine Object Types – Actions ...........................................................................................................2-26 Media Engine Object Types – Events ............................................................................................................2-27 Agenda ...........................................................................................................................................................2-28 Media Engine Administration Tools ................................................................................................................2-29 Media Engine Administration Tools – CLI ......................................................................................................2-30 Configure box object using CLI command (example: box IP address) ...........................................................2-31 Configure vsp object using CLI command (example: default-session-config in-encryption) ...........................2-32 Configure vsp object using CLI command (continue) ....................................................................................2-33 Show object status using CLI command (example: ice-state-status) .............................................................2-34 Show object status using CLI command (verbose) ........................................................................................2-35 Media Engine Administration Tools – Web UI ................................................................................................2-36 Configure vsp object using web UI (example: default-session-config in-encryption) ......................................2-37 Configure box object using web UI (example: box IP address) ......................................................................2-38 Configure box object using web UI (continue) ................................................................................................2-39 Show object status using Web UI (example: ice-state-status) .......................................................................2-40 Show object status using Web UI (verbose) ..................................................................................................2-41

Signaling Engine Installation and Administration .........................................................................................3-1 WebRTC Session Controller Signaling Engine Installation and Administration ..............................................3-3 Agenda ...........................................................................................................................................................3-4 Installation Prerequisites and Requirements ..................................................................................................3-5 Installation Modes ..........................................................................................................................................3-6 Signaling Engine Installation ..........................................................................................................................3-7 Signaling Engine Installation (Optional Silent Mode) .....................................................................................3-8 Agenda ...........................................................................................................................................................3-10 WebLogic Server Concepts ...........................................................................................................................3-11 WebLogic Server Domain ..............................................................................................................................3-12 WebLogic Server Domain, Continued ...........................................................................................................3-13 WebLogic Administration Server ....................................................................................................................3-15 WebLogic Managed Servers ..........................................................................................................................3-16 WebLogic Managed Server Clusters ..............................................................................................................3-17 Agenda ...........................................................................................................................................................3-18

Creating the Signaling Engine Domain ..........................................................................................................3-19 Silent Domain Creation ..................................................................................................................................3-20 Silent Domain Creation, Continued ................................................................................................................3-21 Agenda ...........................................................................................................................................................3-22 Signaling Engine Administration.....................................................................................................................3-23 Accessing the Administration Consoles .........................................................................................................3-24 User Interface Overview .................................................................................................................................3-25 Concepts ........................................................................................................................................................3-26 Applications ....................................................................................................................................................3-27 Packages .......................................................................................................................................................3-28 Packages and Mapping to Criteria .................................................................................................................3-29 Applications ....................................................................................................................................................3-30 Applications – Request URI ...........................................................................................................................3-31 Applications – Security Group ........................................................................................................................3-32 Applications – Resource Limits ......................................................................................................................3-33 Applications – Allowed Domains ....................................................................................................................3-34 Applications – Packages ................................................................................................................................3-35 Packages .......................................................................................................................................................3-36 Script Library ..................................................................................................................................................3-37 Configuration – Signaling Engine ...................................................................................................................3-38 Configuration – Media Engine ........................................................................................................................3-39

Architecture

Chapter 1 - Page 1

Architecture

Chapter 1

Architecture

Chapter 1 - Page 2

Architecture

Chapter 1 - Page 3

WebRTC Session Controller Architecture

Architecture

Chapter 1 - Page 4

Agenda

Architecture

Chapter 1 - Page 5

Network Deployment

WebRTC Session Controller is a gateway server at the border of SIP/IMS network.

Architecturally parallel to a P-CSCF. While P-CSCF is entry for the SIP endpoints, WebRTC Session Controller is entry point for HTML5 endpoints.

Provide signaling and media integration between WebRTC browser clients with SIP/IMS.

WebRTC Session Controller does not host any business applications, but leverage such functions from IMS applications deployed in the IMS application server.

Architecture

Chapter 1 - Page 6

Signaling and Media

WebRTC Session Controller interact with WebRTC app:

• Using JSON-RTC (JSON over WebSockets) for signaling.

• Using SRTP/ICE/STUN/TURN for media.

WebRTC Session Controller interact with SIP network for signaling.

WebRTC Session Controller interact with legacy SIP nodes and media functions using RTP.

Architecture

Chapter 1 - Page 7

Signaling and Media Integration

WebRTC Session Controller is physically split in a Signaling Engine (WSC-SE) and a Media Engine (WSC-ME).

WSC-SE handle all signaling and WSC-ME handle all media.

WSC-SE and WSC-ME communicate to control the media sessions using an internal HTTP/SOAP based protocol: JSON-RTC.

Architecture

Chapter 1 - Page 8

Signaling and Media Anchored Flow

Sample call flow for simple call setup

Architecture

Chapter 1 - Page 9

Signaling and Media Deployment

Signaling Engine Cluster

- All nodes are active

- Cluster state is shared

- Load balance logic towards Media Engines is built in

Media Engine

- Multiple independent clusters of master/slave

- Response is sent to originating Signaling Engine or the backup Signaling Engine

Signaling Engines and Media Engines can scale independently

Architecture

Chapter 1 - Page 10

Agenda

Architecture

Chapter 1 - Page 11

Signaling Engine Technologies

Architecture

Chapter 1 - Page 12

Signaling Engine Feature Highlights

Architecture

Chapter 1 - Page 13

Signaling Engine Components

Admin Server Configuration and Management

Engine Servers WSC-SE app with runtime processing

Client javascript library For writing WebRTC HTML5 apps

Converged Load Balancer (CLB) SIP load balancer

Lightweight Proxy Registrar (LWPR) Built-in Proxy/Registrar

Architecture

Chapter 1 - Page 14

Signaling Engine Architecture

Main layers:

- Protocol stacks (SIP, HTTP, Diameter)

- Services

- Message processing, including Template Engine (Groovy) and APIs

- Fabric

Architecture

Chapter 1 - Page 15

Signaling Engine Protocols

Architecture

Chapter 1 - Page 16

Signaling Engine APIs and Extensibility

Architecture

Chapter 1 - Page 17

Signaling Engine Interfaces

Architecture

Chapter 1 - Page 18

Signaling Engine Domain

Engine and Replica Tier scale independently

Architecture

Chapter 1 - Page 19

Signaling Engine JSON-RTC protocol

Architecture

Chapter 1 - Page 20

Signaling Engine Sessions

WEB Session ~ Web Socket

Sub Session ~ SIP Session

Media session, 0-1 per Sub Session

Architecture

Chapter 1 - Page 21

Signaling Engine Application Concepts

Architecture

Chapter 1 - Page 22

Signaling Engine Message Flow

Web Handler manage websockets (Web Socket Application)

Fabric makes the right node process each message (local if possible). Leverage Coherence.

Message Processing do protocol mapping and translation

SIP Handler manage SIP (SIP Servlet) and maintains SIP session state. Leverage SIP application session.

Side Functions provide integration with external features such as Rx and Media Engine

Architecture

Chapter 1 - Page 23

Signaling Engine Templating

Groovy scripts are used for mediation between web and sip messages.

There are a large number of template groovy scripts available out-of-the-box.

Architecture

Chapter 1 - Page 24

Note that example is simplified for readability.

1. Standard HTTP authentication (e.g. username/password or OAuth)

2. Browser establish Web Socket connection

3. Browser send connect JSON message

4. Signaling Engine process the JSON frame (creates session “A”, sub session “1”, SIP session)

5. Signaling Engine resolve script to execute based on criteria

6. Groovy execute script

7-8. Groovy script create and send SIP REGISTER to SIP network

9. 200 OK received from SIP network

10-11. Signaling Engine process the SIP response and resolve script to execute

12. Groovy execute script

13-14. Groovy script create and send JSON response (including session info)

Architecture

Chapter 1 - Page 25

Red marks highlight various application concepts.

Architecture

Chapter 1 - Page 26

Signaling Engine Templating, Continued

Architecture

Chapter 1 - Page 27

Signaling Engine Templating , Continued

Architecture

Chapter 1 - Page 28

Signaling Engine Configuration

Architecture

Chapter 1 - Page 29

Signaling Engine High Availability and Load Balancing

Architecture

Chapter 1 - Page 30

Signaling Engine Failover Scenario

Application web socket connected to Signaling Engine 1

SIP signaling flow through Signaling Engine 1

Media interaction between Signaling Engine 1 and Media Engine

Media flow through Media Engine

Architecture

Chapter 1 - Page 31

Signaling Engine Failover Scenario, Continued

The application detect web socket disconnect (by heartbeat or socket disconnect)

- Reconnects to the Load Balancer, which forwards to Signaling Engine 2 and recovers full state

- Messages are queued until the application is reconnected

- SIP signaling flow redirected through Signaling Engine 2

- Media interaction between Signaling Engine 2 and Media Engine

- Media continue to flow through Media Engine

Theoretically, the application, Media Engine and SIP can all connect to different nodes. The fabric make sure messages are distributed properly.

Architecture

Chapter 1 - Page 32

Signaling Engine Security

Architecture

Chapter 1 - Page 33

Agenda

Architecture

Chapter 1 - Page 34

Media Engine Technologies

Architecture

Chapter 1 - Page 35

Media Engine Feature Highlights

Architecture

Chapter 1 - Page 36

Media Engine Components

Architecture

Chapter 1 - Page 37

Media Engine Architecture

Architecture

Chapter 1 - Page 38

Media Engine Protocols

Architecture

Chapter 1 - Page 39

Media Engine Cluster

Architecture

Chapter 1 - Page 40

Media Engine Interfaces

Each node in the cluster can host a VRRP interface on one or more local physical interfaces.

Each physical interface can host more than one VRRP interface at a time.

Architecture

Chapter 1 - Page 41

Media Engine SDP processing

Architecture

Chapter 1 - Page 42

Media Engine High Availability and Load Balancing

Architecture

Chapter 1 - Page 43

Media Engine Security

Architecture

Chapter 1 - Page 44

Media Engine Security – ICE

Architecture

Chapter 1 - Page 45

Media Engine Security – DTLS

Architecture

Chapter 1 - Page 46

Media Engine Installation and Administration

Chapter 2 - Page 1

Chapter 2

Chapter 2 - Page 2

Chapter 2 - Page 3

WebRTC Session Controller Media Engine Installation and Administration

Chapter 2 - Page 4

Agenda

Chapter 2 - Page 5

Installation Options

Chapter 2 - Page 6

Installation Packages

Chapter 2 - Page 7

Hardware Requirements

Chapter 2 - Page 8

Installation Overview

Chapter 2 - Page 9

Hardware Installation Overview

Chapter 2 - Page 10

Xen Installation Overview

Chapter 2 - Page 11

Setup Management IP Interface

Chapter 2 - Page 12

Shell and Poweroff

Chapter 2 - Page 13

Media Engine Directories

Chapter 2 - Page 14

Agenda

Chapter 2 - Page 15

Media Engine Configuration

Chapter 2 - Page 16

Access Configuration

Chapter 2 - Page 17

Cluster Configuration

Chapter 2 - Page 18

Load Factor Application Configuration

Chapter 2 - Page 19

Master Services Configuration

Chapter 2 - Page 20

Chapter 2 - Page 21

Virtual System Partition Configuration

Chapter 2 - Page 22

Agenda

Chapter 2 - Page 23

Media Engine Object Types

Chapter 2 - Page 24

Media Engine Object Types – Configuration

Chapter 2 - Page 25

Media Engine Object Types – Status

Chapter 2 - Page 26

Media Engine Object Types – Actions

Chapter 2 - Page 27

Media Engine Object Types – Events

Chapter 2 - Page 28

Agenda

Chapter 2 - Page 29

Media Engine Administration Tools

Chapter 2 - Page 30

Media Engine Administration Tools – CLI

Chapter 2 - Page 31

Configure box object using CLI command (example: box IP address)

Chapter 2 - Page 32

Configure vsp object using CLI command (example: default-session-config in-encryption)

Chapter 2 - Page 33

Configure vsp object using CLI command (continue)

Chapter 2 - Page 34

Show object status using CLI command (example: ice-state-status)

Chapter 2 - Page 35

Show object status using CLI command (verbose)

Chapter 2 - Page 36

Media Engine Administration Tools – Web UI

Chapter 2 - Page 37

Configure vsp object using web UI (example: default-session-config in-encryption)

Chapter 2 - Page 38

Configure box object using web UI (example: box IP address)

Chapter 2 - Page 39

Configure box object using web UI (continue)

Chapter 2 - Page 40

Show object status using Web UI (example: ice-state-status)

Chapter 2 - Page 41

Show object status using Web UI (verbose)

Chapter 2 - Page 42

Signaling Engine Installation and Administration

Chapter 3 - Page 1

Chapter 3

Chapter 3 - Page 2

Chapter 3 - Page 3

WebRTC Session Controller Signaling Engine Installation and Administration

Chapter 3 - Page 4

Agenda

Chapter 3 - Page 5

Installation Prerequisites and Requirements

Chapter 3 - Page 6

Installation Modes

Chapter 3 - Page 7

Signaling Engine Installation

Chapter 3 - Page 8

Signaling Engine Installation (Optional Silent Mode)

Chapter 3 - Page 9

Signaling Engine Installation (Optional Silent Mode)

Chapter 3 - Page 10

Agenda

Chapter 3 - Page 11

WebLogic Server Concepts

Chapter 3 - Page 12

WebLogic Server Domain

Chapter 3 - Page 13

WebLogic Server Domain, Continued

Chapter 3 - Page 14

WebLogic Server Domain, Continued

Chapter 3 - Page 15

WebLogic Administration Server

Chapter 3 - Page 16

WebLogic Managed Servers

Chapter 3 - Page 17

WebLogic Managed Server Clusters

Chapter 3 - Page 18

Agenda

Chapter 3 - Page 19

Creating the Signaling Engine Domain

Chapter 3 - Page 20

Silent Domain Creation

Chapter 3 - Page 21

Silent Domain Creation, Continued

Chapter 3 - Page 22

Agenda

Chapter 3 - Page 23

Signaling Engine Administration

Chapter 3 - Page 24

Accessing the Administration Consoles

Chapter 3 - Page 25

User Interface Overview

Chapter 3 - Page 26

Concepts

Chapter 3 - Page 27

Applications

Chapter 3 - Page 28

Packages

Chapter 3 - Page 29

Packages and Mapping to Criteria

Chapter 3 - Page 30

Applications

Chapter 3 - Page 31

Applications – Request URI

Chapter 3 - Page 32

Applications – Security Group

Chapter 3 - Page 33

Applications – Resource Limits

Chapter 3 - Page 34

Applications – Allowed Domains

Chapter 3 - Page 35

Applications – Packages

Chapter 3 - Page 36

Packages

Chapter 3 - Page 37

Script Library

Chapter 3 - Page 38

Configuration – Signaling Engine

Glare Handling: Handles simultaneous updates.

Sip Session Default Time: Maps to sip extension field Session-Expires (default time is 3600 seconds), which defines lifetime of a sip session.

Sip Session Minimum Time: Maps to sip extension field Min-SE (min value 90 seconds), defines sip session timer.

Websocket Disconnect Time Limit: Time interval between disconnect and reconnect of the websocket session (default time is 60000 ms).

Websocket Idle Time Limit: Idle time interval after which websocket times out (30 seconds).

Websocket Maximum Connections: Number of maximum connections.

Chapter 3 - Page 39

Configuration – Media Engine

User/Password: Media engine user and password.

Block Traffic: To unblock the traffic from the node.

Unblock Traffic: To block the traffic from the node.

Address/Port: Media engine address and port

Media Node Traffic Enabled: Node is allowed to receive the traffic.

Media Node Status: Up or Down.

Load Factor: Load value on the current node.

Chapter 3 - Page 40

Oracle Communications WebRTC Session Controller …...6. Groovy execute script 7-8. Groovy script...

Documents

groovy transforms

Groovy Documentationdocs.groovy-lang.org/docs/groovy-2.1.3/pdf/wiki-snapshot.pdf · Groovy Introduction Groovy... • is an agile and dynamic language for the Java Virtual Machine

soapUI Prodl.eviware.com/whitepapers/soapUI Pro - The Value.pdf · • Groovy Script Library soapUI Pro provides functionality enabling reuse of Groovy scripts. Your scripts can be

Groovy 2.5 features & Groovy 3+ Roadmap · Groovy Roadmap Groovy 2.5 2.5.4 released, 2.5.5 soon Macros, AST transformation improvements, various misc. features JDK 7 minimum, runs

Adventures in Groovy – Part 20: Groovy On-Premise vs

Groovy 2.5 features & Groovy 3+ Roadmap...What is Groovy? Groovy = Java –boiler plate code + extensible dynamic and static natures + better functional programming + better OO programming

Groovy Update, Groovy Ecosystem, and Gaelyk -- Devoxx 2010 -- Guillaume Laforge

Groovy Tutorial - testa.roberta.free.frtesta.roberta.free.fr/My Books/Computer programming/Java/Groovy... · Agile 2007 - 3 07 What is Groovy? •“Groovy is like a super version

Siegfried Goeschl Groovy Scripting - home.apache.orgpeople.apache.org/.../2016/linuxwochen/groovy-scripting.pdf · • Groovy is easy for Java developers • Groovy is nice for non-trivial

Groovy 2.5+ Roadmap - objectcomputing.com · • Home of Grails & Micronaut • Friend of Groovy ... AST Transformations –Groovy 2.4, Groovy 2.5, Groovy 3.0 @AutoFinal @AutoImplement

What makes Groovy Groovy - Guillaume Laforge (Pivotal)

Gerrit Code Review: how to script a plugin with Scala and Groovy

Groovy Programming Cookbook · Groovy Programming Cookbook ii Contents 1 Groovy Script Tutorial for Beginners 1 1.1 Environment

Groovy And Grails - Chariot Solutionschariotsolutions.com/.../archive/449/groovy-grails-keynote.pdf · Groovy And Grails An Overview. Groovy. What Is Groovy?

New Who's speaking? - Jfokus · 2019. 9. 11. · Frogs ️ Groovy Hosting Groovy on Bintray Hosting Groovy on Artifactory Bintray UI is Grails Artifactory plugins are Groovy ... Use

Automate APIs with Groovy Script - cisco.com · testRunner.gotoStepByName("Groovy Script − DataSource") //go to the DataSource} 10. 11. In this example procedure, a 1000 ms delay

groovys Documentation - Read the Docs · Groovy 2.4 Java 6 Java 8 Java 9 snapshot groovy-nio Java 7 invokeDynamic Java 7+ Java 8 Groovy CI Java Groovy 10000 Java Groovy 1.1.2Maven

Groovy&&&Grails2.x&update - Callista Enterprisecallistaenterprise.se/.../presentationer/cadec-2013-groovy-grails.pdf · Groovy&Grails2.xupdate ©&2013&CallistaEnterprise&|& Agenda

GROOVY COTBED BED GROOVY LIT GROOVY · GROOVY GROOVY BED LIT. SAFETY INSTRUCTIONS Your child’s safety is your responsibility.. and use only spare parts approved by the manufacturer

Groovy grails20110120Présentation sur Groovy / Grails par Olivier Gourment