Specifications

2-32
Reference Guide
Model No.
Running Head
Management Channel Concentrator (MCC) Server Applications
2.6.7.5 DPNSS Trunk Routing
Digital Private Network Signaling System #1 (DPNSS) is the predominant Common Channel
Signaling scheme used in the United Kingdom for private inter PABX communications.
DPNSS Trunk Routing, provides low delay for multi DPNSS channel provisioning off a single
E1 DPNSS aggregate. This is achieved by mapping the B channels to dedicated time slots
rather than to hunt groups, which in turn provides efficient D channel grooming and
subsequent billing.
2.7 Management Channel Concentrator (MCC) Server
The Management Communications Concentrator (MCC) provides management connectivity
to remote integrated access systems. It can concentrate the TCP/IP management traffic from
up to 131 remote IAD clients onto either a single, local 10 BASE-T Ethernet port, or
encapsulate the information as per RFC1490 on to a Frame Relay link. There can be up to 3
MCC server cards in an IAD chassis in non-redundant operation. The following hardware and
firmware must be included in an IAD to add MCC Server operation:
8803- CPU Control Card with 8 T1/E1 Cross Connect (redundant-capable)
8922/8923/8924xx - 8 T1/E1 Interface card w/ 128K NVRAM.
8813 - Advanced Communication Server (ACS) with 131 logical ports
60520 - Host Firmware version 5.2
63120 - MCC Server firmware
The following protocols are supported by the MCC:
Ethernet Media Access Control Protocol (MAC)
Address Resolution Protocol (ARP)
Internet Protocol, version 4. (IP)
Internet Control Message Protocol (ICMP)
User Datagram Protocol (UDP)
Routing Information Protocol (RIP)
Frame Relay (RFC1490)
The MCC provides management of remote IADs’ using TCP/IP and SNMP/UDP/IP through
the FDL bit of the ESF format if used for T1. For E1, management is provided through the
SA4 bit of the frame following the frame alignment word in time-slot 0. The MCC offers far
more interfaces and functionality than the B7R, thus replacing it, and the device used to route
between the asynchronous aggregate serial port and Ethernet. MCC can be configured to use
unnumbered or numbered interfaces. If unnumbered interfaces are used, MCC is accessed
through the global Ethernet address regardless of what interface is used. If numbered