Avaya BCM450 Configuration Guide download pdf (Page 4)

AAA; Reviewed:

04/02/2010

BCM Solutions Test Lab

Reserved.

4 of 11

Optus SIP Trunking

2009-00002518 Page 4 of 11

2.0 System Software / Loadware

To achieve successful interoperability between the BCM and OPTUS Evolve Voice SIP Trunking, the

various network elements must the running the version of software as shown below:

System

Platform Firmware

BCM 50 All platforms

• Release 3.0 plus most

recent smart update

BCM450 All platforms

• Release 1.0 plus most

recent smart update

Nortel BCM Phones All supported phones

0624C6T or higher

Table 1 Validated Equipment and Software

3.0 Technical Caveats

1. The Optus Evolve Voice network requires that all signaling and media to/from the BCM

terminates/originates to one IP address, if IP phones and/or clients are deployed then the BCM,

IP phones, and clients would need to reside behind a router employing NAT.

2. The Optus Evolve Voice network requires that 10 digits are sent as the OLI. Depending upon

the configured OLI digit length, additional digits may need to be added in the Public network

dialing plan, see item 5.5.1

below

3. The default DNIS number from the Optus Evolve Voice network has the full 10 digit national

number which includes the leading zero. This leading zero conflicts with the default destination

code zero on the BCM [in the Australian profile]. It should be requested that the digits being sent

do not include a leading digit zero.

4. On an incoming INVITE message the BCM can only use the 1st codec in the offer list, it does

not utilize the codec in the preferred codec list. It should be requested that the network be

configured with the desired codec being the 1

codec in the INVITE message. Outgoing calls

use the codec as per the configured preferred codec list.

1 2 3 4 5 6 7 8 9 10 11

No comments

Avaya BCM450 Configuration Guide Page 4