Cableado Estructurado

NICARAGUA NATIONAL POLICE
MPT System Upgrade and Expansion

IP and Backbone Linking Specifications
Requirements
Tait Project Number:

Document Version: Version 1.2
Date: 27-Mar-2018
CONTACT INFORMATION
Tait Communications Corporate Head Office

Tait Limited
P.O. Box 1645
Christchurch
New Zealand
Tait Communications Regional Office

Tait Americas
15342 Park Row Blvd,
Houston, Texas
United States of America
For addresses and telephone numbers of regional offices, refer to http://www.taitradio.com.
COPYRIGHT AND TRADEMARKS

All information contained in this document is the property of Tait Limited. All rights reserved.
This Document may not, in whole or in part, be copied, photocopied, reproduced, translated, stored, or reduced
to any electronic medium or machine-readable form, without prior written permission from Tait Limited.
The word Tait and the Tait logo are trademarks of Tait Limited.
All trade names referenced are the service mark, trademark or registered trademark of the respective
manufacturers.
Page 2 of 27 Nicaragua National Police MPT System Upgrade and Expansion  System Requirements Specification  Version 1.1
CONTENTS
PREFACE ............................................................................................................................................................. 5
Project details ........................................................................................................................................... 5
Scope ....................................................................................................................................................... 5
Document Status ...................................................................................................................................... 5
Publication Record ................................................................................................................................... 5
Associated Documents ............................................................................................................................ 6
Document Control .................................................................................................................................... 6
Terms and Abbreviations ......................................................................................................................... 6
1. INTRODUCTION ........................................................................................................................................ 8
2. RADIO SYSTEM OVERVIEW.................................................................................................................... 9

2.1 Background .................................................................................................................................... 9
3. IP LINKING REQUIREMENTS ................................................................................................................ 10

3.1 Network Performance .................................................................................................................. 10
3.2 Site Bandwidth Requirements ..................................................................................................... 11
3.3 Network Time Protocol (NTP) ...................................................................................................... 12
3.4 Quality of Service (QOS) ............................................................................................................. 12
3.5 IP Protocols and Ports ................................................................................................................. 13
3.6 Multicast ....................................................................................................................................... 15
3.7 Backhaul Validation Approach ..................................................................................................... 15
3.8 Site Equipment IP Addresses ...................................................................................................... 15
4. SECURITY REQUIREMENTS ................................................................................................................. 16

4.1 Access Control ............................................................................................................................. 16
4.2 Network Segmentation ................................................................................................................ 16
4.2.1 Recommended Perimeter Security ....................................................................................................... 16
5. PROJECT ENGINEERING DOCUMENTATION ACCEPTANCE ACKNOWLEDGEMENT.................... 17
APPENDIX A – IP ADDRESSING PLAN ........................................................................................................... 18

Infrastructure Equipment IP addressing ................................................................................................. 18
RF Site Equipment IP Addressing ......................................................................................................... 18
Site 1 18
Site 2 19
Site 3 20
Site 4 20
Site 5 21
Site 6 21
Site 7 22
Site 8 22
Site 9 23
Nicaragua National Police MPT System Upgrade and Expansion  System Requirements Specification  Version 1.1  Page 3 of 27
Site 10 ..................................................................................................................................................... 23
Site 11 ..................................................................................................................................................... 23
Site 12 ..................................................................................................................................................... 24
Site 13 ..................................................................................................................................................... 24
Site 14 ..................................................................................................................................................... 24
Site 15 ..................................................................................................................................................... 25
Site 16 ..................................................................................................................................................... 25
Site 17 ..................................................................................................................................................... 25
Site 18 ..................................................................................................................................................... 26
Site 19 ..................................................................................................................................................... 26
Site 20 ..................................................................................................................................................... 26
Site 21 ..................................................................................................................................................... 27
PREFACE
Project details
Project Reference TEMA 60-10000A
SYSCOM NICARAGUA – NICARAGUA NATIONAL POLICE

Customer
PROJECT
Project description MPT System Upgrade and Expansion
Technical Authority Blad Guzman
Project Manager Fabian Castiblanco
Global Program Manager Wellington Carvalho
Deployment Engineer Fabian Castiblanco
Scope
This document is intended to clarify the IP network and backbone requirements for the end-to-end transport of
voice, control and other radio data services across the Nicaragua National Police radio network.
This is done to ensure that the contractor (Syscom Nicaragua), the equipment supplier (Tait Radio
Communications) have the same understanding and have reached agreement on the backbone and IP network
specifications requirements for the National Police of Nicaragua’s radio system upgrade and expansion project.
The signature of the responsible parties indicates understanding and acceptance of the proposed IP networking
equipment. Likewise, the signature of the supplier indicates understanding and acceptance to provide the IP
network equipment as proposed in this document.
Any changes required after the signature of this document will require a revision and changes can affect price
and delivery. The full impact of any changes will be described in revised versions of this document.
Document Status
Author Blad Guzman
Issue Version 1.1
Status Final for Customer Review
Date 2 April 2018
Publication Record
Issue Date Signature Comment
1.0 Mar 10, 2018 BG Final for customer review
1.01 Mar 14, 2018 BG Small correction to bandwidth calculations pages 11-12
1.02 Mar 27,2018 FC IP addressing suggest by Nicaragua Police
Associated Documents
Reference documentation includes:
Document Control
Issue 1.0 indicates review and acceptance by all parties. Issue 2.0, 3.0, and later indicates revision and
acceptance due to a change order. Minor edits which do not affect scope or cost are captured as 1.1, 1.2 and
so forth.
Terms and Abbreviations
Abbreviation / Term Description

Bandwidth Maximum available bit-rate required to transfer the designated protocol
using Ethernet framing.
Control plane traffic – call signalling, trunked registration, mode

C-Traffic
changes.
DMR Digital Mobile Radio, a standards based two-way radio technology
DSCP Differentiated Services Code Point
IP Internet Protocol
Variation in latency. See ITU-Y Y.1541 and RFC3393. Measured at the

Jitter 99.9 percentile, which means that less than 1 in 1000 packets will
exceed the specified jitter.
LAN Local area network
LMR Land Mobile Radio
Arithmetic mean delay for voice-service sized packets (approx. 200

bytes) measured in one direction between the designated endpoint
devices via the designated routing element (e.g. Network Element to
Latency
Node Controller for DMR trunked systems, Base station to Base station
via Central Voter for P25 Conventional systems). See RFC 2681 and
RFC 2679 for further detail.
Management plane traffic – Monitoring, configuration. The aggregation

M-Traffic
of SNMP, HTTPS, Syslog, firmware downloads, backup/restore etc.
NTP Network time protocol
Type P one-way packet loss as defined in RFC 2680, where the

Packet Loss protocol is UDP. Packet rate is 50 packets/second and the duration of
measurement is one minute.
Abbreviation / Term Description
PG&E Pacific Gas and Electric
QoS Quality of Service
RF Radio Frequency
SNMP Simple Network Management Protocol
User plane traffic – voice or packet data from subscriber equipment or

U-Traffic destined to subscriber equipment (e.g. portable, mobile, dispatcher,
PSTN, data terminal)
WAN Wide area network
Referenced Documents
Document ID Title
ITU-T. Y1564 ITU-T. Y1564 (Ethernet service activation test methodology),
International Telecommunications Union (ITU), http://www.itu.int/rec/T-
REC-Y.1564/en
MNB-00003-13 TN9300 DMR Tier 3 Trunked Network System Manual, January 2017
MNA-00026-09 TaitNet MPT-IP Radio Network System Manual
TN-2167a Technical Note TN-2167a, Network Linking Design, November 2015
1. INTRODUCTION
Tait will supply design and deploy services to Syscom Nicaragua in support to the National Police’s MPT radio
system upgrade and expansion project.
Based on the agreement between Syscom and the National Police, a Service Provider (Claro Networks) will
supply the required IP bandwidth and IP connectivity between the radios sites and the central node location.
The intention of this document is to provide SYSCOM NICARAGUA with the detailed requirements for the IP
links that will be supplied by service provider CLARO. CLARO will provision these IP links and will make the
links available at the time of system installation. CLARO will also perform all relevant testing and corrective
actions to ensure the link performance meets the requirement highlighted in this document.
The linking requirements for the TaitNet MPT-IP systems can be found in the following Tait documents:
• TaitNet MPT-IP Radio Network, System Manual (MNA-00026-09), section 2.9, Network Linking Design.
• Tait Technical Note TN-2167a - network Linking Design, dated 23 November 2015 (TN-2167a Network
Linking Design.pdf) that further explores IP network requirements beyond simple bandwidth requirements.
Note that the recommended minimum bandwidth per site for the MPT-IP Technology is the same for all the
radio sites (600kbps) at the channel counts determined for this project. An additional 100 kbps for other
monitoring and management traffic takes the total bandwidth requirement to 700kbps.
This is driven primarily by jitter considerations based on the difference in packet size between the packets
associated with radio traffic (C, U & M traffic is generally small packet based) and the large packets usually
associated with enterprise networks. Jitter performance is only guaranteed by correct application of the Tait
specified QoS configuration within the IP network supporting the radio system. More details and Tait QoS
recommendations can be read in the following sections. It is also important to note that, the required bandwidth
of 700kbps has to be provisioned from each of the individual site locations (MPT-IP Radio Sites) to each of the
Node controller locations within the system concurrently.
2. RADIO SYSTEM OVERVIEW
2.1 Background
The Nicaragua National Police currently operates a TaitNet T1541 (“MPT Classic”) MPT1327 trunked radio
network with 3 radio sites and a single node. This project consists of an upgrade from MPT Classic to a new
TaitNet MPT-IP system configuration. It furthermore includes the expansion of radio sites to a total count of 21.
The new TaitNet MPT-IP system provides a significant step towards IP-connected digital operations. This digital
infrastructure is based on a stable and proven communications technology requiring digital linking and IP
connectivity.
The following high-level diagram presents the new MPT-IP system and equipment that requires IP connectivity
between sites and central location.
Site 21 – 2 Channels
Site 7 – 4 Channels Site 17 – 2 Channels
TX Preselector
Tx Site 6 – 4 Channels Site 16 – 2 Channels
Combiner Rx Multicoupler Combiner
8x DUAL TB9300,
50W UHF Site 3 – 4 Channels Site 13 – 2 Channels
CH 13 CH 14 CH 15 CH 16 Site 2 – 4 Channels Site 12 – 2 Channels
CH 9 CH 10 CH 11 CH 12
TX Preselector
Combiner Rx Multicoupler
CH 5 CH 6 CH 7 CH 8
2x DUAL TB9300,
Preselector
50W UHF TX
Combiner Rx Multicoupler
CH 1 CH 2 CH 3 CH 4 CH 1 CH 2 CH 3 CH 4
CH 1 CH 2
1x DUAL TB9300,
50W UHF
CISCO WS-C3650-24 CISCO WS-C3650-24

SWITCH SWITCH CISCO WS-C3650-24
SWITCH
TCP/IP Linking Backbone (including firewalls)
MPT-IP Node Controller x1

(4xDIP + 1 SIP Interface)
TCP/IP Connections Equipment supplied by
(x2) LDT-1 LDT-2 LDT-3 LDT-4 Tait & SYSCOM
Equipment supplied
SIP Telephony (TCP/IP) IP Linking Supplier
x1
PBX TCP/IP Connections
(x4) Tait Network Gateways
SIP-Bases PBX (Interface to LDTs)
CISCO 4331 TCP/IP Connections (x4) x4Wire Connections

with 16-Port EtherSwit ch To LDTs
All system elements within an MPT-IP system are interconnected via an IP backhaul network. The IP
Network Service Provider will need to ensure that all the individual sites have layer 3 connectivity from each
site location to each of the node locations at the same time, making it less prone to single points of failure,
and for load sharing purposes.
3. IP LINKING REQUIREMENTS
This section describes the IP linking requirements for the end-to-end transport of voice, control and other radio
data services across the Nicaragua Police network. The backhaul network must meet or exceed performance
specifications in order to guarantee correct operation of the radio system also to ensure that there are no impacts
on voice delay and call setup times.
The radio network shall make use of private IP network addresses as defined by the Internet Engineering Task
Force (IETF) in RFC 1918.
Demarcation between Tait Supplied Equipment and Network provider is presented in below concept network
diagram
Site 1 Site 2 Site 3 Site 4 Site 5 Site 6 Site 7 Site 8 Site 9 Site 10 Site 11
LAN IP LAN IP LAN IP LAN IP LAN IP LAN IP LAN IP LAN IP LAN IP LAN IP LAN IP
subnet subnet subnet subnet subnet subnet subnet subnet subnet subnet subnet
172.18.1.0 172.18.1.128 172.18.2.0 172.18.2.128 172.18.3.0 172.18.3.128 172.18.4.0 172.18.4.128 172.18.5.0 172.18.5.128 172.18.6.0
/25 /25 /25 /25 /25 /25 /25 /25 /25 /25 /25
Cisco 3650 Switch Cisco 3650 Switch Cisco 3650 Switch Cisco 3650 Switch Cisco 3650 Switch Cisco 3650 Switch Cisco 3650 Switch Cisco 3650 Switch Cisco 3650 Switch Cisco 3650 Switch Cisco 3650 Switch
Demarcation Point
(Ethernet at Tait
Switch)
ISP Router ISP Router ISP Router ISP Router ISP Router ISP Router ISP Router ISP Router ISP Router ISP Router ISP Router
Backhaul Network
- Nicaragua Police/ Internet Service Provider (ISP) to provision connectivity between sites)
- Secure Routing between sites and central node to be provisioned by Nicaragua Police/ISP
- Routable IP address for LAN and WAN to be provided by Nicaragua Polic/ISP
- Default Gateway for all repeater sites to be provided by Nicaragua Police/ISP PROVISIONAL
- Network Performance Requirement for Voice between repeater sites and Central Node location
- Latency of < 40ms
- Jitter < 20ms
** Please note:- The Tait provided Cisco 3650 switches at the site will act as a Layer 2 device, with no routing
functionality implemented. All secure routing between sites and central node to be provisioned by the routers
Installed by Nicaragua Police/ISP
communications
ISP Router
Nicaragua Police
National
ISP Router ISP Router ISP Router ISP Router ISP Router ISP Router ISP Router ISP Router ISP Router ISP Router
2WR Replacement
Project
MPT IP Network
Overview
Date 03-12-2018
Cisco 3650 Switch Cisco 3650 Switch
Cisco 3650 Switch Cisco 3650 Switch Cisco 3650 Switch Cisco 3650 Cisco 3650 Switch Cisco 3650 Switch Cisco 3650 Switch Cisco 3650 Switch Cisco 3650 Switch
Cisco 4331 ISR Drawn MT
Router Checked MT
LAN IP LAN IP LAN IP LAN IP LAN IP LAN IP LAN IP LAN IP LAN IP LAN IP
Subnet Subnet Subnet Subnet Subnet Subnet Subnet Subnet Subnet Subnet FILE:\nicaragua national police
172.18.6.128 172.18.7.0 172.18.7.128 172.18.8.0 172.18.8.128 LAN IP Subnet 172.18.9.0 172.18.9.128 172.18.10.0 172.18.10.128 172.18.11.0 backhaul network v1.1.vsdx
/25 /25 /25 /25 /25 172.18.101.0/24 /25 /25 /25 /25 /25
Node Central Site
Equipment supplied
by Tait Limited
Site 12 Site 13 Site 14 Site 15 Site 16 All Site LAN IP address Site 17 Site 18 Site 19 Site 20 Site 21
ranges are tentative (To Equipment supplied
by Nicaragua Police
be provided by (Customer)
Nicarangua Police/ ISP)
3.1 Network Performance

The linking network shall provide a full duplex, 10/100 Mbps Ethernet port for each IP equipped device in the
radio network.
Tait recommends that the IP Network Provider implement the backhaul and IP network within the specifications
which is a latency of 10ms, but not more than 40ms, for the best performance between the base station and the
node controller. Refer to Page 4 of TN2167a document for further details.
The maximum jitter that can be accommodated by Tait equipment is 20 ms between the base station at radio
sites and the node controller. The backhaul network is required to meet this specification. Jitter data needs to be
provided to Tait at time of commissioning to ensure that the above requirement is met.
The network specifications are defined in the following table.
Parameter Value (ms)
Minimum bandwidth to carry C+U traffic 100 kb/s per channel for MPT-IP operation
Minimum bandwidth to carry M traffic 128 kb/s per site (1M recommended)
Out of order C and U traffic packets Less than 0.01%
Packet Loss Less than 0.01%
Latency (max) 100 ms
Latency (recommended) Less than 40 ms
Jitter (max) Less than 20 ms

Table 1: Latency and Jitter Requirements
Note: If the jitter requirements above cannot be met then the value of “Network Interfaces > Network >
Connection > Data Delay” in the TB9300 Base Stations should be adjusted accordingly.
3.2 Site Bandwidth Requirements

The following bandwidth requirements are approximate. Values are synchronous minimums assuming a star
network topology:
They have been calculated based on the number of devices at each site and their individual bandwidth values.
Backhaul links for the National Police MPT System must meet the minimum specified bandwidth including a
minimum 20% contingency factor. Also a bandwidth allowance of 1 Mbps is recommended for site maintenance
which facilitates remote configuration, firmware upgrades and real time monitoring.
Site Name Site Name Channel Count Required Bandwidth
Voice + Site Maintenance =

Sites of 16 RF Channel (8 dual 1.6MBps
[1] Site 1
TB9300 Base Stations 16 TOTAL (with 20% Contingency)
operating MPT-IP) = 1.92 Mbps
[2] Site 2 Voice + Site Maintenance =

[3] Site 3 400 kpbs +128kbps
[4] Site 4 Sites of 4 RF Channel (2 dual
[5} Site 5 TB9300 Base Stations 4 TOTAL(with 20% Contingency)
[6] Site 6 operating MPT-IP) = 634 kbps
[7] Site 7 Although Site maintenance is specified as
128kbps and it is recommended at 1M link
[8] Site 8 bandwidth be provisioned to facilitate
configuration
Voice + Site Maintenance =
200 kbps + 128kbps
TOTAL (with 20% Contingency)
[09] Site 9, = 394 kbps
[10] Site 10, Although Site maintenance is specified as
[11] Site 11 128kbps and it is recommended at 1M link
[12] Site 12 bandwidth be provisioned to facilitate
configuration
[13] Site 13
Sites of 2 RF Channel (1dual
[14] Site 14
[15] Site 15
TB9300 Base Stations 2
operating MPT-IP)
[16] Site 16
[17] Site 17
[18] Site 18
[19] Site 19
[20] Site 20
[21] Site 21
Site Number Site Name Required Bandwidth
DMR Site Traffic to Central

Location
(the aggregation of traffic to the central
1x1.92 Mbps
location depends on how the backhaul 7x394 kbps 2.949 Mbps
(+ 1M for Site Maintenance)
network are interconnected between 13x394 kbps
sites – the assumption here is that hub
and spoke topology for the backhaul) )
‘* all the above figures includes 1Mbps for site maintenance/remote monitoring and factors a 20% contingency overall.
Table 2: Link Bandwidth Requirements
3.3 Network Time Protocol (NTP)

The Network Time Protocol (NTP) will be used to keep node and monitor server clocks accurate. IP Service
Provider will need to supply IP address of NTP servers for time synchronization purposes. The NTP server is
configured on all TB9300 Base Stations, the MPT-IP Node and Tait Network Gateways.
The NTP server should be available for the MPT-IP network.
3.4 Quality of Service (QOS)

The backhaul network should use Differentiated Services Code Point (DSCP) to ensure that traffic over streams
are given the highest QOS priority on the network. The suggested DSCP assignments for the different packet
types are listed in the table below.
SERVICE CLASS TRAFFIC TYPE PACKET TYPE PROTOCOL PORT NUMBER DSCP
EXPEDITED FORWARDING REAL-TIME Voice data protocol UDP 9050 46 (EF)

(EF) (VDP/RTP)
Base station protocol UDP 9017 46 (EF)
(BSP)
Network gateway UDP 9006 46 (EF)

protocol (NGP)
ASSURED FORWARDING SIGNALLING Node to node TCP 9060 26 (AF31)

(AF) communications
Application interface UDP 5060 26 (AF31)

specification (AIS)
Dispatcher information TCP 9005 26 (AF31)

protocol (DIP)
Session initiation UDP 5060 26 (AF31)

protocol (SIP)
Location information UDP 11433 26 (AF31)

protocol (LIP)
Radius authentication UDP 1813 26 (AF31)
Mobile IP UDP 434 26 (AF31)
MANAGEMENT Domain Name Server TCP 53 28 (AF32)

(DNS)
ICMP TCP 28 (AF32)
Secure shell (ssh) TCP 22 28 (AF32)
Syslog UDP 514 28 (AF32)
SNMP UDP 161/162 28 (AF32)
CLASS SELECTOR (CS) NETWORK Routing protocols 48 (CS6)

CONTROL
BEST EFFORT WEB TRAFFIC Web interface TCP 443 0

(http/https)
Table 3: Quality of Service
Strict priority-queuing QoS is required. Weighted Fair Queuing (WFQ) such as 8421-type round-robin
priority queuing will typically breach the jitter requirement unless significant additional bandwidth is available.
Marking must be left intact by network switches and routers. In “Cisco speak” this means that a line such as
“mls qos trust dscp” must be present in the configuration of every router through which RF network traffic is
carried.
QoS will need to be applied to network equipment from IP Linking Service Provider.
3.5 IP Protocols and Ports

The network uses a variety of IP based protocols between its elements. In some situations firewalls must be
configured to allow this traffic to pass across the IP bearer network. The table below lists the ports and usage,
strike out font has been used where there is no plan to use the protocol in the pilot system :
Type Usage Ports/Protocols
Core Interfaces
Voice data protocol (VDP) Node controllers to/from base stations and UDP 9050
network gateways
Base station protocol (BSP) Node controllers to/from base stations UDP 9017
Network Gateway Protocol (NGP) Node Controllers to/from Network UDP 9006
Gateways
Node to node communications Node controllers to/from node controllers TCP 9060
Radius Authentication Radius Authentication Server to/from Node UDP 1813

Controllers, Switches, Base Stations,
Network Gateways and Routers
Interfaces to consoles, AVL and data applications
Dispatcher Interface Protocol (DIP) AVL and Dispatch systems to node TCP 9005
controllers
Application interface specification Dispatch systems to/from node controllers UDP/TCP 5060
(AIS)
Session initiation protocol (SIP) Telephony/PABX to/from node controllers UDP/TCP 5060
Real time protocol (RTP) Dispatch systems to/from node controllers UDP varies
Management interfaces
Web interface (https) Management PC to node controllers, base TCP 443

stations, NMS, switches and routers
Secure shell (ssh) Node controllers, network gateways, base TCP 22

stations, switches and routers to NMS
Syslog Node controllers, network gateways, base UDP 514

stations, switches and routers to NMS
Simple network management NMS to node controllers, network UDP 161/162

protocol (SNMP) gateways, base stations switches and
routers
ICMP NMS to node controllers, network ICMP

gateways, base stations switches and
routers
RDP SNMP Manager Remote Desktop. (Not TCP 3389

required but preferred for VPN access if
Enable Monitor is deployed)
Table 4: IP Protocols and Ports
3.6 Multicast
Multicast will need to be enabled on switches at all RF sites to support multi-repeater fallback modes. Multicast
will not be enabled on the primary router interfaces and will not cross the local switching domain onto the
National Police Network.
The Multicast address assignment for each of the site locations is given in Section 4. Site Equipment IP
Addressing
3.7 Backhaul Validation Approach

Due to the complexity of IP networks, it is impossible to perfectly predict performance during the design stage,
and for that reason they must be tested (and possibly configurations adjusted) after installation. Once the IP
linking architecture has been deployed by the IP Linking Service Provider, the performance needs to be
validated via testing.
The primary reason for the testing is to provide assurance that the IP network will perform to the standard
necessary for the MPT-IP network, and will therefore not degrade the performance of the radio system.
Key performance indicators (KPIs) are specific traffic characteristics that indicate the minimum performance
requirements of LMR traffic. KPIs for backhaul network are based on the system IP network requirements
defined in all Section 3 of this document, derived from Tait Technical Note TN-2167a “Network Linking Design”.
As the IP Linking Service Provider owns and operates the site-to-node IP links, the responsibility of testing the
links against the provided networking/linking requirement specification will be with theirs.
3.8 Site Equipment IP Addresses

The IP plan for the National Police Network will be designed based on recommendations within the TaitNet
MPT-IP Radio Network System Manual. Alternatively, the service provider needs to specify IP address
availability and subnets. The IP Address Plan based on recommendations from service manual for each of the
site locations is presented in Appendix A – IP Addressing Plan .
4. SECURITY REQUIREMENTS
4.1 Access Control
Operating
Tait Product Database Access Control Supported
System
Local user accounts
TN8291 Node Controller
CentOS 6.8 sqlite3 3.6 LDAP
(MPT-IP)
RADIUS (Authentication Only)
Web interface user accounts:
Local User Account

Linux kernel
TB9300 Base Station 3.12.36, plus Tait sqlite3 3.8.8.3 LDAP
modifications
RADIUS (Authentication Only)
SSH disabled by Web interface
Linux kernel 2.4,

TN8271 Network Gateway plus Tait Configuration file Root user account
modifications
Table 5: Access Control
4.2 Network Segmentation
4.2.1 Recommended Perimeter Security

IP networks should include perimeter security:
• Separation of National Police’s radio network from others’ LANs;
• Firewalling between networks and LANs; and
• Intrusion detection / prevention.
5. PROJECT ENGINEERING DOCUMENTATION ACCEPTANCE
ACKNOWLEDGEMENT
The signature of the responsible parties at SYSCOM NICARAGUA indicates their understanding and
acceptance of the IP network design services as described in this IP Linking and Backbone Specifications
Requirements document. Likewise, the signature of the responsible parties of Tait Radio Communications
indicates their understanding and acceptance to provide the system design as presented in this document and
reference deliverables including the corresponding supply of CISCO networking equipment, planning and
configuration of equipment.
Any changes required after the signing of this document will require a revision of this document and the
agreement and signature of all parties involved. The full impact of any changes will be fully described in the
revised document.
Signed by Representative of Tait Comments
Name
Signature
Date
Signed by Representative of SYSCOM

Comments
NICARAGUA
Name
Signature
Date
APPENDIX A – IP ADDRESSING PLAN
All Site LAN IP address ranges are tentative - (To be provided by Service Provider ISP)
Infrastructure Equipment IP addressing

Suggested LAN IP Subnet: 172.18.101.0/24
Item Description Device IP Address
MPT-IP Node Controller 1 TN8291-N2 172.18.101.11
MPT-IP Node Controller 1 BMC (LOM) TN8291-N2 172.18.101.10
Routers at Central Site CISCO ISR 4331 172.18.101.1
Switch at Central Location SM-X EtherSwitch within 172.18.101.2

ISR4331
RF Site Equipment IP Addressing

Within each of the sites there are common hardware elements.
The IP addresses for the hardware elements are given in the following tables.
Site 1
TB9300-CH1 TB9300 Channel 1 172.18.1.11
TB9300-CH2 TB9300 Channel 2 172.18.1.12
TB9300-CH3 TB9300 Channel 3 172.18.1.13
TB9300-CH4 TB9300 Channel 4 172.18.1.14
TB9300-CH5 TB9300 Channel 5 172.18.1.15
TB9300-CH6 TB9300 Channel 6 172.18.1.16
TB9300-CH7 TB9300 Channel 7 172.18.1.17
TB9300-CH8 TB9300 Channel 8 172.18.1.18
TB9300-CH9 TB9300 Channel 9 172.18.1.19
TB9300-CH10 TB9300 Channel 10 172.18.1.20
TB9300-CH11 TB9300 Channel 11 172.18.1.21
TB9300-CH12 TB9300 Channel 12 172.18.1.22
TB9300-CH13 TB9300 Channel 13 172.18.1.23
TB9300-CH14 TB9300 Channel 14 172.18.1.24
TB9300-CH15 TB9300 Channel 15 172.18.1.25
TB9300-CH16 TB9300 Channel 16 172.18.1.26
Switch Cisco Catalyst 3650 24 Port 172.18.1.2
Interface Router ISP Router Port 172.18.1.1
Site 2
TB9300-CH1 TB9300 Channel 1 172.18.1.141
TB9300-CH2 TB9300 Channel 2 172.18.1.142
TB9300-CH3 TB9300 Channel 3 172.18.1.143
TB9300-CH4 TB9300 Channel 4 172.18.1.144
Site 3
TB9300-CH1 TB9300 Channel 1 172.18.2.11
TB9300-CH2 TB9300 Channel 2 172.18.2.12
TB9300-CH3 TB9300 Channel 3 172.18.2.13
TB9300-CH4 TB9300 Channel 4 172.18.2.14
Site 4
TB9300-CH1 TB9300 Channel 1 172.18.2.141
TB9300-CH2 TB9300 Channel 2 172.18.2.142
TB9300-CH3 TB9300 Channel 3 172.18.2.143
TB9300-CH4 TB9300 Channel 4 172.18.2.144
Site 5
TB9300-CH1 TB9300 Channel 1 172.18.3.11
TB9300-CH2 TB9300 Channel 2 172.18.3.12
TB9300-CH3 TB9300 Channel 3 172.18.3.13
TB9300-CH4 TB9300 Channel 4 172.18.3.14
Site 6
TB9300-CH1 TB9300 Channel 1 172.18.3.141
TB9300-CH2 TB9300 Channel 2 172.18.3.142
TB9300-CH3 TB9300 Channel 3 172.18.3.143
TB9300-CH4 TB9300 Channel 4 172.18.3.144
Site 7
TB9300-CH1 TB9300 Channel 1 172.18.4.11
TB9300-CH2 TB9300 Channel 2 172.18.4.12
TB9300-CH3 TB9300 Channel 3 172.18.4.13
TB9300-CH4 TB9300 Channel 4 172.18.4.14
Site 8
TB9300-CH1 TB9300 Channel 1 172.18.4.141
TB9300-CH2 TB9300 Channel 2 172.18.4.142
TB9300-CH3 TB9300 Channel 3 172.18.4.143
TB9300-CH4 TB9300 Channel 4 172.18.4.144
Site 9
TB9300-CH1 TB9300 Channel 1 172.18.5.11
TB9300-CH2 TB9300 Channel 2 172.18.5.12
Site 10
TB9300-CH1 TB9300 Channel 1 172.18.5.141
TB9300-CH2 TB9300 Channel 2 172.18.5.142
Site 11
TB9300-CH1 TB9300 Channel 1 172.18.6.11
TB9300-CH2 TB9300 Channel 2 172.18.6.12
Site 12
TB9300-CH1 TB9300 Channel 1 172.18.6.141
TB9300-CH2 TB9300 Channel 2 172.18.6.142
Site 13
TB9300-CH1 TB9300 Channel 1 172.18.7.11
TB9300-CH2 TB9300 Channel 2 172.18.7.12
Site 14
TB9300-CH1 TB9300 Channel 1 172.18.7.141
TB9300-CH2 TB9300 Channel 2 172.18.7.142
Site 15
TB9300-CH1 TB9300 Channel 1 172.18.8.11
TB9300-CH2 TB9300 Channel 2 172.18.8.12
Site 16
TB9300-CH1 TB9300 Channel 1 172.18.8.141
TB9300-CH2 TB9300 Channel 2 172.18.8.142
Site 17
TB9300-CH1 TB9300 Channel 1 172.18.9.11
TB9300-CH2 TB9300 Channel 2 172.18.9.12
Site 18
TB9300-CH1 TB9300 Channel 1 172.18.9.141
TB9300-CH2 TB9300 Channel 2 172.18.9.142
Site 19
TB9300-CH1 TB9300 Channel 1 172.18.10.11
TB9300-CH2 TB9300 Channel 2 172.18.10.12
Site 20
TB9300-CH1 TB9300 Channel 1 172.18.10.141
TB9300-CH2 TB9300 Channel 2 172.18.10.142
Site 21
TB9300-CH1 TB9300 Channel 1 172.18.11.11
TB9300-CH2 TB9300 Channel 2 172.18.11.12

Cableado Estructurado

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cableado Estructurado

Uploaded by

Copyright:

Available Formats

NICARAGUA NATIONAL POLICE

MPT System Upgrade and Expansion

Tait Project Number:

Tait Communications Corporate Head Office

Tait Communications Regional Office

For addresses and telephone numbers of regional offices, refer to http://www.taitradio.com.

COPYRIGHT AND TRADEMARKS

2. RADIO SYSTEM OVERVIEW.................................................................................................................... 9

3. IP LINKING REQUIREMENTS ................................................................................................................ 10

4. SECURITY REQUIREMENTS ................................................................................................................. 16

5. PROJECT ENGINEERING DOCUMENTATION ACCEPTANCE ACKNOWLEDGEMENT.................... 17

APPENDIX A – IP ADDRESSING PLAN ........................................................................................................... 18

SYSCOM NICARAGUA – NICARAGUA NATIONAL POLICE

Project description MPT System Upgrade and Expansion

Technical Authority Blad Guzman

Project Manager Fabian Castiblanco

Global Program Manager Wellington Carvalho

Deployment Engineer Fabian Castiblanco

Issue Version 1.1

Status Final for Customer Review

Date 2 April 2018

1.02 Mar 27,2018 FC IP addressing suggest by Nicaragua Police

Terms and Abbreviations

Abbreviation / Term Description

Control plane traffic – call signalling, trunked registration, mode

DMR Digital Mobile Radio, a standards based two-way radio technology

DSCP Differentiated Services Code Point

Variation in latency. See ITU-Y Y.1541 and RFC3393. Measured at the

LAN Local area network

LMR Land Mobile Radio

Arithmetic mean delay for voice-service sized packets (approx. 200

Management plane traffic – Monitoring, configuration. The aggregation

NTP Network time protocol

Type P one-way packet loss as defined in RFC 2680, where the

QoS Quality of Service

SNMP Simple Network Management Protocol

User plane traffic – voice or packet data from subscriber equipment or

WAN Wide area network

MNA-00026-09 TaitNet MPT-IP Radio Network System Manual

TN-2167a Technical Note TN-2167a, Network Linking Design, November 2015

CISCO WS-C3650-24 CISCO WS-C3650-24

TCP/IP Linking Backbone (including firewalls)

MPT-IP Node Controller x1

CISCO 4331 TCP/IP Connections (x4) x4Wire Connections

Node Central Site

3.1 Network Performance

Parameter Value (ms)

Out of order C and U traffic packets Less than 0.01%

Packet Loss Less than 0.01%

Latency (max) 100 ms

Latency (recommended) Less than 40 ms

Jitter (max) Less than 20 ms

3.2 Site Bandwidth Requirements

Site Name Site Name Channel Count Required Bandwidth

Voice + Site Maintenance =

[2] Site 2 Voice + Site Maintenance =

Site Number Site Name Required Bandwidth

DMR Site Traffic to Central

Table 2: Link Bandwidth Requirements

3.3 Network Time Protocol (NTP)

3.4 Quality of Service (QOS)

EXPEDITED FORWARDING REAL-TIME Voice data protocol UDP 9050 46 (EF)

Network gateway UDP 9006 46 (EF)