ifd_fax_v2_10_5
TRANSCRIPT
-
7/28/2019 IFD_FAX_v2_10_5
1/18
-
7/28/2019 IFD_FAX_v2_10_5
2/18
A4-IFD-003076-4 Facsimile User InterfaceIssue 2.10 - Accepted27 Oct 2000
The contents of this document are proprietary to HNS Limited and cannot be disclosed,duplicated, reproduced or used in part or in whole for any purpose other than in connec-tion with the associated binding contract between HNS Limited and the recipient. Thisrestriction does not apply to information in this document if it is obtainable from another
source without breach of this notice.
APPROVAL SIGNATURES
NAME : SIGNATURE :
JOBTITLE : DATE :
NAME : SIGNATURE :
JOBTITLE : DATE :
DISTRIBUTION LIST
Document Source: TCM TEAM: DOC, TCM LIBRARY: [IFD], TCM VERSION: IFD_FAX_V2.9
To generate document: @ifd_Fax
[ifd_fax.mss]
-
7/28/2019 IFD_FAX_v2_10_5
3/18
Facsimile User Interface A4-IFD-003076-4Issue 2.10 - Accepted
27 Oct 2000
References
1. System ManualIdentity: A4-OMM-003076 Issue: V3.1
2. CCITT RecommendationIdentity: T(30) Issue: (Blue Book)
3. Inmarsat-C System Definition ManualIdentity: Issue: 1.3.1 Plus CNs 92-98
4. Satellite User Interface DefinitionIdentity: A4-IFD-003076-5 Issue: V3.1
5. Inmarsat-C LES Operator GuideIdentity: A4-OPG-003076 Issue: V3.23
-
7/28/2019 IFD_FAX_v2_10_5
4/18
A4-IFD-003076-4 Facsimile User InterfaceIssue 2.10 - Accepted27 Oct 2000
Glossary
ACSE Access, Control and Signalling Equipment
ASCII American Standard Code for Information Interchange. Standard alpha-numericcharacter set, also known as IA5.
AORE Atlantic Ocean Region - East
AORW Atlantic Ocean Region - West
CCITT Comite Consultatif International Telegraphique et Telephonique. Publishes stan-dards and recommendations for telecommunications systems.
CSID Calling Station Identity
CSI Called subscriber identity
CSPR Customer Service Problem Report
DTMF Dual tone multifrequency
HNS Hughes Network Systems
IA5 International Alphabet 5. Standard alpha-numeric character set, also known asASCII.
IOR Indian Ocean Region
LES Land Earth Station
NDN Non Delivery Notification
PDN Positive Delivery Notification
PIN Personal Identification Number
POR Pacific Ocean Region
PC Personal Computer
PSTN Public switched telephone network
SAC Special access code
SDI Service definable identifier
TSI Transmitting subscriber identity
Zetafax Trademark of the Fax software package used in the LES facsimile interface.
-
7/28/2019 IFD_FAX_v2_10_5
5/18
Facsimile User Interface A4-IFD-003076-4Issue 2.10 - Accepted
27 Oct 2000
REVISION HISTORY
Issue Date Status Author Change References
1.0A 04-Oct-1991 Draft K Fenwick
1.0B 22-Oct-1991 Draft K Fenwick
1.0 21-Jan-1992 Accepted K Fenwick Incorporate review comments
2.0a 01-Sep-1992 Draft K Fenwick Revisions to header format
2.0b 02-Sep-1992 Draft K Fenwick Further corrections
2.0c 08-Sep-1992 Draft K Fenwick NDN format correctedFailure reasons expanded.
2.0 20-Aug-1993 Accepted J Barber Further changes in format documentissued to match 72000 release.
2.1A 01-Nov-1993 Pre QC J Barber SPR20466
2.1B 15-Nov-1993 Follow up J Barber Incorporate review comments
2.1 23-Nov-1993 Accepted J Barber Final checks complete, for R72040
2.2 15-Apr-1994 Accepted M Hart New Fax Driver in Releases 72060,7017, SPR 21428
2.3A 16-Jun-1994 Draft M Hart Fax header changes
2.3B 1-Aug-1994 Pre QC J Barber New customer, SCR 324, SPR 21726
2.3 20-Sep-1994 Accepted J Barber Incorporate review comments,SCR 304, SPR 22100Matches Release 73000
2.4A 29-Jan-1995 For Review M Butcher SPR 20359,22228,22472,22509and 22615. Format Improvement &Correction of Scribe macros.
2.4 21-Feb-1995 Accepted M Butcher After Review
2.5A 24-Apr-1995 For Review M Butcher New Fax Customer and minor editorialcorrections.
2.5B 24-Apr-1995 For Review M Butcher Review Comments Included
2.5 04-May-1995 Accepted M Butcher After final review
-
7/28/2019 IFD_FAX_v2_10_5
6/18
A4-IFD-003076-4 Facsimile User InterfaceIssue 2.10 - Accepted27 Oct 2000
REVISION HISTORY - continued
2.6A 31-Oct-1995 For Review A Chisholm Updated abnormal line
conditions, SCR385, SPR24160
2.6 22-Nov-1995 Accepted A Chisholm After Review
2.7A 8-Jan-1997 For Review A Chisholm Introducing FAX to CATSPR24440
2.7 28-Jan-1997 Accepted A Chisholm Incorporating review comments
2.8A 25-Mar-1997 For Review A Chisholm GSOR, SCR 414
2.8 9-Apr-1997 Accepted A Chisholm Incorporating review comments
2.9A 30-Apr-1997 For Review A Chisholm IMR1, SCR 555
2.9 21-May-1997 Accepted A Chisholm After Review
2.10a 18-Oct-2000 For Review M.J.Williams Millennium change - removal ofDate/Time from ZF banner SPR26049
2.10 27-Oct-2000 Accepted M.J.Williams Accepted - Review comments
Telstra name change
Change bars highlight changes made since Issue V2.6 of this document
-
7/28/2019 IFD_FAX_v2_10_5
7/18
A4-IFD-003076-4 Facsimile User InterfaceIssue 2.10 - Accepted27 Oct 2000
Reporting Issues with this Document
Any errors or omissions found in this document should be reported to HNS by means of a
Customer Service Problem Report (CSPR). This method may also be used to raise any sugges-tions for future releases. The procedure for raising an CSPR is explained in Appendix F of theSystem Operator Console Operator Guide reference [5].
-
7/28/2019 IFD_FAX_v2_10_5
8/18
Facsimile User Interface A4-IFD-003076-4Issue 2.10 - Accepted
27 Oct 2000
-
7/28/2019 IFD_FAX_v2_10_5
9/18
A4-IFD-003076-4 Facsimile User InterfaceIssue 2.10 - Accepted27 Oct 2000
i
Table of Contents
Reporting Issues with this Document . . . . . . . . . . . . . . . . . . . . . . .
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
2. Handling Facsimile Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2.1. Access to the PSTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12.2. Address from Mobiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12.3. Address Information to PSTN . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12.4. Message Completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12.5. Delivery Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
3. Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.1. Page Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.2. Format of Delivered Facsimile . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13.2.1. Format of Front Page Header . . . . . . . . . . . . . . . . . . . . . . . 3-23.2.2. Format of Delivery Notification . . . . . . . . . . . . . . . . . . . . . . 3-2
-
7/28/2019 IFD_FAX_v2_10_5
10/18
A4-IFD-003076-4 Facsimile User InterfaceIssue 2.10 - Accepted27 Oct 2000
1
List of Figures
3-1 Format of Front Page Header . . . . . . . . . . . . . . . . . . . . . . . 3-3
3-2 Format of Delivery Notification . . . . . . . . . . . . . . . . . . . . . . . 3-4
-
7/28/2019 IFD_FAX_v2_10_5
11/18
A4-IFD-003076-4 Facsimile User InterfaceIssue 2.10 - Accepted27 Oct 2000
1-1
Chapter 1
Introduction
This document defines how messages are delivered by the ACSE over the Public SwitchedTelephone Network (PSTN) in the form of facsimile transmissions.
The facsimile interface is available only for mobile to shore messages. It is not possible to carrymessages in the opposite direction since the satellite link is only suitable for character transmis-sion due to its limited speed.
The methods of addressing from the mobile and routing to the facsimile interface are defined inthe System Manual, Reference 1. This document therefore concentrates on the format of thefacsimile transmissions.
It is also possible to deliver delivery notifications to registered users by facsimile.
This interface handles Group 3 facsimile only, see reference 2.
-
7/28/2019 IFD_FAX_v2_10_5
12/18
Facsimile User Interface A4-IFD-003076-4Issue 2.10 - Accepted
27 Oct 2000
1-2
-
7/28/2019 IFD_FAX_v2_10_5
13/18
A4-IFD-003076-4 Facsimile User InterfaceIssue 2.10 - Accepted27 Oct 2000
2-1
Chapter 2
Handling Facsimile Messages
2.1 Access to the PSTN
The ACSE supports facsimile transmission via third party software which runs on one or morePCs, which are configured to include Fax modem cards.
The ACSE passes fax messages to a Fax PC associated with the appropriate outgoing route. It isthen the responsibility of the Fax PC software to transmit the fax and inform the ACSE of theeventual delivery status.
The normal minimum equipment provision is two PCs, each supporting up to four PSTN lines. Thisis to provide protection against failure.
2.2 Address from Mobiles
Messages are received from mobiles in the same way as for other terrestrial interfaces but withthe :
destination network set to PSTN
address extension field set to T30
The destination address as received from the mobile is in the form of :
country code + national number
If the country country code is less than 3 digits, then the mobile makes the field up to 3 digits withleading 0s.
Messages from mobiles must be in IA5 code.
2.3 Address Information to PSTN
The address information to the PSTN can be in one of the following forms :
local number
national number, including 0 prefix
international number, including 00 prefix
The ACSE will perform the necessary translation between the address received from the mobileand the address passed to the PSTN.
2.4 Message Completion
Message delivery is ultimately the responsibility of the Fax PC software. The final delivery status
being reported back from the Fax PC software to the Fax driver in the ACSE. The message is thenmarked as delivered or non-delivered, as appropriate, in the ACSE.
If message delivery is initially unsuccessful, perhaps because the dialled number is engaged, then
-
7/28/2019 IFD_FAX_v2_10_5
14/18
Facsimile User Interface A4-IFD-003076-4Issue 2.10 - Accepted
27 Oct 2000
2-2
the Fax PC software will retry the transmission after a retry interval and will make a number ofretry attempts. If the call is still unsuccessful after the retry attempts then the Fax PC will return anon-delivery status to the ACSE. Note that, by default, the retry interval is 5 minutes and there area maximum of 5 retry attempts. However these values can be modified by the ACSE operator from
the Fax PC.
The following abnormal line conditions will be detected and reported to the ACSE :
OCC FAX Number Busy - busy tone received on PSTN line.
NP FAX No Reply - No answer from dialled number.
LPE FAX No Dial Tone - No dial tone detected by the fax modem when a call attemptwas made. This indicates either a failure in the exchange or the connection to theexchange.
RPE FAX Invalid Response - An incorrect response was received from the diallednumber, i.e. Call answered but not by a valid fax machine. This covers answer byhuman, other machine (i.e. modem) or faulty fax machine.
BK FAX Transmission Error - Unable to deliver message due to a communicationserror occurring during transmission of the message, e.g. call cut off.
The administration should make arrangements to handle cases where delivery of the facsimile isincomplete, i.e. where the recipient has enough information to know that the message wasdelivered via the LES but has not received all of the message or one or more pages have becomecorrupted.
2.5 Delivery Notification
Delivery Notifications, both Non Delivery Notificationsand Positive Delivery Notifications, can bedelivered by facsimile for registered users. For delivery the appropriate PSTN address must beentered in the LESs Registered User database and the service is enabled for the user of the PINwho sent the original message. This address should be in the form in which it is received by theACSE, i.e.
Country code + National number
This will be translated by the ACSE in the same way as addresses received from mobiles.
-
7/28/2019 IFD_FAX_v2_10_5
15/18
A4-IFD-003076-4 Facsimile User InterfaceIssue 2.10 - Accepted27 Oct 2000
3-1
Chapter 3
Message Format
The delivered facsimile will consist one or more pages of text containing the message as receivedfrom the mobile. A section of the front page will identify the origin and destination of the messageand provide other details.
The header and the text portion of all pages will conform to CCITT Recommendation T30.
3.1 Page Header
At the top of each page there is a header containing the following :
ZF: a small zetafax logo.
PH : a small icon representing a telephone handset
CSID: Calling Station Identifier. This is set by the operator in the Zetafax startup filei.e. c:\Zetafax\System\z-db\Setup.ini section FClass-: (where n is 1-4) and fieldPhoneNum: . A value should be set for each modem installedand does NOT need to be unique or the number of the PSTN line used by theModem. It will normally contain a voice telephone contact number for the LES faxinterface. This number is not only printed in the fax header but is also exchanged aspart of the fax protocol with the remote fax machine. It can be used to identify thecalling station (e.g. the LES).
SDI : Service Definable Identifier. Set by the operator and contains up to 30 charac-ters. This is used to identify that the message has been handled by the ACSE. Thisfield also acts to identify the licencee of the Zetafax software and any change to theSDI will also involve a change to the licence on the FAX PC.
TSI : Transmitting Subscriber Identity. In this case the identity of the originator of themessage i.e. the mobile number.
->: a small arrow indicating that the call is in the direction TSI to CSI
CSI : Called Subscriber Identity. The number addressed over the PSTN, in the sameformat as received from the mobile, i.e. country code + national number, without any
spaces.
Page number/Total Pages : the page of the fax and the total number of pages, start-ing at 1/1.
Each of the above fields are separated by spaces and is in a different font from the message text.
3.2 Format of Delivered Facsimile
Two separate formats are identified :
For mobile to shore originated messages, including distress messages, distress alerts
and land mobile alerts, the format consists of a header, as illustrated in Figure 3-1 ,and text which starts on the front page below the header and continues on as manypages as necessary.
-
7/28/2019 IFD_FAX_v2_10_5
16/18
Facsimile User Interface A4-IFD-003076-4Issue 2.10 - Accepted
27 Oct 2000
3-2
For delivery notifications, the fax will consist of one page which will identify therecipient of the delivery notification as the destination address and will omit the mobileaddress and ocean region fields. The format is shown in Figure 3-2.
The format of the content of distress messages, distress alerts and land mobile alerts is specifiedin the Satellite Driver Interface specification, reference 4.
Pages containing only text will consist of up to 66 lines of text, each of up to 80 characters. Thefront page will contain as many lines as will fit in to the same boundaries after the identifier hasbeen inserted.
Where the mobile has not inserted carriage returns before the 80th character, these will be in-serted by the Fax software at the last space before. If there is a string of more than 40 charactersat the end of a line, a carriage return will be forced at the 80th character.
The Fax software only accepts printable ASCII characters, plus the following control characters :
3.2.1 Format of Front Page Header
Figure 3-1 shows the placing of the fields in the front page header; the typeface used is SansSerif.
If any field has no contents, the corresponding descriptor is not printed. If there is an entry in theSACfield, there must also be an entry in the Destinationfield.
Figure 3-1 shows the front page header format for a Facsimile addressed using a SAC. If themessage does not use a SAC then the SAC identifier and field is omitted from the header.
Note:
The Mobile No. field will have an entry 400000000 for a maritime mobile which is unregisteredwhen a distress message or alert is being sent over Facsimile, and an entry 480000000 for anon-maritime mobile which is unregistered when a land alert is being sent over Facsimile.
3.2.2 Format of Delivery Notification
Figure 3-2 shows the format of a delivery notification. The format is the same whether it is an
NDN or a PDN.
Note: The ORIGINATOR field will be set to the telex answerback if the original call came from thetelex network. If the answerback has a preceding , then these characters will appear asquestion marks (?) in the ORIGINATOR field.
-
7/28/2019 IFD_FAX_v2_10_5
17/18
A4-IFD-003076-4 Facsimile User InterfaceIssue 2.10 - Accepted Interface Definition27 Oct 2000 Table of Contents
3-3
ZF PH CSID SDI TSI -> CSI 1/1
TELEMEX SATRED
INMARSAT-C FACSIMILE SERVICE
Destination : national number SAC : Special access code
+ subscriber number
From (MES) : mobile number
Ocean Region : Indian Ocean Region
Date : e.g. 2 August 1994 Transmission Time: e.g. 11:34 UTC
No. of Pages : e.g. 1 (Including this page)
Msg Ref No : Message reference number
The text appears here
Figure 3-1. Format of Front Page Header
-
7/28/2019 IFD_FAX_v2_10_5
18/18
Facsimile User Interface A4-IFD-003076-4Interface Definition Issue 2.10 - AcceptedTable of Contents 27 Oct 2000
ZF PH CSID SDI TSI -> CSI 1/1
TELEMEX SATRED
INMARSAT-C FACSIMILE SERVICE
Date e.g. 20 March 1997 Time e.g. 16:25 UTC
Total Pages e.g. 1 (Including this page)
(NON-)DELIVERY NOTIFICATION FOR
MSG REF : Message Reference Numberas received by originator
ORIGINATOR : Telex Answerbackor X25 Address
DESTINATION : Mobile Addressor
Ocean Region Numberin the case of EGCs or Polls -
0 = non Inmarsat, 1 = AORE, 2 = POR, 3 = IOR, 4 = AORW
Failure Reasonor Success Indication, e.g. :
DELIVERY SUCCESSFUL or
DELIVERY FAILED - e.g. SD Satellite Call Failed
Note: The DESTINATION and REASON lines are repeated for each destination addressed(whether there was success or failure) up to a maximum of 20 addresses, eachtime preceded by a blank line.
Figure 3-2. Format of Delivery Notification