1、 TECHNICAL REPORT ATIS-1000041 TEST SUITES FOR IP NETWORK TO NETWORK INTERCONNECTION RELEASE 1.0 ATIS is the leading technical planning and standards development organization committed to the rapid development of global, market-driven standards for the information, entertainment and communications i
2、ndustry. More than 250 companies actively formulate standards in ATIS 18 Committees, covering issues including: IPTV, Service Oriented Networks, Energy Efficiency, IP-Based and Wireless Technologies, Quality of Service, and Billing and Operational Support. In addition, numerous Incubators, Focus and
3、 Exploratory Groups address emerging industry priorities including “Green”, IP Downloadable Security, Next Generation Carrier Interconnect, IPv6 and Convergence. ATIS is the North American Organizational Partner for the 3rd Generation Partnership Project (3GPP), a member and major U.S. contributor t
4、o the International Telecommunication Union (ITU) Radio and Telecommunications Sectors, and a member of the Inter-American Telecommunication Commission (CITEL). For more information, please visit . Notice of Disclaimer however, additional work will be required to develop actual test scripts based on
5、 the test scenarios, configurations and protocol suites presented. 3. It is understood that test SIP device endpoint E.164 addresses will need to be exchanged prior to testing. SIP URIs converted from TEL URI format will be used to convey the E164 addresses. (See ATIS-1000009.2006 for example URIs.)
6、 4. IPv4 is assumed unless otherwise stated. 5. The term Provider is used to generically represent all types of parties. 2 NORMATIVE REFERENCES The following standards contain provisions which, through reference in this text, constitute provisions of this ATIS Standard. At the time of publication, t
7、he editions indicated were valid. All standards are subject to revision, and parties to agreements based on this ATIS Standard are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. ATIS-1000007.2006, Generic Signaling and Control Plane S
8、ecurity Requirements for Evolving Networks.1ATIS-1000008.2006, ANSI Extensions to Q.1980.1 - The Narrowband Signaling Syntax (NSS) Syntax Definitions.1ATIS-1000009.2006, IP Network -To-Network Interface Standard for VoIP.1ATIS-1000010.2006, Support of Emergency Telecommunications Service (ETS) in IP
9、 Networks.1ATIS-1000011, ETS Packet Priority for IP NNI Interfaces - Use of Existing DiffServ Per Hop Behaviors.1ATIS-1000013.2007, Lawfully Authorized Electronic Surveillance (LAES) for Internet Access and Services.1ATIS-1000013.a.2009, Supplement to ATIS-1000013.2007, LAES for Internet Access and
10、Services.1ATIS-1000014, VoIP Network-to-Network Interface Testing Framework. 11This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005. ATIS-1000041 3 ATIS-1000017.2008, Network Interface Protocol and the Sess
11、ion Initiation Protocol (SIP) with ANSI Extensions to the Narrowband Signaling Syntax (NSS).1ATIS-1000020, ETS Packet Priority for IP NNI Interfaces - Requirements for a Separate Expedited Forwarding Mechanism.1ATIS-1000026.2008, Session/ Border Control Functions and Requirements.1ATIS-1000028.2008,
12、 IP Device (SIP for UA) to Network Interface Standard.1ATIS-1000029.2008, NGN Security Requirements.1ATIS-1000030.2008, NGN Authenticating Requirements.1ATIS-1000035.2009, NGN Identity Management (IdM) Framework. 1ATIS-1000036, NGN Operator Services Architectures and Interfaces.1ATIS-1000104.1991 (R
13、2008), Exchange-Interexchange Carrier Interfaces - Individual Channel Signaling Protocols.1ATIS-1000018, NGN Architecture.1ATIS-1000019.2007, Network to Network (NNI) Standard for Signaling User enters DTMF; the VoIP phone or media gateway generates RTP packets per 4733. Conditions to be checked: 1.
14、 Verify Provider B receives all the DTMF digits 0-9, *, and # with accurate representation of frequency, duration, and volume. 2. Verify that DTMF signals are transported via RTP across the NNI. Figure 9: DTMF Test 1 (received post answer, from the caller) ATIS-1000041 15 4.2.3.2 Verify digits (0-9
15、and * and #) received post-answer from the callee Description: Regular call session in progress; User enters DTMF; the VoIP phone or media gateway generates RTP packets per 4733. Conditions to be checked: 1. Verify Provider A receives all the DTMF digits 0-9, *, and # with accurate representation of
16、 frequency, duration, and volume. 2. Verify that DTMF signals are transported via RTP across the NNI. Figure 10: DTMF Test 2 (received post-answer, from the callee) 4.2.3.3 Verify digits (0-9 and * and #) to a network based call prompter post-answer from the callee Description: Regular call session
17、in progress; Prompter requests a DTMF indication response; User enters DTMF; the VoIP phone or media gateway generates RTP packets per 4733. Conditions to be checked: 1. Verify Provider A receives all the DTMF digits 0-9, *, and # with accurate representation of frequency, duration, and volume. 2. V
18、erify that DTMF signals are transported via RTP across the NNI. ATIS-1000041 16 Figure 11: DTMF Test 3 (network based call prompter, post answer from the callee) 4.2.3.4 Verify digits (0-9 and * and #) to a network based call prompter post-answer from the caller Description: Regular call session in
19、progress; Prompter requests a DTMF indication response; User enters DTMF; the VoIP phone or media gateway generates RTP packets per RFC 4733. Conditions to be checked: 1. Verify Provider B receives all the DTMF digits 0-9, *, and # with accurate representation of frequency, duration, and volume. 2.
20、Verify that DTMF signals are transported via RTP across the NNI. ATIS-1000041 17 Figure 12: DTMF Test 4 (network based call prompter, post answer from the caller) 4.2.4 Fax service with T.38 support For each of these application layer tests, it is assumed that the Network Layer Tests and Codec Type
21、and Configuration Tests have previously been successfully performed and completed. The following test suites for Fax service with T.38 support are included in this section: G.711 Pass-Thru Mode without Re-Negotiation G.711 Fall Back (originating media gateway does not support T.38) G.711 Fall Back (
22、from non-G.711 session) T.38 Fax Mode The description, purpose, service parameters, and references are the same for each of these tests. Description: Fax calls can be supported at the NNI via circuit emulation using G.711 pass-thru or T.38 packet transmission mode. In G.711 pass-thru mode, during a
23、fax call, an audio channel is established between the originating and terminating T.30 fax devices. The fax-tones originated from a T.30 fax device are encoded using in G.711 format and the G.711 traffic is sent across the NNI to the receiving T.30 fax device terminal. In T.38 mode, a T.38 capable f
24、ax device terminal is used to encode the fax tones into T.38 format and send the T.38 traffic across the NNI to the receiving fax device terminal, which in turn decodes the T.38 traffic format to fax tones. Signaling and fax tone exchange faults may occur during set-up (fax discrimination, transitio
25、n, capabilities negotiation). Faults during the call-phase (transmission) may affect image transmission quality due to packet loss, delay, and jitter. Gateways and customer equipment during set-up impact fax set-up success. Gateway-to-gateway tests under varying configurations for signaling and medi
26、a is ATIS-1000041 18 warranted. However, it is not feasible to test CPE terminal and gateway incompatibility and deficiencies at the NNI. Purpose: To verify the use of T.38 protocol to transport fax and the use of G.711 flow through as a fallback method. Configuration Note for Fax Endpoint: 1. The u
27、se of Echo Cancellers by the gateways when switching from an audio to a fax session can impact the set-up phase and fax image transmission and it should be turned off. 2. The use of Voice Activity Detection (VAD) features needs to be deactivated by the gateways during the fax session. Notes for T.38
28、 Fax Mode: The use of TCP and UDP to transport T.38 packets between T.38 capable gateways, servers, and devices are specified in the ITU-T T.38 recommendation. SIP is used to set up and negotiate the use of T.38 for fax transmission across the NNI. A SIP re-INVITE will close the audio channel and th
29、e gateway will switch to fax-to-relay (T.38) upon detection of a fax event, or for unsuccessful fax relay negotiation, fallback to pass-through with up-speed to G.711. An integrated access device (IAD) fax could setup a call offering only a T.38 fax relay. 1. To minimize signaling failures, the corr
30、ect SIP ReINVITE message offering the generic SDP offer for G.711 codec is needed to switch from audio to G.711 up-speed for fax tone transmission. 2. Voice Activity Detection (VAD) needs to be deactivated by the MGC for successful set-up. 3. The T.38 fax “no signal detected” failure may be caused w
31、hen no fax tone (V.21 preamble?) is detected (which are optional for T.38, but required for T.30 fax) but not always supported by all fax machines. The use of called-tone prior to the T.38 ReINVITE to ensure tone detection as required by the T.30 protocol may reduce signaling failure and should be t
32、ested. Service Parameters: N/A. References: 1. ITU-T Recommendation T.30, Fax PSTN. 2. ITU-T Recommendation T.38, Fax 3. IETF RFC 4040, RTP Payload Format for a 64 kbit/s Transparent Call, 2005-04. 4. IETF RFC 3362, Real-time Facsimile (T.38) image/t.38 MIME Sub-type Registration, 2002-08. 4.2.4.1 G
33、.711 Pass-Thru Mode without Re-Negotiation Description: Regular call session in progress using G.711 codec; Provider A or Provider B initiates fax transmission using existing G.711 circuit emulation mode to transmit fax signal. Conditions to be checked: 1. The fax document is successfully transmitte
34、d over G.711 RTP and decoded accurately on the receiving side. 2. The same G.711 media streams connected to transmit voice signals are used to transit fax tones on both directions. ATIS-1000041 19 Figure 13: G.711 Pass-Thru Mode without Re-Negotiation 4.2.4.2 G.711 Fall Back (originating media gatew
35、ay does not support T.38) Description: Regular call session in progress using non-G.711 codec; Provider B initiates fax transmission offering a T.38 connection; Provider A does not support T.38; Provider B re-invites using G.711 circuit emulation mode to transmit fax signal. Conditions to be checked
36、: 1. Verify that a Re-INVITE with T.38 is first offered and rejected before a re-Invite with G.711 offer is sent. 2. The fax document is successfully transmitted over G.711 RTP and decoded accurately on the receiving side. ATIS-1000041 20 Figure 14: G.711 Fall Back (originating media gateway does no
37、t support T.38) 4.2.4.3 G.711 Fall Back (from non-G.711 session) Description: Regular call session in progress using non-G.711 codec; Provider B does not support T.38 and initiates fax transmission offering a G.711 connection; Provider A accepts the offer and the transmission is completed using G.71
38、1. Conditions to be checked: 1. Verify that a Re-INVITE with G.711 is offered and accepted before a G.711 RTP connections is established. 2. The fax document is successfully transmitted over G.711 RTP and decoded accurately on the receiving side. ATIS-1000041 21 Figure 15: G.711 Fall Back (from non-
39、G.711 session) 4.2.4.4 T.38 Fax Mode Description: Regular call session in progress using any negotiated voice codec; Provider B initiates fax transmission offering a T.38 connection; Provider A supports T.38, a T.38 session is established and the transmission is completed using T.38. Conditions to be checked: 1. A SIP re-Invite with a T.38 offer is sent and accepted before the T.38 connection is established. 2. Verify that while the T.38 connection is up the previous connection it disconnected. ATIS-1000041 22 Figure 16: T.38 Fax Mode
