Nortel BCM50 2.0, Installation Manual

Page: 45 / 86

Chapter 6 IP telephone overview 45
Telephony Device Installation Guide
M1-IPT
The Meridian 1 Internet Telephony Path (M1-IPT) allows Meridian 1 systems to communicate
with the BCM50 2.0 via H.323 trunks. Telephones on the M1, such as Meridian telephone A, can
initiate and receive calls with the other telephones on the system across IP networks.
To provide fallback at times when IP traffic cannot pass, you can also connect the Meridian to the
BCM50 2.0s through ISDN PRI SL-1 lines, which provide the same MCDN capability that you
can achieve through the H.323 VoIP trunks with MCDN active.
A BCM50 2.0 connected to an M1-IPT using the MCDN protocol can provide access to a central
voice mail and call attendant systems, which can streamline multi-office telephony administration.
Telephones
The BCM50 2.0 can communicate using digital telephones (Model 7000, 7100, 7208, 7316,
7316E/7316E+KIMs, 7406 (cordless telephone), Norstar M-series telephones, ISDN telephones,
analog telephones, and IP telephones and applications. With this much flexibility, the BCM50 2.0
can provide the type of service you require to be most productive in your business.
While analog and digital telephones cannot be connected to the BCM50 2.0 system with an IP
connection, they can make and receive calls to and from other systems through VoIP trunks. Calls
received through the VoIP trunks to system telephones are received through the integrated
interface (LAN card) or the IP network and are translated within the BCM50 2.0 to voice channels.
The IP telephones connect to the BCM50 2.0 across an IP network through either a LAN or a
WAN. From the BCM50 2.0 connection, they can then use standard lines or VoIP trunks to
communicate to other telephones on other public or private networks. The BCM50 2.0 also
supports H.323 (version 4) and H.323 third-party devices through this type of connection.
Gatekeepers on the network
A gatekeeper tracks IP addresses of specified devices, and provides routing and (optionally)
authorization for making and accepting calls for these devices. A gatekeeper is not required as part
of the network to which your BCM50 2.0 system is attached, but gatekeepers can be useful on
networks with a large number of devices. Referring to
Figure 10 , for example: Digital telephone A
wants to call IP telephone B, which is attached to BCM50 2.0 B, over a network that is under the
control of a gatekeeper. Digital telephone A sends a request to the gatekeeper. The gatekeeper,
depending on how it is programmed, provides Digital telephone A with the information it needs to
contact BCM50 2.0 B over the network. BCM50 2.0 B then passes the call to IP telephone B.
The BCM50 2.0 does not contain a gatekeeper application. If you want to put a gatekeeper on your
network, it must be put on a separate gatekeeper server. The BCM50 2.0 is compatible with
CS1000 (CSE1K) gatekeepers.
Warning: Meridian 1 IPT does not support the RadVision gatekeeper.