Avaya Breeze ™ web GUI, and navigate to Avaya Breeze ™ Dashboard.

Avaya Breeze ™ command line, and run the status service command.

Avaya Aura® System Manager web GUI, and navigate to Breeze Dashboard.

Avaya Aura® System Manager command line, run the status service command.

Use SSH to Avaya Breeze ™, and run SMnetSetup.

Use SSH to Avaya Breeze ™, and use the route command to correct the routing table.

Use Avaya Aura® System Manager web GUI to update the SIP Entity screen.

Use Avaya Aura® System Manager web GUI to access the Engagement Development Platform < Server Administration, and edit the Server Instance.

https://135.xx.xxx.xx:8443/WebLM/LicenseServer

https://135.xx.xxx.xx:8080/LicenseServer

https://135.xx.xxx.xx:52233/WebLM/LicenseServer

https://135.xx.xxx.xx/WebLM

The amount of virtual memory used

The status information about the virtual machine

The statistical information about voicemail boxes

The count of mailbox password violation attempts

They immediately escalate to Tier 3 as issue is encountered.

They describe the problem to Tier 3 in an escalation ticket and Tier 3 isolates and resolves the issue.

They isolate issue, resolve issue then escalate to Tier 3 for corrective action.

They isolate the issue, and if no root cause is found, escalate to Tier 3 to resolve the issue.

20 Voice Ports are always reserved for retrieving messages.

AAM can run on Avaya-provided hardware that runs Linux® and Avaya Aura® System Platform, or

VMware in a virtualized environment.

You can choose to use the Avaya Message Store or Microsoft Exchange Store.

AAM Multi-Server configuration separates Application Servers from Avaya Message Store.

Each message application server allows for up to 100 simultaneous SIP or H323 sessions, with 300 active ports permitted per Voice Mail Domain (VMD).

Edit the Cluster, access the Servers tab, and assign the server to the cluster; then set the cluster to Accept New Service.

Under Engagement Development Platform > Server Administration, select the server and change the

System State to Accept New Service, then return to the Cluster Administration screen and set the cluster to Accept New Service.

Obtain and install an Avaya Breeze™ license on webLM with more instances of Avaya Breeze™ nodes.

Edit the cluster to change the cluster profile from Core Platform to General Purpose.

It is eight steps that guarantee a logical way to isolate an issue.

It is eight steps that ensure a faster time to resolution.

It is eight steps used to guarantee systems are operational after an implementation.

It is eight steps that define how to escalate third-party integration issues.

It is eight steps that guarantee a thorough analysis of a failure, containment actions, full resolution, and

prevention for the future.

Avaya Aura® Presence sends Notify to the telephone via Avaya Aura® Session Manager.

Phone sends Register message to Avaya Aura® Session Manager via Avaya Session Border Controller for Enterprise.

The telephone sends Subscribe message to Avaya Aura® Session Manager via Avaya Session Border

Controller for Enterprise.

Avaya Aura® Presence sends Notify to the SIP endpoint via Avaya Session Border Controller for

Enterprise.

WebRTC uses a STUN/TURN server to relay WebRTC media from the public network through to the

Avaya Aura® Media Server (AAMS).

WebRTC and Presence Services Snap-ins can co-reside on a General Purpose Cluster.

WebRTC uses the Avaya Aura© Media Server (AAMS) to convert WebRTC media to SIP mediA.

The WebRTC Snap-in will validate the authorization token created and encrypted by the web server.

The web browser uses the “Cluster IP Address” to reach an Avaya Breeze ™ node when making a

WebRTC call.