EB/TA

 

New Application to Application Requirements

 

When migrating to the app to app interface from the GUI or bringing up a customer’s initial connection  to EB/TA via the app to app, it is imperative that the testing phases below take place:

 

  1. Stack-To-Stack Test
  2. Gateway-to-Gateway test
  3. End-to-End Testing
  4. Network Validation Test
  5. Operational Readiness Test  

 

 

Stack-to-Stack and Gateway-to-Gateway Testing Requirements

Back to Top

  1. IP address information for test, production and failover machines must be exchanged and added to both companies firewall configuration.
  2. Insure that a route exists between AT&T and bonded partner gateways.
  3. Insure that a route exists (in the bonded partner’s network) to the AT&T gateways.
  4. Identify the number of CMIP associations required by the bonded partner.

1.    If multiple CMIP associations are required for logical business units, then each association will require separate Entity Identifiers, key files, etc. 

2.    Each connection will require its own stack-to-stack and gateway-to-gateway connectivity test.

  1. NOTE: AT&T will not engage in Unit Testing with the bonded partner, nor can AT&T’s test machines be used as “agent simulators” by the bonded partner.

 

 

End-to-End Testing Requirements

Back to Top

  1. Signed JIA between AT&T and bonded partner
  2. Test specifications must be agreed to by AT&T and bonded partner
  3. Test data must be exchanged and configured in AT&T and bonded partner legacy systems
  4. Testing schedule and bridge information must be exchanged between AT&T and bonded partner.
  5. Bonded partner gateway must support connection auto retry function
  6. Bonded partner must have an inactivity timeout procedure in place.  This prevents the TCP/IP connection from timing-out.

1.    Generally this procedure will take the form of a GET transaction on a Trouble Ticket Number that does not exist (for example LST0000000).  The bonded partner will not be allowed to send more than one keep-alive transaction every 50 minutes.  This means that the bonded partner will need to have a firewall timeout value over 50 minutes—preferably 60 minutes or more.

 

NVT Testing Requirements

Back to Top

  1. Production IP addresses for AT&T and bonded partner must be allowed through the appropriate Firewalls.
  2. Routes must be established within AT&T and the bonded partner to connect the                                    partner’s production gateway and any failover gateway(s) to tsp8012a.AT&T.com (155.179.124.83).
  3. Connectivity cannot be verified with either “trace route” or “ping” as both of these utilities make use of the Internet Control Message Protocol (ICMP) which is not allowed across AT&T’s firewall.  Connectivity testing can only be accomplished by telnet’ing to port 102 on the above IP address with AT&T on the line to verify the test results.
  4. NVT testing will be complete when the bonded partner brings up an association on the production AT&T Gateway (tsp8012a.AT&T.com)

 

Operational Readiness Testing

Back to Top

  1. Pre-production conference call at least 30 days prior to going live (this does not guarantee going live in 30 days -- during the call production dates must be negotiated with AT&T and bonded partner)
  2. Full ORT required (Creates, Sets, Events must be tested)
  3. Customer must have a 7x24 contact for application problems and either a single point of contact for their application or a hotline/pager number and an email address for questions and system notifications