BCM50 Technical Configuration Guide ¾ BCM50 with Mediatrix ® 1102® ¾ in a Direct Gateway Environment Sales Engineering Document Date: June 16, 2006 Document Version: 1.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 Nortel is a recognized leader in delivering communications capabilities that enhance the human experience, ignite and power global commerce, and secure and protect the world’s most critical information.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 Caveat The information provided in the document is intended for an informed audience who possess the appropriate level of training to configure and maintain network equipment. Nortel does not support the third party products depicted in this document; it is the responsibility of the reader to secure adequate support agreements with the manufacturer.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 TABLE OF CONTENTS 1. OVERVIEW: BCM50 TO MEDIATRIX ® ANALOG GATEWAY IN A DIRECT GATEWAY ENVIRONMENT 4 2. BASE SCENARIO:.............................................................................................................................................................4 2.1 ASSUMPTIONS:..............................................................................................................................................................4 2.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 1. Overview: BCM50 to Mediatrix ® Analog Gateway in a Direct Gateway Environment Analog gateways are becoming more of a necessity in the enterprise to provide faxing capabilities over Voice Over IP (VoIP) networks. The gateway handles the responsibility of transcoding the analog call to IP using VoIP standards. These gateways interoperate with core VoIP telephony servers.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 Figure 1 Hardware Matrix Manufacturer Nortel ® Platform BCM Model 50 Mediatrix ® Mediatrix ® Nortel ® Analog Gateway Unit Manager Client Enterprise Switch 1102 ® 470 Version 1.1 with cumulative patch 1 4.0.12.47 3.2.17.40 3.6.0.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 2.2 Objectives: The objective of the testing and configuration was to extend analog capabilities to a Mediatrix ® analog gateway from a BCM50 over a VoIP network. This allows users to deploy devices such as analog phones across a VoIP capable network allowing a reduction in cable infrastructure. 2.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 Figure 3 2.4.1.2 Destination Code Configuration A destination code is defined on the BCM to access the Mediatrix ® analog port. For this solution, we used the entire 7 digit phone number associated with the analog phone on the gateway as the destination code and set the Absorbed Length to 0 so that all digits would pass to the Mediatrix ®.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 Figure 4 2.4.1.3 PRI Route Configuration (External Trunk) The PRI route is defined on the BCM50 with a DN type of Public (Unknown). For this setup, route 004 was utilized.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 Figure 5 2.4.1.4 Remote Access Package Definition For calls to tandem from one trunk to the other, a remote access package must be configured and all lines within the pool associated with the tandem trunks need to be assigned to the remote access package.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 Figure 6 2.4.1.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 Figure 7 Adding the PRI lines to the Remote Access Package; in this configuration, the PRI falls into lines 65-87.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 Figure 8 2.4.1.6 H.323 Direct Configuration For these tests the BCM50 was configured to support a direct connection to a remote VoIP gatekeeper. Utilizing a gatekeeper was not tested.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 Figure 9 2.4.1.7 Remote Gateway Definition The Mediatrix ® now needs to be defined as a remote gateway. The IP address of the Mediatrix ® is defined along with the destination digits used for the port on the gateway associated with the analog device. In this configuration 2345678 was used. This matches the destination digits previously defined for the call routing destination digits.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 Figure 10 2.4.1.8 BCM50 Codec Definition The Codec is set to G.711 mu-law and T.38 FAX is disabled under the Media Parameters Tab.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 Figure 11 At this point the BCM50 configuration should be complete. 2.4.2 Mediatrix® Configuration 2.4.2.1 Mediatrix® IP Address Assignment Mediatrix® 1102 ® configuration Mediatrix® ships a GUI based configuration tool named “Unified Manager Client”® (UMC) with each of the analog gateways. The UMC is used to manipulate the MIB variables that define the configuration on the gateway. Out of the box, the gateway requests an IP address utilizing DHCP.
BCM50 to Mediatrix® Direct Gateway 2.4.2.2 V1.0 June 2006 Mediatrix® GUI Install The UMC install is a straightforward windows installation. The CD is placed in the CD drive and autorun should launch a web page which will guide you through the setup. If autorun does not launch the web page, file explorer can be used to navigate to the root of the CD where you will find a HTM file named “ReadMeFirst.htm”. Double click this file and it will launch a web browser with a start page. 2.4.2.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 Once the device is discovered, the gateway will show up under the Unit Manager tree. Once under the Unit Manager tree the properties of the gateway can be expanded. Figure 13 2.4.2.4 H.323 and Port Configuration Now the gateway is ready for a configuration. To get the gateway up and running with the BCM50, the H.323 and port configuration needs to be completed first. Right Click on H.323 and select “Edit”. The H.323 properties screen appears.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 An alias must be defined on a per port basis. For this setup, only 1 port was used. Port 1 was defined with a 7 digit phone number with a type of E164 (National). This is the phone number that corresponds to the port. If the incoming dialed phone number matches the number defined on the port and the type matches, the port will ring the analog device.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 The analog port being configured is set to “enable” and the IP address of the BCM50’s advertised IP telephony address is defined. This is where all calls will be routed originating from analog port 1 on the gateway. When completed select “ok” Figure 15 2.4.2.6 Gateway CODEC Definition Once the direct gateway is configured, the CODEC for the individual analog ports need to be defined.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 Figure 16 Right click on “port” and select “edit”. The “port” properties page appears. Set the preferred codec to “G.711 mulaw (PCMU)” and T38 fax to “Disabled”. The country locale is set to “North America 1”. Click on “OK”.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 Figure 17 Right click on “codec activation” under “port” on the tree and select “edit”. The codec activation screen appears. Disable all codecs except for G.711 mu-law. Select “OK” when completed.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 Figure 18 2.4.2.7 Mediatrix® Configuration Transfer At this point the configuration needs to be transferred to the gateway. Right click on the MAC address of the gateway under the Unit Manager icon. Go to “configuration file” and “transfer to unit”. The configuration is now transferred to the gateway but is not yet active.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 Figure 19 2.4.2.8 Packetization Time Now the packetization time or PTIME needs to be defined to be inline with the BCM50. Access this parameter by right clicking on the MAC address of the gateway under the Unit Manger icon and selecting “edit snmp”.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 Figure 20 Once selected the entire MIB structure of the Mediatrix ® gateway is displayed.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 Figure 21 Do a Get on the OID (Object ID) Mediatrix.mediatrixConfig.voiceIfMib.voiceIfCodecTable by right clicking on the Mib and selecting “get”.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 Figure 22 After you execute the get you need to Double click in the voiceIfCodecPcmuMaxPTime field and set the parameter to an integer value of 40. This sets the packetization rate between 10ms and 40ms for PCMU (G.711 mu-law). Once the value is changed, the SNMP Set button at the top of the page must be selected or the change will not be transferred to the gateway.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 Figure 23 2.4.2.9 Out of Band Signaling Out of Band Signaling now needs to be enabled. This is under the voiceIfDtmfTransport MIB. Right click and do a get. Once the values are displayed, change the voiceIfDtmfTransport option from “InBand” to “outOfBandUsingSignalingProtocol”. Once changed, click on the Set Icon at the top of the page.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 Figure 24 2.4.2.10 Alias Type Restriction Navigate to the h323AliasTypeRestriction MIB and change the value to “disable”. Click on the SNMP set icon at the top of the page.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 Figure 25 2.4.2.11 Gateway Configuration Activation When completed, close the Edit SNMP page. At this point, the config should be transferred again to the gateway by right clicking on the MAC address under the Unit Manager icon and navigating to “configuration file” and selecting “transfer to unit”.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 Figure 26 Once transferred, the gateway needs to be restarted for the config changes to become active. Right click on the MAC address under the Unit Manager icon, navigate to “action” and select “Restart (graceful)”. The gateway will restart and load the new config.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 Figure 27 This should complete the Mediatrix® configuration steps. 2.5 Verification: The most useful tool in troubleshooting the setup is the BCM monitor. By utilizing the BCM monitor, tandem functionality and call setup can be verified.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 The first thing to verify is that the calls are incoming and outgoing appropriately. In the below screen shot, the call is incoming on Line 065 and tandeming through to Line 006. This is an incoming call on the PRI and Outgoing call on the VoIP line and the call is in a connected state.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 Figure 29 3. Software Baseline: Hardware Matrix Manufacturer Nortel ® Platform BCM Model 50 Mediatrix ® Mediatrix ® Nortel ® Analog Gateway Unit Manager Client Enterprise Switch 1102 ® 470 Version 1.1 with cumulative patch 1 4.0.12.47 3.2.17.40 3.6.0.
BCM50 to Mediatrix® Direct Gateway V1.0 June 2006 4. Reference Documentation: Document Title Publication Number “Quintum Voice Over IP Gateway on BCM Technical Configuration Guide” “Configuration Notes for Mediatrix FXS Units in Nortel CS1K Release 3 H.323 Environment” Description TCG Created by Pierre Fournier from Nortel 0203 Mediatrix ® Configuration Note Contact Us: For product support and sales information, visit the Nortel Networks website at: http://www.nortel.
