Primary Route: Successful message
	
		MTELPage sends a message to the MDS system in 
	Brisbane. For priority messages this takes about 2-3 seconds.
		MDS sends the message to the MTELGateway. This takes 
	about 2 seconds.
		MTELGateway sends the message to the WBB Pico. This 
	takes 0.5 seconds.
		The WBB queues the message and sends an ACK back to 
	the MTELGateway. About 0.5 seconds.
		The MTELGateway then sends an ACK back to the MDS. 
	About 0.5 seconds.
		The MDS sends the ACK back to MTELPage. About 2 
	seconds.
		All up about 10 seconds.
	
	 
	
		
			
				
				 
				 
			
		
		There is a log of these events readily available 
		for last few messages. Go to the menu and select Show Relay Log. A 
		separate window will pop up and display the communication between 
		MTELPage and the MDS.
		
			
				
				 
			
		
		An example of the log is shown below.
		
			
				17/03/14 15:31:24 c0215270120189 RESP: Strip 
				Response String-> 15:27:01 CREATED 15:31:10 INPUTQ 15:31:10 
				PORTASSIG 15:31:13 BUSY 17/03/14 15:31:24 c0215270120189 ELog: 
				15:27:01 CREATED
				17/03/14 15:31:24 c0215270120189 ELog: 15:31:10 INPUTQ
				17/03/14 15:31:24 c0215270120189 ELog: 15:31:10 PORTASSIG
				17/03/14 15:31:24 c0215270120189 ELog: 15:31:13 BUSY
				17/03/14 15:31:24 c0215270120189 ELog: 15:31:15 SMSSTX
				17/03/14 15:31:24 c0215270120189 ELog: 15:31:16 SMSACC
				17/03/14 15:31:24 c0215270120189 ELog: 15:31:18 MESSDELETED
				17/03/14 15:31:24 c0215270120189 ELog: 15:31:20 DONE
				17/03/14 15:31:24 c0215270120189 RESP: Updated history.
				17/03/14 15:31:28 c0215270120190 RESP: Strip Response String-> 
				15:27:02 CREATED 15:31:23 INPUTQ 15:31:23 USERNOTINBASE 15:31:24 
				DONE
				17/03/14 15:31:28 c0215270120190 ELog: 15:27:02 CREATED
				17/03/14 15:31:28 c0215270120190 ELog: 15:31:23 INPUTQ
				17/03/14 15:31:28 c0215270120190 ELog: 15:31:23 USERNOTINBASE
				17/03/14 15:31:28 c0215270120190 system: User not in MDS 
				database. Redirect to MTELQue
				17/03/14 15:31:28 c0215270120190 RESP: Updated history.
				17/03/14 15:31:34 c0215270020188 RESP: Strip Response String-> 
				15:31:30 SWITCH_NO_RESP
				17/03/14 15:31:34 c0215270020188 ELog: 15:31:30 SWITCH_NO_RESP
				17/03/14 15:31:34 c0215270020188 system: No response from MDS. 
				Redirect to MTELQue
				17/03/14 15:31:34 c0215270020188 RESP: Updated history.
 
			
		
	
	 
	Primary Route: Picocell is not available on the 
	WBB network.
	
		There are times when the picocell is not 
		available. These are when the communications module in the picocell are 
		reset on a daily basis and when Telstra performs maintenance in the 
		local communications sites. This downtime has been reduced to a minimum 
		of around 1 minute per day.
		Picocell messages are never stored in this case. 
		It is preferable that the emergency service user knows that the message 
		was undeliverable rather than delay it. In this way the user can make 
		alternative plans or chose to resend the message.
		It the picocell is inoperable the following 
		sequence of events occurs.
	
	 
	
		
			MTELPage sends a message to the MDS system in 
	Brisbane. For priority messages this takes about 2-3 seconds.
			MDS sends the message to the MTELGateway. This takes 
	about 2 seconds.
			MTELGateway determines the picocell is not 
	available.
			The MTELGateway then sends an FAILURE back to the 
	MDS. About 0.5 seconds.
			The MTELGateway also sends an email message 
			to the designated region Comms centre.
			The MDS sends the FAILURE back to MTELPage. About 2 
	seconds.
			All up about 6 seconds.
		
	
	 
	
		
			
				