MIGRATION
DOCUMENT
FOR
CONVERTING
MBM
TO
MAX-NG
Introduction
MIGRATION TO CDOT MAX-NG
With the emergence of Voice-over-IP (VoIP) and convergence of
services over internet, service providers need to migrate from their
TDM based PSTN network to an all-IP network using IP/MPLS
technology. Evolution path to next generation network (NGN) for
most service providers worldwide is the creation of an optical network
at the core. Converged voice, video and data services will be provided
on the core network using IP based protocols. Service providers
require migration from existing TDM based PSTN network to the all-
IP network with minimum disruption in subscriber services.
As almost 50% BSNL’s PSTN switching network is based on CDOT
DSS technology, CDOT has developed cost effective MAXNG solution
on the same line for migration of this entire legacy network to all IP
network. The up-gradation approach is to evolve the CDOT DSS
technology to Soft Switch controlled VoIP. The MAX DSS systems are
being converted to VoIP based systems with minimal hardware
replacement and ANRAX is connected to the core nodes of the
MAXNG systems through V5AG. Maximum functionality is being
implemented in firmware and software to ensure cost effectiveness of
the solution. MAXNG solution retains the line termination circuits,
which constitute a substantial portion of existing equipment cost, to
reduce the migration cost for BSNL.
INTRODUCTION TO CDOT MAX-NG
MAXNG solution is based on de-linking call processing and service
logic functions in the MAX DSS systems from media paths and
moving them out to an external Soft Switch. The Soft Switch is
modular. The Class 5 module implements Local Exchange functions,
while the Class 4 module implements the Tandem functions. All calls
are presented to the Soft Switch as SIP based calls. The Digital Trunk
Media and the SS7 functionalities are also not retained in the switch
and are performed by the specially defined NGN nodes viz Trunk
Media Gateway and the Signaling Gateway. All the access nodes of
MAXNG system interact with the centralized node- Soft switch, in
standard SIP protocol. The media (data, voice & video) and its
associated signaling messages are carried in the form of IP packets in
the network.
In essence, the modifications in MAX hardware and software are
confined to handling the subscriber interface and the remaining call
processing is carried out by the other NGN components of MAX-NG
solution. This architecture permits retention of existing terminal units
for only as long as they are necessary in the BSNL network without
having to retain the associated back end processing modules.
CDOT MAXNG also supports ADSL interfaces which can be
additionally added to the MAX and AN-RAX systems for providing
broadband services at much higher bit rates to the existing fixed lined
customers. The data and voice services are carried on the same local
loop and are separated at customer premises and Exchanges by using
Splitters. With this ADSL approach customer can have one high speed
data access along with voice service on same telephone line.
In rural area, CDOT MAXNG solution provides wireless broadband
service based on Wi-Max technology.
SCOPE OF THE DOCUMENT
This is a technical informative “Migration document for converting
MBM to MAX-NG” for C-DOT MAX-NG.It includes various steps
involved for complete migration exercise. This document intends to
give step by step procedure to migrate MBM exchange to MAX-NG
exchange. Steps for Migration includes Pre-Migration, Migration and
Post-Migration activities, detailed activities and timelines of activities
which are explained in this document.
STEPS FOR MIGRATION
Pre Migration 1. Site Survey.
2. Intimation for WAN IP provisioning in BSNL IP/MPLS network.
3. Verification of BOM (Bill of Material)
4. DATA Extraction by BSNL and communication to NCNGN for frozen data
5. Data Creation at Core site in Class 5 Softswitch, SGP and Class 4 Softswitch, IPTAX and POI.
Migration
7. CACU Physical Installation which includes following activities:
i) Identification of Spare BM.
ii) Installation of CACU System and DDF Frame.
iii) Identification and Laying of E1/PCM.
iv) PCM termination at CACU TAG Block.
v) PCM/Ethernet cable connectivity.
vi) Uplink connectivity to core site.
vii) -48V DC Supply to BM.
8. Software Installation and Configuration which includes
i) Installation, Configuration and verification of CACU cards.
ii) Configuration and Verification of MLS cards.
9. Sample Call testing from co-located BM site.
10. LAGU Installation.
Post Migration
11. Call Verification
12. Site Observation
13. AT Test Cases
Detailed Activities and Timelines for Pre Migration
Site Survey
Site Survey includes information related to infrastructure, number of spare BMs, total
number of working BMs, number of co-located BMs, AN-RAXs, availability and type of
connectivity at RSU s availability and type of Uplink connectivity, SFP connector type,
distance of spare BM (in which CACU chassis will be installed) from DDF and MPLS
Uplink port. The Site Survey sheet is attached in Annexure-I.
This activity requires 2-3 days.
This activity has to be completed at-least 15 days before migration.
Intimation of WAN IP Provisioning in BSNL IP/MPLS Network
Respective Installation teams will intimate BSNL team for IP configuration and configuration of
WAN interfaces in IP/MPLS network for connectivity of access network to core network. i.e. for
CDOT VOIP WAN, SSTP WAN, CDR WAN. This activity should be done at-least 15 days
before actual migration.
Data Extraction
This activity includes extraction of data from IOP terminal and to be done at-least 15
days before actual migration. The output files are to be saved at local PC at access site
and as well as core site. This ED backup has to be taken in cartridge for future reference.
Any modification in the exchange data done after extraction has to maintain in the log
book and changes has to be done manually once MAX-NG migration is completed.
This will require 2 to 3 days and time may vary depending on number of sites.
Verification of BOM
Verify the delivered equipment as per the BOM and this will require 4 hours
approximately.
DATA Creation at Core Site
Create data at core sites which includes execution of csv files which may take 1-2 hours
and this data will be created by the core team at respective core site. Freeze data at-least 7
days before actual migration.
Output files are required for routing related information and TGPs.CMD file which can
be downloaded from C-DOT helpline portal will be provided for execution of commands
and output of files can be saved and sent by mail also.
Detailed Activities and Timelines for Migration
CACU Physical Installation (1-2 Days)
Identification of Spare BM
A spare BM need to be identified for the installation of CACU chassis.
Installation of CACU System and DDF frame
CACU chassis, DDF frame and TAG Block will be installed physically at co-located BM
site for connecting E1s from RBMs.
Identification and laying of E1/PCM
E1 cables coming from RSUs, AN-RAX’s, TAX and POI’s need to be identified at BSNL’s
DDF and spare PCM cable must be laid from BSNL DDF room to CACU tag block.
PCM termination at CACU TAG block
Connect the PCM’s at CACU tag block and proper marking at PCM has to be done.
Divert at least one working PCM (going towards TAX) to CACU before migration of
Line BM.
PCM/Ethernet cable connectivity (One day)
Laying of PCM/Ethernet cable from BPU and TSU at RBM site
Spare PCM cable can be laid and routed from Principal TU to DDF at RBM site as
well or use existing PCM cable. Two Ethernet cables from each Co-Located BM has to
be laid up to CACU, the Ethernet cable at BM must be drop behind TSU of the
corresponding BM.
Uplink connectivity to Core Site
Optical Patch cord has to be laid from CACU chassis up to the optical port available
for the connectivity of MPLS network.
-48V DC Supply to BM
Connect -48V DC to spare BM in which CACU system has to be installed.
Software Installation and configuration (One Day)
Installation, Configuration and Verification of CACU cards
Install and configure SLM, NGTJ, and EBM cards with corresponding software
applications and it may take 2 hours approximately. CACU cards will have pre-installed
software deliverables only configuration of the cards has to be done.
Configuration and Verification of MLS cards
Configure MLS cards and verify connectivity to core site which may take 2 to 3
hours approximately.
Sample Call Testing
Testing of Different call scenarios ( One Day)
Connect the SIP phone at any Ethernet port of MLS given at the backplane of
CACU and make a call to SIP phone available at Core site to verify the connectivity.
Verify the CDR details of calls at core site. Make a FTP account to fetch the CDR by
ITPC and process the CDR, concerned should be addressed if any. Verification is
required by ITPC team for further migration.
LAGU Installation
Installation of LAGU System at Co-located BM and RSU’s site ( 2
hours approx. per RSU site)
At Co-located BM/RBM replace BPU and TSU frames by LAGU chassis.
Configure NGTJ card according to IP list of specific BM. Connect E1s or Ethernet cables
depending on the connectivity to LAGU system. Approximately 2 hours are required for
migrating each RBM site which also includes Call Verification. Total time may vary
depending on number of sites which are to be migrated. To migrate BM to LAG
following steps are to be taken.
Steps for Migration of RSU Site
Shut off the Power of the BM to be migrated.
Un-screw the BPU and TSU frame.
Remove the cables connected at the back plane of TSU and BPU. These cables are TT
cables, TB cables and power cables.
Remove the filters of BPU and TSU frames from the BUS BAR.
Pull out the TSU and BPU frames from the BM cabinet.
Install the new filter box in place of BPU filter boxes at Copy 0 and Copy 1 side of Bus
bar.
For physical installation of LAGU chassis, a fixture needs to be installed first.
This fixture will hold the LAGU chassis vertically. Now in this fixture install the LAGU
chassis
Put the LAGU chassis in the fixture and screw it properly.
TT cables at TU side will remain same.
At LAGU end TT cables have to be connected in position 1A, 1B, 2A and 2B
connectors.
At LAGU TT cables will be connected in the same way as it was connected in the TSU of
MAX BM.
Now connect the power cable for copy-0 and copy-1 of LAGU chassis and make sure
that the cables are connected properly to the newly installed filter box of LAGU chassis.
For TSI cards the power is to be tapped from the back plane of ATU, from the specified
Pins of connector B, behind any of the LCC cards.
Before connecting these TSI power cables at LAGU mother Board, power-ON the
ATU’s and verify the voltages at the connector.
The voltage must be as per the specified range. At red cable the voltage must be 4.5 volt
to 7 volt. The black cable is Digital ground and at the yellow cable the voltage should
vary between -10 to -15 Volts.
In case you are not getting the desired voltage place the connectors in different LCC slot.
In the respective card slots insert the NGTJ and TSI cards
These NGTJ cards will be delivered to site with pre-installed software and root file
system.
Now after the cards are jacked-in Switch-ON the power supply of all the ATU's and
LAGU.
The prints in the minicom terminal will appear showing the booting sequence.
Observe the messages and wait for the LAG to come UP.
Once the LAG is UP, create data through CLI interface using extracted files from IOP for
corresponding BM.
Intimation of CDR provisioning in ITPC of respective zone for MAX-NG
network
Before migrating the site, Clarity will be informed 5 to 10 days before actual migration. No
operations shall be done by Clarity once exchange data will be freezed. After complete
migration exercise, inform respective ITPC for the respective zone. After then only, all
pending orders will be fired.
During migration, CDRs of the corresponding site will be fetched from both MAX and MAX-NG
system that is from both IOP and MAX-NG at same time from the first hour of migration of first
BM. After complete migration activity, CDRs will be fetched from MAX-NG System.
FTP account will be created and details like username and password will be shared for fetching
CDR records for billing purposes.
For MAX subscriber, CDRs can be pulled from the IOP and for MAX-NG subscribers, CDRs can be
pulled from the specified directory created at the core server for the corresponding zone. Once
again, verification of dumping of CDR at core server will be done after complete migration.
Detailed Activities and Timelines for Post Migration
Call Verification ( One day )
Different calls will be tested from each RBM site once LAGU system comes in
Level 5 with test number in exchange itself. Verify CDRs for different calls scenarios at
core and ITPC.
Site Observation
Site will be kept under observation for 24 hours to check stability.
AT Test Cases
AT Test cases will be executed as per the AT schedule for testing of installed CACU and
LAGU units hardware and software wise. This will require 2 or 3 days.
ANNEXURE-I
Technical Site Survey Sheet
ZONE Name
_ _ _ _ _ _ _ _ _ _
Circle Name
_ _ _ _ _ _ _ _ _ _
Site Name
_ _ _ _ _ _ _ _ _ _
Self-Point Code
_ _ _ _ _ _ _ _ _ _
Name of SDCA
_ _ _ _ _ _ _ _ _ _
STD Code
_ _ _ _ _ _ _ _ _ _
Number of other
1. SITE SURVEY FORM:
Site Name : _ _ _ _ _ _ _ _ _ _
Date of Preparation : _ _ _ _ _ _ _ _ _ _
Prepared by (Name &
Designation of BSNL Official)
_ _ _ _ _ _ _ _ _ _
SDCA parented _ _ _ _ _ _ _ _ _ _
Area Codes of other
SDCA (if any)
_ _ _ _ _ _ _ _ _ _
2. CONTACT INFORMATION
Installation Location Information (Postal address of Main Exchange Location):
Site Address: _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _
Switch Room Telephone Number (with STD Code):
_ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _
Contact Details of BSNL Officials:
On-Site Contact
PERSONAL
NAME MOBILE NUMBER EMAIL Address
JTO
SDE/SDO
DE
DGM
GM
Table 2.0: Contact Details of BSNL Officials
3 EXCHANGE CONFIGURATION
Kindly fill the below sheet with the complete exchange related information:
1. Total Equipped Capacity _ _ _ _ _ _ _ _ _ _
_
2. Total Working Capacity _ _ _ _ _ _ _ _ _ _
_
4. No. of Co-located Line BM after Compression _ _ _ _ _ _ _ _ _ _
_
5. No. of RSU’s _ _ _ _ _ _ _ _ _ _ _
RSUs with IP connectivity _ _ _ _ _ _ _ _ _ _
_
RSUs without IP
connectivity _ _ _ _ _ _ _ _ _ _
_
6. No. of AI Interface _ _ _ _ _ _ _ _ _ _
_
7. No. of PRI Links _ _ _ _ _ _ _ _ _ _
_
8. No. of BRI subs (C-DOT will not provide support in MAX-NG
therefore these subscribers will be migrated to other exchange) _ _ _ _ _ _ _ _ _ _
_
9. No. of Data link _ _ _ _ _ _ _ _ _ _
_
10. No. of PCMs Working _ _ _ _ _ _ _ _ _ _
_
11. No. of PCM towards POI _ _ _ _ _ _ _ _ _ _
_
12 Details of special route
12. Availability of GE Port at T1/T2 SW/ OCLAN _ _ _ _ _ _ _ _ _ _
_
13 Approx. length of PCM cable (from switch root to DDF) (in meters)
14 WAN IP provisioning and configuration at PE Router done Yes/No
15 Connector Type (FC/LC/SC)
16 SFP Wavelength (850/1310/1550 nm)
17 Number of frozen subscribers
18 All Area Code of parented SDCAs
19 Area codes of BM
Table 3.1: Detail of Exchange Configuration
4 BM Related Information
Fill the details of RSU/co-located line BM parented to the MBM along with the
type of connectivity available and the exchange code.
RBM /Co-located
BM number
Name of
RBM
Site
Area Code
Exchange/
Subscriber
Level
Type of
Connectivity
(E1 or STM)
Equipped
Capacity
Working
Capacity
Table 4.1: Detail of Remote BM
Note: Kindly add the required numbers of row depending upon
the RSU and co-located BM working.
5 AN-RAX Related Information
Fill the details of AN-RAX parented to the MBM along with the exchange code of
the AN-RAX subscriber.
AI Number Name of AN-RAX Area Code Equipped
Capacity
Working
capacity
Subs Level
working
Table 5.1: Detail of AN-RAX
Note: Kindly add the required numbers of row depending upon
the AN-RAX working.
6 PRI Related Information
Fill the details of PRI parented to the MBM along with the exchange code of the
PRI subscriber.
S.No.
Principal Directory Number of
DDI Group
(PDDI)
Number of Digits
(NUM-DGTS)
Directory Number
(DIRNO)
Table 6.1: Detail of PRI
Note: Kindly add the required numbers of row depending upon
the PRI working.
7. EXCHANGE LAYOUT
Kindly draw the complete layout of your MBM location clearly depicting the position of CM, Local BM,
TBM and VU-BM and DDF. Reference diagram is shown below in Fig 7.0. This may be given by hand
also.
Fig. 7.0 Reference diagram of Exchange Layout
BM-1
LINE
BM-1
LM
BM-2
LM
BM-2
LINE
BM-2
LM
BM-3
VU
BM-4
TRK
BM-5
SUM
BM-6
VU
CM-XL
BM-7
TRK
BM-8
VU
BM-9
LM
BM-9
LINE
BM-9
LM
IOP
RO
OM
Exchange Layout Diagram :
Fig. 4.1: Exchange Layout Diagram
Fig. 7.1: Exchange Layout
Note: This may be drawn by hand also and scanned copy can be attached.
8. NETWORK RELATED INFORMATION
In this section kindly fill the network related information i.e. connectivity towards
different direction/exchange through CC7#7 Links. In case of any working MOD-
R2 or DECADIC links, the same is required to be upgraded to CCS#7 as NGN do
not support MOD-R2 or DECADIC types of signalling. Kindly furnish the
information of SSTP links in the below mentioned table.
Sl. No. Destination Exchange Destination
Point Code
Number of
E1s
Number of
Signalling Links
Eg. OCB TAX Dehradun 8271 6 3(NUC)
1.
2.
3.
Table 8.1: Network Related Information
Also draw a network diagram showing different directions connectivity with MBM. Reference diagram
has been shown in Fig 8.1
Fig. 8.1 Reference diagram of Network Connectivity
Note: This may be drawn by hand also and scanned copy can be attached.
Fig. 8.2 Network Diagram
Fig. 8.2: Network Connectivity Diagram
Note: This may be drawn by hand also and scanned copy can be attached.