Avaya

Message Networking Help

Home | Search  
Print | Back | Fwd | Close
  
Getting Started Admin Maintenance Reference
Home > Getting Started > Message Networking concepts and features > Bridging feature overview > Sample Message Networking Bridged Networks

Sample Message Networking Bridged Networks

Message Networking supports a bridging feature in which Message Networking is used to transmit messages to or from remote machines designated as bridged machines. With this feature, Message Networking no longer acts as a hub for all message activity between remote machines in the network. Instead, Message Networking only allows messages to pass between two remote machines when one of the remote machines is designated as a bridged remote machine. Any attempts to send messages directly between nonbridged remote machines fail.

This document provides two sample Message Networking bridged networks:

  • A system in which Modular Messaging systems are bridged to a network.
  • A system in which a Unified Messenger system is bridged to a network.

Sample 1: Bridged Modular Messaging systems

The following figure depicts a sample Message Networking bridged network in which two Modular Messaging systems are administered as bridged systems. The systems on the left side of the dotted line (the two MM systems are designated as bridged systems. The systems on the right side of the dotted line are remote machines in the network that are not designated as bridged systems. The straight lines indicate the message paths that are supported.

 

In this configuration:

  • A message sent from one of the Modular Messaging systems to the INTUITY AUDIX through Message Networking is delivered because the Modular Messaging system is designated as a bridge.
  • A message sent from the INTUITY AUDIX to the Octel 250/350 through the Message Networking bridge fails with a “sending restrictions” error code because neither the INTUITY AUDIX and Octel 250/350 systems are not bridged systems.
  • A message sent directly from the Octel 200/300 to the Octel 100 is delivered because the message is not sent through the Message Networking system and those system can communicate directly via Octel Analog.

 

Sample 2: Bridged Unified Messenger system

The following figure depicts a sample Message Networking bridged network in which one Unified Messenger system is administered as a bridged system. The system on the left side of the dotted line (the UM system) is designated as a bridged system. The systems on the right side of the dotted line are remote machines in the network that are not designated as bridged systems. The straight lines indicate the message paths that are supported.

In this configuration:

  • A message sent from the UM to the Octel 250 through Message Networking is delivered because the UM system is designated as a bridge.
  • A message sent from the INTUITY LX to the Serenade 300 through the Message Networking bridge fails with a “sending restrictions” error code because neither the INTUITY LX and Serenade 300 systems are not bridged systems.
  • A message sent directly from the Octel 200/300 to the Octel 100 is delivered because the message is not sent through the Message Networking system and those system can communicate directly via Octel Analog.

 

Home | Search | Print | Back | Fwd | Close
©2006 Avaya Inc. All rights reserved.
Last modified 11 January, 2006