Cisco Cisco MeetingPlace IP Gateway Manuale Tecnico
Avaya Communication Manager Media Server Configuration
Limitations
If the Avaya Communication Manager is not version R010c.01.036.0 or later, any inbound calls to the
Cisco MeetingPlace Server do not receive ring back tone. Although no ring back tone is heard, the
Avaya Communication Manager and the Cisco MeetingPlace Server are working. The Avaya
Communication Manager does not hear ring back because the Avaya Communication Manager Media
Server expects the terminating system (Cisco MeetingPlace Server) to provide the ring back tone
in−band. After a momentary pause of around 5 to 8 seconds, the Cisco MeetingPlace Server provides
the "Welcome to MeetingPlace Greeting", presumably based upon an H.323 (alerting) message from
the Avaya Communication Manager. For Avaya Communication Manager release 11, these
conditions no longer exist.
Cisco MeetingPlace Server do not receive ring back tone. Although no ring back tone is heard, the
Avaya Communication Manager and the Cisco MeetingPlace Server are working. The Avaya
Communication Manager does not hear ring back because the Avaya Communication Manager Media
Server expects the terminating system (Cisco MeetingPlace Server) to provide the ring back tone
in−band. After a momentary pause of around 5 to 8 seconds, the Cisco MeetingPlace Server provides
the "Welcome to MeetingPlace Greeting", presumably based upon an H.323 (alerting) message from
the Avaya Communication Manager. For Avaya Communication Manager release 11, these
conditions no longer exist.
•
IP Shuffling does not work, regardless of codec. It is also assumed the both the Avaya
Communication Manager and Cisco MeetingPlace Server only work on a G.711 end−to−end.
Therefore, in situations where it is mixed, it is not clear if the Avaya Communication Manager Media
Processor can gracefully compensate for this issue, although it is known that it does in later releases.
Communication Manager and Cisco MeetingPlace Server only work on a G.711 end−to−end.
Therefore, in situations where it is mixed, it is not clear if the Avaya Communication Manager Media
Processor can gracefully compensate for this issue, although it is known that it does in later releases.
•
IP Hair−pinning does not work between Avaya Communication Manager Media Server and Cisco
MeetingPlace Servers.
MeetingPlace Servers.
•
Step 1: Establish the Node−Name IP Information
Tell the Avaya Communication Manager the name and IP address of your Cisco MeetingPlace Windows 2000
Server. This is very similar to the Domain Name Tables (or /etc/hosts) commonly found in other computer
systems.
Server. This is very similar to the Domain Name Tables (or /etc/hosts) commonly found in other computer
systems.
In this example, the Cisco MeetingPlace Windows 2000 Server name is nt−irva−1503 and the IP address is
10.9.192.74.
10.9.192.74.
The local Control LAN (CLAN) interface name used in this document is clan−1900−01 and the IP address is
10.9.6.20. It is important to note that, if the Avaya Communication Manager has a CLAN already
administered, then further administration is not necessary. In this case, this is clan−1900−01. Otherwise, you
need to administer them.
10.9.6.20. It is important to note that, if the Avaya Communication Manager has a CLAN already
administered, then further administration is not necessary. In this case, this is clan−1900−01. Otherwise, you
need to administer them.
In summary, within the Node−Name IP form, you must administer the names and IP addresses for the entries
for CLAN, Media Processor, and the MeetingPlace Windows 2000 IP Gateway.
for CLAN, Media Processor, and the MeetingPlace Windows 2000 IP Gateway.
To add the Cisco MeetingPlace Windows 2000 IP Gateway, issue the change node−name IP command. On
this form, add the NETBIOS name of the Windows 2000 Server. In this example, it is nt−irva−1503 (or what
you have named yours). This is an example of the Node Name IP form:
this form, add the NETBIOS name of the Windows 2000 Server. In this example, it is nt−irva−1503 (or what
you have named yours). This is an example of the Node Name IP form: