Inter Application Communication  MTELpage 2013

Focus

This instruction describes the MTELpage communication to all other MTEL products in the latest 2013 release of MTELPage.

MTELPage to MDS Operation

The primary paging path is from MTELPage to MDS. MTELPage connects on a state wide basis to a single MTERelays located in all the Comm Centres. The MTELRelays communicate to a single PagerDEC application. PagerDEC delivers the messages to the MDS.

The MDS is duplicated in QEOC and Springhill. MTELRelays can switch to either system via a DNS alias record.

mterelay would close then restart on the alias

mention only talk to one or other

mtel configured using to send packets

changed current to regional

change workstation to server

show one line dotted

prefer qeoc

The Off Air Decoder path uses the reverse direction to send decoded messages back to the Comm Centres.

Filtered messages oad back to regions

The following diagram shows the packet flow from MTELPage to PagerDEC for a normal message packet.

expain packets names

MTELPage operation on a MDS failure

The primary paging path is from MTELPage to MDS. If this link fails then the message is rerouted from MTELPage back to the local servers. The failure can be temporary or even pager based. There are several databases in use and it is possible for these to be out of sync. The local comm centre database is considered to be the most accurate so if the MDS does not have the pager in its database it sends a USERNOTINBASE flag back to MTELPage. MTELPage then redirects the message out the local MTELServers.

The following diagram shows the packet flow from MTELPage to PagerDEC to MTELServe when there is a PagerDEC failure

[ Home ] [ Up ]  
Copyright © 2012-2021 MTEL Communications Pty Ltd
Last modified: 01-Jun-2022