Reviewed:
07/27/2010
BCM Test Lab Application Notes
©2010 Avaya Inc. All Rights Reserved.
6 of 38
BCM_Configuration_Guide_For
ATT.doc
NN10000-125
Special Notes
Emergency 911/E911 Services Limitations
While AT&T IP Flexible Reach services support E911/911 calling capabilities in certain
circumstances, there are significant limitations on how these capabilities are delivered.
Please review the “AT&T IP Flexible Reach” Service Guide in detail to understand these
limitations and restrictions.
BCM Soft Phones not currently supported
Avaya BCM soft phones are not currently supported with the AT&T IP Flexible Reach
Services.
Ring back Issues with Unattended Transfers
An unattended transfer is one in which the party initiating the transfer hangs up prior to
answer by the party to whom the call is being transferred. When 2 phones are in an
active call on the BCM and one of those phones performs an unattended transfer to
certain endpoints on the AT&T network, the BCM phone remaining on the call will not
hear ring back prior to answer.
T.38 Fax must be used
T.38 fax should be configured on the BCM with AT&T IP Flexible Reach service. Fax via
G.711 transport should not be used on the BCM.
Error Correction Mode Not Supported
In T.38 fax calls originated by the BCM, during capabilities negotiation, BCM disables
Error Correction Mode (ECM); therefore, these particular calls will not use ECM during
fax transmission. However, calls will still work.
Find Me/Follow Me Restrictions
Directory Information (i.e., 411 and 555-1212) and 8YY numbers should not be used for
Find Me/Follow Me external destinations.
20-byte G.729 Payload Size to/from PSTN
The G.729 payload size will always be 20 bytes with calls to/from PSTN.
G.726 Codec not supported
BCM does not support the G.726 codec – G.711 and G.729 codecs should be used.
Comentários a estes Manuais