Multitech MTA128NT Manual de usuario descargar pdf

Avaya Communication Manager, Release 3.1

Known Issues and Workarounds for the S8500 Media Server

ID Symptom WorkaroundKeywords

a31005d The documents Hardware Description and Reference for

Avaya Communication Manager, 555-245-207 (p. 362)

and Overview for the Avaya G250 and the Avaya G350

Media Gateways, 03-300435 (p. 29-30) contain a

description of the MM716 Analog Media Module. That

description states that the MM716 provides 24 analog

ports supporting telephones, trunks, modem, and fax.

The description should read: “The MM716 provides 24

analog ports supporting telephones, modem and fax.

These ports can also be configured as DID trunks with

either wink-start or immediate-start.” In addition, the

MM716 analog media module supports type 1 caller ID

only, and is compatible with Avaya Communication

Manager Release 3.1 (not 2.0) and later releases. The

link here provides a corrected description of the MM716

Media Module:

Media Gateway,

Media Module,

Maintenance,

H.248 IP

MM716 Media Module

a31004d The document Hardware Description and Reference for

Avaya Communication Manager, 555-245-207, contains a

note on p. 313 stating that the TN1654 DS1 converter

circuit pack is not used in a G650 Media Gateway. This

note is incorrect.

The G650 Media Gateway supports the TN1654 DS1

converter circuit pack.

Media Gateway,

Circuit Packs,

Maintenance,

H.248 IP

a08710s

On a G350 media gateway, you cannot change the IP

mask for an existing interface.

Remove the old IP and create a new one with the correct

IP address and mask.

Note: old Release Notes ID number = 0a8710s

Administration,

Maintenance,

Media Gateway,

CLI, H.248 IP

a08652s

If you open a telnet session from a G350 media gateway

to a G350 on which the telnet server is down, no operation

failure indication is given.

Verify that the telnet server is running on the remote

G350.

Note: old Release Notes ID number = 0a8652s

Administration,

Maintenance,

Media Gateway,

H.248 IP

a00004s

If the primary server is running Release 1.3 or earlier of

Communication Manager, and an LSP is running Release

1.3.1 or later, filesync to LSPs does not work properly,

and other transmissions through the server firewall do not

behave as expected.

Even if nothing appears to have changed after creating

this disparity between the primary server and the LSP,

always re-administer the firewall. To do this:

1. Go to the Set LAN Security Web page and click the

Advanced Settings button.

2. Review the settings. Make sure all needed ports are

open, including shell on port 514.

3. Click the Set Security button.

On a configuration with two servers, do this on both

servers.

Note: old Release Notes ID number = 000a04s

LSP, Upgrades,

Security, File

Transfer

061353s

If, on the login administration form, the field Days To

Disable After Inactivity contains a value, and the field

Change Password At First Login is set to Yes, then that

To prevent this from happening, set Change Password

At First Login to No, or remove the value from Days To

Disable After Inactivity.

To use both fields, contact your technical support

organization. Request and apply patch 11847 or any

later patch that includes 11847.

Indice de contenidos

Pagina 1 - ID Symptom WorkaroundKeywords

Avaya Communication Manager, Release 3.1Known Issues and Workarounds for the S8500 Media ServerID Symptom WorkaroundKeywordsa31005d The documents Hard

Pagina 2

ID Symptom WorkaroundKeywords061096s A call on a wireless endpoint routed via AAR/ARS over a trunk group that uses a private number format does not di

Pagina 3

ID Symptom WorkaroundKeywords060485s In a configuration using the TN457 circuit pack for voice synthesis, following a certain mis-operation – specific

Pagina 4

ID Symptom WorkaroundKeywords060133s If a call attempts to use an announcement or music sourced from a media gateway, but the media gateway cannot pro

Pagina 5

ID Symptom WorkaroundKeywords054573s If Busy Tone Detection is enabled and Direct IP (shuffling) is disabled, an incoming analog trunk call to a vecto

Pagina 6

ID Symptom WorkaroundKeywords052248s When a narrow WAN (Wide Area Network) link to a remote office terminates to a G350 or G250 Media Gateway, calls o

Pagina 7

ID Symptom WorkaroundKeywords033556s On a call from an H.323 IP telephone over an IP (H.323) or SIP trunk, if the DTMF method for the trunk's si

Pagina 8

ID Symptom WorkaroundKeywords021127h When a caller hangs up on a call using an analog trunk on a G700 media gateway, the trunk used for that call migh