|
|
|
|
MTELRelay (Client/Server)
This instruction is specific to the MTELRelay 2015 client/server application. This application distributes decoded pager data from the Hutchison "3 Paging" network from the PagerDEC server. The data is not transformed in any way it is simply relayed to the clients. It is capable of sending pager messages in the reverse direction to PagerDEC from MTELPage. It now includes the DIRECT Host connection for WBB picocells and the user acknowledgement data.
MTELRelay will only work with PagerDEC V4.1(69) and above. MTELPage 4.1 (421) is the minimum revision to receive all the relay messages and user acknowledgement. The configuration file is MTELRelaysys.mdb
The MTELRelay application distributes decoded pager data from PagerDEC to the MTELPage products for message acknowledgement. The distribution is via dedicated TCP sockets. The relay simply takes messages from the PagerDEC server and forwards the packets in a one to many relationship to all connected MTELPage clients. The messages are delivered by TCP onto the MTELPage client window. This technique provides fastest possible delivery for message acknowledgement. The time it takes from the decoder to MTELPage is typically less than a few seconds. In addition to this instantaneous delivery the messages are stored in to the standard MTELPage history files. MTELPage can then access these messages via the standard history lists. These lists can be viewed by the user Each relay application normally handles traffic for one DCS communications centre. The relay resides on the MTELPage server. It does this so the connection to the decoded data is located in a local database in the MTELPage suite. However as all applications communicate via the NETWORK the relay could reside anywhere on the network.
1.3 Setting up the MTELRelay application system tablesThe MTELRelaysys.mdb is the configuration file for the application and must reside in the current directory. The relay has only this working file which is an Access database configuration file. There are 4 tables in the database, StartUp, Outputs, MTELPage, and ErrorCodes. Outputs table This is the connection to the PagerDEC configuration. The table can contain information for one or more TCP connections. However only one should be active at any time. This Port in the Outputs table should match the Port in the PagerDEC configuration MTELRelay table in MTELPDecsys.mdb which the relay is connecting to. Ideally the description should match the connection with PagerDEC. i.e. this table should indicate connecting to the Primary PDEC on MDS as an example. The description in PagerDEC should reflect this relay application name. In the case below the output in the MTELRelay was called PDEC_MDS_PRI operating on port 7031. In PagerDEC the listener was labelled Test and is Y for active and port is 7031. Note also the Region is set to "*" (see PagerDEC) which is send all decoded messages to Test. So the MTELRelay receives all the messages. In a normal service only messages for that region will be sent to the MTELRelay
The Description field is not active in the program it is just for documentation. Active is Y or N (Y is active all other entries are treated as N). Address and Port are the TCP connection to PagerDEC. PagerDEC operates as a server and the relay as a client automatically connects to PagerDEC. If the link fails the relay will continue to retry the TCP connection forever. One consequence of this is the logs will be filled unnecessarily. If ports are not in use they should be disabled. MTELpage table This is the MTELPage Clients configuration. All MTELPage applications act as a clients. They connect to the relay which acts as a server. The table can contain information for one or more TCP connections. The connections can be all active or all disabled. The Relay does not monitor the connections, it is up to the MTELpage clients to connect to the relay. One consequence of this is the logs will be filled unnecessarily. If ports are not in use they should be disabled.
ErrorCodes table This is error code configuration for the application. It has no real value for the user or installer. It is a simple way to store standard errors for this application.
StartUp table BackUpPeriod is the number of hours between backups of the log files. BackUpTime provides a time to begin a backup. In the case below it is 5 am every day. Critical settings are FServer. This is the file server for the MTELpage directory, normally c:\pager on the current server. LogName is the name of the log for the relay. LogsDIR can be anywhere. OADLog is the location of the MTELPage history database. Normally it is in the MTELPage file structure such that the full file location is FServer & OADLog in the example below it is c:\base\pager and the string \logs\mtelmess.mdb to give c:\base\pager\logs\mtelmess.mdb ServerID is the name in the banner of the application for easy identification in the task bar.
|
|
|
