MOTOTRBOTM LINKED CAPACITY PLUS Training Roadshow.

MOTOTRBOTM LINKED CAPACITY PLUS Training Roadshow

Linked Capacity Plus OVERVIEW
Combines all the benefits of IP Site Connect and Capacity Plus Adds CAPACITY to existing IP Site Connect (IPSC) systems Adds COVERAGE to existing Capacity Plus (Cap+) systems No central controller needed Logic is managed in a distributed fashion like Cap+ Does not use a dedicated control channel Resilient to channel interference Suitable for shared channels Repeaters (Peers) / sites connected via an IPv4 based network like IPSC Linked Capacity Plus (LCP) requires more bandwidth than IPSC Consists of up to 5 sites (15 sites - future release) Up to 6 trunked (voice and data) & 3 data revert repeaters per site Same number of repeaters per site not required Tolerates failures by design The Master repeater is the single point of failure, however this single point of failure is limited only to the arbitration of IP addresses Cap+ / LCP provides a Control Channel (known as a Rest Channel) in all senses of the meaning, however it is not dedicated to a single repeater channel / sot. The reasons why Cap+ / LCP utilises a Control (Rest) Channel which rotates among the repeaters at a given site are as follows: Call setup time is improved because it is the radios not involved in the call setup that move to a new channel rather than the radios involved in the call setup. The system is resilient to RF interference because a repeater detecting interference is simply removed from the pool of available channels until the RF interference disappears (if the system contained a dedicated control channel then this would be a single point of failure). The system is resilient to equipment failure because a non-functioning repeater is simply removed from the pool of available channels (again, if the system contained a dedicated control channel then this would be a single point of failure). Excessive “control” loading shared among several repeaters rather than placed on a single repeater.

} = Linked Capacity Plus OVERVIEW Linked Capacity Plus BR 12 Site 1
A set of Single-Site Capacity Plus systems + Physical connection like an IP Site System + Some additional software Linked Capacity Plus System Wide Master Capacity Plus  Trunking IP Site Connect  Link Management, Wide Area call processing Additional Software  Dynamically forms an IPSC between the current Rest channels Identifies the Rest channel Combines the Call set-up procedures (i.e. Arbitration + TRT*) (* TRT: Transmit-Receive-Transmit) BR 11 BR 12 Site 1 BR 13 BR 14 Switch BR 21 BR 22 Site 2 BR 23 BR 24 BR 31 Master BR 32 Site 3 BR 33 Router WAN IP Network Can use MTR3000 and/or 32MB DR 3000 repeaters (but NOT 8MB DR 3000 repeaters). Rest channel Master

Features Includes the following MOTOTRBO “special” features Enhanced privacy Transmit Interrupt Digital telephone patch GPS (including enhanced) Data applications (ADP interfaces) Option board RDAC Includes the following trunking system features Selective site light-up: Dynamic for individual calls Static for talkgroup calls Automatic subscriber roaming Site restriction

Total Number of Talkgroups
Linked Capacity Plus OVERVIEW Features ID Space for Talkgroups is limited to 1 to 254 for Local and Wide Area Talkgroups (W = Number of Wide Area IDs, S = Number of sites) No local channels like IPSC No local All Call Talkgroup A Wide Area Talkgroup ID is associated with a set of sites Enables Statically defined Selective site “light up” for Talkgroup calls A number of channels at each site can optionally be reserved for Wide Area talkgroup calls. All Wide Area talkgroup repeater configuration parameters are provisioned into the Master repeater only. Group Call Type Site 1 Site 2 … Site S Total Number of IDs Local 254-W (254-W) * S Wide Area W Total Number of Talkgroups (254-W) * S + W The ID space for Talkgroups is limited to {1..254} A customer can define some of these IDs (say “w”) as Wide Area The remainder of the IDs are Local Local Talkgroup IDs can be reused at different sites Thus, total number of talkgroups = (254 – w) * s + w (where “s” is the number of sites) Why LCP uses local talkgroups instead of local channels? 1. LCP is a trunked system and efficiency of trunking increases with number of available channels. By not dividing the channels into two groups of local and wide area channels, the number of channels available for trunking increases, which increases the trunking efficiency. 2. The local talkgroup Ids can be reused at other sites and thus effectively increases the total number of talkgroup Ids. 3. The local talkgroups provide backward compatibility to the existing talkgroups of a Capacity Plus system. 4. Unlike local channels, the local talkgroups do not require a radio user to change personality before PTT.

Features - Data LCP data is similar to Cap+… Radio to Radio data is always on a trunked channel Server to Radio data is always on a trunked channel Radio to Server data is either on a trunked or data revert channel Radios share the revert channels LCP data is similar to IPSC… Supports both local and wide area data revert channels A wide area / local setting is configured into all data revert repeaters A wide area data revert channel is formed by multiple data revert channels (one per site) sharing a common Channel ID Initially, LCP supports server data via Control stations ONLY In the future, LCP will also support server data via the repeater IP interface

Features - Data Flexibility for configuring Data Revert Repeater Channel IDs. Example System 1 Site 1 (Ch ID 33W) Site -2 (Ch ID 33W) Site 3 (Ch ID 33W) Site 4 (Ch ID 33W) Site 5 (Ch ID 33W) Example System 2 Site 1 (Ch ID 33W) Site -2 (Ch ID 33W) Site 3 (Ch ID 33W) Site 4 (Ch ID 35W) Site 5 (Ch ID 35W) Example System 3 Example system 1: Shows 1 wide area data revert channel across 5 sites. Example system 2: Shows 1 wide area data revert channel across 3 sites and 1 wide area data revert channel across 2 sites. Example system 3: Shows 5 local data revert channels (since all repeaters are configured for ‘Local’, it makes no difference what the Channel IDs are set to). Site 1 (Ch ID 33L) Site -2 (Ch ID 33L) Site 3 (Ch ID 43L) Site 4 (Ch ID 47L) Site 5 (Ch ID 47L)

Features LCP does not support… Priority Queuing of Calls However, where all system channels are busy: Emergency calls are able to clear down existing calls using transmit interrupt (if necessary). Additionally, supervisors can clear down existing calls using transmit interrupt (Remote Voice De-key). Priority Monitor* However, this is supported for All Call and Emergency call Subscriber Access Control However, this will be supported in a release later this year (* this is the ability for radios to leave a call in progress to join a higher priority call)

System Loading An LCP system handles Local calls as efficiently as Cap+, therefore if all calls are Local, T = the sum of the number of radios supported by each individual site. The number of radios supported by a given LCP site = the number of radios supported by a Cap+ system having the same number of trunked channels. If there are Wide Area calls, T is estimated by first estimating R for a Cap+ system having N trunked channels. If all calls are Wide Area, T = R. If there are a mixture of both Local and Wide Area calls, T = R*S (L + (1-L)/W) Note: T = Total number of Radios supported by LCP system R = Number of Radios supported by Cap+ system N = Number of trunked channels at the smallest LCP site S = Number of LCP Sites W = Average number of Sites associated with Wide Area Talkgroups L = Number of Local calls as a fraction of the total number of calls

System Loading Example For a 5 site system where each site contains 12 trunking channels: Assume the loading for a 12 channel Cap+ system = 1,200 radios (note: this corresponds to low voice, low GPS & 5% GoS). If all calls are local, LCP loading = 1,200 x 5 = 6,000 radios If all calls are wide area, LCP loading = 1,200 radios If 40% of calls are Local and Wide Area calls are setup over an average of 3 sites, LCP loading = 1,200 x 5 ( (1 – 0.4)/3) = 3,600 radios

Requires a software upgrade of radios and repeaters Repeaters must have 32MB of flash memory Compatible with current and next generation MOTOTRBO radios Requires feature activation in the repeater HKVN4108A DR 3000 Full license key* HKVN4063A DR 3000 Incremental license key (from Cap+) HKVN4109A MTR3000 Full license key* HKVN4070A MTR3000 Incremental license key (from Cap+) New LCP compatible version of RDAC available GMVN5520F RDAC CD * The full LCP license does not support Cap+ channels, so if a repeater needs also to support Cap+ channels then a Cap+ / Incr. LCP license combination should be purchased instead.

Backwards compatibility with Cap+ An old (non-upgraded) Cap+ radio will only operate on a single LCP site. However, its ID must still be unique across all sites for the LCP system. Site 1 Site 2 Old radios can neither make nor receive Wide Area Individual Calls Old radios can receive incoming audio targeted to a Wide Area TG but can not transmit audio to a Wide Area TG. Compatible Individual calls Compatible Group calls Incompatible Calls Old Old (1) (1) New New (1) (2) (2) New Old New New Full Old/New interoperability for: Local individual calls Local talkgroup calls Limited Old/New interoperability for: Wide area talkgroup calls (Old radios can receive but NOT transmit in wide area talkgroups) No Old/New interoperability for: Wide area individual calls Local TG Wide Area TG

Linked Capacity Plus COMPONENTS
Complete System System Wide Master BR 11 BR 12 Site 1 BR 13 BR 14 Router + Switch BR 21 BR 22 Site 2 BR 23 BR 24 BR 31 Master BR 32 Site 3 BR 33 TRNK CS TRNK CS LAN Network LAN Network LAN Network Conv CS BR 34 Conv CS RDAC Figure shows a basic LCP system having three sites. Each site has 3 trunked repeaters, however the number of repeaters/site does not need to be the same Each site also has one data revert repeater, where the data revert repeaters are acting in “wide area” mode. Only one of the repeaters has an additional role of “Master”, which acts as a broker for discovering repeaters If the address of the Master changes, then all the repeaters must be reconfigured with the new address. PC1 Router + Switch Router + Switch WAN IP Network Rest channel Master Data Revert Repeaters (Optional)

Linked Capacity Plus Components
The role of the “Master” System Wide Master Requires a static IP address of which all repeaters (via their configuration) need to be aware Introduces repeaters to each other Single point of failure (for arbitration of IP addresses) BR 11 BR 12 Site 1 BR 13 BR 14 Router + Switch BR 21 BR 22 Site 2 BR 23 BR 24 BR 31 Master BR 32 Site 3 BR 33 LAN Network LAN Network LAN Network BR 34 Router + Switch Router + Switch WAN IP Network Rest channel Master Data Revert Repeaters (Optional)

If the Master repeater fails… The system continues to function Additional repeaters, sites, or host PCs CANNOT be added to the system A redundant repeater can be switched to act as a Master

The role of a “Peer” Exchange “Keep Alive” messages Use information to dynamically configure system Participate in selecting the next Rest Channel Distribute the voice/data payload to all repeaters BR 11 BR 12 Site 1 BR 13 BR 14 Router + Switch BR 21 BR 22 Site 2 BR 23 BR 24 BR 31 Master BR 32 Site 3 BR 33 LAN Network LAN Network LAN Network BR 34 Router + Switch Router + Switch WAN IP Network Rest channel Master Data Revert Repeaters (Optional)

Linked Capacity Plus BACK END NETWORK
Repeaters at a site are connected over a LAN like Cap+ Only LCP repeaters should be present on the LAN BR 11 BR 12 Site 1 BR 13 BR 14 Router + Switch BR 21 BR 22 Site 2 BR 23 BR 24 BR 31 Master BR 32 Site 3 BR 33 An IP Network is used for voice / data communication between sites like IPSC Requires greater bandwidth (compared to IPSC) from ISP provider. LAN Network LAN Network LAN Network BR 34 Router + Switch Router + Switch WAN IP Network Rest channel Master All repeaters (and only the repeaters) at a site must be behind a router and a switch Data Revert Repeaters (Optional)

IP Limited Broadcast address (255.255.255.255) messages
Linked Capacity Plus BACK END NETWORK Communication Among Repeaters IP Limited Broadcast address ( ) messages IP Limited Broadcast address messages: For communication among repeaters at a site. Common Site IP Address messages: Rest channel repeaters uses these to generate periodic site Keep Alive messages. Start of call setup: Source Rest channel repeater sends one message to each Site IP Address associated with call, and each Rest Channel repeater in call responds such that all repeaters in call learn IP addresses of all other repeaters (at other sites) in call. Common Site IP Address messages BR 11 BR 12 Site 1 BR 13 BR 14 Router + Switch BR 21 BR 22 Site 2 BR 23 BR 24 BR 31 Master BR 32 Site 3 BR 33 LAN Network LAN Network LAN Network BR 34 LCP repeaters at a given site use IP Limited Broadcast address ( ) messages to communicate among each other when managing (for example) the site’s Rest Channel (note: Cap+ repeaters communicate with each other using multiple unicast messages). LCP repeaters at a given site are configured with a common Site IP Address (referred to as the Rest Channel IP Address by the CPS) and the current Rest Channel repeater at the site uses this Site IP Address when sending periodic Keep Alive messages to the other sites. At the start of a new call the source Rest channel repeater does not know which are the current Rest channel repeaters at the other sites. The source Rest channel repeater therefore sends one message to each Site IP Address associated with the call (note: the source Rest channel repeater finds out from the Master repeater which Site IP Addresses to use). When a repeater at a given site receives a Site IP address message, it re-broadcasts this message to the other repeaters at that site using the IP Limited Broadcast address message (note: the repeater that receives the Site IP Address message will normally be the Rest channel repeater unless the Rest channel has changed since the last Keep Alive message was generated). The current Rest Channel repeater at the site then responds to the Site IP address message. This mechanism enables all repeaters involved in a call to learn which are the other repeaters (at the other sites) involved in the same call. LCP uses 3 types of keep alive message Repeaters at a given site send periodic keep alive messages to each other using the IP Limited Broadcast address message. These are used to manage the site rest channel. Repeaters send period keep alive messages to the Master repeater and RDAC. These are used for automatic discovery of repeaters and to keep open ports from the Master repeater and RDAC to all repeaters in the system. The rest channel repeater at each site sends periodic keep alive messages to the other sites. These are used during call initiation and for beacon synchronisation. These message also keep open ports between the sites. Router + Switch Router + Switch WAN IP Network Rest channel Master Data Revert Repeaters (Optional)

Linked Capacity Plus BACK END NETWORK
Considerations Master repeater - Must have a static IPv4 address Peer repeaters (and RDAC applications) - Either static or dynamic IP IPv4 addresses. Since LCP repeaters at a given site use IP Limited Broadcast address messages to communicate among each other, then: All repeaters pertaining to a given site must be behind a single Ethernet Switch/Router The only devices that can be on the site’s LAN are the repeaters pertaining to that site (and any RDAC applications) Hairpinning routers generally* do not need to be used Refer to the System Planner for details on recommended Switches/Routers. For constructing a small Linked capacity Plus demo system, the “NETGEAR WNR1000” Ethernet Switch/Router is recommended. Refer to the System Planner for details on how to calculate the bandwidth requirements of the backend network. * A Hairpinning router must be used at a site if that site contains multiple LCP devices and one of these devices is either a Master repeater or an RDAC application. All repeaters pertaining to a given site must be behind a single Ethernet Switch/Router because IP Limited Broadcast address messages never get forwarded by a site’s router to the WAN. The only devices that can be on the site’s LAN are the repeaters pertaining to that site (and any RDAC applications) because IP Limited Broadcast address messages (which are received by all devices on the LAN) could have an undesired effect on other devices. Hairpinning routers generally* do not need to be used, again because IP Limited Broadcast address messages never get forwarded by a site’s router to the WAN. A Hairpinning router must be used at a site if that site contains multiple LCP devices and one of these devices is either a Master repeater or an RDAC application, since: Peers need to address the Master repeater using its WAN address. An RDAC application communicates directly with repeaters (rather than using IP Limited Broadcast address messages).

Linked Capacity Plus PROCEDURES
A Wide Area Talkgroup call goes out on it’s (CPS configured) associated sites and only starts if channels are available at all associated sites. A configurable number of channels at each site can be reserved for Wide Area Talkgroup calls). A radio tries up to 3 times to setup a call with random delays inserted in between each attempt. An Individual call setup goes out on all sites where a channel is available. These sites all attempt a high-speed handshake (called “RTR”) with the target radio. The site that succeeds with the high-speed handshake and the site where the initiating radio is located remain in the call while the other sites drop out (i.e. Dynamic selective site light-up). The high-speed handshake occurs concurrently with the call set-up, so no additional delay. Since a Wide Area Talkgroup call only goes out on it’s configured associated sites, this provides static selective site light-up for Wide Area Talkgroup calls. A configurable number of channels at each site can be reserved for Wide Area Talkgroup calls to help prevent local calls from capturing all trunked channels at a site, leaving no channels available for Wide Area Talkgroup calls. For an individual call setup, if the initiating and target radios are on the same site this leaves 1 site involved in the individual call and if the initiating and target radios are on different sites this leaves 2 sites involved in the individual call. This provides Dynamic selective site light-up for Individual Calls.

Linked Capacity Plus PROCEDURES
“TRT” in Cap+ restricts the effect of collisions. “Arbitration” in IPSC ensures that all the sites select the same call. LCP improves and combines these two processes into a single process called “TR-A-RT”. “TR-A-RT” can manage and allocate the channels for up to 5 concurrent calls (each occurring at separate sites) in one arbitration. The Wide Area Call setup time for LCP is approximately 240 ms more than for Cap+ (this increases where more than 2 concurrent calls need to be allocated). The Local Call setup time for LCP is same as for Cap+. A radio can receive a Digital Telephone Patch Call on any site, however a radio can only initiate a Digital Telephone patch call on a site connected to an APP (i.e. a radio can not initiate a Digital telephone patch call via an APP connected to a different site).

Linked Capacity Plus procedures
Emergency Voice Call User initiation of Emergency LCP only uses impolite channel access for emergency calls (where necessary). When a repeater detects an impolite call it updates the system call status to the new call. LCP frees up channels at associated sites (if necessary) during an emergency call setup. The start of an emergency call is announced over all busy channels at all associated sites, thereby allowing radios to leave their current calls and join the emergency call (where applicable). After setting up an emergency call, if there are no free channels left at a site then the busy rest channel shifts to a channel where there is a non emergency call in progress (thus ensuring that one emergency call does not clear down another emergency call). Yes Radio on Traffic channel? Move to Rest Channel No Emergency Call for same Talkgroup already active? Emergency Call transmitted over ongoing Emergency Call because receiving radios already on channel. Yes No Emergency Call transmitted on Idle Rest channel. Yes Rest Channel Idle? No Call on busy Rest Channel interruptible? Transmit interrupt used to stop ongoing call. Emergency Call then transmitted on Idle Rest channel. Emergency Call transmitted impolitely over busy Rest channel. No Yes

CPS Configurable Interval
Linked Capacity Plus procedures Roaming To minimise the amount of Beacon signalling An LCP (Roaming) Beacon is appended to every 5th Cap+ (Lost Signal Detection) Beacon To facilitate faster scanning The Rest Channels at all the sites synchronise their Beacons The LCP (Roaming) Beacons at a given site contain a list of Rest Channel IDs for that site’s neighbouring sites Radios use the list of Rest Channel IDs for a site’s neighbouring sites to determine which channels to scan when trying to roam using either Passive or Active Site search The list of neighbouring sites for each site is configured only into the Master repeater (note: the Master repeater shares this information with all the other repeaters in the system) Site 1 Rest Channel LCP Beacon 5 * Cap+ Beacon Interval CPS Configurable Interval Cap+ Beacon Site 2 Rest Channel Site 3 Rest Channel Site 4 Rest Channel Site 5 Rest Channel

Roaming – Passive Site Search (Automatic Roaming) Radio builds up sorted roam list based on the LCP (Roaming) Beacons transmitted on the home site’s Rest Channels. If home site signal strength drops below a programmable threshold, radio starts to scan through sorted roam list for a new site Radio only scans for a new site while in the idle state. Also, the radio does not scan for new site if Site Lock feature enabled. During Passive Site search, radio identifies site with strongest signal then makes that site its new home site. Radio remains on the current home site and continues scanning until a better site is found. While a radio is carrying out a Passive Site Search, it needs to leave its current home site for short durations which may cause the radio to miss activity on its home site (resulting in late entry to voice calls, or missed control/data). To minimise missed activity on home site, programmable threshold should not be configured too high. Additionally, a user may suspend automatic roaming using the Site Lock feature (this is particularly useful if the radio is stationary and the user is satisfied with the quality of service from the current home site).

Roaming – Active Site Search Radio sends wake-up messages to each site in sorted roam list until it finds an active site. Active Site Search is initiated if a radio initiates transmission and it’s home site rest channel repeater can not be woken, or a user initiates a Manual Site Roam (using the menu or a programmable button). On waking a repeater, the radio synchronises itself with the repeater, completes the transmission and makes the new site its home site. If the end of the sorted roam list is reached and a site is not found, the radio provides the user with a failure indication. Active Site Search does not necessarily find the best site, but rather allows the radio to move to the next “in range” site. During an active site search radios only transmit a single (polite) wake up message to any given repeater, however there may still be regulatory reasons why it might not be desirable for a radio to transmit wake up messages on each of its sorted roam list member’s frequencies until a site is found. Where this is the case, then radios should be configured with Active Site Search disabled.

Linked capacity Plus User Interface
Home Screen Roaming Icon: Radio not in locked state. It will disappear after the user locks the site. Channel name Turn on repeaters Press PB to lock site Out of range state (Same as Cap+) Unlock state Lock State Radio’s LED will flash yellow if radio in system busy or local system busy state

Linked capacity Plus User Interface
Site Information Press Programmable Button to display site alias Site Alias Site Number Press site button to display site alias Press Programmable Button to find site Cannot find site Press PB to find site Successfully Found Site

Linked capacity PLUS DEMO SYSTEM
Equipment List 4 x DR 3000 UHF1, 1-25W (MDM27QNR9JA7AN) 4 x DR 3000 Linked Capacity Plus full licence key (HKVN4108A) 4 x DP 3600 UHF1 (MDH55QDH9JA1AN) 1 x RDAC v4.0 (Build 50) (GMVN5520F) 3 x NETGEAR WNR1000 Wireless Router including power supply ( 4 x 30dB attenuator 7 x Ethernet cable 1 x PC (for RDAC application)

System Architecture There are 3 subnets (Site 1, Site 2 and WAN) and each subnet has its own IP Address range.. Each LCP device (i.e. Repeater/RDAC) is addressed by an IP Address/UDP Port number. Repeaters also contain a Rest Channel (or Site) IP/UDP Address which is common among all repeaters at a site and is used when addressing a site rather than an individual repeater. At power up, each LCP device registers with the Master using the Master’s wide area IP/UDP Address (i.e /50011). The Master stores each LCP device’s return IP/UDP Address. The Site 1 (Master Site) router needs configuring for Port Forwarding. Even LCP devices on the Master Site need to use the Master’s wide area IP/UDP Address, this requires the Site 1 (Master Site) router to support Hairpinning. RDAC can also be placed at a site.

Site 1 (Master) Router Configuration – Step 1, Disabling the Wireless Router Step 1 Configure the local area network on the computer to be in the same subnet as the router The default address of the Netgear WNR1000 router is User Name: Admin , Password: password Go to Wireless Setting and uncheck ‘Enable Wireless Router Radio’ to disabled the wireless

Site 1 (Master) Router Configuration - Step 2, Setting the LAN IP Step 2 Go to the ‘LAN Setup’ tab to configure the local area network IP address to a static. In this example on the master end, the IP address is set as , IP submask is set as Click ‘apply’ to make the change

Site 1 (Master) Router Configuration – Step 3, Setting the WAN IP Step 3 Go to the ‘Basic Setting’ tab to configure the Wide area network IP address to a static address. In this example on the master end, the IP address is set as , IP subnet mask is set as , Gateway IP address set as Set both the Primary and Secondary DNS IP to Click ‘apply’ to make the change

Site 1 (Master) Router Configuration - Step 4, Setting the Port Forwarding Step 4 Go to the ‘Port Forwarding’ tab Click ‘Add Customer Service’ to configure the port requires to be forwarded.

Site 1 (Master) Router Configuration - Setting the Port Forwarding Provide a Service Name. In this example, ‘Master’ is use as the service name Under the service type, choose ‘TCP/UDP’ or ‘UDP’ Specify the start port number and end port number. In this example, enter ‘50011’ as both the start and end port number Enter the Master Repeater’s IP address under the Server IP address. In this example, the master Repeater IP address is Click ‘apply’ to make the change Port forwarding is designed for FTP, Web server, or other server-based services. Once port forwarding is set up, requests from the WAN are forwarded to the master repeater.

Site 2 (Peer) Router Configuration Step 1 - Disabling the Wireless Router Step 2 - Set the LAN IP Step 3 – Set the WAN IP WAN Router Configuration Step 1 - Disabling the Wireless Router Step 2 - Set the LAN IP

Repeater Configuration – General Settings / Privacy Upgrade all repeaters to LCP compatible version of firmware. Activate LCP licenses in all repeaters. Configure General Settings: Choose unique Radio name / ID All repeaters on the same site share the same Site ID / Alias (note: radio’s also need to be configured with the same Site ID / Alias in their Site Lists). Set Privacy Type.

Repeater Configuration – Network Configure Network: Set Link Type to Master or Peer accordingly. For Peer repeaters define the Master IP / UDP Port. This must correspond to an address which is visible on the WAN port of the Master site router which for the LCP demo system is / (note: cannot be used because this local address is not visible to Peers outside the Site 1 LAN). Ensure DHCP is not selected for the Master and set accordingly for each Peer. For the LCP demo system all IP addresses are static. For static IP addresses, configure the LAN parameters (Ethernet IP / Gateway IP / Gateway Netmask) accordingly. Configure the UDP Port accordingly. For the LCP demo system unique UDP Ports have been used for simplicity, however most router NAT algorithms should be able to manage duplicate UDP ports on their LANs. For Peer repeaters set the ‘Peer Firewall Open Timer’ accordingly to ensure sufficiently regular keep-alive messages are generated in order to maintain the connections open. The LCP beacon interval is five times the Cap+ beacon interval and the LCP beacon duration consists of a single burst appended to every 5th Cap+ beacon. All repeaters on the same site share the same Rest Channel/Site IP and UDP Port.

Repeater Configuration – Cap+ Voice Channel (Linked) Add a Capacity Plus Voice Channel (Linked): The ‘Message Delay’ is a new parameter for LCP and this needs to be left as ‘Normal’. The ‘RSSI Threshold (dBm)’ value determines the level at which an interfering signal causes the repeater to temporarily withdraw itself from the pool of available channels. For the LCP demo system -90 dBm should be sufficiently high. Set the Slot 1 / 2 Channel IDs to unique values for that site (note: radios also need to be configured with these Channel IDs). Configure the Colour Code and Rx/Tx frequencies accordingly. For the LCP demo system the Power Level needs to be set to Low to minimise interference and help demonstrate roaming.

Repeater Configuration – Sites / Talkgroups (Master Only) Site 1 Site 2 For the Master repeater only, define the system sites: Configure the number of channels to be reserved at each site for Wide Area calls (this improves wide area call setup reliability for busy systems). Define the neighbouring sites (i.e. the overlapping sites) for each site – this speeds up automatic roaming. For the Master repeater only, define the wide area talkgroup calls. For the LCP demo system there is just one wide area call which is associated with both sites, all other talkgroup calls are treated as local.

Radio Configuration – General Settings Configure General Settings: Choose unique Radio name / ID.

Radio Configuration – Cap+ Contacts / Cap+ Group Lists Configure Contacts (as per Capacity Plus). Configure Group Lists (as per Capacity Plus).

Radio Configuration – Cap+ Channels Configure all LCP channels (for all sites) in the Channel Pool (as per Capacity Plus): Ensure that Color Code and RX/TX frequencies are consistent with the repeater configurations.

Radio Configuration – Channel Lists (for each site) Configure Channel Lists for each site (as per Capacity Plus): Ensure that Channel IDs are consistent with the repeater configurations.

Radio Configuration – LCP Site Lists (for all sites) Configure LCP site lists: For each list, include only those sites on which the radio is required to operate (for the LCP demo system there are three examples provided; one where the radio operates on both sites, one where the radio operates only on site 1 and one where the radio operates only on site 2). For each list, specify the ‘RSSI Threshold (dBm)’ at which the radio is required to start scanning for another site. For each site, specify the Site ID / Alias and ensure that these are consistent with the repeater configurations. For each site, specify the Voice / Data Lists (for Capacity Plus this is specified at a Channel / Personality level). For each site, specify the RX Group List (for Capacity Plus this is specified as a Channel / Personality level).

Radio Configuration – LCP Channels / Personalities Add the LCP Channels / Personalities: Select / De-select the Auto Roam option accordingly (for the LCP demo system, the first LCP channel / personality has this option selected so the radio will roam automatically between the two sites). Select the Site List which defines all LCP sites on which the radio is required to operate for that LCP personality. Configure the Rest Channel Acquisition TOT and Beacon Interval (as per Capacity Plus) and ensure that the Beacon Interval is consistent with the repeater configurations. Configure the Contact name (as per Capacity Plus). For the LCP demo system the Power Level needs to be set to Low to minimise interference and help demonstrate roaming.

Radio Configuration – Buttons Define the radio Button configurations: Site Alias displays the current LCP Site details (note: by default, radio displays LCP Channel / Personality) Sit Lock On/Off allows the user to lock the radio onto the current site and prevent it from scanning for a different site. Manual Site Roam allows the user to initiate an Active Site Search.

MOTOTRBOTM LINKED CAPACITY PLUS Training Roadshow.

Similar presentations

Presentation on theme: "MOTOTRBOTM LINKED CAPACITY PLUS Training Roadshow."— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

MOTOTRBOTM LINKED CAPACITY PLUS Training Roadshow.

Similar presentations

Presentation on theme: "MOTOTRBOTM LINKED CAPACITY PLUS Training Roadshow."— Presentation transcript:

Similar presentations

About project

Feedback