Showing posts with label CP PM. Show all posts
Showing posts with label CP PM. Show all posts

The Signaling Server

A CS1000E system can have one of four types of signaling servers. There are two Signaling Servers that are available from a third party and there is the CP PM Signaling Server. In addition, there is support for the legacy ISP1100 Signaling Server.

The two COTS Signaling Servers that can be used are the IBM X306m Signaling Server and the HP DL320-G4 Signaling Server. Both of these servers can be configured using either Linux or the VxWorks software that the Nortel equipment uses. If the COTS signaling server is using Linux it adds the functionality of a tool called Enterprise Common Manager that allows for more advanced configuration options through a web interface than the default Nortel software allows through Element Manager.
The ISP1100 Signaling Server was used with previous releases and is supported for backwards compatibility. It is now discontinued and is not recommended, although it will function as a signaling server.

The CP PM Signaling Server uses the same hardware as the CP PM Call Server. There are a few small differences, however. The most noticeable difference is that the Signaling Server has a 40 GB Hard Disk Drive and no on-board Compact Flash. To enable the system to use the 40 GB Hard Disk Drive to load software it is necessary to set Switch 5 to position 2. Additionally, there is no security dongle on the Signaling Server.

The CP PM Signaling Server is connected either directly to the MGC or to a layer 2 switch using the ELAN and TLAN ports. Nortel recommends connecting them via a layer 2 switch. The ELAN port is used for address, data, and control signals between the various components of the CS1000E system. The TLAN port is used for telephony signaling traffic. The HSP port is not used on a signaling server. The indicator lights are the same as those on the CP PM Call Server.

The role of the signaling server is to provide SIP and H.323 signaling, IP phone signaling, and IP peer networking. The signaling server can use either VxWorks of Linux to perform these functions. The CP PM Signaling Server can only use VxWorks. A signaling server also provides the H.323 Gateway software to provide IP Peer Networking features between multiple MG1000Es and the CS1000E Call Server. In addition, it provides virtual trunk application and support for IP terminals. It can be configured with a survivability configuration and a load-sharing configuration. Each signaling server can support up to 5,000 IP users and a maximum of 1,800 SIP and H.323 trunks. Of these 1,800 trunks, a maximum of 1,200 H.323 trunks are available. This maximum can only be achieved if H.245 tunneling is enabled. If the server is running Personal Directory, Redial List, and Caller List, a maximum of 1,000 IP users are supported per Signaling Server.

A Signaling Server has a number of software applications that are installed to provide functionality. This includes the SIP/H.323 Gateway Signaling Software (for virtual trunks), IP Line Software (including the Terminal Proxy Server), a Network Routing Service (NRS) application, the Element Manager web server, the NRS Manager web server, and an application server that includes Personal Directory, Callers List, and Redial List.

The Call Server

The core component of a CS1000E is the Call Server. There are three types of call servers that are supported – the CP PII, the CP PIV, and the CP PM. The CP PII is a legacy system that is no longer available. It was a separate system that was rack-mountable and used a Pentium II processor. The CP PIV uses a Pentium M processor and is also a rack-mountable. The CP PM is a slot-based board that can be used as a Call Server or a Signaling Server. This is the type of system that I will focus on, as most new installations use the CP PM style of call processor, and the CP PM board can also be used as a Signaling Server.

The CP PM Call Server can reside in slots 1-4 of the MG1000E Chassis. Slot 0 is reserved for the Media Gateway Controller (MGC) card. When used as a call server the CP PM system has a 1 GB onboard Compact Flash (CF) card for operating software, and ships with 512 MB of DDR RAM (expandable up to 2 GB). There is a Compact Flash slot on the front of the system that is used for software loading and backups. The CP PM Call Server is also generally shipped with a 512 MB CF Card containing the installation media and keycodes. Additionally, a 128 MB CF Card is shipped for software backups. There is a switch on the board, known as switch 5, which needs to be in position 1 to designate that the CP PM system should boot from the onboard CF card. In addition the Call Server must also have a Large System Security Device (Part # NTDK57AAE5). This looks like a large cell battery and is also known as a security dongle. This device is used to indicate to the operating system which software packages and resources are available.

The CP PM Call Server connects to the Media Gateway Controller using Ethernet. As such, the only backplane connectivity that is required for operation is power and Slot ID. There are three Ethernet ports on the CP PM system, so it is important to remember which one is used for what purpose. The CP PM Call Server must be connected through the ELAN port on the CP PM system to the MGC. This can either be a direct connection or through a QoS-enabled Layer 2 Switch. Nortel recommends the use of a Layer 2 switch. For ease of cabling it is recommended to put the CP PM Call Server in Slot 1. In addition, a redundant system will use the HSP Port to connect to a secondary call server. This is done either through a direct connection between the two call servers or through a High Speed WAN link from one site to another, in the case of campus redundancy.

There is a main status LED on the CP PM Call Server that indicates the current system status. It can be one of three colors, Red, Yellow, and Green. Additionally it can be blinking or solid, or even off. If the Status LED is red it means that the system is on the Hardware/BIOS level. Once it starts loading the Bootrom and OS it starts flashing red. The light will go yellow as the system starts the first Sysload phase, and flashes yellow during the second Sysload phase. Once the operating software has been loaded and the system is operating normally the light will be a solid green. During the installation process the main status LED will flash green. If the light is off this indicates that there is no power.

In addition to the main status LED there are three additional LEDs that are of importance. The first one is the redundancy LED. The same color options exist here. A red light indicates that there is no redundancy (single mode). A green light means that the system is in a redundant mode and is active. A yellow light indicates that the system is the standby redundancy system. A flashing red or yellow light indicates that the system is in split mode. There are also activity lights for the internal FMD and the external RMD. These lights will flash green when there is activity on these devices.

Finally, there are two push buttons on the faceplate. There is a RST button that is inset into the case (it requires the use of something to depress the button). The RST button will perform a Sysload. There is also a button labeled INI that will re-initialize the CP PM system.

There are two serial ports on the CP PM systems that are available through an MDF connector on the backplane of the MG1000E system. These ports are SDI0 and SDI1. (SDI stands for Serial Data Interface). The default settings for these ports are 9600/8/N/1 with no parity of flow control. Port 0 is used for software installation and maintenance. SDI1 is used for modem/PC access to the operating software. If you are connecting SDI1 to a PC you must use a Modem Eliminator (Null Modem) to connect.

Finally, I would like to briefly mention the keycode. Every CP PM system must have a keycode file to install the software. The keycode file lets the system know what software features are available for use. At a very minimum there are certain packages that MUST be enabled for the system to work. These are:

368 CPP_CNI CP Pentium Backplane for Intel Machine
402
SOFT_SWITCH
403 IPMG


In addition a Branch Office system must have

390 SBO Branch Office

And a High Availability system must have

410 HIGH_AVAIL High Availability.

Installation and Commisioning a CS1000E with Release 5.5

There are a few options when setting up a CS1000E system as to the hardware that is used. A basic configuration will include one or two call servers, one or two signaling servers, a Media Gateway Controller, a data switch, and any trunking resources and voice media gateways.

In previous releases of the CS1000 series of hardware the signaling server and the Small Systems Controller (SSC) were co-located on one card. With the release of the 5.0 software this is no longer the case – now the signaling server is on a separate CP PM card, and the SSC is no longer used, instead we use a Media Gateway Controller. The Media Gateway Controller (MGC) also contains slots for two DSP Daughterboards which provide Digital Signal Processing resources, eliminating the need for a separate card for a Media Card. A separate media card may still be installed to increase the number of resources available.

I will now discuss the physical components of the Media Gateway 1000E.