Thursday, January 21, 2021

Cisco Unified CallManager Attendant Console

This document describes one reason why Cisco CallManager does not communicate with the Avaya Unified Messaging system through the Cisco VG224 Voice Gateway using the Simplified Message Desk Interface (SMDI) protocol. This document also provides a solution.

Preconditions

Required conditions

Cisco recommends that you understand the following topics:

Cisco CallManager

Cisco VG224 Voice Gateway

Avaya Unified Messaging System

Components used

The information in this document is based on the following hardware and software versions:

Cisco CallManager 4.x

The information in this document was created from devices in a specific lab environment. All devices used in this document started with a cleared (default) configuration. If your network is operational, make sure that you understand the potential effect of any command.

Conventions

For more information about the conventions used in this document, see Cisco Technical Advice Conventions .

Problem

A problem exists when Cisco CallManager communicates with the Avaya Unified Messaging system through the serial port using an SMDI protocol such as Message Waiting Indicator (MWI) refresh / resynch.

In the corresponding trace, it is recognized that the Cisco Messaging Interface Service (CMI) is not receiving the SsInfoInd signal from Cisco CallManager. Therefore, subsequent signaling stops because CMI is not generating SMDI messages.

This output displays the corresponding error message on the Avaya Unified Messaging system:

failed to get integration data

No comments:

Post a Comment

Server management systems

Enterprises receive the services and functions they need (databases, e-mail, website hosting, work applications, etc.) for their corporate I...