Max-Ng Access Migration Doc-Old

C-DOT MAX-NG
MAX-TO MAX-NG
MIGRATION MANUAL
CENTRE FOR
DEVELOPMENT OF TELEMATICS
Section No.431-316-1061
System Issue 02 May 2017
Practices
C-DOT MAX-NG
MAX-TO MAX-NG
MIGRATION MANUAL
© 2017, C-DOT
Printed in India
C-DOT MAX-NG
MAX TO MAX-NG MIGRATION MANUAL
ISSUE 02
MAY 2017
JYESTHA 2073
SERIES 100: PLANNING
CSP SECTION NO. 431-101-1061
THIS C–DOT SYSTEM PRACTICE REFERS TO THE C–DOT DIGITAL SWITCHING SYSTEM MAIN AUTOMATIC EXCHANGE NEXT GENERATION (ABBREVIATED AS
C-DOT MAX-NG IN THE REST OF THIS PUBLICATION).
THE INFORMATION IN THIS SYSTEM PRACTICE IS FOR INFORMATION PURPOSES AND IS SUBJECT TO CHANGE WITHOUT NOTICE.
ANY FEEDBACK ON THE DOCUMENT MAY BE SENT AT MXNGPMTC@CDOT.IN.
© 2017 BY C–DOT, NEW DELHI

Table of Contents
Chapter 1. Introduction ...................................................................................................... Error! Bookmark not defined.
1.1.............................................................................................................................. Overview 5
1.2............................................................................................................... NGN Core Network 5
1.3............................................................................................................. NGN Access Network 6
1.4................................................................................................. BSNL C-DOT MAX Network 6
1.5..................................................................................... Migration PLAN of MBM to MAXNG 6
Chapter 2. Pre-Retrofit Activity – Core Network ......................................................................................................... 9
2.1....................................................................................................................... Pre-Requisites 9
Chapter 3. Pre-Retrofit Activity – Access Network .................................................................................................... 29
3.1............................................................................ Steps for Access Site Migration TO MAXNG 29
3.2....................................................................................................................... Pre Requisites 29
3.3........................................................................................ Physical Installation of Cacu System 33
3.4............................................................................. Network Related Configuration and Testing 34
3.5..................................................... Preparation of NGTJ Cards (LAG) for Different BM’S/RSU 36
Chapter 4. Physical Installation of LAGU System ...................................................................................................... 38
4.1........................................................................................................... BM Migration to LAG 38
Chapter- 5 IP Address Configuration IN MLS Card .................................................................................................. 33
Annexure - 6 C-DOT MAX-NG Network Connectivity ................................................................................................. 34
H:\HOME\NG-MAX\User\FinalCDOT-MAXNG-MIGRATION-MAN-V02.doc May 29. 2017

Chapter 1.
BRIEF OVERVIEW AND MIGRATION PLAN

1.1. OVERVIEW
The MAX-NG network is an IP based platform for delivery of voice, video, data and
multimedia services to subscribers. It supports seamless traversal of calls between IP,
PSTN and PLMN networks.
The MAX-NG network is structurally divided into the following four sub-network
segments:
 NGN Core Network for delivery of Services
 NGN Access Network consisting of MAX exchanges upgraded to MAX-NG
exchanges
 Operations Support Network consisting of
i. MAX-NG Billing System Interface
ii. MAX-NG Service Provisioning Interface
iii. MAX-NG Network Management
 The existing IP/MPLS based NIB/NIB-II Transport Network
1.2. NGN CORE NETWORK
The NGN Core Network handles all Session Establishment, Call Processing and Service
Delivery functions centrally. The core network consists mainly of following servers.
 C5 Softswitch
 C4 Softswitch
 Session Border controller (SBC)
 Rating Engine
 SG Server
 EMS Server
 LIS Server
 NOC
MAX-TO MAX-NG MIGRATION MANUAL 5

Chapter 1.
1.3. NGN ACCESS NETWORK

The NGN Access Network is the C-DOT DSS MAX exchanges upgraded to MAX-NG.
After the upgrade to MAX-NG, the Base Processor Unit and Time Switch Unit in Base
Modules of MAX exchanges are no longer required. Only TSI cards from Time switch unit
will be required and terminal Units (TU) which terminate PSTN subscribers are retained
for providing migration of existing users to MAX-NG. The TUs are connected to a new
unit called the Line Access Gateway (LAG). The LAG converts PSTN connections to
SIP/IP sessions and forwards them to a central software based switching exchange (Soft
switch).
Central Access Control Unit (CACU Chassis): In every MBM system one CACU System
will be installed. CACU, which is a 6-Slot Chassis to in house 02 Nos. of Network Access
Gateway Cards (for SG/MG/V5/PRI applications), 02 Nos. of Main LAN Switch (C-DOT
Aggregator) and 02 Nos. of Ethernet to E1 Main Card along with Shelf Manager (SLM)
Card.
1.4. BSNL C-DOT MAX NETWORK
The whole BSNL Network administratively and technically partitioned into 24 Telecom
Circles. Most of the telecom circles are equivalent to states except UP-E &UP- W, NE-1 &
NE-2 and the head quarter of telecom circles are mainly the capital of the state. SDCA is
the smallest administrative division of telecom. In every SDCA there is a Main exchange.
Remote exchanges or RSU’s are parented to SDCAs main exchange and some rural
exchanges i.e. AN-RAX/WLLs are also parented to Main exchanges of SDCA. The main
exchanges (ILT Exchange) are connected to L2 TAX of SSA over CC7 interface. C-DOT
MBM is working at most of the SDCAs and as per the migration plan, every C-DOT MBM
will be converted to MAX-Next Generation (i.e. MAX-NG).All SDCA MBMs which are
comprise of Local BMs, Remote BMs, AN-RAXs, WLLs & PRI PBXs will became Access
Equipment and will be a part of access network. At every SDCA a CACU chassis will be
installed, a detail description of CACU is discussed in the later section of this document.
The access network will be controlled by centrally located C-DOT Soft switch i.e. core
network. Each CACU will be directly connected to IPTAX over IP wherever possible
otherwise it will be connected to next higher level exchange or IPTAX over SS7.
1.5. MIGRATION PLAN OF MBM TO MAXNG
There will be 8 core sites for each zone, having MAXNG core equipment’s. as mentioned
in section 1.2 Al four zones of India i.e. North, South, East & West will have 2 core sites
each .One site will act as Primary site & other site will act as geographical redundant site
for corresponding Primary site and vice versa.
North Zone will have two core sites at Gurgaon and Chandigarh.
South Zone will have two core sites at Bengaluru and Hyderabad.
West Zone will have two core sites at Bhopal and Pune.
East Zone will have two core sites at Cuttack and Kolkata.
6 C-DOT MAX-NG
In each circle two sites will be migrated by BEL / ECIL teams with the help of C-
DOT,therefore, total 48 SDCAs of 24 circles are planned to be migrated by BEL & ECIL
with the help of C-DOT.
In C-DOT MAX-NG Helpline portal, BSNL circle user will approve SDCA username.
Through portal, SDCA concerned person will create Username and Password and Circle
User will approve same. After this , SDCA user will enter SDCA specific details regarding
Number of RSUs, Number of co-located BMs, No. of AN-RAXs , Number of PRI , etc .
Then SDCA user will inform Circle User. Circle User will enter Start IP Address of
concerned SDCA and list of IPs i.e. LAN IP and WAN IP of concerned SDCA.IPs will be
automatically through portal itself. User can Download or give print through options
available in portal itself. You can also save Excel Sheet in PC/Laptop itself.
Circle level BSNL teams designated for further conversions of sites in their respective
circles will be provided hands-on training in the corresponding two sites of the circles.
Each exchange will take around 7 to 8 days for migration including pre-retrofit activity,
migration to MAXNG and AT of the site.
The migration strategy has been planned in such a manner so as to minimize the actual
system downtime.
The data of sites to be migrated will be created offline in advance at core sites in softswitch
& rater.
The downtime will be from 90 to 120 minutes on an average for each BM. During
migration downtime will be there for BM being migrated only. Other BM’s will continue to
work in normal manner. Thus a total partial downtime of a complete MBM will vary
depending on the number of BM’s working and depending on the BM’s being converted
parallel or sequentially subject to availability of trained manpower for migration.
First of all, for preparation of NGTJ cards as per the site configuration test LAGU setup
will be prepared in CACU chassis in vacant space with one ATU frame. Check all TIC IDs
i.e. tic01-0, tic01-1, tic05-0, tic05-1, tic09-0, tic09-1, tic13-0, tic13-1 with NGTJ card and
dialtone after execution of bulk script by Core Administrator. This will be done for each
RSU site in 2-slot chassis installed in identified spare BM in which CACU chassis will be
installed. Before proceeding for migration, take printout of TIC IDs and PIC ID of working
exchange.
For this login into IOP of concerned exchange using Username admn and Password
CDOTadmn. Type crp and press enter.
Enter following command to check status of working TIC IDs and PIC ID in MAX
Exchange.
#displ-sys-all

Chapter 1.
For hardware retrofit in each LINE BM and RSU’s, choose BMs which have unique levels
to be retrofitted first and after this plan rest of the BMs to be retrofitted.
During migration, the BM’s migrated to LAGU will be able to make outgoing calls only as
incoming route will be activated after complete site migration. So incoming calls to BM
converted to LAGU will be activated only after all BM’s of the site are migrated.
Site In-charge and Migration team will intimate GM of respective site before proceeding
for Migration.
Site In charge should fill data in prescribed Data template. Verification and
Correction of data must be done by circle nodal team. Vetted data should be provided
to core team at T-1 day where T is the date of actual migration.
Routing and data creation should be done in Class 5 & Class 4 Softswitch in core network at T-1
day.
Approximate time for BM retrofit will be around 2 to 2.5 hours. Outgoing calls will work
immediately after BM migration. Incoming calls will not be possible until calls
from the IPTAX are diverted to MAX-NG core.
Ethernet connectivity at RSU sites to CACU Chassis is preferred over E1

connectivity. Therefore kindly ensure readiness of media connectivity before
actual migration.
It was decided earlier that CDR support for POI will be provided in next release,
hence as discussed with GM, NCNGN, POIs will work with existing DSS MAX.
IOP, required trunk BMs and CM will remain working as it is. The alternate solution is
that these POIs can be shifted to another switch so that DSS MAX can be switched off
to take advantage of power saving.
Tested and working spare cards (TUI, TIC, SPC, TSI, PSU, and LCC) should be available at
site at the time of migration. Spare SCIC card can be used as TIC card.
Before Migration, lst files should be generated by Core In-charge/Administrator and at the
same time, Thin Client PC installed in MBM site should be accessible. Core Administrator
will run scripts both for access and core at T-1 day before actual migration. After execution
of scripts, please check file sizes, number of subscribers. File sizes will be checked by ls –ls
8 C-DOT MAX-NG
command. Check number of subscribers by #displ line_counters in CLI of NGTJ card.

Procedure for CLI is as follows:
# telnet <IP address of NGTJ card> 3333 where 3333 is the port code
Here , root and public is the Username and Password of CLI.
After logging into this , give command #displ line_counters to check total number of
subscribers in MAX-NG system i.e. migrated LAGU System.
Before proceeding for actual migration at RSU sites, Take Medical Emergency Kits and
some food supplements.
After creation of MAX- NG data in Core and Access network, core incharge will run audit
utilities which will verify MAX and MAX-NG data then only Core Administrator will send
output files by ftp to Thin Client at /home/cdot and /root location. Now, Core
Administrator will intimate access Administrator / Site In-charge / Migration Team that
data is ready for retrofit telephonically or by E-Mail. Now Access in-charge will
acknowledge same.
At Core Site, before creation of core data take backups of each node SBC, C5, C4, Rater,
NGEMS, LAGEMS.
For V5/PRI subscribers, numbers of subscribers will be checked by FE.
Note: Backups at core site of respective elements i.e. C5, C4, Rater, SBC, NGEMS,
LAGEMS must be taken before site migration
Following point must be kept in mind during MAX-NG migration activity and are as
follows:
i) Before starting MAX-NG Migration, a PC with Internet connection is required. Connect

PC to internet and go through MAX-NG Videos available on the below google drive
link.
https://drive.google.com/open?id=0BwopHy_VRqwINHREcHNRSlFDdVU
Copy and paste the above link in chrome or Firefox browser in PC/Laptop
Going through Videos is must.
ii) For understanding MAX-NG Network architecture, please follow P94-PI-ARC-MXNG-

v04 document. The S.No. can be checked in INDEX.

Chapter 1.
iii) Please fill Site Survey Sheet and Checklist as per attached document in which all details
related to BMs,RSU,AN-RAXs and POIs, etc. are required. The S.No. can be checked in
INDEX.
iv) For connecting MAX-NG access network to Core network, WAN (definition given below)
interfaces are required to be defined and created in IP/MPLS network. Accordingly,
please send attached WAN IP and LAN IP to concerned teams for configuration of
specific site planned for migration.
Definitions:
i) A wide area network (WAN) is a geographically distributed private
telecommunications network that interconnects multiple local area networks
(LANs). Multiple LAN networks can be connected through routers in
Telecommunication networks.
ii) A local area network (LAN) is a network that connects computers and other devices
in a relatively small area, typically a single building or a group of buildings.
Most LANs connect workstations and personal computers and enable users to
access data and devices (e.g., printers and modems) anywhere on the network.
iii) A virtual LAN (VLAN) is any broadcast domain that is partitioned and isolated in a
computer network at the data link layer (OSI (Open System Interconnections)
layer 2). ... VLANs allow network administrators to group hosts together even if
the hosts are not on the same network switch.
iv) The Open Systems Interconnection model (OSI model) is a conceptual model that
characterizes and standardizes the communication functions of a
telecommunication or computing system without regard to their underlying
internal structure and technology. ... The original version of the model defined
seven layers.
v) VLAN (Virtual Local Area Network) Tagging is the practice of inserting a VLAN ID
into a packet header in order to identify which VLAN the packet belongs to.
More specifically, switches use the VLAN ID to determine which port(s), or
interface(s), to send a broadcast packet to. Tagging (Switching) is a flexible and
efficient network communication mechanism used to transmit Internet Protocol
(IP) traffic over a telecommunications network.
vi) Switches create a network. Routers connect networks. A router links computers to
the Internet, so users can share the connection.
vii) The main purpose of a virtual network is to enable a data center or service provider
network to provision the most suitable and efficient networking structure for the
applications it hosts – and to alter that structure as conditions warrant, using
software rather than requiring physical changes in connections to hardware.
v) Multiprotocol Label Switching (MPLS) is a type of data-carrying technique for high-

performance telecommunications networks. MPLS directs data from one network node
10 C-DOT MAX-NG
to the next based on short path labels rather than long network addresses, avoiding
complex lookups in a routing table.
vi) As per PAN INDIA IP planning, WAN IPs & LAN IPs have been already planned.LAGU
& CACU Systems are required to be configured and allowed in IP/MPLS network with
unique WAN IP and LAN IP for specific site planned for migration.
vii) Check connectivity to core network such as C5, SBC and C4 from access network for
example Thin Client PC.
Command to check connectivity:
# ping <IP Address of C5 Softswitch>
# ping <IP Address of SBC>
# ping < IP Address of C4>
Softswitch IP of corresponding core site may be 10.187.0.15 for Gurugram Core Site, 10.187.1.15
for Chandigarh Core Site, etc.SBC IP of corresponding core site may be 10.187.0.12 for
Gurugram Site, 10.187.1.12 for Chandigarh Site.
If core site is not connecting, for reachability of core site traceroute command is used.
#traceroute <IP Address of core node>
#traceroute <IP Address of Class 5 Softswitch>
Note: IP Address may be 10.187.0.12 for SBC, 10.187.0.15 for C5 Softswitch for Gurugram
Core Site.
viii) Order of documents to be read is as follows:

a) MAX-NG General Description document having overview of MAX-NG
Project. (Introduction, Upgradation, Access Network Architecture,
Integration, etc.)
b) General Administrative document having administrative details for
migration. (Summary of Important Migration Steps, Migration Document
for converting MBM to MAX-NG )
c) Main LAN Switch (MLS) document having description, details and
configuration procedure in MLS card.
d) WAN IP & LAN IP details required to be configured in BSNL/IP MPLS
network.
e) Installation and configuration documents of LAGU & CACU System.
f) Procedure approved by Director, CFA, BSNL.

Chapter 1.
g) Matrix for Call Testing post migration which is available on google drive link
https://drive.google.com/open?id=1axpE7Pl8skghg6gNVZyLuas2-MrW7sdo
ix) As per document at S.No. 5, Template has to be filled by ITPC (IT Project Circle) which
takes approximately 3-4 days and need to be verified by Exchange Incharge and same
will be sent to respective circle teams for migration activity. In case of any
discrepancies, incharge will communicate same to ITPC and nodal team.
x) Please follow Installation and configuration documents of LAGU & CACU System.
xi) Note: Exchange person will take ED & BD backup before actual migration and keep it in
safe custody.
xii) After preparation and installation of CACU and LAGU System, a sample call is tested
from access network to different PSTN and Mobile networks as per Matrix attached in
mail. Make a sample call from SIP phone connected to CACU system and PSTN phone
connected to each LAGU System (Co-located & Remotely located Unit).
xiii) Site Monitoring for 2 to 3 days.
1.6 FLOW of activities during MAX-NG Migration

1. Site Survey :-
Site survey will be done atleast 15 days before actual date of migration
2. MAX-NG Equipment delivered at SSA store
3. MAX-NG Equipment delivered at SDCA site
4. Verification of delivered Equipment as per BOM ( Bill of Material) list.
5. Enter Site Survey details by SDCA user through user login details in MAX-NG Project
Management Web portal. Start IP address will be entered by Corporate user. Then only
portal will automatically generate IP addresses of CACU and LAGU Systems depending on
number of co-located BM and RSU sites.
12 C-DOT MAX-NG
5. Take IP list and site configuration details of identified site for migration from MAX-NG
Project Rollout Management portal. Also take details of PR/GR configuration also. For any
issues/concerns, please contact core site administrator.
6. LAN and WAN IP provisioning in IP/MPLS network.
7. Configuration of MLS cards at SDCA site and Uplink connectivity to respective core site.
8. Software Installation and Configuration in CACU cards i.e. SLM,NGTJ,MLS and EBM
cards at SDCA site.
9. Software Installation and Configuration in CACU cards.
10. Configuration of SIP phone and sample Call Testing of all PAN-INDIA circles from
Test number connected to CACU unit. Core user will create sample number in core data.
Intimation will be sent by SDCA user and Core user will acknowledge same. Alongwith
this, Subscriber and Routing Data will also be created by Core Administrator. Also
differential data will be created alongwith actual data.
11. Check Uplink connectivity and Call Testing from sample number of SIP test
subscriber.Also check all types of calls from SIP subscriber.
12. Preparation and configuration of LAGU cards in 2-slot chassis mounted in same BM.
Alongside provisioning of Ethernet connectivity at RSU sites if possible otherwise
provisioning of spare E1s from RSU sites. Laying of Ethernet cable from co-located BM to
CACU units.
13. Take printout of all TIC IDs , PIC IDs , TSI copy of working MAX exchange ( RSU/co-
located) or not down same before migrating exchange to MAX-NG. Same information may
be taken from IOP using command #displ-sys-all
14. Retrofitting of co-located BM and RSU which includes replacing BPU and TSU units by
2-slot chassis and NGTJ cards.
15. Test all types of calls from migrated exchange.
15. Diversion of AN-RAX and PRI E1 to CACU System and configuration in NGTJ card
for connectivity.
16. Switch OFF CM,TBM and IOP once all BMs, AN-RAXs and PRI exchanges will be
migrated.
17. Discover all nodes in LAGEMS and NGEMS and monitoring of site for 24 hours post
migration.
18. Acceptance Testing and Commissioning of Site.

Chapter 1.
14 C-DOT MAX-NG
Chapter 2.
Pre-Requisites & Data Creation in Class 5

Softswitch– Core Network
2.1. PRE-REQUISITES
The site under migration will receive site survey sheet along with WAN and LAN IP details
from respective migration team (BEL/ECIL/BSNL). The exchange incharge will fill the site
survey sheet as per the prescribed format and send back to the migration team. Exchange
incharge will also do IP provisioning of WAN & LAN network as per the WAN/LAN IP
details. For PAN INDIA LAN & WAN IP Address, please follow below google drive link
https://drive.google.com/drive/folders/0B4p-A3NGB0piWHdibUliZXR1aFk?usp=sharing
On the basis of the details provided in survey sheet, user will be created in C5 along with
an operator with Admin rights by the core incharge.
The login id & default password for the sites will be informed by core incharge to
respective site administrator.
The site operator will login to soft switch GUI with given login id & default password for
the site.
On first login the site operator shall change his password & login to softswitch with
changed password.
The core incharge or the site operator can create corresponding LAG’s with given IP
addresses for the site in soft switch
All current MBM site data has to be filled in prescribed DATA template by site in-charge.
Site in-charge must get data from respective ITPC before 7 days (T-7) of migration. Site
in-charge has to fill data template with the help of Data from ITPC and some additional
data which he can retrieve from working IOP. Site in-charge will take the ED/BD backup
and keep in its repository. Filled data template will be send to the circle nodal in-charge for
verification latest by T-2 days. The nodal in-charge will send the vetted data to the
respective MAX-NG core and it must be reach to the core site at T-1 day. The period T-7 to
T-2 is said to be a black out period during which creation and deletion of subscriber is not
allowed. Other modification related activity such as ten modification etc., exchange in-
charge will note down and will update manually after migration. On receiving the data
template on T-1 day core in-charge will examine it and if found ok he will create data in
the core server, in case there is any discrepancy in data template he will sent it back to the
circle nodal in-charge for correction.
15 C-DOT MAX-NG
Chapter 2.
Note: ITPC need to be informed at-least 2 working days in advance

so that migration at Clarity may be planned accordingly.
2.1.1. C5 Softswitch
 Data creation in Soft switch is done using soft switch GUI (super user by C-DOT
only) till the creation of site administrator. After creating site administrator,
credentials will be shared to the BSNL operators (SDCA specific) to
create/modify/delete subscribers. Following is example of NUH (SDCA site) in
Haryana:-
Access the C5 GUI of the particular zone using URL:-https://<ip>/softswitch
COUNTRY CREATION
INDIA
91
16 C-DOT MAX-NG
PRE-REQUISITES & DATA CREATION IN CLASS 5 SOFTSWITCH– CORE NETWORK
STATE CREATION
STATE NAME : HARYANA
STATE CODE : HA

Chapter 2.
CITY CREATION
CITY CREATION : NUH
CITY CODE : 1267
18 C-DOT MAX-NG
AREA CODE GROUP CREATION

AREA CODE GROUP NAME : C5GROUP_NORTH
AREA CODE : 1267

Chapter 2.
ROUTE DEVICE CREATION

ROUTING DEVICE NAME : C4_NORTH
ROUTING DEVICE IP&PORT : 10.187.0.29:5060
ROUTING DEVICE TYPE : C4
20 C-DOT MAX-NG
GROUP CREATION
GROUP NAME: GROUP_HA

Chapter 2.
OPERATOR CREATION
LOGIN NAME : Admin_1267
OPERATOR PASSWORD : Admin123
EXCHANGE CODE : 271,278,274,275
22 C-DOT MAX-NG
ZONE CREATION
{ LOG IN WITH OPERATOR }
ZONE NAME : NZ1267

Chapter 2.
LAG ADDITION
LOG IN WITH OPERATOR
LAG NAME : LAG_NUHU
LAG IP : 10.187.212.38
LAG PASSWORD : 1234
24 C-DOT MAX-NG
LAG ADDITION
LAG NAME : LAG_UJJINA
LAG IP : 10.187.212.46
LAG PASSWORD : 1234

Chapter 2.
LAG ADDITION
LAG NAME : LAG_PARA
LAG IP : 10.187.212.54
LAG PASSWORD : 1234
26 C-DOT MAX-NG
LAG EXCHANGE MAP

LAG_NUH:271 274
LAG_UJJINA: 275
LAG_PARA: 278
BILLING INFO
PRIMARY SERVER IP: 10.187.0.18 (IP OF RATER)
PRIMARY SECRET: secret

Chapter 2.
Complete site data has to be compiled into a file and same will be injected in
softswitch.
2.1.2. C4 Softswitch
All specific levels of a particular SDCA have to be created for respective
IPTAX/L2TAX/L1TAX in C4 softswitch.
28 C-DOT MAX-NG
Chapter 3.
STEPS AND PHYSICAL

INSTALLATION,CONFIGURATION –ACCESS
NETWORK
3.1. STEPS FOR ACCESS SITE MIGRATION TO MAXNG
3.2. PRE REQUISITES
i. Receiving of MAX-NG Equipment (as per BoM)
a) A PC has to be installed at MBM site with internet connection.
b) Login to C-DOT Project Management site & click on MAX-NG Project
Management option on top as per the SDCA login.
c) Download the BOM of SDCA.
ii. Check & Verify delivered material at SDCA site as per BoM in Project
Management portal.
iii. Verify received material as per BOM.
iv. For IP Addresses of Access sites , please follow google drive link
https://drive.google.com/drive/folders/0B4pA3NGB0piWHdibUliZXR1aFk?usp=sharing
For Pre-requisites for migrating MAX-NG access network , please refer Appendix-B. please read
instructions carefully which will help in better understanding approach and implementation
during actual migration.
v. Verify IP addresses as per the Web-portal data for respective site for all the Access
hardware.
For migration of LAGU and CACU sites, please watch installation videos before
proceeding further which can be downloaded on official website of C-DOT
http://www.cdothelpline.cdot.in
a) At home page click MAX-NG PROJECT MANAGEMENT
b) Login to your account
c) Click on Documents
d) Select VIDEOS

Chapter 3.
xiv) Before starting MAX-NG Migration, a PC with Internet connection is required.

Connect PC to internet and go through MAX-NG Videos available on the below google
drive link.
xv) For understanding MAX-NG Network architecture, please follow P94-PI-ARC-MXNG-v04

document.
xvi) Please fill Site Survey Sheet and Checklist as per attached document in which all
details related to BMs,RSU,AN-RAXs and POIs, etc. are required.
xvii) Please read MAX-NG General Description document to have an Overview of MAX-
NG Migration activity and Network Connectivity as per attached Document
xviii) For connecting MAX-NG access network to Core network, WAN (definition given
below) interfaces are required to be defined and created in IP/MPLS network.
Accordingly, please send attached WAN IP and LAN IP to concerned teams for
configuration of specific site planned for migration.
Definitions:
viii) A wide area network (WAN) is a geographically distributed private
ix) A local area network (LAN) is a network that connects computers and other devices
in a relatively small area, typically a single building or a group of buildings.
Most LANs connect workstations and personal computers and enable users to
access data and devices (e.g., printers and modems) anywhere on the network.
x) A virtual LAN (VLAN) is any broadcast domain that is partitioned and isolated in a
computer network at the data link layer (OSI (Open System Interconnections)
layer 2). ... VLANs allow network administrators to group hosts together even if
the hosts are not on the same network switch.
xi) The Open Systems Interconnection model (OSI model) is a conceptual model that
characterizes and standardizes the communication functions of a
seven layers.
xii) VLAN (Virtual Local Area Network) Tagging is the practice of inserting a VLAN ID
into a packet header in order to identify which VLAN the packet belongs to.
More specifically, switches use the VLAN ID to determine which port(s), or
interface(s), to send a broadcast packet to. Tagging (Switching) is a flexible and
30 C-DOT MAX-NG
STEPS AND PHYSICAL INSTALLATION,CONFIGURATION –ACCESS NETWORK
efficient network communication mechanism used to transmit Internet Protocol

(IP) traffic over a telecommunications network.
xiii) Switches create a network. Routers connect networks. A router links

computers to the Internet, so users can share the connection.
xiv) The main purpose of a virtual network is to enable a data center or service
provider network to provision the most suitable and efficient networking
structure for the applications it hosts – and to alter that structure as conditions
warrant, using software rather than requiring physical changes in connections to
hardware.
xix) Multiprotocol Label Switching (MPLS) is a type of data-carrying technique for high-
xx) As per PAN INDIA IP planning, WAN IPs & LAN IPs have been already planned.LAGU
& CACU Systems are required to be configured and allowed in IP/MPLS network with
unique WAN IP and LAN IP for specific site planned for migration.
xxi) Types of SFP connectors are SC, LC, FC type and wavelength of 1310nm and
1550nm. At both sides C-DOT MLS side and Transmission end, both SFP connectors
should be of same make and same Wavelength.
xxii) Follow data retrofit steps given in Appendix-O for Data retrofit steps using LAG CLI.
xxiii) Order of documents to be read is as follows:

h) MAX-NG General Description document having overview of MAX-NG
Integration, etc.)
i) General Administrative document having administrative details for
j) Main LAN Switch (MLS) document having description, details and
k) WAN IP & LAN IP details required to be configured in BSNL/IP MPLS
network.
l) Installation and configuration documents of LAGU & CACU System.
m) Procedure approved by Director, CFA, BSNL.
n) Matrix attached for Call Testing post migration.

Chapter 3.
xxiv) Before starting activity, please go through procedure already approved by Director,
CFA, BSNL.
xxv) Please follow Installation and configuration documents of LAGU & CACU System.
xxvi) Note: Exchange person will take ED & BD backup before actual migration and keep
it in safe custody.
xxvii) After preparation and installation of CACU and LAGU System, a sample call is
tested from access network to different PSTN and Mobile networks as per Matrix
attached in mail. Make a sample call from SIP phone connected to CACU system and
PSTN phone connected to each LAGU System (Co-located & Remotely located Unit).
xxviii) Site Monitoring for 2 to 3 days.
3.2.1. IP Address requirement for access Equipment:

MAX-NG ACCESS NODES IP ADDRESS REQUIREMENTS and allocations as
per the following sequence:
I. 2 IP addresses for the SDCA in the range allocated will be used as follows:
a) 1 Network IP address (1st IP address in the allocated range for
SDCA) and
b) 1 Broadcast IP address (Last IP address in the allocated range for
SDCA)
II. 6-Slot Chassis CACU: One CACU is required for every exchange (MBM or
SBM) which has to be migrated to MAX-NG. Each CACU requires 24 IP
addresses as follows:
a) 2 MLS cards : 6 IP addresses ( 3 IPs for each MLS card ).The three IP
addresses allocated for each MLS are as follows:
i. One Gateway IP or MLS management IP for the Network to which
the core network is to be connected.
b) 2 SLM cards : 3 IP addresses (one floating IP and 2 physical IPs)
c) 2 EEB cards : 2 IP addresses (one for each)
d) 2 NGTJ cards : 12 IP addresses (6 IP addresses for each NGTJ card
as given below):-
i. 1 physical IP address (eth0) for each NGTJ card
ii. 1 DSP IP address for each NGTJ card
iii. 4 virtual IP addresses for 4 Gateway applications in the order MG,
SG, V5 and PRI
d) Client terminal IP Addresses : 1
 Total IP addresses per CACU: 24 (6+3+2+12+1)
III. 2-Slot Chassis LAGU: At each BM i.e. RSU & co-located BM site, BPU and
TSU units will be replaced by one LAGU unit. Each LAGU has two copies of
32 C-DOT MAX-NG
LAGs for support of duplex mode. A total of seven IP addresses are required
for each LAGU as follows:
a) 1 physical IP for each LAG card.
b) 1 IP for each DSP interface in both the LAGs.
c) 1 Floating IP for the LAGU.
d) 1 fixed IP each for Mate eth1 link communication between 2 LAGs.
e) Total IPs addresses per LAGU : 7 (2+2+1+2)
 Total IP Address required for each SDCA = 2+ 24 + 7* (No. of LAGU)
3.3. PHYSICAL INSTALLATION OF CACU SYSTEM
Watch CACU & LAGU installation video before proceeding further.
Find a spare BM in which CACU System is to be installed and do the following activities:-
1. Switch OFF the power of the rack.
2. Remove all TT, TB and power cables.
3. Remove all filter boxes.
4. Unscrew and remove all frames of rack.
5. Now install new filter box for Copy 0 and Copy 1 at each side of bus bar.
6. For physical installation of CACU chassis, a fixture needs to be installed. The
fixture will be installed at 2nd and 3rd TU positions in identified BM, which will be
required to hold the CACU chassis in vertical direction.
7. Install the CACU chassis in this vacant space. Put CACU chassis in the fixture,
now place this frame support assembly and screw it properly.
8. At top of the MAX-NG BM i.e. at first TU position, put a card cage without
backplane of any spare frame. This will be used to mount DDF TAG block for
termination of E1/PCMs being used in the MAX-NG system from TDM TAX, Remote BMs
and AN-RAXs.
9. PCM cables are delivered with CACU chassis for termination of E1’s used for
V5/PRI/SS7/RSU interfacing to new MAX-NG hardware.
10. After verifying -48V DC connect power cable for copy-0 and copy-1 of CACU chassis to
newly installed filter box and make sure that power cables are connected properly.
NOTE: The existing E1s from the AN-RAXs, IP-TAX, PRI, RSUs etc. are currently
routed to the Trunk BM or VU BM or Central Module (CM) of the exchange. Now
we need to identify these E1s at the Cable entry point and during the migration, re-
route E1s to this newly installed TAG block. Make sure that the length of E1 cables
is sufficient to reroute them to the TAG block during migration. From TAG Block,
these E1 cables are to be extended through a PCM cable to the respective connectors
at the back plane of CACU that is 3C, 4C, 5C and 6C.

Chapter 3.
Slot 3C and 4C are for the termination of TAX/POI E1s, AN-RAX E1s and PRI E1s
to the NGTJ card depending upon which application(SG/MG/V5AG/PRIAG) is
installed in the NGTJ card. Slot 5C and 6C are for the termination of RSU E1s to
EBM card as per the requirement.
3.4. NETWORK RELATED CONFIGURATION AND TESTING
i. Jack in all cards in respective slot of CACU chassis which are delivered at site.
ii. Connect Thin Client to MLS card and assign IP address to thin Client if not
configured.
For assigning the IP address to thin client do the following:
Go to setting
-MAX-NG (Give Any Name to The connection)
Address
this site
iii. MLS cards are powered on by itself, when jacked-in the CACU Chassis.
iv. Access MLS cards through minicom and configure IP in MLS card.
Note: Refer MLS installation document for the same. (Chapter-5 & Chapter-6)
v. Connect one end of optical patch cord to either 21 or 22 port (Uplink ports) at front
face plate of MLS card and connect another end to configured Uplink port for connectivity
to IP/MPLS and MAX-NG respective core network.
vi. Configure MLS card for Uplink connectivity to MPLS.
vii. Configuration at BSNL MPLS end is also required. This has to be done at-least 15
days before actual migration by MPLS NOC.
viii. After configuration, bidirectional connectivity between respective Access site and
core site shall be tested by Pinging the TEST-IP of the MAX-NG core site. For IP addresses
of core network, please refer IP address list of corresponding Zone and corresponding site.
ix. Ensure reachability by pinging IP address of IPTAX, SSTP, CDR and MAX-NG
core network.
Now open terminal in Thin Client, check connectivity and reachability of MAX-NG
core network. Following is the command:-
# ping 10.187.1.12 (where 10.187.1.12 is the IP of SBC in MAX-NG
Chandigarh core network)
Following print will appear if the connectivity is through.
PING 192.168.3.75 (192.168.103.75): 56 data bytes
34 C-DOT MAX-NG
64 bytes from 192.168.103.75: icmp_seq=0 ttl=64 time=5.080 ms

4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 2.362/3.188/5.080/1.111 ms
Similarly ping the IP addresses of corresponding SSTP, CDR and verify
reachability of access network with core network.
x. Verify IP addresses of other cards as well i.e. SLM, EBM and NGTJ.
For verifying the IP of the NGTJ card login in to the card through serial cable, a
root prompt will appear. At the prompt do the following.
root@NGTK] cd /jffs2/conf
root@NGTK] cat net
/sbin/ifconfig eth0 down
/sbin/ifconfig eth0 10.187.3.228 netmask 255.255.255.0 broadcast 10.187.3.255
/sbin/route add default gw 10.187.3.2
/sbin/ifconfig eth0 10.187.3.228 up
All the IP’s should be as per the allocated list. The modification can be done
through vim editor if required. Refer Annexure-3
xi. Install applications in all cards which are delivered with CACU chassis.
Please refer CACU Installation Procedure Document (Annexure-3)
xii. Login to SLM, NGTJ, EBM and check processes once cards come UP. For checking
processes, refer installation manual of CACU system.
xiii. After installation of CACU chassis and insertion of cards, connect configured SIP
phone to MLS card.
For configuring SIP phone, select CONFIG from the menu, and define the following
Number = 91-1360-250000 [Country code -Area code- Subscriber
number]
This number and the reg password must be created in the C5 softswitch first
PASS = **** [Default registration password 0000]
Select IP allocation type STATIC.
Give the valid IP against IP =10.197.5.175
Give the valid netmask against NETMASK =255.255.255.0
Give the valid Gateway IP against G/w =10.197.5.175
Give reboot from the menu.

Chapter 3.
There will be two test numbers created in softswitch for testing purpose only. Make
sure that two numbers are created in core softswitch for Call testing. Connect
configured SIP phone with MLS cards and subscribers will be registered in core
softswitch.
xiv. Make a call from configured SIP phone to core site to test speech and signaling.
One test Number is already created and available at the core site of that ZONE
which can be called to check the speech quality.
xv. Make all types of calls i.e. Local, STD and PSTN/PLMN networks.
The routing data for each SDCA will be created in Class 4 softswitch therefore
PSTN/PLMN network must be reachable and call should be successful.
3.5. PREPARATION OF NGTJ CARDS (LAG) FOR DIFFERENT BM’S/RSU

1. First jack out NGTJ card from CACU chassis i.e. 3rd slot of CACU chassis.
2. Jack in NGTJ card which has to be prepared for LAGU site.
3. Access NGTJ card through serial RS-232 (minicom cable) and check net file in
/jffs2/conf/net file. Follow the sequence of commands to access net file, the IP’s in
the net file should be as per the IP allocation for that LAG.
# mount /dev/mtdblock0 /jffs2
# cd /jffs2/conf
# cat net
# chmod 777 net
4. Assign IP address of LAG card as per the IP list in the net file of same NGTJ card.
Refer IP address list for the same.
5. Gracefully shutdown and reboot NGTJ card so that it can be accessed on same IP
segment.
6. Ping IP address of NGTJ card i.e. self IP address of NGTJ card in the net file.
7. Prepare mmc in the NGTJ card and card should come UP and check Level 5 of
NGTJ card at the same time.
Create data for specific BM using files which were extracted from IOP.
8. Prepared NGTJ card has to be installed in the specific BM for which this card is
prepared.
9. Shutdown NGTJ card and jack out from CACU chassis. LABEL site name, copy of
specific BM, IP address and BM number. Similarly, prepare NGTJ cards for all co-
located BMs and RBMs.
10. NGTJ card which was earlier working can be inserted back in the same slot of
CACU chassis. Check processes again in NGTJ card.
36 C-DOT MAX-NG
11. All prepared NGTJ cards have to be installed in the specific BM for which these
cards are prepared.
12. After migration, the PCM’s from RSU’s and TAX need to be diverted to the TAG
block installed in the MAX-NG BM itself.
13. Before migration some of the PCM’s from TAX can be diverted to TAG block and
for PCM connectivity of RSUs, PCM cable can be laid from the Exchange’s DDF to
the TAG block of CACU system.
Please note that existing MBM will be working with CM in normal manner till complete
migration of site to minimize downtime.

Chapter 4.
Physical Installation of LAGU System

In following steps mentioned in this chapter actual system downtime will start and
normally it shall vary from 90-120 minutes per BM at the site.
4.1. BM MIGRATION TO LAG
1. Note down the status of all TIC’s, TSI’s working in the BM i.e. which copy of
TIC/TSI is active and which copy is standby (if TIC’s and/or TSI’s are in duplex).
Also take a note of the status of Announcement card and TTC card.
2. This is important because we will bring the LAGU (after conversion of BM it will
become LAGU) up with same set of TIC and TSI copies as active and standby.
3. Shut off the Power of the BM which is to be migrated.
4. Un-screw the BPU and TSU frame.
5. Remove the cables connected at the back plane of TSU and BPU. These cables are
TT cables, TB cables and power cables.
6. Remove filters of BPU and TSU frames from the BUS BAR.
7. Pull out TSU and BPU frames from the BM cabinet.
8. Install new filter box replacing BPU filter boxes at Copy 0 and Copy 1 side of Bus
bar. First yellow cable will be connected to the black bus bar then after installing
filter box, Blue cable will be connected to blue point and red to the red point of filter
box.
9. For physical installation of LAGU chassis, fixture needs to be installed first, which
will be required to hold the LAGU chassis in vertical direction. Now in this space
install the LAGU chassis.
10. Put LAGU chassis in the fixture and screw it properly.
11. Connect TT cables; TT cables at TU side will remain same. At LAGU end TT cables
have to be connected in position 1A, 1B, 2A and 2B connector in the same way as it
was connected in the TSU of MAX BM.
12. Now we will 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 will be fed from ATU’s. Each TSI power cable at LAGU
end will be connected to D-Type connector respectively for copy-0 and copy-1 of TSI
cards which is given at the back plane of LAGU chassis. The other end of the TSI
power cable will be connected at the back plane of ATU motherboard, behind any
38 C-DOT MAX-NG
PHYSICAL INSTALLATION OF LAGU SYSTEM
LCC card slot B, Tab3 and Tab4. These TSI power cables, for copy-0 and copy-1
should be connected to different ATU’s to provide redundancy to the TSI cards.
In this power cable, red is 5 Volts DC and it can vary between 5 to 7 volts. The black
cable is Digital ground and the yellow cable is -12 Volts which can vary from -10 to -
15 Volts.
Before connecting these TSI power cables at LAGU mother Board, power-ON the
ATU’s and verify the voltages at the connector through multimeter. The voltage
must be as per the specified range. In case you are not getting the desired voltage
the connectors should be tried in different LCC slot. After verifying these voltages,
we will connect these TSI power cables at LAGU motherboard in the given
positions.
13. In case of local connectivity through serial cable we will connect client PC / Thin
client through the minicom cable i.e. RS232 cable. This serial cable has to be
connected in this position, for copy-0 of LAG card and for copy-1 this cable will be
connected here.
14. The LAG converts the TDM voice samples to IP based VoIP packets. These IP
packets are then uplinked towards Main LAN switch of MBM site through Ethernet
cable in case of collocated BM. The Ethernet cables will be connected here at eth1
port of LAG -0 and in this position for copy-1 card of LAG. If both the copies of
LAG are inserted, then this Ethernet cable can be connected in any of these ports.
In case of RSU’s it may be possible that the transport medium is E-1. In that case
the existing PCM cable of RSU can be directly connected at tab-1 position of 3A and
4A connectors. The Ethernet cable for uplink is not required in that case. But if the
RSU has STM connectivity then eth cable can be used for unlinking in the same way
as it is done in Co-located BM.
15. Now insert the NGTJ cards in the given slots corresponding to copy-0 and copy-1
and similarly the TSI cards are inserted in their respective slots. The NGTJ card
here are working as a Line Access Gateway. Line Access Gateway converts Time
Division Multiplexed voice sample to Voice Packets. These NGTJ card will be
delivered to site with pre-installed software, root file system, configuration and
system data etc. as per site specific requirement. The pre-configured data is stored
in the storage device of NGTJ card i.e. Micro SD card. .
16. Now after the cards are inserted Switch-ON the power of all the ATU's and
LAGU. The prints in the minicom terminal will appear showing the booting
sequence and then wait for the LAG to come UP.
17. During first time installation of LAGU unit, TIC cards will be brought in service
one by one at each RSU site through CLI only.
18. When the LAG comes up make intra LAG, PSTN & PLMN calls and verify that
proper CDR’s are being made in soft switch.
19. If CDR’s are not proper or calls are not through then either fix the problems or
revert back the LAGU to BM as a fall-back option. In this scenario call the CDOT
helpline for assistance before going for fall-back option.

Chapter 4.
20. When all LAGU’s of the exchange comes up then power off the CM and now create
incoming routes in IPTAX corresponding to these LAGU’s so that incoming calls
are also through.
21. Make inter Lag, intra LAG, PSTN & PLMN calls and verify that proper CDR’s are
being made in soft switch.
22. Now the installer can test all tests mentioned in AT schedule of LAGU,CACU-1and
CACU-2(if applicable to that site) and if all test are working then the site can can be
offered for AT. If some test are failing then fix the tests before offering it to AT
Table 1 below displays the activities to be performed & approximate no. of days required
for migration of one exchange to MAX-NG.
Table 2: Planned activities for MAX to MAX-NG migration (one exchange)
CACU Hardware and Software Installation and making IP Connectivity of
MAX Site to BSNL MPLS N/W 4 DAYS
1 CACU Physical Installation
2 Last Mile connectivity between MAX-NG MLS in CACU and T2/T1
Network/IP Configuration between SDCA and Core switch by Data
3 Network NOC and verification
Network Data Creation in Class-4 SS for connectivity of SDCA to L2/L1
4 TAX and POIs
PSTN & PLMN call testing from SIP Phone and alternate ISUP
5 Connectivity
Retrofit data preparation for MAX to MAX-NG migration for Core and
6 Access Nodes
7 Installation of CACU DDF
8 Termination of alternate media PCM's towards distant exchange.
9 Configuration w.r.t Billing and Provisioning through BSNL CDR system
LAGU's Hardware and software Installation at co-located and RSU Site 5 DAYS
1 Physical Installation of LAGU at collocated BM & RBM
Configuration and DATA creation of Line Access Gateways and of AN-
2 RAXs/PRI in NGTJ card which is configured as Sg/MG/V5/PRI.
3 Termination and configuration of ANRAX's & PRI's to CACU
Post Migration verification Checks of MAX Site 2 DAYS
1 Testing of Different Call scenarios, PCO Calls etc.
2 Verification of processing of CDR & Interworking with CLARITY
40 C-DOT MAX-NG
PHYSICAL INSTALLATION OF LAGU SYSTEM
A/T and commissioning of MAX Site 4 DAYS

1 Successful Completion of Acceptance Testing of SDCA
2 Taking Over Certificate by BSNL
3 Commissioning of the site
Total No. of DAYS for Migration of one MAX exchange 15 DAYS

Chapter - 5
IP Address Configuration IN MLS Card

1. Log in to the MLS card with the serial interface (minicom) if the default IP address is not
set, or login using ssh or telnet if an IP address is already assigned. The user credentials are
username ‘admin’ and the password is blank.
2. Type the following commands on the terminal:
(The commands are shown starting with a ‘#’ prompt)
# configure terminal
# interface vlan1
ip address <ip address to be assigned to the VLAN 1> <netmask> eg:
#ip address 192.168.101.12 255.255.255.0
#exit
3. Exit the terminal using the command
# logout
Note: The above steps are only for assigning the VLAN 1 IP address to the MLS
card and the same will be used as a gateway address in the cards. The procedure to
create Layer-3 routing is not written here. IP address of VLAN1 is 192.168.101.12
and netmask is 255.255.255.0.
For VLAN configuration in MLS card, please refer next Chapter.

C-DOT MAX-NG NETWORK CONNECTIVITY & VLAN CREATION IN MLS CARD
Chapter - 6
C-DOT MAX-NG Network Connectivity &

VLAN CREATION IN MLS CARD
Table of Contents
Chapter 1.
Network
Connectivity...........................................................................................2
1.1Purpose and scope of the Document
1.2Introduction
Chapter 2
Access Site Connectivity ...................................................................................3

2.1 Connecting an access site
2.2 MLS Configuration
MAX-NG Access SW Inst & Config Page 43

Chapter 4.
C-DOT MAX-NG NETWORK

CONNECTIVITY
1.1 PURPOSE AND SCOPE OF THE

DOCUMENT
This document provides an overview of C-DOT MAX-NG access site
connectivity to the core network. It also provides information regarding
LAN and WAN IP provisioning and the procedure to configure MLS card.
1.2 INTRODUCTION
During the migration of MAX system to MAXNG the most important point
is the reachability of the access site to the core network. Each access site is
allocated an IP pool of 64, 128 or 256 IPs depending upon the capacity of
the MAX system. This pool of IP is referred as LAN IP pool. Similarly,
three WAN IP pools of 4 IPs in redundant mode are allocated to each site
for creation of interfaces between access site and MPLS network. These
interfaces are created in redundant mode. For getting accessibility
between MAX-NG access node and core network, information pertaining
to WAN IPs need to be shared with the administrator of the MAX
exchange at least 15 days before migration so that the configuration at the
BSNL’s MPLS PE router can be done. The information consists of the IP
pool for LAN and WAN interfaces, VLAN numbers,interface IPs to be
configured at BSNL PE router end etc. Three VLANs, IPTAX, SSTP and
CDOT-VOIP are created at both BSNL PE router and CDOT MLS card.
Each VLAN is provided an unique VRF-ID. A unique LAN IP pool is
given to each SDCA which is required for the configuration of all the access
gateways which will be installed at access site in each BM/RBMs and in
CACU chassis. This IP pool is required to be publish at PE router for all
the three VRFs.
44 C-DOT MAX-NG
ACCESS SITE CONNECTIVITY
2.1 CONNECTING AN ACCESS SITE

Suppose an access site is allocated, LAN IP pool starting from 10.187.35.0
to 10.187.35.255 of 256 IPs denoted as 10.187.35.0/24 and WAN IP pool
10.189.107.40/30, 10.189.107.44/30 and 10.189.107.48/30. For redundant
interfaces the IP pools are 10.189.107.52/30, 10.189.107.56/30 and
10.189.107.60/30 . These WAN IPs are required to create interfaces
between different VLANs. These VLANs are IPTAX , SSTP and CDOT-
VOIP VLAN with unique VRF ID and required to be created at both the
end.
2.2 MLS CONFIGURATION

Once configuration at PE router is done, configuration at MAX-NG access
node is required. For configuration at MAX-NG node, CACU chassis need
to be physically installed and power-on. Once the physical installation of
CACU is done insert the MLS card in the corresponding slot at CACU
chassis and connect the minicom cable to the thin client. Allocate an IP to
the thin client from the list of LAN IPs allocated to the given site, run
minicom from the thin client as shown in fig-1 and configure the
management IP of MLS as given in the IP list (fig-3). The management IP
of the MLS will act as a gateway IP for the given pool. As there is a
provision of two MLS cards, dual gateways support is available.

Chapter 4.
fig-1
Fig-2
46 C-DOT MAX-NG
Fig-3 (IP configuration in MLS)
Once the IP of the MLS is set, it can be accessed through internet browser
and rest of the configuration can be done through GUI interface of the
MLS.
Fig-4 MLS card GUI interface

Now create WAN interfaces at MLS card, these interfaces should be as per
the WAN IPs allocated and as per the configuration done at PE router

Chapter 4.
end. For creation of the IP interfaces from the left pane select
Configuration IP, a window will open showing the VLAN 1 configuration
(fig-5) which is the native VLAN for the subnet allocated to that site.
Fig -5 VLAN1 configuration of the MLS
Now as per the example mentioned in the section above , at BSNL MPLS
end interfaces are created at two different PE routers for redundancy. At
a cisco routers interfaces created using WAN IP pools 10.189.107.40/30,
10.189.107.44/30 and 10.189.107.48/30. One interface is for IPTAX VLAN
(VLAN ID=2900) and IP given to this interface is 10.189.107.42 at BSNL
end. Similarly SSTP VLAN and CDOT-VOIP VLANS are created with
VLAN ID 2901 and 2902 and IPs 10.189.107.46 and 10.189.107.50
respectively.
For redundant interfaces the IP pools are 10.189.107.52/30,
10.189.107.56/30 and 10.189.107.60/30 used at Huawai router VLAN
created are 2700, 2701 and 2702 for IPTAX, SSTP and CDOT-VOIP
VLANs and the interface IPs are 10.189.107.54, 10.189.107.58 and
10.189.107.62.
Similar interfaces need to be created at MAX-NG node also. An interface
towards cisco PE router need to be created at MLS1 and towards huawai
router the interface will be created from MLS2. With respect to Huawai
router at MLS2 , VLANs 2700, 2701 and 2702 will be created with the
interface IPs 10.189.107.53, 10.189.107.57 and 10.189.107.61 respectively as
shown in fig-6. For creating interfaces click on “add interface” and enter
48 C-DOT MAX-NG
the VLAN id, Ip address and mask length. After the interfaces are added,
create IP routes. Create a default route with network 0.0.0.0 mask length
0, the default gateway for this default route will be the interface IP of
IPTAX VLAN. This indicates that any network IP other than the specified
network will be routed towards IPTAX VLAN as it may be the address
belonging to media IP of IPTAX. Similarly a network 10.187.0.0/24, is a
pool allocated to MAX-NG and will be routed towards CDOT-VOIP
VLAN and the gateway IP will be 10.189.107.60 which is an IP address
forCDOT-VOIP interface created at Huawai PE router, refer fig-7. Select
mode as “router” from the drop down and click to “save” button once
interfaces and routes are added.
Fig-6 Adding interfaces

Chapter 4.
Fig-7 Add IP routes
From the left pane select Spanning tree  Bridge setting and do the STP
bridge configuration as shown in fig-8
Fig-8 STP bridge configuration
Now from the left pane click on VLANs Configuration a window will
open showing Global VLAN configuration. Here all the ports of MLS are
visible with their mode and Port VLAN as shown in fig-9
50 C-DOT MAX-NG
Fig -9 Global VLAN configuration

The mode of the port can be Access or Trunk and can be selected from the
drop down and Port VLAN can be defined according to the configuration.
Default value of Port VLAN is
1.
Fig-10 Allowing Access VLAN

Chapter 4.
It is also to be noted that against the field “allowed access VLAN” all the
VLANs number to be given see fig-10.
In the face plate of MLS card two optical ports 21 and 22 are available
which are used for uplink connectivity. An SFP of 1310 or 1550 nm
wavelength can be used in these ports depending the SFP type available at
BSNL end. An optical patch cord is used for the connectivity of MLS and
PE router. The “Mode” of the port 21 or 22 which is being used for uplink
is to be set as Trunk port as shown in fig-11.
Fig-11
On selecting the required port as Trunk all the VLANs 1-4095 will be
allowed and Egress port setting wiil be by default set as Untag Port VLAN
now save the setting from the button given below. After all the
configuration is done, in the left pane select Configuration  save
startupconfig to save the configuration as shown in fig-12.
52 C-DOT MAX-NG
Fig-12 Saving the configuration
After the configuration is done, one should be able to ping the core network
from MLS and behind MLS i.e. from LAGU, thin client etc.

Chapter 4.
CONFIGURATION REQUIRED
FOR DUAL UPLINK
REDUNDANCY
For Dual Uplink connectivity at migration site, following are the

requirements:
Both Uplinks must be physically UP and configured.
Configuration Required at PE Router
 BFD ECO configured should be with parameters
bfd min-transmit-interval 200

bfd min-receive-interval 200
bfd min-echo-receive-interval 200
bfd detect-multiplier 3
 Static routing with bfd for all VPN/VRF interfaces.
 Latest Patch must be installed in both LAGU & CACU.
At C-DOT MLS card end,

 RSTP should be configured at both MLS cards with following
parameters and also shown in below screenshot
Hello Time 1
Forward Delay 4
Max Age 6
Maximum Hop Count 6
Transmit Hold Count 2
54 C-DOT MAX-NG
 Please configure BFD ECO for all VRF/VLAN interface and static
routing with BFD for both Uplinks.

Chapter 4.
 Additional setting required for NTP and Trap configuration is as follows:
For this , Go to Configuration -> System -> NTP Mode should be Enabled
and enter SBC FVIP of PR Site in Server 1 option and in Server 2 option,
enter SBC FVIP (GR Site) IP address. In below screenshot, Chandigarh
Core Site is taken as PR site and Gurugram is taken as GR site.
PR SITE
NTP GR
SERVER SITE
NTP
SERV
ER
56 C-DOT MAX-NG
Trap Configuration Settings in MLS card
For trap configuration settings, go to Configuration -> System -> Security

-> SNMP -> Trap. Mode should be Enabled. Add Entries of NGEMS
Server of both PR and GR sites. In below screenshot , NGEMS server IP
are 10.187.1.39 and 10.187.1.40 i.e. of Chandigarh Primary Site.
10.187.0.167 and 10.187.0.168 are NGEMS server IP of Gurugram Site
in GR configuration with Chandigarh site. Here , Chandigarh is PR site
and Gurugram is GR site.

Chapter 4.
58 C-DOT MAX-NG
C-DOT MAX-NG
MAX-NG ACCESS SOFTWARE

INSTALLATION AND
CONFIGURATION

Chapter 4.
MAX-NG ACCESS SOFTWARE INSTALLATION AND

CONFIGURATION
Following are the broad steps in brief for Access nodes (CACU and LAGU) Software
Installations and configuration at the C-DOT BSNL exchanges/sites.
a) The “IP ADDRESS DETAILS” sheet for the site is available with the CACU and LAGU wise IP
addresses allocated (as available in the MAX-NG Rollout Project Management web portal). Refer
Appendix-A.
b) Prepare the Thin Client machine and configure the minicom settings. Refer Appendix-I (steps 1 to
6).
c) If the MAC address for the MLS cards (MLS1 & MLS2) are mentioned in the “IP ADDRESS
DETAILS”, against the parameter “MLS Card1/2 Management IP (Gateway-1/2)” only then these need
to be allocated to the CACU MLS cards during IP configuration using minicom. Paste the stickers
for the MAC address allocated on the MLS cards face plate. Refer Appendix-B. This step is
required only in case a pool of 24 MAC addresses is not allocated to each of MLS card.
d) Do the MLS cards IP, VLAN and WAN-IP configurations as mentioned in detail in a separate
document for MLS card Configuration. Refer Appendix-D for broad steps.
e) Configure the IP of the Thin Client machine and setting up of TFTP server and Access software
loading as mentioned in the Appendix-I (steps 7 onwards).
f) Load the revised MLS software file CEServices3_65-MLSSD1_SW002.dat over the MLS through
GUI. It takes around 5 minutes. Refer Appendix-C.
g) The NGTJ cards (both LAGU and CACU) have to be loaded with the provided VER53 uboot and
dtb files. It takes around 5 minutes to load these files over the NGTJ cards. Refer the Appendix-E.
h) Ensure that the MAC addresses for the cards are allocated and the stickers for the same are
present/ pasted over the card face plates.
i) Allocate the CARD-IP addresses to the cards for all the CACU cards using the minicom cable.
Refer to the CACU Installation procedure steps in Appendix-G (step 7).
j) Allocate the CARD-IP addresses to all the cards for all the LAGU NGTJ cards using the minicom
cable. Refer to the CACU Installation procedure steps in Appendix-H (step 3).
k) Test the Uplink connectivity for the CACU and LAGU cards connected and IP addresses are
configured.
After that, test the reachability of the LAGU and CACU cards from the core network.
60 C-DOT MAX-NG
l) Load the LAGU and the CACU software release/patch tarball over the thin client machines. Refer
the Appendix-F.
m) Connect the LAGU system with either the CACU MLS card over the MLS card ethernet port or
CACU EBM card over E1.
n) Do the automated Installation and configurations for the CACU release software over the CACU
cards (SLM, NGTJ and EBM) which have already been configured the IPs and are accessible
from the thin client machine (having the CACU deliverables) connected with MLS-1 card. Refer
Appendix-G.
o) Similarly, do the automated LAGU release software installation and configurations from the thin
client machine with the loaded LAGU release tarball. Refer Appendix-H.
p) Configure the parameters on the BSNL MPLS routers to enable CACU Link Redundancy. Refer
Appendix J.

Chapter 4.
Appendix-A
(An example of the IP ADDRESS DETAILS SHEET from Web Portal)
IP ADDRESS DETAILS
SDCA Nimbahera
Starting IP Address 10.188.168.0
Total Used
64 Using IP Range 10.188.168.0 - 10.188.168.63 Network IP 10.188.168.0
IP
CIDR 10.188.168.4
Subnet Mask 255.255.255.192 /26 Gateway(s) Broadcast 10.188.168.63
Prefix 10.188.168.7
WAN IP Details IP TAX WAN SSTP WAN CDOT WAN SPARE WAN
Uplink 1 10.189.73.64/30 10:189:73:68/30 10:189:73:72/30 10:189:73:76/30
Uplink 2 10:189:73:80/30 10:189:73:84/30 10:189:73:88/30 10:189:73:92/30
Total CACU System (with EBM-16) 1
CACU#1 10.188.168.2 - 10.188.168.30

MLS Card1 Network-Self IP 10.188.168.2
MLS Card1 Network-Other IP 10.188.168.3
MLS Card1 Management IP(Gateway-1) 10.188.168.4 (MAC - 00-1D-36-01-CF-51)
MLS Card2 Network-Self IP 10.188.168.5
62 C-DOT MAX-NG
MLS Card2 Network-Other IP 10.188.168.6

MLS Card2 Management IP(Gateway-2) 10.188.168.7 (MAC - 00-1D-36-01-CF-69)
SLM Floating IP 10.188.168.8
SLM Card1 IP 10.188.168.9
SLM Card2 IP 10.188.168.10
EBM Card1 IP 10.188.168.11
EBM Card2 IP 10.188.168.12
NGTJ Card1
Card IP 10.188.168.13
DSP IP 10.188.168.14
TMG IP 10.188.168.15
SGL2 IP 10.188.168.16
V5 IP 10.188.168.17
PRI IP 10.188.168.18
NGTJ Card2
Card IP 10.188.168.19
DSP IP 10.188.168.20
TMG IP 10.188.168.21

Chapter 4.
SGL2 IP 10.188.168.22
V5 IP 10.188.168.23
PRI IP 10.188.168.24
Terminal (Thin Client) IP 10.188.168.25
Free IP(s) 10.188.168.26 - 10.188.168.30
Total CACU System (with EBM-32) 0

Total LAGU System 4
LAGU#1 10.188.168.31 - 10.188.168.38

Self eth0 IP 10.188.168.31
Self eth1 IP 10.188.168.32
Mate eth0 IP 10.188.168.33
Mate eth1 IP 10.188.168.34
Floating IP 10.188.168.35
Active DSP IP 10.188.168.36
Standby DSP IP 10.188.168.37
Free IP(s) 10.188.168.38
LAGU#2 10.188.168.39 - 10.188.168.46
Self eth0 IP 10.188.168.39
64 C-DOT MAX-NG
Self eth1 IP 10.188.168.40

Mate eth0 IP 10.188.168.41
Mate eth1 IP 10.188.168.42
Free IP(s) 10.188.168.46
LAGU#3 10.188.168.47 - 10.188.168.54
Self eth0 IP 10.188.168.47
Self eth1 IP 10.188.168.48
Mate eth0 IP 10.188.168.49
Mate eth1 IP 10.188.168.50
Free IP(s) 10.188.168.54
LAGU#4 10.188.168.55 - 10.188.168.62
Self eth0 IP 10.188.168.55

Chapter 4.
Self eth1 IP 10.188.168.56

Mate eth0 IP 10.188.168.57
Mate eth1 IP 10.188.168.58
Free IP(s) 10.188.168.62
66 C-DOT MAX-NG
Appendix-B
(MLS Card MAC and IP Address Entry)
MAC ADDRESS ALLOCATIONS IN MLS CARD (with 3.65 static layer-3 version)
The MLS card requires one MAC address for the system itself (CPU) and one for each of the front
ports. The front port SMACs are needed for PAUSE frame generation. So, in total 24 MAC
addresses get allocated to each MLS card. We have to reserve a pool of 24 MAC addresses for
each MLS card but need to enter only the first MAC address of the pool as per the below
mentioned steps. The rest of 23 MAC addresses get internally allocated upon entry of the first
MAC for CPU.
NOTE: This procedure is required to be executed only if pool of 24 MAC addresses have not been
already allocated to each MLS card (with steps as mentioned as below to enter only the first MAC
of the 24 MAC pool).
Steps for MAC address allocation:
1. Connect minicom
2. Login to the ICLI (login user: admin password : <enter>)

# platform debug allow
(Assuming MAC Address pool of MLS card is, say 00-01-c1-00-00-01 to 00-01-c1-00-00-18 in hex)
# debug board mac 00-01-c1-00-00-01
# platform debug deny
IP ADDRESS ALLOCATIONS IN MLS CARD:

(Refer to the detailed MLS configuration document with snapshots of the GUI based configurations)
The Management IP address of each MLS card will be used as the gateway IP address for the
CACU cards. The configuration may be done through the CLI or GUI. The first steps is for
assigning IP address to the default VLAN 1 (if not assigned) and then the GUI using a browser
can be used to configure the MLS cards.
Note: The examples of the commands are shown starting with a '#' prompt.
LAN AND WAN IP POOL:

Suppose an access site is allocated with:
a) LAN IP pool starting from 10.187.35.0 to 10.187.35.255 of 256 IPs denoted as 10.187.35.0/24
with the two Gateway IPs as 10.187.35.4 & 10.187.35.7

Chapter 4.
b) The VLAN1 will be created at both MLS cards which is the native VLAN for the LAN IP pool
subnet allocated to that site.
For MLS-1 card VLAN1, configure the Gateway-1 IP as 10.187.35.4 with mask length as 24.
The following Steps to be performed using a serial interface/minicom, unless a default VLAN1 IP
address is already assigned.
1. Ensure that the thin-client has been configured as per the details given in the Appendix-I.
Connect Minicom Cable from C-DOT MLS-1 card to Thin Client/Client PC/ Laptop.
2. Launch Minicom Application in Thin Client/PC/Laptop as a root user.
# minicom
3. Assign an IP address to the VLAN 1 (default) of the C-DOT MLS-1 card as :
#configure terminal
#interface vlan 1
(ip address <ip address of VLAN 1> <netmask>)
#ip address 10.187.35.4 255.255.255.0
#exit
# copy running-config startup–config
# show ip interface brief
(This command will show the ip address which has been configured).
Example:
Interface Address Method Status
--------------------------------------------------
Vlan 1 10.187.35.4 Manual UP
6 C-DOT MAX-NG
Appendix-C
(MLS Card CEServices3_65-MLSSD1_SW002.dat loading)
Firmware update through GUI of MLS card:
1) Login to MLS through ‘admin’ login from the thin client machine with the MLS Application
software CEServices3_65-MLSSD1_SW002.dat loaded.
2) Ensure that the network configuration data is saved (MaintenanceConfiguration  Save startup-
config)
3) From Maintenance-> Software -> Upload page, Firmware of the card can be updated.
Browse the PC location for the firmware in CEServices3_65-MLSSD1_SW002.dat format. Click
‘upload’ button. After the software image is uploaded, a page announces that the firmware
update is initiated. After about a minute, the firmware is updated and the switch restarts.
Warning: While the firmware is being updated, Web access appears to be defunct. The front LED
flashes Green/Off with a frequency of 10Hz while the firmware update is in progress. Do not
restart or power off the device at this time or the switch may fail to function afterwards.

Chapter 4.
Appendix-D
(MLS Card WAN IP CONFIGURATIONs)
NOTE: For exact details, please refer the MLS IP configuration document.
WAN IP POOL:
a) For uplink through MLS-1, WAN IP pools are 10.189.107.40/30, 10.189.107.44/30 and
10.189.107.48/30.
b) For redundant uplink through MLS-2 interface, the WAN IP pools are 10.189.107.52/30,
10.189.107.56/30 and 10.189.107.60/30.
These WAN IPs are required to create interfaces between different VLANs. These VLANs are
IPTAX, SSTP and CDOT-VOIP VLAN with unique VRF ID and required to be created at both
the end (MLS and MPLS Router)
Once the IP of the MLS is set, it can be accessed through internet browser and rest of the configuration
can be done through GUI interface of the MLS, as follows:
1) Create interfaces for other VLANs (IPTAX, SSTP and CDOT-VOIP) for uplink from MLS-1 and
MLS-2 cards.
2) After the interfaces are added, create IP routes. Create a default route with network 0.0.0.0 with
mask length 0, the default gateway for this default route will be the interface IP of IPTAX VLAN.
This indicates that any network IP other than the specified network will be routed towards IPTAX
VLAN as it may be the address belonging to media IP of IPTAX.
3) In the face plate of MLS card two optical ports 21 and 22 are available which are used for uplink
connectivity. An SFP of 1310 or 1550 nm wavelength can be used in these ports depending upon the
SFP type available at BSNL end. An optical patch cord is used for the connectivity of MLS and PE
router. The “Mode” of the port 21 or 22 which is being used for uplink is to be set as Trunk port.
4) On selecting the required port as Trunk all the VLANs 1-4095 will be allowed and Egress port
setting will be by default set as Untag Port VLAN.
5) From the left pane select Spanning tree  Bridge setting and do the STP bridge configuration with
Protocol as RSTP.
6) After all the configurations is done, in the left pane select Configuration  Save startup config to
save the configuration.
7) After the configuration is done, one should be able to ping the core network from MLS and behind
MLS i.e. from LAGU, thin client etc.
8 C-DOT MAX-NG

Chapter 4.
Appendix-E
(UBOOT and DTB files Loading over NGTJ Card)
This new uboot file (NGTJ.u-boot.bin.VER53) is being loaded on the LAGU NGTJ cards because till
the latest uboot releases, EEB modules on the NGTJ cards came up as soon as the card booted, thus
potentially caused network looping when the LAGU was connected to the EBM card of CACU using the
PCM/E1 links. The new release of uboot (version 53) disables the EEB module of the NGTJ card on
boot time and is enabled only by the LAG application.
The new DTB file (NGTJ.dtb.VER53) takes care of the issue of an unhandled interrupt crashing kernel as
soon as NAND flash was accessed through net file.
S/no Deliverable-Name Size(in bytes) Checksum

1. NGTJ.u-boot.bin.VER53 (UBOOT) 369880 4027088522
2. NGTJ.uImage.VER52 (LINUX 3806124 2389537443
IMAGE)
3. NGTJ.dtb.VER53 (DTB) 10067 3601580650
4. NGTJ.rfs.s.VER52 (RAM-RFS) 19078430 933627270
Note: Verify the current Firmware loaded in NGTJ card as :

# ‘fpga’ command should give output as:
Control FPGA version is 23 on (NGTJ)
Time switch FPGA version is 21 on (NGTJ)
# ‘cat /etc/issue’ command gives output as: MAXNG NGTK Console Rel 1.52
 For NGTJ card ver AE3 for LAGU, revised UBOOT file VER53 is required to be loaded.
 For NGTJ card ver SE3 or AE3 being used for CACU, revised DTB file VER53 is required to be
loaded.
The Uboot and DTB installation and setup procedure for the LAGU is as follows:
1) Connect the LAGU chassis with the power supply and turn on the power.
2) Connect the minicom cable to one of the RS-232 ports of the LAGU chassis.
10 C-DOT MAX-NG
3) Make sure that the application tftpserver is installed and running on the PC/thinclient which is to be
used for further operations. Note that the Thin Client is loaded and configured for TFTP server as
mentioned in the Appendix-I (step-I)
4) Connect an ethernet cable from the ThinClient/PC to the LAGU chassis at any of the ethernet ports.
5) Ensure that the step-I for the Thin Client is done already for the TFTP server configuration and
copying the NGTJ.u-boot.bin.VER53 and NGTJ.dtb.VER53 driver files at the path
/var/lib/tftpboot/
6) Use the ‘cksum’ command at the path /var/lib/tftpboot/ of the Thin Client to ensure the above
mentioned checksums for uboot and dtb files.
# cksum /var/lib/tftpboot/NGTJ*VER53
7) Else, Copy the file named NGTJ.u-boot.bin.VER53 and NGTJ.dtb.VER53 to the path /tftpboot on
the PC configured for TFTP server.
8) On the ThinClient/PC, open the minicom application using the command 'minicom -s' to access the
serial port interface and set baud rate to 115200, no flow control as serial port parameters. After
applying the above settings, save then as default and exit to go to the minicom application.
9) Now, jack-in the NGTJ card in that slot to which minicom has been connected in step-2 and press
the reset button.
10) In the minicom terminal window, see if the print ''Autoboot in 6 seconds. Hit 'a' to stop from
Autoboot'' appears, then press the 'a' key to stop the booting so that NGTJ card comes in the uboot
prompt. The uboot prompt as => should appear. If the uboot prompt could not be stopped, press the
reset button on the NGTJ card and try again.
11) In the uboot prompt, do the following steps (steps a to k) :
a) Ensure the IP address of the PC mentioned above is set as the serverip in u-boot command
prompt. To set it use the command:
=> setenv serverip <serverip/IP address of the tftp server ThinClient/PC>.
e.g. => setenv serverip 10.187.1.5
b) Set the IP address of the NGTJ for loading uboot as an IP address that is reachable from the

Chapter 4.
ThinClient/PC, using the command:

=> setenv ipaddr <NGTJ card IP>
e.g. => setenv ipaddr 10.187.1.6
c) Set the netmask of the NGTJ card in the uboot as 255.255.255.0, using the command:
=> setenv netmask 255.255.255.0
e.g. => setenv netmask 255.255.255.0
d) Set the gateway IP address of the NGTJ cards as that of the PC itself. The command is:
=>setenv gatewayip <IP address of the PC>
e.g. => setenv gatewayip 10.187.1.5
e) Set the ubootfile parameter as NGTJ.u-boot.bin.VER53 and dtbfile file as

NGTJ.dtb.VER53
The command used is:
=> setenv ubootfile NGTJ.u-boot.bin.VER53
=>setenv dtbfile NGTJ.dtb.VER53
f) Now save the above entries using the command:

=> saveenv
g) ping the IP address of the tftp server using the command:

=>ping <IP address of the tftpserver/ThinClient>
An output as the following should come:
Using UEC0 device
host 10.187.1.5 is alive
Run the command to fuse uboot using:

h) =>run FUSE_UBOOT
On execution following messages-extract be printed on screen :
Load address : 0x7000000

Loading: ################################### 972.7 KiB/s
done
12 C-DOT MAX-NG
i) Check for existence of following three parameters :

1. Uboot=>pri bootargs
If it prints like
“bootargs=root=/dev/ram rw console=ttyS0,115200
ramdisk_size=300000”
Or
“bootargs=root=/dev/ram rw console=ttyS0,115200
ramdisk_size=400000”
then continue to check the next point, otherwise set it with following commands:
Uboot=> setenv bootargs 'root=/dev/ram rw console=ttyS0,115200

ramdisk_size=400000'
Uboot=>saveenv
2. Uboot=>pri bootcmd
If it prints like
“bootcmd=run UEC0_ping;run UEC1_ping;bootm $kerneladdr

$rfsaddr $dtbaddr”
then continue to the next check, otherwise set it with following commands :
Uboot=> setenv bootcmd ‘bootm $kerneladdr $rfsaddr $dtbaddr’

Uboot=>saveenv
3. Uboot=>pri load_dtb
If it prints like
“load_dtb=tftp $loadaddr $dtbfile;cp.b $loadaddr $dtbaddr

$filesize”

Chapter 4.
then continue to next check otherwise set it with following commands :
Uboot=> setenv load_dtb ‘tftp $loadaddr $dtbfile;cp.b $loadaddr $dtbaddr

$filesize’
Uboot=>saveenv
Run the commands mentioned below to fuse DTB using:
j) => erase $dtbaddr f8cfffff
On execution following messages-extract will be printed on screen :
.... done
Erased 4 sectors
k) => run load_dtb
On execution following messages-extract will be printed on screen :
Load address : 0x7000000

Loading: # 818.4 KiB/s
done
Bytes transferred = 10067 (2753 hex)
l) Reboot the card with the loaded uboot and dtb files.
=> boot
m) Login into the card using “user/password = root/root” and give

“reboot” command at $prompt.
A message-string “U-BOOT 5.3” will be printed on minicom-screen once the card will reset.
This verifies the updated U-boot version .
14 C-DOT MAX-NG
Appendix-F
(LAGU and CACU Release Deliverables)
1) LAGU APPLICATION DELIVERABLE DETAILS:
LAGU Release CLAGL2_4_1.2_1 and Patch files:

1) clagl2_4_1.2_1-lagagent.tar – 10270720 bytes
2) clagl2_4_1.2_1-linuxagent.tar – 3532800 bytes
3) lagconf_1.2.tar – 8488960 bytes
4) lagrel_1.2.tar – 46202880 bytes
5) PATCH1-Over-CLAGL2_4_1.2_1-cli_bulk_commands-10280960 bytes
6) PATCH9-Over-CLAGL2_4_1.2_1-EBM_loop_RBT_Call_Clear_log.tar- 5785600 bytes
LAGU Backend Release/Patch files:
1) PATCH13-Over-SWINSTL1_1_2.16_1-SWBELAG-COMB.tar – 276480 bytes
2) bkrs_lagbackend.tar – 215040 bytes
3) PATCH5-Over-SWINSTL1_1_2.16_1-SCHDBACKUP_RESTORE.tar – 10240 bytes
2) CACU APPLICATION DELIVERABLE DETAILS:
1) XEYEPL1_1_2.12_1.zip – 64135367 bytes

2) TEMP-OVER-XEYEPL2.12.zip – 5628172 bytes
3) NGTJ_DRIVERS-REL4.zip – 330804 bytes
4) PATCH10-Over-SLML1_1_1.5_1-install_cacu_cards-NGTJ-INSTALL.sh – 115285 bytes
Details of product wise Release and Patches contained in the above zip files:
a) XEYEPL1_1_2.12_1.zip :
1) XEYEPL1_1_2.12_1-Deliverables.txt (1019 bytes)

2) V5AG Patch:PATCH4-Over-AGL1_1_3.4_1-RingBackSwitching-PRBT.tar (113448960
bytes)
3) NGTJ card EMS Agent tar file: gwyagentl3_1_1.5_1-NGTJCardAgent.tar (8990720
bytes)
4) PRIAG EMS Agent tar file: PATCH1-Over-GWYAGENTL3_1_1.5_1-
PriAgentNGTJ.tar (686080 bytes)

Chapter 4.
5) TMG EMS Agent tar file: PATCH2-Over-GWYAGENTL3_1_1.5_1-

TmgAgentNGTJ.tar (460800 bytes)
6) V5AG EMS Agent tar file: PATCH4-Over-GWYAGENTL3_1_1.5_1-
V5AgentNGTJ.tar (1433600 bytes)
7) NGTJ I2C Agent Patch :PATCH7-Over-NGTJCDL1_1_1.6_1-I2CAGNT-READ-
UPDATE.tar (61440 bytes)
8) NGTJ Common deliverables patch: PATCH10-Over-NGTJCDL1_1_1.6_1-
callKillingOnPRGR-MASTER.tar (3061760 bytes)
9) PRIAG Release: PATCH2-Over-PRIAGL1_1_2.5_1-
ONE_WAY_VOICE_ACT_CALL_KILL.tar (50339840 bytes)
10) CACU Chassis NGEMS Agent: slml1_1_1.5_1-ChassisAgent.tar (9144320 bytes)
11) SLM card patch deliverable: PATCH12-Over-SLML1_1_1.5_1-FALSE-JACK-IN-
ALRM-GR-SIP-10S-SHM.tar (1597440 bytes)
b) TEMP-OVER-XEYEPL2.12.zip :
1) TEMP-OVER-XEYEPL2.12-Deliverables.txt (496 bytes)

2) CDOT Trunk Media Release TAR for CACU Solution: PATCH1-Over-CDTMGL1_1_1.9_1-NGTJ-
CACU.tar (5396480 bytes)
3) CACU EBM EMS Agent : ebml1_1_1.7_1-EBMCardAgent.tar ( 8970240 bytes)
4) EBM Release TAR : eebrel_1.7.tar (81920 bytes)
5) Patch Deliverables CACU EBML1_1_1.7_1: PATCH1-Over-EBML1_1_1.7_1-DISPL-INVALID-
PORT-NUM.tar (20480 bytes)
6) Patch Deliverables SGL1_3_1.9_1: PATCH1-Over-SGL1_3_1.9_1-INIT-CACU-ONLY.tar (3225600
bytes)
c) NGTJ_DRIVERS-REL4.zip :
1) NGTJ_DRIVERS-REL4-Deliverables.txt (245 bytes)

2) CACU Drivers TAR : NGTJ_DRIVER_CACU-REL4.tar (737280 bytes)
3) Installation Script : install_ngtj_drivers.sh (1262 bytes)
3) MISC ACCESS SOFTWARE
a) MLS Card Application :

1) CEServices3_65-MLSSD1_SW002.dat (5,466,769 bytes)
b) NGTJ Card Drivers :
1) NGTJ.u-boot.bin.VER53 (369880 bytes)

2) NGTJ.dtb.VER53 (10067 bytes)
16 C-DOT MAX-NG
c) TFTP Server application over thin client
1) tftpd-hpa_5.0-11ubuntu2.1_armel.deb (44,938 bytes)

2) tftp (384 bytes)

Chapter 4.
Appendix-G
(Automated Installations for CACU Application Release/Patch)
PREREQUISITES:
1) The application release CEServices3_65-MLSSD1_SW002.dat should be loaded on both the MLS
cards of the CACU.
2) The dtb file for the NGTJ card should be loaded on the SE3 or AE3 NGTJ card to be used in the
CACU.
3) The CACU deliverables described in the Appendix-F, part 2 should be copied to a directory on the
thin-client/PC from where application release installation has to be done on the CACU cards.
4) A detailed list of IP addresses to be allocated to the cards of CAU should be present as described in
the Appendix - A.
5) The thin-client should have been configured and readied according to the Appendix-I.
6) Connect an RS-232/minicom cable to the thin-client at one end and with the minicom serial port
behind each card slot one by one to assign IP addresses to the cards.
7) Log-in to the cards via the minicom using the username “root” and password “root”. The process to
assign IP addresses to the every type of CACU cards is described as follows:
 For MLS card IP settings; set the VLAN1 (native default VLAN) IP address. See
Appendix-B for reference.
 For SLM cards IP settings (eth1 port is used)

 #mount -t jffs2 /dev/mtdblock5 /jffs2
 #cd /jffs2/conf
 # > net
 #vi net
 Press ‘i’ to enter the INSERT mode of vi editor and then add/edit the following 3
lines of net file.
ifconfig eth1 down
ifconfig eth1 <SLM-CARD-IP-ADDR> netmask <netmask> up
route add default gw <Gateway-IP-Addr>
 After editing the file successfully, save and exit the net file by first pressing the
‘ESC’ key and then “:wq” and then press ENTER key
 give execute permission to net file using command : # chmod +x net
 execute net file to set the card ip address: # ./net
 For CACU NGTJ card (SE3 version) IP settings; eth0 port is used
Note: In case the CACU NGTJ card is not accessible from minicom, login to the NGTJ card
from the Thin /Client using “ssh root@<NGTJcard-IP-Address>” (with the default IP
address allocated to the card by the manufacturer). Before this step, the Thin Client should
also be set with the default IP subnet of the NGTJ card, so that the NGTJ card can be
accessed from the Thin Client machine. And after changing the IP of the NGTJ SE3 card
for the site IP, the Thin Client IP should be reverted to the site wise IP for the thin client.
 #mount /dev/mtdblock0 /jffs2
18 C-DOT MAX-NG
 #cd /jffs2/conf
 # > net
 #vi net
 Press ‘i’ to enter the INSERT mode of vi editor and then add/edit the following 3
lines of net file.
ifconfig eth1 down
ifconfig eth0 <NGTJ-CARD-IP-ADDR> netmask <netmask> up
 Save the net file by pressing Esc key and then typing :wq and then press Enter/Return
key.
 For EBM card IP settings (eth0 port is used )

 #cd /jffs2/conf
 Open ‘net’ file and edit with following 4 lines using ‘vi’, with the i and save the net
file (using a sequence of Esc, :wq and Enter commad on vi editor)
ifconfig eth0 <EBM-CARD-IP-ADDR> netmask <netmask> up
cd /cdot/bin
./bcm_rst
After this, press “Esc” key then type “:wq!” and then press “Enter” key
Once the above is ensured, proceed with the actual installation of the application software release as
given below.
SOFTWARE INSTALLATION PROCEDURE:
1) Switch to the root user on the thin-client/PC (to be used for further installation process), if not
already using the command ‘su - root’.
2) Now connect the thin-client with any free Ethernet port (RJ-45) available on the MLS-1 card at the
7th slot of the CACU chassis.
3) Assign an IP address to the thin-client (or PC) using the IP address available at the site as detailed in
the Appendix I (steps 7 onwards).
4) On the thin-client/PC for installation, go to the path where CACU application release deliverables
have been copied using the command:

Chapter 4.
#cd /home/Ubuntu/CACU-SOURCE
5) Now, give the script named PATCH10-Over-SLML1_1_1.5_1-install_cacu_cards-NGTJ-

INSTALL.sh executable permission using the command
#chmod +x *sh
6) Execute the script using the command:
#./PATCH10-Over-SLML1_1_1.5_1-install_cacu_cards-NGTJ-INSTALL.sh
7) When the script is run for the first time on a particular thin-client/PC, the script will initiate the
unzipping of the release/patch files locally to arrange them in a structure as required during the
installation on the cards.
8) Once the unzipping is complete, the script asks for the Type of CACU system. For MAX-NG, it
must be entered as 1. Output is similar to
Enter Configuration Type, 1 for MAX-NG or 2 for The Red Network
The Configuration Selected for installation is 1
Enter Y/y to continue with above entered config or no to enter new one
9) After this, the script will ask for input for various parameters such as the IP addresses for the CACU,
IP address of the NGEMS, NGSM, NTP server etc. The sample output is:
Configuration file is not present, all the values need to be filled
All the values need to be entered:
Enter the Configuration Type for CACU
Already Entered Configuration is 1. Want to continue with it?
Enter y/Y to Continue with Above entered configuration or n/N to enter new one
y
Continuing with configuration 1
The Updated Configuration value is 1
Enter the Start IP for CACU
Enter Start IP For CACU Range
10.187.212.2
The updated Start-IP is 10.187.212.2
Enter the End IP for CACU
Enter End IP For CACU Range
10.187.212.25
Final output 10.187.212.25
End IP is as expected
The updated End-IP is 10.187.212.25
Enter the GateWay IP for CACU
Enter Gateway IP For CACU
20 C-DOT MAX-NG
10.187.212.4
The updated Gateway-IP is 10.187.212.4
Enter the BroadCast IP for CACU
Enter BroadCast IP For CACU
10.187.212.63
The updated Broadcast-IP is 10.187.212.63
Enter the NetMask for CACU
Enter NetMask for CACU
255.255.255.192
The updated Netmask value is 255.255.255.192
Enter the IP Offset for Usable IP
Enter Offset for Starting IP range, Default will be 0
0
The Updated Number of IP start offset is 0
Enter the System Name to be used in NGEMS Manager
Enter System Name For Agent Configuration
CACU_NUH
The Updated System Name is CACU_NUH
Enter the Region
Enter Region Code
North_HA_1267
The Updated Region Code is North_HA_1267
Enter the Number of NGEMS Manager
Enter Number of EMS Managers, Default will be 1
4
The Updated Number of EMS Managers is 4
Enter the IP Addresses for NGEMS Manager 1 to Number of Managers [
Entered value is 4]
The Number of NGEMS Manager is 4
The NGEMS Manager IPs will be Entered Sequentially
First 2 IP Addresses for PR and the next 2 IP Addresses for GR
NGEMS Managers
Enter NGEMS Manager IP Address 1 [ PR 1 ]
10.187.0.39
Entered value NGEMS Manager 1 [ PR 1 ] IP Address is 10.187.0.39
10.187.0.40
Entered value for NGEMS Manager 2[PR 2 ]IP Address is 10.187.0.40

Chapter 4.
Enter NGEMS Manager IP Address 3 [ GR 1 ]

10.187.1.167
Entered value for NGEMS Manager 3[GR 1]IP Address is 10.187.1.167
10.187.1.168
The updated NGEMS Manager IP(s) is/are
PR 1 NGEMS Manager IP Address: 10.187.0.39
GR 1 NGEMS Manager IP Address: 10.187.1.167
Enter the Number of NGSM
Enter Number of NGSM, Default will be 4
4
The Updated Number of NGSM is 4
Enter the IP Addresses for NGSM Manager 1 to Number of NGSM
Managers [ Entered value is 4]
The Number of NGSM is 4
The NGSM IP Addresses will be Entered Sequentially
First 2 IP Addresses for PR and the next 2 IP Addresses for GR
NGSMs
Enter NGSM IP Address 1 [ PR 1 ]
10.187.0.22
Entered value for NGSM 1 [ PR 1 ] IP Address is 10.187.0.22
10.187.0.23
Enter NGSM IP Address 3 [ GR 1 ]
10.187.1.150
Entered value for NGSM 3 [ GR 1 ] IP Address is 10.187.1.150
10.187.1.151
The updated NGSM IP(s) is/are
PR 1 NGSM IP Address: 10.187.0.22
GR 1 NGSM IP Address: 10.187.1.150
Enter the IP of the NTP Server
Enter NTP Server IP
22 C-DOT MAX-NG
10.187.4.12
The updated NTP server IP is 10.187.4.12
Enter the Periodicity to sync with NTP server (in seconds)
Enter Periodicity for syncing with NTP Server, Default will be 600
(Value will be in seconds)
900
The Updated NTP periodicity (in seconds) is 900
Note: The above IP address, ports, system name etc are just an indicative example and the actual entries
must be entered according to the field data.
10) Now the user is displayed the values that have been entered so far and is asked whether these values
have to be changed (eg in case of some discrepancy)
The conf file created is as follows:

Note 1: The values marked as <blank> are just for display, they
will not be sent to card.
Note 2: In case of Configuration 2 Entries corresponding to NGSM

will not be used, even if present.
Configuration File is present with values:

[1] Configuration Type for CACU: 1
[2] Start IP of the CACU range: 10.187.212.2
[3] End IP of the CACU range: 10.187.212.25
[4] Gateway IP for CACU: 10.187.212.4
[5] Broadcast IP for CACU: 10.187.212.63
[6] NetMask: 255.255.255.192
[7] Offest to Start usable IP: 0
[8] System Name used for EMS: CACU_NUH
[9] Region Name to be used in EMS: North_HA_1267
[10] Number of EMS Managers: 4
[11] IP Address of EMS Manager1: 10.187.0.39
IP Address of EMS Manager2: 10.187.0.40
[12] Number of NGSM: 4
[13] IP Address of NGSM 1: 10.187.0.22
IP Address of NGSM 2: 10.187.0.23

Chapter 4.

[14] IP Address of the NTP server: 10.187.4.12
[15] Periodicity to sync with NTP server (In Seconds): 900
[0] To Proceed
Enter the option corresponding to the value to be changed
0
To change any value, enter the number corresponding to it, such as to change the NGEMS Region
Name, enter 9.
To proceed (without changing these entries or after changing particular entry), enter 0.
11) After this the script asks whether the IP addresses on the CACU cards have been updated, this
should be confirmed by entering ‘Y’ if the steps in the prerequisites have been completed, else, the
script should be exited and the IP addresses should be assigned to the cards.
********
The physical card IPs for CACU chassis are:
MLS1 = 10.187.212.4
MLS2 = 10.187.212.7
SLM1 = 10.187.212.9
SLM2 = 10.187.212.10
EBM1 = 10.187.212.11
EBM2 = 10.187.212.12
NGTJ1 = 10.187.212.13
NGTJ2 = 10.187.212.19
********
Above IPs present at /home/Ubuntu/CACU_SOURCE/physical_ip_list.txt

for reference
Please make sure these values are assigned as card IPs,

Enter (y/Y) to confirm or 0 to exit installation and assign IPs to
cards
y
12) Once done that is ‘Y’ has been entered to confirm and proceed, the script will ask the following
option:
Available options are:

[1] For Installation and Configuration
[2] For Installation Only (No Configuration Changes)
24 C-DOT MAX-NG
[3] For Configuration Only (No Release Installation)

[0] To Exit without Installation
Select your option
1
During the field migration installation of the CACU for the first time, the user should select the option
1, that is for installation and configuration.
13) After this step, the script prompts for the card on which the installation has to be done, through a
following menu:
Select Card Type:
[1] For SLM
[2] For NGTJ
[3] For EBM
[0] To Exit
Enter Your Option
The user should select each of the cards,that is for the SLM, NGTJ and EBM cards one by one as
the script returns to ask for this input again. Once a card type is selected, the script will proceed
with that card and after the installation is complete on that card, the script will present the same
menu for the other cards.
14) After any card type is selected, the user will be prompted for the IP address of the card to be
confirmed and then some other input parameters for the cards. For SLM card, the script will also ask
if the setup is in a simplex or duplex SLM configuration.
Installation For SLM Selected
Is the system in Duplex (Y/y) or Simplex(Press Enter)

y
15) Now, when the user enters an IP address, here 10.187.1.5 is an example, the ssh prompt is shown,
something similar to the following:
Creating Connection for User:root to the Card(10.187.1.5)

The authenticity of host '10.187.1.5 (10.187.1.5)' can't be established.
RSA key fingerprint is c9:66:1f:4e:6e:b9:c9:c3:cc:46:4c:44:1b:56:ad:1e.
Are you sure you want to continue connecting (yes/no)?
Here, type yes and press Enter.

Chapter 4.
In the above example, 10.187.1.5 is the IP address of the CACU card on which installation is being
done and c9:66:1f:4e:6e:b9:c9:c3:cc:46:4c:44:1b:56:ad:1e is the ssh RSA key for that particular
CACU card (SLM/EBM or NGTJ). These two values will be different for every card depending upon
the site.
16) This will display an output as the following and ask for the password for the root user of CACU card
(SLM/EBM/NGTJ) on which the installation option has been selected :
Warning: Permanently added '10.187.1.5' (RSA) to the list of known
hosts.
root@10.187.1.5's password: (Default is root)
Now try logging into the machine, with "ssh 'root@10.187.1.5'", and
check in:
.ssh/authorized_keys
to make sure we haven't added extra keys that you weren't

expecting.
NOTE: This “warning” is not actually an error or a warning and should be ignored.
17) During the installation of the SLM cards, some prints would be shown related to file transfer and file
creation. One input will be asked related to the secure connection between the active and stand-by
SLM cards, which will be something similar to the following:
******************************************************
* ssh key file not present on this system

* You will have to press enter thrice in a row
******************************************************
Here, the user will be have to press the Enter key thrice for the secure key creation.
18) Once the installation is finished on the SLM cards (simplex or duplex), the script will show the
following output
ssh: : Temporary failure in name resolution

Selected Operation Completed.
26 C-DOT MAX-NG
NOTE: This temporary failure is not an error or a failure, but is shown because the entry of that particular SLM card
was not yet present in the DNS. This should be ignored.
19) Now the user will again presented the main menu of the script and the user should select the
application release installation for other CACU card, say NGTJ card.
Select Option for Another Card

Select Card Type:
[1] For SLM
[2] For NGTJ
[3] For EBM
[0] To Exit
Enter Your Option
2
Installation for NGTJ Selected
20) Again the IP address of the NGTJ card will be asked and output similar to steps 15 and 16 will be
presented. Such warnings are to be ignored The output will be similar to as follows:
Enter IP Address of NGTJ

10.187.212.13
The authenticity of host '10.187.212.13 (10.187.212.13)' can't be

established.
RSA key fingerprint is
ba:7f:2f:86:f5:6f:92:d8:05:7c:db:2e:65:df:07:dc.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '10.187.212.13' (RSA) to the list of
known hosts.
Now try logging into the machine, with "ssh 'root@10.187.212.13'",
and check in:
expecting.
Here, the IP address 10.187.212.13 is just an example IP address for the CACU NGTJ card.

Chapter 4.
21) Now the operator is presented with some information regarding the NGTJ card OS release version
and the FPGA version. When asked to continue with the installation, the operator should enter ‘y’.
NGTJ release on NGTJ 10.187.212.13 is 1.52 and Control FPGA version

is 23 on (NGTJ)
NGTJ @ 10.187.212.13 has 72% free space left
Do you want to continue? (Y/y to continue, Press Enter to exit)
y
You have selected to Continue with the installation
22) Once the initial I2C driver related installation is done on the NGTJ card, a welcome message is
displayed to the operator, that looks similar to:
@@@@@@@@@@ @@@@@
@@@@@@@@@@ @@@@@
@@@@@@@@@@ @@@@@
@@@@@
@@@@@ @@@@@
@@@@@ @@@@@
@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@
C-DOT
At the end of this text it asks whether the operator wants to continue with the installation and to
modify the ‘default input’ file. The operator should continue (y) with the installation and should not
modify the ‘default input’ file. The screen output is:
:-continue?:-: :Want to continue with installation ?[ [n]/y ]: y
Here, ‘y’ should be entered to proceed with the installation.
23) Upon continuing with the installation of the CACU NGTJ card, some other inputs will also be taken
from the user. These include the C5 server IP address, C4 server IP address, whether to enable a
particular gateway on the NGJT card and likewise. The output is shown as follows:
Want to install 'ALL NGTJ APPLICATION softwares' ?[n/y]: y
Want enable to run v5ag after installation?[n/y]: y
Want enable to run priag after installation?[n/y]: y
28 C-DOT MAX-NG
Want enable to run tmg after installation?[n/y]: y
Want enable to run sgl2_start after installation?[n/y]: y

::install (y,y,y,y,y)=--==> enable(y y y y)
Here the operator should select ‘y’ installing a particular gateway on the NGTJ card and for
enabling particular gateway according to the site (as shown in the example above).
24) Once the above fields are entered, some configuration entries will be asked from the operator, such
as the IP addresses of the C5 and C4 servers, enabling PR/DR feature configuration, domain name,
IP addresses of the nameservers, domain name of the sbc etc. (r may be pressed in a later
installation when these values are known to be present already, but for the first time site migration
configuration, the values should be entered according to the site. r is for repeating and using the
value being shown). The output shown is as follows:
: 'Want to enable PR/GR feature' ?[n/y]: y
Note: 'r' means the indicated value is correct
[120s] [1/3]:: INPUT THE VALUE OF DOMAIN NAME: maxng.bsnl.in [r]:

maxng.bsnl.in
[120s] [1/3]:: INPUT THE VALUE OF nameserver [SBC] of PR:

192.168.149.118 [r]: 10.187.1.12
[120s] [1/3]:: INPUT THE VALUE OF nameserver [SBC] of GR:

192.168.109.183 [r]:
10.187.4.12
[120s] [1/3]:: INPUT THE VALUE OF DOMAIN NAME of 'sbc':

sbc.maxng.bsnl.in [r]: sbc.maxng.bsnl.in
[120s] [1/3]:: Input 'P.R.' Floating Ip Of C4 (Primary_mgc):

192.168.103.159 [r]: 10.187.0.12
[120s] [1/3]:: Input 'G.R.' Floating Ip Of C4 (Secondary_mgc):

192.168.119.224 [r]: 10.187.0.15
In the example above, '10.187.212.13' is NGTJ card IP address.

10.187.0.12 is the ’P.R.’ Floating IP of C4 server, whereas 10.187.0.15 is the ‘G.R.’
Floating IP of C4 server.

Chapter 4.
25) Alternatively, if the operator does not want to configure the DR feature, the C5 IP address is asked
as well and the entries related to the domain name are not asked. The output shown is as follows,
when the DR feature is not configured:
Want to install 'Want to enable PR/GR feature' ?[n/y]: n
[120s] [1/3]:: INPUT THE VALUE OF C5: 196.1.106.100 [r]:

10.187.0.15
[120s] [1/3]:: Input The Value Of Primary C4: 192.168.103.159 [r]:

10.187.0.12
In the example above, the DR feature was not enabled selecting ‘n’,'10.187.0.15' is the C5
server IP address and 10.187.0.12 is the C4 server IP address.
26) After these values are provided by the operator, the values are confirmed and the operator is asked
whether to proceed with the installation. ‘y’ should be entered to proceed/re-confirm proceeding
with the installation.
Press y to continue or n to modify above inputs? [ y/n ]: y
Verify these input values

prcd?(y)
[41s]:Want to proceed with these input values...[n/y]: y
27) In case the operator opts to not proceed with the installation, the options presented by the script are
continue:Want to continue with installation ?[ [n]/y ]: n
: Want to continue installation?: :Press 'y' to Confirm , : 'n'

no, I want to exit ... n
28) When the installation option is selected (Point 26), a list of the files to be installed on the NGTJ card
is shown and the file transfer to the NGTJ card starts, where you will be prompted to enter ‘y’ in
intervals.
29) Once the installation step reaches the SG installation, it also asks for some inputs, related to the SG
server and PR-GR configuration.
The output is similar to the following and the user should enter the values asked:
30 C-DOT MAX-NG
Please wait... Processing.....
Enter Domain Name of SG : sgppp
Please wait.... SG tarball is processing.....

Enter PR SGP SERVER VIRTUAL_IP : 192.168.200.70
Enter PR SGP SERVER Bcast_ipAddr : 192.168.200.255
Enter PR SGP SERVER NodeId1 ipAddr : 192.168.200.2
Enter GR SGP SERVER VIRTUAL_IP : 192.168.200.6

Enter GR SGP SERVER NodeId1 Bcast_ipAddr : 192.168.200.8
Enter GR SGP SERVER NodeId1 ipAddr : 192.168.200.10
Please wait, Processing...
please wait... Building tarball for CACU : ngtj
Please wait....Installation in progress ..

TERM environment variable not set.
Sat Sep 23 15:06:10 IST 2017

Installing stk_sgl2 ........
stk_sgl2 installed ...
30) The installation for SGL2 starts after this and when the SGL2 installation is finished, a following
message is displayed:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
!!!! 10.187.212.21 :sgl2 installed sucessfully!!!!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Chapter 4.
31) When the installation of release is completed on the NGTJ card, the NGEMS agent installation on
the NGTJ card, per gateway is asked, and the user should enter ‘y’ according to the gateways
installed on the CACU NGTJ card. An example output is:
Agent directory created on NGTJ card...

Do you want to install NGTJ card EMS Agent? (y/Y) or Enter to skip
y
In the above example, the NGTJ card Agent has been selected for installation and the user has
selected y.
Similarly for other Agents, such as PRI EMS GatewayAgent , V5 EMS Gateway Agent and SG
EMS Gateway Agent, whichever is applicable, y should be entered to installed otherwise, only Enter
should be pressed to skip a particular gateway agent installation.
32) Finally when the installation is complete on the NGTJ card the NGTJ card must be given a
command to reboot:
NGTJ Card needs to go for a reboot now ...

Do you want to reboot NGTJ card now? (y/Y) or Enter to skip
y
reboot_ngtj.sh
100% 43 0.0KB/s 00:00
NGTJ card going for a Reboot now ...
33) Once the installation is completed on the NGTJ card , the script returns to the main menu as the
follows and the installation for EBM card should be selected after this

Select Card Type:
[1] For SLM
[2] For NGTJ
[3] For EBM
[0] To Exit
Enter Your Option
3
34) Finally when all the installation is completed on the CACU cards and the option to exit the script is
selected, the output is shown as
32 C-DOT MAX-NG

Select Card Type:
[1] For SLM
[2] For NGTJ
[3] For EBM
[0] To Exit
Enter Your Option
0
OPERATION COMPLETED.
35) The estimated installation time for the cards is as follows:
a. SLM cards: 5 – 8 minutes

b. NGTJ cards: 8 – 15 minutes
c. EBM cards: 3 – 5 minutes
The above timing varies upon the space available and performance of the thin-client/PC being used
for installation, and the connection speed between the CACU cards and the thin-client/PC.

Chapter 4.
Appendix-H
(Automated Installations for LAGU Application Release/Patch)
PREREQUISITES:
a) Ensure that the IP addresses are available with the user as described in Appendix –A.
b) The thin-client has been prepared/configured according to the Appendix-I.
c) For complete release and patches installations, ensure that all the eight LAGU application
release/patch tarballs (9) as mentioned in the Appendix-F are present in the thin client folder,
say “/home/Ubuntu/LAGU-SOURCE/”.
d) The NGTJ cards have to be loaded with the provided VER53 uboot and dtb files. Refer the
Appendix-E.
Steps of LAGU Applications release and patch installations:

1) Connect the LAGU chassis with the power supply and turn on the power.
2) Connect the minicom cable to the RS-232 port of one of the NGTJ cards of the LAGU chassis
and log-in using the username “root” and password “root”.
3) Before proceeding for LAGU installations, do the following steps to shutdown the LAG
applications :
# /cdot/bin/mount_mmc_ext3
# chroot /mmc /etc/lag_shutdown.sh 2
4) Connect the LAGU with the CACU for uplink either using the Ethernet ports to the CACU MLS
card or via the E1/PCM links on the LAGU to the EBM cards of the CACU.
It should be noted that both the Ethernet and E1 links for a same LAGU should not be used,
otherwise it may cause network looping.
5) Configure the site IP for the LAGU NGTJ cards through the minicom terminal using the
following four (4) commands to be typed on the terminal window of the NGTJ card in the
sequence given(replace values inside angular brackets < >) :
# /sbin/ifconfig eth0 down
# /sbin/ifconfig eth1 down
34 C-DOT MAX-NG
# /sbin/ifconfig eth0 <IP-Address-of-1st-LAGU-NGTJ-card> netmask <Netmask-

address-of-the-NGTJ-card> broadcast <broadcast-IP-address-of-the-NGTJ-card>
up
# /sbin/ip route flush 0/0
# /sbin/route add default gw <IP address of MLS-1>
6) For complete release and patches installations, ensure that all the nine LAGU application
release/patch tarballs (9) as mentioned in the Appendix-F are present in the thin client
folder, say “/home/Ubuntu/LAGU-SOURCE/”. In case the release CLAGL2_4_1.2_1 is
already installed, for only the patches installations over LAGU, it may be noted that at least
the following four (4) patch files should be present before starting the installations :
 PATCH9-Over-CLAGL2_4_1.2_1-EBM_loop_RBT_Call_Clear_log.tar- 5785600 bytes

 PATCH1-Over-CLAGL2_4_1.2_1-cli_bulk_commands.tar – 10280960 bytes
 PATCH13-Over-SWINSTL1_1_2.16_1-SWBELAG-COMB.tar – 276480 bytes
 bkrs_lagbackend.tar – 215040 bytes
 PATCH5-Over-SWINSTL1_1_2.16_1-SCHDBACKUP_RESTORE.tar – 10240 bytes
7) Untar the PATCH9-Over-CLAGL2_4_1.2_1-EBM_loop_RBT_Call_Clear_log.tar using the

below mentioned command:
#cd /home/Ubuntu/LAGU-SOURCE
#tar -xvf PATCH9-Over-CLAGL2_4_1.2_1-EBM_loop_RBT_Call_Clear_log.tar
8) Invoke the install_lagu.sh script as follows :

# ./install_lagu.sh
9) Following options are provided to user for installations:

[1] Installation of LAG Application Software Release on LAGU
[2] Installation of LAG Patch Release (including Backends) on LAGU
[3] Installation of LAG Application Software Release and Patch Release
(including Backends) both
[0] Exit
Select your option
10) Currently for field migrations, option [2] will be invoked in case the base release

Chapter 4.
CLAGL2_4_1.2_1 is already installed over the LAGU cards and only the patches need to be
loaded. In this case, ensure that the four(4) tarballs as mentioned in the step 5 above are present.
11) The option [3] is executed in case the base release CLAGL2_4_1.2_1 and the latest patches need
to be installed over the LAGU cards. This option is the most appropriate to ensure proper release
and patches installation. In this case, ensure that all the nine (9) tarballs for LAGU as mentioned
in Appendix-F are present.
12) Backend Release as well as patches will be installed as well (if their tarballs are present at the
same path, as mentioned in Point no. 6), when the user will select either option [2] or option [3].
13) In case we select the option [3], then following output/prompt is given to user:
Option selected for both Application Software Release and Patch

Release installation on LAGU NGTJ Cards
Checking for Release Tar files ...
Release files are present for LAGU NGTJ
14) The user is asked for an option to perform an installation on a simplex or duplex LAGU system
Enter 2 for Duplex Installation and 1 for simplex installation

15) For a simplex installation, the user is shown the following output:
Option of Simplex Installation selected

Enter the COPY-ID(0/1) of LAGU's NGTJ Card
16) If the user selects the option for a duplex installation, the output shown is as:
Enter IP Address of the LAGU's 1st NGTJ Card(Copy-0)
Upon entering the IP address of the first NGTJ card, the user is prompted for the IP address of
the second NGTJ card:
Enter IP Address of the LAGU's 2nd NGTJ Card(copy-1)

The user is not prompted for a copy id in case the duplex option is selected.
17) The user is then asked whether a backup of existing configuration files on the LAGU cards has
36 C-DOT MAX-NG
to be taken or not, the output shown is:
Do you want to take backup of configuration files before installation?

(Warning: Existing files on the card may be incorrect)
It is recommended that for the first time field migration installation, this option must not be
done. Output shown is:
Not taking backup due to user action ...

Enter new configuration value
For subsequent installation on the site, it may be input as Y.
18) After the above entries are taken, the following configuration values will be asked from the user:
Is DNS Based routing to be done? Enter your choice [yes/no]

<yes or no entered>
It has to be entered as a YES if the DNS server is known.

19) If the DNS based is selected as yes, the user is asked for the following entries:
(Note: The following values of the IP addresses, domain name, port, etc are just indicative
examples and must be something else at the site.)

yes
Enter the search domain
maxng.bsnl.in
Enter the IP address of primary DNS server
10.187.0.12
Enter the IP address of secondry DNS server
10.187.0.10
Enter the DNS Name for Softswitch
nzggnsbc.maxng.bsnl.in

Chapter 4.
Enter NTP Server IP

10.187.0.13
Enter the IP address for Feature Server
10.187.0.15
Enter the IP address for EMS Server
10.187.0.21
Enter the Port for EMS Server
8003
Is PR/DR EMS servers / Multiple EMS servers configured? Enter
your choice [yes/no]
yes
Enter the IP address for Secondary EMS Server
10.187.0.19
8003
Enter the IP address of the machine which is to be mounted on
LAG e.g. IP of ThinClient
192.168.200.20
20) If a no is input by the user for DNS based routing, the user prompts for input would be as the
followings:
(Note: These values are just examples, and must be replaced with actual values at the site.)

no
Enter the IP address for Softswitch
192.168.200.73
Enter NTP Server IP
192.168.200.73
Enter the IP address for Feature Server
192.168.200.74
Enter the IP address for EMS Server
192.168.200.87
38 C-DOT MAX-NG

5008
Is PR/DR EMS servers / Multiple EMS servers configured? Enter
your choice [yes/no]
yes
Enter the IP address for Secondary EMS Server
192.168.200.100
9999
Enter the IP address of the machine which is to be mounted on
LAG e.g. IP of ThinClient
192.168.200.20
21) After these entries have been done, the user is then displayed the inputs received so far and an
option to change them.
The user may change any entry corresponding to its number if needed., eg, to change the value of
NTP Server IP Address, 6 should be entered.
The output is similar to:
The inputs received so far are:

[ 1 ] DNS Based Routing = yes
[ 2 ] Search Domain = maxng.bsnl.in
[ 3 ] Primary DNS Entry = 10.187.0.12
[ 4 ] Secondary DNS Entry = 10.187.0.10
[ 5 ] Softswitch Name/IP Address =
nzggnsbc.maxng.bsnl.in
[ 6 ] NTP Server IP Address = 10.187.0.13
[ 7 ] Feature Server IP Address = 10.187.0.15
[ 8 ] EMS 1 Server IP Address = 10.187.0.21
[ 9 ] EMS 1 Port = 8003
[ 10 ] EMS 2 Server IP Address = 10.187.0.19
[ 11 ] EMS 2 Port = 8003

Chapter 4.
[ 12 ] IP of the machine to be mounted on LAG = 10.187.1.20

[ 13 ] Path of the machine to be mounted on LAG =
/etc/SWINST/FTP/
[ 0 ] To Proceed
Do you want to change any value? [yes/no]
no
User selected to proceed with the given configuration
22) In the next prompt, the script creates an ssh/scp connection between the PC/Thin-client and the
NGTJ cards. The user is asked to ensure the authenticity of the ssh host (NGTJ cards) followed
by the password of the NGTJ card, which should be entered as root. The following output should
be displayed:
The authenticity of host '10.187.1.5 (10.187.1.5)' can't be

established.
RSA key fingerprint is
c9:66:1f:4e:6e:b9:c9:c3:cc:46:4c:44:1b:56:ad:1e.
In the above example, 10.187.1.5 is the IP address of the NGTJ card on which installation is
being done and c9:66:1f:4e:6e:b9:c9:c3:cc:46:4c:44:1b:56:ad:1e is the ssh RSA key for that
particular NGTJ card. These two values will be different depending upon the site.
23) After this step, the password for the root user of the NGTJ card is asked, with an output similar
to:
hosts.
root@10.187.1.5's password:
Here, enter the password of the root user. The password as you type will not be visible.
Note that the Warning shown here is not any error or warning, so should be ignored.
24) Now, the installation proceeds and takes around half an hour for each NGTJ card, thus around an
hour for each LAGU. There would be continuous prints on the screen while the installation
40 C-DOT MAX-NG
progresses.
25) First the release is installed and the prints are shown as follows:
NGTJ release on simplex NGTJ 10.187.1.5 is 1.52 and Control FPGA

version is 23 on (NGTJ)
jjfs2 is already mounted on NGTJ1 @ 10.187.1.5, will initiate
mmc is mounted on NGTJ @ 10.187.1.5, will initiate installation
Shutting down the LAG process before installation
Installing files on NGTJ - 10.187.1.5
lagconf_1.2.tar
100% 8290KB 2.0MB/s 00:04
lagrel_1.2.tar
100% 44MB 1.1MB/s 00:41
Untarring lagconf*.tar file...
Untarring lagrel*.tar file...
Executing conf_install.sh...
/etc/lag Exist
hosts.tmp arleady exists
Executing install.script...
CHECKING FOR LP ...
YES IT IS LP .... CONTINUE INSTALLATION
INTALLATION OF LAG IN PROGRESS
Creating Directories ....

Directories Created
Installing & Verifying FT module .. . . . . . . 100%
Installing & Verifying DB module . . 100%

Chapter 4.
Installing & Verifying Initialisation module . . 100%
Installing & Verifying Communication module . . . 100%
Installing & Verifying Libraries . . . . . . 100%
Installing & Verifying PSG Binaries . .. . . . 100%
Installing & Verifying CTSB Modules . . . . 100%
Installing & Verifying Utilities Modules . . . . . . 100%
Installing & Verifying Configuration Files . . . . . 100%
Installing & Verifying Call Processing PACKAGE ..........100%
MAKING DELIVERABLE LIST ....
Installing lag_pre_reboot & lag_ems_reboot.sh in /jffs2/conf
INSTALLATION OF LAG COMPLETED SUCCESSFULLY
PLEASE DO LAG EMS AGENT SOFTWARE INSTALLATION ....

clagl2_4_1.2_1-lagagent.tar
100% 10MB 436.1KB/s 00:23
Untarring clag*-lagagent.tar file...
clagl2_4_1.2_1-linuxagent.tar
100% 3450KB 1.7MB/s 00:02
Untarring clag*-linuxagent.tar file...
Editing install_run_lag.sh on 10.187.1.5
Editing install_run_lin.sh on 10.187.1.5
Executing install_run_lag.sh...
Enter the option : 1 Installation on HOST
2 Installation on PIC
42 C-DOT MAX-NG
3 Installation on SGTK
4 Installation on NGTJ
RELEASE IS INSTALLED SUCCESSFULLY ON PATH
/usr/local/bin/lag/AGENT
with directory name ^[[1m lagagent ^[[0m
....
....
....
....
PLEASE CREATE BASE REFERENCE FILE FOR AUDIT USING
/usr/local/bin/lag/AUDIT/auditBaseFileCreation.sh ...
Executing install_run_lin.sh...
Enter the option : 1 Installation on HOST
2 Installation on PIC
3 Installation on SGTK
4 Installation on NGTJ
RELEASE IS INSTALLED SUCCESSFULLY ON PATH
/usr/local/bin/lag/AGENT
with directory name ^[[1m linuxagent ^[[0m
....
....
....
....
Modifying /jffs2/conf/net file ...
Modifying the net file...
Modifying /mmc/etc/lag_sys.conf file ...
SELFIP0=10.187.1.5 MATEIP0=10.187.1.7 FLOATIP=10.187.1.9
ACTDSPIP=10.187.1.10 SBYDSPIP=10.187.1.11
SELFIP1=10.187.1.6 MATEIP1=10.187.1.8
The gateway 1 is 10.187.10.2
Please wait while we retrive the value of DSP MAC Address ....
DSP Booting...compiled on Aug 24 2016 11:51:53
RESETING TI Dsp through GPIO
TI DSP is OUT_OF_RESET and ready for HPI boot
Loading Core0
Loading Core1
Loading Core2
Loading Core3

Chapter 4.
Loading Core4
Loading Core5
Writing DEV_COMPLETE_STAT to bring all TI DSP cores out of reset
and start booting
DEV_COMPLETE_STAT = 3f
DSP Code version 2_1_5
32.195.143.7.141.120
NETMSK=255.255.255.0 BRDCST=10.187.1.255 GWAY=10.187.1.2
MACADDHEX=20:c3:8f:07:8d:78 DSPMACDECDOT=32.195.143.7.141.120
lag_sys.conf file updated on NGTJ card 10.187.1.5
lag_resolv.conf
100% 99 0.1KB/s 00:00
lag_resolv.conf
100% 99 0.1KB/s 00:00
26) After this, the backend for remote software installation and backup and restoration modules are
installed when the option to install patch installation was also selected in point 9. There is no
need to manually install them. The prints are shown as follows:
Option selected to perform patch installation also on 10.187.1.5 ...

PATCH5-Over-SWINSTL1_1_2.16_1-SCHDBACKUP_RESTORE.tar
100% 10KB 10.0KB/s 00:00
bkrs_lagbackend.tar
100% 210KB 210.0KB/s 00:00
Creating backend_install.sh file...
backend_install.sh
100% 43 0.0KB/s 00:00
Shutting down the lag_backup.exe process...
This script should be run from RAMDISK

This script is to STOP LAG backup and restoration process
Killed: lag_backup.exe
in RAMDISK Verify by command: ps | grep lag_backup.exe
mkdir: cannot create directory '/mmc/BKRS_RELEASE': File exists
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
BACKUP & RESTORATION INSTALLATION FOR LAG STARTED
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Installing backup.conf in /etc
44 C-DOT MAX-NG
Installing lag_backup.exe in /usr/bin

Installing lag_backupschd.exe in /usr/bin
Installing lagbkrs_start in /usr/bin
Installing lagbkrs_stop in /usr/bin
Installing CDS_FTP.sh in /usr/bin
================================================================
Installation of BACKUP-RESTORATION completed ...
Now configure /etc/backup.conf file with the required information
To start backup process usage : /usr/bin/lagbkrs_start
To stop the backup process usage : /usr/bin/lagbkrs_stop
================================================================
Creating config_install.sh file...

config_install.sh
100% 162 0.2KB/s 00:00
Restarting the lag_backup.exe process...
This script should be run from RAMDISK

This script is to START LAG backup and restoration process
!!!! lag_backup.exe found!!!!

mkdir: cannot create directory 'bkrs': File exists
lag_backup.exe: no process killed
Verify by command: ps -ef | grep lag_backup.exe
See log at : tail -f /tmp/bkrs.log
Shutting down the swbe_lag.exe process...

PATCH13-Over-SWINSTL1_1_2.16_1-SWBELAG-COMB.tar
100% 270KB 270.0KB/s 00:00
Creating Directory Structure for S/W Installation BE Software
Installing swbe_lag.exe ...
Installing CRS_FTP.sh ...
Installing CRS_FTP_root.sh ...
Installing INST.sh ...
Installing INST_root.sh ...
Installing conf_mod.sh ...

Chapter 4.
Installing conf_mod_root.sh ...

Installing ftpstatus.sh ...
Installing ftpstatus_root.sh ...
Installing patch_move.sh ...
Installing swbe_comn.conf ...
Installation over
Restarting the swbe_lag.exe process...
PATCH-Over-CLAGL2_4_1.2_1-dual_GW_EBM_loop.tar
100% 540KB 540.0KB/s 00:00
LAGI.exe: no process killed
lagpatch
100% 165 0.2KB/s 00:00
The patch has been installed sucessfully...
Since backup was not taken, it is not to be restored

Release and Patch installation both done, will now go for a
Reboot/Process restart...
Installation on NGTJ card 10.187.1.5 of LAGU completed

Do you want to reboot the NGTJ Card 10.187.1.5(Enter y for Yes, n for
No)?
n
Restart the process on the NGTJ card 10.187.1.5 using the command
lag_restart.sh
46 C-DOT MAX-NG
Appendix-I
(PREPARATION OF THE THIN CLIENT MACHINE)
Following are the steps for preparation of the Thin-client machine for usage in CACU and LAGU cards
access and software loading and configurations:
1) Connect the Thin-Client machine/box with the keyboard, monitor and mouse, power source, and
boot the thin client.
2) Log-in to the thin-client with the default user named Ubuntu (in case not directly logged in).
3) Open the terminal window.
4) Set the password for the ‘root’ user at the thin client machine. The procedure to it is as follows:
a. In the terminal window opened in step 3, type the command:
#sudo passwd root
b. This command firstly asks the operator to enter the password of the Ubuntu user, which
is cdot123.
c. After this enter the password for the root user, as root123. The password will be once
input and then confirmed. Thus the password has to be entered twice.
d. The password for the root user has been updated.
5) Now, connect the thin client with the CACU MLS-1 card at any free FE port (RJ-45) with an
Ethernet cable.
6) Connect the USB interface of the minicom device with any free USB port of the thin-client.
After this, configure the minicom settings using the following steps:
a. #su - root
b. #ls -lrt /dev/*tty*
Note the last entry, it should be similar to something such as:
crw-rw---- 1 root dialout <some no.>, 0 <date> <time> /dev/ttyUSB0
c. Note the last entry that may be /dev/ttyUSB0 or /dev/ttyUSB1 etc depending upon the
USB port used.
d. #minicom - s
e. It will ask Change Which Setting and present a menu list.
f. Go to the option ‘Serial Port Setup’ and press Enter.
g. In the input menu, press ‘A’ to edit the Serial Device to a value noted in the point b/c

Chapter 4.
above and press Enter to save it.

h. Set the option E, Bps/Par/Bits to 115200 8N1 if not set already.
i. Set option F, Hardware Flow Control to No.
j. Set the option G, Software Flow Control to No.
k. Press Enter to go back to the previous menu.
l. In this menu, go to the option Save Setup as dfl and press Enter. This will save the
settings made in the steps g through j. A message Configuration Saved will be
displayed.
m. Go to the Second Last option, Exit and press Enter. This exits from the Menu and
launches the minicom.
n. Note: In case the USB port is changed for the minicom, steps b to g must be
repeated.
7) Now connect the other end of the minicom cable to the MLS-1 card of CACU and assign it
VLAN-1 IP address according to the Appendix–B.
8) Ensure that the MLS cards have been configured for the Native VLAN IPs, gateways and the
WAN IPs/routes configurations have been completed for uplink as detailed in Appendix–B.
9) Configure the thin client machine IP address settings as per the IP address available in the IP
ADDRESS DETAILS mentioned as “Terminal (Thin Client) IP” (in Appendix – A) using the
following steps:
 su - root
 #vi /etc/network/interfaces
 Type 100dd
 Press ‘i’ to enter into the insert mode in the editor and type the following (while replacing the
fields inside < > with the actual values):
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address <IP address of the thin client>
netmask <Netmask of the thin client>
network <Network address of the thin client>
broadcast <Broadcast IP address for the thin client>
gateway <Management IP Address of the MLS-1 card>
 Press the ‘Esc’ key to exit out of the insert mode of the editor and type ‘:wq’. After this,
press the Enter key.
48 C-DOT MAX-NG
 Now bring the network interface up using the command:

#ifconfig eth0 up
 Confirm the settings done above using the command ‘/sbin/ifconfig’ on the terminal
window and after that, ping the gateway IP address, that is the IP address of the MLS card-0,
using the command ‘ping <IP address of the MLS-1 card>’ in the terminal window.
10) Now test the core nodes reachability and the connection speed as mentioned in the steps below
(with transfer of application patches from the Core server) :
a. Ping the Core Server using its domain name. The command to be used is:
#ping <Domain Name of the Core server>
In case the pinging results in a packet loss, ensure the IP connectivity is made.
b. If ping is known to be disabled, use the following command to check the IP connectivity:
#nc –w 1 <Domain name of the Core Server> 22
This command should output something similar to
SSH-2.0-OpenSSH_5.3
This means that the IP connectivity is fine.
If the nc command does not output anything after some time, this means that there is some
issue in the reachability till the core. Ensure the IP Connectivity first.
c. If the ping or nc (if ping is disabled) is successful, type the following commands:
#mkdir /home/ubuntu/LAGU-SOURCE;scp -r
USER@<CoreServer>:/home/fileuser/LAGU-SOURCE/*
/home/ubuntu/LAGU-SOURCE
This will transfer LAGU Access Software files from the core server to the thin client and
save them at the location /home/ubuntu/LAGU-SOURCE. This will take few minutes.
d. Similarly, type the following commands to transfer the CACU Access software and patches
from the Core node to the thin client:
#mkdir /home/ubuntu/CACU-SOURCE;scp -r USER@<Core

Server>:/home/fileuser/CACU-SOURCE/* /home/ubuntu/CACU-SOURCE
This will also take few minutes.

Chapter 4.
e. Further, type the following commands to transfer miscellaneous other Access software from
the Core node to the thin client:
#mkdir /home/ubuntu/MISC;scp –r USER@<Core

Server>:/home/fileuser/MISC/* /home/ubuntu/MISC
This will also take few minutes.
f. Based upon the success of the above two points, the connectivity between the core server and
the access node network is ensured.
g. Following steps need to be followed for installation of the tftp server over thin client and
copy the relevant drivers at the /var/lib/tftpboot/ path:
(Please enter the Ubuntu user password when prompted)
 # cd /home/ubuntu/MISC
 # sudo dpkg -i tftpd-hpa_5.0-11ubuntu2.1_armel.deb
 # sudo cp tftp /etc/xinetd.d/
 # sudo cp NGTJ.u-boot.bin.VER53 /var/lib/tftpboot/
 # sudo cp NGTJ.dtb.VER53 /var/lib/tftpboot/
Note: In case of space issue over the Thin Client machine; check with
the following command for presence of large size files (say more than
100 MB)
# find / -size +100M
And then remove the unwanted files to create space
50 C-DOT MAX-NG
h. Following steps need to be followed for quicker response of EMS GUI in ThinClient.
 Go to ejre1.6.0_25 path on the client machine

# cd /usr/lib/ejre1.6.0_25/bin/
 Invoke ControlPanel
# ./ControlPanel
 Click on Java tab in the Java Control Panel GUI
 In the Java Runtime Environment Settings GUI, enter in the Runtime Parameters
-Xms128m –Xms1024m
 Click OK, Apply.

Chapter 4.
52 C-DOT MAX-NG

Chapter 4.
Appendix-K
(MLS Card MAC and IP Address Entry)
MAC ADDRESS ALLOCATIONS IN MLS CARD (with Software version 3.65 static layer-3)
The MLS card requires one MAC address for the system itself (CPU) and one for each of the front
ports. The front port SMACs are needed for PAUSE frame generation. So, in total 24 MAC
addresses get allocated to each MLS card. We have to reserve a pool of 24 MAC addresses for
each MLS card but need to enter only the first MAC address of the pool as per the below
mentioned steps. The rest of 23 MAC addresses get internally allocated upon entry of the first
MAC for CPU.
NOTE: This procedure is required to be executed only if pool of 24 MAC addresses have not been
already allocated to each MLS card (with steps as mentioned as below to enter only the first MAC
of the 24 MAC pool).
Steps for MAC address allocation:
3. Connect minicom cable from Thin Client PC to MLS card (7th and 8th slot MLS cards) using
USB to serial convertor. The box delivered at site contains one Minicom cable ( with 3 pin connector
at one end to be connected to CACU chassis and 9-pin connector at other end to be connected to
Serial to USB convertor delivered along with Thin Client PC). The one end of one cable delivered in
USB to serial convertor box will be connected to rounded end of 9 pin connector and 9 pin
connector will be connected to minicom cable (black) delivered with the CACU chassis. Minicom
ports are available at the rear end of each slot of CACU chassis.
4. After initializing minicom , login prompt will automatically come and login prompt will appear
(login user: admin password : <enter>). Here password is not required just press Enter key. You will
be logged in MLS card and # prompt will appear.
# platform debug allow
(Assuming MAC Address pool of MLS card is, say 00-01-c1-00-00-01 to 00-01-c1-00-00-18 in
hex)
# debug board mac 00-01-c1-00-00-01
# platform debug deny
Note: Please do not enter commands with # prompt. For example,

Please enter platform debug allow command only.MLS cards delivered by BEL
manufacturer will have MAC address on front face plate of MLS card.MAC address of MLS
cards delivered by manufacturer ECIL will be re-entered using above procedure.
As the MLS cards supplied by ECIL have been allocated with only 1 MAC address each; but
we require to allocate 24 MAC addresses for each MLS card. So, the site wise MAC
54 C-DOT MAX-NG
addresses have been allocated for the all sites of South/West and North/East (for
Rajasthan Circle only).
Only the First MAC address out of the allocated pool of 24 MACs is mentioned for
each MLS card for each site.
It may be noted that the only the First MAC address (out of the pool of 24 MACs)
has to be entered as per the simple procedure given the Access site migration
document also (Appendix-B). The rest of the 23 MACs get internally allocated to ports.
As mentioned in the Access site migration document also :

c) In case the MAC address for the MLS cards (MLS1 & MLS2) are mentioned in the
“IP ADDRESS DETAILS”, then only these need to allocated to the CACU MLS cards
during IP configuration using minicom. Paste the stickers for the MAC address
allocated on the MLS cards face plate. Refer Appendix-B. This step is required
only in case a pool of 24 MAC addresses is not allocated to each of MLS card.
NOTE: The same will be entered in the MAX-NG Web Portal under IP ADDRESS DETAILS
head for these ECIL supplied sites. The same can be taken from below google drive link.Just copy
and paste link in Web Browser.
https://drive.google.com/file/d/19_OKTGc356k961l0_px4BsrVt8Ho738c/view?usp=sharing
https://drive.google.com/file/d/1BKBYuekzRflv3UxwVkh6qA35XgwXt1Zl/view?usp=sharing
IP ADDRESS ALLOCATIONS IN MLS CARD:

(Refer to the detailed MLS configuration document with snapshots of the GUI based
configurations)
The Management IP address of each MLS card will be used as the gateway IP address for the
CACU cards. The configuration may be done through the CLI or GUI. The first steps is for
assigning IP address to the default VLAN 1 (if not assigned) and then the GUI using a browser

Chapter 4.
can be used to configure the MLS cards. WAN IPs are for IPTAX WAN, SSTP WAN, C-DOT
WAN and spare WAN in BSNL IP/MPLS network.
Note: The examples of the commands are shown starting with a '#' prompt.
LAN AND WAN IP POOL:

c) LAN IP pool starting from 10.187.35.0 to 10.187.35.255 of 256 IPs denoted as 10.187.35.0/24
with the two Gateway IPs as 10.187.35.4 & 10.187.35.7
d) The VLAN1 will be created at both MLS cards which is the native VLAN for the LAN IP pool
subnet allocated to that site.
The following Steps to be performed using a serial interface/minicom, unless a default VLAN1 IP
address is already assigned.
4. Ensure that the thin-client has been configured as per the details given in the Appendix-I.
Connect Minicom Cable from C-DOT MLS-1 card to Thin Client/Client PC/ Laptop.
5. Launch Minicom Application in Thin Client/PC/Laptop as a root user.
# minicom
6. Assign an IP address to the VLAN 1 (default) of the C-DOT MLS-1 card as :
#configure terminal
#interface vlan 1
(ip address <ip address of VLAN 1> <netmask>)
#ip address 10.187.35.4 255.255.255.0
#exit
# copy running-config startup–config
# show ip interface brief
(This command will show the ip address which has been configured).
Example:
Interface Address Method Status
56 C-DOT MAX-NG
--------------------------------------------------
Vlan 1 10.187.35.4 Manual UP
Note: Please do not enter commands with #.

Chapter 4.
Appendix-L
(MLS Card CEServices3_65-MLSSD1_SW002.dat loading)
Firmware update through GUI of MLS card:
4) Connect minicom cable to 7th slot and 8th slot MLS cards (one by one).Check minicom settings and
launch minicom application in Thin Client.
5) Once minicom application is launched, login to MLS through ‘admin’ login from the thin client
machine with the MLS Application software CEServices3_65-MLSSD1_SW002.dat loaded.
6) Ensure that the network configuration data is saved (MaintenanceConfiguration  Save startup-
config). For this, go to MLS GUI through Management IP in Firefox browser.
7) From Maintenance-> Software -> Upload page, Firmware of the card can be updated.
Browse the PC location for the firmware in CEServices3_65-MLSSD1_SW002.dat format. Click
‘upload’ button. After the software image is uploaded, a page announces that the firmware update
is initiated. After about a minute, the firmware is updated and the switch restarts.
Warning: While the firmware is being updated, Web access will not function. The front LED
flashes Green/Off with a frequency of 10Hz while the firmware update is in progress. Do not
restart or power off the device at this time or the switch may fail to function afterwards.
8) For Bridge settings, Go to Configuration > System > Spanning Tree > Bridge Settings in
STP Bridge Configuration as shown in the screenshot given on next page.
58 C-DOT MAX-NG

Chapter 4.
60 C-DOT MAX-NG
Appendix-M
(Automated Installations for CACU Application Release/Patch)
PREREQUISITES:
8) The application release CEServices3_65-MLSSD1_SW002.dat should be loaded on both the MLS
cards of the CACU.
9) The dtb file for the NGTJ card should be loaded on the SE3 or AE3 NGTJ card to be used in the
CACU.
10) The CACU deliverables described in the Appendix-F, part 2 should be copied to a directory on the
thin-client/PC from where application release installation has to be done on the CACU cards.
11) A detailed list of IP addresses to be allocated to the cards of CAU should be present as described in
the Appendix - A.
12) The thin-client should have been configured and readied according to the Appendix-I.
13) Connect an RS-232/minicom cable to the thin-client at one end and with the minicom serial port
behind each card slot one by one to assign IP addresses to the cards.
14) Log-in to the cards via the minicom using the username “root” and password “root”. The process to
assign IP addresses to the every type of CACU cards is described as follows:
 For MLS card IP settings; set the VLAN1 (native default VLAN) IP address. See Appendix-B for reference.
 For SLM cards IP settings (eth1 port is used)

 #cd /jffs2/conf
 # > net
 #vi net
 Press ‘i’ to enter the INSERT mode of vi editor and then add/edit the following 3 lines of net file.
ifconfig eth1 down
ifconfig eth1 <SLM-CARD-IP-ADDR> netmask <netmask> up
Note : Gateway IP will be the IP list of first MLS card.
 After editing the file successfully, save and exit the net file by first pressing the ‘ESC’ key and then
“:wq” and then press ENTER key
 For CACU NGTJ card (SE3 version) IP settings; eth0 port is used
Note: In case the CACU NGTJ card is not accessible from minicom, login to the NGTJ card from the Thin Client
using “ssh root@<NGTJcard-IP-Address>” (with the default IP address allocated to the card by the
manufacturer). Before this step, the Thin Client should also be set with the default IP subnet of the NGTJ card,
so that the NGTJ card can be accessed from the Thin Client machine. And after changing the IP of the NGTJ
SE3 card for the site IP, the Thin Client IP should be reverted to the site wise IP for the thin client.
 #mount /dev/mtdblock0 /jffs2
 #cd /jffs2/conf
 # > net
 #vi net
 Press ‘i’ to enter the INSERT mode of vi editor and then add/edit the following 3 lines of net file.
ifconfig eth1 down
ifconfig eth0 <NGTJ-CARD-IP-ADDR> netmask <netmask> up

Chapter 4.

 Save the net file by pressing Esc key and then typing: wq and then press Enter/Return key.
 For EBM card IP settings (eth0 port is used )

 #cd /jffs2/conf
 Open ‘net’ file and edit with following 4 lines using ‘vi’, with the i and save the net file (using a
sequence of Esc, :wq and Enter commad on vi editor)
ifconfig eth0 <EBM-CARD-IP-ADDR> netmask <netmask> up
cd /cdot/bin
./bcm_rst
After this, press “Esc” key then type “:wq!” and then press “Enter” key
Once the above is ensured, proceed with the actual installation of the application software release as
given below.
Following is the exact location of net files in CACU cards SLM,NGTJ and EBM cards and is as
follows:
After logging into cards,
For NGTJ card:
# ssh root@<IP Address of NGTJ card>

# cd /jffs2/conf
# ls
In /jffs2/conf directory, net file is present.
For EBM card:
# ssh root@<IP Address of NGTJ card>

# mount –t jffs2 /dev/mtdblock5 /jffs2
# cd /jffs2/conf
# ls
62 C-DOT MAX-NG
For SLM card:
# ssh root@<IP Address of SLM card>

# mount –t jffs2 /dev/mtdblock5 /jffs2
# cd /jffs2/conf
# ls
SOFTWARE INSTALLATION PROCEDURE:
36) Switch to the root user on the thin-client/PC (to be used for further installation process), if not
already using the command ‘su - root’.
37) Now connect the thin-client with any free Ethernet port (RJ-45) available on the MLS-1 card at the
7th slot of the CACU chassis.
38) Assign an IP address to the thin-client (or PC) using the IP address available at the site as detailed
in the Appendix I (steps 7 onwards). If already assigned, please ignore.
Following is the procedure to shutdown processes in SLM , EBM , and NGTJ cards for IP assigning
as per the site IP list.
For SLM card,
# Login into card :

# ssh root@ < IP address of SLM card>
# cd /jffs2_ram/SLM/bin
# ./shm_shutdown.sh
Shm.exe processes will be shut down. After this messages in minicom terminal will be stopped.

Chapter 4.
For EBM card,

Login into card :
# ssh root@<IP address of EBM card>
# cd /jffs2_ram/eeb/bin
# ./eeb_stop.sh
For NGTJ card,
Login into card

# ssh root@<IP address of NGTJ card>
# cd /mmc/ngtj
# ./stopall
Note : After following these steps, each card can be accessed through Minicom and Ethernet cable.
Thin Client will be connected to respective cards through minicom cable and Ethernet cable
(delivered alongwith equipment) to 7A port of MLS card present at rear end of CACU chassis.
39) On the thin-client/PC for installation, go to the path where CACU application release deliverables
have been copied using the command:
#cd /home/Ubuntu/CACU-SOURCE
40) Now, give the script named PATCH10-Over-SLML1_1_1.5_1-install_cacu_cards-NGTJ-

INSTALL.sh executable permission using the command
#chmod +x *sh
41) Execute the script using the command:
#./PATCH10-Over-SLML1_1_1.5_1-install_cacu_cards-NGTJ-INSTALL.sh
42) When the script is run for the first time on a particular thin-client/PC, the script will initiate the
unzipping of the release/patch files locally to arrange them in a structure as required during the
installation on the cards.
43) Once the unzipping is complete, the script asks for the Type of CACU system. For MAX-NG, it
must be entered as 1. Output is similar to
64 C-DOT MAX-NG
Enter Configuration Type, 1 for MAX-NG or 2 for The Red Network

The Configuration Selected for installation is 1
Enter Y/y to continue with above entered config or no to enter new one
44) After this, the script will ask for input for various parameters such as the IP addresses for the
CACU, IP address of the NGEMS, NGSM, NTP server etc. The sample output is:
Configuration file is not present, all the values need to be filled
All the values need to be entered:
Enter the Configuration Type for CACU
Already Entered Configuration is 1. Want to continue with it?
Enter y/Y to Continue with Above entered configuration or n/N to enter new one
y
Continuing with configuration 1
The Updated Configuration value is 1
Enter the Start IP for CACU
Enter Start IP For CACU Range
10.187.212.2
The updated Start-IP is 10.187.212.2
Enter the End IP for CACU
Enter End IP For CACU Range
10.187.212.25
Final output 10.187.212.25
End IP is as expected
The updated End-IP is 10.187.212.25
Enter the GateWay IP for CACU
Enter Gateway IP For CACU
10.187.212.4
The updated Gateway-IP is 10.187.212.4
Enter the BroadCast IP for CACU
Enter BroadCast IP For CACU
10.187.212.63
The updated Broadcast-IP is 10.187.212.63
Enter the NetMask for CACU
Enter NetMask for CACU
255.255.255.192
The updated Netmask value is 255.255.255.192

Chapter 4.
Enter the IP Offset for Usable IP

Enter Offset for Starting IP range, Default will be 0
0
The Updated Number of IP start offset is 0
Enter the System Name to be used in NGEMS Manager
Enter System Name For Agent Configuration
CACU_NUH
The Updated System Name is CACU_NUH
Enter the Region
Enter Region Code
North_HA_1267
The Updated Region Code is North_HA_1267
Enter the Number of NGEMS Manager
Enter Number of EMS Managers, Default will be 1
4
The Updated Number of EMS Managers is 4
Enter the IP Addresses for NGEMS Manager 1 to Number of Managers [ Entered value is 4]
The Number of NGEMS Manager is 4
The NGEMS Manager IPs will be Entered Sequentially
First 2 IP Addresses for PR and the next 2 IP Addresses for GR NGEMS Managers
10.187.0.39
Entered value NGEMS Manager 1 [ PR 1 ] IP Address is 10.187.0.39
10.187.0.40
Entered value for NGEMS Manager 2[PR 2 ]IP Address is 10.187.0.40
10.187.1.167
10.187.1.168
The updated NGEMS Manager IP(s) is/are
66 C-DOT MAX-NG

Enter the Number of NGSM
Enter Number of NGSM, Default will be 4
4
The Updated Number of NGSM is 4
Enter the IP Addresses for NGSM Manager 1 to Number of NGSM Managers [ Entered value is
4]
The Number of NGSM is 4
The NGSM IP Addresses will be Entered Sequentially
First 2 IP Addresses for PR and the next 2 IP Addresses for GR NGSMs
10.187.0.22
10.187.0.23
10.187.1.150
10.187.1.151
The updated NGSM IP(s) is/are
Enter the IP of the NTP Server
Enter NTP Server IP

Chapter 4.
10.187.4.12
The updated NTP server IP is 10.187.4.12
Enter the Periodicity to sync with NTP server (in seconds)
Enter Periodicity for syncing with NTP Server, Default will be 600 (Value will be in seconds)
900
The Updated NTP periodicity (in seconds) is 900
Note: The above IP address, ports, system name, etc. are just an indicative example and the actual entries must
be entered according to the field data. The IPs may change as this will depend on PR and GR configuration.
45) Now the user is displayed the values that have been entered so far and is asked whether these values
have to be changed (eg in case of some discrepancy)
The conf file created is as follows:

Note 1: The values marked as <blank> are just for display, they will not be sent to card.
Note 2: In case of Configuration 2 Entries corresponding to NGSM will not be used, even if
present.
Configuration File is present with values:

[1] Configuration Type for CACU: 1
[2] Start IP of the CACU range: 10.187.212.2
[3] End IP of the CACU range: 10.187.212.25
[4] Gateway IP for CACU: 10.187.212.4
[5] Broadcast IP for CACU: 10.187.212.63
[6] NetMask: 255.255.255.192
[7] Offest to Start usable IP: 0
[8] System Name used for EMS: CACU_NUH
[9] Region Name to be used in EMS: North_HA_1267
[10] Number of EMS Managers: 4
[11] IP Address of EMS Manager1: 10.187.0.39
[12] Number of NGSM: 4
[13] IP Address of NGSM 1: 10.187.0.22
68 C-DOT MAX-NG

[14] IP Address of the NTP server: 10.187.4.12
[15] Periodicity to sync with NTP server (In Seconds): 900
[0] To Proceed
Enter the option corresponding to the value to be changed
0
To change any value, enter the number corresponding to it, such as to change the NGEMS Region Name, enter 9.
To proceed (without changing these entries or after changing particular entry), enter 0.
46) After this the script asks whether the IP addresses on the CACU cards have been updated, this
should be confirmed by entering ‘Y’ if the steps in the prerequisites have been completed, else, the
script should be exited and the IP addresses should be assigned to the cards.
********
The physical card IPs for CACU chassis are:
MLS1 = 10.187.212.4
MLS2 = 10.187.212.7
SLM1 = 10.187.212.9
SLM2 = 10.187.212.10
EBM1 = 10.187.212.11
EBM2 = 10.187.212.12
NGTJ1 = 10.187.212.13
NGTJ2 = 10.187.212.19
********
Above IPs present at /home/Ubuntu/CACU_SOURCE/physical_ip_list.txt for reference
Please make sure these values are assigned as card IPs,

Enter (y/Y) to confirm or 0 to exit installation and assign IPs to cards
y

Chapter 4.
47) Once done that is ‘Y’ has been entered to confirm and proceed, the script will ask the following
option:

[1] For Installation and Configuration
[2] For Installation Only (No Configuration Changes)
[3] For Configuration Only (No Release Installation)
[0] To Exit without Installation
Select your option
1
During the field migration installation of the CACU for the first time, the user should select the option 1, that is
for installation and configuration.
48) After this step, the script prompts for the card on which the installation has to be done, through a
following menu:
Select Card Type:
[1] For SLM
[2] For NGTJ
[3] For EBM
[0] To Exit
Enter Your Option

The user should select each of the cards,that is for the SLM, NGTJ and EBM cards one by one as the script
returns to ask for this input again. Once a card type is selected, the script will proceed with that card and after
the installation is complete on that card, the script will present the same menu for the other cards.
49) After any card type is selected, the user will be prompted for the IP address of the card to be
confirmed and then some other input parameters for the cards. For SLM card, the script will also
ask if the setup is in a simplex or duplex SLM configuration.
Installation For SLM Selected
Is the system in Duplex (Y/y) or Simplex(Press Enter)

y
50) Now, when the user enters an IP address, here 10.187.1.5 is an example, the ssh prompt is shown,
something similar to the following:

70 C-DOT MAX-NG
RSA key fingerprint is c9:66:1f:4e:6e:b9:c9:c3:cc:46:4c:44:1b:56:ad:1e.

In the above example, 10.187.1.5 is the IP address of the CACU card on which installation is being done and
c9:66:1f:4e:6e:b9:c9:c3:cc:46:4c:44:1b:56:ad:1e is the ssh RSA key for that particular CACU card (SLM/EBM
or NGTJ). These two values will be different for every card depending upon the site.
51) This will display an output as the following and ask for the password for the root user of CACU
card (SLM/EBM/NGTJ) on which the installation option has been selected :
hosts.
Now try logging into the machine, with "ssh 'root@10.187.1.5'", and
check in:

expecting.
NOTE: This “warning” is not actually an error or a warning and should be ignored.
52) During the installation of the SLM cards, some prints would be shown related to file transfer and
file creation. One input will be asked related to the secure connection between the active and stand-
by SLM cards, which will be something similar to the following:
******************************************************
* ssh key file not present on this system

* You will have to press enter thrice in a row
******************************************************
Here, the user will be have to press the Enter key thrice for the secure key creation.

Chapter 4.
53) Once the installation is finished on the SLM cards (simplex or duplex), the script will show the
following output
ssh: : Temporary failure in name resolution

Selected Operation Completed.
NOTE: This temporary failure is not an error or a failure, but is shown because the entry of that particular SLM
card was not yet present in the DNS. This should be ignored.
54) Now the user will again presented the main menu of the script and the user should select the
application release installation for other CACU card, say NGTJ card.

Select Card Type:
[1] For SLM
[2] For NGTJ
[3] For EBM
[0] To Exit
Enter Your Option
2
Installation for NGTJ Selected
55) Again the IP address of the NGTJ card will be asked and output similar to steps 15 and 16 will be
presented. Such warnings are to be ignored The output will be similar to as follows:
Enter IP Address of NGTJ

10.187.212.13
Creating Connection for User: root to the Card (10.187.212.13)

RSA key fingerprint is ba:7f:2f:86:f5:6f:92:d8:05:7c:db:2e:65:df:07:dc.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '10.187.212.13' (RSA) to the list of known hosts.
Now try logging into the machine, with "ssh 'root@10.187.212.13'", and check in:
72 C-DOT MAX-NG
to make sure we haven't added extra keys that you weren't expecting.
Here, the IP address 10.187.212.13 is the example IP address of the CACU NGTJ card.
56) Now the operator is presented with some information regarding the NGTJ card OS release version
and the FPGA version. When asked to continue with the installation, the operator should enter ‘y’.
NGTJ release on NGTJ 10.187.212.13 is 1.52 and Control FPGA version is 21 on (NGTJ)
NGTJ @ 10.187.212.13 has 72% free space left
Do you want to continue? (Y/y to continue, Press Enter to exit)
y
You have selected to Continue with the installation
57) Once the initial I2C driver related installation is done on the NGTJ card, a welcome message is
displayed to the operator, that looks similar to:
@@@@@@@@@@ @@@@@
@@@@@@@@@@ @@@@@
@@@@@@@@@@ @@@@@
@@@@@
@@@@@ @@@@@
@@@@@ @@@@@
@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@
C-DOT
At the end of this text it asks whether the operator wants to continue with the installation and to modify the
‘default input’ file. The operator should continue (y) with the installation and should not modify the ‘default
input’ file. The screen output is:
:-continue?:-: :Want to continue with installation ?[ [n]/y ]: y
Here, ‘y’ should be entered to proceed with the installation.

Chapter 4.
58) Upon continuing with the installation of the CACU NGTJ card, some other inputs will also be taken
from the user. These include the C5 server IP address, C4 server IP address, whether to enable a
particular gateway on the NGJT card and likewise. The output is shown as follows:
Want to install 'ALL NGTJ APPLICATION softwares' ?[n/y]: y
Want enable to run v5ag after installation?[n/y]: y
Want enable to run priag after installation?[n/y]: y
Want enable to run tmg after installation?[n/y]: y
Want enable to run sgl2_start after installation?[n/y]: y

::install (y,y,y,y,y)=--==> enable(y y y y)
Here the operator should select ‘y’ installing a particular gateway on the NGTJ card and for enabling particular
gateway according to the site (as shown in the example above).
59) Once the above fields are entered, some configuration entries will be asked from the operator, such as the IP
addresses of the C5 and C4 servers, enabling PR/DR feature configuration, domain name, IP addresses of the
nameservers, domain name of the sbc etc. (r may be pressed in a later installation when these values are known
to be present already, but for the first time site migration configuration, the values should be entered according
to the site. r is for repeating and using the value being shown). The output shown is as follows:
: 'Want to enable PR/GR feature' ?[n/y]: y
Note: 'r' means the indicated value is correct
[120s] [1/3]:: INPUT THE VALUE OF DOMAIN NAME: maxng.bsnl.in [r]: maxng.bsnl.in
[120s] [1/3]:: INPUT THE VALUE OF nameserver [SBC] of PR: 192.168.149.118 [r]: 10.187.1.12
[120s] [1/3]:: INPUT THE VALUE OF nameserver [SBC] of GR: 192.168.109.183 [r]:
10.187.0.140
[120s] [1/3]:: INPUT THE VALUE OF DOMAIN NAME of 'sbc': sbc.maxng.bsnl.in [r]:
ggnsbc.maxng.bsnl.in
74 C-DOT MAX-NG
[120s] [1/3]:: Input 'P.R.' Floating Ip Of C4 (Primary_mgc): 192.168.103.159 [r]: 10.187.0.29
[120s] [1/3]:: Input 'G.R.' Floating Ip Of C4 (Secondary_mgc): 192.168.119.224 [r]: 10.187.1.157
In the example above, '10.187.212.13' is NGTJ card IP address.

10.187.0.29 is the ’P.R.’ Floating IP of C4 server, whereas 10.187.1.157 is the ‘G.R.’ Floating IP of C4
server.
60) Alternatively, if the operator does not want to configure the DR feature, the C5 IP address is asked as well
and the entries related to the domain name are not asked. The output shown is as follows, when the DR feature is
not configured:
Want to install 'Want to enable PR/GR feature' ?[n/y]: y
[120s] [1/3]:: INPUT THE VALUE OF C5: 196.1.106.100 [r]: 10.187.1.143
[120s] [1/3]:: Input The Value Of Primary C4: 192.168.103.159 [r]:

10.187.1.157
In the example above, the DR feature was enabled selecting ‘n’,'10.187.1.143' is the C5 server IP address
and 10.187.1.143 is the C4 server IP address. Here Gurugram site is PR site and Chandigarh is GR site.
61) After these values are provided by the operator, the values are confirmed and the operator is asked
whether to proceed with the installation. ‘y’ should be entered to proceed/re-confirm proceeding
with the installation.
Press y to continue or n to modify above inputs? [ y/n ]: y
Verify these input values

prcd?(y)
[41s]:Want to proceed with these input values...[n/y]: y
62) In case the operator opts to not proceed with the installation, the options presented by the script are

Chapter 4.
continue:Want to continue with installation ?[ [n]/y ]: n
: Want to continue installation?: :Press 'y' to Confirm , : 'n' no, I want to exit ... n
63) When the installation option is selected (Point 26), a list of the files to be installed on the NGTJ
card is shown and the file transfer to the NGTJ card starts, where you will be prompted to enter ‘y’
in intervals.
64) Once the installation step reaches the SG installation, it also asks for some inputs, related to the SG
server and PR-GR configuration.
The output is similar to the following and the user should enter the values asked:
Please wait... Processing.....
Enter Domain Name of SG : sgppp
Please wait.... SG tarball is processing.....

Enter PR SGP SERVER VIRTUAL_IP : 10.187.0.35
Enter PR SGP SERVER Bcast_ipAddr : 10.187.0.127
Enter GR SGP SERVER VIRTUAL_IP : 10.187.1.163

Enter GR SGP SERVER NodeId1 Bcast_ipAddr : 10.187.1.255
Please wait, Processing...
please wait... Building tarball for CACU : ngtj
Please wait....Installation in progress ..

76 C-DOT MAX-NG
Sat Sep 23 15:06:10 IST 2017
Installing stk_sgl2 ........

stk_sgl2 installed ...
65) The installation for SGL2 starts after this and when the SGL2 installation is finished, a following
message is displayed:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
!!!! 10.187.212.21 :sgl2 installed sucessfully!!!!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
66) When the installation of release is completed on the NGTJ card, the NGEMS agent installation on
the NGTJ card, per gateway is asked, and the user should enter ‘y’ according to the gateways
installed on the CACU NGTJ card. An example output is:
Agent directory created on NGTJ card...

Do you want to install NGTJ card EMS Agent? (y/Y) or Enter to skip
y
In the above example, the NGTJ card Agent has been selected for installation and the user has selected y.
Similarly for other Agents, such as PRI EMS GatewayAgent , V5 EMS Gateway Agent and SG EMS Gateway
Agent, whichever is applicable, y should be entered to installed otherwise, only Enter should be pressed to skip a
particular gateway agent installation.
67) Finally when the installation is complete on the NGTJ card the NGTJ card must be given a
command to reboot:
NGTJ Card needs to go for a reboot now ...

Do you want to reboot NGTJ card now? (y/Y) or Enter to skip
y

Chapter 4.
reboot_ngtj.sh
100% 43 0.0KB/s 00:00
NGTJ card going for a Reboot now ...
68) Once the installation is completed on the NGTJ card , the script returns to the main menu as the
follows and the installation for EBM card should be selected after this

Select Card Type:
[1] For SLM
[2] For NGTJ
[3] For EBM
[0] To Exit
Enter Your Option
3
69) Finally when all the installation is completed on the CACU cards and the option to exit the script is
selected, the output is shown as
Select Card Type:
[1] For SLM
[2] For NGTJ
[3] For EBM
[0] To Exit
Enter Your Option
0
OPERATION COMPLETED.
70) The estimated installation time for the cards is as follows:

d. SLM cards: 5 – 8 minutes
e. NGTJ cards: 8 – 15 minutes
f. EBM cards: 3 – 5 minutes
The above timing varies upon the space available and performance of the thin-client/PC being used for
installation, and the connection speed between the CACU cards and the thin-client/PC.
78 C-DOT MAX-NG
Appendix-O
(PREREQUISITES FOR INSTALLATION & CONFIGURATION AT SITE)
1. Please follow instructions and steps
mentioned in this MAX-NG Migration manual
otherwise it is difficult to start from
first step because all activities are depend
on each and if we will not follow sequence
then problems may come.
2. Take IP list of concerned SDCA and Core
setup (in PR/GR configuration) before
proceeding for installation & configuration
from MAX-NG Project management portal.
3. Before installation, it is very mandatory to
note old IP segement of CACU cards prepared
& delivered by manufacturer.In SLM card,EBM
card IP can be seen through ifconfig
command. But in NGTJ card,card will be
accessed only through Ethernet connection
and ssh command.Give command ssh
root@192.168.101.21 for setup number 1 but
102.21,103.21,….,192.168.108.21 for setup
number 2,3,4,5,6,7,8. For 5th setup number,
IP will be 192.168.105.21 and 192.168.105.27
for second NGTJ card.Please note the IP
segment of cards prepared by manufacturer
(ECIL/BEL). The segment may be
192.168.101.8,192.168.102.8,192.168.103.8,19
2.168.104.8,192.168.105.8,192.168.106.8,192.
168.107.8,192.168.108.8 depending on setup
number. This was for setup number 1. For
setup number 2 IPs will be 192.168.102.8,The
total number of setups prepared by
manufacturer at a time is 8. Therefore
192.168.10x.xx will be the segment of cards
where 10x may vary from 101 to 108. IP of
CACU cards considering setup number 1 may
be as follows:
SLM- 192.168.101.16 (FVIP) ,SLM1-
192.168.101.17,SLM2-192.168.101.18
NGTJ1 – 192.168.101.21,
NGTJ2 – 192.168.101.27,
EBM1- - 192.168.101.19
EBM2 – 192.168.101.20
MLS1 – 192.168.101.12
MLS2 – 192.168.101.15

Chapter 4.
4. CACU chassis must be mounted and powered ON

in identified BM.
5. Shutdown all processes of all cards i.e.
SLM1,SLM2,NGTJ1,NGTJ2,EBM1,EBM2. Configure
MLS1 and MLS2 after assigning new IP segment
to SLM1,SLM2,NGTJ1,NGTJ2,EBM1,EBM2
cards.Then only configure MLS1 and MLS2.
6. Before connecting Uplink to MLS1 and MLS2
card, it is mandatory to assign MAC address
to MLS cards delivered by ECIL manufacturer
only.For MAC address of particular site,
please follow google drive link and
carefully search specific site and
corresponding MAC address.
The same can be taken from below google drive link.Just copy and paste link in Web Browser.
https://drive.google.com/file/d/19_OKTGc356k961l0_px4BsrVt8Ho738c/view?usp=sharing
https://drive.google.com/file/d/1BKBYuekzRflv3UxwVkh6qA35XgwXt1Zl/view?usp=sharing
For assigning MAC address,please follow

Appendix-B.
7. Both Uplinks Uplink1 and Uplink 2 must be

ready before actual migration at T-7 days.
8. ITPC need to be informed at-least 2 working

days in advance so that migration at Clarity
may be planned accordingly.
9. Scripts for data creation in core and access

network must be ready at T-2 day. At same
time, software for LAGU and CACU System must
be ready at T-7 days.
10. Differential data from T-7 to T-2 data must

be ready at T-1 day where T is the actual
data of migration.
11. Scripts for data creation in core and access

must run at T-1 day and core administrator
80 C-DOT MAX-NG
must transfer file via ftp in Thin Client at

/home/cdot location.Core Administrator will
intimate access incharge/migration team.
Access Incharge/migration team will
acknowledge same.
12. InCACU BM, 2-slot chassis needs to be

mounted in which NGTJ cards for access sites
are prepared and checked with spare number.
Therefore, each NGTJ card, 2-slot chassis
hardware wise will be checked.
13. ThinClient machine must be configured and

installed to access CACU cards through
minicom and Ethernet connection. For minicom
connection, minicom ports are available at
the rear end of CACU chassis. For Ethernet
connection, prepare one Ethernet cable
before starting migration activity. Take the
length of Ethernet cable after measuring
distance of spare identified BM for
migration and Thin Client PC. Ethernet
ports 7A and 8A are available at the rear
end of CACU chassis. For setting up Minicom
connection, steps are given in next point.
14. Minicomdevice specified in the document

refer to 9 pin serial to USB convertor. One
long cable having USB connector will be
connected to Thin Client PC and 9 pin
connector will be connected to minicom cable
connected to CACU chassis delivered at site.
In 9 pin connector , 9 pin connector male
type connector will be connected to female
type connector of minicom cable. On other
side of cable , minicom USB serial connector
will be physically connected to USB port of
Thin Client PC.
15. Connect3-pin connector of minicom cable to

minicom port of CACU chassis. Out of 3
minicom ports, minicom port at the top one

Chapter 4.
will be used in each of the card as shown in

the Video. For SLM card slots, upper one is
for accessing copy-1 of SLM card and lower
one for copy-0 of SLM card. From front end,
copy-0 and copy-1 are left sided and right
sided copies. After connecting minicom cable
to minicom port follow these steps :
Connect the USB interface of the minicom device with any free USB port of the thin-
client. After this, configure the minicom settings using the following steps and command will be
given without #:
#su - root
#ls -lrt /dev/*tty*
Note the last entry, it should be similar to something such as:
crw-rw---- 1 root dialout <some no.>, 0 <date> <time> /dev/ttyUSB0
Note the last entry that may be /dev/ttyUSB0 or /dev/ttyUSB1 etc depending upon the
USB port used.
#minicom - s
It will ask Change Which Setting and present a menu list.
Go to the option ‘Serial Port Setup’ and press Enter.
In the input menu, press ‘A’ to edit the Serial Device to a value noted in the point b/c
above and press Enter to save it.
Set the option E, Bps/Par/Bits to 115200 8N1 if not set already.
Set option F, Hardware Flow Control to No.
Set the option G, Software Flow Control to No.
Press Enter to go back to the previous menu.
In this menu, go to the option Save Setup as dfl and press Enter. This will save the
settings made in the steps g through j. A message Configuration Saved will be
displayed.
Go to the Second Last option, Exit and press Enter. This exits from the Menu and
launches the minicom.
Note: In case the USB port is changed for the minicom, steps b to g must be
repeated.
16. ForEthernet connection, prepare one Ethernet cable which is to be

connected to 7th slot MLS card and Thin Client PC. Assign IP
Address to Thin Client PC.
82 C-DOT MAX-NG
Configure the thin client machine IP address settings as per the IP address available in the IP
ADDRESS DETAILS mentioned as “Terminal (Thin Client) IP” (in Appendix – A) using the
following steps:
 su - root
 #vi /etc/network/interfaces
 Type 100dd
 Press ‘i’ to enter into the insert mode in the editor and type the following (while replacing the
fields inside < > with the actual values):
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address <IP address of the thin client>
netmask <Netmask of the thin client>
network <Network address of the thin client>
broadcast <Broadcast IP address for the thin client>
gateway <Management IP Address of the MLS-1 card>
 Press the ‘Esc’ key to exit out of the insert mode of the editor and type ‘:wq’. After this,
press the Enter key.
 Now bring the network interface up using the command:
#ifconfig eth0 up
 Confirm the settings done above using the command ‘/sbin/ifconfig’ on the terminal
window and after that, ping the gateway IP address, that is the IP address of the MLS card-0,
using the command ‘ping <IP address of the MLS-1 card>’ in the terminal window.
17. Thin Client must be configured as tftp server and please follow
below steps and are as follows:
Copy the relevant drivers at the /var/lib/tftpboot/ path:

(Please enter the Ubuntu user password when prompted)
 # cd /home/ubuntu/MISC
 # sudo dpkg -i tftpd-hpa_5.0-11ubuntu2.1_armel.deb
 # sudo cp tftp /etc/xinetd.d/
 # sudo cp NGTJ.u-boot.bin.VER53 /var/lib/tftpboot/
 # sudo cp NGTJ.dtb.VER53 /var/lib/tftpboot/

Chapter 4.
Note: In case of space issue over the Thin Client machine; check with
the following command for presence of large size files (say more than
100 MB)
Command: find / -size +100M
And then remove unwanted files to create space.
Command: rm –rf /root/Desktop/CACU ( just as an example)

In the above example, we are removing CACU folder.
Just copy complete path of files/folders/directories/tar files shown in find

/ -size +100M command and check space by df –h command. Percentage will be
shown on extreme right side of each one. For example of mtdblock0, mmc.
mtdblock0 is jffs2_ram and mtdblock3 or mmc is NAND FLASH memory.
Command: df –h
After this, your Thin Client is ready for installation and

configuration in CACU cards.
84 C-DOT MAX-NG
SETUP MINICOM (IN P.C)
Following points is used to setup Minicom in PC:
 Connect RS232 cable from NGTJ card to PC using serial cable.
 Open the Terminal in PC
 [root@ajay ~]# minicom -s
 Select serial port setup and press enter

Chapter 4.
 Select all the settings as shown in the picture.
 NOTE :- 1.If RS232 port is used to start minicom then use /dev/ttyS0 or /dev/ttyS1
2. If Serial converter (RS232 to USB) is used to start minicom then use
/dev/ttyUSB0 or /dev/ttyUSB1
3. Baud rate to be given for NGTJ is 115200.
86 C-DOT MAX-NG
Appendix-P
Zone wise Circle Distribution for PAN INDIA
ZONE WISE CIRCLE DISTRIBUTION
Zone Core Site Location Circle
Gurgaon UP East, UP West, Haryana, Jammu & Kashmir

North
Chandigarh Rajasthan, Uttarakhand, Punjab, Himachal Pradesh
Cuttack Bihar, Orissa, Jharkhand

East
Kolkata, West Bengal, NE1, NE2, Andaman & Nicobar,
Kolkata
Assam
Pune Maharashtra, Chhattisgarh

West
Bhopal Madhya Pradesh, Gujrat
Bengaluru Karnataka, Tamil Nadu

South
Hyderabad Andhra Pradesh, Kerala

Chapter 4.
Appendix-Q
Note: Please verify IP Address list of core site with IP list in MAX-NG Project Rollout
Management portal.
Note 1: IP list of respective core site can also be taken from MAX-NG Project
Rollout Management portal.
Note 2: Only Core IP segment of core sites will change .Rest IP will remain
same. For example, SBC IP of Gurugram site (PR) is 10.187.0.12 while SBC IP
of Chandigarh (PR) will be 10.187.1.12, SBC IP of Chandigarh site is
10.187.1.12, of Cuttack is 10.187.3.12, of Pune, Bhopal is 10.187.5.12 and
10.187.4.12, Bangalore and Hyderabad is 10.187.6.12, 10.187.7.12. The .1, .2,
.3, .4, .5, .6, .7 is changing while rest 10.187.x. 12 will remain same for all sites.
In above table, IP range defines the IP segment for respective core site. For
GR site, 10.187.1.140 is IP of SBC (GR).
88 C-DOT MAX-NG
For
Self-Copy Chassis 1
BANGALORE

Chapter 4.
BLADE 1 BLADE 2 BLADE 3 BLADE 4 BLADE 5 BLADE 6
BLRPRSBCC0 BLRPRC5C0 BLRPRRATERC0 BLRPRDBC0 BLRPRSPSC0 SPARE

SERV
10.187.6.10 10.187.6.13 10.187.6.16 10.187.6.19 10.187.6.22
ER
BLRPRSBCC1 BLRPRC5C1 BLRPRRATERC1 BLRPRDBC1 BLRPRSPSC1 SPARE

SERV
10.187.6.11 10.187.6.14 10.187.6.17 10.187.6.20 10.187.6.23
ER
SELF-COPY CHASSIS 2
BLRPRC4C0 BLRPRINSSPC0 BLRPRSGC0 BLRPRLISC0 BLRPRNGEMSC0 SPARE

SER
10.187.6.27 10.187.6.30 10.187.6.33 10.187.6.36 10.187.6.39
VER
BLRPRC4C1 BLRPRINSSPC1 BLRPRSGC1 BLRPRLISC1 BLRPRNGEMSC1 SPARE

SER
10.187.6.28 10.187.6.31 10.187.6.34 10.187.6.37 10.187.6.40
VER
MATE COPY CHASSIS 1
HYDDRSBCC0 HYDDRC5C0 HYDDRRATERC0 HYDDRDBC0 HYDDRSPSC0 SPARE

SER
10.187.6.44 10.187.6.47 10.187.6.50 10.187.6.53 10.187.6.56
VE
R
90 C-DOT MAX-NG
HYDDRSBCC1 HYDDRC5C1 HYDDRRATERC1 HYDDRDBC1 HYDDRSPSC1 SPARE

SER
10.187.6.45 10.187.6.48 10.187.6.51 10.187.6.54 10.187.6.57
VE
R
MATE COPY CHASSIS 2
HYDDRC4C0 HYDDRINSSPC0 HYDDRSGC0 HYDDRLISC0 HYDDRNGEMSC0 SPARE

SE
10.187.6.61 10.187.6.64 10.187.6.67 10.187.6.70 10.187.6.73
R
V
BLADE 9 BLADE 10 BLADE 11 BLADE 12 BLADE 13 BLADEER
14
HYDDRC4C1 HYDDRINSSPC1 HYDDRSGC1 HYDDRLISC1 HYDDRNGEMSC1 SPARE
SE
10.187.6.62 10.187.6.65 10.187.6.68 10.187.6.71 10.187.6.74
R
V
ER
DNS:- MAXNG.BSNL.IN
IP Range: (10.187.6.0/24) Default Gateway: 10.187.6.2
Self Copy
Application Mod. ID Host Name Chassis ID Server IP Address Remarks
ID
Session BLR_SELF_SBC_1 blrprsbcc0 BLR_01 01 10.187.6.10 Copy 0 Bangaluru Self SBC
Border
Controller BLR_SELF_SBC_2 blrprsbcc1 BLR_01 09 10.187.6.11 Copy 1 Bangaluru Self SBC
BLR_SELF_SBC blrprsbc BLR_01 Floating IP Bangaluru Self
10.187.6.12
SBC.
Class 5 BLR_SELF_C5_1 blrprc5c0 BLR_01 02 Copy 0 Bangaluru Self C5
10.187.6.13
Subscriber SS
Server
BLR_SELF_C5_2 blrprc5c1 BLR_01 10 Copy 1 Bangaluru Self C5
10.187.6.14
SS
BLR_SELF_C5 blrprc5 BLR_01 Floating IP Bangaluru Self
10.187.6.15
C5.
Rating and BLR_SELF_RTR_1 blrprraterc0 BLR_01 03 Copy 0 Bangaluru Self
10.187.6.16
Charging Rating Server

Chapter 4.

ID
Server BLR_SELF_RTR_2 blrprraterc1 BLR_01 11 Copy 1 Bangaluru Self
10.187.6.17
Rating Server
BLR_SELF_RTR blrprrater BLR_01 Floating IP of Bangaluru
10.187.6.18
Self Rating Server
Database BLR_SELF_DB_1 blrprdbc0 BLR_01 04 Copy 0 Bangaluru Self DB
10.187.6.19
Server Server
BLR_SELF_DB_2 blrprdbc1 BLR_01 12 Copy 1 Bangaluru Self DB
10.187.6.20
Server
BLR_SELF_DB blrprdb BLR_01 Floating IP of Bangaluru
10.187.6.21
Self DB Server
Subscriber BLR_SELF_PROV_1 blrprspsc0 BLR_01 05 Copy 0 Bangaluru Self Prov.
10.187.6.22
Provisioning Server
Server
BLR_SELF_PROV_2 blrprspsc1 BLR_01 13 Copy 1 Bangaluru Self Prov.
10.187.6.23
Server
BLR_SELF_PROV blrprsps BLR_01 Floating IP of Bangaluru
10.187.6.24
Self Prov. Server
Spare Server BLR_01 06
Class 4 BLR_SELF_C4_1 blrprc4c0 BLR_02 01 Copy 0 Bangaluru Self C4
10.187.6.27
Trunking SS
Server
BLR_SELF_C4_2 blrprc4c1 BLR_02 09 Copy 1 Bangaluru Self C4
10.187.6.28
SS
BLR_SELF_C4 blrprc4 BLR_02 Floating IP Bangaluru Self
10.187.6.29
C4.
IN Service BLR_SELF_SSP_1 blrprinsspc0 BLR_02 02 10.187.6.30 Copy 0 Bangaluru Self SSP
Switching
Point BLR_SELF_SSP_2 blrprinsspc1 BLR_02 10 10.187.6.31 Copy 1 Bangaluru Self SSP
BLR_SELF_SSP blrprinssp BLR_02 Floating IP Bangaluru Self
10.187.6.32
SSP
SIGTARN BLR_SELF_SIG_1 blrprsgc0 BLR_02 03 Copy 0 Bangaluru Self Sig.
10.187.6.33
Signaling Server
Gateway
Server BLR_SELF_SIG_2 blrprsgc1 BLR_02 11 Copy 1 Bangaluru Self Sig.
10.187.6.34
Server
BLR_SELF_SIG blrprsg BLR_02 Floating IP of Bangaluru
10.187.6.35
Self Sig. Server
Lawful BLR_SELF_LIS_1 blrprlisc0 BLR_02 04 10.187.6.36 Copy 0 Bangaluru Self LIS
Interception
Server BLR_SELF_LIS_2 blrprlisc1 BLR_02 12 10.187.6.37 Copy 1 Bangaluru Self LIS
BLR_SELF_LIS blrprlis BLR_02 Floating IP of Bangaluru
10.187.6.38
Self LIS
Next BLR_SELF_NGEMS_ blrprngemsc0 BLR_02 05 10.187.6.39 Copy 0 Bangaluru Self
92 C-DOT MAX-NG

ID
Generation 1 NGEMS
EMS
BLR_SELF_NGEMS_ blrprngemsc1 BLR_02 13 Copy 1 Bangaluru Self
10.187.6.40
2 NGEMS
BLR_SELF_NGEMS blrprngems BLR_02 Floating IP of Bangaluru
10.187.6.41
Self NGEMS
Mate Copy
Application Mod. ID Host Name Chassis Server IP Address Remarks
ID ID
Session Border BLR_MATE_SBC_1 hyddrsbcc0 BLR_03 01 10.187.6.44 Copy 0 Bangaluru Mate SBC
Controller
BLR_MATE_SBC_2 hyddrsbcc1 BLR_03 02 10.187.6.45 Copy 1 Bangaluru Mate SBC
BLR_MATE_SBC hyddrsbcc0 BLR_03 Floating IP Bangaluru Mate
10.187.6.46
SBC.
Class 5 BLR_MATE_C5_1 hyddrc5c0 BLR_03 03 Copy 0 Bangaluru Mate C5
10.187.6.47
Subscriber SS
Server
BLR_MATE_C5_2 hyddrc5c1 BLR_03 04 Copy 1 Bangaluru Mate C5
10.187.6.48
SS
BLR_MATE_C5 hyddrc5 BLR_03 Floating IP Bangaluru Mate
10.187.6.49
C5.
Rating and BLR_MATE_RTR_1 hyddrraterc BLR_03 05 Copy 0 Bangaluru Mate
10.187.6.50
Charging 0 Rating Server
Server
BLR_MATE_RTR_2 hyddrraterc BLR_03 06 Copy 1 Bangaluru Mate
10.187.6.51
1 Rating Server
BLR_MATE_RTR hyddrrater BLR_03 Floating IP of Bangaluru
10.187.6.52
Mate Rating Server
Database BLR_MATE_DB_1 hyddrdbc0 BLR_03 07 Copy 0 Bangaluru Mate DB
10.187.6.53
Server Server
BLR_MATE_DB_2 hyddrdbc1 BLR_03 08 Copy 1 Bangaluru Mate DB
10.187.6.54
Server
BLR_MATE_DB hyddrdb BLR_03 Floating IP of Bangaluru
10.187.6.55
Mate DB Server
Subscriber GURSLE_PROV_1 hyddrspsc0 BLR_03 09 Copy 0 Bangaluru Mate Prov.
10.187.6.56
Provisioning Server

Chapter 4.

ID ID
Server BLR_MATE_PROV_2 hyddrspsc1 BLR_03 10 Copy 1 Bangaluru Mate Prov.
10.187.6.57
Server
BLR_MATE_PROV hyddrsps BLR_03 Floating IP of Bangaluru
10.187.6.58
Mate Prov. Server
Class 4 BLR_MATE_C4_1 hyddrc4c0 BLR_04 01 Copy 0 Bangaluru Mate C4
10.187.6.61
Trunking SS
Server
BLR_MATE_C4_2 hyddrc4c1 BLR_04 02 Copy 1 Bangaluru Mate C4
10.187.6.62
SS
BLR_MATE_C4 hyddrc4 BLR_04 Floating IP Bangaluru Mate
10.187.6.63
C4.
IN Service BLR_MATE_SSP_1 hyddrinsspc BLR_04 03 Copy 0 Bangaluru Mate SSP
10.187.6.64
Switching 0
Point
BLR_MATE_SSP_2 hyddrinsspc BLR_04 04 Copy 1 Bangaluru Mate SSP
10.187.6.65
1
BLR_MATE_SSP hyddrinssp BLR_04 Floating IP Bangaluru Mate
10.187.6.66
SSP
SIGTARN BLR_MATE_SIG_1 hyddrsgc0 BLR_04 05 Copy 0 Bangaluru Mate Sig.
10.187.6.67
Signaling Server
Gateway
Server BLR_MATE_SIG_2 hyddrsgc1 BLR_04 06 Copy 1 Bangaluru Mate Sig.
10.187.6.68
Server
BLR_MATE_SIG hyddrsg BLR_04 Floating IP of Bangaluru
10.187.6.69
Mate Sig. Server
Lawful BLR_MATE_LIS_1 hyddrlisc0 BLR_04 07 10.187.6.70 Copy 0 Bangaluru Mate LIS
Interception
Server BLR_MATE_LIS_2 hyddrlisc1 BLR_04 08 10.187.6.71 Copy 1 Bangaluru Mate LIS
BLR_MATE_LIS hyddrlis BLR_04 Floating IP of Bangaluru
10.187.6.72
Mate LIS
Next BLR_MATE_NGEMS hyddrngems BLR_04 09 Copy 0 Bangaluru Mate
10.187.6.73
Generation _1 c0 NGEMS
EMS
BLR_MATE_NGEMS hyddrngems BLR_04 10 Copy 1 Bangaluru Mate
10.187.6.74
_2 c1 NGEMS
BLR_MATE_NGEMS hyddrngems BLR_04 Floating IP of Bangaluru
10.187.6.75
Mate NGEMS
Spare IP Addresses (reserved):
94 C-DOT MAX-NG
10.187.6.25 to 10.187.6.26
10.187.6.42 to 10.187.6.43
10.187.6.59 to 10.187.6.60
10.187.6.76 to 10.187.6.79
Hardware Management IP of Server
Chassis ID Server ID Serial Number MAC Address IP Address

BLR_01 01 10.187.6.80
BLR_01 02 10.187.6.81
BLR_01 03 10.187.6.82
BLR_01 04 10.187.6.83
BLR_01 05 10.187.6.84
BLR_01 06 10.187.6.85
BLR_01 07 10.187.6.86
BLR_01 08 10.187.6.87
BLR_01 09 10.187.6.88
BLR_01 10 10.187.6.89
BLR_01 11 10.187.6.90
BLR_01 12 10.187.6.91
BLR_01_ILO1 OA1 10.187.6.92
BLR_01_ILO2 OA2 10.187.6.93
BLR_01_ILO3 SW1 10.187.6.94
BLR_01_ILO4 SW2 10.187.6.95
BLR_02 01 10.187.6.96
BLR_02 02 10.187.6.97
BLR_02 03 10.187.6.98
BLR_02 04 10.187.6.99

Chapter 4.
BLR_02 05 10.187.6.100
BLR_02 06 10.187.6.101
BLR_02 07 10.187.6.102
BLR_02 08 10.187.6.103
BLR_02 09 10.187.6.104
BLR_02 10 10.187.6.105
BLR_02 11 10.187.6.106
BLR_02 12 10.187.6.107
BLR_02_ILO1 OA1 10.187.6.108
BLR_02_ILO2 OA2 10.187.6.109
BLR_02_ILO3 SW1 10.187.6.110
BLR_02_ILO4 SW2 10.187.6.111
BLR_03 01 10.187.6.112
BLR_03 02 10.187.6.113
BLR_03 03 10.187.6.114
BLR_03 04 10.187.6.115
BLR_03 05 10.187.6.116
BLR_03 06 10.187.6.117
BLR_03 07 10.187.6.118
BLR_03 08 10.187.6.119
BLR_03 09 10.187.6.120
BLR_03 10 10.187.6.121
BLR_03 11 10.187.6.122
BLR_03 12 10.187.6.123
BLR_03_ILO1 OA1 10.187.6.124
BLR_03_ILO2 OA2 10.187.6.125
BLR_03_ILO3 SW1 10.187.6.126
BLR_03_ILO4 SW2 10.187.6.127
96 C-DOT MAX-NG
BLR_04 01 10.187.6.128
BLR_04 02 10.187.6.129
BLR_04 03 10.187.6.130
BLR_04 04 10.187.6.131
BLR_04 05 10.187.6.132
BLR_04 06 10.187.6.133
BLR_04 07 10.187.6.134
BLR_04 08 10.187.6.135
BLR_04 09 10.187.6.136
BLR_04 10 10.187.6.137
BLR_04 11 10.187.6.138
BLR_04 12 10.187.6.139
BLR_04_ILO1 OA1 10.187.6.140
BLR_04_ILO2 OA2 10.187.6.141
BLR_04_ILO3 SW1 10.187.6.142
BLR_04_ILO4 SW2 10.187.6.143
BLR_05_ILO1 OA1 10.187.6.144
BLR_05_ILO2 OA2 10.187.6.145
BLR_05_ILO3 SW1 10.187.6.146
BLR_05_ILO4 SW2 10.187.6.147

10.187.6.148 to 10.187.6.149
Other Core Elements IP
Device Name Device ID Serial Number MAC Address IP Address
Client Terminal BLR_CL1 10.187.6.150

Chapter 4.
1 (LED Panel)
2
3
4
5
Printer BLR_PRN1 10.187.6.155
IP Addresses (To be used for SIP Clients):

10.187.6.156 to 10.187.6.169
IP Addresses (To be used for Laptops):

10.187.6.170 to 10.187.6.179
Spare IP Addresses:
10.187.6.180 to 10.187.6.254
Note: IP list of respective core site can also be taken from MAX-NG Project Rollout
Management portal. Please crosscheck same before proceeding for installation.
Appendix-M
East Zone Core: CUTTACK (PRIMARY Site)
98 C-DOT MAX-NG
Updated On 22.08.2017
IP Range: (10.187.3.0/25) VLAN ID:
Default Gateway: 10.187.3.2

Network Address: 10.187.3.0 Broadcast Address: 10.187.3.127
Netmask: 255.255.255.128
Self PE Port (at Cuttack): eth0:

Adj. PE Port (at Cuttack): eth0:
DOMAIN NAME of MAX-NG North Zone (Self): @maxng.bsnl.in

DOMAIN NAME of MAX-NG North Zone (Mate): @maxng.bsnl.in
LAYER 3 SWITCH IP ADDRESS

LAN CTK_L3SW1_P 10.187.3.1
Switch_C0 0
LAN CTK_L3SW1_P 10.187.3.3
Switch_C0 1
LAN CTK_L3SW2_P 10.187.3.4
Switch_C1 0
LAN CTK_L3SW2_P 10.187.3.5
Switch_C1 1

Chapter 4.
10.187.3.6 to 10.187.3.9
SELF COPY
Chassis Server
Application Mod. ID IP Address Remarks
ID ID
CTK_SELF_SBC_1 CTK_01 1 10.187.3.10 Copy 0 Cuttack Self SBC
Session
CTK_SELF_SBC_2 CTK_01 2 10.187.3.11 Copy 1 Cuttack Self SBC
Border
Controller Floating IP Cuttack Self
CTK_SELF_SBC CTK_01 10.187.3.12
SBC.
CTK_SELF_C5_1 CTK_01 3 10.187.3.13 Copy 0 Cuttack Self C5 SS
Class 5
Subscriber
Server Floating IP Cuttack Self
CTK_SELF_C5 CTK_01 10.187.3.15
C5.
Copy 0 Cuttack Self
CTK_SELF_RTR_1 CTK_01 5 10.187.3.16
Rating Server
Rating and
Copy 1 Cuttack Self
Charging CTK_SELF_RTR_2 CTK_01 6 10.187.3.17
Rating Server
Server
Floating IP of Cuttack Self
CTK_SELF_RTR CTK_01 10.187.3.18
Rating Server
Copy 0 Cuttack Self DB
CTK_SELF_DB_1 CTK_01 7 10.187.3.19
Server
Database Copy 1 Cuttack Self DB
CTK_SELF_DB_2 CTK_01 8 10.187.3.20
Server Server
CTK_SELF_DB CTK_01 10.187.3.21
DB Server
Copy 0 Cuttack Self Prov.
CTK_SELF_PROV_1 CTK_01 9 10.187.3.22
Server
Subscriber
Copy 1 Cuttack Self Prov.
Provisioning CTK_SELF_PROV_2 CTK_01 10 10.187.3.23
Server
Server
CTK_SELF_PROV CTK_01 10.187.3.24
Prov. Server
Spare Server CTK_01 11
100 C-DOT MAX-NG


Class 4
Trunking
Server Floating IP Cuttack Self
CTK_SELF_C4 CTK_02 10.187.3.29
C4.
CTK_SELF_SSP_1 CTK_02 3 10.187.3.30 Copy 0 Cuttack Self SSP
IN Service
CTK_SELF_SSP_2 CTK_02 4 10.187.3.31 Copy 1 Cuttack Self SSP
Switching
Point Floating IP Cuttack Self
CTK_SELF_SSP CTK_02 10.187.3.32
SSP
Copy 0 Cuttack Self Sig.
CTK_SELF_SIG_1 CTK_02 5 10.187.3.33
Server
SIGTARN
Signaling Copy 1 Cuttack Self Sig.
CTK_SELF_SIG_2 CTK_02 6 10.187.3.34
Gateway Server
Server
CTK_SELF_SIG CTK_02 10.187.3.35
Sig. Server
CTK_SELF_LIS_1 CTK_02 7 10.187.3.36 Copy 0 Cuttack Self LIS
Lawful
CTK_SELF_LIS_2 CTK_02 8 10.187.3.37 Copy 1 Cuttack Self LIS
Interception
Server Floating IP of Cuttack Self
CTK_SELF_LIS CTK_02 10.187.3.38
LIS
CTK_SELF_NGEMS_ Copy 0 Cuttack Self
CTK_02 9 10.187.3.39
1 NGEMS
Next
CTK_SELF_NGEMS_ Copy 1 Cuttack Self
Generation CTK_02 10 10.187.3.40
2 NGEMS
EMS
CTK_SELF_NGEMS CTK_02 10.187.3.41
NGEMS

10.187.3.25 to 10.187.3.26
10.187.3.42 to 10.187.3.43

Chapter 4.

Client Terminal 16A098 10.187.3.44
CTK_CL1
1 (LED Panel)
CTK_CL2
2
CTK_CL3
3
CTK_CL4
4
CTK_CL5
5
Printer CTK_PRN1 PHBBV74604 10.187.3.49
Chassis ID Bay ID Serial Number MAC Address ILO IP Server IP

Address Address
CTK_01 1 10.187.3.80 10.187.3.10
CTK_01 2 10.187.3.81 10.187.3.13
CTK_01 3 10.187.3.82 10.187.3.16
CTK_01 4 10.187.3.83 10.187.3.19
CTK_01 5 10.187.3.84 10.187.3.22
CTK_01 6 10.187.3.85
CTK_01 9 10.187.3.86 10.187.3.11
CTK_01 10 10.187.3.87 10.187.3.14
CTK_01 11 10.187.3.88 10.187.3.17
CTK_01 12 10.187.3.89 10.187.3.20
CTK_01 13 10.187.3.90 10.187.3.23
102 C-DOT MAX-NG

CTK_01 14 10.187.3.91
CTK_01_ILO OA1
10.187.3.92
1
CTK_01_ILO OA2
10.187.3.93
2
CTK_01_ILO SW1
10.187.3.94
3
CTK_01_ILO SW2
10.187.3.95
4
CTK_02 1 10.187.3.96 10.187.3.27
CTK_02 2 10.187.3.97 10.187.3.30
CTK_02 3 10.187.3.98 10.187.3.33
CTK_02 4 10.187.3.99 10.187.3.36
CTK_02 5 10.187.3.100 10.187.3.39
CTK_02 6 10.187.3.101
CTK_02 9 10.187.3.102 10.187.3.28
CTK_02 10 10.187.3.103 10.187.3.31
CTK_02 11 10.187.3.104 10.187.3.34
CTK_02 12 10.187.3.105 10.187.3.37
CTK_02 13 10.187.3.106 10.187.3.40
CTK_02 14 10.187.3.107
CTK_02_ILO OA1
10.187.3.108
1
CTK_02_ILO OA2
10.187.3.109
2
CTK_02_ILO SW1
10.187.3.110
3
CTK_02_ILO SW2
10.187.3.111
4

Chapter 4.

10.187.3.50 to 10.187.3.65

10.187.3.66 to 10.187.3.79
Spare IP Addresses:
10.187.3.112 to 10.187.3.126
Note: IP list of respective core site can also be taken from MAX-NG Project Rollout
Management portal. Please crosscheck same before proceeding for installation.
East Zone Core: CUTTACK (MATE)
IP Range: (10.187.3.128/25) VLAN ID:
104 C-DOT MAX-NG


Netmask: 255.255.255.128



LAN CTK_L3SW1_P 10.187.3.129
Switch_C0 0
LAN CTK_L3SW1_P 10.187.3.131
Switch_C0 1
LAN CTK_L3SW2_P 10.187.3.132
Switch_C1 0
LAN CTK_L3SW2_P 10.187.3.133
Switch_C1 1

10.187.3.134 to 10.187.3.137
MATE COPY
Application Mod. ID Chassis Server IP Address Remarks

Chapter 4.
ID ID
Copy 0 Cuttack Mate
CTK_MATE_SBC_1 CTK_03 1 10.187.3.138
SBC
Session
Copy 1 Cuttack Mate
Border CTK_MATE_SBC_2 CTK_03 2 10.187.3.139
SBC
Controller
Floating IP Cuttack
CTK_MATE_SBC CTK_03 10.187.3.140
Mate SBC.
Copy 0 Cuttack Mate
CTK_MATE_C5_1 CTK_03 3 10.187.3.141
C5 SS
Class 5
Copy 1 Cuttack Mate
Subscriber CTK_MATE_C5_2 CTK_03 4 10.187.3.142
C5 SS
Server
Floating IP Cuttack
CTK_MATE_C5 CTK_03 10.187.3.143
Mate C5.
Copy 0 Cuttack Mate
CTK_MATE_RTR_1 CTK_03 5 10.187.3.144
Rating Server
Rating and
Copy 1 Cuttack Mate
Charging CTK_MATE_RTR_2 CTK_03 6 10.187.3.145
Rating Server
Server
Floating IP of Cuttack
CTK_MATE_RTR CTK_03 10.187.3.146
Mate Rating Server
Copy 0 Cuttack Mate
CTK_MATE_DB_1 CTK_03 7 10.187.3.147
DB Server
Database Copy 1 Cuttack Mate
CTK_MATE_DB_2 CTK_03 8 10.187.3.148
Server DB Server
CTK_MATE_DB CTK_03 10.187.3.149
Mate DB Server
Copy 0 Cuttack Mate
CTK_MATE_PROV_1 CTK_03 9 10.187.3.150
Prov. Server
Subscriber
Copy 1 Cuttack Mate
Provisioning CTK_MATE_PROV_2 CTK_03 10 10.187.3.151
Prov. Server
Server
CTK_MATE_PROV CTK_03 10.187.3.152
Mate Prov. Server
Class 4 CTK_MATE_C4_1 CTK_04 1 10.187.3.155 Copy 0 Cuttack Mate
106 C-DOT MAX-NG

Trunking C4 SS
Server
Copy 1 Cuttack Mate
CTK_MATE_C4_2 CTK_04 2 10.187.3.156
C4 SS
Floating IP Cuttack
CTK_MATE_C4 CTK_04 10.187.3.157
Mate C4.
Copy 0 Cuttack Mate
CTK_MATE_SSP_1 CTK_04 3 10.187.3.158
SSP
IN Service
Copy 1 Cuttack Mate
Switching CTK_MATE_SSP_2 CTK_04 4 10.187.3.159
SSP
Point
Floating IP Cuttack
CTK_MATE_SSP CTK_04 10.187.3.160
Mate SSP
Copy 0 Cuttack Mate
CTK_MATE_SIG_1 CTK_04 5 10.187.3.161
Sig. Server
SIGTARN
Signaling Copy 1 Cuttack Mate
CTK_MATE_SIG_2 CTK_04 6 10.187.3.162
Gateway Sig. Server
Server
CTK_MATE_SIG CTK_04 10.187.3.163
Mate Sig. Server
Copy 0 Cuttack Mate
CTK_MATE_LIS_1 CTK_04 7 10.187.3.164
LIS
Lawful
Copy 1 Cuttack Mate
Interception CTK_MATE_LIS_2 CTK_04 8 10.187.3.165
LIS
Server
CTK_MATE_LIS CTK_04 10.187.3.166
Mate LIS
CTK_MATE_NGEMS_ Copy 0 Cuttack Mate
CTK_04 9 10.187.3.167
1 NGEMS
Next
CTK_MATE_NGEMS_ Copy 1 Cuttack Mate
Generation CTK_04 10 10.187.3.168
2 NGEMS
EMS
CTK_MATE_NGEMS CTK_04 10.187.3.169
Mate NGEMS

10.187.3.153 to 10.187.3.154

Chapter 4.
10.187.3.170 to 10.187.3.171

Chassis ID Bay ID Serial Number MAC Address ILO IP Server IP
Address Address
CTK_03 1 10.187.3.208 10.187.3.138
CTK_03 2 10.187.3.209 10.187.3.141
CTK_03 3 10.187.3.210 10.187.3.144
CTK_03 4 10.187.3.211 10.187.3.147
CTK_03 5 10.187.3.212 10.187.3.150
CTK_03 6 10.187.3.213
CTK_03 9 10.187.3.214 10.187.3.139
CTK_03 10 10.187.3.215 10.187.3.142
CTK_03 11 10.187.3.216 10.187.3.145
CTK_03 12 10.187.3.217 10.187.3.148
CTK_03 13 10.187.3.218 10.187.3.151
CTK_03 14 10.187.3.219
CTK_03_ILO OA1
10.187.3.220
1
CTK_03_ILO OA2
10.187.3.221
2
CTK_03_ILO SW1
10.187.3.222
3
CTK_03_ILO SW2
10.187.3.223
4
CTK_04 1 10.187.3.224 10.187.3.155
CTK_04 2 10.187.3.225 10.187.3.158
CTK_04 3 10.187.3.226 10.187.3.161
CTK_04 4 10.187.3.227 10.187.3.164
CTK_04 5 10.187.3.228 10.187.3.167
108 C-DOT MAX-NG

CTK_04 6 10.187.3.229
CTK_04 9 10.187.3.230 10.187.3.156
CTK_04 10 10.187.3.231 10.187.3.159
CTK_04 11 10.187.3.232 10.187.3.162
CTK_04 12 10.187.3.233 10.187.3.165
CTK_04 13 10.187.3.234 10.187.3.168
CTK_04 14 10.187.3.235
CTK_04_ILO OA1
10.187.3.236
1
CTK_04_ILO OA2
10.187.3.237
2
CTK_04_ILO SW1
10.187.3.238
3
CTK_04_ILO SW2
10.187.3.239
4
CTK_05_ILO OA1
10.187.3.240
1
CTK_05_ILO OA2
10.187.3.241
2
CTK_05_ILO SW1
10.187.3.242
3
CTK_05_ILO SW2
10.187.3.243
4

10.187.3.172 to 10.187.3.192

10.187.3.193 to 10.187.3.207
Spare IP Addresses:
10.187.3.244 to 10.187.3.255

Chapter 4.
North Zone Core: CHANDIGARH (PRIMARY Site)

Self-Copy Chassis 1
110 C-DOT MAX-NG

CHDPRSBCC0 CHDPRC5C0 CHDPRRATERC0 CHDPRDBC0 CHDPRSPSC0 SPARE

SERV
10.187.1.10 10.187.1.13 10.187.1.16 10.187.1.19 10.187.1.22
ER
CHDPRSBCC1 CHDPRC5C1 CHDPRRATERC1 CHDPRDBC1 CHDPRSPSC1 SPARE

SERV
10.187.1.11 10.187.1.14 10.187.1.17 10.187.1.20 10.187.1.23
ER
SELF-COPY CHASSIS 2
CHDPRC4C0 CHDPRINSSPC0 CHDPRSGC0 CHDPRLISC0 CHDPRNGEMSC0 SPARE

SER
10.187.1.27 10.187.1.30 10.187.1.33 10.187.1.36 10.187.1.39
VE
R
CHDPRC4C1 CHDPRINSSPC1 CHDPRSGC1 CHDPRLISC1 CHDPRNGEMSC1 SPARE

SER
10.187.1.28 10.187.1.31 10.187.1.34 10.187.1.37 10.187.1.40
VE
R
MATE COPY CHASSIS 1
GGNDRSBCC0 GGNDRC5C0 GGNDRRATERC0 GGNDRDBC0 GGNDRSPSC0 SPARE

SER
10.187.1.44 10.187.1.47 10.187.1.50 10.187.1.53 10.187.1.56
VE
R

Chapter 4.
GGNDRSBCC1 GGNDRC5C1 GGNDRRATERC1 GGNDRDBC1 GGNDRSPSC1 SPARE

SER
10.187.1.45 10.187.1.48 10.187.1.51 10.187.1.54 10.187.1.57
VE
R
MATE COPY CHASSIS 2
GGNDRC4C0 GGNDRINSSPC0 GGNDRSGC0 GGNDRLISC0 GGNDRNGEMSC0 SPARE

SE
10.187.1.61 10.187.1.64 10.187.1.67 10.187.1.70 10.187.1.73
R
V
BLADE 9 BLADE 10 BLADE 11 BLADE 12 BLADE 13 BLADEER
14
GGNDRC4C1 GGNDRINSSPC1 GGNDRSGC1 GGNDRLISC1 GGNDRNGEMSC1 SPARE

SE
10.187.1.62 10.187.1.65 10.187.1.68 10.187.1.71 10.187.1.74
R
V
ER
\\
DNS:- MAXNG.BSNL.IN
Self Copy
ID
Session CHD_SELF_SBC_1 chdprsbcc0 CHD_01 01 Copy 0 Chandigarh Self
10.187.1.10
Border SBC
Controller
CHD_SELF_SBC_2 chdprsbcc1 CHD_01 09 Copy 1 Chandigarh Self
10.187.1.11
SBC
CHD_SELF_SBC chdprsbc CHD_01 Floating IP Chandigarh Self
10.187.1.12
SBC.
112 C-DOT MAX-NG


ID
Class 5 CHD_SELF_C5_1 chdprc5c0 CHD_01 02 Copy 0 Chandigarh Self C5
10.187.1.13
Subscriber SS
Server
CHD_SELF_C5_2 chdprc5c1 CHD_01 10 Copy 1 Chandigarh Self C5
10.187.1.14
SS
CHD_SELF_C5 chdprc5 CHD_01 Floating IP Chandigarh Self
10.187.1.15
C5.
Rating and CHD_SELF_RTR_1 chdprraterc0 CHD_01 03 Copy 0 Chandigarh Self
10.187.1.16
Server
CHD_SELF_RTR_2 chdprraterc1 CHD_01 11 Copy 1 Chandigarh Self
10.187.1.17
Rating Server
CHD_SELF_RTR chdprrater CHD_01 Floating IP of Chandigarh
10.187.1.18
Self Rating Server
Database CHD_SELF_DB_1 chdprdbc0 CHD_01 04 Copy 0 Chandigarh Self DB
10.187.1.19
Server Server
CHD_SELF_DB_2 chdprdbc1 CHD_01 12 Copy 1 Chandigarh Self DB
10.187.1.20
Server
CHD_SELF_DB chdprdb CHD_01 Floating IP of Chandigarh
10.187.1.21
Self DB Server
Subscriber CHD_SELF_PROV_1 chdprspsc0 CHD_01 05 Copy 0 Chandigarh Self
10.187.1.22
Provisioning Prov. Server
Server
CHD_SELF_PROV_2 chdprspsc1 CHD_01 13 Copy 1 Chandigarh Self
10.187.1.23
Prov. Server
CHD_SELF_PROV chdprsps CHD_01 Floating IP of Chandigarh
10.187.1.24
Self Prov. Server
Spare Server CHD_01 06
Class 4 CHD_SELF_C4_1 chdprc4c0 CHD_02 01 Copy 0 Chandigarh Self C4
10.187.1.27
Trunking SS
Server
CHD_SELF_C4_2 chdprc4c1 CHD_02 09 Copy 1 Chandigarh Self C4
10.187.1.28
SS
CHD_SELF_C4 chdprc4 CHD_02 Floating IP Chandigarh Self
10.187.1.29
C4.
IN Service CHD_SELF_SSP_1 chdprinsspc0 CHD_02 02 10.187.1.30 Copy 0 Chandigarh Self SSP
Switching
Point CHD_SELF_SSP_2 chdprinsspc1 CHD_02 10 10.187.1.31 Copy 1 Chandigarh Self SSP
CHD_SELF_SSP chdprinssp CHD_02 Floating IP Chandigarh Self
10.187.1.32
SSP
SIGTARN CHD_SELF_SIG_1 chdprsgc0 CHD_02 03 Copy 0 Chandigarh Self Sig.
10.187.1.33
Signaling Server

Chapter 4.

ID
Gateway CHD_SELF_SIG_2 chdprsgc1 CHD_02 11 Copy 1 Chandigarh Self Sig.
Server 10.187.1.34
Server
CHD_SELF_SIG chdprsg CHD_02 Floating IP of Chandigarh
10.187.1.35
Self Sig. Server
Lawful CHD_SELF_LIS_1 chdprlisc0 CHD_02 04 10.187.1.36 Copy 0 Chandigarh Self LIS
Interception
Server CHD_SELF_LIS_2 chdprlisc1 CHD_02 12 10.187.1.37 Copy 1 Chandigarh Self LIS
CHD_SELF_LIS chdprlis CHD_02 Floating IP of Chandigarh
10.187.1.38
Self LIS
Next CHD_SELF_NGEMS chdprngemsc CHD_02 05 Copy 0 Chandigarh Self
10.187.1.39
Generation _1 0 NGEMS
EMS
CHD_SELF_NGEMS chdprngemsc CHD_02 13 Copy 1 Chandigarh Self
10.187.1.40
_2 1 NGEMS
CHD_SELF_NGEMS chdprngems CHD_02 Floating IP of Chandigarh
10.187.1.41
Self NGEMS
Mate Copy
ID ID
Session Border CHD_MATE_SBC_1 ggndrsbcc0 CHD_03 01 Copy 0 Chandigarh Mate
10.187.1.44
Controller SBC
CHD_MATE_SBC_2 ggndrsbcc1 CHD_03 02 Copy 1 Chandigarh Mate
10.187.1.45
SBC
CHD_MATE_SBC ggndrsbcc0 CHD_03 Floating IP Chandigarh Mate
10.187.1.46
SBC.
Class 5 CHD_MATE_C5_1 ggndrc5c0 CHD_03 03 Copy 0 Chandigarh Mate C5
10.187.1.47
Subscriber SS
Server
CHD_MATE_C5_2 ggndrc5c1 CHD_03 04 Copy 1 Chandigarh Mate C5
10.187.1.48
SS
CHD_MATE_C5 ggndrc5 CHD_03 Floating IP Chandigarh Mate
10.187.1.49
C5.
Rating and CHD_MATE_RTR_1 ggndrraterc0 CHD_03 05 Copy 0 Chandigarh Mate
10.187.1.50
Server
CHD_MATE_RTR_2 ggndrraterc1 CHD_03 06 Copy 1 Chandigarh Mate
10.187.1.51
Rating Server
114 C-DOT MAX-NG


ID ID
CHD_MATE_RTR ggndrrater CHD_03 Floating IP of Chandigarh
10.187.1.52
Mate Rating Server
Database CHD_MATE_DB_1 ggndrdbc0 CHD_03 07 Copy 0 Chandigarh Mate DB
10.187.1.53
Server Server
CHD_MATE_DB_2 ggndrdbc1 CHD_03 08 Copy 1 Chandigarh Mate DB
10.187.1.54
Server
CHD_MATE_DB ggndrdb CHD_03 Floating IP of Chandigarh
10.187.1.55
Mate DB Server
Subscriber CHD_MATE_PROV_1 ggndrspsc0 CHD_03 09 Copy 0 Chandigarh Mate
10.187.1.56
Server
CHD_MATE_PROV_2 ggndrspsc1 CHD_03 10 Copy 1 Chandigarh Mate
10.187.1.57
Prov. Server
CHD_MATE_PROV ggndrsps CHD_03 Floating IP of Chandigarh
10.187.1.58
Mate Prov. Server
Class 4 CHD_MATE_C4_1 ggndrc4c0 CHD_04 01 Copy 0 Chandigarh Mate C4
10.187.1.61
Trunking SS
Server
CHD_MATE_C4_2 ggndrc4c1 CHD_04 02 Copy 1 Chandigarh Mate C4
10.187.1.62
SS
CHD_MATE_C4 ggndrc4 CHD_04 Floating IP Chandigarh Mate
10.187.1.63
C4.
IN Service CHD_MATE_SSP_1 ggndrinsspc0 CHD_04 03 10.187.1.64 Copy 0 Chandigarh Mate SSP
Switching
Point CHD_MATE_SSP_2 ggndrinsspc1 CHD_04 04 10.187.1.65 Copy 1 Chandigarh Mate SSP
CHD_MATE_SSP ggndrinssp CHD_04 Floating IP Chandigarh Mate
10.187.1.66
SSP
SIGTARN CHD_MATE_SIG_1 ggndrsgc0 CHD_04 05 Copy 0 Chandigarh Mate Sig.
10.187.1.67
Signaling Server
Gateway
Server CHD_MATE_SIG_2 ggndrsgc1 CHD_04 06 Copy 1 Chandigarh Mate Sig.
10.187.1.68
Server
CHD_MATE_SIG ggndrsg CHD_04 Floating IP of Chandigarh
10.187.1.69
Mate Sig. Server
Lawful CHD_MATE_LIS_1 ggndrlisc0 CHD_04 07 10.187.1.70 Copy 0 Chandigarh Mate LIS
Interception
Server CHD_MATE_LIS_2 ggndrlisc1 CHD_04 08 10.187.1.71 Copy 1 Chandigarh Mate LIS
CHD_MATE_LIS ggndrlis CHD_04 Floating IP of Chandigarh
10.187.1.72
Mate LIS
Next CHD_MATE_NGEMS ggndrngems CHD_04 09 10.187.1.73 Copy 0 Chandigarh Mate

Chapter 4.

ID ID
Generation _1 c0 NGEMS
EMS
CHD_MATE_NGEMS ggndrngems CHD_04 10 Copy 1 Chandigarh Mate
10.187.1.74
_2 c1 NGEMS
CHD_MATE_NGEMS ggndrngems CHD_04 Floating IP of Chandigarh
10.187.1.75
Mate NGEMS
10.187.1.25 to 10.187.1.26
10.187.1.42 to 10.187.1.43
10.187.1.59 to 10.187.1.60
10.187.1.76 to 10.187.1.79

CHD_01 01 10.187.1.80
CHD_01 02 10.187.1.81
CHD_01 03 10.187.1.82
CHD_01 04 10.187.1.83
CHD_01 05 10.187.1.84
CHD_01 06 10.187.1.85
CHD_01 07 10.187.1.86
CHD_01 08 10.187.1.87
CHD_01 09 10.187.1.88
CHD_01 10 10.187.1.89
CHD_01 11 10.187.1.90
CHD_01 12 10.187.1.91
116 C-DOT MAX-NG

CHD_01_ILO1 OA1 10.187.1.92

CHD_01_ILO2 OA2 10.187.1.93
CHD_01_ILO3 SW1 10.187.1.94
CHD_01_ILO4 SW2 10.187.1.95
CHD_02 01 10.187.1.96
CHD_02 02 10.187.1.97
CHD_02 03 10.187.1.98
CHD_02 04 10.187.1.99
CHD_02 05 10.187.1.100
CHD_02 06 10.187.1.101
CHD_02 07 10.187.1.102
CHD_02 08 10.187.1.103
CHD_02 09 10.187.1.104
CHD_02 10 10.187.1.105
CHD_02 11 10.187.1.106
CHD_02 12 10.187.1.107
CHD_02_ILO1 OA1 10.187.1.108
CHD_02_ILO2 OA2 10.187.1.109
CHD_02_ILO3 SW1 10.187.1.110
CHD_02_ILO4 SW2 10.187.1.111
CHD_03 01 10.187.1.112
CHD_03 02 10.187.1.113
CHD_03 03 10.187.1.114
CHD_03 04 10.187.1.115
CHD_03 05 10.187.1.116
CHD_03 06 10.187.1.117
CHD_03 07 10.187.1.118

Chapter 4.
CHD_03 08 10.187.1.119
CHD_03 09 10.187.1.120
CHD_03 10 10.187.1.121
CHD_03 11 10.187.1.122
CHD_03 12 10.187.1.123
CHD_03_ILO1 OA1 10.187.1.124
CHD_03_ILO2 OA2 10.187.1.125
CHD_03_ILO3 SW1 10.187.1.126
CHD_03_ILO4 SW2 10.187.1.127
CHD_04 01 10.187.1.128
CHD_04 02 10.187.1.129
CHD_04 03 10.187.1.130
CHD_04 04 10.187.1.131
CHD_04 05 10.187.1.132
CHD_04 06 10.187.1.133
CHD_04 07 10.187.1.134
CHD_04 08 10.187.1.135
CHD_04 09 10.187.1.136
CHD_04 10 10.187.1.137
CHD_04 11 10.187.1.138
CHD_04 12 10.187.1.139
CHD_04_ILO1 OA1 10.187.1.140
CHD_04_ILO2 OA2 10.187.1.141
CHD_04_ILO3 SW1 10.187.1.142
CHD_04_ILO4 SW2 10.187.1.143
CHD_05_ILO1 OA1 10.187.1.144
CHD_05_ILO2 OA2 10.187.1.145
CHD_05_ILO3 SW1 10.187.1.146
118 C-DOT MAX-NG

CHD_05_ILO4 SW2 10.187.1.147

10.187.1.148 to 10.187.1.149

Client Terminal CHD_CL1 10.187.1.150
1 (LED Panel)
2
3
4
5
Printer CHD_PRN1 10.187.1.155

10.187.1.156 to 10.187.1.169

10.187.1.170 to 10.187.1.179
Spare IP Addresses:
10.187.1.180 to 10.187.1.254
Note: IP list of MAX-NG core sites are available on C-DOT MAX-NG Helpline Portal.

Chapter 4.
West Zone Core:PUNE (PRIMARY Site)

FOR
Self-Copy Chassis 1
120 C-DOT MAX-NG

PUNPRSBCC0 PUNPRC5C0 PUNPRRATERC0 PUNPRDBC0 PUNPRSPSC0 SPARE

SERV
10.187.5.10 10.187.5.13 10.187.5.16 10.187.5.19 10.187.5.22
ER
PUNPRSBCC1 PUNPRC5C1 PUNPRRATERC1 PUNPRDBC1 PUNPRSPSC1 SPARE

SERV
10.187.5.11 10.187.5.14 10.187.5.17 10.187.5.20 10.187.5.23
ER
SELF-COPY CHASSIS 2
PUNPRC4C0 PUNPRINSSPC0 PUNPRSGC0 PUNPRLISC0 PUNPRNGEMSC0 SPARE

SER
10.187.5.27 10.187.5.30 10.187.5.33 10.187.5.36 10.187.5.39
VER
PUNPRC4C1 PUNPRINSSPC1 PUNPRSGC1 PUNPRLISC1 PUNPRNGEMSC1 SPARE

SER
10.187.5.28 10.187.5.31 10.187.5.34 10.187.5.37 10.187.5.40
VER
MATE COPY CHASSIS 1
BPLDRSBCC0 BPLDRC5C0 BPLDRRATERC0 BPLDRDBC0 BPLDRSPSC0 SPARE

SERV
10.187.5.44 10.187.5.47 10.187.5.50 10.187.5.53 10.187.5.56
ER

Chapter 4.
BPLDRSBCC1 BPLDRC5C1 BPLDRRATERC1 BPLDRDBC1 BPLDRSPSC1 SPARE

SERV
10.187.5.45 10.187.5.48 10.187.5.51 10.187.5.54 10.187.5.57
ER
MATE COPY CHASSIS 2
BPLDRC4C0 BPLDRINSSPC0 BPLDRSGC0 BPLDRLISC0 BPLDRNGEMSC0 SPARE

SER
10.187.5.61 10.187.5.64 10.187.5.67 10.187.5.70 10.187.5.73
VER
BPLDRC4C1 BPLDRINSSPC1 BPLDRSGC1 BPLDRLISC1 BPLDRNGEMSC1 SPARE

SER
10.187.5.62 10.187.5.65 10.187.5.68 10.187.5.71 10.187.5.74
VER
DNS:- MAXNG.BSNL.IN
Self Copy
ID
Session PUN_SELF_SBC_1 punprsbcc0 PUN_01 01 10.187.5.10 Copy 0 Pune Self SBC
Border
Controller PUN_SELF_SBC_2 punprsbcc1 PUN_01 09 10.187.5.11 Copy 1 Pune Self SBC
PUN_SELF_SBC punprsbc PUN_01 10.187.5.12 Floating IP Pune Self SBC.
Class 5 PUN_SELF_C5_1 punprc5c0 PUN_01 02 10.187.5.13 Copy 0 Pune Self C5 SS
Subscriber
Server PUN_SELF_C5_2 punprc5c1 PUN_01 10 10.187.5.14 Copy 1 Pune Self C5 SS
PUN_SELF_C5 punprc5 PUN_01 10.187.5.15 Floating IP Pune Self C5.
Rating and PUN_SELF_RTR_1 punprraterc0 PUN_01 03 Copy 0 Pune Self Rating
10.187.5.16
Charging Server
Server
PUN_SELF_RTR_2 punprraterc1 PUN_01 11 Copy 1 Pune Self Rating
10.187.5.17
Server
PUN_SELF_RTR punprrater PUN_01 Floating IP of Pune Self
10.187.5.18
Rating Server
Database PUN_SELF_DB_1 punprdbc0 PUN_01 04 10.187.5.19 Copy 0 Pune Self DB Server
122 C-DOT MAX-NG


ID
Server PUN_SELF_DB_2 punprdbc1 PUN_01 12 10.187.5.20 Copy 1 Pune Self DB Server
PUN_SELF_DB punprdb PUN_01 Floating IP of Pune Self DB
10.187.5.21
Server
Subscriber PUN_SELF_PROV_1 punprspsc0 PUN_01 05 Copy 0 Pune Self Prov.
10.187.5.22
Provisioning Server
Server
PUN_SELF_PROV_2 punprspsc1 PUN_01 13 Copy 1 Pune Self Prov.
10.187.5.23
Server
PUN_SELF_PROV punprsps PUN_01 Floating IP of Pune Self
10.187.5.24
Prov. Server
Spare Server PUN_01 06
Class 4 PUN_SELF_C4_1 punprc4c0 PUN_02 01 10.187.5.27 Copy 0 Pune Self C4 SS
Trunking
Server PUN_SELF_C4_2 punprc4c1 PUN_02 09 10.187.5.28 Copy 1 Pune Self C4 SS
PUN_SELF_C4 punprc4 PUN_02 10.187.5.29 Floating IP Pune Self C4.
IN Service PUN_SELF_SSP_1 punprinsspc0 PUN_02 02 10.187.5.30 Copy 0 Pune Self SSP
Switching
Point PUN_SELF_SSP_2 punprinsspc1 PUN_02 10 10.187.5.31 Copy 1 Pune Self SSP
PUN_SELF_SSP punprinssp PUN_02 10.187.5.32 Floating IP Pune Self SSP
SIGTARN PUN_SELF_SIG_1 punprsgc0 PUN_02 03 10.187.5.33 Copy 0 Pune Self Sig. Server
Signaling
Gateway PUN_SELF_SIG_2 punprsgc1 PUN_02 11 10.187.5.34 Copy 1 Pune Self Sig. Server
Server PUN_SELF_SIG punprsg PUN_02 Floating IP of Pune Self Sig.
10.187.5.35
Server
Lawful PUN_SELF_LIS_1 punprlisc0 PUN_02 04 10.187.5.36 Copy 0 Pune Self LIS
Interception
Server PUN_SELF_LIS_2 punprlisc1 PUN_02 12 10.187.5.37 Copy 1 Pune Self LIS
PUN_SELF_LIS punprlis PUN_02 10.187.5.38 Floating IP of Pune Self LIS
Next PUN_SELF_NGEMS_ punprngemsc PUN_02 05 Copy 0 Pune Self NGEMS
10.187.5.39
Generation 1 0
EMS
PUN_SELF_NGEMS_ punprngemsc PUN_02 13 Copy 1 Pune Self NGEMS
10.187.5.40
2 1
PUN_SELF_NGEMS punprngems PUN_02 Floating IP of Pune Self
10.187.5.41
NGEMS

Chapter 4.
Mate Copy
ID ID
Session Border PUN_MATE_SBC_1 bpldrsbcc0 PUN_03 01 10.187.5.44 Copy 0 Pune Mate SBC
Controller
PUN_MATE_SBC_2 bpldrsbcc1 PUN_03 02 10.187.5.45 Copy 1 Pune Mate SBC
PUN_MATE_SBC bpldrsbcc0 PUN_03 10.187.5.46 Floating IP Pune Mate SBC.
Class 5 PUN_MATE_C5_1 bpldrc5c0 PUN_03 03 10.187.5.47 Copy 0 Pune Mate C5 SS
Subscriber
Server PUN_MATE_C5_2 bpldrc5c1 PUN_03 04 10.187.5.48 Copy 1 Pune Mate C5 SS
PUN_MATE_C5 bpldrc5 PUN_03 10.187.5.49 Floating IP Pune Mate C5.
Rating and PUN_MATE_RTR_1 bpldrraterc0 PUN_03 05 Copy 0 Pune Mate Rating
10.187.5.50
Charging Server
Server
PUN_MATE_RTR_2 bpldrraterc1 PUN_03 06 Copy 1 Pune Mate Rating
10.187.5.51
Server
PUN_MATE_RTR bpldrrater PUN_03 Floating IP of Pune Mate
10.187.5.52
Rating Server
Database PUN_MATE_DB_1 bpldrdbc0 PUN_03 07 10.187.5.53 Copy 0 Pune Mate DB Server
Server
PUN_MATE_DB_2 bpldrdbc1 PUN_03 08 10.187.5.54 Copy 1 Pune Mate DB Server
PUN_MATE_DB bpldrdb PUN_03 Floating IP of Pune Mate DB
10.187.5.55
Server
Subscriber GURSLE_PROV_1 bpldrspsc0 PUN_03 09 Copy 0 Pune Mate Prov.
10.187.5.56
Provisioning Server
Server
PUN_MATE_PROV_2 bpldrspsc1 PUN_03 10 Copy 1 Pune Mate Prov.
10.187.5.57
Server
PUN_MATE_PROV bpldrsps PUN_03 Floating IP of Pune Mate
10.187.5.58
Prov. Server
Class 4 PUN_MATE_C4_1 bpldrc4c0 PUN_04 01 10.187.5.61 Copy 0 Pune Mate C4 SS
Trunking
Server PUN_MATE_C4_2 bpldrc4c1 PUN_04 02 10.187.5.62 Copy 1 Pune Mate C4 SS
PUN_MATE_C4 bpldrc4 PUN_04 10.187.5.63 Floating IP Pune Mate C4.
IN Service PUN_MATE_SSP_1 bpldrinsspc0 PUN_04 03 10.187.5.64 Copy 0 Pune Mate SSP
Switching
Point PUN_MATE_SSP_2 bpldrinsspc1 PUN_04 04 10.187.5.65 Copy 1 Pune Mate SSP
PUN_MATE_SSP bpldrinssp PUN_04 10.187.5.66 Floating IP Pune Mate SSP
SIGTARN PUN_MATE_SIG_1 bpldrsgc0 PUN_04 05 10.187.5.67 Copy 0 Pune Mate Sig. Server
Signaling
PUN_MATE_SIG_2 bpldrsgc1 PUN_04 06 10.187.5.68 Copy 1 Pune Mate Sig. Server
124 C-DOT MAX-NG


ID ID
Gateway PUN_MATE_SIG bpldrsg PUN_04 Floating IP of Pune Mate Sig.
Server 10.187.5.69
Server
Lawful PUN_MATE_LIS_1 bpldrlisc0 PUN_04 07 10.187.5.70 Copy 0 Pune Mate LIS
Interception
Server PUN_MATE_LIS_2 bpldrlisc1 PUN_04 08 10.187.5.71 Copy 1 Pune Mate LIS
PUN_MATE_LIS bpldrlis PUN_04 10.187.5.72 Floating IP of Pune Mate LIS
Next PUN_MATE_NGEMS bpldrngemsc PUN_04 09 Copy 0 Pune Mate NGEMS
10.187.5.73
Generation _1 0
EMS
PUN_MATE_NGEMS bpldrngemsc PUN_04 10 Copy 1 Pune Mate NGEMS
10.187.5.74
_2 1
PUN_MATE_NGEMS bpldrngems PUN_04 Floating IP of Pune Mate
10.187.5.75
NGEMS
10.187.5.25 to 10.187.5.26
10.187.5.42 to 10.187.5.43
10.187.5.59 to 10.187.5.60
10.187.5.76 to 10.187.5.79

PUN_01 01 10.187.5.80
PUN_01 02 10.187.5.81
PUN_01 03 10.187.5.82
PUN_01 04 10.187.5.83
PUN_01 05 10.187.5.84
PUN_01 06 10.187.5.85

Chapter 4.
PUN_01 07 10.187.5.86
PUN_01 08 10.187.5.87
PUN_01 09 10.187.5.88
PUN_01 10 10.187.5.89
PUN_01 11 10.187.5.90
PUN_01 12 10.187.5.91
PUN_01_ILO1 OA1 10.187.5.92
PUN_01_ILO2 OA2 10.187.5.93
PUN_01_ILO3 SW1 10.187.5.94
PUN_01_ILO4 SW2 10.187.5.95
PUN_02 01 10.187.5.96
PUN_02 02 10.187.5.97
PUN_02 03 10.187.5.98
PUN_02 04 10.187.5.99
PUN_02 05 10.187.5.100
PUN_02 06 10.187.5.101
PUN_02 07 10.187.5.102
PUN_02 08 10.187.5.103
PUN_02 09 10.187.5.104
PUN_02 10 10.187.5.105
PUN_02 11 10.187.5.106
PUN_02 12 10.187.5.107
PUN_02_ILO1 OA1 10.187.5.108
PUN_02_ILO2 OA2 10.187.5.109
PUN_02_ILO3 SW1 10.187.5.110
PUN_02_ILO4 SW2 10.187.5.111
PUN_03 01 10.187.5.112
PUN_03 02 10.187.5.113
126 C-DOT MAX-NG

PUN_03 03 10.187.5.114
PUN_03 04 10.187.5.115
PUN_03 05 10.187.5.116
PUN_03 06 10.187.5.117
PUN_03 07 10.187.5.118
PUN_03 08 10.187.5.119
PUN_03 09 10.187.5.120
PUN_03 10 10.187.5.121
PUN_03 11 10.187.5.122
PUN_03 12 10.187.5.123
PUN_03_ILO1 OA1 10.187.5.124
PUN_03_ILO2 OA2 10.187.5.125
PUN_03_ILO3 SW1 10.187.5.126
PUN_03_ILO4 SW2 10.187.5.127
PUN_04 01 10.187.5.128
PUN_04 02 10.187.5.129
PUN_04 03 10.187.5.130
PUN_04 04 10.187.5.131
PUN_04 05 10.187.5.132
PUN_04 06 10.187.5.133
PUN_04 07 10.187.5.134
PUN_04 08 10.187.5.135
PUN_04 09 10.187.5.136
PUN_04 10 10.187.5.137
PUN_04 11 10.187.5.138
PUN_04 12 10.187.5.139
PUN_04_ILO1 OA1 10.187.5.140

Chapter 4.
PUN_04_ILO2 OA2 10.187.5.141

PUN_04_ILO3 SW1 10.187.5.142
PUN_04_ILO4 SW2 10.187.5.143
PUN_05_ILO1 OA1 10.187.5.144
PUN_05_ILO2 OA2 10.187.5.145
PUN_05_ILO3 SW1 10.187.5.146
PUN_05_ILO4 SW2 10.187.5.147

10.187.5.148 to 10.187.5.149

Client Terminal PUN_CL1 10.187.5.150
1 (LED Panel)
2
3
4
5
Printer PUN_PRN1 10.187.5.155

10.187.5.156 to 10.187.5.169

10.187.5.170 to 10.187.5.179
Spare IP Addresses:
128 C-DOT MAX-NG

10.187.5.180 to 10.187.5.254

Chapter 4.
East Zone Core: KOLKATA (PRIMARY Site)
130 C-DOT MAX-NG

Self-Copy Chassis 1

Chapter 4.
KOLPRSBCC0 KOLPRC5C0 KOLPRRATERC0 KOLPRDBC0 KOLPRSPSC0 SPARE

SERV
10.187.2.10 10.187.2.13 10.187.2.16 10.187.2.19 10.187.2.22
ER
KOLPRSBCC1 KOLPRC5C1 KOLPRRATERC1 KOLPRDBC1 KOLPRSPSC1 SPARE

SERV
10.187.2.11 10.187.2.14 10.187.2.17 10.187.2.20 10.187.2.23
ER
SELF-COPY CHASSIS 2
KOLPRC4C0 KOLPRINSSPC0 KOLPRSGC0 KOLPRLISC0 KOLPRNGEMSC0 SPARE

SER
10.187.2.27 10.187.2.30 10.187.2.33 10.187.2.36 10.187.2.39
VER
KOLPRC4C1 KOLPRINSSPC1 KOLPRSGC1 KOLPRLISC1 KOLPRNGEMSC1 SPARE

SER
10.187.2.28 10.187.2.31 10.187.2.34 10.187.2.37 10.187.2.40
VER
MATE COPY CHASSIS 1
CTKDRSBCC0 CTKDRC5C0 CTKDRRATERC0 CTKDRDBC0 CTKDRSPSC0 SPARE

SER
10.187.2.44 10.187.2.47 10.187.2.50 10.187.2.53 10.187.2.56
VER
132 C-DOT MAX-NG

CTKDRSBCC1 CTKDRC5C1 CTKDRRATERC1 CTKDRDBC1 CTKDRSPSC1 SPARE

SER
10.187.2.45 10.187.2.48 10.187.2.51 10.187.2.54 10.187.2.57
VER
MATE COPY CHASSIS 2
CTKDRC4C0 CTKDRINSSPC0 CTKDRSGC0 CTKDRLISC0 CTKDRNGEMSC0 SPARE

SE
10.187.2.61 10.187.2.64 10.187.2.67 10.187.2.70 10.187.2.73
RV
ER
CTKDRC4C1 CTKDRINSSPC1 CTKDRSGC1 CTKDRLISC1 CTKDRNGEMSC1 SPARE

SE
10.187.2.62 10.187.2.65 10.187.2.68 10.187.2.71 10.187.2.74
RV
ER
DNS:- MAXNG.BSNL.IN
Self Copy
ID
Session KOL_SELF_SBC_1 kolprsbcc0 KOL_01 01 10.187.2.10 Copy 0 Kolkata Self SBC
Border
Controller KOL_SELF_SBC_2 kolprsbcc1 KOL_01 09 10.187.2.11 Copy 1 Kolkata Self SBC
KOL_SELF_SBC kolprsbc KOL_01 Floating IP Kolkata Self
10.187.2.12
SBC.
Class 5 KOL_SELF_C5_1 kolprc5c0 KOL_01 02 10.187.2.13 Copy 0 Kolkata Self C5 SS
Subscriber
Server KOL_SELF_C5_2 kolprc5c1 KOL_01 10 10.187.2.14 Copy 1 Kolkata Self C5 SS
KOL_SELF_C5 kolprc5 KOL_01 10.187.2.15 Floating IP Kolkata Self C5.
Rating and KOL_SELF_RTR_1 kolprraterc0 KOL_01 03 Copy 0 Kolkata Self Rating
10.187.2.16
Charging Server
Server
KOL_SELF_RTR_2 kolprraterc1 KOL_01 11 Copy 1 Kolkata Self Rating
10.187.2.17
Server
KOL_SELF_RTR kolprrater KOL_01 Floating IP of Kolkata Self
10.187.2.18
Rating Server

Chapter 4.

ID
Database KOL_SELF_DB_1 kolprdbc0 KOL_01 04 Copy 0 Kolkata Self DB
10.187.2.19
Server Server
KOL_SELF_DB_2 kolprdbc1 KOL_01 12 Copy 1 Kolkata Self DB
10.187.2.20
Server
KOL_SELF_DB kolprdb KOL_01 Floating IP of Kolkata Self
10.187.2.21
DB Server
Subscriber KOL_SELF_PROV_1 kolprspsc0 KOL_01 05 Copy 0 Kolkata Self Prov.
10.187.2.22
Provisioning Server
Server
KOL_SELF_PROV_2 kolprspsc1 KOL_01 13 Copy 1 Kolkata Self Prov.
10.187.2.23
Server
KOL_SELF_PROV kolprsps KOL_01 Floating IP of Kolkata Self
10.187.2.24
Prov. Server
Spare Server KOL_01 06
Class 4 KOL_SELF_C4_1 kolprc4c0 KOL_02 01 10.187.2.27 Copy 0 Kolkata Self C4 SS
Trunking
Server KOL_SELF_C4_2 kolprc4c1 KOL_02 09 10.187.2.28 Copy 1 Kolkata Self C4 SS
KOL_SELF_C4 kolprc4 KOL_02 10.187.2.29 Floating IP Kolkata Self C4.
IN Service KOL_SELF_SSP_1 kolprinsspc0 KOL_02 02 10.187.2.30 Copy 0 Kolkata Self SSP
Switching
Point KOL_SELF_SSP_2 kolprinsspc1 KOL_02 10 10.187.2.31 Copy 1 Kolkata Self SSP
KOL_SELF_SSP kolprinssp KOL_02 10.187.2.32 Floating IP Kolkata Self SSP
SIGTARN KOL_SELF_SIG_1 kolprsgc0 KOL_02 03 Copy 0 Kolkata Self Sig.
10.187.2.33
Signaling Server
Gateway
Server KOL_SELF_SIG_2 kolprsgc1 KOL_02 11 Copy 1 Kolkata Self Sig.
10.187.2.34
Server
KOL_SELF_SIG kolprsg KOL_02 Floating IP of Kolkata Self
10.187.2.35
Sig. Server
Lawful KOL_SELF_LIS_1 kolprlisc0 KOL_02 04 10.187.2.36 Copy 0 Kolkata Self LIS
Interception
Server KOL_SELF_LIS_2 kolprlisc1 KOL_02 12 10.187.2.37 Copy 1 Kolkata Self LIS
KOL_SELF_LIS kolprlis KOL_02 Floating IP of Kolkata Self
10.187.2.38
LIS
Next KOL_SELF_NGEMS kolprngemsc0 KOL_02 05 Copy 0 Kolkata Self
10.187.2.39
Generation _1 NGEMS
EMS
KOL_SELF_NGEMS kolprngemsc1 KOL_02 13 Copy 1 Kolkata Self
10.187.2.40
_2 NGEMS
KOL_SELF_NGEMS kolprngems KOL_02 Floating IP of Kolkata Self
10.187.2.41
NGEMS
134 C-DOT MAX-NG

Mate Copy
ID ID
Session Border KOL_MATE_SBC_1 ctkdrsbcc0 KOL_03 01 10.187.2.44 Copy 0 Kolkata Mate SBC
Controller
KOL_MATE_SBC_2 ctkdrsbcc1 KOL_03 02 10.187.2.45 Copy 1 Kolkata Mate SBC
KOL_MATE_SBC ctkdrsbcc0 KOL_03 Floating IP Kolkata Mate
10.187.2.46
SBC.
Class 5 KOL_MATE_C5_1 ctkdrc5c0 KOL_03 03 10.187.2.47 Copy 0 Kolkata Mate C5 SS
Subscriber
Server KOL_MATE_C5_2 ctkdrc5c1 KOL_03 04 10.187.2.48 Copy 1 Kolkata Mate C5 SS
KOL_MATE_C5 ctkdrc5 KOL_03 10.187.2.49 Floating IP Kolkata Mate C5.
Rating and KOL_MATE_RTR_1 ctkdrraterc0 KOL_03 05 Copy 0 Kolkata Mate Rating
10.187.2.50
Charging Server
Server
KOL_MATE_RTR_2 ctkdrraterc1 KOL_03 06 Copy 1 Kolkata Mate Rating
10.187.2.51
Server
KOL_MATE_RTR ctkdrrater KOL_03 Floating IP of Kolkata Mate
10.187.2.52
Rating Server
Database KOL_MATE_DB_1 ctkdrdbc0 KOL_03 07 Copy 0 Kolkata Mate DB
10.187.2.53
Server Server
KOL_MATE_DB_2 ctkdrdbc1 KOL_03 08 Copy 1 Kolkata Mate DB
10.187.2.54
Server
KOL_MATE_DB ctkdrdb KOL_03 Floating IP of Kolkata Mate
10.187.2.55
DB Server
Subscriber KOL_MATE_PROV_1 ctkdrspsc0 KOL_03 09 Copy 0 Kolkata Mate Prov.
10.187.2.56
Provisioning Server
Server
KOL_MATE_PROV_2 ctkdrspsc1 KOL_03 10 Copy 1 Kolkata Mate Prov.
10.187.2.57
Server
KOL_MATE_PROV ctkdrsps KOL_03 Floating IP of Kolkata Mate
10.187.2.58
Prov. Server
Class 4 KOL_MATE_C4_1 ctkdrc4c0 KOL_04 01 10.187.2.61 Copy 0 Kolkata Mate C4 SS
Trunking
Server KOL_MATE_C4_2 ctkdrc4c1 KOL_04 02 10.187.2.62 Copy 1 Kolkata Mate C4 SS
KOL_MATE_C4 ctkdrc4 KOL_04 10.187.2.63 Floating IP Kolkata Mate C4.
IN Service KOL_MATE_SSP_1 ctkdrinsspc0 KOL_04 03 10.187.2.64 Copy 0 Kolkata Mate SSP
Switching
KOL_MATE_SSP_2 ctkdrinsspc1 KOL_04 04 10.187.2.65 Copy 1 Kolkata Mate SSP

Chapter 4.

ID ID
Point KOL_MATE_SSP ctkdrinssp KOL_04 Floating IP Kolkata Mate
10.187.2.66
SSP
SIGTARN KOL_MATE_SIG_1 ctkdrsgc0 KOL_04 05 Copy 0 Kolkata Mate Sig.
10.187.2.67
Signaling Server
Gateway
Server KOL_MATE_SIG_2 ctkdrsgc1 KOL_04 06 Copy 1 Kolkata Mate Sig.
10.187.2.68
Server
KOL_MATE_SIG ctkdrsg KOL_04 Floating IP of Kolkata Mate
10.187.2.69
Sig. Server
Lawful KOL_MATE_LIS_1 ctkdrlisc0 KOL_04 07 10.187.2.70 Copy 0 Kolkata Mate LIS
Interception
Server KOL_MATE_LIS_2 ctkdrlisc1 KOL_04 08 10.187.2.71 Copy 1 Kolkata Mate LIS
KOL_MATE_LIS ctkdrlis KOL_04 Floating IP of Kolkata Mate
10.187.2.72
LIS
Next KOL_MATE_NGEMS ctkdrngemsc KOL_04 09 Copy 0 Kolkata Mate
10.187.2.73
EMS
KOL_MATE_NGEMS ctkdrngemsc KOL_04 10 Copy 1 Kolkata Mate
10.187.2.74
_2 1 NGEMS
KOL_MATE_NGEMS ctkdrngems KOL_04 Floating IP of Kolkata Mate
10.187.2.75
NGEMS
10.187.2.25 to 10.187.2.26
10.187.2.42 to 10.187.2.43
10.187.2.59 to 10.187.2.60
10.187.2.76 to 10.187.2.79

KOL_01 01 10.187.2.80
KOL_01 02 10.187.2.81
KOL_01 03 10.187.2.82
136 C-DOT MAX-NG

KOL_01 04 10.187.2.83
KOL_01 05 10.187.2.84
KOL_01 06 10.187.2.85
KOL_01 07 10.187.2.86
KOL_01 08 10.187.2.87
KOL_01 09 10.187.2.88
KOL_01 10 10.187.2.89
KOL_01 11 10.187.2.90
KOL_01 12 10.187.2.91
KOL_01_ILO1 OA1 10.187.2.92
KOL_01_ILO2 OA2 10.187.2.93
KOL_01_ILO3 SW1 10.187.2.94
KOL_01_ILO4 SW2 10.187.2.95
KOL_02 01 10.187.2.96
KOL_02 02 10.187.2.97
KOL_02 03 10.187.2.98
KOL_02 04 10.187.2.99
KOL_02 05 10.187.2.100
KOL_02 06 10.187.2.101
KOL_02 07 10.187.2.102
KOL_02 08 10.187.2.103
KOL_02 09 10.187.2.104
KOL_02 10 10.187.2.105
KOL_02 11 10.187.2.106
KOL_02 12 10.187.2.107
KOL_02_ILO1 OA1 10.187.2.108
KOL_02_ILO2 OA2 10.187.2.109

Chapter 4.
KOL_02_ILO3 SW1 10.187.2.110

KOL_02_ILO4 SW2 10.187.2.111
KOL_03 01 10.187.2.112
KOL_03 02 10.187.2.113
KOL_03 03 10.187.2.114
KOL_03 04 10.187.2.115
KOL_03 05 10.187.2.116
KOL_03 06 10.187.2.117
KOL_03 07 10.187.2.118
KOL_03 08 10.187.2.119
KOL_03 09 10.187.2.120
KOL_03 10 10.187.2.121
KOL_03 11 10.187.2.122
KOL_03 12 10.187.2.123
KOL_03_ILO1 OA1 10.187.2.124
KOL_03_ILO2 OA2 10.187.2.125
KOL_03_ILO3 SW1 10.187.2.126
KOL_03_ILO4 SW2 10.187.2.127
KOL_04 01 10.187.2.128
KOL_04 02 10.187.2.129
KOL_04 03 10.187.2.130
KOL_04 04 10.187.2.131
KOL_04 05 10.187.2.132
KOL_04 06 10.187.2.133
KOL_04 07 10.187.2.134
KOL_04 08 10.187.2.135
KOL_04 09 10.187.2.136
KOL_04 10 10.187.2.137
138 C-DOT MAX-NG

KOL_04 11 10.187.2.138
KOL_04 12 10.187.2.139
KOL_04_ILO1 OA1 10.187.2.140
KOL_04_ILO2 OA2 10.187.2.141
KOL_04_ILO3 SW1 10.187.2.142
KOL_04_ILO4 SW2 10.187.2.143
KOL_05_ILO1 OA1 10.187.2.144
KOL_05_ILO2 OA2 10.187.2.145
KOL_05_ILO3 SW1 10.187.2.146
KOL_05_ILO4 SW2 10.187.2.147

10.187.2.148 to 10.187.2.149

Client Terminal KOL_CL1 10.187.2.150
1 (LED Panel)
2
3
4
5
Printer KOL_PRN1 10.187.2.155

10.187.2.156 to 10.187.2.169

Chapter 4.

10.187.2.170 to 10.187.2.179
Spare IP Addresses:
10.187.2.180 to 10.187.2.254
South Zone Core: HYDERABAD (PRIMARY Site)
Self-Copy Chassis 1
140 C-DOT MAX-NG

HYDPRSBCC0 HYDPRC5C0 HYDPRRATERC0 HYDPRDBC0 HYDPRSPSC0 SPARE

SER
10.187.7.10 10.187.7.13 10.187.7.16 10.187.7.19 10.187.7.22
VER
HYDPRSBCC1 HYDPRC5C1 HYDPRRATERC1 HYDPRDBC1 HYDPRSPSC1 SPARE

SER
10.187.7.11 10.187.7.14 10.187.7.17 10.187.7.20 10.187.7.23
VER
SELF-COPY CHASSIS 2
HYDPRC4C0 HYDPRINSSPC0 HYDPRSGC0 HYDPRLISC0 HYDPRNGEMSC0 SPARE

SE
10.187.7.27 10.187.7.30 10.187.7.33 10.187.7.36 10.187.7.39
RV
ER
HYDPRC4C1 HYDPRINSSPC1 HYDPRSGC1 HYDPRLISC1 HYDPRNGEMSC1 SPARE

SE
10.187.7.28 10.187.7.31 10.187.7.34 10.187.7.37 10.187.7.40
RV
ER
MATE COPY CHASSIS 1
BLRDRSBCC0 BLRDRC5C0 BLRDRRATERC0 BLRDRDBC0 BLRDRSPSC0 SPARE

SER
10.187.7.44 10.187.7.47 10.187.7.50 10.187.7.53 10.187.7.56
VER

Chapter 4.
BLRDRSBCC1 BLRDRC5C1 BLRDRRATERC1 BLRDRDBC1 BLRDRSPSC1 SPARE

SER
10.187.7.45 10.187.7.48 10.187.7.51 10.187.7.54 10.187.7.57
VER
MATE COPY CHASSIS 2
BLRDRC4C0 BLRDRINSSPC0 BLRDRSGC0 BLRDRLISC0 BLRDRNGEMSC0 SPARE

SER
10.187.7.61 10.187.7.64 10.187.7.67 10.187.7.70 10.187.7.73
VE
R
BLRDRC4C1 BLRDRINSSPC1 BLRDRSGC1 BLRDRLISC1 BLRDRNGEMSC1 SPARE

SER
10.187.7.62 10.187.7.65 10.187.7.68 10.187.7.71 10.187.7.74
VE
R
DNS:- MAXNG.BSNL.IN
Self Copy
ID
Session HYD_SELF_SBC_1 hydprsbcc0 HYD_01 01 10.187.7.10 Copy 0 Hyderabad Self SBC
Border
Controller HYD_SELF_SBC_2 hydprsbcc1 HYD_01 09 10.187.7.11 Copy 1 Hyderabad Self SBC
HYD_SELF_SBC hydprsbc HYD_01 Floating IP Hyderabad Self
10.187.7.12
SBC.
Class 5 HYD_SELF_C5_1 hydprc5c0 HYD_01 02 Copy 0 Hyderabad Self C5
10.187.7.13
Subscriber SS
Server
HYD_SELF_C5_2 hydprc5c1 HYD_01 10 Copy 1 Hyderabad Self C5
10.187.7.14
SS
HYD_SELF_C5 hydprc5 HYD_01 Floating IP Hyderabad Self
10.187.7.15
C5.
Rating and HYD_SELF_RTR_1 hydprraterc0 HYD_01 03 Copy 0 Hyderabad Self
10.187.7.16
Server
HYD_SELF_RTR_2 hydprraterc1 HYD_01 11 Copy 1 Hyderabad Self
10.187.7.17
Rating Server
142 C-DOT MAX-NG


ID
HYD_SELF_RTR hydprrater HYD_01 Floating IP of Hyderabad
10.187.7.18
Self Rating Server
Database HYD_SELF_DB_1 hydprdbc0 HYD_01 04 Copy 0 Hyderabad Self DB
10.187.7.19
Server Server
HYD_SELF_DB_2 hydprdbc1 HYD_01 12 Copy 1 Hyderabad Self DB
10.187.7.20
Server
HYD_SELF_DB hydprdb HYD_01 Floating IP of Hyderabad
10.187.7.21
Self DB Server
Subscriber HYD_SELF_PROV_1 hydprspsc0 HYD_01 05 Copy 0 Hyderabad Self
10.187.7.22
Server
HYD_SELF_PROV_2 hydprspsc1 HYD_01 13 Copy 1 Hyderabad Self
10.187.7.23
Prov. Server
HYD_SELF_PROV hydprsps HYD_01 Floating IP of Hyderabad
10.187.7.24
Self Prov. Server
Spare Server HYD_01 06
Class 4 HYD_SELF_C4_1 hydprc4c0 HYD_02 01 Copy 0 Hyderabad Self C4
10.187.7.27
Trunking SS
Server
HYD_SELF_C4_2 hydprc4c1 HYD_02 09 Copy 1 Hyderabad Self C4
10.187.7.28
SS
HYD_SELF_C4 hydprc4 HYD_02 Floating IP Hyderabad Self
10.187.7.29
C4.
IN Service HYD_SELF_SSP_1 hydprinsspc0 HYD_02 02 10.187.7.30 Copy 0 Hyderabad Self SSP
Switching
Point HYD_SELF_SSP_2 hydprinsspc1 HYD_02 10 10.187.7.31 Copy 1 Hyderabad Self SSP
HYD_SELF_SSP hydprinssp HYD_02 Floating IP Hyderabad Self
10.187.7.32
SSP
SIGTARN HYD_SELF_SIG_1 hydprsgc0 HYD_02 03 Copy 0 Hyderabad Self Sig.
10.187.7.33
Signaling Server
Gateway
Server HYD_SELF_SIG_2 hydprsgc1 HYD_02 11 Copy 1 Hyderabad Self Sig.
10.187.7.34
Server
HYD_SELF_SIG hydprsg HYD_02 Floating IP of Hyderabad
10.187.7.35
Self Sig. Server
Lawful HYD_SELF_LIS_1 hydprlisc0 HYD_02 04 10.187.7.36 Copy 0 Hyderabad Self LIS
Interception
Server HYD_SELF_LIS_2 hydprlisc1 HYD_02 12 10.187.7.37 Copy 1 Hyderabad Self LIS
HYD_SELF_LIS hydprlis HYD_02 Floating IP of Hyderabad
10.187.7.38
Self LIS
Next HYD_SELF_NGEMS hydprngemsc HYD_02 05 10.187.7.39 Copy 0 Hyderabad Self

Chapter 4.

ID
EMS
HYD_SELF_NGEMS hydprngemsc HYD_02 13 Copy 1 Hyderabad Self
10.187.7.40
_2 1 NGEMS
HYD_SELF_NGEMS hydprngems HYD_02 Floating IP of Hyderabad
10.187.7.41
Self NGEMS
Mate Copy
ID ID
Session Border HYD_MATE_SBC_1 blrdrsbcc0 HYD_03 01 10.187.7.44 Copy 0 Hyderabad Mate SBC
Controller
HYD_MATE_SBC_2 blrdrsbcc1 HYD_03 02 10.187.7.45 Copy 1 Hyderabad Mate SBC
HYD_MATE_SBC blrdrsbcc0 HYD_03 Floating IP Hyderabad Mate
10.187.7.46
SBC.
Class 5 HYD_MATE_C5_1 blrdrc5c0 HYD_03 03 Copy 0 Hyderabad Mate C5
10.187.7.47
Subscriber SS
Server
HYD_MATE_C5_2 blrdrc5c1 HYD_03 04 Copy 1 Hyderabad Mate C5
10.187.7.48
SS
HYD_MATE_C5 blrdrc5 HYD_03 Floating IP Hyderabad Mate
10.187.7.49
C5.
Rating and HYD_MATE_RTR_1 blrdrraterc0 HYD_03 05 Copy 0 Hyderabad Mate
10.187.7.50
Server
HYD_MATE_RTR_2 blrdrraterc1 HYD_03 06 Copy 1 Hyderabad Mate
10.187.7.51
Rating Server
HYD_MATE_RTR blrdrrater HYD_03 Floating IP of Hyderabad
10.187.7.52
Mate Rating Server
Database HYD_MATE_DB_1 blrdrdbc0 HYD_03 07 Copy 0 Hyderabad Mate DB
10.187.7.53
Server Server
HYD_MATE_DB_2 blrdrdbc1 HYD_03 08 Copy 1 Hyderabad Mate DB
10.187.7.54
Server
HYD_MATE_DB blrdrdb HYD_03 Floating IP of Hyderabad
10.187.7.55
Mate DB Server
Subscriber GURSLE_PROV_1 blrdrspsc0 HYD_03 09 Copy 0 Hyderabad Mate
10.187.7.56
Server
HYD_MATE_PROV_2 blrdrspsc1 HYD_03 10 Copy 1 Hyderabad Mate
10.187.7.57
Prov. Server
144 C-DOT MAX-NG


ID ID
HYD_MATE_PROV blrdrsps HYD_03 Floating IP of Hyderabad
10.187.7.58
Mate Prov. Server
Class 4 HYD_MATE_C4_1 blrdrc4c0 HYD_04 01 Copy 0 Hyderabad Mate C4
10.187.7.61
Trunking SS
Server
HYD_MATE_C4_2 blrdrc4c1 HYD_04 02 Copy 1 Hyderabad Mate C4
10.187.7.62
SS
HYD_MATE_C4 blrdrc4 HYD_04 Floating IP Hyderabad Mate
10.187.7.63
C4.
IN Service HYD_MATE_SSP_1 blrdrinsspc0 HYD_04 03 10.187.7.64 Copy 0 Hyderabad Mate SSP
Switching
Point HYD_MATE_SSP_2 blrdrinsspc1 HYD_04 04 10.187.7.65 Copy 1 Hyderabad Mate SSP
HYD_MATE_SSP blrdrinssp HYD_04 Floating IP Hyderabad Mate
10.187.7.66
SSP
SIGTARN HYD_MATE_SIG_1 blrdrsgc0 HYD_04 05 Copy 0 Hyderabad Mate Sig.
10.187.7.67
Signaling Server
Gateway
Server HYD_MATE_SIG_2 blrdrsgc1 HYD_04 06 Copy 1 Hyderabad Mate Sig.
10.187.7.68
Server
HYD_MATE_SIG blrdrsg HYD_04 Floating IP of Hyderabad
10.187.7.69
Mate Sig. Server
Lawful HYD_MATE_LIS_1 blrdrlisc0 HYD_04 07 10.187.7.70 Copy 0 Hyderabad Mate LIS
Interception
Server HYD_MATE_LIS_2 blrdrlisc1 HYD_04 08 10.187.7.71 Copy 1 Hyderabad Mate LIS
HYD_MATE_LIS blrdrlis HYD_04 Floating IP of Hyderabad
10.187.7.72
Mate LIS
Next HYD_MATE_NGEMS blrdrngemsc HYD_04 09 Copy 0 Hyderabad Mate
10.187.7.73
EMS
HYD_MATE_NGEMS blrdrngemsc HYD_04 10 Copy 1 Hyderabad Mate
10.187.7.74
_2 1 NGEMS
HYD_MATE_NGEMS blrdrngems HYD_04 Floating IP of Hyderabad
10.187.7.75
Mate NGEMS
10.187.7.25 to 10.187.7.26

Chapter 4.
10.187.7.42 to 10.187.7.43
10.187.7.59 to 10.187.7.60
10.187.7.76 to 10.187.7.79

HYD_01 01 10.187.7.80
HYD_01 02 10.187.7.81
HYD_01 03 10.187.7.82
HYD_01 04 10.187.7.83
HYD_01 05 10.187.7.84
HYD_01 06 10.187.7.85
HYD_01 07 10.187.7.86
HYD_01 08 10.187.7.87
HYD_01 09 10.187.7.88
HYD_01 10 10.187.7.89
HYD_01 11 10.187.7.90
HYD_01 12 10.187.7.91
HYD_01_ILO1 OA1 10.187.7.92
HYD_01_ILO2 OA2 10.187.7.93
HYD_01_ILO3 SW1 10.187.7.94
HYD_01_ILO4 SW2 10.187.7.95
HYD_02 01 10.187.7.96
HYD_02 02 10.187.7.97
HYD_02 03 10.187.7.98
HYD_02 04 10.187.7.99
HYD_02 05 10.187.7.100
HYD_02 06 10.187.7.101
146 C-DOT MAX-NG

HYD_02 07 10.187.7.102
HYD_02 08 10.187.7.103
HYD_02 09 10.187.7.104
HYD_02 10 10.187.7.105
HYD_02 11 10.187.7.106
HYD_02 12 10.187.7.107
HYD_02_ILO1 OA1 10.187.7.108
HYD_02_ILO2 OA2 10.187.7.109
HYD_02_ILO3 SW1 10.187.7.110
HYD_02_ILO4 SW2 10.187.7.111
HYD_03 01 10.187.7.112
HYD_03 02 10.187.7.113
HYD_03 03 10.187.7.114
HYD_03 04 10.187.7.115
HYD_03 05 10.187.7.116
HYD_03 06 10.187.7.117
HYD_03 07 10.187.7.118
HYD_03 08 10.187.7.119
HYD_03 09 10.187.7.120
HYD_03 10 10.187.7.121
HYD_03 11 10.187.7.122
HYD_03 12 10.187.7.123
HYD_03_ILO1 OA1 10.187.7.124
HYD_03_ILO2 OA2 10.187.7.125
HYD_03_ILO3 SW1 10.187.7.126
HYD_03_ILO4 SW2 10.187.7.127
HYD_04 01 10.187.7.128

Chapter 4.
HYD_04 02 10.187.7.129
HYD_04 03 10.187.7.130
HYD_04 04 10.187.7.131
HYD_04 05 10.187.7.132
HYD_04 06 10.187.7.133
HYD_04 07 10.187.7.134
HYD_04 08 10.187.7.135
HYD_04 09 10.187.7.136
HYD_04 10 10.187.7.137
HYD_04 11 10.187.7.138
HYD_04 12 10.187.7.139
HYD_04_ILO1 OA1 10.187.7.140
HYD_04_ILO2 OA2 10.187.7.141
HYD_04_ILO3 SW1 10.187.7.142
HYD_04_ILO4 SW2 10.187.7.143
HYD_05_ILO1 OA1 10.187.7.144
HYD_05_ILO2 OA2 10.187.7.145
HYD_05_ILO3 SW1 10.187.7.146
HYD_05_ILO4 SW2 10.187.7.147

10.187.7.148 to 10.187.7.149

Client Terminal HYD_CL1 10.187.7.150
1 (LED Panel)
2
148 C-DOT MAX-NG


3
4
5
Printer HYD_PRN1 10.187.7.155

10.187.7.156 to 10.187.7.169

10.187.7.170 to 10.187.7.179
Spare IP Addresses:
10.187.7.180 to 10.187.7.254

Chapter 4.
West Zone Core: BHOPAL (PRIMARY Site)
Self-Copy Chassis 1
Self-Copy Chassis 1
150 C-DOT MAX-NG

BPLPRSBCC0 BPLPRC5C0 BPLPRRATERC0 BPLPRDBC0 BPLPRSPSC0 SPARE

SERV
10.187.4.10 10.187.4.13 10.187.4.16 10.187.4.19 10.187.4.22
ER
BPLPRSBCC1 BPLPRC5C1 BPLPRRATERC1 BPLPRDBC1 BPLPRSPSC1 SPARE

SERV
10.187.4.11 10.187.4.14 10.187.4.17 10.187.4.20 10.187.4.23
ER
SELF-COPY CHASSIS 2
BPLPRC4C0 BPLPRINSSPC0 BPLPRSGC0 BPLPRLISC0 BPLPRNGEMSC0 SPARE

SER
10.187.4.27 10.187.4.30 10.187.4.33 10.187.4.36 10.187.4.39
VER
BPLPRC4C1 BPLPRINSSPC1 BPLPRSGC1 BPLPRLISC1 BPLPRNGEMSC1 SPARE

SER
10.187.4.28 10.187.4.31 10.187.4.34 10.187.4.37 10.187.4.40
VER
MATE COPY CHASSIS 1
PUNDRSBCC0 PUNDRC5C0 PUNDRRATERC0 PUNDRDBC0 PUNDRSPSC0 SPARE

SER
10.187.4.44 10.187.4.47 10.187.4.50 10.187.4.53 10.187.4.56
VER
PUNDRSBCC1 PUNDRC5C1 PUNDRRATERC1 PUNDRDBC1 PUNDRSPSC1 SPARE

SER
10.187.4.45 10.187.4.48 10.187.4.51 10.187.4.54 10.187.4.57
VER

Chapter 4.
MATE COPY CHASSIS 2
PUNDRC4C0 PUNDRINSSPC0 PUNDRSGC0 PUNDRLISC0 PUNDRNGEMSC0 SPARE

SE
10.187.4.61 10.187.4.64 10.187.4.67 10.187.4.70 10.187.4.73
RV
ER
PUNDRC4C1 PUNDRINSSPC1 PUNDRSGC1 PUNDRLISC1 PUNDRNGEMSC1 SPARE

SE
10.187.4.62 10.187.4.65 10.187.4.68 10.187.4.71 10.187.4.74
RV
ER
DNS:- MAXNG.BSNL.IN
Self Copy
ID
Session BPL_SELF_SBC_1 bplprsbcc0 BPL_01 01 10.187.4.10 Copy 0 Bhopal Self SBC
Border
Controller BPL_SELF_SBC_2 bplprsbcc1 BPL_01 09 10.187.4.11 Copy 1 Bhopal Self SBC
BPL_SELF_SBC bplprsbc BPL_01 10.187.4.12 Floating IP Bhopal Self SBC.
Class 5 BPL_SELF_C5_1 bplprc5c0 BPL_01 02 10.187.4.13 Copy 0 Bhopal Self C5 SS
Subscriber
Server BPL_SELF_C5_2 bplprc5c1 BPL_01 10 10.187.4.14 Copy 1 Bhopal Self C5 SS
BPL_SELF_C5 bplprc5 BPL_01 10.187.4.15 Floating IP Bhopal Self C5.
Rating and BPL_SELF_RTR_1 bplprraterc0 BPL_01 03 Copy 0 Bhopal Self Rating
10.187.4.16
Charging Server
Server
BPL_SELF_RTR_2 bplprraterc1 BPL_01 11 Copy 1 Bhopal Self Rating
10.187.4.17
Server
BPL_SELF_RTR bplprrater BPL_01 Floating IP of Bhopal Self
10.187.4.18
Rating Server
Database BPL_SELF_DB_1 bplprdbc0 BPL_01 04 Copy 0 Bhopal Self DB
10.187.4.19
Server Server
BPL_SELF_DB_2 bplprdbc1 BPL_01 12 Copy 1 Bhopal Self DB
10.187.4.20
Server
BPL_SELF_DB bplprdb BPL_01 Floating IP of Bhopal Self
10.187.4.21
DB Server
Subscriber BPL_SELF_PROV_1 bplprspsc0 BPL_01 05 10.187.4.22 Copy 0 Bhopal Self Prov.
152 C-DOT MAX-NG


ID
Provisioning Server
Server
BPL_SELF_PROV_2 bplprspsc1 BPL_01 13 Copy 1 Bhopal Self Prov.
10.187.4.23
Server
BPL_SELF_PROV bplprsps BPL_01 Floating IP of Bhopal Self
10.187.4.24
Prov. Server
Spare Server BPL_01 06
Class 4 BPL_SELF_C4_1 bplprc4c0 BPL_02 01 10.187.4.27 Copy 0 Bhopal Self C4 SS
Trunking
Server BPL_SELF_C4_2 bplprc4c1 BPL_02 09 10.187.4.28 Copy 1 Bhopal Self C4 SS
BPL_SELF_C4 bplprc4 BPL_02 10.187.4.29 Floating IP Bhopal Self C4.
IN Service BPL_SELF_SSP_1 bplprinsspc0 BPL_02 02 10.187.4.30 Copy 0 Bhopal Self SSP
Switching
Point BPL_SELF_SSP_2 bplprinsspc1 BPL_02 10 10.187.4.31 Copy 1 Bhopal Self SSP
BPL_SELF_SSP bplprinssp BPL_02 10.187.4.32 Floating IP Bhopal Self SSP
SIGTARN BPL_SELF_SIG_1 bplprsgc0 BPL_02 03 Copy 0 Bhopal Self Sig.
10.187.4.33
Signaling Server
Gateway
Server BPL_SELF_SIG_2 bplprsgc1 BPL_02 11 Copy 1 Bhopal Self Sig.
10.187.4.34
Server
BPL_SELF_SIG bplprsg BPL_02 Floating IP of Bhopal Self
10.187.4.35
Sig. Server
Lawful BPL_SELF_LIS_1 bplprlisc0 BPL_02 04 10.187.4.36 Copy 0 Bhopal Self LIS
Interception
Server BPL_SELF_LIS_2 bplprlisc1 BPL_02 12 10.187.4.37 Copy 1 Bhopal Self LIS
BPL_SELF_LIS bplprlis BPL_02 Floating IP of Bhopal Self
10.187.4.38
LIS
Next BPL_SELF_NGEMS_ bplprngemsc0 BPL_02 05 Copy 0 Bhopal Self NGEMS
10.187.4.39
Generation 1
EMS
BPL_SELF_NGEMS_ bplprngemsc1 BPL_02 13 Copy 1 Bhopal Self NGEMS
10.187.4.40
2
BPL_SELF_NGEMS bplprngems BPL_02 Floating IP of Bhopal Self
10.187.4.41
NGEMS

Chapter 4.
Mate Copy
ID ID
Session Border BPL_MATE_SBC_1 pundrsbcc0 BPL_03 01 10.187.4.44 Copy 0 Bhopal Mate SBC
Controller
BPL_MATE_SBC_2 pundrsbcc1 BPL_03 02 10.187.4.45 Copy 1 Bhopal Mate SBC
BPL_MATE_SBC pundrsbcc0 BPL_03 Floating IP Bhopal Mate
10.187.4.46
SBC.
Class 5 BPL_MATE_C5_1 pundrc5c0 BPL_03 03 10.187.4.47 Copy 0 Bhopal Mate C5 SS
Subscriber
Server BPL_MATE_C5_2 pundrc5c1 BPL_03 04 10.187.4.48 Copy 1 Bhopal Mate C5 SS
BPL_MATE_C5 pundrc5 BPL_03 10.187.4.49 Floating IP Bhopal Mate C5.
Rating and BPL_MATE_RTR_1 pundrraterc BPL_03 05 Copy 0 Bhopal Mate Rating
10.187.4.50
Charging 0 Server
Server
BPL_MATE_RTR_2 pundrraterc BPL_03 06 Copy 1 Bhopal Mate Rating
10.187.4.51
1 Server
BPL_MATE_RTR pundrrater BPL_03 Floating IP of Bhopal Mate
10.187.4.52
Rating Server
Database BPL_MATE_DB_1 pundrdbc0 BPL_03 07 Copy 0 Bhopal Mate DB
10.187.4.53
Server Server
BPL_MATE_DB_2 pundrdbc1 BPL_03 08 Copy 1 Bhopal Mate DB
10.187.4.54
Server
BPL_MATE_DB pundrdb BPL_03 Floating IP of Bhopal Mate
10.187.4.55
DB Server
Subscriber GURSLE_PROV_1 pundrspsc0 BPL_03 09 Copy 0 Bhopal Mate Prov.
10.187.4.56
Provisioning Server
Server
BPL_MATE_PROV_2 pundrspsc1 BPL_03 10 Copy 1 Bhopal Mate Prov.
10.187.4.57
Server
BPL_MATE_PROV pundrsps BPL_03 Floating IP of Bhopal Mate
10.187.4.58
Prov. Server
Class 4 BPL_MATE_C4_1 pundrc4c0 BPL_04 01 10.187.4.61 Copy 0 Bhopal Mate C4 SS
Trunking
Server BPL_MATE_C4_2 pundrc4c1 BPL_04 02 10.187.4.62 Copy 1 Bhopal Mate C4 SS
BPL_MATE_C4 pundrc4 BPL_04 10.187.4.63 Floating IP Bhopal Mate C4.
IN Service BPL_MATE_SSP_1 pundrinsspc BPL_04 03 Copy 0 Bhopal Mate SSP
10.187.4.64
Switching 0
Point
BPL_MATE_SSP_2 pundrinsspc BPL_04 04 Copy 1 Bhopal Mate SSP
10.187.4.65
1
154 C-DOT MAX-NG


ID ID
BPL_MATE_SSP pundrinssp BPL_04 10.187.4.66 Floating IP Bhopal Mate SSP
SIGTARN BPL_MATE_SIG_1 pundrsgc0 BPL_04 05 Copy 0 Bhopal Mate Sig.
10.187.4.67
Signaling Server
Gateway
Server BPL_MATE_SIG_2 pundrsgc1 BPL_04 06 Copy 1 Bhopal Mate Sig.
10.187.4.68
Server
BPL_MATE_SIG pundrsg BPL_04 Floating IP of Bhopal Mate
10.187.4.69
Sig. Server
Lawful BPL_MATE_LIS_1 pundrlisc0 BPL_04 07 10.187.4.70 Copy 0 Bhopal Mate LIS
Interception
Server BPL_MATE_LIS_2 pundrlisc1 BPL_04 08 10.187.4.71 Copy 1 Bhopal Mate LIS
BPL_MATE_LIS pundrlis BPL_04 Floating IP of Bhopal Mate
10.187.4.72
LIS
Next BPL_MATE_NGEMS_ pundrngems BPL_04 09 Copy 0 Bhopal Mate NGEMS
10.187.4.73
Generation 1 c0
EMS
BPL_MATE_NGEMS_ pundrngems BPL_04 10 Copy 1 Bhopal Mate NGEMS
10.187.4.74
2 c1
BPL_MATE_NGEMS pundrngems BPL_04 Floating IP of Bhopal Mate
10.187.4.75
NGEMS

10.187.4.25 to 10.187.4.26
10.187.4.42 to 10.187.4.43
10.187.4.59 to 10.187.4.60
10.187.4.76 to 10.187.4.79

BPL_01 01 10.187.4.80
BPL_01 02 10.187.4.81
BPL_01 03 10.187.4.82

Chapter 4.
BPL_01 04 10.187.4.83
BPL_01 05 10.187.4.84
BPL_01 06 10.187.4.85
BPL_01 07 10.187.4.86
BPL_01 08 10.187.4.87
BPL_01 09 10.187.4.88
BPL_01 10 10.187.4.89
BPL_01 11 10.187.4.90
BPL_01 12 10.187.4.91
BPL_01_ILO1 OA1 10.187.4.92
BPL_01_ILO2 OA2 10.187.4.93
BPL_01_ILO3 SW1 10.187.4.94
BPL_01_ILO4 SW2 10.187.4.95
BPL_02 01 10.187.4.96
BPL_02 02 10.187.4.97
BPL_02 03 10.187.4.98
BPL_02 04 10.187.4.99
BPL_02 05 10.187.4.100
BPL_02 06 10.187.4.101
BPL_02 07 10.187.4.102
BPL_02 08 10.187.4.103
BPL_02 09 10.187.4.104
BPL_02 10 10.187.4.105
BPL_02 11 10.187.4.106
BPL_02 12 10.187.4.107
BPL_02_ILO1 OA1 10.187.4.108
BPL_02_ILO2 OA2 10.187.4.109
BPL_02_ILO3 SW1 10.187.4.110
156 C-DOT MAX-NG

BPL_02_ILO4 SW2 10.187.4.111

BPL_03 01 10.187.4.112
BPL_03 02 10.187.4.113
BPL_03 03 10.187.4.114
BPL_03 04 10.187.4.115
BPL_03 05 10.187.4.116
BPL_03 06 10.187.4.117
BPL_03 07 10.187.4.118
BPL_03 08 10.187.4.119
BPL_03 09 10.187.4.120
BPL_03 10 10.187.4.121
BPL_03 11 10.187.4.122
BPL_03 12 10.187.4.123
BPL_03_ILO1 OA1 10.187.4.124
BPL_03_ILO2 OA2 10.187.4.125
BPL_03_ILO3 SW1 10.187.4.126
BPL_03_ILO4 SW2 10.187.4.127
BPL_04 01 10.187.4.128
BPL_04 02 10.187.4.129
BPL_04 03 10.187.4.130
BPL_04 04 10.187.4.131
BPL_04 05 10.187.4.132
BPL_04 06 10.187.4.133
BPL_04 07 10.187.4.134
BPL_04 08 10.187.4.135
BPL_04 09 10.187.4.136
BPL_04 10 10.187.4.137

Chapter 4.
BPL_04 11 10.187.4.138
BPL_04 12 10.187.4.139
BPL_04_ILO1 OA1 10.187.4.140
BPL_04_ILO2 OA2 10.187.4.141
BPL_04_ILO3 SW1 10.187.4.142
BPL_04_ILO4 SW2 10.187.4.143
BPL_05_ILO1 OA1 10.187.4.144
BPL_05_ILO2 OA2 10.187.4.145
BPL_05_ILO3 SW1 10.187.4.146
BPL_05_ILO4 SW2 10.187.4.147

10.187.4.148 to 10.187.4.149

Client Terminal BPL_CL1 10.187.4.150
1 (LED Panel)
2
3
4
5
Printer BPL_PRN1 10.187.4.155

10.187.4.156 to 10.187.4.169
158 C-DOT MAX-NG


10.187.4.170 to 10.187.4.179
Spare IP Addresses:
10.187.4.180 to 10.187.4.254
Note: IP list of MAX-NG core sites are also available on C-DOT MAX-NG Helpline Portal.
North Zone Core: Gurgaon (PRIMARY Site)
Self-Copy Chassis 1

Chapter 4.
North Zone Core: GURGAON (PRIMARY Site)
IP Range: (10.187.0.0/25) VLAN ID:

160 C-DOT MAX-NG

Netmask: 255.255.255.128
Self PE Port (at Gurgaon): eth 0:

Self PE Port (at Gurgaon): eth1:
Adj. PE Port (at Ambala): eth 0:
Adj. PE Port (at Ambala): eth1:


LAN GUR_L3SW1_P 14A120 10.187.0.1
Switch_C0 0
LAN GUR_L3SW1_P 14A128 10.187.0.3
Switch_C0 1
LAN GUR_L3SW2_P 14A124 10.187.0.4
Switch_C1 0
LAN GUR_L3SW2_P 14A146 10.187.0.5
Switch_C1 1

10.187.0.6 to 10.187.0.9
SELF COPY

ID ID
Session GUR_SELF_SBC_1 GUR_01 01 10.187.0.10 Copy 0 Gurgaon Self SBC
Border
GUR_SELF_SBC_2 GUR_01 02 10.187.0.11 Copy 1 Gurgaon Self SBC

Chapter 4.
Controller GUR_SELF_SBC GUR_01 Floating IP Gurgaon Self

10.187.0.12
SBC.
Class 5 GUR_SELF_C5_1 GUR_01 03 Copy 0 Gurgaon Self C5
10.187.0.13
Subscriber SS
Server
GUR_SELF_C5_2 GUR_01 04 Copy 1 Gurgaon Self C5
10.187.0.14
SS
GUR_SELF_C5 GUR_01 Floating IP Gurgaon Self
10.187.0.15
C5.
Rating and GUR_SELF_RTR_1 GUR_01 05 Copy 0 Gurgaon Self
10.187.0.16
Server
GUR_SELF_RTR_2 GUR_01 06 Copy 1 Gurgaon Self
10.187.0.17
Rating Server
GUR_SELF_RTR GUR_01 Floating IP of Gurgaon
10.187.0.18
Self Rating Server
Database GUR_SELF_DB_1 GUR_01 07 Copy 0 Gurgaon Self DB
10.187.0.19
Server Server
GUR_SELF_DB_2 GUR_01 08 Copy 1 Gurgaon Self DB
10.187.0.20
Server
GUR_SELF_DB GUR_01 Floating IP of Gurgaon
10.187.0.21
Self DB Server
Subscriber GUR_SELF_PROV_1 GUR_01 09 Copy 0 Gurgaon Self
10.187.0.22
Server
GUR_SELF_PROV_2 GUR_01 10 Copy 1 Gurgaon Self
10.187.0.23
Prov. Server
GUR_SELF_PROV GUR_01 Floating IP of Gurgaon
10.187.0.24
Self Prov. Server
Spare Server GUR_01 11
Class 4 GUR_SELF_C4_1 GUR_02 01 Copy 0 Gurgaon Self C4
10.187.0.27
Trunking SS
Server
GUR_SELF_C4_2 GUR_02 02 Copy 1 Gurgaon Self C4
10.187.0.28
SS
GUR_SELF_C4 GUR_02 Floating IP Gurgaon Self
10.187.0.29
C4.
162 C-DOT MAX-NG

IN Service GUR_SELF_SSP_1 GUR_02 03 10.187.0.30 Copy 0 Gurgaon Self SSP

Switching
Point GUR_SELF_SSP_2 GUR_02 04 10.187.0.31 Copy 1 Gurgaon Self SSP
GUR_SELF_SSP GUR_02 Floating IP Gurgaon Self
10.187.0.32
SSP
SIGTARN GUR_SELF_SIG_1 GUR_02 05 Copy 0 Gurgaon Self Sig.
10.187.0.33
Signaling Server
Gateway
Server GUR_SELF_SIG_2 GUR_02 06 Copy 1 Gurgaon Self Sig.
10.187.0.34
Server
GUR_SELF_SIG GUR_02 Floating IP of Gurgaon
10.187.0.35
Self Sig. Server
Lawful GUR_SELF_LIS_1 GUR_02 07 10.187.0.36 Copy 0 Gurgaon Self LIS
Interception
Server GUR_SELF_LIS_2 GUR_02 08 10.187.0.37 Copy 1 Gurgaon Self LIS
GUR_SELF_LIS GUR_02 Floating IP of Gurgaon
10.187.0.38
Self LIS
Next GUR_SELF_NGEMS_ GUR_02 09 Copy 0 Gurgaon Self
10.187.0.39
Generation 1 NGEMS
EMS
GUR_SELF_NGEMS_ GUR_02 10 Copy 1 Gurgaon Self
10.187.0.40
2 NGEMS
GUR_SELF_NGEMS GUR_02 Floating IP of Gurgaon
10.187.0.41
Self NGEMS

10.187.0.25 to 10.187.0.26
10.187.0.42 to 10.187.0.43

Chapter 4.

Client Terminal GUR_CL1 152044 00:50:43:DE:34:3A 10.187.0.44
1 (LED Panel)
Client Terminal GUR_CL2 10.187.0.45
2
Client Terminal GUR_CL3 152064 00:50:43:7A:2B:38 10.187.0.46
3
Client Terminal GUR_CL4 152056 00:50:43:0A:29:38 10.187.0.47
4
Client Terminal GUR_CL5 152060 00:50:43:7C:14:39 10.187.0.48
5
Printer GUR_PRN1 3221052713 9C:93:7E:21:31:6E 10.187.0.49

GUR_01 01 SGH439WKWH C4:34:6B:CA:D9:F0
GUR_01 02 SGH439WN6W C4:34:6B:CA:9B:28
GUR_01 03 SGH439WKX8 C4:34:6B:CA:6A:A8
GUR_01 04 SGH439WN6S C4:34:6B:CA:FA:68
GUR_01 05 SGH439WN50 C4:34:6B:CA:65:78
GUR_01 06 SGH439WN6X C4:34:6B:CA:55:40
GUR_01 07 SGH439WN5C C4:34:6B:CA:87:A0
GUR_01 08 SGH439WN4V C4:34:6B:CA:D9:B0
GUR_01 09 SGH439WKWS C4:34:6B:CA:3A:16
GUR_01 10 SGH439WN2J C4:34:6B:CA:0A:60
GUR_01 11 SGH439WN35 C4:34:6B:CA:D1:78
GUR_01 12 SGH439WN79 C4:34:6B:CA:E7:58
GUR_01_ILO1 OA1 10.187.0.92
GUR_01_ILO2 OA2 10.187.0.93
GUR_01_ILO3 SW1 10.187.0.94
GUR_01_ILO4 SW2 10.187.0.95
164 C-DOT MAX-NG

GUR_02 01 SGH439WN2W C4:34:6B:CA:A3:58

GUR_02 02 SGH439WN29 14:58:D0:59:78:90
GUR_02 03 SGH439WN31 C4:34:6B:CA:D4:18
GUR_02 04 SGH439WN54 C4:34:6B:CA:6A:60
GUR_02 05 SGH439WN4C C4:34:6B:CA:04:70
GUR_02 06 SGH439WN4P C4:34:6B:CA:89:C0
GUR_02 07 SGH439WN5B C4:34:6B:CA:C6:90
GUR_02 08 SGH439WN72 C4:34:6B:CA:80:80
GUR_02 09 SGH439WN7J 14:58:D0:59:3A:98
GUR_02 10 SGH439WN4N C4:34:6B:CA:23:38
GUR_02 11 SGH439WN2D C4:34:6B:CA:D9:38
GUR_02 12 SGH439WN5H C4:34:6B:CA:B8:68
GUR_02_ILO1 OA1 10.187.0.108
GUR_02_ILO2 OA2 10.187.0.109
GUR_02_ILO3 SW1 10.187.0.110
GUR_02_ILO4 SW2 10.187.0.111

10.187.0.50 to 10.187.0.65

10.187.0.66 to 10.187.0.79
Spare IP Addresses:
10.187.0.112 to 10.187.0.126

Chapter 4.
North Zone Core: GURGAON (MATE)
IP Range: (10.187.0.0/25) VLAN ID:

Netmask: 255.255.255.128
Self PE Port (at Gurgaon): eth 0:

Self PE Port (at Gurgaon): eth1:
Adj. PE Port (at Ambala): eth 0:
Adj. PE Port (at Ambala): eth1:


LAN GUR_L3SW1_P 14A120 10.187.0.129
Switch_C0 0
LAN GUR_L3SW1_P 14A128 10.187.0.131
Switch_C0 1
LAN GUR_L3SW2_P 14A124 10.187.0.132
Switch_C1 0
LAN GUR_L3SW2_P 14A146 10.187.0.133
Switch_C1 1
166 C-DOT MAX-NG


10.187.0.134 to 10.187.0.137
MATE COPY

ID ID
Session GUR_MATE_SBC_1 GUR_03 01 Copy 0 Gurgaon Mate
Border 10.187.0.138 SBC
Controller
GUR_MATE_SBC_2 GUR_03 02 Copy 1 Gurgaon Mate
10.187.0.139 SBC
GUR_MATE_SBC GUR_03 Floating IP Gurgaon
10.187.0.140 Mate SBC.
Class 5 GUR_MATE_C5_1 GUR_03 03 Copy 0 Gurgaon Mate
Subscriber 10.187.0.141 C5 SS
Server
GUR_MATE_C5_2 GUR_03 04 Copy 1 Gurgaon Mate
10.187.0.142 C5 SS
GUR_MATE_C5 GUR_03 Floating IP Gurgaon
10.187.0.143 Mate C5.
Rating and GUR_MATE_RTR_1 GUR_03 05 Copy 0 Gurgaon Mate
Charging 10.187.0.144 Rating Server
Server
GUR_MATE_RTR_2 GUR_03 06 Copy 1 Gurgaon Mate
10.187.0.145 Rating Server
GUR_MATE_RTR GUR_03 Floating IP of Gurgaon
10.187.0.146 Mate Rating Server
Database GUR_MATE_DB_1 GUR_03 07 Copy 0 Gurgaon Mate
Server 10.187.0.147 DB Server
GUR_MATE_DB_2 GUR_03 08 Copy 1 Gurgaon Mate
10.187.0.148 DB Server
GUR_MATE_DB GUR_03 Floating IP of Gurgaon
10.187.0.149 Mate DB Server
Subscriber GURSLE_PROV_1 GUR_03 09 Copy 0 Gurgaon Mate
Provisioning 10.187.0.150 Prov. Server
Server
GUR_MATE_PROV_2 GUR_03 10 10.187.0.151 Copy 1 Gurgaon Mate

Chapter 4.
Prov. Server
GUR_MATE_PROV GUR_03 Floating IP of Gurgaon
10.187.0.152 Mate Prov. Server
Class 4 GUR_MATE_C4_1 GUR_04 01 Copy 0 Gurgaon Mate
Trunking 10.187.0.155 C4 SS
Server
GUR_MATE_C4_2 GUR_04 02 Copy 1 Gurgaon Mate
10.187.0.156 C4 SS
GUR_MATE_C4 GUR_04 Floating IP Gurgaon
10.187.0.157 Mate C4.
IN Service GUR_MATE_SSP_1 GUR_04 03 Copy 0 Gurgaon Mate
Switching 10.187.0.158 SSP
Point
GUR_MATE_SSP_2 GUR_04 04 Copy 1 Gurgaon Mate
10.187.0.159 SSP
GUR_MATE_SSP GUR_04 Floating IP Gurgaon
10.187.0.160 Mate SSP
SIGTARN GUR_MATE_SIG_1 GUR_04 05 Copy 0 Gurgaon Mate
Signaling 10.187.0.161 Sig. Server
Gateway
Server GUR_MATE_SIG_2 GUR_04 06 Copy 1 Gurgaon Mate
10.187.0.162 Sig. Server
GUR_MATE_SIG GUR_04 Floating IP of Gurgaon
10.187.0.163 Mate Sig. Server
Lawful GUR_MATE_LIS_1 GUR_04 07 Copy 0 Gurgaon Mate
Interception 10.187.0.164 LIS
Server
GUR_MATE_LIS_2 GUR_04 08 Copy 1 Gurgaon Mate
10.187.0.165 LIS
GUR_MATE_LIS GUR_04 Floating IP of Gurgaon
10.187.0.166 Mate LIS
Next GUR_MATE_NGEMS_ GUR_04 09 Copy 0 Gurgaon Mate
Generation 1 10.187.0.167 NGEMS
EMS
GUR_MATE_NGEMS_ GUR_04 10 Copy 1 Gurgaon Mate
2 10.187.0.168 NGEMS
GUR_MATE_NGEMS GUR_04 10.187.0.169 Floating IP of Gurgaon
168 C-DOT MAX-NG

Mate NGEMS

10.187.0.153 to 10.187.0.154
10.187.0.170 to 10.187.0.171

GUR_03 01 SGH439WN33 C4:34:6B:CA:88:00
GUR_03 02 SGH439WKX6 C4:34:6B:CA:09:28
GUR_03 03 SGH439WN7B C4:34:6B:CA:78:68
GUR_03 04 SGH439WN21 C4:34:6B:CA:00:C0
GUR_03 05 SGH439WN75 C4:34:6B:CA:80:78
GUR_03 06 SGH439WN4Y C4:34:6B:CA:A3:50
GUR_03 07 SGH439WKX4 14:58:D0:59:05:A8
GUR_03 08 SGH439WN27 C4:34:6B:CA:89:00
GUR_03 09 SGH439WN4L C4:34:6B:CA:18:F8
GUR_03 10 SGH439WKWK 14:58:D0:59:D6:00
GUR_03 11 SGH439WN5F C4:34:6B:CA:99:E8
GUR_03 12 SGH439WN7D C4:34:6B:CA:80:38
GUR_03_ILO1 OA1 10.187.0.220
GUR_03_ILO2 OA2 10.187.0.221
GUR_03_ILO3 SW1 10.187.0.222
GUR_03_ILO4 SW2 10.187.0.223
GUR_04 01 SGH439WN2T C4:34:6B:CA:15:20
GUR_04 02 SGH439WN2Y C4:34:6B:CA:FA:78

Chapter 4.
GUR_04 03 SGH439WN57 C4:34:6B:CA:0A:D0

GUR_04 04 SGH439WN28 C4:34:6B:CA:AF:A0
GUR_04 05 SGH439WN4H C4:34:6B:CA:B6:40
GUR_04 06 SGH439WN39 C4:34:6B:CA:18:F0
GUR_04 07 SGH439WN7F C4:34:6B:CA:77:A8
GUR_04 08 SGH439WN23 C4:34:6B:CA:6B:58
GUR_04 09 SGH439WN2F C4:34:6B:CA:23:28
GUR_04 10 SGH439WN53 C4:34:6B:CA:77:C0
GUR_04 11 SGH439WN37 C4:34:6B:CA:51:E8
GUR_04 12 SGH439WKX0 14:58:D0:53:F4:30
GUR_04_ILO1 OA1 10.187.0.236
GUR_04_ILO2 OA2 10.187.0.237
GUR_04_ILO3 SW1 10.187.0.238
GUR_04_ILO4 SW2 10.187.0.239
170 C-DOT MAX-NG

GUR_05_ILO1 OA1 10.187.0.240

GUR_05_ILO2 OA2 10.187.0.241
GUR_05_ILO3 SW1 10.187.0.242
GUR_05_ILO4 SW2 10.187.0.243
10.187.0.244 to 10.187.0.245

10.187.0.172 to 10.187.0.192

10.187.0.193 to 10.187.0.207
Spare IP Addresses:
10.187.0.246 to 10.187.0.255

Chapter 4.
Appendix-R
MIGRATION
DOCUMENT
FOR
CONVERTING
MBM
TO
MAX-NG
172 C-DOT MAX-NG

INTRODUCTION
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.

Chapter 4.
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 completing 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.
 Intimation for WAN IP provisioning in BSNL IP/MPLS network.
 Verification of BOM (Bill of Material)
 DATA Extraction by BSNL and communication to NCNGN for frozen data
 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.
174 C-DOT MAX-NG

INTRODUCTION
 LAGU Installation
Post Migration
11. Call Verification

12. Site Observation
13. AT Test Cases

Chapter 4.
Detailed Activities and Timelines for Pre Migration
Site-Survey
1) 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.
2) This activity requires 2-3 days.
3) 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
1. 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.
2. 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.
3. This will require 2 to 3 days and time may vary depending on number of sites.
Verification of BOM
a) Verify the delivered equipment as per the BOM and this will require 4 hours
approximately.
DATA Creation at Core Site
b) 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.
176 C-DOT MAX-NG

INTRODUCTION
c) 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.

Chapter 4.
Software Installation and configuration (One Day)
1. 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.
1. 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

I. 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
1. 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.
2. Steps for Migration of RSU Site
i. Shut off the Power of the BM to be migrated.
ii. Un-screw the BPU and TSU frame.
iii. Remove the cables connected at the back plane of TSU and BPU. These cables are
TT cables, TB cables and power cables.
iv. Remove the filters of BPU and TSU frames from the BUS BAR.
v. Pull out the TSU and BPU frames from the BM cabinet.
vi. Install the new filter box in place of BPU filter boxes at Copy 0 and Copy 1 side of
Bus bar.
vii. For physical installation of LAGU chassis, a fixture needs to be installed first.
178 C-DOT MAX-NG

INTRODUCTION
viii. This fixture will hold the LAGU chassis vertically. Now in this fixture install the
LAGU chassis
ix. Put the LAGU chassis in the fixture and screw it properly.
x. TT cables at TU side will remain same.
xi. At LAGU end TT cables have to be connected in position 1A, 1B, 2A and 2B
connectors.
xii. 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.

Chapter 4.
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

A. 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.
a) Site Observation
Site will be kept under observation for 24 hours to check stability.
b) 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.
180 C-DOT MAX-NG

INTRODUCTION
ANNEXURE-I

Chapter 4.
Technical Site Survey Sheet
ZONE Name __________
Circle Name __________
Site Name __________
Self-Point Code __________
Name of SDCA __________
STD Code __________

Number of other SDCA parented
__________
Area Codes of other SDCA (if
any) __________
Site Name : __________
Date of Preparation : __________
Prepared by (Name & Designation of BSNL
Official)
__________
182 C-DOT MAX-NG

INTRODUCTION
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 NAME MOBILE NUMBER EMAIL Address
PERSONAL
JTO
SDE/SDO
DE
DGM
GM
Table 2.0: Contact Details of BSNL Officials

Chapter 4.
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
184 C-DOT MAX-NG

INTRODUCTION
19 Area codes of BM
Table 3.1: Detail of Exchange Configuration

Chapter 4.
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.
Type of Workin
Name
RBM /Co-located Exchange/ Connectivit Equipped g
of RBM Area Code
BM number y (E1 or Capacity Capacit
Site Subscriber
STM) y
Level
Table 4.1: Detail of Remote BM

Note: Kindly add the required numbers of row depending upon the RSU and co-located BM
working.
186 C-DOT MAX-NG

INTRODUCTION
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 Equipped Working Subs Level

Name of AN-RAX Area Code
Number Capacity capacity working
Table 5.1: Detail of AN-RAX

Note: Kindly add the required numbers of row depending upon the AN-RAX working.

Chapter 4.
6 PRI Related Information

Fill the details of PRI parented to the MBM along with the exchange code of the PRI subscriber.
Principal Directory Number Number of

of DDI Group Digits Directory Number
S.No.
(DIRNO)
(PDDI) (NUM-DGTS)
Table 6.1: Detail of PRI

Note: Kindly add the required numbers of row depending upon the PRI working .
188 C-DOT MAX-NG

INTRODUCTION
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.
BM-1 BM-1 BM-2 BM-2 BM-2 BM-3

LINE LM LM LINE LM VU
BM-4 BM-5 BM-6 CM- BM-7 BM-8

XL
TRK SUM VU TRK VU
BM-9 BM-9 BM-9
IOP ROOM
LM LINE LM
Fig. 7.0 Reference diagram of Exchange Layout

Chapter 4.
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.
190 C-DOT MAX-NG

INTRODUCTION
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. Destination Exchange Destination Number of Number of

No. Point Code E1s 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


Chapter 4.
Fig. 8.2 Network Diagram

Fig. 8.2: Network Connectivity Diagram
192 C-DOT MAX-NG

INTRODUCTION
Appendix-S
Following points to be followed for Smooth Migration of Site

xxix) Before starting MAX-NG Migration, a PC with Internet connection is required.
Connect PC to internet and go through MAX-NG Videos available on the below google
drive link.
xxx) Please fill Site Survey Sheet and Checklist as per attached document in which all
details related to BMs,RSU,AN-RAXs and POIs, etc. are required
xxxi) Please read MAX-NG General Description document to have an Overview of MAX-
NG Migration activity and Network Connectivity as per attached Document
xxxii) For connecting MAX-NG access network to Core network, WAN (definition given
below) interfaces are required to be defined and created in IP/MPLS network.
Accordingly, please send attached WAN IP and LAN IP to concerned teams for
configuration of specific site planned for migration.
Definitions:
xv) A wide area network (WAN) is a geographically distributed private
xvi) A local area network (LAN) is a network that connects computers and other
devices in a relatively small area, typically a single building or a group of
buildings. Most LANs connect workstations and personal computers and enable
users to access data and devices (e.g., printers and modems) anywhere on the
network.
xvii) A virtual LAN (VLAN) is any broadcast domain that is partitioned and
isolated in a computer network at the data link layer (OSI (Open System
Interconnections) layer 2). ... VLANs allow network administrators to group hosts
together even if the hosts are not on the same network switch.
xviii) The Open Systems Interconnection model (OSI model) is a conceptual model
that characterizes and standardizes the communication functions of a
seven layers.
xix) VLAN (Virtual Local Area Network) Tagging is the practice of inserting a
VLAN ID into a packet header in order to identify which VLAN the packet

Chapter 4.
belongs to. More specifically, switches use the VLAN ID to determine which
port(s), or interface(s), to send a broadcast packet to. Tagging (Switching) is a
flexible and efficient network communication mechanism used to transmit
Internet Protocol (IP) traffic over a telecommunications network.
xx) Switches create a network. Routers connect networks. A router links computers to
the Internet, so users can share the connection.
xxi) The main purpose of a virtual network is to enable a data center or service
provider network to provision the most suitable and efficient networking
structure for the applications it hosts – and to alter that structure as conditions
warrant, using software rather than requiring physical changes in connections to
hardware.
xxxiii) Multiprotocol Label Switching (MPLS) is a type of data-carrying technique for high-
xxxiv) As per PAN INDIA IP planning, WAN IPs & LAN IPs have been already
planned.LAGU & CACU Systems are required to be configured and allowed in
IP/MPLS network with unique WAN IP and LAN IP for specific site planned for
migration.
xxxv) Important points which should be taken care off before and during migration
activity are as follows:
o) MAX-NG General Description document having overview of MAX-NG
Integration, etc.)
p) General Administrative document having administrative details for
q) Main LAN Switch (MLS) document having description, details and
r) WAN IP & LAN IP details required to be configured in BSNL/IP MPLS
network.
s) Installation and configuration documents of LAGU & CACU System.
t) Procedure approved by Director, CFA, BSNL.
u) Matrix attached for Call Testing post migration.
xxxvi) As per document at S.No. 5, Template has to be filled by ITPC (IT Project Circle)
which takes approximately 3-4 days and need to be verified by Exchange Incharge and
194 C-DOT MAX-NG

INTRODUCTION
same will be sent to respective circle teams for migration activity. In case of any
discrepancies, incharge will communicate same to ITPC and nodal team.
xxxvii) As per attached document, this will give basic idea of migration and network.
xxxviii) Please follow Installation and configuration documents of LAGU & CACU System.
xxxix) Note: Exchange person will take ED & BD backup before actual migration and keep
it in safe custody.
xl) After preparation and installation of CACU and LAGU System, a sample call is tested
from access network to different PSTN and Mobile networks as per Matrix attached in
mail. Make a sample call from SIP phone connected to CACU system and PSTN phone
connected to each LAGU System (Co-located & Remotely located Unit).
xli) Site Monitoring for 2 to 3 days.

Chapter 4.
Appendix-T
Data Retrofit Steps using LAG CLI.
1. Login on LAG.
2. Shutdown LAG.
3. Remove Shared memory

ipcs –m
ipcrm shm < pids obtained from above command>
remove data( bak files also)

shutdown standby copy of LAG
4. remove data( bak files also)
5. Shutdown Standby Copy of LAG. (Mandatory)
6. Delete node of LAG if discovered on EMS.(MUST)
7. Bring the LAG simplex copy up.
8. Steps for lagbulk script:
Assumptions:-
i)In Exchange Code info Sheet Type is given as "LAG" [column 8]
196 C-DOT MAX-NG

INTRODUCTION
ii)In Subscriber info

For Time / Untimed hotline respective column should be filled as "Y/N" [column 32 & 33]
For Call waiting respective column should be filled as

"Y/N" [column 34]
Procedure for the Generation of the LAG Scripts
STEP 1 : Open the "Exchange Code info" Sheet and save it as "Excod.txt" after removing the
Header. Field delimiter is to be given as ";".
STEP 2 : Open the "Equipage info" Sheet and save it as "Eqpinfo.txt" after removing the Header.
Field delimiter is to be given as ";".
STEP 3 : Open the "subscriber Info" Sheet and save it as "Subinfo.txt" after removing the
Header. Field delimiter is to be given as ";".
STEP 4 : Open the "Centrex info" Sheet and save it as "Ctxinfo.txt" after removing the Header.
STEP 5 : Open the "Hotline info" Sheet and save it as "Htlninfo.txt" after removing the Header.
STEP 6 : Make a directory LAG_BULK.
STEP 7 : Move all the above txt files in to it.
STEP 8 : Copy the script "lagbulk.sh" in this directory.
STEP 9 : Give command chmod +x lagbulk.sh
STEP 10 : Run lagbulk.sh as "./lagbulk.sh"

Chapter 4.
LAG wise bulk script is the output of this script like LAG_1.lst, LAG_2.lst etc.
#############################################################
#############################################################
#############################################################
#############################################################
9. Ftp .lst file to respective LAG (mmc) in path

/usr/local/bin/lag/AGENT/lagagent/
10. Open LAG CLI (login root password public)
12. Give command mod-general-param to create exchange code.

mod general_params dirno_len=6 exc_code =2 country_code =91 area_code=1477
(The above command is the example of Nimbahera exchange for BM-1 . Fill data according to
sites. Take the help from core team for this information)
13. Give command bulk cfg file = LAG_1.lst

(here data of BM-1 is getting retrofit)
14. Search for fail in file LAG_1.lst.log in path

/usr/local/bin/lag/AGENT/lagagent directory on LAG.
15. Bring All Tics inservice with command

force unit_ins tic01-0
so on for all the tic ids
16. Bring All terminal cards inservice with command

force line_card_ins rack=1 frame=1 slot=3
So on for all the line cards in all the frames
198 C-DOT MAX-NG

INTRODUCTION
17. Run DB utility on LAG

Steps for DB Utility to activate and register call waiting facility (Excluding CCB subscribers):
Copy db_CALL_WTNG_ACT.exe to the path /mmc/usr/local/bin/lag/AD-DB/ on LAGU-NGTJ

card.
Go to the above mentioned path and execute the utility.
chmod 777 db_CALL_WTNG_ACT.exe
#./db_CALL_WTNG_ACT.exe
Select the option 153.
Enter the BM no. as '0'.(Be careful….BM no should be ‘0’ (ZERO)
4. The directory numbers of the subscribers for whom the utility successfully executed can be
seen in /tmp/db.output file.
5. Apart from this, the number of subscribers for which the utility was successful can be seen
using the command
# wc -l /tmp/db.output
6. Now shutdown LAG and restart again.
Note : Run data creation script .lst from CLI interface only not from EMS GUI.

Chapter 4.
Data Migration from MAX to MAXNG
At Core Site and strictly for Core Administrator

Prerequisite to run Migration utility:
NOTE: Data of the exchange to be migrated (subscribers, emergency zones, admin, language
group etc) should not be present in the C5 DB before migration
Following data should be created in C5 DB through C5 GUI before running migration utility :
 Country data
 State data
 City data for each Area Code in a Exchange
 Language group data
Note: Language Group Naming Nomenclature should be like Group_<exchange_name>. For
Example: If Exchange to be migrated is Nuh, then Language group created should be
“Group_Nuh”.
 Mapping of Area Codes in GroupAreaCode
 Area Code Group Name: North_GGN (for example)
 Route Device Name:
Assumptions :
B. Excel Sheet should be converted to CSV Files according to the following naming
convention.
C. CSV file should contain data exchange wise i.e there should be separate file for each
exchange.
D. All set of file should exist during bulk utility run. If data is not present in any sheet, a blank
.CSV file should be created
Naming convention for CSV files used by Migration utility:

3. Master Migration Data(Exchange Info) : exchange_<exchange name>.csv
4. Emergency Zone Creation : emg_zone_<exchange name>.csv
200 C-DOT MAX-NG

INTRODUCTION
5. Subscriber Creation : subs_<exchange name>.csv

6. Centrex Creation : ctx_<exchange name>.csv
7. Hunt Group Creation : hgp_<exchange name>.csv
8. PRI Creation : pri_<exchange_name>.csv
For Example for Exchange Rohtak, files will be as follows

exchange_Rohtak.csv
emg_zone_Rohtak.csv
subs_Rohtak.csv
ctx_Rohtak.csv
hgp_Rohtak.csv
pri_Rohtak.csv
For generating csv file , open excel sheet in Microsoft Excel in Linux / Windows PC.
Save each sheet in TEXT (MS-DOS) and rename to csv. For example, exchange_Rohtak will be
saved in TEXT MS-DOS and later this will be renamed to exchange_Rohtak.csv.
Likewise all sheets will be first saved in TEXT (MS-DOS) and later this will be renamed with csv
extension i.e. .csv
Copy the .csv files to the Service Provisioning server
Make a Directory <exchange_name> in the path /home/cdot/Max_Migration

$ cd /home/cdot
$ mkdir Max_Migration
$ cd Max_Migration
$ mkdir <exchange_name>
Copy the .csv files (6 files) in the path /home/cdot/Max_Migration<exchange_name>
Note: Open each file & delete blank lines & columns (if present) & Save the files.
Copying the DataMigration.tar to the SP server

Chapter 4.
Copy ‘PATCH11-Over-MXMIGRL1_1_1.2_1-Patch-For-NGSM-New-Data-
Template.tar’ in directory /home/cdot/Max_Migration from CRS server under MAX-
NG Network project ,MXMIGRL1_1_1.2_1 product & patch ‘PATCH11-Over-
MXMIGRL1_1_1.2_1-Patch-For-NGSM-New-Data-Template.tar’.
Installation & Run procedure of Migration Utility for DataMigration
Installation Procedure:
Untar patch file ‘PATCH11-Over-MXMIGRL1_1_1.2_1-Patch-For-NGSM-New-Data-

Template.tar’
$ cd /home/cdot/Max_Migration
$ tar -xvf PATCH11-Over-MXMIGRL1_1_1.2_1-Patch-For-NGSM-New-Data-Template.tar
Untar DataMigration.tar
$ cd /home/cdot/Max_Migration
$ tar -xvf DataMigration.tar
Run install.sh [#./install.sh] as root user

$ cd /home/cdot/Max_Migration/DataMigration
$ ./install.sh
Enter the values of C5 Database IP, NGSM IP and Rater IP when prompted.
Choose the Zone for which configuration is to be done
Utility will be installed in /opt/CDOT-GUI/dataMigration
202 C-DOT MAX-NG

INTRODUCTION
Run Migration.sh
Go to installation directory
$ cd /opt/CDOT-GUI/dataMigration
Run runMigration.sh [#./runMigration.sh]
$ ./runMigration.sh
Enter the absolute path for CSV files and exchange name when prompted.
Note: This script will create data at C5 and Rater through CSV files
Run procedure of Audit Utility for DataMigration
To add a new LAG node for Audit:
1. Go to installation directory [#cd /opt/CDOT-GUI/dataMigration]

2. Run updateTmpLAGSts.sh[#./updateTmpLAGSts.sh]
$ ./updateTmpLAGSts.sh
Enter values for C5 IP and IP of this LAG as prompted.
(To be repeated for multiple LAG)
To add a new V5 node for Audit:
1. Go to installation directory [#cd /opt/CDOT-GUI/dataMigration]


Chapter 4.
2. Run updateTmpV5Sts.sh[#./updateTmpV5Sts.sh]
$ ./updateTmpV5Sts.sh
Enter values for C5 IP and IP of this V5 as prompted.
(To be repeated for multiple V5)
Run Utility
Run runUtility.sh (with ampersand) [#./runUtility.sh &]

$ ./runUtility.sh &
Note: This script will run as daemon to sync subscriber status as in CSV file for Subscribers
created on LAG and Rater
Post Migration
Restart the C5 processes (ngcpe,ngfs,ngms)
Create Charging data for the Site Code of migrated exchange in Rater
Post Migration Verification
Through C5 GUI
Check Subscriber count

Check Emergency zones & emergency numbers mapped
Check count of LAG, V5 & PRI Subscribers created.
Check Centrex & Hunt Groups created
204 C-DOT MAX-NG

INTRODUCTION
Check Billing Zone created
Through Rater GUI
Check Subscriber count

Check PRI & Hunt Group
Note: It is possible that PRI might not be created on Rater, so if not created, it needs to be created
manually through C5 GUI
Check all types of calls (Local, STD, ISD, Mobile, STD Mobile, IN, Emergency etc)
from all the nodes
Check CDRs on C5 & Rater
Check Charging on Rater

Chapter 4.
Appendix-U
Procedure to Shutdown
Processes in CACU Cards
206 C-DOT MAX-NG

INTRODUCTION
Appendix-U
For SLM card,
# Login into card :

# ssh root@ < IP address of SLM card>
# cd /jffs2_ram/SLM/bin
# ./shm_shutdown.sh
Shm.exe processes will be shut down. After this messages in minicom terminal will be stopped.
For EBM card,

Login into card :
# ssh root@<IP address of EBM card>
# cd /jffs2_ram/eeb/bin
# ./eeb_stop.sh
For NGTJ card,
Login into card

# ssh root@<IP address of NGTJ card>
# cd /mmc/ngtj
# ./stopall

Chapter 4.
Appendix-V
Procedure to Shutdown
Processes in LAGU Cards
208 C-DOT MAX-NG

INTRODUCTION
In LAGU System ,
Procedure to give Soft Shutdown / Soft reboot in NGTJ card
1. Login into NGTJ card by ssh using self IP of NGTJ card i.e. selfeth0
of copy-0 and selfeth0 of copy-1 . In copy-0 , you can find selfeth0 and
mateeth0 in lag_sys.conf file present in /mmc/etc path.
#chroot /mmc
#cat /etc/lag_sys.conf
# ssh root@<IP address ( self eth0) of NGTJ card>
Default password will be root.
If you have logged in through FVIP (floating IP ) , please login through selfeth0 of same copy
mentioned in lag_sys.conf file.
2. Go to /mmc/etc path where lag_shutdown.sh script is present.
#cd /mmc/etc
#./lag_shutdown.sh 1 or 2 ( 1 for Simplex when only one copy is working and 2 for Duplex
when both copies are working i.e. copy-0 and copy-1.)
3. For starting processes in NGTJ card or soft start , go to same
/mmc/etc path and give following commands.
#cd /mmc/etc ( for going to /mmc/etc/ path )
#./lag_restart.sh ( processes will restart ).
After this , check whether processes have come UP or not using following procedure as follows:
# tail –f /tmp/lag_init.log
Important Note : Commands will be given exactly as mentioned above
otherwise error may come.

Chapter 4.
Procedure to give Hard Shutdown in NGTJ card
1. Login into NGTJ card by ssh using self IP of NGTJ card i.e. selfeth0
of copy-0 and selfeth0 of copy-1 . In copy-0 , you can find selfeth0 and
mateeth0 in lag_sys.conf file present in /mmc/etc path.
#chroot /mmc
#cat /etc/lag_sys.conf
# ssh root@<IP address ( self eth0) of NGTJ card>
Default password will be root.
2. Check whether jffs2 is mounted or not. If jffs2 not mounted , please
mount jffs2 using mount command.
#df –h ( command to check whether jffs2 is mounted ) as
shown in below screenshot.
3. Go to /jffs2/conf path in NGTJ card . Run script ./lag_pre_reboot.sh

1 or 2 . 1 is for Simplex and 2 is for Duplex.
#cd /jffs2/conf
#./lag_pre_reboot.sh 1
Note : Option 1 is for Simplex
#./lag_pre_reboot.sh 2
Note : Option 2 is for Duplex
210 C-DOT MAX-NG

INTRODUCTION
4. Give Reboot command in command prompt.

#reboot
Important Note : Please give commands exactly as mentioned above.

Chapter 4.
CENTRE FOR
C-DOT MAX-NG
GENERAL DESCRIPTION
212 C-DOT MAX-NG

INTRODUCTION

Chapter 4.
Section No.431-005-1035
System Issue 01, March 2016
Practices
C-DOT MAX-NG
GENERAL DESCRIPTION
© 2016, C-DOT
214 C-DOT MAX-NG

INTRODUCTION
Printed in India
C-DOT MAX-NG
GENERAL DESCRIPTION
ISSUE 01
MARCH 2016
MAGH 2072
SERIES 000 : OVERVIEW
ANY FEEDBACK ON THE DOCUMENT MAY BE SENT AT MXNGPMTC@C-DOT.IN.
© 2016 BY C–DOT, NEW DELHI.

INTRODUCTION

INTRODUCTION
Introduction
 4.2. MIGRATION TO C-DOT MAXNG
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.
As almost 50% BSNL’s PSTN switching network is based on C-DOT DSS technology, C-
DOT 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 C-DOT
 4.3. INTRODUCTION TO C-DOT MAXNG
Trunk Media Gateway and the Signalling 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 signalling messages are carried in the form of IP
packets in the network.

Chapter 4.
 4.4. SCOPE OF THE DOCUMENT

Chapter 1 explains the hardware architecture of the MAXNG LAGU and CACU access
site components.
Chapter 2 details the various subscriber features which MAXNG supports, the system
administration for MAXNG and the Disaster recovery mechanism, built in MAXNG
solution.
The detailed design of the solution is not in the scope of this document.
6 C-DOT MAX-NG
ACCESS GATEWAY H/W ARCHITECTURE
CHAPTER-1
Access Gateway H/W Architecture

The gateways are either housed in the Central Access Control Unit (CACU), which is a
card frame having slots for the cards thereby facilitating ease of migration of MAX
exchanges to MAX-NG and their subsequent maintenance or in form of Line Access
Gateway Unit (LAGU), a system having two NGTJ cards functioning as LAG in redundant
mode, which will convert the Co-located Line BM and Remote BM (RSU).
The cards to be used in the slots of CACU are:
 Shelf Manager Cards (SLM) – to monitor and manage the chassis
 NGN Gateway Card (NGTJ) – to run gateway applications.
 Ethernet E1 Bridge Main Card (EBM) – to terminate E1 links carrying Ethernet
traffic from LAGU.
 MAX-NG L3 Switch (MLS) – for traffic aggregation and switching over CACU.
The LAGU has the same NGTJ cards which are used in the CACU, only the software
differs.
Other than the cards, there are miscellaneous cards used in CACU for proper functionality
and fault handling, which are Temperature Sensor Card (TSN) and Fan Controller Card
(FCL).
The Hardware details of the cards are as follows:
CENTRAL ACCESS CONTROL UNIT(CACU)
 CACU is installed in a Co-located BM site in a spare BM rack
 Chassis will be powered from the same dual bus bars as other units in the MAX
exchange.
 Dual power feeds take -48V DC power from two independent sources.
 Tag Block for connecting E1s is also installed in the same rack

Chapter 4.
KEY COMPONENTS IN CACU CHASSIS

 The 6-slot MAX-NG Card Frame (CACU) variant consists of the following
components:
 Four Universal slots
 Pair of redundant aggregation slots
 Pair of redundant Shelf Management and Controller slots
 Pair of redundant -48V power feeds
 A FAN tray at the bottom
 Temperature sensor card with digital temp sensing for each slot
POWER TO CACU CHASSIS
 Card is fed with -48V supply
 The other necessary supply voltages are generated by using DC-DC converters.
CARDS INSTALLED IN CACU CHASSIS
 Shelf Manager (SLM) cards: A pair of SLM cards will be installed in the two slots at
the lower left side of CACU Chassis.
 NGTJ cards: NGTJ cards can be installed in any of the first four universal slots.
These cards work in 1+1 configuration.
 EBM cards: EBM cards can be installed/jacked in into any of the first four
universal slots. These cards work in 1+1 configuration.
 MLS cards: A pair of MLS cards can be installed in the last two slots.
 TSN cards : Temperature sensor cards
INSTALLATION DETAILS OF CACU Chassis
8 C-DOT MAX-NG
FRAME TO
INSTALL DDF
MODULE
DDF MODULE
CACU CHASIS
 4.5. SHELF MANAGER CARD (SLM):

The Chassis version (APC-SLML22/H-AE2) of the SLM card is the controller card in
duplex configuration. The SLM cards are installed in the first two slots in the extreme left
side of CACU Chassis. This card monitors the status of the CACU Chassis cards and other
health parameters of Chassis like temperature and fan status.
HARDWARE DETAILS
The SLM card uses MPC8306s Power PC processor from Freescale. In this card only 2 fast
Ethernet ports are used i.e. FEC1 and FEC2. FEC1 is connected directly to outside world
through RJ45 whereas FEC2 is connected through Ethernet switch PSB6970.
The SLM card consists of an FPGA EP4C15F23C8N (U11) which along with the processor
plays the main functionality of the SLM card. The FPGA interfaces with the back plane
connector (J8) and the backplane power connector (J16). The backplane connector of SLM
card has the motherboard ID bits which will give the ID for the motherboard. The
processor reads the Mother board ID and intimates the EMS during discovery of CACU
Chassis. The FPGA also holds the functionality to perform the redundancy by having the
MATE MATESR signals.
Power Supply: In Chassis version -48v which is supplied to the board through connector
J16 which is internally converted to 5V using device PTEA415050N2AD.All Ethernet
connections and E1’s are connected to 96 pin euro connector J8. There are two power

Chapter 4.
supply sources termed as copy-0 and copy-1 power supply. Power Supply Alarms are
raised for these two copies.
Two RS232 links are provided on SLM card. The RS232 links are given from two three pin
connectors J17and J18 with MAX3232 (U29) as an RS232 transceiver.
LED Indicators
 Power on LED indicator: This LED indicates whether the +5v is supplied to the board.
 2 Ethernet ports status (1 and 4 ports being used currently for connecting to MLS).
 8 LEDs free currently and that can be configured to the Chassis and SLM card related status.
Following interfaces are present on SLM card:
 2 Fast Ethernet ports
 Dual power supply
 Mate interface signals
 I2C for communicating with other cards in MAX-NG chassis
 RS232 serial port from Processor for debug console(minicom connectivity)
 Push button reset.
FUNCTIONALITY OF SLM CARDS
The Shelf Manager cards have following major functionality:
 Resolves the self-status to come up as active or standby copy.
 In active copy, SLM does the following activities :
 On first time invocation, takes/registers the IP address range allocated to the
CACU Chassis along with the netmask, gateway-address and broadcast
addresses.
 Discovers the card type (NGTJ/EBM/MLS) present in the CACU slots.
 Allocates the IP addresses to the NGTJ and EBM cards discovered from the
allocated range input.
 Checks the MLS card presence by pinging to the management IP of MLS cards
as per the IP range given by operator for CACU Chassis cards.
 Intimates the EMS regarding the card types present in CACU slots along with
the IP addresses.
 Checks/registers the FAN running (ON/OFF) status for all the four fans of
CACU Chassis.
 Checks/registers the temperature for all the equipped cards in the Chassis
(including the SLM slots).
 Initializes the SLM database for the card slots for card type, IP addresses,
Ethernet port info and their respective temperature levels.
 After first time discovery and initialization, the SLM goes into monitoring mode.
 In monitoring mode, the SLM card periodically (after 1 min) checks the CACU
slots for any card Jack-in/Jack-outs, temperature level and FANs status changes.
10 C-DOT MAX-NG
In case of changes, alarms are sent to EMS. The alarms are raised in case any of
the two power supplies (copy0 and copy1) goes down.
 On Switchover command from operator, switches the status of self-copy from
active to standby status and stops periodic monitoring of CACU cards.
 In standby copy, it does the following activities :
 Periodically checks mate status register to verify the mate active copy up status
 Switches the status of self from standby to Active in case the mate copy is not up
and starts periodic monitoring of CACU cards, FANs status and temperature
level.
 4.6. NGN GATEWAY CARD (NGTJ):
The NGN Gateway Card is a flexible and versatile hardware designed to support gateway
functionality between PSTN and IP networks. It has a processor that handles all signalling
related information while the DSP supports various kinds of transcoding, voice
packetization, tone generation, detection etc.
The card when housed in CACU will be used to act any or multiple functions as Signalling
Gateway, Trunk Media Gateway, V5 Access Gateway or PRI Gateway. When used in a LAGU, it
will be used as a Line Access Gateway.
It has a main processor and a DSP which acts as a slave to the processor. The hardware details
are:
HARDWARE DETAILS
The version of the NGTJ card to be used for MAX-NG Rollouts in CACU Chassis is
NGTJ-SE3. The NGTJ-AE3 version is to be used over LAGU that contains the additional
internal EEB module chip.
MAIN PROCESSOR AND CAPABILITIES
The MPC8360 Power PC processor from Freescale is used. It has a capability of supporting
2GiG Ethernet interfaces, 127 channels of HDLC and 127 channels of SS7 at the same time
with no restriction on number and size of buffer descriptors.
 It supports 1GB of RAM.
 It has 1GB of permanent storage over NAND flash (on file-system /dev/mtdblock2 mounted
over /mmc).
 It also supports 256MB of permanent storage over NOR Flash. This 256 MB is split as boot-
flash of 128 MB and code-flash of 128 MB.
 Out of the 128 MB of boot-flash, 64MB is used for u-boot, root file system, Linux and
dtb(device tree blob) files. The rest storage of 64 MB can be used for storing data (on file-
system /dev/mtdblock0 mounted over /jffs2).
 The code-flash of 128MB, is not used currently.
DSP PROCESSOR AND CAPABILITIES

Chapter 4.
The Texas Instruments chip TMS320C6486 is used, with 6 cores, each core operating at
600MHz.
 It has 64MB of DDR2 interface and support to SPI flash for storing configurationdata.
 DSP has interface to two Ethernet ports, one with 10/100/1000Mbps (GiG) and second with
10/100Mbps.
 Internally, GiG ethernet interface is connected to vitesse GIG switch and 10/100 ethernet
interface is connected to Lantiq 10/100 ethernet switch. Lantiq 10/100 switch is inturn is
connected to Vitesse GIG switch.
 The DSP can support 1024 channels of voice with RTP packetization, DTMF detection and
tone generation (Codec G711 is supported).
The NGTJ can support a total of 32 E1s (apart from 4E1s for EEB functionality). In total,
it can support 1024 channels on PCM. Apart from 32 E1’s, 8 Nos. of 8Mbps links is also
supported through LAG interface.
The NGTJ FPGA block provides glue interface and interconnects all devices on NGTJ
card. It helps to provide resets to devices, generates chip selects, adjusts timing parameters
between devices and drives LED displays.
CLOCK MODES OF NGTJ OPERATION
NGTJ can operate in two modes when connected on E1:
 Loop time mode, also called as slave mode
 TX Time mode, also called as Master mode
 When configured as an LAG, NGTJ can operate only in Master Mode.
Loop Time mode or slave mode: Here, NGTJ will lock to RX clock from E1 connected to
TAX or MAX, which has high clock stability. If there are 32 different E1s connected from
32 different exchanges, then NGTJ has a capability to extract clock from 32 E1s and
synchronize to each exchange. This feature was not available in SGTK.
TX Time mode or Master mode: Here, NGTJ will act like a master and provide clock on
E1s connected to access nodes such as V5 or PRI. It is possible to have few E1s in loop time
mode and few E1s in TX time mode. For e.g. few E1s configured for SGW, MGW and few
E1s configured for V5/PRI. set_e1conf command on NGTJ is used to set each e1 in either
loop timed or master mode.
POWER SUPPLY
NGTJ card operates on dual -48V power supply. Operating range of NGTJ is from -36V to
-60V DC. NGTJ has a power monitor mechanism which monitors supply voltages and
shuts down the card in the event of any power going down. Peak power consumption is
approximately 80 watts under full load condition. The operating temperature for NGTJ is
from 0 to 55 degrees Celsius at 95% humidity.
LED INDICATORS
 Power on LED indicator: This LED indicates whether the +5v is supplied to the board.
 32 LEDs corresponding to 32 E1’s. The LEDs glow green in case the E1 is connected.
12 C-DOT MAX-NG
 8 LED indicators are free and can be configured to required status indications in future.
NGTJ CARD INTERFACES
 4 Fast Ethernet ports
 I2C for communicating with SLM card
 RS232 serial port from Processor for debug console (minicom connectivity).
 32 E1’s interface to support 1024 channels on PCM
 4 E1’s interfaces from internal EEB (for LAG configuration).
 2 Nos. of 8Mbps links are connected between Time switch and PowerPC to handle HDLC
signalling (required for PRIAG, v5AG and LAG) and SS7 signalling for SG.
 8 Nos. of 8Mbps links are connected between Time switch and DSP for DSP functionality.
 8 Nos. of 8Mbps links between Time switch and LAG interface for LAG functionality.
 Dual power supply
 Push button reset
FUNCTIONALITY OF NGTJ CARDS
NGTJ cards will be used for the connectivity with various TDM exchanges i.e. L2-TAX and
POIs. NGTJ cards support 32 E1s and depending upon the site requirement, these 32E1s
can be configured as Media/Signalling E1s, V5.2 E1s and PRI E1s. This will give V5.2 E1
interface various AN-RAXs parented to the MBM and PRI-E1 interface for any ISDN-PRI
PBX interconnected to MBM system.
 4.7. ETHERNET 16/32 E1 BRIDGE MAIN CARD (EBM):
16/32 x E1 ports EBM card is used for upgrading the E1 link end point at the erstwhile
Central Module site to a MAX-NG node. One EBM card can connect up to 8/16 Remote
Base Modules to the Aggregator Slots at the erstwhile Central Module site. This is
sufficient to meet requirements of configurations of the MAX-NG exchanges deployed in
the BSNL network. As per the existing MBM configuration, 85% MBMs are working with
maximum 8 Remote Base Modules and only 15% MBMs are working with more 8 RSUs.
This card has two versions with the same PCB (APC-EBMJ22):
 APC-EBMJ22/D-SE2: having capability to convert Ethernet to 32 E1s.
 APC-EBMJ22/D-AE2: having capability to convert Ethernet to 16 E1s.
HARDWARE DETAILS
This card has a Freescale processor MPC8306s and on-board Ethernet switches PSB6970,
BCM532342 and can convert Ethernet to 32/16 E1’s using Raycom’s 16 RC6105.
Power Supply: -48v is supplied through J12 power connector.
LED Indicators

Chapter 4.
 Power on LED indicator: this indicates +5v is supplied to the board Ethernet Link
Status LEDs.
 Ethernet Link Status LEDs: The following signalling scheme is supported:
 If Link is up, then the respective LED glows
 If Link is down, then the respective LED does not glow.
 If there is an activity on link, then the respective LED blinks.
Following interfaces are present on EBM card:
 -48V (Dual power supply) Power supply interface through J12 power connector
 2 RJ45 connectors for direct Ethernet connectivity for EBM cards.
 160 pin euro connector for 32 E1’s connectivity
 RS232 connector for serial port connectivity (minicom).
FUNCTIONALITY OF EBM CARD
As each Base Module after migration is converted to an IP network Node, which connects
to the IP network over Ethernet interfaces. BSNL’s IP/MPLS network is available at each
Central Module site but not at site of each Base Module. Presently the only connectivity
between Central Module and the Base Module is the existing E1 PSTN links. In order to
extend BSNL’s IP network to site of each Base Module, these links have be used for carry
IP traffic. A conversion device called Ethernet to E1 Bridge (EEB) is required at each end
of the E1 link to utilize the link for carrying IP traffic instead of PSTN circuits. For
simplicity of explanation, the EEB can be viewed as an ‘Ethernet modem’ installed at each
end of the E1 link to convert the PSTN E1 link to E1 link carrying IP traffic.
The remote BM is upgraded to LAGU having the internal EBM card. The IP traffic at the
remote LAGU is converted to PCM E1 signals by the internal EBM module. The E1’s from
the internal EBM card at remote LAGU terminate at the EBM card in CACU Chassis in
main exchange. Further the IP traffic aggregated through the E1’s from different remote
LAGU’s is carried to the BSNL MPLS network through the Ethernet connectivity between
the EBM card and Aggregator switch (MLS) in CACU.
 4.8. MAX-NG LAYER-2 SWITCH CARD (MLS):
MLS card is used as a general purpose Ethernet Switch in MAX-NG. The version of the
MLS card to be used for MAX-NG Rollouts in CACU Chassis is APC-MLSJ64/O-SD1. In
the present version, MLS is functioning as a Layer-2 switch. But, there is built into it a
provision for adding an AMC board to provide Layer-3 functionality.
The IP traffic from the NGTJ card and EBM cards in the universal slots is aggregated
through the MLS cards Ethernet ports. The SLM cards Ethernet links also terminate over
the MLS card. Additionally, the external node LAGU IP traffic is carried to the MLS
Ethernet ports. The MLS has uplink Ethernet connectivity to BSNL MPLS network.
A pair of Aggregation Switch (Main LAN Switch) in 1+1 configuration provides the
Ethernet interfaces required for migration of MAX exchanges to MAX-NG systems at
Central location.
HARDWARE DETAILS
14 C-DOT MAX-NG
It is a 22 port Ethernet Carrier switch card based on Vitesse VSC7460 carrier Ethernet
switch. MLS Carrier Card supports 20 X 10/100/1000 Mbps copper ports towards
backplane via EURO Connector and 2 X 1Gbps Optical SFP Ports (front side as 1G
UPLINK).
Reset: A MAX811 power watchdog monitors the 3.3 V supply and generates reset when
applicable. The other supply voltages are not monitored. A reset can also be triggered by
the reset button mounted on front side of the boards. Reset Button present at the bottom is
to reset the board. No reset is required after Jack-In of the card in to MAX-NG chassis.
Power Supply
Card is fed with -48V supply and the necessary supply voltages are generated by using DC-
DC converters (Main Supply 12V@10A and subsequent voltages are generated from this).
Following interfaces are present on MLS card:
 6 Ethernet ports 1Gbps (electrical) in the backplane of MLS card used for aggregating traffic
from Universal Slots and Shelf Manager within the Card Frame (CACU Chassis) with the
following distribution:
 2 internally routed for the 2 NGTJ cards
 2 internally routed for the 2 EBM cards
 2 externally routed for the 2 SLM cards
 (14+14) x 100/1000 Mbps Ethernet interfaces (Electrical) in the backplane for aggregating
traffic from third party network equipment outside the Card Frame.
 Two numbers of 1 Gbps optical Ethernet ports/interfaces in the Front plane of MLS towards
Tier 2/ Tier 1/ PE router or Core router in the IP/MPLS network.
 RS232 connector for serial port connectivity (minicom).
 -48V Power supply interface (dual power supply).
LED Indicators:
 Power LED: A power LED is available, powered by the 3.3V output of the 12V to 3.3V DC/DC
Converter.
 Board status LEDs: A tri-colour (individual green/red pins, both ON equals yellow) LED is
available on the board front. It is OFF during reset. When Status LED is Green, the board is
working fine. If it is Red, the board has some problem.
 Port status LEDs
On MLS Card 22 bi-colour (green/yellow) ‘1G’ LEDs are available on the board front; If 1G Ports
are connected then the Port LED Status will be green otherwise (for 100Mbps) the status will be
yellow.

Chapter 4.
 Ports 1 to 20 are Electrical 1G Ethernet 10/100/1000 Mbps ports in the

backplane.
 Ports 21 and 22 are for Optical 1G Ethernet Up-link ports in the front
faceplate.
 LED mode select button
A button for selecting port LED mode is available on the board front, next to the 4-
high port LED mode indicator LED tower. By default, ALL Port LED's indicate
Link/Traffic and this corresponds to the 1st LED of LED Tower (from TOP). The
LED mode switch/button is used to display the status of 22 ports. Corresponding to
each LED of Tower (4 LED's Tower) one particular mode is assigned to it. If we go
on pressing the LED mode button it will cycle through the below mentioned modes:
1. 1st from TOP to show the port status/activity. Status refers to Port Up/Down
and activity refers to Data Transmission.(By default, the MLS is in this state
and other modes are not supported.)
2. 2nd from TOP to Show the duplex mode of the port.
3. 3rd from TOP to show the SyncE (synchronous Ethernet) feature Enabled
ports.
4. 4th from TOP to show the POE (power over Ethernet) feature Enabled
ports.
All the 22 Port LED's represent default Status/Activity only when the TOP Tower
1st LED is glowing green.
FUNCTIONALITY OF MLS CARD
The 2 MLS cards will provide the Ethernet connectivity for the other CACU Chassis cards.
Also the external LAGU Chassis Ethernet connectivity is provided by the MLS cards in
1+1 configuration. From each LAGU NGTJ card redundant Ethernet connectivity is
provided to the two MLS cards. Also, the IP traffic aggregated by the MLS layer-2
switches is uplinked through the 1G optical connectivity from MLS switches to the BSNL
MPLS network.
 4.9. TEMPERATURE SENSOR CARD FOR MAX-NG (TSN):
Temperature Sensor card for MAX-NG (TSN) is part of Shelf Manager of MAX-NG
CACU Chassis. It senses the temperature of the individual slots of the CACU Chassis (on
which it is fixed) with the equipped hardware modules and communicates the data to Shelf
Manager Card (SLM) through an Inter-Integrated Circuit (I2C) interface.
 The version of the TSN card being used in MAX-NG is APC-TSNL10/T-SC0.
HARDWARE DETAILS:
The TSN has eight temperature sensors ICs (LM75A), each positioned above daughter
card slot of MAX-NG CACU Chassis with eight slots (including SLM/Time Switch card
slots). The LM75A is a temperature-to-digital converter using an on-chip band gap
temperature and Sigma-delta A-to-D conversion technique.
16 C-DOT MAX-NG
TSN is a two-layered PCB and supports a single I2C interface, which is used by SLM to
fetch the ambient temperature.
Power Supply: VCC (2.8V to 5.5V) and GND (digital ground) are provided from the SLM
card through the 4-pin I2C interface connector J1’s pins 1 and 4 respectively.
The maximum rated current for the TSN is approximately 15mA. The ambient
temperature range is from -55 to +125 degrees Celsius.
Following interfaces are present on TSN card:
 4-pin I2C interface connector (J1)
 Interfaced to the SLM card through the I2C interface.
FUNCTIONALITY OF TSN CARD
The eight temperature sensor chips on the TSN card provide the digital temperature at
each of the CACU cards slot. The temperature is read by SLM card through the I2C
interface with the TSN card. The 11-bit digital temperature data can be measured at a
resolution of 0.125 degrees Celsius.

Chapter 4.
LINE ACCESS GATEWAY UNIT (LAGU)

 LAGU is a Two Slot Chassis to In-House
1- NGTJ CARD
2- TERMINAL SWITCH INTERFACE (TSI) CARDS
 It provides different interfaces in its back plane for different type of connectivity.
TWO SLOTS FOR

TSI CARDS
TWO SLOTS FOR

NGTJ CARDS
18 C-DOT MAX-NG
SUBSCRIBER AND SYSTEM FEATURES
Chapter 2.
Subscriber and System Features

The MAX-NG solution offers a wide range of telephony features and supplementary
services. Besides the normal calls (Local/STD/ISD) it also offers a variety of services e.g.
call forwarding, video services, voice mail etc. The subscriber can access various features
from either hard phone or soft phone. The subscriber services can be invoked through
various procedures as explained below:
 Display Keys: There are certain display keys available on the screen of the SIP
hard-phone/soft-phone. Using these options displayed on the screen the subscriber can
activate/deactivate subscriber’s facilities.
 Feature Activation Code: The Feature Code Activation is a mean for the subscriber
to activate /deactivate his services directly by dialing the appropriate sequence of
numbers on the subscriber phone line.
 4.10. PSTN (ANALOG) AND SIP SUBSCRIBER SERVICES
The subscriber services provided to PSTN (Analog) as well as SIP subscribers by MAXNG
system are explained as per their logical grouping.
4.10.1. Number Identification Service
i) Calling Line Identification Presentation (CLIP)
With this service subscribed by user, all the incoming calls are offered to the
user with the calling party's identity. The CLIP service allows the calling
subscriber number to be displayed on the called subscriber’s phone display
screen.
In exceptional cases where the calling party has subscribed CLIR or
interworking constraints in the network, CLIP service will not work.
ii) Calling Line Identification Restriction (CLIR)
This service is offered to the calling party to restrict presentation of its
number to the called party. When CLIR is subscribed, the originating
exchange notifies the destination exchange that the calling party’s number is
not allowed to be presented to the called party. The terminating local
exchange may indicate to the called user that the calling user identity is
unavailable due to restriction.
iii) Calling Line Identification Restriction Override (CLIRO)

Chapter 4.
Subscriber with CLIRO as terminating facility instead of CLIP receives the

call with the calling line identification even if the calling party has requested
that his (the calling party’s) identification should not be presented to the
called user. The CLIRO facility is offered at the discretion of the
administration to special category subscribers like the police, hospitals,
operator positions and other emergency centers.
iv) Calling Name Identification Presentation(CNIP)
With this service, all the incoming calls are offered to the user along with the
calling party's name. The CNIP service allows the calling party’s name and
number both to be displayed on the users phone display screen. The phone
should support alphanumeric display for this feature to work.
In exceptional cases as the calling party has subscribed CLIR or
interworking constraints in the network, it will not be possible to provide
caller's identity.
v) Calling Name Identification Restriction(CNIR)
The Calling Name Blocking Restriction (CNIR) service allows the originating
subscriber to block the delivery of his name (CNIP) information to the
destination subscriber.
vi) Calling Line Restriction Per Call Wise (Per Call CLIR)
This service allows the originating subscriber to restrict his CLIP when
desired.
vii) Calling Line Un restriction Per Call Wise (Per Call Un CLIR)
This service is used by the subscriber having CLIR facility. By using this
service, the subscriber’s CLI is not restricted for that call.
4.10.2. Call Offering Supplementary Services
These services permit the subscriber to request the network to divert the incoming
calls to a specific number. In call forwarding, the network forwards the calls to a
pre-registered number which can be specified by the user or exchange
administrator.
i) Call Forwarding Unconditional (CFU)
This service permits the subscriber to request the exchange to forward all
incoming calls to another number (It may be phone or voice mail). Number
could be a fixed pre-registered number or a number specified by the
subscriber in the activation request. The subscriber’s call originating service
remains unaffected. This feature has precedence over all features of the
terminating call.
ii) Call Forwarding Busy (CFB)
This service permits the subscriber to request the exchange to forward all
incoming calls to another number (It may be phone or voice mail) if the
subscriber is busy. The subscriber’s originating service is unaffected. When a
subscriber is called and it is busy then a busy tone/announcement is played to
20 C-DOT MAX-NG
caller by default but if CFB is activated then call is forwarded to particular

destination.
iii) Call Forwarding On No ANSWER (CFNA)
This service permits the served user to request the exchange to forward all
incoming calls which are not replied within ring time-out period to other
number (It may be phone or voice mail). The served user’s originating
service is unaffected. When a phone is ringing and no one is available to
answer this call then an announcement is played to caller by default but if
CFNA is activated then call is forwarded to particular destination.
iv) Call Forwarding When Subscriber Is Not Reachable(CFNR)
This service allows forwarding of calls to a designated forwarding destination
(it may be phone or voice mail) when the phone is unreachable. When the
registration of the subscriber expires then, it is assumed to be unreachable.
The Personal Voice Portal is a mean for the subscriber to access his account
information. It can be done through the subscriber phone line by using a
special code. The subscriber is connected to an Interactive Voice Response
(IVR) application. The subscriber can follow the voice menu to access
different services.
v) Selective Call Forwarding
This service allows any incoming call for a particular subscriber having this
service activated, to be forwarded to a particular destination (Phone or
voicemail).
vi) Find Me
This service makes an attempt to locate the user by calling all locations
specified in the Find Me list by the user, if this service is activated.
vii) Follow Me
This service is used to invoke Call Forwarding Unconditional feature from
destination, where call would be finally forwarded. To use this service one
requires the password. This feature is only for the Centrex subscribers.
4.10.3. Call Completion Services
i) Call Waiting
A subscriber engaged in an existing call, is given an indication (Call Waiting
tone or ZIP tone) that another caller is attempting to connect to his number.
The caller will hear ring back tone. By flashing the hook-switch the called
subscriber can talk with either party while keeping the other on hold
(acceptance without clearing). If the called subscriber replaces his handset in
response to the tone (acceptance by clearing), the exchange will automatically
extend ring to the subscriber and re-establish the connection on answer with
the party waiting.

Chapter 4.
ii) Call Hold/Third Party Enquiry

This facility is used by the user to put the existing conversation on hold for
the time being and initiate a new call to a third party for enquiry or receive a
call in waiting. The call, which has been put on hold, is retrieved by the user
as and when it is required.
iii) Call Transfer
A call transfer is a telecommunications mechanism that enables a user to
relocate an existing call to another telephone by using the Flash/Transfer
button and dialing the required location. Call Transfer enables the
subscriber to transfer an in-progress established call to a third party. The
call to be transferred may be an incoming or outgoing call.
4.10.4. Multi-Party Services
i) Three party conference Dial-In
The three party call services enables the users to establish, participate in, and
control a simultaneous communication involving three parties. This service
allows callers to dial into a conference call. A Dial-In/Meet-Me conference
requires a special conference number that is pre-configured by the system
administrator.
ii) Multi-party conference (Add-on conference)
This service allows a subscriber (the dial-in conference moderator) who is
already in a conference to invite other subscribers.
4.10.5. Subscriber Controlled Call Restriction Services
i) Outgoing call Barring
This service allows the user to restrict the outgoing call on the basis of
current access level. Various access levels of origination from a line are local
call, STD call, ISD call, Local and Level 1 call etc. This service doesn’t affect
the terminating facility of the user. This facility offers flexibility to a
subscriber to change outgoing restrictions by selection one access level, using
defined procedure through secret password. To maintain the secrecy of the
password, the user can modify the password using defined procedure.
ii) Do Not Disturb
This service allows the subscriber to block all incoming calls.
iii) Selective Call Rejection (Black List)
This service allows filtering of the calls selectively (the numbers from which
the subscriber does not want to receive the call). The chosen subscribers are
called black listed subscribers. A call coming from a particular number will
be barred if the number is present in Black List and Black List feature is
activated.
iv) Anonymous Call Rejection
22 C-DOT MAX-NG
This feature allows the subscriber to block incoming calls that do not reveal
the caller's Caller ID information. Any call coming from anonymous user
name will be rejected if Anonymous Call Rejection is activated.
v) Selective Call Acceptance (White List)
This service allows the subscriber to accept an incoming call from a
particular number if the number is present in White List and White List
feature is activated.
4.10.6. Miscellaneous Services
i) Hot Line (Timed)
This service is also referred as a Fixed Destination Call with Time-out. It
allows a subscriber to establish calls to a pre-registered number. After
getting dial tone, if the subscriber does not dial any digit for a specified
minimum time, he is automatically connected to the number already
registered in the system. If subscriber dials digits before the time-out, a
normal connection is established in accordance with the dialed digits.
Incoming calls are not affected by this service.
ii) Hot Line (Without Time-out)
This service is also referred a Fixed Destination Call - Immediate. It allows a
subscriber to establish calls to a pre-registered number by just lifting the
handset. In this service such a connection is set up immediately upon lifting
the handset, hence the subscriber cannot dial normal outgoing calls.
Incoming calls are not affected by this service.
iii) Reminder Call/Wakeup Alarm Services
When this service is activated, the subscriber is offered a call initiated by the
exchange at a specified time/s. When the alarm call matures and is answered,
an announcement follows to notify the alarm call. This service is available in
two forms:
 The subscriber can book daily alarm or one time alarm.
 The one time alarm is valid for next 24 hour only.
iv) Voice Mail Service
The voice-mailbox is available to all the users. If the subscriber has activated
CFU/CFB/CFNA/CFNR/Selective Call forwarding to voicemail, the call of
the subscriber lands into his mailbox. The user can record the message there
if any of the condition is met.
v) Walking Class of Service
This service allows the subscriber to access the particular outgoing service of
his phone from another phone. The subscriber can activate this feature prior
to dialing each call and is only effective for the duration of each call. This
feature is only for the Centrex subscribers.

Chapter 4.
vi) Dialing by Terminal Equipment Number

Sometimes, a specific tone or announcement is to be accessed by its Terminal
Equipment Number (TEN) in the exchange. This is specifically required for
dialing to lines which do not have a directory number. This facility is used by
the maintenance personnel as part of routine maintenance activities.
vii) Call Queuing Service
This service enables the subscriber to have one or more calls placed in a
queue when his line/group of lines is busy. When the subscriber line becomes
free, the first caller in the queue is connected and the other callers in the
queue move one place ahead.
viii) Call Return
This service enables the subscriber to make the call to last received or missed
call.
ix) Call Completion to Busy Subscriber(CCBS)
The CCBS service, formerly known as automatic callback or auto callback,
provides subscribers with the capability to activate an automatic callback if
the called subscriber is busy. Completion of Calls to Busy Subscriber service
enables a user - who gets the busy tone/announcement when calling - to have
the call completed without having to make new call himself. When the called
user is no longer busy, the network will automatically ring back the calling
user. When this user answers, the network will make a new call to the called
user, who is now free.
x) Call Completion on No Reply(CCNR)
CCNR (Call Completion on No Reply) service allows a calling subscriber to
be automatically connected to a no reply called subscriber when that
subscriber becomes available. When the user is unavailable, a calling
subscriber activates this service towards the called subscriber. Whenever
called subscriber does some activity at the phone, the next call that lands on
called subscriber is the one from calling subscriber.
xi) Call Parking
Call parking allows the subscriber to park a call at the parking server. This
feature is only for the Centrex subscribers.
xii) Call Pick Up
Call pick-up feature allows the user to pick up a parked call from some other
location. When a call is parked at parking server, an announcement
regarding parking extension is played which is used to pick a parked call.
xiii) Group Call Pick Up
In this service, a group is made by the administrator, for group call pick-up.
In any phone out of these group members rings, then the ringing phone in
the group can be picked up by dialing only the service code. This feature is
only for the Centrex subscribers.
24 C-DOT MAX-NG
xiv) Direct Call Pick Up

In this service, subscriber can pick any ringing phone by dialing Call Pickup
service code followed by ringing phone. Any subscriber can prepare a buddy
list using this feature abbreviated number from different location.
xv)Speed Dial
This service enables a subscriber to reach the destination by dialing
minimum digits. A subscriber can prepare a buddy list using this feature.
xvi) Personal Ring Back Tone(PRBT)
A personalized ring-back tone service enables subscribers to replace a
standard ring-back tone (the sound a caller hears while waiting for the call to
be answered), with individually selected music, a personal message, or other
audio clips of choice.
xvii) Personal Voice Portal (PVP)
The Personal Voice Portal is a provision for the subscriber to access his
account information. It can be done through the subscriber phone line by
using a special code. The subscriber is connected to an Interactive Voice
Response (IVR) application. The subscriber can follow the voice menu to
access different services.
 4.11. SYSTEM AND SUBSCRIBER ADMINISTRATION
MAXNG System administration is taken care of by NGEMS. The concept behind the
NGEMS is to provide a centralized web based system to manage all type of network
elements of MAXNG network. The NGEMS provides a user friendly single interface to
perform management operations on different network device. NGEMS provides FCAPS
functionality, subscription management and general O & M functionality for the MAXNG
nodes.
Data creation and subscriber management is done through C-DOT Soft switch portal,
accessible through NGEMS. It has four interfaces- Super, Admin, Operator and
Subscriber. The Super can create different “Admins” in different sites, with different
language groups assigned to them .It also assigns area code and exchange code to respective
Admin, Admins can create different “zones” and number of Operators for each zone.
Operators use area code and exchange code to create subscribers.
 4.12. GEOGRAPHICAL RECOVERY MECHANISM
MAXNG solution supports “Geographical Recovery” mechanism, in case of any major
hardware/module failure or natural calamity. The concept introduces Domain Name based
routing of calls and physical replication of the nodes SBC, DNS( Domain Name System)
server, C5, C4 , SG, MG and SG in different geographical locations as Primary and
Secondary setups . The Access Gateways (LAG/V5/PRI) shall route the ongoing calls to
Primary set up, using DNS based routing. Data consistency is maintained in Secondary
setup. In case of any disaster in the region where primary setup is placed, the Secondary

Chapter 4.
setup takes over the role of Primary setup, and access gateways route the calls to this new
Primary setup.
26 C-DOT MAX-NG
Annexure - A
Abbreviations
This document uses the following abbreviations:
CDR Call Detailed Record
CTU Concentrated Terminal Unit
DSP Digital Signal Processor
EBM Ethernet to E1 Board Main
IVR Interactive voice Response
LAG Line Access Gateway
M3UA MTP Level 3 UA
MAXNG Main Automatic Exchange-Next Generation
MTP2 Message Transfer Part 2
MTP3 Message Transfer Part 3
NGEMS Next Generation Element Management System (IEMS)
NGTJ NGN Gateway Card
NOC Network Operations Centre
POI Point Of Interface
PRIAG PRI Gateway
PSTN Public Switched Telephone Network
PTU Principal Terminal Unit
PVP Personal Voice Portal
RAX Rural Automatic Exchange
RE Rating Engine
SBC Session Border Controller
SCTP Stream Control Transmission Protocol
SG Signalling Gateway
SGL2 Signaling Gateway Layer 2
SLM Shelf Manager Card
SS Soft Switch (Class IV, V)
MAX-TO MAX-NG MIGRATION MANUAL i

Chapter 4.
STP Signal Transfer Point

TAX Tandem Automatic Exchange
TDM Time Division Multiplexing
TEN Terminal Equipment Number
TMG Trunk Media Gateway
V5AG V5 Access Gateway
XML Extended Mark Up Language
ii C-DOT MAX-NG
ABBREVIATIONS
C-DOT MAX-NG
CACU USER MANUAL
MAX-NG Access SW Inst & Config Page iii

Chapter 4.
Section No.431-005-1040
Practices
C-DOT MAX-NG
CACU USER MANUAL
(This document is updated as per S/W release XEYEPL1_1_2.9_1)
© 2016, C-DOT
iv C-DOT MAX-NG
ABBREVIATIONS
Printed in India
C-DOT MAX-NG
CACU USER MANUAL
ISSUE 01
MARCH 2016
MAGH 2072
SERIES 000 : OVERVIEW
© 2016 BY C–DOT, NEW DELHI.
H:\HOME\NG-MAX\User\Final\CDOT-MAXNG-CAC-UMAN-v01.docx March 23, 2016
MAX-NG Access SW Inst & Config Page v

Chapter 1.
Introduction
1.1 PURPOSE AND SCOPE OF THE DOCUMENT
This document provides a general description of C-DOT Central Access Control Unit
(CACU) It also provides information regarding architecture of the CACU and Man
Machine Interface (MMI) commands along with various troubleshooting techniques.
 1.2 INTRODUCTION
The MAX-NG Central Access Control Unit (CACU) Chassis is Telco grade Card Frame
integrating all standalone units into single Chassis for easing the migration from
MAX exchanges to MAX-NG and subsequent maintenance of the migrated nodes.
One CACU Chassis will be located in the existing MAX exchange racks and is powered
from the same dual bus bars as other units in the MAX exchange.
In one CACU chassis two gateways of TMG, V5AG, PRIAG can work on two NGTJ cards
respectively.
CACU replaces Trunk BM’s by TMG, ISTU of MAX by PRIAG, VU of MAX by
V5AG.SUM of MAX is replaced by SG server at core site & line cards of SG are at CACU.
V5AG Introduction:
MAX-NG (Main Automatic Exchange for Next Generation) is a MAX system with the
functionalities of switching and control being moved out to a Soft switch. V5 Access
Gateway is one of the MAX-NG component which transport V5 signaling from TDM to IP
network and convert media from TDM to IP Packet Network.
V5 Access Gateway has two major components, V5 Signaling Gateway for signaling
transport and Media Converter for converting media from TDM to IP networks and vice
versa. V5 Signaling Gateway component transport the V5 Signaling over IP Networks.
PSTN Subscribers are directly connected to MAX and V5 Subscribers are connected
through Access Network with CDOT MAX as follows, a standard V5.2 Protocol is working
between AN and MAX as shown in figure 1.1

Chapter
Figure 1.1 Showing V5 Subscribers connected with CDOT

C-DOT MAX has been upgraded from TDM to IP based MAX-NG (Main Automatic
Exchange for Next Generation Network). For retaining V5 subscribers a V5 Access
Gateway is required to be deployed as shown in Fig. 1.2
Figure 1.2 showing V5 Subscribers connected with CDOT MAX-NG via Access Gateway
V5AG which interfaces with MAX on V5.2 interface over E1s is now connected with the
Packet Network through V5 Access Gateway over Ethernet for both data and signaling
path. V5 Access Gateway in MAX-NG network has been depicted in the following figure
1.3.
V5AG can run on any E1 port of any NGTJ card housed in CACU
6 C-DOT MAX-NG
INTRODUCTION
Figure 1.3 Showing MAX-NG Network Elements and their Interfaces

PRIAG introduction:
PRI Access Gateway is acting as a mediation device which converts ISDN-PRI signaling
from connected ISPBX’s on PRI links to SIP signaling towards soft switch & vice versa.
This PRIAG is capable of converting time division multiplexed (TDM) voice to IP packets
and vice versa. These IP packets are delivered over Ethernet links to IP network. It talks to
soft switch over SIP (Session initiation protocol.)
PRIAG can run on any E1 port of any NGTJ card housed in CACU

Chapter
Following figure shows the network diagram of a PRIAG connected in a network.
Soft Switch
SIP
NGEMS
XML
E1 PRI Access Gateway E1 ISDN

ISDN
PBX-2
PBX-1
Figure 1.4: Showing PRIAG Network Interfaces

Signalling Gateway/ TMG introduction:
A Signalling/Media Gateway creates a bridge between the SS7 network and the IP
network. It facilitates seamless interworking between SS7 network and IP based network.
It acts as a bridge or gateway between a circuit switch network and a packet switch
network. It relays and translates SS7 signalling in a circuit switch network to SIGTRAN
signaling in a packet switch network & vice-versa. The SG can also behave as an STP.
The SG consists of the SS7 stack, the SIGTRAN stack and some interworking functions.
A Signaling Gateway causes a Softswitch to appear like an ordinary SS7 point code (SS7
node) in an SS7 network. The Signaling Gateway only handles SS7 signaling;
Media Gateway handles the voice circuits established by the SS7 signaling mechanism. It
supports G.711 voice codec. It supports Media Protocol as RTP.
8 C-DOT MAX-NG
INTRODUCTION
Figure 1.5: showing the Basic MAX-NG components connected in a Network

Chapter
Introduction:
TMG can run on any E1 port of any NGTJ card housed in CACU
TMG connected in a network.
Figure 1.6: Showing TMG Network Interfaces
Soft Switch Soft Switch
H248
NGEMS
NGEMS
XML
E1 TMG/SGPRI Access Gateway E1 PSTNI

PSTNIS
SDN
DN
PBX-2
PBX-1
10 C-DOT MAX-NG
Chapter 2.
Specifications of CACU
 4.13. CAPACITY
a. A maximum of 64 E1 links are supported by CACU. One NGTJ card can support
32 E1 links & two NGTJ cards can support 64 E1 links.
b. Each NGTJ card can work as a V5 access gateway, PRI access gateway, trunk
media gateway & signalling gateway line card.
c. Each port or E1 link on a NGTJ card can be configured as a V5AG,PRIAG, TMG
or as a signalling gateway line card
d. A maximum of sixty four V5.2 interfaces with one link each or a maximum of sixty
four ISDN interfaces or a maximum of sixty four E1 interfaces as a TMG can be
supported. Average traffic supported per bearer channel is 0.7 erlang as per TEC
specifications.
e. A maximum of 60 SS7 links can be created in a NGTJ card having 32 E1 links.
f. Packet forwarding rate is at least 70 Mbps.
g. Each CACU supports a traffic of 1920 E during a busy hour.
h. Each V5 Access Gateway supports 32K subscriber creations.
 4.14. INTERFACE TOWARDS LOCAL EXCHANGE
The system has a provision of sixty four 2 Mbps digital trunks (E1 Links) towards Local
exchange. These E1 links can be configured as V5AG,PRIAG,TMG or SG line card in any
fashion.
 4.15. INTERFACE TOWARDS SOFT SWITCH
The system has a provision of two 1 Gbps Ethernet links towards soft switch.
The system provides one serial RS 232 port for connecting it to a computer for operating
system & software drivers loading.
 4.16. SIGNALLING INTERFACE TO THE EXCHANGE
V5.2 signalling interface and PRI links uses TS16 of E1 links for signalling, related to the
PSTN subscribers. SS7 link can be configured on any channel from 1 to 32 of any E1.
 4.17. ALARM
Each AI link status, PRI link status & SS7 link status is displayed in an alarm window on
NGEMS screen from where operator interacts with the CACU system.
Health status for each E1 Link is indicated by the colour of a corresponding LED to that
E1 on NGTJ card. If E1 is connected then colour of corresponding LED is shown as

Chapter
“GREEN”, if E1 is physically disconnected then colour of corresponding LED is shown as

“RED”.
 4.18. POWERING OPTION
Power is derived from nominal -48V DC.
 4.19. CODEC SUPPORTED
CACU supports ITU-T G.711, codec as per ITU-T recommendations. For all calls codec
“ITU-T G.711” is being used.
“T.38” for Fax calls is also supported.
 4.20. ECHO CONTROL
Echo control and Echo cancellation procedures as per ITU-T G.168 are provided by the
call control protocols in the CACU on a per call basis.
 4.21. VOICE ACTIVITY DETECTION
V5AG & PRIAG IN CACU provides activation and deactivation of silence suppression by
means of Voice Activity Detection (VAD).It also provides comfort noise generation and
insertion. Silence suppression and comfort noise insertion procedures on a per call basis
are provided.
 4.22. TONES & ANNOUNCEMENTS
CACU supports DTMF signals and tones received during call Setup as well as in call
established phase. It is possible to program new tones whenever required.
2.11. Subscriber Management
Both decadic and DTMF dialing is supported
12 C-DOT MAX-NG
Chapter 3.
System Architecture
CACU chassis has got a pair of redundant Shelf Management and Controller slots for
housing the Shelf Manager (SLM) cards. There are 6 other slots in the CACU Chassis as
given below:
Four Universal slots housing pair of NGTJ and EBM cards
Two Aggregation slots for housing the MLS cards
The CACU Chassis is fed with two independent pair of redundant -48V power feeds in the
backplane. There is a FAN tray at the bottom hosing four FANs for cooling the
Chassis and the temperature sensor card with digital temperature sensing for each slot at
the top of the CACU Chassis.
Figure-2.1: CACU Chassis

The front plane face plates of the CACU Chassis cards has mainly the LED indicators for
status and the motherboard at the backplane of the Chassis has mainly various
connectors like RJ45 Ethernet ports, Euro E1 connectors, RS232 serial ports and power
feed connectors. In the front face plate of MLS cards, apart from the LEDs, there are
two optical SFP connectors for uplink connectivity with MPLS router.
The Central Site (Main exchange) is equipped with a 6-slot CACU Chassis. The last two
slots on right side are reserved for the two copies of MLS cards. In the remaining 4
universal slots on left of the Aggregation slots, different gateways units may be
configured in any combination Gateway Applications for Signalling Gateway (SG),

Chapter
Media Gateway (MG), V5 Access Gateway (V5AG) and PRI Access Gateway (PRIAG).
All gateways use the NGTJ card and differ only in the functional software release
loaded on the card. Besides these gateways, two copies of Ethernet to E1 conversion
modules with each card supporting up to 16/32 E1s can also be optionally equipped in the
universal slots for providing E1 connectivity to LAGs at remote BM sites. Uplink to the NGN
Core Network can be up to 1 Gbps dual redundant links from each MLS. Normally a
typical configuration at main site would have a 6-slotCard Frame housing two MLS , two
NGTJ boards for gateway applications and two EBM boards (for remote BM
connectivity).
The Central Module in existing main exchange is completely removed. It is replaced
with an MLS. Any Trunk BMs co-located with the Central Modules are also upgraded to
gateways. After the upgrade, all E1 based gateways like Trunk Media Gateways,
Signaling Gateways, V5.2
Gateways and PRI Gateways are always co-located with the MLS at the Central Site (in the
6- slot MAX-NG Card Frame as explained earlier).
The collocated BMs in the main exchange site will have the LAGs uplinked via MLS in
CACU Chassis, however for the remote BMs the E1s links are terminated at the EBM
equipped in CACU Chassis.
Following cards can be installed over the CACU chassis:
SLM (Shelf Manager) card: A pair of SLM cards will be installed in the first two slots
at the lower left side of CACU Chassis. These cards have smaller form factor than the rest
of 6 cards in the CACU Chassis. This card monitors the status of the CACU Chassis cards
and other health parameters of the Chassis like temperature and fan status. The Shelf
Manager and Controller slots house the management Agent software and aggregate
management related information like equipment, infrastructure alarms, and traps for
sending them to the Element Management System through the MLS slots.
NGTJ (Next Generation Gateway) card: Two NGTJ cards can be installed in any of the four
universal slots. The four slots after SLM cards are called universal slots. These cards can work as
combo gateways for SG/MG/V5/PRI. The two combo gateways can be configured with E1’s
distribution in different directions . Generally NGTJ cards are placed in first two universal slots.
EBM (Ethernet 16/32 E1 Bridge Main) card: EBM cards can be installed into any of the four
universal slots. These cards terminate the E1 links carrying the t r af f i c from the remote LAGU
(the MAX-NG upgraded RSUs) & convert this E1 traffic from remote LAGU to Ethernet traffic
& give it to MLS.EBM cards come in two variants-EBM 16 & EBM 32 which supports 16 & 32 E1
links respectively from remote LAGU. Generally EBM cards are placed in last two universal slots.
If NGTJ cards are not required then EBM cards can be installed in all four universal slots.
MLS (MAX-NG Layer3 Switch) card: A pair of MLS cards can be installed in the last two
slots. MLS card aggregates all the traffic of CACU from all cards & connected LAGU’s to CACU
& forwards this traffic to MPLS network via 1 GB optical uplink. MLS in slot 7 is active & in slot
8 is standby.
TSN (Temperature Sensor) card: Temperature sensor card. This card is pre-installed fixed card
at the top side of CACU Chassis with temperature sensors for each of 8 slots (including the 2
SLM slots).
14 C-DOT MAX-NG
SYSTEM ARCHITECTURE
The Universal slots are designed to house VoIP Gateway Boards (NGTJ
cards) and boards implementing bank of Ethernet-over-E1 Bridges. Traffic from
the four Universal Slots is collected in the MLS slots. The aggregated traffic is
then sent over redundant uplink ports to OCLAN/Tier-II/Tier-I switches in
the IP network over Gigabit Ethernet links.
IP ADDRESSES REQUIREMENT FOR CACU CHASSIS
Following is the distribution of IP addresses, considering the standard configuration of
CACU Chassis with 2 MLS cards, 2 SLM cards, 2 EBM cards and 2 NGTJ cards along
with one client terminal:
2 MLS cards: 6 IP addresses ( 3 IPs for each MLS card )
 One GW IP for the N/w to which the S/w is connected.
 One GW IP for other side of N/w connectivity to BSNL
 One IP for S/w management (EMS).
2 SLM cards : 3 IP addresses (one floating IP and 2 physical IPs)
2 EBM cards : 2 IP addresses (one for each)
2 NGTJ cards : 12 IP addresses (6 IP addresses for each NGTJ card as given below)
 1 physical IP address (eth0) for each NGTJ card
 1 DSP IP address for each NGTJ card
 4 virtual IP addresses for 4 Gateway applications in the order MG, SG, V5 and
PRI
Client terminal IP Addresses : 1

Chapter
Total IP addresses required per CACU: 24 (6+3+2+12+1)

CACU CHASSIS IP ADDRESS DISTRIBUTION (Usable IP range of 24 IP addresses)
Main LAN Switch Shelf EBM (NGTJ-C0) Network (NGTJ-C1) Network

IP (MLS) (6 IP Manager IP Gateway Copy 0 IP Gateway Copy 1 IP
addr) (3 IP addr) (2 IP
addr) (6 IP addr) (6 IP addr)
[1st to 6th IP addr ] [ 7th to 9th IP
addr] [10-11 th th [18th to 23rd IP addr]
IP [12 to 17 IP addr]
addr]
t
Note : Above table is just an example but this will depend on the
C IP range assigned to
specific site. J
CACU CHASSIS CARDS DETAILS G
1.LS SLMLS2(SHELF MANAGER) CARD N
1 SLM card is the controller card in duplex configuration. The SLM cards are
installed in the first two slots in the extreme left side of CACU Chassis. This card
monitors the status of the CACU Chassis cards and other health parameters of
Chassis like temperature and fan status.
LED Indicators
 Power on LED indicator: This LED indicates whether the +5v is supplied to the
board.
 2 Ethernet ports status (1 and 4 ports being used currently for connecting to
MLS).
 8 LEDs free currently and that can be configured to the Chassis and SLM card
related status.(For future use)
16 C-DOT MAX-NG
SYSTEM ARCHITECTURE
Following interfaces are present on SLM card:

 2 Fast Ethernet ports
 Dual power supply
 Mate interface signals
 I2C for communicating with other cards in MAX-NG chassis
 RS232 serial port from Processor for debug console(minicom connectivity)
 Push button reset.
FUNCTIONALITY OF SLM CARDS
The Shelf Manager cards have following major functionality:
 Resolves the self-status to come up as active or standby copy.
 In active copy, SLM does the following activities :
 On first time invocation, takes/registers the IP address range allocated to the
CACU Chassis along with the netmask, gateway-address and broadcast
addresses.
 Discovers the card type (NGTJ/EBM/MLS) present in the CACU slots.
 Allocates the IP addresses to the NGTJ and EBM cards discovered from the
allocated range input.
 Checks the MLS card presence by pinging to the management IP of MLS cards
as per the IP range given by operator for CACU Chassis cards.
 Intimates the EMS regarding the card types present in CACU slots along with
the IP addresses.
 Checks/registers the FAN running (ON/OFF) status for all the four fans of
CACU Chassis.
 Checks/registers the temperature for all the equipped cards in the Chassis
(including the SLM slots).
 Initializes the SLM database for the card slots for card type, IP addresses,
Ethernet port info and their respective temperature levels.
 After first time discovery and initialization, the SLM goes into monitoring mode.
 In monitoring mode, the SLM card periodically (after 1 min) checks the CACU
slots for any card Jack-in/Jack-outs, temperature level and FANs status
changes. In case of changes, alarms are sent to EMS. Also, the alarms are
raised in case any of the two power supplies (copy0 and copy1) goes down.
 On Switchover command from operator, switches the status of self-copy from
active to standby status and stops periodic monitoring of CACU cards.
 In standby copy, it does the following activities :
 Periodically checks mate status register to verify the mate active copy up status

Chapter
 Switches the status of self from standby to Active in case the mate copy is not up
and starts periodic monitoring of CACU cards, FANs status and temperature
level.
2. NGTJ (NGN GATEWAY) CARD
The NGTJ is a flexible and versatile hardware designed to support gateway
functionality between PSTN and IP networks. It has a processor that handles all
signalling related information while the DSP supports various kinds of
transcoding, voice packetization, tone generation, detection etc.
DSP PROCESSOR AND CAPABILITIES
 The DSP can support 1024 channels of voice with RTP packetization, DTMF
detection and tone generation (Codec G711 is supported).
The NGTJ can support a total of 32 E1s (apart from 4E1s for EEB
functionality). In total, it can support 1024 channels on PCM. Apart from
32 E1’s, 8 Nos. of 8Mbps links is also supported through LAG interface.
Note: The NGTJ in LAG configuration can support 8 Nos. of 8Mbps
links from Time switch towards TIC. Apart from PCM signals, HW
error, Active Passive, Watch dog signals are available at connector for
duplex purposes.
CLOCK MODES OF NGTJ OPERATION
NGTJ can operate in two modes when connected on E1:
 Loop time mode, also called as slave mode
 TX Time mode, also called as Master mode
Note: In LAG, NGTJ can operate only in Master Mode.
18 C-DOT MAX-NG
SYSTEM ARCHITECTURE
Loop Time mode or slave mode: Here, NGTJ will lock to RX clock from E1
connected to TAX or MAX, which has high clock stability. If there are 32 different
E1s connected from 32 different exchanges, then NGTJ has a capability to extract
clock from 32 E1s and synchronize to each exchange.
TX Time mode or Master mode: Here, NGTJ will act like a master and provide
clock on E1s connected to access nodes such as V5 or PRI. It is possible to have
few E1s in loop time mode and few E1s in TX time mode. For e.g. few E1s
configured for SGW, MGW and few E1s
Note: Operator shall configure proper mode of clock when E1 is equipped as SG-
TMG. Generally it shall be in slave mode.
POWER SUPPLY
NGTJ card operates on dual -48V power supply. Operating range of NGTJ is from -
40V to -54V DC. NGTJ has a power monitor mechanism which monitors supply
voltages and shuts down the card in the event of any power going down. Peak power
consumption is approximately 80 watts under full load condition. The operating
temperature for NGTJ is from 0 to 55 degrees Celsius at 95% humidity.
LED INDICATORS
 Power on LED indicator: This LED indicates whether the +5v is supplied to the
board.
 32 LEDs corresponding to 32 E1’s. The LEDs glow green in case the E1 is
connected.
FUNCTIONALITY OF NGTJ CARDS
NGTJ cards will be used for the connectivity with various TDM exchanges i.e.
L2-TAX and POIs. NGTJ cards support 32 E1s and depending upon the site
requirement, these 32E1s can be configured as Media/Signalling E1s, V5.2 E1s
and PRI E1s. This will give V5.2 E1 interface various AN-RAXs parented to
the MBM and PRI-E1 interface for any ISDN-PRI PBX interconnected to
MBM system.
3. EBM CARD (ETHERNET 16/32 E1 BRIDGE MAIN) CARD
16/32 x E1 ports EBM card is used for upgrading the E1 link end point at the
erstwhile Central Module site to a MAX-NG node. One EBM card can connect upto
8/16 Remote Base Modules to the Aggregator Slots at the erstwhile Central Module
site.
This card has two versions :
 having capability to convert Ethernet to 32 E1s.
 having capability to convert Ethernet to 16 E1s.
Power Supply: -48V is supplied through J12 power connector.
LED Indicators

Chapter
 Power on LED indicator: this indicates +5v is supplied to the board Ethernet
Link
 Status LEDs.
 Ethernet Link Status LEDs: The following signalling scheme is supported:
 If Link is up, then the respective LED glows
 If Link is down, then the respective LED does not glow.
 If there is an activity on link, then the respective LED blinks.
Following interfaces are present on EBM card:
 -48V (Dual power supply)Power supply interface through J12 power connector
 2 RJ45 connectors for direct Ethernet connectivity for EBM cards.
 160 pin euro connector for 32 E1’s connectivity
 RS232 connector for serial port connectivity (minicom).
FUNCTIONALITY OF EBM CARD
As each Base Module after migration is converted to an IP network Node, which
connects to the IP network over Ethernet interfaces. IP/MPLS network is
available at each Central Module site but not at site of each Base Module.
Presently the only connectivity between Central Module and the Base Module is
the existing E1 PSTN links. In order to extend IP network to site of each Base
Module, these links have be used for carry IP traffic. A conversion device called
Ethernet to E1 Bridge (EEB) is required at each end of the E1 link to utilize the link
for carrying IP traffic instead of PSTN circuits. For simplicity of explanation, the
EEB can be viewed as an ‘Ethernet modem’ installed at each end of the E1 link to
convert the PSTN E1 linkto E1 link carrying IP traffic.
The remote BM is upgraded to LAGU having the internal EBM card. The IP
traffic at the remote LAGU is converted to PCM E1 signals by the internal EBM
module. The E1’s from the internal EBM card at remote LAGU terminate at the
EBM card in CACU Chassis in main exchange. Further the IP traffic aggregated
through the E1’s from different remote LAGU’s is carried to the BSNL MPLS
network through the Ethernet connectivity between the EBM card and Aggregator
switch (MLS) in CACU.
4. MLS (MAX-NG LAYER-2 SWITCH) CARD
MLS card is used as a general purpose Ethernet Switch in MAX-NG
The IP traffic from the NGTJ card and EBM cards in the universal slots is
aggregated through the MLS cards Ethernet ports. The SLM cards Ethernet
links also terminate over the MLS card. Additionally, the external node LAGU
IP traffic is carried to the MLS Ethernet ports. The MLS has uplink Ethernet
connectivity to MPLS network.
A pair of Aggregation Switch (Main LAN Switch) in 1+1 configuration
provides the Ethernet interfaces required for migration of MAX exchanges
to MAX-NG systems at Central location.
20 C-DOT MAX-NG
SYSTEM ARCHITECTURE
It is a 22 port Ethernet Carrier switch card. MLS Card supports 20 X

10/100/1000 Mbps copper ports towards backplane via EURO Connector and 2 X
1Gbps Optical SFP Ports (front side as 1G UPLINK).
Reset: A reset can also be triggered by the reset button mounted on front side of
the boards. Reset Button present at the bottom is to reset the board. No reset is
required after Jack-In of the card in to MAX-NG chassis.
Power Supply
Card is fed with -48V supply and the necessary supply voltages are generated by
using DC-DC converters (Main Supply 12V@10A and subsequent voltages are
generated from this).
Following interfaces are present on MLS card:
 6 Ethernet ports 1Gbps (electrical) in the backplane of MLS card used for
aggregating traffic from Universal Slots and Shelf Manager within the Card
Frame (CACU
Chassis) with the following distribution:
 2 internally routed for the 2 NGTJ cards
 2 internally routed for the 2 EBM cards
 2 externally routed for the 2 SLM cards
 (14+14) x 100/1000 Mbps Ethernet interfaces (Electrical) in the backplane for
aggregating traffic from third party network equipment outside the Card
Frame.
 Two numbers of 1 Gbps optical Ethernet ports/interfaces in the Front plane of
MLS
 towards Tier 2/ Tier 1/ PE router or Core router in the IP/MPLS network.
 RS232 connector for serial port connectivity (minicom).
 -48V Power supply interface (dual power supply)
 LED Indicators
 Power LED: A power LED is available, powered by the 3.3V output of the
12V to3.3V DC/DC Converter.
 Board status LEDs: A tri-colour (individual green/red pins, both ON equals
yellow) LED is available on the board front. It is OFF during reset. When
Status LED is Green, the board is working fine. If it is Red, the board has some
problem.
 Port status LEDs
 On MLS Card 22 bi-colour (green/yellow) ‘1G’ LEDs are available on the
board front; If 1G Ports are connected then the Port LED Status will be green
otherwise (for100Mbps) the status will be yellow.
 Ports 1 to 20 are Electrical 1G Ethernet 10/100/1000Mbps ports in the
backplane.

Chapter
 Ports 21 and 22 are for Optical 1G Ethernet Up-link ports in the front
faceplate.
 LED mode select button
A button for selecting port LED mode is available on the board front, next
to the 4- high port LED mode indicator LED tower. By default, ALL
Port LED's indicate Link/Traffic and this corresponds to the 1st LED of
LED Tower (from TOP). Second LED of LED Tower (from TOP)
corresponds to Duplex/Speed.
FUNCTIONALITY OF MLS CARD
The 2 MLS cards will provide the Ethernet connectivity for the other CACU
Chassis cards. Also the external LAGU Chassis Ethernet connectivity is
provided by the MLS cards in 1+1configuration. From each LAGU NGTJ
card redundant Ethernet connectivity is provided to the two MLS cards. The IP
traffic aggregated by the MLS layer-2 switches is uplinked through the 1G optical
connectivity from MLS switches to the BSNL MPLS network.
5. TSN (TEMPERATURE SENSOR) CARD FOR MAX-NG
Temperature Sensor card for MAX-NG (TSN) is part of Shelf Manager of
MAX-NG CACUChassis. It senses the temperature of the individual slots of the
CACU Chassis (on which it is fixed) with the equipped hardware modules and
communicates the data to Shelf Manager Card (SLM) through an Inter-Integrated
Circuit (I2C) interface.
The maximum rated current for the TSN is approximately 15mA. The ambient
temperature range is from -55 to +125 degrees Celsius.
Following interfaces are present on TSN card:
 4-pin I2C interface connector (J1)
 Interfaced to the SLM card through the I2C interface.
FUNCTIONALITY OF TSN CARD
The eight temperature sensor chips on the TSN card provide the digital
temperature at each of the CACU cards slot. The temperature is read by SLM
card through the I2C interface with the TSN card. The 11-bit digital temperature
data can be measured at a resolution of 0.125 degrees Celsius
22 C-DOT MAX-NG
Chapter 4.
MMI Commands & Descriptions

1. Open the NGEMS in the firefox using the IP address of the NGEMS server as
http://10.187.0.41:9090 as shown in the figure below.
Enter user name as super and password as Admin123.
User should be logged in.
Note : NGEMS release may change but procedure to be followed will remain same.
2. Discovering the cacu chassis having Ip address 192.168.103.136. SLM IP will be
192.168.103.136.
Go to the File Add node command.
Enter the IP address of the CACU chassis as 192.168.103.136 and click the add node
button. CACU chassis IP will be floating IP of SLM card in duplex mode.

Error! Reference source not found.
CACU chassis will be discovered successfully .

1. Details of CACU chassis.
2. Right click the CACU node and run the Node details command. It will show the
CACU chassis details as shown below.
24 C-DOT MAX-NG
MMI COMMANDS & DESCRIPTIONS
1. Opening the main chassis of CACU

Right click the CACU node icon and run chassis command of CACU.Following
screen will be opened.

Chassis will show the card status for different card in the cacu chassis along with
the FAN status of CACU chassis. It will show the status of following cards.
SHM copy Act and standby
NGTJ cards in slot 3 & 4.
Two EBM cards in slot 5 &6
MLS cards in slots 7 & 8.
Status of four fans for temperature control.
2. SHM cards commands
i) SHM cards detail command.
Right click the SHM card in the slot one and select shm card detail
command.It will show the card status along with the allocated ip address.
26 C-DOT MAX-NG
Similarly we can see the status of shm card at slot 2.

ii) SHM release info command
This command will show the current resale version of shm card.

Note : Release may change in future and will be shown exactly as per BOM.
iii) SHM temperature level command
This command will show the current temperature of the SHM card
28 C-DOT MAX-NG
SHM switchover command.

This command will provide the SHM switchover.

On clicking the yes SHM switchover command will be executed. Now after
switchover Active SHM card will become standby and standby card becomes
ACT.
3. NGTJ card commands
i) NGTJ card release command.
This command will show the NGTJ card release info.
30 C-DOT MAX-NG
9. NGTJ card detail command

This command will show the NGTJ card details as shown below along with
the ports status equipped for different configurations.

10. NGTJ card hardware status details command

This will show the NGTJ card hardware status as shown below
32 C-DOT MAX-NG
11. NGTJ card temperature status command

This command will show the Card temperature as shown below

12. Ethernet process details command

This command will show the CPU status as well as DSP status of the NGTJ
card.
34 C-DOT MAX-NG
13. Equip Port command.

Using this command Free ports can be equipped as v5ag, priag, TMG,
SG+TMG as based upon the user requirements.

v) Unequip port command

Using this command ports can be unequipped. After unequipping these ports
becomes free.
36 C-DOT MAX-NG
vi) Equip SG line card command.

SG Line card can be equipped using this command.

vi) NGTJ card application status details command

This command will show the various applications running on the selected
NGTJ card along with their IP address.
38 C-DOT MAX-NG
vii) Running V5AG commands from CACU chassis

To run the V5ag command.
For details of V5ag commands refer the V5AG user manual.

viii) PRIAG configuration commands

PRIAG configuration commands can be run from CACU chassis.
For details of PRIAG commands refer the PRIAG user manual
40 C-DOT MAX-NG
viii) TMG configuration commands

TMG configuration can be done using the TMG configuration commands.

4. Alarms
Alarms appearing on the CACU chassis can be seen from alarm window
42 C-DOT MAX-NG
Fan alarms:

SHM alarms
44 C-DOT MAX-NG
 4.23. V5 AG CONFIGURATION COMMANDS

Run WEB Browser and give hypertext link address as given below
http://<MANAGERIPADDRESS>:9090 where manager IP address is 10.187.0.41 for
Gurugram Core Site.
Login in “super” account
The NGEMS GUI will appear as shown belowSelect option as
CDOT-MAX-NGEMS->Network Maps->North zone the discovered “CACU node” will
appear on screen.

Right click on CACU CHASSIS, Select Chassis (N)->View Chassis
The CACU chassis screen will appear
Right Click on NGTJ slot, Select Gatewy EMS->V5AG EMS->V5ag Configuration
46 C-DOT MAX-NG
COMMAND: Create V5 Access Interface

Description: Interface creation is used to configure V5 interface.
Give Create v5.2 Access Interface command as shown in the screen shot given below.
AI should be created successfully.
GUI showing the Create v5.2 Access Interface command

4.23.1. Command: Start AI

Description: This command will start AI
GOTO V5 protocolstart AI
Give command start AI as shown in the screen shot given below.
Command should be successfully executed.
48 C-DOT MAX-NG
4.23.2. Command: Delete V5 Access Interface

Description: To delete the Interface. Interface Id to which this link has been mapped
will be used as an input in this command.
Block links in the AI interface to be deleted
Command should be successfully executed
Give Delete V5 Access Interface command as shown in the screen shot
Command should be successfully executed.

GUI showing deletes V5 Access Interface command

4.23.3. Command: Block Link Operation
Description: This command block the given link of AI
Give command Block Link as shown in the screen shots
50 C-DOT MAX-NG
GUI showing Block Link Operation command

4.23.4. Command: Un Block Link Operation
Description: This command unblock the given link of AI
Give command Un Block Link as shown in the screen shots

GUI showing Un Block Link Operation command

4.23.5. Command: Display V5L3 General Attributes
Description: This command will display all V5L3 related attributes. Give Display
V5 General Attributes command
Command should be successfully executed. And show output as given below
52 C-DOT MAX-NG
GUI showing Display V5L3 General Attributes command
4.23.6. Command: Display AI Attributes

Description: To display V5 Interface related attributes. Interface name will be used
as the only input to display the required attributes.
Give Display AI Attributes command as
Shown in the screen shot.
Command should be executed successfully.

GUI showing Display AI Attributes command
4.23.7. Command: DISPL-AI-STATUS, COMMAND

Description: This command shows the status of a AI.
Give command Display AI status as shown in the screen shot.
Command should be executed successfully showing the required AI status
54 C-DOT MAX-NG
GUI showing DISPL-AI-STATUS command
4.23.8. Command: DISPL-LINK-STATUS

Description: This command shows the status of links in AI.
Give command Display Link Status as shown in the screen shot.
Command should be executed successfully showing the required link status

GUI showing DISPL-LINK-STATUS command
4.23.9. Command: DISPL-ALL-AI-INFO

Description: This command shows the Information of all the AIs created.
Give command Display All AI Info as shown in the screen shot.
Command should be executed successfully showing the information of all the AIs
created.
56 C-DOT MAX-NG
GUI showing DISPL-ALL-AI-INFO command

4.23.10. Command: Create Subscriber (Ordinary) Command
Description: This command will create AN subscriber at V5AG. A L3Addr will be
created and a directory number will be assigned to subscriber.
Give create subscriber command with inputs shown in the screen shot.
Subscriber will be created successfully

GUI showing Create Subscriber Command

4.23.11. Command: Create Subscriber (CCB) Command
Description: This command will create AN subscriber at V5AG. A L3Addr will be
created and a directory number will be assigned to subscriber. Give create
subscriber command with inputs shown in the screen shot.
Subscriber will be created successfully
58 C-DOT MAX-NG
GUI showing create subscriber (CCB) command

4.23.12. Command: Delete Subscriber
Description: This command Delete a given subscriber
Give Delete subscriber command with inputs shown in the screen shot.
Subscribers will be deleted successfully.

GUI showing Delete Subscriber Command

4.23.13. Command: Modify Subscriber Line Type
Description: Modify given subscriber line type with new line type Ordinary or CCB.
Give Modify Subscriber Line Type
With inputs shown in the screen shot.
Command will be executed successfully.
60 C-DOT MAX-NG
GUI showing Modify given subscriber line type command

4.23.14. Command: Modify Subscriber Status: Block / Unblock
Description: Modify subscriber maintenance status. Subscriber can be blocked or
unblocked.
Give Modify Subscriber Status command with inputs shown in the screen shot
Command will be executed successfully

GUI showing Modify Subscriber Status: Block / Unblock command

4.23.15. Command: Un-Freeze Directory Number
Description: Remove directory numbers from the freeze table
Give Un-Freeze Directory Number command with inputs shown in the screen shot
Command will be executed successfully
62 C-DOT MAX-NG
GUI showing Un-Freeze Directory Number command

4.23.16. Command: Display Subscriber Char
Description: Display all the characteristics of a subscriber
Give Display subscriber char command with inputs shown in the screen shot
Subscriber Characteristics will be displayed successfully.

GUI showing Display Subscriber Char command

4.23.17. Command: Display Subscriber Status
Description: Display the current status of the subscriber.
Give Display subscriber status command with inputs shown in the screen shot.
Subscriber Status Will is displayed.
64 C-DOT MAX-NG
GUI showing Display Subscriber Status command

 4.24. MISCELLANEOUS COMMANDS
4.24.1. Command: Display System Parameter
Description: Display system parameter value with name for given system
parameter id
Give Display System Parameter command with inputs shown in the screen shot
System Parameters will be displayed.

66 C-DOT MAX-NG
 4.25. V5AG ALARMS AND EVENTS

4.25.1. Alarms /Events are generated in the NGEMS window in the following cases.
When one link of AI Interface is OOS.
Setup Detail: AI Interface is created with two links active & standby and is
up.

Make one link of AI interface OOS by blocking.

Status of link will be changed to Blocked and Alarm will be raised.
Click on logical chassis View.
Green LED should change to Red for one link only.
Unblock one link through unblock command.
Links should be unblocked successfully
Check the status on logical chassis View.
RED LED should turn to GREEN.
When AI Interface is OOS by blocking both the links..
up.
When AI Interface is OOS by taking out cable from the port.
Make both the links of AI interface OOS by blocking.
Status of links will be changed to Blocked and critical Alarm will be raised.
Green LEDs should change to Red for both the links and for the AI.
Unblock both the links through unblock command.
Click on Network Events node and Alarm Node.
Critical Alarm raised for the AI and for the links should be removed from
the list and Event with INFO as CLEAR should be raised.
Click on logical chassis View..
AI Interface is created with two links active & standby and is up. Both the links are created on the
same port.
Make both the links of AI interface OOS by jacking out cable from the port.
Status of AI interface will become OOS.
Click on Alerts and Events.
Event and Alarm with severity as Critical will be raised for both the links
and for the AI.
Jack-in cable which was jacked out.
68 C-DOT MAX-NG
Click on chassis View.

4.25.2. Alarms /Events are generated in the NGEMS window in the following cases
 When one link of AI Interface is OOS.
up.
Make one link of AI interface OOS by blocking.

Status of link will be changed to Blocked and Alarm will be raised.

Green LED should change to Red for one link only.
Unblock one link through unblock command.
Check the status on logical chassis View.
 When AI Interface is OOS by blocking both the links..
up.
When AI Interface is OOS by taking out cable from the port.
Make both the links of AI interface OOS by blocking.
Status of links will be changed to Blocked and critical Alarm will be raised.
Unblock both the links through unblock command.
Click on Network Events node and Alarm Node.
Click on logical chassis View..
 AI Interface is created with two links active & standby and is up. Both the
links are created on the same port.
Make both the links of AI interface OOS by jacking out cable from the port.
Status of AI interface will become OOS.
Click on Alerts and Events.
Event and Alarm with severity as Critical will be raised for both the links
and for the AI.
Jack-in cable which was jacked out.
Click on chassis View.
70 C-DOT MAX-NG

Chapter 5.
PRIAG COMMANDS
 5.1. PROCEDURE TO INVOKE GUI
To Run WEB Browser, give hypertext link address as given below
http:// <MANAGER IP ADDRESS> :9090
(e.g http://10.187.0.41:9090)
Login in root account
Select option as
CDOT-MAXNGEMS->Applications->Network maps->MAX-NG Devices
Right click on NGTJ card icon, Select Gateway EMS->PRIAG->PRIAG Configuration
 5.2. COMMAND: EQUIP PORT

Description: This command will equip the E1 ports
72 C-DOT MAX-NG
PRIAG COMMANDS
 5.3. COMMAND: CREATE PDDI

Description: This command will create the PDDI on a specific port

74 C-DOT MAX-NG
PRIAG COMMANDS
5.3.1. Command: Display PDDI

Description: This command will display the characteristics of PDDI created.
Command can be used to Display All the PDDIs created or Specific PDDI.

5.3.2. Command: Un Equip Port

Description: This command will unequip the E1 port.
76 C-DOT MAX-NG
PRIAG COMMANDS
5.3.3. Command: Delete PDDI

Description: This command will delete the PDDI

5.3.4. Command: Display Country and Area Code

Description: This command will display port wise country and Area codes. This
command can be used for the specific port also.
78 C-DOT MAX-NG
PRIAG COMMANDS
PRIAG Alarms and Events

5.3.5. Alarms /Events are generated in the NGEMS window in the following cases
5.3.5.1. When Ports are equipped.
Setup Requirement: E1 cable is connected to load simulator (Marconi)
S. No. Action Response
1. Give command to equip port. Ports should be equipped successfully
2.. Click on chassis View. Color E1 Ports icon should turn GREEN on equipage
as shown in screenshot given below
5.3.5.2. When PORT is OOS

S. No. Action Response
1. Jackout E1 cable where PDDI is created. Status of PDDI will become OOS.
2. Check for the Alarms and Events. Critical Alarm will be raised for the Port.
3. Click on chassis View. Color E1 Ports icon should turn RED. as shown in
screenshot given below.
80 C-DOT MAX-NG
Chapter 6.
TMG Access Gateway User Commands

COMMAND – Modify TMG configuration
Description – This command will modify TMG configuration

Chapter 6.
COMMAND – Backup command

Description – This command will take backup of TMG.
82 C-DOT MAX-NG
COMMAND -Restore
Description – This command will restore the backup.

Chapter 6.
COMMAND – Display TMG Configuration

Description – This command will display the TMG configurations.
84 C-DOT MAX-NG
COMMAND – Release info

Description – This command will display the release information.

Chapter 6.
COMMAND – View Channel Status

Description – This command will display the status of a channel.
86 C-DOT MAX-NG
COMMAND – View Channel Status

Description – This command will display the status of a channel.

Chapter 6.
COMMAND – TMG alarm

Description – This command will display the alarms of TMG
88 C-DOT MAX-NG
Chapter 7.
EBM and MLS User Commands

EBM & MLS GUI
ON NGEMS GUI EBM and MLS cards are displayed as follows
In the screen below 1 EBM card and Two MLS cards are shown. There may be two EBM
cards in the network.

Chapter 7.
 7.1. EBM CARD DETAILS

On EBM card right click following options are available.
EBM card Details, EBM card Device Release Name, View Current Temperature, Alarms.
Very First is EBM card Details
On Selecting View Card details following information is displayed.
90 C-DOT MAX-NG
Card details show the status of 32 ports. Ip address and MAC Address, serial no. etc as
clearly shown in above screen
 7.2. EBM CARD DEVICE RELEASE NAME
On selecting this current release of EBM is displayed.

Chapter 7.
The output will display the release version of the card.
92 C-DOT MAX-NG
 7.3. SHOW CURRENT TEMPERATURE ON EBM
On selecting view current temperature on EBM, Current temperature on EBM is

displayed.

Chapter 7.
In the example below current temperature on EBM is measured as 37 degree C.

 7.4. ALARMS
On selecting alarms current faults on device is displayed in sorted order. It shows the port
number where alarm is there.
94 C-DOT MAX-NG

Chapter 7.
96 C-DOT MAX-NG
Chapter 8.
MLS Card GUI

 8.1. SWITCH CARD GUI
On selecting Switch card GUI, GUI gets opened in different tab as follows:
Enter proper user name and password (which is configured in MLS only). Following
screen will appear.

Chapter 8.
98 C-DOT MAX-NG
MLS Card GUI
 8.2. VIEW CURRENT TEMPERATURE
On selecting view current temperature, device temperature is shown as follows

Chapter 8.
 8.3. ALARMS
On selecting Alarms, faults on MLS cards are displayed
100 C-DOT MAX-NG

MLS Card GUI
Alarms are displayed in date & time wise sorted order as follows

Chapter 8.
102 C-DOT MAX-NG

Chapter 9.
Troubleshooting
 9.1. DEBUGGING PROCEDURE V5AG
This procedure is used for debugging various problems coming in v5ag link like no dial
tone, call failing, AI not coming up etc. User has to enable the various options as given
below
options 5,6 & 7of the main menu are used for debugging purposes
Main Menu (Enter number. )
5. Event Configuration
6. Trace level
7. Logger file
Enter Your Choice =5 (for event configuration user has to enter this option)
Event Configuration Menu (Enter number)
1. MAC
2. ENV
3. LAPV5-DL
4. V5L3
5. Back to main Menu
6. Quit
Enter Your Choice =1
MAC layer menu will be opened as
MAC: (MISCELLANEOUS COMMANDS)
**********************************
1. ENABLE DEBUG
2. DISABLE DEBUG
3. Back to event configuration Menu
4. Back to Main menu
5. exit
Enter Your Choice = 1
1. For enable all AI:

Chapter 9.
2. For enable specific AI: 2

Enter AI Num: 1
1. For enable debug print of layer manager interface
2. For enable debug print of upper interface
3. For enable debug print of lower layer interface
4. All the above interfaces
Enter Layer to debug:
2. for LAPV5-DL (Layer2)
3. for V5 Layer3
Note - option 2 is used for l2+l3 layers in cases like AI is not coming inservice option
3 is used for cases like DT not coming or calls are failing.
Enter Your Choice = 7 of Main menu
Parameters required Logger file
Input Operation:
1.Display 2.Modify : 2
Input debugVal: (combination of more means sum of those values)
0.None 1.ERROR 2.WARNING 4.NOTICE 8.DEBUG ... 15.ALL: 15
#####To display the parameters set in logger file #########
Parameters required Logger file
Input Operation:
1.Display 2.Modify : 1
Value:
full => error,warning,notice,debug
########to verify at device ###############
vi /mmc/etc/v5ag/logger.conf
############################################
Enter TraceFlag (1.Screen, 2.Full Log File, 3.unsol event, 4.CHANV5-CONF-
RELOAD): 5.Stack an d wrapper prints: 4
Note - CHANV5-CONF-RELOAD option is generally used to debug dial tone or call
related issues.
104 C-DOT MAX-NG

Troubleshooting
#####After enabling the logs, /mmc/var/log/v5ag/full & all files of /mmc/ag/cmlog

are required for debugging
check the logs in following files
$vi /mmc/var/log/v5ag/full
$tail -f /mmc/ag/cmlog/Tcdotagt.log
1. Debugging dial tone case (no dial tone)
When Dial tone is not coming for v5ag subscribers then check following
points
Check the DSP is pinging or not
Give command ipcfg on dsp minicom to check whether all ips are configured properly or not
Also check the fused tones on DSP minicom
Use command lsmod at /mmc to check the installed DSP drivers.
Re-installation of DSP drivers may be tried by commnad rmmod, insmod
ii) Debugging (AI is not coming inservice)
Check the AI related data at v5ag & V5AG, both should be same.
E1 cables are connected physically at right place.
START-AI is given at both ends
iii) Debugging (calls are not successful)
Check the subscriber data created at soft switch or not.
Check the softswitch ipaddress given in the V5AG
Check the status of softswitch . It should be up and pinging from V5AG
Check subscriber status at both ends
Ethereal tool can be used to find out cause of failure.
Logger files can be used.
Above procedure can be followed through ngems gui also by enabling the respective
prints in Event configuration commands as shown below.

Chapter 9.
106 C-DOT MAX-NG

Troubleshooting
 9.2. DEBUGGING PROCEDURE PRIAG

This procedure is used for debugging various problems coming in PRIAG link like D
channel of any PDDI not coming in-service, call failing, etc. User has to enable the various
options as given below
Options 6 of the misc commands menu is used for debugging purposes
Following screen will appear on selecting this option
Edit the LOG files for PRIAG Call Controller

Chapter 9.
Press 0 for :: No Log File

Press 1 for :: Warning, Error
Press 2 for :: Notice, Warning, Error
Press 3 for :: Notice, Warning, Error, Debug, Verbose
Enter the level of debugging :: 3
Do you wish to Start Layer 2 and 3 Prints as well ?
Press y for YES and n for NO :: y
Do you wish to remove the previous LOG files ?
Press y for YES and n for NO :: n
Enter 'E' to EXECUTE / 'T' to TERMINATE (E/T) :
This command is used for debugging purposes by the Software Designers.
Expected problems & solutions
i) Debugging (PDDI is not coming in-service)
* Check the PDDI related data at PRIAG & ISDN-PBX, both should be match.
* Check E1 cables are connected physically at right place & PCM loop is ok.
ii) Debugging (calls are not successful)
* Check the subscriber data created at soft switch or not.
* Check the softswitch ipaddress given in the PRIAG
* Check the status of soft switch. It should be up and pinging from PRIAG.
* Check PDDI data & status at both ends PRIAG & EPBX.
* Ethereal tool can be used to find out cause of failure.
* Check Logger files
Above procedure can be followed through ngems gui also by enabling the respective
prints in Event configuration commands as shown below.
 9.3. DEBUGGING PROCEDURE TMG
108 C-DOT MAX-NG

Chapter 10.
Do’s & Don’ts

 10.1. DO’S
1. Take the backups at regular interval of time
2. Ensure the availability of tested spares
3. Ensure the availability of all required software releases.
4. Check the status of V5, PRI & SS7 links daily.
 10.2. DON’TS
1. Don’t switch off the power supply of the CACU chassis cards without proper
shutdown.
2. Don’t Jack out any card without proper shutdown.

Chapter 11.
Data Creation
C5 V5ag AN-RAX
SIP V5.2
192.168.103. 192.168.103.10
69 0 SGTK
192.168.103.99
DSP
AI=1 Ai=1
SIP1=91112555 VAR ID=1
001@192.168.10 VAR ID=1
Link type=V5.2 Link
3.100 type=V5.2
L3 ADDR=1
SUB=2555001 L3 ADDR=1
Area code=9111
Figure: Example showing network diagram of V5AG data creation

The data at V5 Access Gateway can be created by either executing commands from CLI or
from GUI. Here the data creation at V5AG is given. For the data creation at C5 soft switch
refer Soft Switch User Manual.
Execute the commands in the order given below either from CLI or from GUI. Both
options are given below
1. Create AI
2. Start AI
3. Displ-ai-status
4. Create subscriber
110 C-DOT MAX-NG

Data Creation
 11.1. COMMAND CRE-AI

Chapter 11.
 11.2. RUN COMMAND: START-AI
GUI showing the Start AI command parameters
112 C-DOT MAX-NG

Data Creation
 11.3. RUN COMMAND: DISPL-V5 AI OR LINK STATUS:
GUI showing the display AI Status command

Chapter 11.
 11.4. RUN COMMAND: CREATE SUBSCRIBER
GUI showing the Create Subscriber command
 11.5. PRIAG DATA CREATION

11.5.1. Command: Equip Port
Description: This command will equip the E1 ports
114 C-DOT MAX-NG

Data Creation
11.5.2. Command: Create Pddi

Description: This command will create the PDDI on a specific port

Chapter 11.
116 C-DOT MAX-NG

Data Creation
 11.6. TMG DATA CREATION

11.6.1. Command: MODIFY TMG CONFIGURATION
Give the required inputs and execute the command.

Chapter 11.
118 C-DOT MAX-NG

Appendix - A
Glossary
ACRONYMS-
PRIAG - Primary Rate Interface Access Gateway
NGTK - Next Generation Signaling Gateway
ISPBX - ISDN Private Branch Exchange
TDM - Time Division Multiplexing
MPC - Microprocessor Controller
NVRAM - Non Volatile Random Access Memory
OS - Operating System
HDLC - High Level Data Link Control
LE - Local Exchange
GUI - Graphic User Interface
CLI - Command Line Interface
RBT - Ring Back Tone
CLIP - Caller Line Identification Presentation
D-channel - Data Channel
QSIG - Q signaling
PDDI - Principle Direct Dialing Inward
DDI - Direct Dialing Inward
ILT - Integrated Local and Tandem
MAX - Main Automatic Exchange
NGN - Next Generation Networks
SS7 - Signaling System no. 7
PAG - PRI Access Gateway
V5AG - V5 Access Gateway
SGTK/NGTK- Next Generation Signaling Gateway
AN - Access Network
TDM - Time Division Multiplexing
MPC - Microprocessor Controller
NVRAM - Non Volatile Random Access Memory
OS - Operating System
HDLC - High Level Data Link Control
DTMF - Dual Tone Multiple Frequency
LE - Local Exchange
GUI - Graphic User Interface
CLI - Command Line Interface
RBT - Ring Back Tone
CLIP - Caller Line Identification Presentation
ILT - Integrated Local and Tandem
MAX - Main Automatic Exchange
NGN - Next Generation Networks
SS7 - Signaling System no. 7
MMI - Man Machine Interface
V5AG - Access Network Rural Automatic Exchange
IP - Internet Protocol
AGW - Access Gateway
SG - Signaling Gateway
MG - Media Gateway
MGC - Media Gateway Controller
MGCP - Media Gateway Controller Protocol
PSTN - Pubic Switches Telephone Network
LAG - Line Access Gateway
SIP - Session Initiated Protocol
FE - Front End
BE - Back End
SNMP - Simple Network Management Protocol
FCAPS - Fault Accounting Configuration Accounting Performance Security
RTP - Real Time Protocol
UDP - User Datagram Protocol
RFC - Request for Comments
IETF - Internet Engineering Task Force
IPV4 - Internet Protocol version no. 4
ETSI - Europe Telecom Standard Institute
PCM - Pulse Code Modulation
DTK - Digital Trunk
NGEMS - Next Generation Elementary Management System
MAC - Media Control Access
MMI - Man Machine Interface
LLO - Line Locked Out
BNP-ANNC - Bill Not Paid Announcement
BNP-DISC - Bill Not Paid Disconnection
DONA - Diversion On No Answer
DOB - Diversion On Busy
C-DOT MAX-NG
LINE ACCESS GATEWAY
(LAG) USER MANUAL
CENTRE FOR
Section No.431-005-1043
Practices
C-DOT MAX-NG
LINE ACCESS GATEWAY

(LAG) USER MANUAL
w.r.t. LAG Release

(CLAGL2_3_1.5_1)
&
IEMS Release (IEMS 3.1.2_4.1)
© 2016, C-DOT
Printed in India
C-DOT MAX-NG
LINE ACCESS GATEWAY (LAG) USER MANUAL
ISSUE 01
MARCH 2016
MAGH 2072
SERIES 000: OVERVIEW
© 2016 BY C–DOT, NEW DELHI
H:\HOME\NG-MAX\User\Final\CDOT-MAXNG-LAG-UMAN-v01.doc March 23, 2016

Chapter 1.
Introduction
1.1 11.7. PURPOSE AND SCOPE OF THE DOCUMENT
This document provides the general description of C-DOT Line Access Gateway unit
(LAGU). It also provides information regarding Hardware and Software architectures,
specifications, pre-requisites and installation procedure in different chapters.
 11.8. INTRODUCTION
C-DOT DSS-MAX comprises of 256-port RAX, SBM RAX and MAX-L and MAX-XL.
Majority of the 256-port and SBMs have been converted to ANRAX and RSUs
respectively, with inherent advantage of centralized administration/ maintenance at the
local exchange level. With the emergence of Voice-over-IP (VoIP) and convergence of
services over IP, telecom operators intend to evolve its PSTN network to an all IP
network using IP/MPLS technology.
Evolution path to next generation network for most carriers in the world is based on IP
technology. Converged voice, video and data services will be provided on the core network
using IP protocol. Telecom operators would like to migrate with minimum disruption in
subscriber services and protect the investment made in the existing networks.
 11.9. BACKGROUND
The main aim of C-DOT MAX-NG project is to upgrade the inherent technology of DSS-
MAX from TDM to IP for existing subscribers. DSS-MAX comprises of Central
Module(CM) & Base modules(BM) . CM does the switching function among the BMs and
BM consists of various Terminal Units (TU) to accommodate various types of interfaces. A
single BM consists of following terminal units.
 ATU – Consists of analog subscriber line termination Cards
 ISTU—Consists of ISDN subscriber line termination Cards
 SU –To handle CCS7 Signaling
 VU—To handle V5 interface
 DTU—To interface with digital trunk(PCM)
 TSU—Time switching Unit
 BPU—Base Processor Unit.
In MAX-NG architecture CM module is completely removed & a new centralized IP based
switching unit is developed, called as Soft Switch which will be installed in a Central
location.

Chapter 1
Various Access gateways have developed to handle the functionalities of various Terminal
Units.
 Line Access Gateway (LAG)—This gateway is responsible for TDM
switching and to convert Time Division Multiplexed (TDM) voice
samples to IP packets. Thus it provides the IP domain access to the
existing analog subscribers.
 PRI Access Gateway (PRIGW)—This gateway provides the interface
with ISDN PRI EPABX.
 V5 Access Gateway (V5AG) -- This gateway provides the interface with
ANRAX or RLC to handle V5 subscribers.
 Signaling Gateway (SG) & Media Gateway (MG) – These gateways
take care of CCS7 Singling & Media part.
This document describes the details of Line Access Gateway (LAG) architecture and the
conversion process.
6 C-DOT MAX-NG
Chapter 2.
System Architecture
 11.10. ARCHITECTURE OVERVIEW
The bulk part of existing DSS-MAX hardware is Terminal Unit (ATU) in which
subscribers lines are connected. In MAX-NG architecture this ATU hardware is retained.
LAG is implemented by connecting the Terminal Units (ATU) to NGTJ Card which acts
as a Gateway for interfacing with IP network. NGTJ card is capable of converting time
division multiplexed (TDM) voice circuits to IP packets and vice versa. These IP packets
are delivered over Ethernet links to IP network.
Thus Line Access Gateway (LAG) basically consists of Line TUs, TSI and Access Gateway
Module (NGTJ).
 11.11. SYSTEM CONFIGURATION
11.11.1. TU Configuration in LAG Architecture
The Analog Terminal Unit (ATU) is used for interfacing 128 analog line
terminations. TU consists of terminal cards (also called as Line Cards) having
interfaces up to 8 subscribers. The 8-bit digital (voice) output of four Line Cards is
multiplexed to form a 32-bit channel, 2 Mbps PCM link – also called a terminal
group (TG). Since a Terminal Unit has a maximum of 16 Terminal cards, there are
four such terminal groups.
The signaling information such as origination detection, answer detection, digit
reception etc. is separated by a scan/drive logic circuit and is sent to the Signaling
Processor (SP) on four different scan/drive signals. After validating these events, SP
reports these signals to Terminal Interface Controller (TIC) for further processing.
Based on the information received from TIC, it drives the event on the selected
terminal through scan/drive signals.
Terminal Interface Controller (TIC) controls the four terminal groups (TG) of 32
channels and multiplexes them to form a duplicated 128-channel, 8 Mbps link
towards NGTJ card. In concentration, three other Terminal Units share the 128-
channel link towards the NGTJ card to have 4:1 concentration. Figure 2 shows the
hardware architecture of a single Terminal Unit.

Chapter 2
Figure 1: Analog Terminal Unit

 11.12. NGTJ CARD IN LAG ARCHITECTURE
In LAG, to support redundancy, two numbers of NGTJ cards are used as copy-0 and copy-
1. NGTJ cards are installed in the BPU frame after removing all existing cards of BPU
including the motherboard. Also only TSI and PSU-II cards are remained in the TSU
frame and all other controller cards are removed. NGTJ cards will be installed in 2 slot
cabinet.
11.12.1. Interface between TU and NGTJ

Line Access Gateway System has various types of interfaces with various entities as
follows:
A) Ethernet Interface
8 C-DOT MAX-NG
SYSTEM ARCHITECTURE
Following are the Ethernet interfaces from NGTJ card:

 NGTJ Card interfaces with Class-5 Softswitch over Ethernet Link for SIP
based communication for call control messages.
 For remote management of LAG, there is SNMP based agent on LAG. This
agent has SNMPv3 based communication with the EMS manager through
Ethernet Link
 LAG also supports CLI interface using Telnet.
B) Serial RS232 Interface
This interface is provided in NGTJ so that the card can be configured locally
after connecting a RS232 interface cable using minicom terminal of a PC.
Terminal settings for RS232 Interface
Bps/Par/Bits :115200 8N1.
11.12.2. Redundancy
Each Terminal Interface Card (TIC) has two copies i.e. COPY-0 & COPY-1 in LAG
architecture same as in DSS-MAX architecture. Similarly two copies of NGTJ card
are used. There is a mate interface between NGTJ-0 and NGTJ-1 copies in chassis
on which both NGTJs can communicate to each other.
For supporting 2K subscribers, concept of concentration is used in LAG. It means
each Primary TU (PTU) along with three Concentration TUs (CTUs) will share
single 128 Time Slot TDM link towards TS. Figure 2 shows how, in a LAG, all the
four PTUs along with 12 CTUs interface with 2 copies of Time Switch & two copies
of NGTJ card

Chapter 2
Softswitch
IP Cloud
Ethernet
NGTJ-0
NGTJ –1 128 Ch, 8Mbps,

TDM links
TSI Interface cards (2 No’s)
P PTU11 PTU21 PTU31 PTU41

128 Ch, 8Mbps,
TDM links
CTU12 CTU22 CTU32 CTU42

128 Ch, 8Mbps,
TDM links

128 Ch, 8Mbps,
TDM links
Figure 2: Redundancy Architecture
10 C-DOT MAX-NG
SYSTEM ARCHITECTURE
11.12.3. Deployment View

11.12.3.1. Hardware Deployment
Hardware information of various units from deployment perspective in LAG
configuration is as follows:
a) Line cards (8 ports) 256 Nos (i.e., 16 TUs arranged in 4:1 concentration)
b) Terminal Interface Controller (TIC) cards 32 Nos (i.e., 16 TUs x 2 per TU)
c) Time Switch Unit (TSU) Frame (with TSI card only) 02 Nos (copy-0 and
copy-1)
d) PSTN Interface Card (NGTJ) 02 Nos (copy-0 and copy-1).
CTU12 PTU11 CTU22
CTU13 PTU21 CTU23
CTU14 PTU31 CTU24
CTU32 PTU41 CTU42
CTU33 CTU43
TSU (with 2 TSI
and 2 NGTJ
CTU34 CTU44
cards)
Figure 3: LAG Architecture
11.12.3.2. CHASSIS VIEW OF LAGU

i) Front view of LAGU (Line Access Gateway Unit)

Chapter 2
Figure 4: Front view of LAGU
Back View of LAGU (Line Access Gateway unit)
12 C-DOT MAX-NG
SYSTEM ARCHITECTURE
Figure 5: Back view of LAGU
11.12.4. Functionality
The LAG provides the following functionalities
 Supports 2048 subscriber in 4:1 concentration

Chapter 2
 Transparently supports all subscriber features of soft switch.

 Supports call waiting & hot line feature
 Supports FAX & G.711 Codec.
 Communicates with soft switch using SIP protocol.
 Supports Redundancy in NGTJ card level.
 Supports Fast Ethernet links (10/100 Base-T)
 Supports automatic line test feature.
 Can perform DGN(Diagnose) of all control cards
 Provides Traffic reports including performance report
 Supports Changed dial tone feature for Centrex members.
 Supports PCO call (16KHZ tone) & battery reversal.
14 C-DOT MAX-NG
Chapter 3.
User Data Creation

This chapter describes user data creation in LAG. Data can be created in LAG by two
methods
1. Graphical User Interface (GUI)
2. Command Line Interface (CLI)
 11.13. DATA CREATION BY GUI.
11.13.1. SCOPE
This section gives a graphical view of the steps involved in the data creation of LAG
using NGEMS.
11.13.2. Pre-requisite:
Client PC/Laptop should have Mozilla Firefox (above 3.0 Version).
Client PC/Laptop should have JRE version1.6.
Client PC/Laptop should have “.java.policy” for Windows PC/ Linux PC.
11.13.3. LAG EMS Interface
To open the GUI follow the steps
Step 1.
Open “firefox browser” on client machine
Step 2.
Enter the ip address of IEMS server with port no 9090 in address bar .
http://<ip address of EMS Manager>:9090
Eg. http://10.187.0.41:9090 where 10.187.0.41 is IP of EMS manager.
15 C-DOT MAX-NG
Chapter 4
Step 3.
Enter the valid user name and password.
Step 4.
Discover LAG in EMS for managing, configuring and monitoring.
(Refer to ANNEXURE A)
Step 5.
Right click on the required LAG node in EMS map view , “EMS” menu will be
shown.Click on LAG EMS menu

16 C-DOT MAX-NG
USER DATA CREATION

Step 6.
Default screen will be opened with four icons on EMS interface for “Chassis,
Configuration, Bulk Configuration and Performance. It will also open the chassis
(physical view of node) with already equipped Frames and Line Cards in LAG.
LAG Chassis interface displays the equipped cards at LAG with different color code
for TIC (Terminal Interface Card) and Line Card. Operational status with role of
terminal cards TIC i.e. in-service, out-of-service, active or standby is also
determined by status color icon on TIC card. One can see the different types of
Line Cards in frame with distinguished color of Line Card. Authorized operator
will be add or remove cards in frame via equip or unequip commands from the
chassis interface.
Following screen snapshot shows the LAG chassis with all equipped frames and line
cards.

Chapter 4


TIC/NGTJ with green colour means in-service active & yellow means in-service standby.
TIC/NGTJ with red colour means out service
Normal Line cards shown in green colour & CCB card marks in violet colour.
TTC card is marked with orange colour.
 11.14. DATA CREATION STEPS USING GUI
User data creation involves following steps
Configuration of system related parameters like creation of Exchange code, Area code, Country
code, Directory length etc.
Equipage of Frames
Equipage of Line cards
 Note -- Subscribers will be created via ngsm.
11.14.1. Configure System Related Parameters
Modify General Parameter commands are used for Modifying General Parameters
of system like Exchange code, Area code, Country code, Directory length etc
Open “Chassis “viewClick “Configuration” iconClick “System”Click
“Modify General Params”
18 C-DOT MAX-NG
USER DATA CREATION
Following input screen will be displayed where required information can be

modified as given in following example.
Exchange code : 2
Dir length : 6
Country code : 91
Area code : 1267
Special ringing flag disable/enable
Note – special Ringing flag default enable
Click “Next”
11.14.2. Equipage of Terminal unit (TU) Frame
One can equip new Terminal Interface card in the blank frame.
i) Open LAG chassis
Right click on “LAG” Node Click “EMS’ Click “LAG-EMS” LAG
chassis will Display
ii) Right click on Blank Frame  Click “Equip Frame”

Chapter 4
Following input form will be displayed
Inputs
Rack and frame number will be automatically populated from the clicked position of frame
Select the option for frame type “ATU”
Select TIC to be equipped in this frame “TIC id”
Output
On successful execution of equip frame command, default cards like power cards
along with TIC cards will be placed in chassis interface and current status of TIC
will be displayed.
11.14.3. Equip Line Cards
Line Cards can be equipped on the equipped frames where TIC are placed and line
cards slots are empty .One can equip Line card using the following command.
There are two types of lines card in the system
 Normal subscriber card
 CCB card ( for PCO subscriber)
20 C-DOT MAX-NG
USER DATA CREATION
Open “Chassis View”Right click equipped frame click on line card

configuration New window will be opened Right click on slot click equip line
card
Input form
Inputs:
Rack, frame and slot no. will be automatically populated.
Select the type of Line Card (it can be Sub-Lin or CCB)
Output
On successful execution of command, line card will be found equipped in given slot
with given Line type on chassis interface.

Chapter 4
11.14.4. Equip TTC (Terminal Testing Card) Card

The TTC card is used for performing automatic line testing on the subscriber line.
TTC card can be equipped by right clicking on the fourth equipped frame on 24 line
card slot. It will give the option for equip TTC if slot is empty. On selecting this
option TTC cards will be equipped at LAG and on successful completion TTC card
image will be updated on chassis interface
Open “Chassis View”  Right click on 4th equipped frame click on card
configuration  new frame window will be opened right click on 24th slot
select equip TTC card
Note: TU should be equipped and 24th slot should be blank.

22 C-DOT MAX-NG
USER DATA CREATION
 Output:
TTC card will be equipped successfully and TTC card image will be updated on chassis interface.

Chapter 4.
Other Commands
 11.15. SCOPE
This chapter describes the other commands of LAG using GUI and CLI.
 11.16. VARIOUS COMMANDS OF LAG UAINF GUI
11.16.1. Modify Status of Subscriber Line
Any subscriber can be made out of service or in service state. There are two ways to
modify the Subscriber line status
i) Through “chassis” view.
ii) Through “configuration” menu.
i) Modify subscriber line through chassis view.
Open “Chassis View”  Right click on frame select line card
configuration Right click on “line ”Select “Line”Click “Modify
status”
24 C-DOT MAX-NG
OTHER COMMANDS
Select “Circuit” numberClick “Next”
Following form will open

Chapter 5
Select “Maintenance status” as “frc-line-oos/ins or put-line-oos/ins”Click “Modify

status”
Output:
i) Subscriber line can be modified through “configuration” menu.

Open Chassis ViewClick “Configuration” iconClick “Subscriber” tabSelect
subscriberClick “Modify Line Status”
26 C-DOT MAX-NG
OTHER COMMANDS

Chapter 5
Following input form will open
Select Check box of “Maintenance Status”Select “frc-line-oos/ins” or “put-line-

oos/ins”Click “Modify Status”
28 C-DOT MAX-NG
OTHER COMMANDS
11.16.2. Modify Status of Line Card

Open “Chassis View”  Right click on frameclick on linecard configuration
Right click on line cardSelect “Line Card” option  Click “Modify line card
status”
Select “Status Change” Command as “frc-line-card-oos/ins” or “put-line-card-

oos/ins” Click on “Next”.
Output:
On successful execution of command, modify line card will be done suceesful
11.16.3. Delete Subscriber
Make a subscriber oos-opr as shown in 5.2.1
Open “chassis” viewClick “Configuration” menuclick on subscriber
tabSelect subscriberClick ”Delete” option
Following screen will be opened.

Chapter 5
Click “Next”
30 C-DOT MAX-NG
OTHER COMMANDS
Output:
Subscriber deleted successfully and subscriber directory number is added in frozen

list.
Note: To reuse the same directory number operator first has to unfreeze the given
directory number. Only then this number can be assigned to someone else.
Subscribers deleted successfully and subscriber’s directory number is added in
frozen list.
Note: To reuse the same directory number operator first has to unfreeze the given
directory number. Only then this number can be assigned to someone else.
Possible Failures;
Subscribers can be fully or partially deleted. Possible Failure :
1. Subscriber(s) are in observation.
2. Subscriber(s ) are having some facility.
3. Subscriber(s) are not oos-opr.11.16.3.1. Un-equip Line Card

Chapter 5
A line card can be un-equipped provided no subscriber is created in it.

Open Chassis View Right click on frame click on line card configuration line
card new window will be opened Select “Line Card”Click “Unequip”--
>click Next button
32 C-DOT MAX-NG
OTHER COMMANDS
Output
On successful execution of command, line card will be unequipped and colour of slot
will become grey(blank).

Chapter 5
11.16.4. Un-Equip the Frame

A Frame can be unequipped only when there are no cards equipped in the frame.
Open Chassis View Right click on tic card  Click “Unequip frame” Click on
“Next” button of input form.
Output
On successful execution of command, frame will be unequipped
34 C-DOT MAX-NG
OTHER COMMANDS
11.16.5. Modify Ten of a Subscriber

Subscriber TEN can be modified as follows
i) Make subscriber out of service as shown in 5.2.1.
ii) Modify TEN of a subscriber.
Open “chassis” viewClick “Configuration” menuSelect subscriberClick
”Modify Ten”

Chapter 5
Insert the new tenClick “Next”.

Inputs
Rack no ,frame no slot no and ckt no
Output
Subscriber ten is modified successfully.
36 C-DOT MAX-NG
OTHER COMMANDS
11.16.6. Modify Status of TIC/NGTJ Card (out of service)

Open chassis view Right click on tic card Click “Modify Status”select frc-
unit-oos click Next

Chapter 5
Output
On executing the command, status on TIC will be changed and will be reflected by
the color on the card.
11.16.6.1. Modify Status of TIC/NGTJ Card INSERVICE

Open chassis view Right click on tic card Click “Modify Status”select frc-
unit-ins click Next
38 C-DOT MAX-NG
OTHER COMMANDS
Output:
On executing the command, status on TIC will be changed and will be reflected by
the color of the card

Chapter 5
11.16.7. Run Test on Line

One can run various tests on line or line card and can see the values of various
parameters of test run. Operator can mention the type of test report while executing
the test i.e. brief or detail report.
Various test set:
 102 test—Open loop test towards subscriber line side. One can select report
format in brief or detail form. The output of this test gives the measured
value of capacitance, insulation, loop impedance etc on subscriber side.
 103 test—Card side test. The output of this test gives an information about
the health of the card.
Go to configuration Menu Click on subscriber TabSelect subscriber no Click

on test line Insert the test no and brief or detail option
Input
40 C-DOT MAX-NG
OTHER COMMANDS

Chapter 5
Output
On executing command, status of submission of test command on line will be given.

Test result of line can be viewed by selecting “view report” interface in Go to configuration menu.
Report test result/status -- >Double click on regarding test result
42 C-DOT MAX-NG
OTHER COMMANDS


 Run Test 107 ---This test for testing the Dial test ,Loop current test and loop
Resistance Test of phone .The output of this test gives an information about the
instrument(phone)Dial test OK or not .
 Procedure – make a call sub A to sub B,A and B are conversation.
 Go to configuration Menu click on subscriber TABselect subscriber
 click on test select test no 107 and press next Button. Now press keys 0-9
and star and #.

 Test result of line can be viewed by selecting “view report” interface in Go to
configuration menu. Report test result/status -- >Double click on regarding
test result.

Chapter 5


 OUTPUT:
 Test result of line can be viewed by selecting “view report” interface in Go to
configuration menu. Report test result/status -- >Double click on regarding
test result.

44 C-DOT MAX-NG
OTHER COMMANDS




 Run Test on Line Card
 Go to chassis view right click on frame select line card configuration
Right click on line card select test insert test no and brief or detail option

Chapter 5

Output :
Test result of line can be viewed by selecting “view report” interface in Go to
configuration menu. Report test result/status -- >Double click on regarding test
result
46 C-DOT MAX-NG
OTHER COMMANDS
11.16.8. DIAGNOSTICS of Controller Card

In lag there are two types of controller card, TIC and NGTJ. One can do the health
checkup by running diagnostics operations. Each type of card runs with two copies.
One copy act as the active copy and other act as the standby copy. To run diagnostic
on a particular card , one has to make the card out of service OPR.(OOS-OPR).

Chapter 5
Diagnostics of TIC card.

Open Chassis view Right click on TIC cardClick “Run Diagnostic”.
48 C-DOT MAX-NG
OTHER COMMANDS
Output:
Report shows the health status of TIC cards. Same way one can perform diagnostic
on NGTJ card also.
11.16.9. Switchover of Controller Cards (NGTJs/TICs)
In LAG there are two types of controller card, TIC and NGTJ. Each type of card
runs with two copies. One copy act as the active copy and other act as the Standby
copy. Operator can switch their role depending upon the requirement by running
the “Switchover” command.

Chapter 5
Switchover of TICs
Open “Chassis” viewRight click “TIC” card click switchover
50 C-DOT MAX-NG
OTHER COMMANDS
Following form will appear
Click “Next”

Chapter 5
Output:
52 C-DOT MAX-NG
OTHER COMMANDS
Switchover of NGTJ.
Open “Chassis” viewRight click on “NGTJ” card  Select Switchover Click
“Next

Chapter 5
Output:
54 C-DOT MAX-NG
OTHER COMMANDS
11.16.10. Display Commands

Display Unit Status
Open “Chassis “view Right Click on TIC cardclick “Display Details”

Chapter 5
Output:
56 C-DOT MAX-NG
OTHER COMMANDS
11.16.11. Display Line Card Status

Open “Chassis “view Right Click on Line cardSelect “Line card ”Click
“Display Status”.

Chapter 5
Output:
11.16.12. Subscriber Related Commands

Clicking on Configuration icon on main screen will bring the operator to
Configuration main screen. It has further sub-menus for “Subscriber related
commands “, “Miscellaneous command” , “System related commands” , “Query”
operations and “Report” . On clicking subscriber menu following interface will be
opened where one can execute the subscriber related commands.
Open “Chassis “viewClick “Configuration” iconClick “Subscriber” tab.
On clicking subscriber menu following interface will be opened.
58 C-DOT MAX-NG
OTHER COMMANDS
List of created subscribers will be shown and on selecting particular subscriber

further sub-menus in left side of panel will open.
11.16.13. Display Subscriber Details:-
Details of a subscriber can be seen by
Open “Chassis “viewClick “Configuration” iconClick “Subscriber” tab
Select subscriber Click “Detail”.

Chapter 5
Output:
CDR details of selected subscriber:-
11.16.14. CDR Details of a Subscriber can be seen by

Open “Chassis “viewClick “Configuration” icon Click “Subscriber”
tabSelect “Subscriber”Click “CDR details”
60 C-DOT MAX-NG
OTHER COMMANDS
Output shows the call status, calling and called number and other details of call. But
for this subscriber has to be put under originating or (and) terminating observation
as per requirement as explained in 5.12.3.
11.16.15. Modify Subscriber Observation

tabSelect “Subscriber”Click “Modify Observation”

Chapter 5
Following screen will be opened
Operator can make subscriber in different observation like originating, terminating.
62 C-DOT MAX-NG
OTHER COMMANDS
Select “Observations”Click “put in Observation” Observation will be

displayed in “Assigned Observation” field.
11.16.16. Modify line status of selected subscriber

Explained in step 5.2.1.
11.16.17. Modify TEN of selected subscriber
Subscriber TEN can be modified in three steps.
ii) Modify subscriber TEN as follows.
Open “Chassis “viewClick “Configuration” icon Click “Subscriber” tabSelect
“Subscriber”Click “Modify Ten”

Chapter 5
Following screen will be opened
Enter new TEN number Click “Next”

Verify changed ten of subscriber, select subscriber and click on “Details” in
subscriber menu.
11.16.18. Modify Terminating Facility (Call Waiting) of Subscriber.
Terminating facility of a subscriber can be modified in four steps as follows.
ii) Register terminating facility as follows.
tabSelect “Subscriber”Click “Modify Term Facility
64 C-DOT MAX-NG
OTHER COMMANDS
Following screen will be displayed
Select “Directory Number”Click “MODIFY”

Chapter 5
Following input screen will be displayed
Click “Next”
66 C-DOT MAX-NG
OTHER COMMANDS
Output:
Output displays that “Modification of Subscriber Terminating Facility Successful”.

Verify status of subscriber terminating facility can be done by clicking of “Modify
Term Facility” in subscriber menu, where operator can verify “Facility” status.
iii) Activate terminating facility as follows.
Click “Modify Term FacilitySelect “Directory Number

Chapter 5
”Click “Activate”
68 C-DOT MAX-NG
OTHER COMMANDS
Click “Next”
Output:
11.16.18.1. Output displays “Modification Successful”.
Verify status of subscriber terminating Facility can be done by clicking of “Modify
Term Facility” in subscriber menu, where operator can verify the “Facility” status.
iv) Make line in-service as shown in 5.2.1.
11.16.18.2. Delete the call waiting facility

1.Make subscriber out of service as shown in 5.2.1.
2.Deactivate terminating facility as follows.
tabSelect “Subscriber”Click “Modify Term Facility click Deactivate
Output:

Chapter 5
3. Delete terminating facility as follows

tabSelect “Subscriber”Click “Modify Term Facility click Delete
Make subscriber in-service as shown in 5.2.1
Output:
70 C-DOT MAX-NG
OTHER COMMANDS
11.16.19. Modify Originating Facility(HOT LINE)

There are two types of originating facilities which can be assigned to subscribers.
i) Timed hotline
ii) Un-timed hotline
Modify Timed/ Un-timed hotline facility
Originating facility of a subscriber can be assigned in four steps as follows.
1. Make subscriber out of service as shown in 5.2.1.
2. Register facility as follows
tabSelect “Subscriber”Click “Modify Orig Facility

Chapter 5
Click “MODIFY”
72 C-DOT MAX-NG
OTHER COMMANDS
Click “Next”

Chapter 5
Select “Facility Name”Enter “Hot Line Directory Number”Click “Next”
74 C-DOT MAX-NG
OTHER COMMANDS
Output:
Output displays that “Modification of Subscriber Originating Facility Successful”.

Verify the status of subscriber Originating Facility can be done by clicking of
“Modify Orig Facility” in subscriber menu, where operator can verify “Facility”
status and “Facility Name”.
1. Activate the facility as follows.
Click “Modify Orig FacilitySelect “originating subscriber facility”click Activate

Chapter 5
Click “Activate”
76 C-DOT MAX-NG
OTHER COMMANDS
Click “Next”

Chapter 5
Output:
Output displays that “Modification Successful”.

Verify the status of subscriber Originating Facility can be done by clicking of
“Modify Orig Facility” in subscriber menu, where operator can verify “Facility”
status and “Facility Name”.
2..Make subscriber In-service as shown in 5.2.1.
Delete Hotline facility

1).Deactivate the facility as follows.
a) Click “Modify Orig FacilitySelect “originating subscriber facility ”Click
Deactivate button
Output:
78 C-DOT MAX-NG
OTHER COMMANDS
2) Remove the hotline facility as follows

a) Click “Modify Orig FacilitySelect “originating subscriber facility ”click Delete button
3) Make subscriber In-service as shown in 5.2.1
11.16.20. Modify Centrex feature of a subscriber

A subscriber can be part of Centrex group. The Centrex group should be created
first in softswitch.
Subscriber can be made part of Centrex group through three steps as follows.
ii) Modify Centrex facility as follows.

Chapter 5

tabSelect “Subscriber”Click “Modify Centrex Facility”
Select “New Escape Code”Select “Abbreviated Length”
80 C-DOT MAX-NG
OTHER COMMANDS
Output:
Output displays that “Modification Successful”. When a subscriber is created as

Centrex number, its dial tone will be changed from normal to Centrex dial tone.
11.16.21. Miscellaneous Commands
Following commands come under this head..
Unfreeze Dirno
Frozen Dirno List
Display Subs Observation
USM User refresh
Create Special Number
Modify Special Number
Delete Special Number
Display Line Counter
Display Lag Release

Chapter 5
Display Lag Time

Start DB Sync (Not Supported in this release)
Create DB sync (Not Supported in this release)
Miscellaneous Commands can be Executed as follows
Open “Chassis “viewClick “Configuration” iconClick “Miscellaneous”
82 C-DOT MAX-NG
OTHER COMMANDS
11.16.22. Display Frozen Dirno List:

Open “Chassis “viewClick “Configuration” iconClick “Miscellaneous” Click
“Frozen Dirno”
Select “Date”Click “Submit”

Chapter 5
Output:
List of frozen list will be displayed.

Frozen no can be unfreezed one by one or unfreeze all by command provided
“Unfreeze” and “Unfreeze All”
11.16.23. Unfreeze Dirno
“Unfreeze Dirno”
84 C-DOT MAX-NG
OTHER COMMANDS
 Enter “Directory number to unfrozen”Click “Next”

Chapter 5
 Output:


11.16.24. Display Subs Observation
One can see the list of subscribers under different type of observation Org &
Terminating.
“Unfreeze Dirno”
86 C-DOT MAX-NG
OTHER COMMANDS
Output will show the list of subscribers under different type of observation Org &
Terminating.
11.16.25. USM User Refresh
USM User refresh command is used if operator opened SNMP error while working
through GUI.
“USM User refresh”

Chapter 5
11.16.26. Create Special Number

Special Number (100,101…) can be created with this command. This command will
be effective only when connection towards Soft Switch is down. The directory
number should belong to same LAG subscriber number.
“Create Special Number”
88 C-DOT MAX-NG
OTHER COMMANDS
Enter “Special Number”Enter “Directory Number”Click “Next”

Chapter 5
Output:
11.16.27. Modify Special Number

Special Number (100,101…) can be modified or reassigned to other directory
number with the help of this command.
“Modify Special Number”
90 C-DOT MAX-NG
OTHER COMMANDS
Enter “special Number”Click “Next”

Chapter 5
Enter “Directory Number”Click “Next”
92 C-DOT MAX-NG
OTHER COMMANDS
Output:
11.16.28. Delete Special Number

Special Number (100,101…) can be deleted with the help of this command.
“Delete Special Number”
Following screen will be displayed.

Chapter 5
Enter “Special Number”Click “Next”
94 C-DOT MAX-NG
OTHER COMMANDS
Output:
11.16.29. Display Line Counter

By this command one can see the counts of lines in different states. It will display the
result in following format like Number of line out of system, Lines out of system
operator, out of system external, out of system LLO, In-service line.
“Display Line Counter”

Chapter 5
Output displays as above.

11.16.30. Display Lag Release
Display Lag Release command displays LAG and Agent release version respectively.
“Display Lag Release”
96 C-DOT MAX-NG
OTHER COMMANDS
11.16.31. Display Lag Time

Display Lag Time command displays time of LAG.
11.16.32. Lag System Related Commands
System Commands provide interface options as follows.
Display General Parameter
Modify General Parameter
Display Timers
Modify Timers
Display Thresholds
Modify Thresholds
Display Charging Parameters
Modify Charging Parameters
Display Digit Length Parameters
Modify Digit Length Parameters
Display Lag Info

Chapter 5
Start (Not support in this release)

Stop (Not support in this release)
Release Install (Not support in this release)
Release Uninstall (Not support in this release)
Miscellaneous Commands can be Executed as follows
Open “Chassis “viewClick “Configuration” iconClick “System”
11.16.33. Display General Parameter

Display General Parameter command displays General Parameters of system like
Exchange code, Area code, Country code, Directory length etc
“Display General Params”
98 C-DOT MAX-NG
OTHER COMMANDS
11.16.34. Display Timers

Click on Display Timer button to see the values of timers set in the LAG. It will
open the result in the following manner..
“Display Timers”

Chapter 5
11.16.35. Modify Timers

One can modify the various timer value in the system.
“Modify Timers”
100 C-DOT MAX-NG

OTHER COMMANDS
Enter the value of “Tone Timers”Click “Next”

Chapter 5
Output:
11.16.36. Display Thresholds

Click on Display threshold button to see the values of various threshold defined in
the LAG. It will open the result in the following manner
“Display Thresholds”
102 C-DOT MAX-NG

OTHER COMMANDS
11.16.37. Modify Thresholds

Modify Thresholds command, Modified system Thresholds.
“Modify Thresholds”

Chapter 5
Enter System Threshold valuesClick “Next”
104 C-DOT MAX-NG

OTHER COMMANDS
Output:
11.16.38. Display Charging Parameters

Display Charging Parameters command, displays charging(sending 16khz tone)
Parameters of PCO subscriber. This command will be effective only when
connection towards soft switch is down. In this condition a PCO subscriber can only
make intra LAG call.
“Display Charging Params”

Chapter 5
11.16.39. Modify Charging Parameters

Modify Charging Parameters command, modifies Charging Parameters of PCO
subscriber.
“Modify Charging Params”
106 C-DOT MAX-NG

OTHER COMMANDS
Enter “Initial Charging units”Enter “Charging Periodicity”Enter “Charging

Units”Click “Next”

Chapter 5
Output:
11.16.40. Display Digit Length Parameters

Display Digit Length Parameters command displays maximum dialed digit length
Parameters of subscriber. Suppose when a subscriber dials with 1st digit as 2 , then
operator can set the maximum dialed digit say 7. So when LAG collects 7 digits
starting from digit 2, it immediately sends all the dialed digits towards soft switch
without waiting for intra digit time out.
“Display Digit Length Params”
108 C-DOT MAX-NG

OTHER COMMANDS
11.16.41. Modify Digit Length Parameters

Modify Digit Length Parameters command, Modifies inter digit length Parameters
of subscriber.
“Modify Digit Length Params”

Chapter 5
11.16.42. Display Lag Info

Display Lag info command, displays Lag system information like IP of both copy of
LAG, Floating IP of LAG, Softswitch IP, TIC status and Number of subscribers etc.
“Display Lag info”
110 C-DOT MAX-NG

OTHER COMMANDS
11.16.43. Query Related Commands

Following interface options are provided by Query as follows.
Subscriber query
Ten query
BNP query
Line status query
Special number query
Cdr query
Transition log query
Open “Chassis “viewClick “Configuration” iconClick “Query”.

Chapter 5
11.16.44. Subscriber Query

In this interface one can see the list of subscribers depending upon the selected line
Type, Line Category, Instrument Type, Subscriber priority and availed facility.
Clicking on subscriber query interface following form will be opened where all
query options are default set to all. One can select input values depending upon the
query to be made on subscriber data.
Open “Chassis “viewClick “Configuration” iconClick “Query”Click “Subs
Query”.
112 C-DOT MAX-NG

OTHER COMMANDS
5.1
Select subscriber query  click “Subscriber Query”

11.16.45. Ten query
Through this query interface one can see the list of terminal lines of particular type
which are equipped/Free/Assigned. Following interface shows the result for query
on the Free, sub-line terminal lines.
Open “Chassis “viewClick “Configuration” iconClick “Query”Click “Ten
Query”.

Chapter 5
Select admin status and line type queryClick “Submit query”
114 C-DOT MAX-NG

OTHER COMMANDS
Output:
Above screen shows the result of free subscriber ten query.
11.16.46. Line Status Query

Line status query commands; displays Line status (in-service, in-service normal, in-
service force, out of service operator, out of service system external, out of service
external, line loop out of service (LLO)) query.
Open “Chassis “viewClick “Configuration” iconClick “Query”Click “Line
Status Query”.

Chapter 5
116 C-DOT MAX-NG

OTHER COMMANDS
Select Line Status  Click “Submit Query”

Chapter 5
Output:
Above screen shows the result of ins-service line status query.

11.16.47. Special Number Query
Special number query commands; displays Special number query.
Open “Chassis “viewClick “Configuration” iconClick “Query”Click “Special
Number Query”.
118 C-DOT MAX-NG

OTHER COMMANDS
Click “Submit”

Chapter 5
Output:
Above screen shows the result of Special number query.

11.16.48. Cdr Query
From this query interface one can see the details of call records for particular
subscriber. Call records are available only when subscriber is put in particular
observation.
Open “Chassis “viewClick “Configuration” iconClick “Query”Click “Cdr
Query”.
120 C-DOT MAX-NG

OTHER COMMANDS
Enter “DIRNO”Select “Call Type”Select “Time field” (if cdr query required
for particular time duration otherwise deselect “Time Field ” to show all cdr of a
subscriber from the date subscriber putted in observation)Click “Submit”

Chapter 5
122 C-DOT MAX-NG

OTHER COMMANDS
Output:
11.16.49. Transition Log Query

This interface will be used to query on the transactions done in LAG. It will open
the following query form with possible query inputs values
Open “Chassis “viewClick “Configuration” iconClick “Query”Click “Trans
Log Query”.

Chapter 5
124 C-DOT MAX-NG

OTHER COMMANDS
Result of Transaction log query will be shown as below.
11.16.50. Report
Report Commands provide interface options as follows.
Test/Status
Bulk Config
Report Commands can be Executed as follows
Open “Chassis “viewClick “Configuration” iconClick “Report”

Chapter 5
11.16.51. Test/Status
Test/status command is used for display status of subscriber line test.
Open “Chassis “viewClick “Configuration” iconClick “Report”Click
“Test/Status”.
126 C-DOT MAX-NG

OTHER COMMANDS
5.2.51 Bulk Configuration

Bulk Configuration Command is used for Create Data.
One can create the data at LAG in bulk mode, where commands to be executed are
specified in text file and is submitted via Bulk configuration interface. For this, user
must have authority for creating the data in bulk mode. On clicking bulk
configuration icon on LAG main interface, file browser interface will be opened
where bulk data file from client location will be selected by operator. All commands
in file will be executed in system and result of each command can be seen from the
report interface.
Open “Chassis “viewClick “Bulk Configuration” icon

Chapter 5

5.2
Browse the path of text file and click open.
128 C-DOT MAX-NG

OTHER COMMANDS
Following output screen will be opened.
We can check the status of bulk configuration via following configuration report
Go to configuration Report bulk configuration

Chapter 5
11.16.52. PERFORAMANCE
Performance Commands provide interface options as follows.
Traffic Report
System Monitoring
Performance Commands can be Executed as follows
Open “Chassis “viewClick “Performance” icon

130 C-DOT MAX-NG

OTHER COMMANDS
5.3
11.16.53. TRAFFIC
Traffic command is used for start, stop and display of traffic report.
Traffic Commands provide interface options as follows.
Start
Stop
Display Active
View Report
Traffic Commands can be executed as follows
Open “Chassis “viewClick “Performance” icon Click “Traffic”


Chapter 5
11.16.53.1. START
Start command is used to start traffic report.
Start Commands can be executed as follows
Open “Chassis “viewClick “Performance” icon Click “Traffic”start

132 C-DOT MAX-NG

OTHER COMMANDS
Select “Start Date and time”Select “Stop Date and time”Select “Polling
interval”Click “Submit”
11.16.53.2. Stop
Stop command is used to stop traffic report.
Stop Commands can be executed as follows
Open “Chassis “viewClick “Performance” icon Click “Traffic”Click

“Stop”

Chapter 5
Click “Submit” to stop current traffic report

11.16.53.3. Display Active
Display Active command is used to Display Active traffic report status.
Display Commands can be executed as follows

“Display Active”
134 C-DOT MAX-NG

OTHER COMMANDS
11.16.53.4. View Report

View Report command is used to see the traffic report.
View Report can be executed as follows

“View Report” list of all Reports  select any one Report double click

Chapter 5
11.16.54. Monitoring
Monitoring interface is used to monitor the System Information
Monitor Commands Provide Interface options as follows.
System
CPU
Memory
Process
Services
11.16.54.1. System
System Commands provide the information of operating system, system name,
kernel version, system date, system up-time, Disk Details and Mount Details.
System Commands can be executed as follows
Open “Chassis “viewClick “Performance” icon Click “MonitoringClick

“System”
136 C-DOT MAX-NG

OTHER COMMANDS
11.16.54.2. CPU
CPU Commands provide the information of processor details and cpu utilization.
CPU Commands can be executed as follows

“CPU”

Chapter 5
11.16.54.3. Memory
Memory Commands provide the information of Memory and Swap Space
utilization Details..
Memory Commands can be executed as follows

“Memory”
138 C-DOT MAX-NG

OTHER COMMANDS
11.16.54.4. Process
Process Commands provide the information of Process name and the PID details.
Process Commands can be executed as follows

“Process”

Chapter 5
11.16.54.5. Services
Services Commands provide the information of Services name, Protocol, client
name and client port details..
Services Commands can be executed as follows

“Services”
140 C-DOT MAX-NG

OTHER COMMANDS
11.16.55. Backup & Restoration of Office Data

Backup command – it will initiate the backup of data and configuration at LAG and
will maintain the backed up file in the form of .tar at EMS.
Restore command – it will restore the LAG data and configuration from the backed
up .tar files maintained at EMS.
Backup:
Write Click on “Node”EMSBACKUP RESTORE

Chapter 5
Now a sub menu will pop up with options Take Backup , Restore from Client and
Check run Level. On Take Backup Option data backup will be taken at Client pc.
On restore data , data will be restored from Client PC. Check run level shows the
level of LAG i.e. level 1 to 5. Level 5 means Softswitch connectivity is up.
142 C-DOT MAX-NG

OTHER COMMANDS
Select “BACKEUP”

Chapter 5
Select “RESTORE”
Note: for restoring of data backup , system has to shutdown first.
144 C-DOT MAX-NG

OTHER COMMANDS
Select “CHECK LAG LEVEL”

On clicking “Check Run level” operator can see that system has come up.
 11.17. CLI INTERFACE FOR LAG

The Data Creation at LAG can also be alternatively using the Command Line Interface.
However this interface is strongly recommended to be used only when the EMS services are
not available due to some failure. Updating using this interface however does not cause any
inconsistency when the EMS services are restored back as the manager database gets
updated for all the CLI commands.
To open the CLI from any machine on the network give the command
$ telnet <LAG IP address> 3333.
For example
$ Telnet 192.168.103.115 3333
(where given IP is the Floating IP of LAG)
On being prompted for login enter user as “root” and give correct password.

Chapter 5
The prompt “CLI>> appears.

CLI>> cmdlist
The above command display the list of all the commands.
List of commands on CLI are
14. :equip frame To equip a frame in LAG

15. equip line_card To equip the LINE card in the LAG
16. equip ttc_card To equip the TTC card
17. cre sub To create a new subscriber
18. activate sub_org_fac To grant the hot line facility to subscriber
19. activate sub_trm_fac To activate the call waiting facility of the given
subscriber
20. deactivate sub_org_fac To De Activate the given subscriber's registered
originating facilities
21. deactivate sub_trm_fac To De Activate the given subscriber's registered
terminating facilities
22. force unit_ins To put the unit in service forcefully
23. force unit_oos To put the unit out of service forcefully
24. force line_card_ins To bring the LINE card in service forcefully
25. force line_card_oos To bring the LINE card out of service forcefully
26. force line_ins To bring the LINE in service forcefully
27. force line_oos To bring the LINE out of service forcefully
28. put unit_ins To put the unit in service normally
29. put unit_oos To put the unit out of service normally
30. put line_card_ins To bring the LINE card in service normally
31. put line_card_oos To bring the LINE card out of service normally
32. put line_ins To bring the LINE in service normally
33. put line_oos To bring the LINE out of service normally
34. mod sub To modify the subscriber Characteristics &
modification of the line characteristics of
146 C-DOT MAX-NG

OTHER COMMANDS
35. mod sub_ten To modify the assigned Terminal Equipment

Number to a DIRNO
36. mod sub_org_fac To modify the subscriber originating facility
37. mod sub_trm_fac To modify the subscriber terminating facility
38. mod thresholds To modify thresholds value
39. mod sub_obs To modify subscriber under observation
40. mod general_params To modify the system parameter
41. mod timers To modify the timer profile
42. del sub_bydirno To delete an existing subscriber by giving DIRNO in
input
43. del sub_byten To delete an existing subscriber by TEN
44. del sub_org_fac To remove the given originating facility
45. del sub_trm_fac To remove the given terminating facility
46. del sub_obs To delete the subscriber observation type
47. dgn NGTJ To run diagnostic on NGTJ card of the LAG
48. dgn tic To run diagnostic on TIC card of the LAG
49. dgn ttc To run diagnostic on TTC card of the LAG
50. displ unit_sts all To display information about the status of the units
of the LAG
51. displ card_sts To display information about the status of the
assigned lines of the card
52. displ line_sts To display information about the status of the
assigned line
53. displ sub To display a subscriber characteristics
54. displ sub_list To display the list of subscriber
55. displ ten To display TEN
56. displ line To display line attributes
57. displ sub_obs To display subscriber under observation
58. displ line_counters To display line counters
59. displ thresholds To display thresold

Chapter 5
60. displ general_params To display the system parameters

61. displ timers To display the timer profile
62. displ lag_info To display information about the equipped NGTJ &
TIC cards of LAG
63. displ release_info To display release information
64. switchover NGTJ To switchover a NGTJ from ACTIVE to STANDBY
65. switchover tic To switchover a TIC from ACTIVE to STANDBY
66. unequip frame To unequip a frame in LAG
67. unequip line_card To unequipe the LINE card in the LAG
68. unequip ttc_card To unequip the TTC card
69. unfreeze bydirno To delete the entry of the subscriber from the frozen
list
70. unfreeze bydate To delete the entry of the subscribers from the
frozen list on the basis of date
71. bulk cfg To bulk configuration
72. adduser To add user
73. clear To clear the display screen
74. deleteuser To delete user
75. editpasswd To change the password of a user
76. edituser To edit the user details
77. errcount To display error occured in processing of commands
78. incount To display no of commands received
79. keepalive To display keepalive time
80. logout To logout
81. man To help of command
82. outcount To display no of response of commands sent to user
83. prompt To change the prompt
84. who To display the current user
148 C-DOT MAX-NG

OTHER COMMANDS
 11.18. DETAIL DESCRIPTION OF CLI COMMANDS OF LAG

This section defines the command details for the LAG to configure, display the
configuration and other details valid for the LAG. This section specifies in details that what
inputs are required from the user and what output is displays to the user. It also specifies
the details of the report which are to be shown to the operator in case, any error occurred
in the system. On execution of a command, ADMN application running on the machine
first receives the inputs given by the operator through CLI, validates those inputs and then
processes it accordingly and sends the result back to CLI.
All the commands have been defined in the following format:
INPUT: Input parameters for the command.
ACTION: Functionality of the command.
OUTPUT: On execution of the every command there can be two results SUCCESS OR
FAILURE. In case of the SUCCESS, success message, vary from command to command,
will be displayed and in case of the FAILURE; reason of failure will be displayed to the
Operator.
REMARKS: Optional.
 11.19. EQUIPAGE COMMANDS
11.19.1. EQUIP-FRAME
Syntax: equip frame rack= frame= frame_type= tic_id=
INPUT:
RACK-NO : 1 TO 3
FRAME-NO : 1 TO 6
FRAME-TYPE: 1
TIC-ID : TIC01 TO TIC16 (or number between 1 and 16)
ACTION: This command is to equip a frame in LAG.
OUTPUT: SUCCESS/FAILURE
SUCCESS: Display string
“The given FRAME is successfully equipped in LAG.”
FAILURE: The reasons of failure
“Given FRAME is already equipped.”
11.19.2. EQUIP-LINE-CARD
Syntax: equip line_card rack= frame= slot= line_type=
INPUT:
LINE-TYP : CCB / SUB-LIN
CARD-SLOT : RACK(1 TO 3)-FRAME(1 TO 6)-SLOT(3 TO 10 or 17 to 24)

Chapter 5
ACTION: This command is for the equipage of the LINE card in the LAG, on
which actual subscribers are created.
SUCCESS: On successful execution of the command following string displays
“LINE card is successfully equipped in LAG.”
FAILURE: The reason of failures can be
“CARD is already equipped in the SLOT.”
“Given FRAME is not equipped.”
11.19.3. EQUIP TTC CARD
Syntax: equip ttc_card
INPUT: no input required.
ACTION: This command is for the equipage of the TTC card in the LAG
SUCCESS: On successful execution of the command following string displays
“TTC card is successfully equipped in LAG.”
FAILURE: The reason of failures can be
“CARD is already equipped in the SLOT.”
“Given FRAME is not equipped.”
 11.20. UNEQUIPAGE COMMANDS
11.20.1. UNEQP-FRAME
Syntax: unequip frame rack= frame=
INPUT:
RACK-NO : 1 TO 3
FRAME-NO : 1TO 6
ACTION: This command is for the unequipage of the FRAME from a LAG.
SUCCESS: The successful completion of the command will display the following
string
“FRAME is successfully unequipped from the LAG.”
FAILURE: The reasons of the failure can be
“FRAME is not equipped in the LAG.”
“CARD is equipped in the FRAME.”
150 C-DOT MAX-NG

OTHER COMMANDS
11.20.2. UNEQP-LINE-CARD
Syntax: unequip line_card rack= frame= slot=
INPUT:
CARD-SLOT : RACK (1 TO 3)-FRAME (1 TO 6)-SLOT (3 to 10 or 17 TO 24)
ACTION: This command is for the removal of a line card from the given slot.
string
“CARD is successfully unequipped from the slot.”
“CARD is not equipped in the SLOT.”
“SUBSCRIBERS are created in the CARD.”
11.20.3. UNEQP-TTC-CARD
Syntax: unequip ttc_card
INPUT: No inputs required.
ACTION: This command is for the removal of a ttc card from the given slot.
string
“CARD is successfully unequipped from the slot.”
“CARD is not equipped in the SLOT.”
 11.21. DISPLAY COMMANDS
11.21.1. DISPL-LAG-INFO
Syntax: displ lag_info
INPUT: No Input required.
ACTION: This command is to display information about the equipped TTC, TIC &
NGTJ cards of LAG.
SUCCESS: On successful Operation of the command it will show the status of the
NGTJ card equipped in LAG.
NGTJ-0 OOS
NGTJ-1 INS
TIC01-0 INS

Chapter 5
TIC01-1 INS-STBY
“No card is equipped in the LAG.”
11.21.2. DISPL-CARD-STS
Syntax: displ card_sts rack= frame= slot=
rack = [ 1..3 ] , frame = [ 1..6 ] , slot = [ 3..10 or 17..24 ]
INPUT
SLOT : RACK-FRAME-SLOT
ACTION: This command is for the display of the Terminal card status in a LAG.
SUCCESS: On successful Operation of the command it will show the list of the
Terminal Equipment Number with the given status.
SLOT : CARD STATUS
1-1-4 INS
“ No CARD is Equipped”
11.21.3. DISPL-TEN
Syntax: displ ten adm_sts= line_type=
INPUT:
STATUS : FREE/ASSGN/UNEQPD/EQPD
LINE-TYPE : CCB / SUB-LIN
ACTION: This command is for the display of the Terminal Equipment Number in a
LAG for the given status.
SUCCESS: On successful Operation of the command it will show the list of the
Terminal Equipment Number with the given status.
Status : EQPD
TEN : 1-4-5-1
1-4-5-2
“ No TEN of the Given line type”
“ No TEN with the given status”
152 C-DOT MAX-NG

OTHER COMMANDS
11.21.4. DISPL-RELEASE-INFO
Syntax: displ release_info
INPUT: No Input required.
ACTION: This command is to display information about the LAG and AGENT
release.
SUCCESS: On successful Operation of the command it will show the release of the
LAG and AGENT.
*****************************************************************
* Result of display release info *
*****************************************************************
LAG Release = clagl3_2_1.1_1
Agent Release = EMSL2.1.2_1.1
“No release is installed”
11.21.5. DISPL-UNIT-STATUS
Syntax: displ unit_sts all
INPUT:
UNIT ID: 1 for tic01...2 for tic01-1tic16-1, 33 for NGTJ0-0,34 for NGTJ0-1,35 for
ttc
RANGE OF INPUT VALUES
unit_id = [1..35] [ 1 for tic01-0 , 2 for tic01-1,,,,32 for tic16-1, 33 for pic-0, 34
for pic-1, 35 for ttc
ACTION: This command is to display the status of all the TICs, NGTJ and TTC.
SUCCESS: On successful Operation of the command it will show the status of tics,
NGTJ and ttc.
Result of display unit sts all
****************************************************
Unit ID Unit Status
****************************************************
tic01-0 oos-opr
tic01-1 oos-opr

Chapter 5
tic02-0 oos-opr
tic02-1 oos-opr
tic03-0 oos-opr
tic03-1 oos-sys
tic04-0 oos-opr
tic04-1 oos-opr
tic05-0 ins-act
tic05-1 ins-sby
tic06-0 oos-sys
tic06-1 oos-ini
tic07-0 oos-sys
tic07-1 oos-sys
tic08-0 oos-sys
tic08-1 oos-sys
tic09-0 oos-sys
tic09-1 oos-sys
tic10-0 oos-opr
tic10-1 oos-opr
tic11-0 oos-opr
tic11-1 oos-opr
tic12-0 oos-opr
tic12-1 oos-opr
tic13-0 oos-ini
tic13-1 oos-ini
tic14-0 oos-opr
tic14-1 oos-opr
tic15-0 oos-opr
tic15-1 oos-opr
tic16-0 oos-opr
tic16-1 oos-opr
NGTJ-0 ins-act
NGTJ-1 oos-ini
ttc oos-suspect
154 C-DOT MAX-NG

OTHER COMMANDS
11.21.6. DISPL-LINE-STATUS
Syntax: displ line_sts ten= ten=<rack>-<frame>-<slot>-<ckt>
INPUT:
rack=[1..3]
frame=[1..4]
slot = [3..10] or [17..24]
ckt= [1..8]
input help
rack = [ 1..3 ] , frame = [ 1..6 ] , slot = [ 3..10 or 17..24 ] , ckt = [ 1..8 ]
ACTION: This command displays of information about the assigned line
SUCCESS: On the successful completion of the command following string displays
*************************************************************
* Result of display line sts *
*************************************************************
TEN = 1-2-17-1
Adm-Status = assigned
Mnt-Status = ins-frc
Dir No. = 22222171
Call Status = idle
11.21.7. DISPL-SUB
Syntax: displ sub dirno=
INPUT: Directory number.
ACTION: This command displays the subscriber characteristics.
Example:
INPUT:
CLI>>displ sub dirno=273246
OUTPUT:
****************************************************************
* Result of display subscriber *
****************************************************************
Subscriber details are:
Dir No. = 273246

Chapter 5
TEN = 1-2-23-6
Inst Type = dtmf
Line Type = ccb-line
Line Category = 1
Subs Priority = 1
Escape Code = Not a CNTRX member
Abbriviated Length = 0
ObservationType = orignating
Orignating facilities are:
Name = None Status = N/A Htln Dir No. = N/A
Terminating facilities are:
Name = None Status = N/A
11.21.8. DISPL-LINE
Syntax: displ line_sts ten=
INPUT:
ten=<rack>-<frame>-<slot>-<ckt>
rack=[1..3] frame=[1..4] slot = [3..10] or [17..24] ckt= [1..8]
ACTION: This command is to display the line attributes
SUCCESS: On successful Operation of the command it will show the status of the
particular ten.
*************************************************************
* Result of display line sts *
*************************************************************
TEN = 1-2-17-1
Adm-Status = assigned
Mnt-Status = ins-frc
Dir No. = 22222171
Call Status = idle
11.21.9. DISPL-SUB-OBS
Syntax: displ sub_obs dirno=
INPUT: Input parameters are optional.
ACTION: This command is to display the subscriber under observation.
156 C-DOT MAX-NG

OTHER COMMANDS
SUCCESS: On successful Operation of the command it will show the type of
observation for the particular subscriber or the list of subscribers.
***********************************************************************
* Result of display subscriber in observation *
***********************************************************************
Dir No. = 22222171
ObservationType = orignating, terminating
“No subscriber is under observation.”
“Wrong dirno is given.”
11.21.10. DISPL-LINE-COUNTERS
Syntax: displ line_counters
INPUT: No Input parameters required.
ACTION: This command is to display the line counter.
SUCCESS: On successful Operation of the command it will show the status of all
the subscribers.
***********************************************************************
* Result of display line counters *
***********************************************************************
Number Of Line OOS-SYS = 41
Number Of Line OOS-OPR = 1770
Number Of Line OOS-EXT = 0
Number Of Line OOS-OUT = 0
Number Of Line OOS-LLO = 0
Number Of Line OOS-Trans = 0
Number Of Line UND-MTC = 1811
Number Of Line In Service = 141
Number Of Line inservice Faulty = 0
Number Of Line inservice LLO = 0
11.21.11. DISPLAY THRESHOLD
Syntax: displ thresholds

Chapter 5

ACTION: This command is to display the threshold..
SUCCESS: On successful Operation of the command it will show the threshold of
LAG.
***********************************************************************
* Result of display thresholds *
***********************************************************************
Warning Threshold Clear = 20
Minor Threshold Clear = 50
Major Threshold Clear = 60
Critical Threshold Clear = 70
Warning Threshold Raise = 50
Minor Threshold Raise = 60
Major Threshold Raise = 70
Critical Threshold Raise = 80
11.21.12. DISPLAY GENERAL PARAMS
Syntax: displ general_params
INPUT: no Input parameters are required.
ACTION: To display the value(s) of given system parameter or all the system
parameters.
SUCCESS: On the successful completion of the command the list of all the system
parameters or the given parameters with the value of the parameter depends on the
input.
***********************************************************************
* Result of display general parameters *
***********************************************************************
Exc. Code Length = 4
Dirno Length = 8
BM Num = 1
Exc. Code = 2222
DSP IP Add = 192.168.2.82
Country Code = 91
158 C-DOT MAX-NG

OTHER COMMANDS
Area Code = 11
Country Area Code = 9111
11.21.13. DISPL-TIMERS:
Syntax: displ timers
ACTION: This command is to display the timer profile
SUCCESS: On successful Operation of the command it will show the timer profile
***********************************************************
* Result of display timers *
***********************************************************
DT Timer = 100
BT Timer = 300
DRB Timer = 3000
DNU Timer = 300
DCR Timer = 2000000
DCNG Timer = 300
DDRB Timer = 3000
DTD Timer = 100
DWD Timer = 100
DPI Timer = 300
DAF Timer = 300
DZ Timer = 400
DP Timer = 300
DS Timer = 2000000
DHOLD Timer = 2000000
DPITConv Timer = 30
DAFTConv Timer = 30
DPAYT Timer = 300
DSLIT Timer = 2000000
DSIT Timer = 300
DINTT Timer = 100
DCLRT Timer = 30

Chapter 5
DCONT Timer = 2000000

DVSIT Timer = 2000000
DCSH Timer = 600
 11.22. SUBSCRIBER CREATION/FACILITIES RELATED COMMANDS
11.22.1. CRE-SUB
Syntax: cre sub dirno= ten= inst_type= line_type= line_ctgy= sub_priority=
no_of_org_fac= no_of_trm_fac= org_fac= trm_fac=
INPUT:
DIRNO : DIGIT NUMBER
TEN : RACK(1 TO 3)-FRAME(0 TO 6)-SLOT(3to 10 or 17 to 24)-
CKT(1TO 8)
LIN-TYP : SUB-LIN/CCB
INS-TYP : DECAD/DTMF
LINE-CTGY : 1to 7
SUB-PRIORITY : 1to 8
ESC_CODE : 0 & 2 to 9(default NONE)
ABBR_LEN : should be same as defined in soft switch (Non-centrex)
ORG-FCLTY : NO-FCLTY/TIMED-HTLN/UNTIMED-HTLN
TRM-FCLTY : NO-FACLTY/CALL-WTNG
ACTION: This command is for the creation of a subscriber data specific to LAG.
“Successfully created the subscriber.”
FAILURE: The reasons of command failure are
“DIRNO already exists.”
“TEN is already assigned.”
“Facility is not valid for the given line type.”
REMARKS: ALL subscriber facilities are there at the SS(soft switch) except the
HOTLINE and CALL WAITING. HOTLINE and CALL WAITING are not
allowed for the CCB subscribers.
11.22.2. MOD-SUB-TEN
Syntax: mod sub_ten dirno= ten=
INPUT: DIRNO DIRECTORY NUMBER
160 C-DOT MAX-NG

OTHER COMMANDS
NEW-TEN : RACK(1 TO 3)-FRAME(0 TO 6)-SLOT(3 TO 10 or 17 to 24) -

CIRCUIT (1TO 8)
ACTION: This command is used to modify the assigned Terminal Equipment
Number to a DIRNO.
“Successfully modified the TEN”
FAILURE: The reason of command failures are
“Subscriber is not OOS.”
“NEW-TEN is already assigned.”
“Given DIRNO does not exists.”
11.22.3. MOD-SUB-ORG-FAC
Syntax: mod sub_org_fac dirno= facility= htln_dirno=
INPUT : DIRNO : DIRECTORY NUMBER
/* htln_dirno is optional input */
ACTION: This command is to give the subscriber facility or to remove the given
facility.
“Successfully modified the FACILITY”
11.22.4. MOD-SUB-TRM-FAC
Syntax: mod sub_trm_fac dirno= facility=
INPUT: DIRNO : DIRECTORY NUMBER
ORG-FCLTY : NO-FCLTY/CALL-WTNG
ACTION: This command is to give the subscriber facility or to remove the given
facility.
FAILURE: The reason of command failure can be
“Given DIRNO does not exist.”

Chapter 5
11.22.5. MOD-SUB
I) Syntax: mod sub dirno= sub_priority=
INPUT: DIRNO DIGIT NUMBER
SUB-PRIORITY : 1to8
ACTION: This command is used to modify the priority of the subscriber
line.
SUCCESS: On the successful completion of the command following string
displays
“Successfully modified the STATUS.”
II) Syntax: mod sub dirno= line_type= inst_type=
INPUT: DIRNO : DIGIT NUMBER
LINE-TYPE : 1-->sub-line, 2-->ccb-line
INST-TYPE : 1-->dec, 2-->dtmf
ACTION: This command is for the modification of the line type or the
instrument type.
displays
“Successfully modified the Characteristics.”
III Syntax: mod sub dirno= ESC_CODE= ABBR_LEN
INPUT: DIRNO : DIGIT NUMBER
ESC_CODE : As defined in Soft Switch
ABBR_LEN : As defined in Soft Switch
ACTION: This command is for including a LAG subscriber in Centrex
group as configured in soft switch .
(NOTE:- when a subscriber put in centrex , its dial tone changed to Centrex
dial tone. On pressing escape code normal dial tone will come.)
displays
“Successfully modified the Characteristics.”
162 C-DOT MAX-NG

OTHER COMMANDS
11.22.6. MOD-THRESHOLD
Syntax: mod thresholds warning_clr= minor_clr= major_clr= critical_clr=
warning_rse= minor_rse= major_rse= critical_rse=
INPUT: Input parameters are optional for this command and values for
parameters are between 0 to 100 */
“Successfully modified the values”
11.22.7. MOD-SUB-OBS
Syntax: mod sub_obs dirno= obs_type=
INPUT: obs_type=[1,2,3,4] 1-->originating, 2-->terminating, 3-->malicious, 4--
>facility
More than one obs_type can be entered at a time by separating ',' i.e 1,3 can be
entered for obs_type for assigning originating and malicious observation type*/
“Successfully modified the observations”
“directory number does not exist”
11.22.8. MOD-GENERAL-PARAMS
Syntax: mod general_params dirno_len= exc_code= country_code= area_code=
mpc_ipadd=
INPUT: Input parameters are optional for this command
dirno_len=[5..8]
ACTION: To modify the value of given system parameter.
SUCCESS: On the successful completion of the command it will displays the
following string along with the parameter name and OLD & MODIFIED value of
that parameter.
“Successfully modified the Parameter.”
“Value of the parameter is out of range.”
11.22.9. MOD-TIMERS
Syntax :mod timers dtt_timer= btt_timer= drb_timer= dnu_timer= dcr_timer=
dcng_timer= ddrb_timer= dtd_timer= dwd_timer= dpit_timer= daft_timer=

Chapter 5
dz_timer= dp_timer= ds_timer= dhold_timer= dpitconv_timer= daftcon_timer=

dpayt_timer= dslit_timer= dsit_timer= dintt_timer= dclrt_timer= dcont_timer=
dvsit_timer= dcsh_timer=
INPUT: input parameters are optional for this command
ACTION: To modify the value of given system parameter.
SUCCESS: On the successful completion of the command it will displays the
following string along with the parameter name and OLD & MODIFIED value of
that parameter.
“Successfully modified the Parameter.”
“Value of the parameter is out of range.”
 11.23. SUBSCRIBER DELETE COMMANDS
11.23.1. DELETE-SUB BY DIRNO
Syntax: del sub_bydirno dirno=
INPUT: DIRNO (DIRECTORY NUMBER)
ACTION: This command is to delete an existing subscriber by giving the DIRNO
“Successfully deleted the subscriber.”
FAILURE: The reason of command failure can
“The given DIRNO does not exists.”
“Given TEN is not assigned.”
11.23.2. DELETE-SUB BY TEN
Syntax : del sub_byten ten=
INPUT: TEN : RACK-FRAME-SLOT-CIRCUIT
ACTION: This command is to delete an existing subscriber by giving the TEN
corresponding to that DIRNO.
“Successfully deleted the subscriber.”
FAILURE: The reason of command failure can
“The given DIRNO does not exist.”
“Given TEN is not assigned.”
164 C-DOT MAX-NG

OTHER COMMANDS
11.23.3. DEL-SUB-TRM-FAC
Syntax: del sub_trm_fac dirno= facility=
TRM-FCLTY : NO-FACLTY/CALL-WTNG
ACTION: This command is to withdraw the given subscriber facilities.
“Successfully withdrawn the subscriber facility.”
“The given DIRNO does not exists.”
“Facility is not given to subscriber.”
11.23.4. DEL-SUB-ORG-FAC
Syntax: del sub_org_fac dirno= facility=
ACTION: This command is to withdraw the given subscriber facilities.
“Successfully withdrawn the subscriber facility.”
“The given DIRNO does not exist.”
“Facility is not given to subscriber.”
11.23.5. DEL-SUB-OBS
Syntax: del sub_obs dirno= obs_type=
INPUT:
DIRNO: DIRECTORY directory number
OBS TYPE :obs_type=[1,2,3,4] 1-->orignating, 2-->terminating,
3-->malicious, 4-->facility
More than one obs_type can be entered at a time by separing ',' i.e 1,3 can be
entered for obs_type for assigning orignating and malicious observation type
ACTION: This command is to delete the given subscriber which is under
observation.

Chapter 5
“Successfully withdrawn the subscriber from observation.”

“The given DIRNO is not under observation.”
 11.24. STATUS CHANGE COMMANDS
11.24.1. PUT-UNIT-INS
Syntax: put unit_ins unit_id=
INPUT: CARD-ID : NGTJ OR TIC Id or TTC
ACTION: This is to bring the NGTJ/TIC/TTC card in service normally.
SUCCESS: On the successful completion of the command the string is displays
“Successfully changed the status.”
“CARD is not present physically.”
“SLOT is not equipped.”
11.24.2. PUT-LINE-CARD-INS
Syntax: put line_card_ins rack= frame= slot=
INPUT: CARD-SLOT : RACK-FRAME-SLOT
ACTION: This is to bring the LINE card in service normally.
“SLOT is not equipped.”
“LINE CARD is not present physically.”
11.24.3. PUT-LINE-INS
Syntax : put line_ins ten=
ACTION: To put the TEN in service normally by giving either the DIRNO or the
TEN corresponding to the DIRNO.
166 C-DOT MAX-NG

OTHER COMMANDS
“DIRNO does not exist.”

“TEN is not assigned.”
11.24.4. FRC-UNIT-INS
Syntax: force unit_ins unit_id=
INPUT: CARD-ID : NGTJ OR TIC or TTC
ACTION: This is to bring the NGTJ/TIC/TTC card in service forcefully.
“SLOT is not Equipped.”
11.24.5. FRC-LINE-CARD-INS
Syntax: force line_card_ins rack= frame= slot=
ACTION: This is to bring the LINE card in service forcefully.
“SLOT is not Equipped.”
“LINE CARD is not present physically.”
11.24.6. FRC-LINE-INS
Syntax: force line_ins ten=
DIRNO : DIRECTORY NUMBER
ACTION: To put the TEN in service forcefully by giving either the DIRNO or the
TEN corresponding to the DIRNO.
“DIRNO does not exists.”

Chapter 5

11.24.7. PUT-LINE-OOS
Syntax: put line_oos ten=
ACTION: To put the TEN out of service normally by giving either the DIRNO or
the TEN corresponding to the DIRNO.
11.24.8. FRC-UNIT-OOS
Syntax: force unit_oos unit_id=
INPUT: CARD-ID : NGTJ/TIC/TTC
ACTION: This is to bring the NGTJ/TIC/TTC card out of service forcefully.
11.24.9. FRC-LINE-CARD-OOS
Syntax: force line_card_oos rack= frame= slot=
ACTION: This is to bring the LINE card out of service forcefully.
11.24.10. `FRC-LINE-OOS
Syntax: force line_oos ten=
168 C-DOT MAX-NG

OTHER COMMANDS
ACTION: To put the TEN out of service forcefully by giving either the DIRNO or
the TEN corresponding to the DIRNO.
11.24.11. PUT-LINE-CARD-OOS
Syntax: put line_card_oos rack= frame= slot=
ACTION: This is to bring the LINE card out of service normally.
11.24.12. PUT-UNIT-OOS
Syntax: put unit_oos unit_id=
INPUT: CARD-ID : NGTJ/TIC/TTC
ACTION: This is to bring the NGTJ/TIC/TTC card out of service normally.
 11.25. SWITCH OVER COMMANDS
11.25.1. SWITCH-OVER-NGTJ
Syntax: switchover NGTJ <unit_id>
INPUT: UNIT ID : NGTJ-0/NGTJ-1
ACTION: This command is for switchover of NGTJ cards in LAG.
SUCCESS: On successful execution of the command displays

Chapter 5
“The Switchover of Card is successful”

FAILURE: The reasons of the failure can be “Other card in not Inservice.”
11.25.2. SWITCH-OVER-TIC
Syntax: switchover tic <unit_id>
INPUT: UNIT-ID : TIC
ACTION: This command is for switchover of TIC cards in LAG.
SUCCESS: On successful execution of the command displays
“The Switchover of Card is successful”
“Other card in not Inservice.”
 11.26. TERMINAL TESTING AND DIAGNOSTICS RELATED COMMANDS
11.26.1. DGN-NGTJ
Syntax: dgn NGTJ <unit_id>
INPUT: UNIT-ID : NGTJ-ID
ACTION: To test a unit of the LAG.
“Successful.”
“CARD is not equipped.”
11.26.2. DGN-TIC
Syntax: dgn tic <unit_id>
INPUT: UNIT-ID : TIC-ID
“Successful.”
11.26.3. DGN-TTC
Syntax: dgn ttc
170 C-DOT MAX-NG

OTHER COMMANDS
INPUT:No input parameters required.

“Successful.”
 11.27. SUBSCRIBER FACILITY COMMANDS
11.27.1. ACTIVATE SUB ORG FAC
Syntax: activate sub_org_fac dirno= facility=
FCLTY : 1-->timed-htln, 2-->untmd-htln, 0-->none
ACTION: This command is to give the subscriber facility to activate the given
facility.
11.27.2. DEACTIVATE SUB ORG FAC
Syntax: deactivate sub_org_fac dirno= facility=
FCLTY : 1-->timed-htln, 2-->untmd-htln, 0-->none
ACTION: This command is to give the subscriber facility to deactivate the given
facility.

Chapter 5
11.27.3. ACTIVATE SUB TRM FAC

Syntax: activate sub_trm_fac dirno= facility=
FCLTY : 1-->call-wtng, 0-->none
ACTION: This command is to give the subscriber facility to activate the given
facility.
“Given DIRNO does not exists.”
11.27.4. DEACTIVATE SUB TRM FAC
Syntax: deactivate sub_trm_fac dirno= facility=
FCLTY : 1-->call-wtng, 0-->none
ACTION: This command is to give the subscriber facility to deactivate the given
facility.
“Given DIRNO does not exists
11.27.5. UNFREEZE BY DIRNO
Syntax: unfreeze bydirno dirno=
ACTION: This command is to delete the entry of the subscriber from frozen table.
“Subscriber is successfully unfreezed”
“Subscriber is not deleted.”
172 C-DOT MAX-NG

OTHER COMMANDS
 11.28. UNFREEZE BY DATE

Syntax: unfreeze bydate date=
INPUT: input parameter is optional.
ACTION: This command is to delete the list of subscriber or single subscriber from frozen
table.
“Subscriber is successfully unfreezed”
“Subscriber is not deleted.”

Chapter 12.
Specifications
 12.1. CAPACITY
A maximum number of 2048 subscribers are supported by a LAG in 1:4 concentrations
and is configured in redundancy mode. The system can handle 5000 BHCA.
 12.2. INTERFACE TOWARDS SOFTSWITCH
The NGTJ card is interfaced with the Softswitch through Ethernet links (RJ45).
 12.3. POWER
Power is derived from nominal –48v DC.
 12.4. SERIAL INTERFACE
Serial RS232 interface provides the flexibility of connecting terminals to the processors as
is done for BM or AM in current DSS-MAX architecture. Following serial RS232
interfaces supported in NGTJ.
MPC Processor and DSP
 12.5. PROTOCOL
Session Initiation Protocol (SIP) is used between LAG and soft switch for various call
control/signalling purposes.
 12.6. DIAGNOSTICS
Health log of the analog subscriber line card and lines can be tested. Diagnostics for
controller card (TIC) and NGTJ is also possible.
174 C-DOT MAX-NG

Annexure -A
Site and Exchange Management

Site Registration Interface Usage:
Any device which is to be added in IEMS should belong to one exchange under one site.
There are following steps to register a site and exchange in IEMS:
To open the GUI follow the steps
Step1.
Open “Firefox browser “on client machine
Step2.
Enter the ip address of IEMS server with port no 9090 in address bar .
http://<ip address of EMS Manager>:9090
Eg. http://192.168.103.77:9090 where 192.168.103.77 is IP of EMS manager.

Annexure - A
Step3.
Enter the valid user name and password.
Step4.
Add Site:
Right click on “Max-NG Network” on the left hand side treePopup window will open i.e.
“Site Registration Form”
176 C-DOT MAX-NG

SITE AND EXCHANGE MANAGEMENT
Enter “Site Name” and “Site Description”Click “Registration

The site will be registered and will be shown in the left hand Tree under Max-NG Network
maps.

Annexure - A
Output:
178 C-DOT MAX-NG

Add Exchange:
Right click on the registered “Site” on left hand tree
 Click “Add Exchange”

Annexure - A
Following screen will be displayed.
Enter “Exchange Name” and “Exchange Description’’Click “ADD”.
180 C-DOT MAX-NG

Site will be registered and will be shown in the left hand Tree under Site Node.
Add Node:
Right click the “Exchange”, the menu for node management and Delete Exchange will
appear. The node management operations can be as follows:
Add Node
Manage Node
Delete Exchange

Annexure - A
Select “ADD Node”
182 C-DOT MAX-NG

Following add node form will be displayed.
Enter “Number of nodesClick “Ok”

Enter the “ IP Address” of each nodeSelect “Node Type”Click “To Discover check
box” Click “ADD”

Annexure - A
Output:
User Management:
There are four types of users in C-DOT IEMS :
i) Super User i.e. root
ii) Site Administrator
iii) Exchange Administrator
iv) Exchange Operator
A site can have at most 1 administrator but administrator can administer more than one
site.
The Exchange Users are of two types –
i) Exchange Administrator
ii) Exchange Operator
A site administrator can create and delete exchange administrator. Exchange
administrator can create or delete exchange operator. Root user only can add or delete a
site administrator.
184 C-DOT MAX-NG

The user management can be done by invoking the Site Management menu from Tools
menu of the client frame. The site user can be created by clicking the Create Site User
button and exchange users can also be created by clicking the Create Exchange User
button. To remove the user the Remove User button is clicked.
For example suppose there is Site-1. Under this site-1 there may be multiple LAGs. Say
NUH is the name of a site & Nuh-main, Ujina & Para are names of LAGs under site NUH.
Thus it is now possible to allow some operator to access multiple LAGs of a same site or
restrict its operation to a single LAG.

Annexure - C
Trouble Shooting
1. No dial tone in subscriber
Check whether Voltage (-48v) is present in the line
Check whether the line is in service or not using GUI.
Verify TIC of the corresponding subscriber is in service or not
Ensure that DSP IP is getting pinged from LAG.
(If DSP is not getting pinged, check the LAN connectivity.)
Check lag –v process is running or not. LAG to work properly ,this process should be
running.
Sh-2.05b#./ ps -ef|grep lag –v
If lag –v process is found ,it means lag is working fine.
If lag –v process is not found, restart the lag.
Sh-2.05b#./cd /etc
Sh-2.05b#././lag_shutdown.sh 1 (option 1 for simplex NGTJ and 2 for duplex)
Sh-2.05b#./lag_restart.sh
2. Dial Tone is there on subscribers BUT INTER LAG and other network calls are failing.
Here Intra LAG calls are running.
Telnet LAG IP
Enter login & password
Type
$ chroot mmc
$ cd /tmp
Now view the file lag_init.log (tail –f lag_init.log). If it shows level 4 up, It means LAG is
up & but connectivity with Soft Switch is down.
For inter LAG and other network call level 5 should be up.
Ping Soft Switch from LAG.
If Soft switch is not getting ping from NGTJ card, then check the LAN connectivity

Chapter 1.
PROCEDURE FOR BACKUP IN LAG CARD AT ACCESS SITE

For data backup of LAG
 In LAGEMS select the LAG node and right click.
 Click Backup.
 Message will come that backup is successful.
 To access backup file, following is the procedure
# ssh root@10.187.212.38
( Enter password of LAG)
# chroot /mmc
# cd /DB_BKP
At this location, CdotLagDBConf.back file will be created.
Note: LAG node should be discovered in LAGEMS & this is one time job after installation of
MAX-NG core and access network. Backup file i.e. CdotLagDBConf.back file will be created in
/DB_BKP path. If you still want to take backup on daily basis, you can follow this procedure also.
Otherwise, automated script runs on daily basis which takes backup of each site in Core server.
PROCEDURE FOR BACKUP IN NGTJ CARD & MLS AT ACCESS SITE
6 C-DOT MAX-NG
TROUBLE SHOOTING
 For MLS, open MLS GUI in Firefox browser in Thin Client/Laptop/PC by entering IP
only.
Example: 10.187.212.2/
 Login with Username admin and password is not required.
 On the left pane select Maintenance, Configuration and then Download option. Select
running-config and download configuration. Configuration will be downloaded in
Downloads folder and browse same file and save in Laptop/Thin Client PC.
Procedure for Backup in SG/MG card in NGTJ card of CACU chassis

Chapter 1.
1. For Backup in TMG card, first discover CACU chassis in NGEMS.

2. Open Chassis view and select NGTJ card which is configured in SG/MG card.
3. Then right click NGTJ card and select Gateway EMS then TMG EMS.
4. Select Backup option. Enter Username and Password as root and root which is by default.
5. Then Click Submit.
6. Then success message will be displayed and then select OK.
7. Now backup of SG/MG card is taken successfully for TMG application.
8. In /mmc/opt/tmg/etc location, cdot_tmg.cfg is created which is the backup file of tmg.
Details of files backup to be taken (for SG, PRI and TMG modules) along with their path are
mentioned below:
a) SGL2
Path : /mmc/sgstk
Filename : cdot_sgl2.conf
b) PRIAG
Path : /mmc/etc/priag
Filename : /mmc/etc/priag
Filename:
Extensions.conf
Priag.conf
Sip.conf
c) TMG
Path : /mmc/opt/tmg/etc
Filename : cdot_tmg.cfg
8 C-DOT MAX-NG
TROUBLE SHOOTING
C-DOT NGN
Operation and Maintenance (OAM)
© 2015, C-DOT
Printed in India
Section No.
System Draft 01, October 2016
Practices
Chapter 1.
10 C-DOT MAX-NG
TROUBLE SHOOTING
INDEX
Chapter 1 : Introduction ……………………………………………………8

Chapter 2 : MAX-NG Network Overview ………………………………..10
Chapter 3 : Operation & Maintenance ……………………………………..13
Chapter 4 : Device Specific Tasks …………………………………………..20
Annexure-I : Problems& Solutions ……………………………………………..23
Appendix ………………………………………………………………………………..27
Chapter 1.
Chapter 13.
Introduction
13.1. PURPOSE AND SCOPE OF THE DOCUMENT
This document provides the description of C-DOT NGN network elements and operation &
maintenance activities that have to be performed by BSNL officials (at exchanges). Details
about MAX-NG network would be there in subsequent chapters.
13.2. INTRODUCTION TO 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.
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
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.
12 C-DOT MAX-NG
INTRODUCTION
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.
13.3. SCOPE
The intended readers of the document includes M/s. BSNL. This document gives MAX-NG
Network Overview, brief overview of nodes and activities to be performed on day to day
basis.
13.4. DEFINITIONS, ACRONYMS AND TERMINOLOGY
13.4.1. Definitions
Network Management System (NMS): A NMS is a system used to monitor and
administer a network.
13.5. ORGANISATION OF THE DOCUMENT
This document is organized in to 4 chapters and the details are given chapter wise.
Chapter 1 : Introduction
Chapter 2 : MAX-NG Network Overview
Chapter 3 : Operation & Maintenance
Chapter 4 : Device Specific Tasks
Annexure-I : Problems& Solutions
Appendix
Chapter 14.
MAX-NG Network Overview

2.1 SYSTEM OVERVIEW
In MAX-NG Project current MAX exchanges are upgraded to MAX-NG System in which
switching is based on software and control of call is moved to centralized node. Switching and
Control of call, the core functionality of telecommunication system, is moved to the centralized
node, Soft Switch, which works in IP domain. The line access of MAX-NG system to the
subscribers is provided by various gateways e.g. Line Access Gateway (LAG), V5 Access
Gateway (V5AG), ISDN Gateway (PRIAG), which inters works between TDM domain and IP
domain. The digital trunk and SS7 signaling functionality are provided by Trunk Media
Gateway (MG) and Signaling Gateway (SG) respectively. All the Gateways are connected to
Soft Switch through backbone IP network.
2.2 SYSTEM ARCHITECTURE

MAX-NG Network consists of 4 cores working in Primary (PR) and Geographical Redundancy (GR)
configuration as follows:-
14 C-DOT MAX-NG
Under normal operating conditions, each Site (PR or GR) independently services a group of
Telecom Circles as illustrated in Table 1.
Table 3: Circles served by each Core Network Site
S. No. North Zone East Zone South Zone West Zone

Each
Hyderabad
Chandigar
Bangalore Core
Gurgaon
Kolkata
Cuttack
Bhopal
site
Pune
consist
h
s of 4
1. Haryana Andaman & Andhra Pradesh Gujarat HP
Nicobar Blade
server
2. Himachal Pradesh Assam Karnataka Chhattisgarh chassis
3. Jammu & Kashmir Bihar Kerala Madhya Pradesh with
48
4. Punjab Jharkhand Tamil Nadu Maharashtra server
and s.
Chennai TD
5. Rajasthan North East 1
6. Uttaranchal North East 2
7. Uttar Pradesh (East) Orissa
8. Uttar Pradesh West Bengal

(West) and
Kolkata
2.3 NETWORK ELEMENTS
In MAX-NG Network following network nodes are present:-
 CORE Nodes
o C5 (Class 5 Soft switch)

o C4 (Class 4 Soft switch)
o SBC (Session Border Controller)
o IN-SSP (Intelligent Network Service Switching Point)
o RE (Rating Engine)
o SGP (Signalling Gateway Processor)
o NGEMS (Next Generation Element Management System)
o LAGEMS (LAG Element Management System)
o SPS (Service Provisioning Server)
o LIS (Lawful Interception System)
o AMM / On-board Administrator Module
o Aggregator (Layer 3 Switch)
 ACCESS Nodes
o CACU Nodes (Centralized Access Control Unit)

 SLM (Shelf Manager)
 Gateway Cards (for SG/TMG/V5AG/PRIAG applications)
 Aggregator (Layer 3 Switch)
 EBM Cards (Ethernet to E1 Bridge Main)
o LAGU Nodes (Line Access Gateway Unit)
16 C-DOT MAX-NG
Chapter 15.
Operation & Maintenance

3.1 GENERAL OVERVIEW
Each of 4 zones have respective Zonal EMS application that can be accessed by operators at access &
core sites for daily monitoring & subscription management purposes. This zonal EMS can be accessed
using Thin Client PC which is provided at every SDCA & at core sites.
The figure shown below explains that hierarchical flow diagram in which Super user can
create different Administrators at different sites with different groups (languages) assigned to
each. Super also assigns area codes & exchange codes to respective Administrators. Admin can
create different zones & number of Operators under it. Operators use area codes & exchanges
codes to create subscribers.
SUPER
Site1 Site2 Site3

Group Group Group
1 2 2
Admin - 1 Admin - 2 Admin - 3
Zone 1 Zone 2 Zone 3
OP – 1 OP – 2 OP – 1 OP – 2 OP – 1 OP – 2
Sub1 SubN Sub1 SubN Sub1 SubN Sub1 SubN Sub1 SubN Sub1 SubN
Fig. 1: Hierarchical flow diagram
3.2 CORE SITE
The operator at core site can open the MAX-NG zonal EMS from C-DOT Thin Client PC by entering
following URL in firefox browser:-http://[DomainName]:8082/NGEMS/maxng.html.
In the above following links would be seen:-
 NEXT GENERATION INTEGRATED EMS
 SUBSCRIPTION MANAGEMENT
 MANAGE LINE ACCESS GATEWAYS
18 C-DOT MAX-NG
 RATING ENGINE CONFIGURATION/REPORT
 MAP AND USER ADMIN
DAILY TASKS
 Monitoring of alarms in the Insight Display Monitor mounted on each of the four chassis, and
performing respective action as instructed in the monitor.
 Viewing real time alarms & network events based on site type (core/access) & operator type
(admin/view), using Zonal EMS link (as instructed above) by entering C-DOT given credentials.
Table 2: Device specific alarms in NGEMS
S Core module Alarm list

.No
1. Chassis/AMM/ Power alarm
On-board
Administrator
Module
Fan alarm
Temperature alarms
Ethernet port alarm
Card down alarm
2. SBC SBC Application Down/Up

status
SBC Application Act/ Backup
status change
Disk full status ( <50 %, < 75% ,
< 90%, > 90%)
3. C5 C5 Application Down/Up status

C5 Application Active/ Backup
status
Subscriber DB DOWN/UP
status change
DB Replication DOWN/UP
status change
< 90%, > 90%)
4. C4 Trunking Server
Application
Down/Up status
Trunking Server
Application
active/standby
status change
MG unavailable
5. RE Standby Copy Reboot
< 90%, > 90%)
DB down on Active/ Standby
copy
RE process down
6. SSP Trunking Server

Application
Down/Up status
Trunking Server
Application
active/standby
status change
7. SG Link Up
Link Down
Card up
Card down
Stack manager down
Stack manager up
8. NGEMS NGEMS
Application
Active/ Backup
status
Disk full status (
<50 %, < 75% , <
90%, > 90%)
9. IEMS IEMS Application
Active/ Backup
status
Disk full status (
20 C-DOT MAX-NG
<50 %, < 75% , <
90%, > 90%)
10. SP Disk full status (
<50 %, < 75% , <
90%, > 90%)
11. LIS Server UP/DOWN
 Scheduling Backup of every core node (including router) using NGEMS. Copy of the backups to be
kept on thin client (of last 15 days).
DEVICE SPECIFIC TASKS

S. No Core Commands Action
module
1. SBC Configure Routes All these operations can
be performed using SBC
Configure Routing policy
EMS by accessing SBC
Routing table commands core node from the
Routing action commands respective chassis node of
the core site.
Initial table commands
2. C5 Create/ Delete/ List Subscribers
All these commands can
Centrex management related be executed by using
subscription management
commands
GUI link present in Zonal
Hunt group management related EMS web page. C-DOT
commands given credentials have to
be used to login on
subscription management
webpage.
3. C4 Configuration Commands All these operations can
be performed using C4
Number Analysis Commands
EMS by accessing C4 core
M3UA Commands node from the respective
Media Gateway configuration chassis node of the core
site.
ISUP Configuration
SIP Route Configuration
Routing case Configuration
CIDP Configuration
AIRP Configuration
Testing Number Analysis
Commands
Call related Commands
Remote signalling Point
Commands
4. RE Area Management Commands All these commands can
be executed by using
Charge Band Management
Rating Engine
Associate charge band Configuration/Report
Service charge band management GUI link present in Zonal
EMS web page. C-DOT
Subscriber management given credentials have to
Bill Plan Management be used to login on Rating
Engine GUI.
Plan Charging Info Management
Operator management
LRN Data management
Hunt group/ PRI management
IN Code Data management
Thresholds Data management
Day type and Tariff Data
management
Revenue Report
NCBR report
CDR report
5. SSP Configuration Commands All these operations can
be performed using INSSP
M3UA
EMS by accessing INSSP
SCCP core node from the
INAP respective chassis node of
the core site.
Media Server
ISUP Configuration
SIP Route Configuration
Routing case Configuration
CIDP Configuration
AIRP Configuration
CS2 Configuration
6. SG Chassis and MTP1 configuration All these operations can
be performed using SG
Equip port
EMS by accessing SG core
Equip Line card node from the respective
22 C-DOT MAX-NG
Modify Card admin status chassis node of the core
site.
Display Card Details
Display All ports
Check SG
SG Release
Display All System Parameters
Delete stack
Swap Card
Status commands
Miscellaneous commands
3.3 ACCESS SITE

Role of operators at access site is mainly subscription management. Apart from this it also includes
monitoring of the CACU nodes & the LAGU nodes coming under that SSA.
DAILY TASKS
 Checking connectivity of CACU and LAGU sites to MAX-NG Core Network.
 Creation and deletion of subscriber in Line Access Gateway through C5 GUI. All operations can be
performed through C5 GUI by logging through SDCA specific Username and Password given by C-
DOT.
 Checking status of working LAG card, TIC cards, PSU, Line cards in Exchange. Normal status is
inservice active, inservice standby. LAG card should be in Level 5 if LAGU and CACU is connected
to Core Network.
 Modification of TEN of subscriber. Status of subscriber is mnt-busy if subscriber is not created at

TEN otherwise idle or busy depending on on-hook or off-hook condition.
 Checking and maintenance of E1/PCM connectivity if exchange is not in Level 5.Trans and Receive
can be checked with the help of LED. Trans will be connected to Receive or Receive is connected to
Trans.Media can be checked with help of ADM Equipment.
 Scheduling Backup of Line Access Gateways (both remote & co-located) using LAGEMS. Copy of
the backups to be kept on thin client (of last 15 days).
 Scheduling Backup of CACU cards using CACU node discovered (of specific SDCA/MBM site) in
NGEMS. Copy of the Backups to be kept on thin client (of last 15 days).
24 C-DOT MAX-NG
Chapter 16.
Device Specific Task
S. No Access Commands Action

module
1. MLS Access through GUI All these operations can
be performed through
Ping Core Network
MLS GUI.
Configuration of Specific Routes
for WAN interfaces like
IPTAX,CDR WAN,CDOT
WAN,etc
2. MLS To ping IP of specific WAN All these operations can
network be performed through
MLS GUI.
3. MLS To check the configuration of PE All these operations can
routers if MLS is pinging CDOT’s be performed through
end PE router. Further routing MLS GUI provided WAN
has to checked. IP should be known to us.
4. SLM SLM card should come UP.Ping All these operation can be
IP address of SLM IP and check performed through
processes through CLI interface. NGEMS GUI.Alarms can
Further this can also be checked be seen in the Alarm
through NGEMS GUI. Panel. Card can also be
accessed through minicom
cable.
5. SG/MG NGTJ card should come UP.Ping All these operations can
IP address of SG/MG. Check also be checked through
processes through CLI interface. NGEMS GUI.
6. SG/MG Corruption of SG/MG data while Recreate and reconfigure
card is UP. data in SG/MG card.
7. SG/MG To check E1/PCM connectivity of LEDs of SG/MG card
POIs with the network. turns green if PCM is
connected otherwise
Red.Trans and Receive of
SG/MG card and POI’s
end can be checked with
the help of LED. On
connecting with trans,
LED turns Red otherwise
not.
8 SG/MG To check E1/PCM at DDF end. E1/PCM can also be
checked at DDF end. i.e of
POI’s End and NGTJ
card’s end. Connection in
TAG block can also be
checked.
9 FAN To check working of FAN in FAN This can be checked
TRAY tray. through NGEMS GUI. If
FANs are running
properly then it should be
green otherwise Red.If not
running then connections
in CACU chassis can also
be checked.
10 EBM To check whether E1 connectivity This can be checked
to LAGU site is OK or not. through LEDs on the
front face plate of EBM
card.If E1 is connected
and UP, LED turns green
otherwise not. Further E1
can be checked at
Exchange’s DDF end also.
11 Thin To check whether Thin Client is This can be checked by
Client working or not. opening terminal and type
ifconfig command to
check IP address assigned
to Thin Client on the same
IP segment. For this, IP
address list is referred.
12 V5/PRI To check processes once card This can be checked by
comes UP. command i.e. ps –ef in
card and mmc itself. List
of processes can be
checked through
installation manual if card
is not running properly.
13 V5/PRI To check E1/PCM connectivity to This can be checked by
AN-RAX and PRI sites. glowing of LED which
turns green on
connectivity with AN-
26 C-DOT MAX-NG
RAX and PRI sites.
ANNEXURE-I: PROBLEMS & SOLUTIONS
Problem 1:
Intra-LAG calls are not connecting.
Solution:
i) Check the status of card whether card is in Level 4 or Level 5.
ii) Check the status of tic cards and line cards. This may happen that particular tic card of
particular frame went out of service. If so, make tic card in service.
iii) Check whether mmc is corrupted or not.
iv) If mmc is corrupted or not mounted/mounting, replace corrupted mmc by prepared mmc.
v) If any other problem related to dial tone or call not connecting, give hard reboot to NGTJ card
and check connectivity to core network. Card should come in Level4 or Level 5 depending
on the connectivity.
vi) Check DSP IP and ping active DSP IP. DSP IP must be reachable.
vii) If still problem persists, give hard reboot to NGTJ card of which procedure is given in
Annexure.
viii) Change NGTJ card by new card and check dialtone.
ix) Check type of NGTJ card which should be AE3 at Access sites and as per the BOM. With
Serial Number also on card, Type of card is mentioned.
Problem 2:
Inter-LAG calls not connecting.
Solution:
i) First check intra-LAG calls.
ii) If intra-LAG calls are working, check Level and connectivity of access network to core
network.
iii) Follow solution of Problem 1 if intra-LAG calls are not connecting.
iv) Check connectivity to core network such as C5, SBC and C4 from access network for example
Thin Client PC.
28 C-DOT MAX-NG
Command to check connectivity:
# ping <IP Address of C5 Softswitch>
# ping <IP Address of SBC>
# ping < IP Address of C4>
Softswitch IP of corresponding core site may be 10.187.0.15 for Gurugram Core Site, 10.187.1.15 for
Chandigarh Core Site, etc.SBC IP of corresponding core site may be 10.187.0.12 for Gurugram Site,
10.187.1.12 for Chandigarh Site.
If core site is not connecting, for reachability of core site traceroute command is used.
#traceroute <IP Address of core node>
#traceroute <IP Address of Class 5 Softswitch>
Note: IP Address of C5 Softswitch may be 10.187.0.12 for SBC, 10.187.0.15 for C5 Softswitch
for Gurugram Core Site.
v) Check the type of SFP connectors which may be SC, LC, and FC of
wavelength 1310nm, 1550nm. Make and wavelength at both sides MLS
side and Transmission end should be same.
Problem 3:
Speech is not continuous.
Solution
i) Check the status of DSP.Ping Active DSP IP of the particular card.Entry is in lag_sys.conf file.
ii) If DSP is not pinging or pinging with packet loss, give soft reboot to NGTJ card.
iii) If problem is not solved, there may be problem in DSP of NGTJ card.
iv) Replace faulty NGTJ card by working NGTJ card.
Problem 4:
Subscribers are not having dial tone in particular frame.
Solution
i) Check status of tic card.TIC card may be in out of service state. Make tic card in service.
ii) Check PSU, TIC, SPC, TUI and LCC cards of particular frame.
iii) TIC, SPC, TUI and LCC card may be faulty. Replace faulty cards by working cards.
iv) Check status of particular subscriber.
APPENDIX:
For logging into NGTJ card;
Login to NGTJ card with root account from the Linux-PC:
# ssh root@<NGTJ-CARD-IP>
After successful login to installed and configured NGTJ LAG card, do following to check the status of
the LAG applications coming up on the card :
# chroot /mmc
# tail -f /tmp/lag_init.log
For CLI,
telnet <IP of NGTJ card> 3333 (3333 is the port code)
Username is root and Password is public
For status of TIC cards;
$ displ unit_sts all
For status of subscribers and Line cards;
$ displ card_sts rack= frame= slot= (Rack=1,2; Frame=1,2,3,4 slot= 3-10 & 17-24)
(IDLE,BUSY & mnt-busy can be seen) ;
mnt-busy means subscriber is not created at TEN
TEN = Rack-Frame-slot-ckt (ONLY for status in CLI)
For checking DSP;

Login into NGTJ card
$ chroot /mmc
$ ping <Active DSP IP> (Active DSP IP is always in lag_sys.conf; cat /etc/lag_sys.conf)
To check whether mmc is mounted or not;
$ df –h ( will show mounted devices)
$ /dev/mmcblk0 or /mmc can be checked
For Mounting jffs2 and checking net file;
30 C-DOT MAX-NG
$ mount /dev/mtdblock0 /jffs2
$ cat /jffs2/conf/net
For giving Soft Reboot to NGTJ card;

$ chroot /mmc
$ cd /etc
$ ./lag_shutdown.sh 1 or 2 (1 for SIMPLEX and 2 for DUPLEX)
$ ./lag_restart.sh (for starting processes)
Processes will be started and card will come up.
For giving Hard Reboot to NGTJ card;

$ cd /jjfs2/conf
$ ./lag_pre_reboot.sh 1 or 2 (1 for SIMPLEX and 2 for DUPLEX)
$ reboot
Card will be hard rebooted.
Sample Net file

/sbin/ifconfig eth0 down
/sbin/ifconfig eth0 10.187.9.103 netmask
255.255.255.128 broadcast 10.187.9.127
/sbin/route add default gw 10.187.9.2
/sbin/ifconfig eth0 10.187.9.103 up
pkill display_e1_led
#/cdot/bin/mount_nand
#mount -t ext3 -o noatime,data=writeback,commit=200
/dev/mtdblock2 /mmc
mount -t ext3 -o noatime,data=writeback,commit=200
/dev/mmcblk0 /mmc
sleep 10
/cdot/bin/set_ngtj_mode 1
/mmc/etc/INT_BE/EXE/SWINST-BE-DMON LAG &
sleep 2
/mmc/etc/SWINST/EXE/swbe_lag.exe &
echo "starting lag_init.sh..."
chroot /mmc /etc/lag_init.sh
sleep 5
/mmc/usr/bin/lagbkrs_start &
#making linuxagent as daemon process
/mmc/usr/local/bin/lag/AGENT/linuxagent/daemon_run
Sample lag_sys.conf file
32 C-DOT MAX-NG
Procedure to check whether mmc is mounted or not
 Give “df” command to check the mounted filesystem

[root@NGTK root]# df -h
Filesystem 1k-blocks Used Available Use% Mounted on
rootfs 187406 64431 113565 36% /
/dev/root 187406 64431 113565 36% /
devtmpfs 507504 0 507504 0% /dev
rwfs 512 0 512 0% /mnt/rwfs
/dev/mmcblk0 1032088 34088 945572 3% /mmc
Following is the screenshot attached.
Note: /dev/mmcblk0 is used since external mmc is mounted.
34 C-DOT MAX-NG
Checking level of NGTJ card
36 C-DOT MAX-NG

Max-Ng Access Migration Doc-Old

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Max-Ng Access Migration Doc-Old

Caricato da

Copyright:

Formati disponibili

C-DOT MAX-NG

MAX TO MAX-NG MIGRATION MANUAL

SERIES 100: PLANNING

CSP SECTION NO. 431-101-1061

C-DOT MAX-NG IN THE REST OF THIS PUBLICATION).

ANY FEEDBACK ON THE DOCUMENT MAY BE SENT AT MXNGPMTC@CDOT.IN.

© 2017 BY C–DOT, NEW DELHI

H:\HOME\NG-MAX\User\FinalCDOT-MAXNG-MIGRATION-MAN-V02.doc May 29. 2017

BRIEF OVERVIEW AND MIGRATION PLAN

MAX-TO MAX-NG MIGRATION MANUAL 5

1.3. NGN ACCESS NETWORK

MAX-TO MAX-NG MIGRATION MANUAL 7

Ethernet connectivity at RSU sites to CACU Chassis is preferred over E1

command. Check number of subscribers by #displ line_counters in CLI of NGTJ card.

For V5/PRI subscribers, numbers of subscribers will be checked by FE.

i) Before starting MAX-NG Migration, a PC with Internet connection is required. Connect

ii) For understanding MAX-NG Network architecture, please follow P94-PI-ARC-MXNG-

MAX-TO MAX-NG MIGRATION MANUAL 9

v) Multiprotocol Label Switching (MPLS) is a type of data-carrying technique for high-

viii) Order of documents to be read is as follows:

MAX-TO MAX-NG MIGRATION MANUAL 11

1.6 FLOW of activities during MAX-NG Migration

MAX-TO MAX-NG MIGRATION MANUAL 13

Pre-Requisites & Data Creation in Class 5

Note: ITPC need to be informed at-least 2 working days in advance

MAX-TO MAX-NG MIGRATION MANUAL 17

AREA CODE GROUP CREATION

MAX-TO MAX-NG MIGRATION MANUAL 19

ROUTE DEVICE CREATION

MAX-TO MAX-NG MIGRATION MANUAL 21

MAX-TO MAX-NG MIGRATION MANUAL 23

MAX-TO MAX-NG MIGRATION MANUAL 25

LAG EXCHANGE MAP

MAX-TO MAX-NG MIGRATION MANUAL 27

STEPS AND PHYSICAL

MAX-TO MAX-NG MIGRATION MANUAL 29

xiv) Before starting MAX-NG Migration, a PC with Internet connection is required.

xv) For understanding MAX-NG Network architecture, please follow P94-PI-ARC-MXNG-v04

efficient network communication mechanism used to transmit Internet Protocol

xiii) Switches create a network. Routers connect networks. A router links

xxiii) Order of documents to be read is as follows:

MAX-TO MAX-NG MIGRATION MANUAL 31

3.2.1. IP Address requirement for access Equipment:

MAX-TO MAX-NG MIGRATION MANUAL 33

-MAX-NG (Give Any Name to The connection)

64 bytes from 192.168.103.75: icmp_seq=0 ttl=64 time=5.080 ms

MAX-TO MAX-NG MIGRATION MANUAL 35

3.5. PREPARATION OF NGTJ CARDS (LAG) FOR DIFFERENT BM’S/RSU

MAX-TO MAX-NG MIGRATION MANUAL 37

Physical Installation of LAGU System

MAX-TO MAX-NG MIGRATION MANUAL 39

A/T and commissioning of MAX Site 4 DAYS

Total No. of DAYS for Migration of one MAX exchange 15 DAYS

MAX-TO MAX-NG MIGRATION MANUAL 41

IP Address Configuration IN MLS Card

For VLAN configuration in MLS card, please refer next Chapter.

MAX-TO MAX-NG MIGRATION MANUAL 42

C-DOT MAX-NG Network Connectivity &

Access Site Connectivity ...................................................................................3

MAX-NG Access SW Inst & Config Page 43

C-DOT MAX-NG NETWORK

1.1 PURPOSE AND SCOPE OF THE

ACCESS SITE CONNECTIVITY