Liaison Checklist for Common Use Sites

CUTE/MUSE/RESA/CUS RESPONSIBILITIES 1. Confirm Atlanta routers have been configured to allow access of the customer IP addresses by issuing command PING 57.5.64.250 from a MS-DOS command prompt. Router access is enabled by the airline SITA account manager forwarding a copy of the SRFII form to ATLDC.Systems.Support.Operations.Center@sita.aero, copy to Liaison.Support@sita.aero. Registered IP addresses must be presented to the Atlanta router. NAT is OK. While subsequent steps through Liaison configuration can be complete before the router config is complete, it is important to pursue this step early to avoid implementation delays. 2. Download the latest certified version of Liaison, Liaison User Guide and the Group Management Tools document from the CUTE administrator web site. 3. Obtain the airlines Liaison registration key from liaison.support@sita.aero. A CUTE registration key differs from the airlines desktop (standalone) key, so you should check with Liaison support, not the airline, for the key. 4. If Static or Pooled PIDs are to be used, obtain PID numbers from the airline. Liaison handles CRT traffic and printer traffic through the same PID. Liaison can use 3 different PID types: Static PID Requires 1 PID per workstation. Pooled PID Static PIDs are configured through the WSCONFIG.EXE program to be shared at the site on a first come first serve basis. Dynamic PID PIDs are assigned dynamically by the host as needed. An initial setup is required per airline. No subsequent setup is required on the host side to deploy additional dynamic PIDs. If dynamic PIDs are to be used, confirm with ATLDC.Systems.Support.Operations.Center@sita.aero that the airline has been configured for dynamic PID usage. A document further describing PIDs can be obtained from the Liaison intranet web site, 57.5.64.254, or internet web site, 57.250.224.47. 5. The following information will also be required from the airline for configuration and testing: Pectab formats to be used (not actual pectabs) Logos 3 numeric airline code User ID/password Signin

6. Install Liaison. See instructions in the Liaison User Guide, section 3.5 SITA CUTE installations for specific instructions. 7. Configure Liaison. Reference both the Group Management Tools document and the Liaison User Guide for assistance. If you require assistance from Liaison support, we will need a site survey including the names of each workstation and the type of equipment attached to each workstation. 8. Test each type of workstation. Enter the User ID/password provided by the airline at the ENTER USER ID/PASSWORD prompt. The default transmit key is the Scroll Lock key. Then enter the Signin provided by the airline. At that point, enlist the airlines assistance to test the peripheral devices. 9. If the ENTER USER ID/PASSWORD prompt is redisplayed each time you transmit a valid user id/pw, the problem could stem from several things. Rendezvous (the server in Atlanta accepting TCP/IP traffic) must be configured to accept traffic from this airline. If this is the first time the airline has Liaison IP traffic into Atlanta, this may not be complete. Contact ATLDC.Systems.Support.Operations.Center@sita.aero to confirm. When Rendezvous is configured, the airline is associated with one of the host systems, PSA or PSB. It could also be that Rendezvous was configured to send traffic to the wrong host. Again, ATLDC can confirm to which host traffic is directed. AIRLINE RESPONSIBILITIES 1. Does the airline have a Liaison contract? If so, does the number of licenses stated in the contract cover installation at this site? Additional Liaison licenses can be ordered via the Liaison-More Copies document. Obtain this document from Liaison.support@sita.aero. 2. Provide the CUTE site administrator with the type of PIDs to be used. If static/pooled PIDs are used, it is the airline responsibility to request them and to ensure they are properly configured for the site. I.E. City/Office, pectabs, Protected, etc. PIDs can be requested from configs.technical.services@sita.aero. A document describing PIDs can be downloaded from the Liaison web site at 57.250.224.47. 3. Provide the CUTE site administrator with a User ID/password for testing. An airline Terminal Security Administrator is responsible for this. If you do not know who within your airline is a Terminal Security Administrator, contact terminal.security@sita.aero and they can advise. 4. Advise the CUTE site administrator what pectabs that will be used.

5. Provide the CUTE site administrator with the logos that will be used. 6. Advise the CUTE site administrator of your airlines 3 numeric airline code, along with the 2 character airline code.