|
|
|
|
Welcome to the DIRECT Host support site. The purpose of this site is to provide two types of support. The first is documentation and the second is product downloads with a version list of known bugs and fixes. OverviewThe DIRECT Host provides three main functions. The first is the transfer of messages from each MTELRelay in the Comms Centre into two queues to MTEL for processing into the MTEL WBB picocell network. The second is to transfer messages from VisiCAD via MDS and the OPC. The third is to send the user acknowledgement notifications back to MTELPage via the MTELRelay. The DIRECT Host like many other MTEL applications contains tabs of information relating to the functionality. The DIRECT Host has the MTELRelays tab which contains all the connection configuration to the MTELRelay's in each QFES Comms Centre. The second tab is the Outputs tab. It contains the configuration of the two ports for the connection to the wireless hardware connections to MTEL Connect Servers. The third tab is the System Logs. The forth tab is the general application Configuration The fifth tab is the Status tab where the flow of information in and out of the application can be viewed in on place. The last tab is the PETLL which is the log of the PET traffic from the leased line OPC. The diagram below shows the DIRECT Host on the MTELRelay tab. The grid holds the configuration of each MTELRelay and can be edited from the application. MTELRelay tabThis tab contains all the MTELRelay clients in the Comms centre. Each socket is a listener ports and MTELRelay is the client. MTELRelay will make a permanent connection to the DIRECT Host when enabled in the MTELRelay. MTELRelay clients can be enabled by the Active field. The description field is used for logging purposes only. The clients can be in any order, the list is sorted alphabetically. If adding new clients shutdown the application and restart it immediately after the edit. At the bottom of the tab is the log showing communication from MTELRelay clients and replies from the DIRECT Host back to MTELRelay. All messages requests are acknowledged or an error packet is sent back. The RQST packet is sent from MTELRelay and the second field is the message ID. The reply from DIRECT Host is the RRPYOK indicating the message has been received successfully as shown in the diagram below.
The current maximum number of MTELRelay clients 20. The table below is and example of the grid table in the configuration table.
Outputs tabThis tab contains the socket information for the wireless hardware. In the Queue they are clients and will automatically connect to the MTELServer's as the applications are started. The devices can be enabled by the Active field. The description field is used for logging purposes only. The clients can be in any order, the list is sorted alphabetically. At present only one output can be active at any time with the current hardware. Multiple entries can exist but must be marked inactive. At the bottom of the tab is the log showing communication from Outputs to MTELConnect which is the MTEL server side of the wireless hardware devices. The log indicates requests and responses going to and coming back from the WBB Gateway. The current maximum number of Outputs clients is 2.
System Logs tabThis tab contains the log for general system messages and errors.
Config tabThis tab contains the general configuration for the application. The configuration is stored in a Microsoft Access database called MTELRelaysys.mdb and it resides in the current directory of the application. There are several tables in this file. Outputs table is the configuration grid of the MTELServe tab. MTELPage table is the configuration grid of the MTELPage tab. The configuration for the application is in the StartUp table.
The entries are explained in the description field. BackUpPeriod is hours between backups. LastBackUp is updated by the application. LogName is the name of the log file in the LogsDIR directory. MTELRelayIP this is the local IP which the MTELRelay sockets are bound to. ServerID this is the name of the application in the banner PETLLPort is the port for the OPC leased Line to connect to PETOPCID is a three letter name to identify the port for the incoming messages
PETLL tabThis tab contains the log of the PET leased line traffic from VisiCAD. The MDS has a port class of PETWBB and messages with this port class are sent via the OPC running in leased line PET mode. The OPC sends a watchdog message every 5 minutes. All messages from the PETLL are ACKed if the connection to MConnect exists. If the connection breaks the input to the PET connection is closed until the link is re-established. Future versions of the OPC will have the ability to diagnose and send more meaningful messages back for the PETLL port.
OperationThis diagram below shows the connections from a single MTELRelay through to the MTEL WBB Gateways. The MTELRelay normally sends messages from the first output in the list. If this is faulty the second port is then selected. If both ports are inactive the message is cancelled by MTELPage and is reissued and sent via MTELQue to the local PSTN system. VisiCAD sends messages to MTEL through the PETLL ports in the same manner as messages sent to other leased line products in the MDS system. If the DIRECT Host hardware is inactive messages are re-routed internally within the MDS system and eventually enter the MTEL system via the dial up service. The outputs from the DIRECT Host can be manually selected to connect to the Lantronix hardware. The hardware doesn't have multiple socket connectivity. The Lantronix to Intelimax serial port is limited to 9600 baud. The Intelimax operates as a client with fallback facility and connects to the MConnect servers. It has two server ports in which to connect to in a cyclic manner and can therefore connect to either MConnect servers. The WBB Gateway has two servers which alternate in operation each day. The inactive system ignores messages from MConnect so that only one set of messages is generated. When a message is generated and sent through the various applications a temporary list of the path taken is stored in each application so that the responses to the message can be rerouted back to MTELPage.
|
|
|
