| Valid8.com/ACATS VoIP SIP Conformance Test Suite, for use with SIP Signaling Tester |
|---|
| TEST SUITE OVERVIEW |
| References | ETSI TS 102 027-2 v4.1.1 (2006-07)) / IETF SIP RFC3261 |
|---|---|
| Archive/Project | voip/sip_ts |
| Version | 19171599 |
| Date | 22 Jan 2009 |
| Number of Scenarios | 708 |
| Number of Groups | 48 |
| Average per Group | 14 |
| GROUP/SCENARIO | TEST PURPOSE |
|---|
| ETSI | Corresponds to ETSI, ACATS enhancements separate |
|---|---|
| ETSI/ RG |
Checks RG signaling |
| ETSI/ RG/ RT |
Checks RT part of RG signaling |
| ETSI/ RG/ RT/ SIP_RG_RT_V |
|
| SIP_RG_RT_V_001 | Tx REGISTER Rq to registrar (no user name, with SIP-URI) |
| Ensure that the SUT, in order to be registered, sends a REGISTER
request to its registrar, without user name in the Request-URI and with a SIP-URI as request-URI. User Action: Make SUT register with Tester. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 10.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RT_V_002 | Rx Success (registration list, expires parameter) |
| Ensure that the SUT having sent a REGISTER request is able to receive
a Success (200 OK) response containing its current registration list in the Contact header and an expires parameter in the header User Action: Make SUT register with Tester. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 10.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RT_V_003 | Tx REGISTER Rq to pre-configured registrar (no user name) |
| Ensure that the SUT, in order to be registered, sends a REGISTER
request to the its pre-configured registrar address and without username. User Action: Make SUT register with Tester. Config: A SUT: User Agent Status: PICS: A.3/1.1 Ref: RFC3261 [1] section 10.2.6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RT_V_004 | Tx REGISTER Rq to host (no username) |
| Ensure that the SUT, in order to be registered, sends a REGISTER
request to host part of address of record as the Request-URI and without username. User Action: Make SUT register with Tester. Config: A SUT: User Agent Status: PICS: A.3/1.2 Ref: RFC3261 [1] section 10.2.6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RT_V_005 | Tx REGISTER Rq to all SIP servers (no username) |
| Ensure that the SUT, in order to be registered, sends a REGISTER
request to the well-known and without username. User Action: Make SUT register with Tester. Config: A SUT: User Agent Status: PICS: A.3/1.3 Ref: RFC3261 [1] section 10.2.6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RT_V_007 | Rx 401 Unauthorized, repeat REGISTER Rq (authorization header, incremented Cseq value) |
| Ensure that the SUT having sent a REGISTER message, on receipt of an
Unauthorized (401 Unauthorized) response including a WWW-Authenticate header, repeats its REGISTER request with an Authorization header and with an incremented Cseq value. Config: A SUT: User Agent Status: PICS: A.8/1 Ref: RFC3261 [1] sections 8.1.3.5 and 22.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RT_V_008 | Tx REGISTER Rq to its registrar (address of record) |
| Ensure that the SUT, in order to be registered, sends a REGISTER
request to its registrar, with a address-of record in the To header of type SIP URI. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 10.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RT_V_009 | Tx REGISTER Rq to registrar (same URI in From and To) |
| Ensure that the SUT, in order to be registered, sends a REGISTER
request to its registrar, with the same URI in the From and the To header. User Action: Make SUT register with Tester. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 10.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RT_V_010 | No Tx new REGISTER Rq before initial request expiry |
| Ensure that the SUT having sent a REGISTER request to which no final
response was received, does not send a new registration before expiration of the initial request. User Action: Make SUT register with Tester. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 10.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RT_V_010_b | No Tx new REGISTER Rq before initial request expiry |
| Ensure that the SUT having sent a REGISTER request to which no final
response was received, does not send a new registration before expiration of the initial request. User Action: Make SUT register with Tester. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 10.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RT_V_011 | Increment CSeq value by one in next REGISTER Rq (same Call-ID) |
| Ensure that the SUT having sent a REGISTER request, will increment the
CSeq value by one in the next new REGISTER request with the same Call-ID. User Action: Make SUT register with Tester. Config: A SUT: User Agent Status: Mandatory AND PICS: A.3/4 Ref: RFC3261 [1] section 10.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RT_V_012 | Rx Success, Tx at least one REGISTER Rq (same Call-ID) |
| Ensure that the SUT, already registered, sends at least one REGISTER
request, during the shortest lifetime indicated in the Contact parameters of the Success (200 OK) response it has received, using the same Call-ID as in the previous REGISTER request User Action: Make SUT register with Tester. Config: A SUT: User Agent Status: Recommended AND PICS: A.3/4 Ref: RFC3261 [1] section 10.2.4. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RT_V_013 | Tx REGISTER Rq (Expires parameter/header = 0) |
| Ensure that the SUT, in order to remove an existing binding sends a
REGISTER request, with Expires parameter set to zero in the Contact headers or an Expires header set to 0 when Contact field is set to <*>. User Action: Make SUT register with Tester. Config: A SUT: User Agent Status: Recommended AND PICS: A.3/3 Ref: RFC3261 [1] section 10.2.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RT_V_013_A | Tx REGISTER Rq (Expires parameter/header = 0) |
| Ensure that the SUT, in order to remove an existing binding sends a
REGISTER request, with Expires parameter set to zero in the Contact headers or an Expires header set to 0 when Contact field is set to <*>. Extends SIP_RG_RT_V_013 to ACK an incoming REGISTER (to establish existing binding) before one with <*>. User Action: Have SUT register with Tester. Config: A SUT: User Agent Status: Recommended Ref: RFC3261 [1] section 10.2.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RT_V_014 | Tx REGISTER Rq to registrar (no Contact header) |
| Ensure that the SUT, in order to get its registered contacts, sends a
REGISTER request to its registrar without Contact header. User Action: Make SUT register with Tester. Config: A SUT: User Agent Status: PICS: A.3/5 Ref: RFC3261 [1] section 10.2.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RT_V_015 | Tx REGISTER Rq to registrar (Expires header field /"expires" Contact header parameter) |
| Ensure that the SUT, in order to suggest an expiration interval for
its binding, sends a REGISTER request to its registrar with either an Expires header field or "expires" Contact header parameter. User Action: Make SUT register with Tester. Config: A SUT: User Agent Status: PICS: A.3/6 Ref: RFC3261 [1] section 10.2.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RT_V_016 | Tx REGISTER Rq to registrar ("q" Contact header parameter) |
| Ensure that the SUT, in order to order its bindings, to indicate a
relative preference for the list in the Contact header field value, sends a REGISTER request to its registrar with "q" Contact header parameter. User Action: Make SUT register with Tester. Config: A SUT: User Agent Status: PICS: A.3/7 Ref: RFC3261 [1] section 10.2.1.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RT_V_017 | Rx Success (Date header field) |
| Ensure that the SUT having sent a REGISTER request is able to receive
a Success (200 OK) response containing a Date header field. User Action: Make SUT register with Tester. Config: A SUT: User Agent Status: PICS: A.3/8 Ref: RFC3261 [1] section 10.2.5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RT_V_018 | Rx 401 Unauthorized, repeat REGISTER (username, realm nonce, digest uri, response HTTP) |
| Ensure that the SUT having sent a REGISTER request, on receipt of an
Unauthorized (401 Unauthorized) response including a WWW-Authenticate header, repeats its REGISTER request with an Authorization header including proper values for username, realm nonce, digest-uri and response HTTP parameters. User Action: Make SUT register with Tester. Config: A SUT: User Agent Status: PICS: A.8/1 Ref: RFC3261 [1] section 8.1.3.5 and 22.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RT_V_019 | Rx Proxy Authentication Required , repeat REGISTER (incremented Cseq value) |
| Ensure that the SUT having sent a REGISTER message, on receipt of a
Proxy Authentication Required (407 Proxy Authentication Required) response including a Proxy-Authenticate header, repeats its REGISTER request with a Proxy-Authorization header and with an incremented Cseq value. User Action: Make SUT register with Tester. Config: A SUT: User Agent Status: PICS: A.8/1 Ref: RFC3261 [1] section 8.1.3.5 and 22.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RT_V_020 | Rx Proxy Authentication Required , repeat REGISTER (username, realm nonce, digest-uri, response HTTP) |
| Ensure that the SUT having sent a REGISTER message, on receipt of a
Proxy Authentication Required (407 Proxy Authentication Required) response including a Proxy-Authenticate header, repeats its REGISTER request with a Proxy-Authorization header including proper values for username, realm nonce, digest-uri and response HTTP parameters. User Action: Make SUT register with Tester. Config: A SUT: User Agent Status: PICS: A.8/1 Ref: RFC3261 [1] section 8.1.3.5 and 22.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ RG/ RT/ SIP_RG_RT_TI |
|
| SIP_RG_RT_TI_001 | Repeat REGISTER Rq, timer E = T1 (unreliable transport) |
| If an unreliable transport is used, ensure that the SUT, having sent a
REGISTER request, repeats its request after timer E set to T1 value expires. User Action: Make SUT register with Tester. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] annex A and section 17.1.2.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RT_TI_002 | Repeat REGISTER Rq, timer E = MIN (2*T1,T2) (unreliable transport) |
| If an unreliable transport is used, ensure that the SUT, having sent
twice times a REGISTER request, repeats its request after timer E set to the MIN(2*T1,T2) value expires. User Action: Make SUT register with Tester. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] annex A and section 17.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RT_TI_003 | Repeat REGISTER Rq, timer E = MIN (4*T1,T2) (unreliable transport) |
| If an unreliable transport is used, ensure that the SUT, having sent
three times a REGISTER request, repeats its request after timer E set to the MIN(4*T1,T2) value expires. User Action: Make SUT register with Tester. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] annex A and section 17.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RT_TI_004 | No repeat REGISTER Rq, timer F = 64*T1 (unreliable transport) |
| If an unreliable transport is used, ensure that the SUT, does not
repeat a REGISTER request, after timer F set to the 64*T1 expires. User Action: Set supervisor timer to 120000. Make SUT register with Tester. Config: A SUT: User Agent Status: PICS: A.15/5 Ref: RFC3261 [1] annex A and section 17.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RT_TI_005 | Repeat REGISTER Rq, timer E = T1 (REGISTER client in the proceeding state) |
| Ensure that the SUT, when a REGISTER client transaction is in the
Proceeding state, repeats its REGISTER request after timer E set to T1 value expires. User Action: Make SUT register with Tester. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] annex A and section 17.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RT_TI_006 | Repeat REGISTER Rq, timer E = T2 (REGISTER client in proceeding state) |
| Ensure that the SUT, when a REGISTER client transaction is in the
Proceeding state and REGISTER request have been already repeated in this state, repeats its REGISTER request after timer E set to T2 value expires. User Action: Make SUT register with Tester. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] annex A and section 17.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RT_TI_007 | Repeat REGISTER Rq, timer F = 64*T1 (REGISTER client in Proceeding state) |
| Ensure that the SUT, when a REGISTER client transaction is in the
Proceeding state, repeats its REGISTER request, after timer F set to 64*T1 expires. User Action: Make SUT register with Tester Config: A SUT: User Agent Status: PICS: A.15/5 Ref: RFC3261 [1] annex A and section 17.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ RG/ RR |
Checks RR part of RG signaling |
| ETSI/ RG/ RR/ SIP_RG_RR_V |
|
| SIP_RG_RR_V_001 | Tx Success (no username) |
| Ensure the SUT on receipt of a REGISTER and without user name in the
Request-URI, sends a Success (200 OK) response, containing all current bindings listed in the Contact header, with the expires parameter for each Contact value. Config: B SUT: Proxy or Redirect Server Status: Mandatory Ref: RFC3261 [1] section 10.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RR_V_002 | Tx Success (multiple Contact header) |
| Ensure that the SUT on receipt of a REGISTER request including
multiple Contact header sends a Success (200 OK) response, and adds these addresses to the current bindings list. Note: **In SIP configuration, set SUT Authentication off and IP_Register_With_Proxy = FALSE** User Action: No action. Config: B SUT: Proxy or Redirect Server Status: Mandatory Ref: RFC3261 [1] section 10.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RR_V_003 | Tx successive Success (same Call-ID, different Contact header) |
| Ensure that the SUT on receipt of a successive REGISTER with the same
Call-ID but with different Contact header answers successively each of them with a Success (200 OK) response, and adds these addresses to the current bindings list. Note: **In SIP configuration, set SUT Authentication off and IP_Register_With_Proxy = FALSE** User Action: No action. Config: B SUT: Proxy or Redirect Server Status: Mandatory Ref: RFC3261 [1] sections 10.2 and 10.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RR_V_004 | Tx Success (third party registration) |
| Ensure that the SUT on receipt of a REGISTER request including a From
header addressing a different entity than that addressed by the To header (third party registration), sends a Success (200 OK) response. Note: **In SIP configuration, set SUT Authentication off and IP_Register_With_Proxy = FALSE** User Action: No action. Config: B SUT: Proxy or Redirect Server Status: PICS: A.63/6 Ref: RFC3261 [1] sections 10.2 and 10.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RR_V_005 | Tx Success (same Call-ID/Contact header, increasing CSeq number) |
| Ensure that the SUT on receipt of periodic REGISTER request with the
same Call-ID and Contact header, and with an increasing CSeq number answers each of them with a Success (200 OK) response. Note: **In SIP configuration, set SUT Authentication off and IP_Register_With_Proxy = FALSE** User Action: No action. Config: B SUT: Proxy or Redirect Server Status: Mandatory Ref: RFC3261 [1] sections 10.2 and 10.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RR_V_006 | Tx Success (no Contact header) |
| Ensure that the SUT when the UA is already registered, on receipt of
REGISTER request without Contact header, sends a Success (200 OK) response including the expiration time of the registration in an expires parameter in the Contact header. Note: **In SIP configuration, set SUT Authentication off and IP_Register_With_Proxy = FALSE** User Action: No action. Config: B SUT: Proxy or Redirect Server Status: Mandatory Ref: RFC3261 [1] sections 10.2 and 10.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RR_V_007 | Tx Success (Expires header) |
| Ensure that the SUT on receipt of a REGISTER request including an
Expires header, sends a Success (200 OK) response. Config: B SUT: Proxy or Redirect Server Status: Mandatory Ref: RFC3261 [1] sections 10.2 and 10.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RR_V_008 | Tx Success (Expires parameter) |
| Ensure that the SUT on receipt of a REGISTER request including an
Expires parameter in the Contact header, sends a Success (200 OK) response Note: **In SIP configuration, set SUT Authentication off and IP_Register_With_Proxy = FALSE** User Action: No action. Config: B SUT: Proxy or Redirect Server Status: Mandatory Ref: RFC3261 [1] sections 10.2 and 10.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RR_V_009 | Tx Success (no display name) |
| Ensure that the SUT on receipt of a REGISTER request including a
Contact header without display name, sends a Success (200 OK) response. Note: **In SIP configuration, set SUT Authentication off and IP_Register_With_Proxy = FALSE** User Action: No action. Config: B SUT: Proxy or Redirect Server Status: Mandatory Ref: RFC3261 [1] sections 10.2 and 20.10. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RR_V_010 | Tx Success, remove binding (Contact header=*, Call-ID=stored value, CSeq>stored value) |
| Ensure that the SUT when a binding already registered, on receipt of
a REGISTER request including a Contact header set to * and an Expires header set to zero, and Call-ID is the same as the stored Call-ID value and CSeq is greater than the stored CSeq value of that binding, removes that binding and sends a Success (200 OK) response. Note: **In SIP configuration, set SUT Authentication off and IP_Register_With_Proxy = FALSE** User Action: No action. Config: B SUT: Proxy or Redirect Server Status: Mandatory Ref: RFC3261 [1] section 10.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RR_V_011 | Tx Success, remove binding (Contact header=*, different Call-ID value) |
| Ensure that the SUT when a binding already registered, on receipt of
a REGISTER request including a Contact header set to * and an Expires header set to zero, and Call-ID is different from the stored Call-ID value of that binding, removes that binding and sends a Success (200 OK) response. Note: **In SIP configuration, set SUT Authentication off and IP_Register_With_Proxy = FALSE** User Action: No action. Config: B SUT: Proxy or Redirect Server Status: Mandatory Ref: RFC3261 [1] section 10.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RR_V_012 | Tx Success, add binding (expiration<>0, different Call-ID value) |
| Ensure that the SUT when a binding already registered, on receipt of
a REGISTER request including a Contact header set to an address which is not in the bindings list, and the received expiration time other than zero, and Call-ID is different from the stored Call-ID value of that binding, adds that binding to the list and sends a Success (200 OK) response. Note: **In SIP configuration, set SUT Authentication off and IP_Register_With_Proxy = FALSE** User Action: No action. Config: B SUT: Proxy or Redirect Server Status: Mandatory Ref: RFC3261 [1] section 10.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RR_V_013 | Tx Success (expiration<>0, different Call-ID value) |
| Ensure that the SUT when a binding already registered, on receipt of
a REGISTER request including a Contact header set to an address which is in the bindings list with a Call-ID different from the value stored for that binding, and an expiration time other than zero, sends a Success (200 OK) response. Note: **In SIP configuration, set SUT Authentication off and IP_Register_With_Proxy = FALSE** User Action: No action. Config: B SUT: Proxy or Redirect Server Status: Mandatory Ref: RFC3261 [1] section 10.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RR_V_014 | Tx Success, delete binding (expiration=0, different Call-ID value) |
| Ensure that the SUT when a binding already registered, on receipt of
a REGISTER request including a Contact header set to an address which is in the bindings list with a Call-ID different from the value stored for that binding, and an expiration time set to zero, deletes that binding and sends a Success (200 OK) response. Note: **In SIP configuration, set SUT Authentication off and IP_Register_With_Proxy = FALSE** User Action: No action. Config: B SUT: Proxy or Redirect Server Status: Mandatory Ref: RFC3261 [1] section 10.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RR_V_015 | Tx Success (Call-ID=stored value, CSeq>stored value, expiration<>0) |
| Ensure that the SUT when a binding already registered, on receipt of a
REGISTER request including a Contact header set to an address which is in the bindings list with the same Call-ID as the value stored for that binding, CSeq is greater than the stored CSeq value of that binding, and an expiration time other than zero, sends a Success (200 OK) response. Config: B SUT: Proxy or Redirect Server Status: Mandatory Ref: RFC3261 [1] section 10.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RR_V_016 | Tx Success, delete binding (Call-ID=stored value, CSeq>stored value, expiration=0) |
| Ensure that the SUT when a binding already registered, on receipt of a
REGISTER request including a Contact header set to an address which is in the bindings list with the same Call-ID as the value stored for that binding, CSeq is greater than the stored CSeq value of that binding, and an expiration time equal to zero, deletes that binding and sends a Success (200 OK) response. Config: B SUT: Proxy or Redirect Server Status: Mandatory Ref: RFC3261 [1] section 10.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RR_V_017 | Tx Success, (established call) |
| Ensure that the SUT when a call is currently established, on receipt
of a REGISTER request, sends a Success (200 OK) response. Note: **In SIP configuration, set SUT Authentication off and IP_Register_With_Proxy = FALSE** User Action: No action. Config: B SUT: Proxy or Redirect Server Status: Mandatory Ref: RFC3261 [1] section 10.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RR_V_018 | Tx 401 Unauthorized/407 Proxy Authentication Required |
| Ensure that the SUT on receipt of a REGISTER request not including
an Authorization or Proxy-Authorization header field, sends an Unauthorized (401 Unauthorized) or Proxy Authentication Required (407 Proxy Authentication Required) response, containing a WWW-Authenticate header or a Proxy-Authenticate header. Note: **In SIP configuration, set SUT Authentication on, and IP_Register_With_Proxy = FALSE** User Action: No action. Config: B SUT: Proxy or Redirect Server Status: PICS: A.68/1 Ref: RFC3261 [1] sections 10.3, item 3 and 22.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RR_V_019 | Tx 403 Forbidden (user not authorized to modify address of record) |
| Ensure that the SUT on receipt of a REGISTER request, but the
authenticated user not authorized to modify this address-of record, sends a Forbidden (403 Forbidden) response. Note: **In SIP configuration, set SUT Authentication off and IP_Register_With_Proxy = FALSE** User Action: No action. Config: B SUT: Proxy or Redirect Server Status: PICS: A.68/1 Ref: RFC3261 [1] section 10.3, item 4. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RR_V_020 | Tx Success ("q" Contact header) |
| Ensure that the SUT on receipt of a REGISTER and including "q" Contact
header parameter, sends a Success (200 OK) response. Note: **In SIP configuration, set SUT Authentication off and IP_Register_With_Proxy = FALSE** User Action: No action. Config: B SUT: Proxy or Redirect Server Status: PICS: A.63/2 Ref: RFC3261 [1] section 10.2.1.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RR_V_021 | Tx 401 Unauthorized/407 Proxy Authentication Required (realm, nonce HTTP) |
| Ensure that the SUT on receipt of a REGISTER request not including an
Authorization or a Proxy_Authorization header fields, sends an Unauthorized (401 Unauthorized) or Proxy Authentication Required (407 Proxy Authentication Required) response, containing a WWW-Authenticate or a Proxy_Authenticate header including Proxy-Authenticate header including proper value for realm and nonce HTTP parameters. Note: **In SIP configuration, set SUT Authentication off and IP_Register_With_Proxy = FALSE** User Action: No action. Config: B SUT: Proxy or Redirect Server Status: PICS: A.68/1 Ref: RFC3261 [1] section 10.3, item 3 and 22.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RR_V_022 | Tx Success (valid Authentication/Proxy-Authorization header field) |
| Ensure that the SUT having sent an Unauthorized (401 Unauthorized) or
a Proxy Authentication Required (407 Proxy Authentication Required) response to a REGISTER request, on receipt of a REGISTER request including a valid Authorization or Proxy-Authorization header field, sends a Success (200 OK) response. User Action: No action. Config: B SUT: Proxy or Redirect Server Status: PICS: A.68/1 Ref: RFC3261 [1] section 10.3, item 3 and 22.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ RG/ RR/ SIP_RG_RR_I |
|
| SIP_RG_RR_I_001 | Tx 404 Not Found (address of record not valid) |
| Ensure the SUT on receipt of a REGISTER request including a To
header from which the extracted address-of-record is not valid for the domain in the Request-URI, sends a Request Failure (404 Not Found) Config: B SUT: Proxy or Redirect Server Status: Mandatory Ref: RFC3261 [1] section 10.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RR_I_002 | Tx 400 response (user name in SIP URI as Request-URI) |
| Ensure that the SUT on receipt of a REGISTER request including a user
name in the SIP URI as the Request-URI, sends a 400 response. Config: B SUT: Proxy or Redirect Server Status: Mandatory Ref: RFC3261 [1] sections 10.3 and 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RR_I_003 | Tx 400 Bad Request (additional Contact header) |
| Ensure that the SUT on receipt of a REGISTER request including a
Contact header set to <*> together with an additional Contact header, sends a Client error (400 Bad Request) response. User Action: No action. Config: B SUT: Proxy or Redirect Server Status: Mandatory Ref: RFC3261 [1] section 10.3, item 3 and 22.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RR_I_004 | Tx 400 Bad Request (expiration<>0) |
| Ensure that the SUT on receipt of a REGISTER request including a
Contact header set to <*>, and an Expires header with an expiration time set to other than zero, sends a Client error (400 Bad Request) response. Config: B SUT: Proxy or Redirect Server Status: Mandatory Ref: RFC3261 [1] section 10.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ RG/ RR/ SIP_RG_RR_O |
|
| SIP_RG_RR_O_001 | Tx Success, no remove binding (Contact=*, Expires=0, Call-ID=stored value, CSeq=stored value) |
| Ensure that the SUT when a binding already registered, on receipt of a
REGISTER request including a Contact header set to * and an Expires header set to zero, and Call-ID is the same as the stored Call-ID value and CSeq is equal to the stored CSeq value of that binding, does not remove that binding and sends a Success (200 OK) response. Config: B SUT: Proxy or Redirect Server Status: Mandatory Ref: RFC3261 [1] section 10.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RR_O_002_A | Tx 500 Server Error |
| Ensure that the SUT when a binding already registered, on receipt of a
REGISTER request including a Contact_1 header set to an address which is in the bindings list with the same Call-ID as the value stored for that binding, CSeq is equal to the stored CSeq value of that binding, and an expiration time other than zero, sends a Server Failure (500 Server Error) response. Config: B SUT: Proxy or Redirect Server Status: Mandatory Ref: RFC3261 [1] section 10.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RR_O_002_B | Tx 200 OK (Contact_1 header=address in binding, expiration<>0) |
| Ensure that the SUT when a binding already registered, on receipt of a
REGISTER request including a Contact_1 header set to an address which is in the bindings list with the same Call-ID as the value stored for that binding, CSeq is equal to the stored CSeq value of that binding, and an expiration time other than zero, sends a 200 OK response. Config: B SUT: Proxy or Redirect Server Status: Mandatory Ref: RFC3261 [1] section 10.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_RG_RR_O_003 | No tx 500 Server Error |
| Ensure that the SUT when a binding already registered, on receipt of a
REGISTER request including a Contact header set to an address which is in the bindings list with the same Call-ID as the value stored for that binding, CSeq is equal to the stored CSeq value of that binding, and an expiration time equal to zero, does not remove that binding and sends a Server Failure (500 Server Error) response. Config: B SUT: Proxy or Redirect Server Status: Mandatory Ref: RFC3261 [1] section 10.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ CC |
Checks CC signaling |
| ETSI/ CC/ OE |
Checks OE part of CC signaling |
| ETSI/ CC/ OE/ SIP_CC_OE |
|
| ETSI/ CC/ OE/ SIP_CC_OE/ SIP_CC_OE_CE_V |
|
| SIP_CC_OE_CE_V_001 | Tx INVITE Rq (To, From, CSeq, Call-ID, Max-Forwards, Contact, Via) |
| Ensure that the SUT, to establish a call sends an INVITE request
including at least To, From, CSeq, Call-ID, Max-Forwards, Contact and Via headers. User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 8.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_002 | Tx INVITE Rq (Request-URI=URI of To header) |
| Ensure that the SUT, to establish a call sends an INVITE request with
a Request-URI set to the same URI value of the To header. User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A, E SUT: User Agent Status: Recommended Ref: RFC3261 [1] section 8.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_003 | Tx INVITE Rq (To=address of callee, no TAG) |
| Ensure that the SUT, to establish a call sends an INVITE request
including a To header set to an address of the callee and without TAG parameter. User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 8.1.1.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_004 | Tx INVITE Rq (From, TAG) |
| Ensure that the SUT, to establish a call sends an INVITE request
including a From header with a TAG parameter. User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 8.1.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_005 | Tx INVITE Rq (CSeq match INVITE) |
| Ensure that the SUT, to establish a call sends an INVITE request
including a CSeq header with a method that matches INVITE. User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 8.1.1.5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_006 | Tx INVITE Rq (Max-Forward=70) |
| Ensure that the SUT, to establish a call sends an INVITE request
including a Max-Forward header set to 70. User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A, E SUT: User Agent Status: Recommended Ref: RFC3261 [1] section 8.1.1.6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_007 | Tx INVITE Rq (Via SIP, protocol version 2.0) |
| Ensure that the SUT, to establish a call sends an INVITE request
including a Via header with a protocol name set to SIP, a protocol version set to 2.0 and a branch parameter set to a value beginning with User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 8.1.1.7. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_008 | Tx INVITE Rq (Allow, Supported) |
| Ensure that the SUT, to establish a call sends an INVITE request
including Allow and Supported headers User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A, E SUT: User Agent Status: PICS: A.22/2.5 Ref: RFC3261 [1] section 13.2.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_009 | Enter Proceeding state on receipt of 100 Trying |
| Ensure that the SUT when an INVITE client transaction is in the
Calling state, on receipt of a Trying (100 Trying) response enters in the Proceeding state. User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 8, 8.1.3.2 and 13.2.2.1, figure 5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_010 | Enter Proceeding state on receipt of 183 Session Progress |
| Ensure that the SUT when an INVITE client transaction is in the
Calling state, on receipt of a Session Progress (183 Session Progress) response enters in the Proceeding state. User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 8.1.3.2 and 13.2.2.1, figure 5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_011 | Enter Proceeding state on receipt of 199 Unknown |
| Ensure that the SUT when an INVITE client transaction is in the
Calling state, on receipt of a Unknown (199 Unknown) response enters in the Proceeding state. User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 8.1.3.2 and 13.2.2.1, figure 5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_012 | Stay in Proceeding state on receipt of 100 Trying |
| Ensure that the SUT when an INVITE client transaction is in the
Proceeding state, on receipt of a Trying (100 Trying) response stays in the Proceeding state. Pre-condition: User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 8.1.3.2 and 13.2.2.1, figure 5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_013 | Tx ACK Rq on receipt of Success (calling state) |
| Ensure that the SUT when an INVITE client transaction is in the
calling state, on receipt of a Success (200 OK) response sends an ACK request Pre-condition: User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 12.2.1.1, 13.2.2.4, figure 5 and 17.1.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_014 | Tx ACK Rq on receipt of Success(Proceeding state) |
| Ensure that the SUT when an INVITE client transaction is in the
Proceeding state, on receipt of a Success (200 OK) response sends an ACK request User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 12.2.1.1, 13.2.2.4, figure 5 and 17.1.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_015 | No Tx ACK Rq (more than one Via) |
| Ensure that the SUT when an INVITE client transaction is in the
Proceeding state, on receipt of a Success (200 OK) response with more than one Via header value does not send an ACK request, discards the response. Pre-condition: User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A, E SUT: User Agent Status: Recommended Ref: RFC3261 [1] section 8.1.3.3, figure 5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_016 | Tx ACK Rq (same sequence number, CSeq method field=ACK) |
| Ensure that the SUT when an INVITE client transaction is in the
Calling state, on receipt of a Success (200 OK) response sends an ACK request with the same sequence number as in the original INVITE request and the CSeq method field value set to Pre-condition: User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 12.2.1.1, 13.2.2.4, figure 5 and 17.1.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_017 | Tx ACK Rq (To=received final response value) |
| Ensure that the SUT when an INVITE client transaction is in the
Calling state, on receit of a Success (200 OK) response sends an ACK request with the To header set to the same value as in the received final response. User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 12.2.1.1, 13.2.2.4, figure 5 and 17.1.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_018 | Tx ACK Rq (To, no TAG) |
| Ensure that the SUT when an INVITE client transaction is in the
Calling state, on receipt of a Success (200 OK) response including a To header without TAG sends an ACK request with a To header without Tag. User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 12.2.1.1, 13.2.2.4, figure 5 and 17.1.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_019 | Tx ACK Rq (different tag) |
| Ensure that the SUT when an INVITE client transaction is in the
Calling state, on receipt of Success (200 OK) responses differing only on the tag in the To header, sends an ACK request with a To header identical to the received one for each received Success (200 OK) responses. User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 12.2.1.1, 13.2.2.4, figure 5 and 17.1.1.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_020 | Tx ACK Rq (same Call-ID, From) |
| Ensure that the SUT when an INVITE client transaction is in the
Calling state, on receipt of a Success (200 OK) response sends an ACK request with the same Call-ID and From headers as in the original INVITE request User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 12.2.1.1, figure 5 and 17.1.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_021 | Tx ACK Rq (no Route header) |
| Ensure that the SUT when an INVITE client transaction is in the
calling state, on receipt of a Success (200 OK) response with no Record-Route header set sends an ACK request with the Request-URI set to the Contact URI included in the received final response and with no Route header set. Pre-condition: User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 12.2.1.1 and 13.2.2.4, figure 5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_022 | Tx ACK Rq, lr parameter (Route=reverse order list of Record-Route) |
| Ensure that the SUT when an INVITE client transaction is in the
Calling state, on receipt of a Success (200 OK) response with a Record-Route header set to a list in which the last element contains lr parameter, sends an ACK request with the Request-URI set to the Contact URI and a Route header set to the list in a reverse order of the Record-Route included in the received final response. Pre-condition: User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 12.2.1.1 and 13.2.2.4, figure 5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_023 | Tx ACK Rq, no lr parameter (Request-URI=lr parameter, Route=remainder list) |
| Ensure that the SUT when an INVITE client transaction is in the
Calling state, on receipt of a Success (200 OK) response with a Record-Route header set to a list in which the last element does not contains lr parameter, sends an ACK request with the Request-URI set to this element and a Route header set to the remainder list in a reverse order of the received Record-Route appended with the received Contact URI. Pre-condition: User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 12.2.1.1 and 13.2.2.4, figure 5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_024 | Tx ACK Rq on receipt of 300 Multiple Choices (Calling state) |
| Ensure that the SUT when an INVITE client transaction is in the
Calling state, on receipt of a Multiple Choices (300 Multiple Choices) response sends an ACK request with the same Call-ID, From headers and Request-URI as in the original INVITE request and the same Tag in the To header as in the Multiple Choices (300 Multiple Choices) response [PX_Contact_3XX_TESTER]. Pre-condition: User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Be sure to set configuration variable PX_Contact_3XX_TESTER to the IP address of the TESTER. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 13.2.2.2, figure 5, 17.1.1.2 and 17.1.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_025 | Tx ACK Rq on receipt of 300 Multiple Choices (Proceeding state) |
| Ensure that the SUT when an INVITE client transaction is in the
Proceeding state, on receipt of a Multiple Choices (300 Multiple Choices) response sends an ACK request with the same Call-ID, From headers and Request-URI as in the original INVITE request and the same Tag in the To header as in the Multiple Choices (300 Multiple Choices) response. Pre-condition: User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Be sure to set configuration variable PX_Contact_3XX_TESTER to the IP address of the TESTER. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 13.2.2.2, figure 5, 17.1.1.2 and 17.1.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_026 | Tx ACK Rq (single Via=top Via) |
| Ensure that the SUT when an INVITE client transaction is in the
Calling state, on receipt of a Multiple Choices (300 Multiple Choices) response sends an ACK request with a single Via header equal to the top Via header sent in the original INVITE request. Pre-condition: User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Be sure to set configuration variable PX_Contact_3XX_TESTER to the IP address of the TESTER. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 13.2.2.2, figure 5 and 17.1.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_027 | Tx ACK Rq on receipt of 301 Moved Permanently |
| Ensure that the SUT when an INVITE client transaction is in the
Calling state, on receipt of a Moved Permanently (301 Moved Permanently) response sends an ACK request with the same Call-ID, From headers and Request-URI as in the original INVITE request and the same Tag in the To header as in the Moved Permanently (301 Moved Permanently) response. Pre-condition: User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Be sure to set configuration variable PX_Contact_3XX_TESTER to the IP address of the TESTER. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 13.2.2.2, figure 5, 17.1.1.2 and 17.1.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_028 | Tx ACK Rq on receipt of 302 Moved Temporarily |
| Ensure that the SUT when an INVITE client transaction is in the
Calling state, on receipt of a Moved Temporarily (302 Moved Temporarily) response sends an ACK request with the same Call-ID, From headers and Request-URI as in the original INVITE request and the same Tag in the To header as in the Moved Temporarily (302 Moved Temporarily) response. Pre-condition: User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Be sure to set configuration variable PX_Contact_3XX_TESTER to the IP address of the TESTER. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 12.2.1.1, 13.2.2.2, figure 5, 17.1.1.2 and 17.1.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_029 | Tx INVITE Rq (PX_Proxy_TESTER) |
| Ensure that the SUT when an INVITE client transaction is in the
Calling state, on receipt of a Use Proxy (305 Use Proxy) response sends an INVITE request to the proxy given by the Contact header [PX_Proxy_TESTER]. Pre-condition: User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A SUT: User Agent Status: PICS A 16 / 1.3 Ref: RFC3261 [1] sections 8.1.3.4, 21.3.4, 13.2.2.2, figure 5, 17.1.1.2 [1] and 17.1.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_030 | Tx INVITE Rq on receipt of 301 Moved Permanently (Request-URI) |
| Ensure that the SUT when an INVITE client transaction is in the
Calling state, on receipt of a Moved Permanently (301 Moved Permanently) response sends a new INVITE request with a Request-URI set with one of URI given in the Contact header of the redirection response. Pre-condition: User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A SUT: User Agent Status: PICS A 16 / 1.3 Ref: RFC3261 [1] section 8.1.3.4, figure 5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_031 | Tx INVITE Rq on receipt of 301 Moved Permanently (new branch ID) |
| Ensure that the SUT when an INVITE client transaction is in the
Calling state, on receipt of a Moved Permanently (301 Moved Permanently) response sends a new INVITE request with a new branch ID in the top Via header. Pre-condition: User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A SUT: User Agent Status: PICS A 16 / 1.3 Ref: RFC3261 [1] section 8.1.3.4, figure 5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_032 | Tx ACK Rq on receipt of 404 Not Found (Calling state) |
| Ensure that the SUT when an INVITE client transaction is in the
Calling state, on receipt of a Not Found (404 Not Found) response sends an ACK request with the same Call-ID, From headers and Request-URI as in the original INVITE request and the same Tag in the To header as in this response. Pre-condition: User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 13.2.2.2, figure 5, 17.1.1.2 and 17.1.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_033 | Tx ACK Rq on receipt of 404 Not Found (Proceeding state) |
| Ensure that the SUT when an INVITE client transaction is in the
Proceeding state, on receipt of a Not Found (404 Not Found) response sends an ACK request with the same Call-ID, From headers and Request-URI as in the original INVITE request and the same Tag in the To header as in this response. Pre-condition: User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 13.2.2.3, figure 5, 17.1.1.2 and 17.1.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_034 | Tx ACK Rq on Rx 410 Gone |
| Ensure that the SUT when an INVITE client transaction is in the
Calling state, on receipt of a Gone (410 Gone) response sends an ACK request with the same Call-ID, From headers and Request-URI as in the original INVITE request and the same Tag in the To header as in this response. Pre-condition: User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 13.2.2.3, figure 5, 17.1.1.2 and 17.1.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_035 | Tx ACK Rq on Rx 480 Temporarily Unavailable |
| Ensure that the SUT when an INVITE client transaction is in the
Calling state, on receipt of a Temporarily Unavailable (480 Temporarily Unavailable) response sends an ACK request with the same Call-ID, From headers and Request-URI as in the original INVITE request and the same Tag in the To header as in this response. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 13.2.2.3, figure 5, 17.1.1.2 and 17.1.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_036 | Tx ACK Rq on Rx 486 Busy Here |
| Ensure that the SUT when an INVITE client transaction is in the
Calling state, on receipt of a Busy Here (486 Busy Here) response sends an ACK request with the same Call-ID, From headers and Request-URI as in the original INVITE request and the same Tag in the To header as in this response. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 13.2.2.3, figure 5, 17.1.1.2 and 17.1.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_037 | Tx ACK Rq on Rx 500 Server Internal Error |
| Ensure that the SUT when an INVITE client transaction is in the
Calling state, on receipt of a Server Internal Error (500 Server Internal Error) response sends an ACK request with the same Call-ID, From headers and Request-URI as in the original INVITE request and the same Tag in the To header as in this response. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 13.2.2.3, figure 5, 17.1.1.2 and 17.1.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_038 | Tx only 1 ACK Rq on Rx 600 Busy Everywhere & 500 Server Internal Error |
| Ensure that the SUT when an INVITE client transaction is in the
Calling state, on receipt of a Busy Everywhere (600 Busy Everywhere) and a Server Internal Error (500 Server Internal Error) responses with different branch parameter value on the top Via header sends only one ACK request. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 13.2.2.3, figure 5, 17.1.1.2 and 17.1.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_039 | Tx ACK Rq on Rx 603 Decline |
| Ensure that the SUT when an INVITE client transaction is in the
Calling state, on receipt of a Decline (603 Decline) response sends an ACK request with the same Call-ID, From headers and Request-URI as in the original INVITE request and the same Tag in the To header as in this response. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 13.2.2.3, figure 5, 17.1.1.2 and 17.1.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_040_A | Tx ACK Msg on Rx 603 Decline |
| Ensure that the SUT having already received a non 2XX final response
to its INVITE request, on receipt of a Decline (603 Decline) response with the same Via branch parameter and CSeq header method as in the INVITE request, sends an ACK message. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 13.2.2.3, figure 5, 17.1.1.2 and 17.1.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_040_B | No Tx ACK Msg on Rx 603 Decline |
| Ensure that the SUT having already received a non 2XX final response
to its INVITE request, on receipt of a Decline (603 Decline) response with the same Via branch parameter and CSeq header method as in the INVITE request, does not send an ACK message. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 13.2.2.3, figure 5, 17.1.1.2 and 17.1.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_041 | Tx ACK Rq (Route=new Record-Route) |
| Ensure that the SUT having already received a 2XX final response to
its INVITE request, on receipt of a Success (200 OK) response with a different Record-Route (PX_Record_Route_1) as in previous response, but with the same Via branch parameter and Cseq header method as in the INVITE request, sends an ACK request with a Route header set according to this new Record-Route. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 17, 13.2.2.3, figure 5, 17.1.1.2 and 17.1.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_042 | Tx ACK Rq on Rx 699 Unknown |
| Ensure that the SUT when an INVITE client transaction is in the
Calling state, on receipt of a Unknown (699 Unknown) response sends an ACK request with the same Call-ID, From headers and Request-URI as in the original INVITE request and the same Tag in the To header as in this response. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 8.1.3.2, 13.2.2.3, figure 5, 17.1.1.2 and 17.1.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_043 | Tx ACK Rq on Rx Success (redirect server) |
| Ensure that the SUT having sent an INVITE to the location get from the
redirect server, on receipt of a Success (200 OK) response sends an ACK request. Config: A SUT: User Agent Status: PICS A 16 / 1.3 Ref: RFC3261 [1] sections 21.3.3, 12.2.1, 13.2.2.2, figure 5, 17.1.1.2 and 17.1.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_044 | Tx unique session description in INVITE Rq/ACK Rq |
| Ensure that the SUT while is establishing a call, sends a unique
session description either in the INVITE request or in the ACK request to answer the initial offers given then in the final 2XX response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 13.2.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_045 | Tx Content-Length header |
| Ensure that the SUT while is establishing a call, sends a
Content-Length header set to the size of the body in the message that contains the session description. Config: A, E SUT: User Agent Status: PICS A 22 / 2.13 Ref: RFC3261 [1] sections 20.14 and 13.2.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_046 | Tx Content-Type header |
| Ensure that the SUT while is establishing a call, sends a Content-Type
header in the message that contains the session description. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 20.15 and 13.2.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_047 | Tx Content-Encoding header |
| Ensure that the SUT while is establishing a call, sends a
Content-Encoding header only in the message that contains the session description. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 7.4 and 13.2.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_048 | Tx ACK Rq followed by BYE Rq (2XX not acceptable session) |
| Ensure that the SUT while is establishing a call on receipt of in 2XX
a not acceptable session, sends an ACK request immediately followed by a BYE request. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 13.2.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_049 | Tx Content_Length header (reliable transport (TCP) used) |
| If a reliable transport (TCP) is used, ensure that the SUT while is
establishing a call, sends a Content_Length header set to the size of the body in the message that contains the session description. User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 20.14 and 13.2.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_050 | Repeat INVITE Rq on Rx 401 Unauthorized (incremented Cseq value) |
| Ensure that the SUT having sent an INVITE request, on receipt of
an Unauthorized (401 Unauthorized) response including a WWW-Authenticate header, repeats its INVITE request with an Authorization header and with an incremented Cseq value. Precondition: User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 8.1.3.5 and 22.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_051 | Rx 401 Unauthorized, repeat INVITE Rq on (username, realm onnce, digest-uri, response HTTP) |
| Ensure that the SUT having sent an INVITE request, on receipt of
an Unauthorized (401 Unauthorized) response including a WWW-Authenticate header, repeats its INVITE request with an Authorization header including proper values for username, realm onnce, digest-uri and response HTTP parameters. User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 8.1.3.5 and 22.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_052 | Rx 407 Proxy Authentication Required, repeat INVITE Rq (incremented Cseq value) |
| Ensure that the SUT having sent an INVITE request, on receipt of a
Proxy Authentication Required (407 Proxy Authentication Required) response including a Proxy-Authenticate header, repeats its INVITE request with an Proxy-Authorization header and with an incremented Cseq value. User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 8.1.3.5 and 22.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_V_053 | Rx 407 Proxy Authentication, repeat INVITE Rq (username, realm nonce, digest-uri, response HTTP) |
| Ensure that the SUT having sent an INVITE request, on receipt of
a Proxy Authentication Required (407 Proxy Authentication Required) response including a Proxy-Authenticate header, repeats its INVITE request with a Proxy-Authorization header including proper values for username, realm onnce, digest-uri and response HTTP parameters. User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 8.1.3.5 and 22.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ CC/ OE/ SIP_CC_OE/ SIP_CC_OE_CE_TI |
|
| SIP_CC_OE_CE_TI_001 | Repeat INVITE Rq (timer A=T1) (unreliable transport (UDP)) |
| If an unreliable transport (UDP) is used, ensure that the SUT,
when an INVITE client transaction is in the Calling state repeats its INVITE request on the timeout condition of timer A set with a value of T1. Precondition: User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] annex A and section 17.1.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_TI_002 | No repeat INVITE Rq (timer A=T1) (reliable transport (TCP)) |
| If a reliable transport (TCP) is used, ensure that the SUT, when an
INVITE client transaction is in the Calling state does not repeat its INVITE request on the timeout condition of timer A set with a value of T1. Config: A, E SUT: User Agent Status: Recommended Ref: RFC3261 [1] annex A and section 17.1.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_TI_003 | Wait before tx INVITE Rq (timer A=2*T1) (unreliable transport (UDP)) |
| If an unreliable transport (UDP) is used, ensure that the SUT, when an
INVITE client transaction is in the Calling state having already repeated its INVITE wait for a timer A set with a value of 2*T1 before sending it again. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] annex A and section 17.1.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_TI_004 | Retransmit INVITE Rq (intervals) (unreliable transport (UDP)) |
| If an unreliable transport (UDP) is used, ensure that the SUT, when an
INVITE client transaction is in the Calling state retransmits its INVITE request with intervals that double after each transmission. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] annex A and section 17.1.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_TI_005 | NoTx ACK (timer B=64*T1 expires) |
| Ensure that the SUT, when an INVITE client transaction is in the
Calling state, when timer B set to a value of 64*T1 expires, does not send an ACK. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] annex A and section 17.1.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_TI_006 | Consider transaction terminated (timer B=64*T1 expires) |
| Ensure that the SUT, when an INVITE client transaction is in the
Calling state, when timer B set to a value of 64*T1 expires, considers the transaction terminated. Config: A SUT: User Agent Status: Recommended Ref: RFC3261 [1] annex A and section 17.1.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_TI_007 | No repeat INVITE Rq (Proceeding state) |
| Ensure that the SUT, when an INVITE client transaction is in the
Proceeding state, does not repeat its INVITE request. Config: A, E SUT: User Agent Status: Recommended Ref: RFC3261 [1] annex A and section 17.1.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_TI_008 | Tx ACK Rq on receipt of matching final responses (timer D=32 second expires) |
| Ensure that the SUT, when an INVITE client transaction is in the
Calling state, on receipt of final responses that matches the transaction, still answer with an ACK request until timer D set to at least 32 second expires. Config: A SUT: User Agent Status: PICS A 38 / 6 Ref: RFC3261 [1] annex A and section 17.1.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_TI_009 | No repeat ACK Rq (reliable transport) (Completed state) |
| If a reliable transport is used, ensure that the SUT, when an INVITE
client transaction is in the Completed state, on receipt of a final response that matches the transaction, does not repeats its ACK request. Config: A, E SUT: User Agent Status: PICS A 38 / 6 Ref: RFC3261 [1] annex A and section 17.1.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_TI_010 | No repeat ACK Rq until timer D=32 second expires (unreliable transport) (Completed state) |
| If an unreliable transport is used, ensure that the SUT, when an
INVITE client transaction is in the Completed state, on receipt of new final responses with different Via branch parameter value, does not repeat its ACK request until timer D set to at least 32 second expires. Config: A, E SUT: User Agent Status: PICS A 38 / 6 Ref: RFC3261 [1] annex A and section 17.1.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_TI_011 | Tx ACK Rq until 64*T1 expires |
| Ensure that the SUT, when an INVITE client transaction has been in the
Terminated state, on receipt of a retransmitted Success (200 OK) responses sends an ACK request until 64*T1 duration expires. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] annex A and section 13.2.2.4. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CE_TI_012 | No tx ACK Rq after 64*T1 expires |
| Ensure that the SUT, when an INVITE client transaction has been in the
Terminated state, after 64*T1 duration expires, on receipt of a retransmitted Success (200 OK) responses does not send an ACK request. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] annex A and section 13.2.2.4. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ CC/ OE/ SIP_CC_OE/ SIP_CC_OE_CR_V |
|
| SIP_CC_OE_CR_V_001 | Tx BYE Rq (To=last received final response) |
| Ensure that the SUT, once a dialog has been established, to release it
sends a BYE request with a To header set to the same value as in the last received final response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 12.2.1.1 and 15. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CR_V_002 | Tx BYE Rq (identical To, no TAG) |
| Ensure that the SUT, once a dialog has been established with a final
response in which the TAG in the To header was omitted, to release it sends a BYE request with an identical To header without TAG value. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 12.2.1.1 and 15. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CR_V_003 | Tx BYE Rq (same Call-ID, From) |
| Ensure that the SUT, once a dialog has been established, to release it
sends a BYE request with the same Call-ID, From headers as in the original INVITE message. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 12.2.1.1 and 15. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CR_V_004 | Tx BYE Rq ( incremented CSeq, CSeq method field=BYE) |
| Ensure that the SUT, once a dialog has been established, to release it
sends a BYE request with an incremented of one CSeq value, a method field in the CSeq header set to BYE. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 12.2.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CR_V_005 | Tx BYE Rq (no Route) |
| Ensure that the SUT, once a dialog has been established with a Success
(200 OK) response including no Record-Router header set, to release it sends a BYE request with the Request-URI set to the Contact URI included in the received final response and with no Route header set. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 12.2.1.1 and 15. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CR_V_006 | Tx BYE Rq, lr parameter (Route= reverse order list of Record-Route) |
| Ensure that the SUT, once a dialog has been established with a Success
(200 OK) response including a Record-Route header set to a list in which the last element contains lr parameter, to release the call, sends a BYE request with the Request-URI set to the Contact URI and a Route header set to the list in a reverse order of the Record-Route included in the received final response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 12.2.1.1 and 15. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CR_V_007 | Tx BYE Rq, no lr parameter (Request-URI=lr parameter, Route=remainder list) |
| Ensure that the SUT, once a dialog has been established with a Success
(200 OK) response including a Record-Route header set to a list in which the last element does not contain lr parameter, to release the call, sends a BYE request with the Request-URI set to this element and a Route header set to the remainder list in a reverse order of the received Record-Route appended with the received Contact URI. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 12.2.1.1 and 15. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CR_V_008 | Consider session & dialog terminated on receipt of Success |
| Ensure that the SUT, once a dialog has been established, having sent a
BYE request, on receiptof a Success (200 OK) response considers the session and the dialog terminated. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 12.2.1.1 and 15. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CR_V_009 | Consider session & dialog terminated on Rx 481 Call Leg/Transaction Does Not Exist |
| Ensure that the SUT, once a dialog has been established, having sent
a BYE request, on receipt of a Call Leg/Transcation Does Not Exist (481 Call Leg/Transaction Does Not Exist) considers the session and the dialog terminated. Pre-condition: User Action: Place a call from the SUT to the Tester. Test case will tear down case automatically. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 12.2.1.1 and 15.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CR_V_010 | Tx CANCEL Rq (after Rx 100 Trying response) |
| Ensure that the SUT having received a Trying (100 Trying) response to
its INVITE request, to give up the call, sends a CANCEL request. Precondition: User Action: Place a call from the SUT to the Tester. Then on-hook the phone. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 15 and 9.1, figure 5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CR_V_011 | Tx CANCEL Rq (same Request-URI, Call-ID, From, To) |
| Ensure that the SUT having received a Trying (100 Trying) response to
its INVITE request, to give up the call, sends a CANCEL request with the same Request-URI, Call-ID, From, To headers as in the original INVITE message. Pre-condition: User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 15 and 9.1, figure 5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CR_V_012 | Tx CANCEL Rq (same CSeq, CSeq method field=CANCEL) |
| Ensure that the SUT having received a Trying (100 Trying) response to
its INVITE request, sends a CANCEL request with the same numeric part of CSeq as in the original INVITE message and with a method field in the CSeq header set to CANCEL. Pre-condition: User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 15 and 9.1, figure 5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CR_V_013 | Tx CANCEL Rq (singla matching Via) |
| Ensure that the SUT having received a Trying (100 Trying) response to
its INVITE request, sends a CANCEL request with a single Via header value matching the top Via value of the Via header of the original INVITE message. Pre-condition: User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 15 and 9.1, figure 5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CR_V_014 | Tx CANCEL Rq (no Require/Proxy-Require) |
| Ensure that the SUT having received a Trying (100 Trying) response to
its INVITE request, to give up the call, sends a CANCEL request without Require or Proxy-Require header. Pre-condition: User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically., Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 15 and 9.1, figure 5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CR_V_015 | Tx ACK Rq after Tx CANCEL Rq on Rx 2xx response |
| Ensure that the SUT having received a Trying (100 Trying) response to
its INVITE request, to give up the call having sent a CANCEL request, on receipt of a 2xx response to the original INVITE sends an ACK request. Pre-condition: User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 15 and 9.1, figure 5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ CC/ OE/ SIP_CC_OE/ SIP_CC_OE_CR_I |
|
| SIP_CC_OE_CR_I_001 | Tx Success Rq to BYE Rq |
| Ensure that the SUT, once a dialog has been established, on receipt of
a CANCEL request followed by a BYE request, sends a Success (200 OK) response to the BYE request. Pre-condition: User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 9 and 16.10. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ CC/ OE/ SIP_CC_OE/ SIP_CC_OE_CR_TI |
|
| SIP_CC_OE_CR_TI_001 | Repeat BYE Rq (timer E=T1 value expires) (unreliable transport (UDP)) |
| If an unreliable transport (UDP) is used, ensure that the SUT, having
sent a BYE request on an established dialog, repeats its request after timer E set to T1 value expires. Pre-condition: User Action: Place a call from the SUT to the Tester. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] annex A and section 15 and 17.1.2.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CR_TI_002 | Repeat BYE Rq (timer E=MIN (2*T1,T2) value expires) (unreliable transport) |
| If an unreliable transport is used, ensure that the SUT, having sent
twice times a BYE request on an established dialog, repeats its request after timer E set to the MIN(2*T1,T2) value expires. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] annex A and section 17.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CR_TI_003 | Repeat BYE Rq (timer E=MIN (4*T1,T2) value expires) (unreliable transport) |
| If an unreliable transport is used, ensure that the SUT, having sent
three times a BYE request on an established dialog, repeats its request after timer E set to the MIN(4*T1,T2) value expires. Pre-condition: User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] annex A and section 17.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CR_TI_004 | No repeat BYE Rq (timer F=64*T1 expires) (unreliable transport) |
| If an unreliable transport is used, ensure that the SUT does not
repeat a BYE request on an established dialog, after timer F set to 64*T1 expires. Pre-condition: User Action: Place a call from the SUT to the Tester. Config: A SUT: User Agent Status: Recommended Ref: RFC3261 [1] annex A and section 17.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CR_TI_005 | Repeat BYE Rq (timer E=T1 value expires) (Proceeding state) |
| Ensure that the SUT, when a BYE client transaction is in the
Proceeding state, repeats its BYE request after timer E set to T1 value expires. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] annex A and section 17.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CR_TI_006 | Repeat BYE Rq (timer E=T2 value expires) (Proceeding state) |
| Ensure that the SUT, when a BYE client transaction is in the
Proceeding state and BYE request have been already repeated in this state, repeats its BYE request after timer E set to T2 value expires. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] annex A and section 17.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CR_TI_007 | No repeat BYE Rq (timer F=64*T1 expires) (Proceeding state) |
| Ensure that the SUT, when a BYE client transaction is in the
Proceeding state, does not repeat a BYE request on an established dialog, after timer F set to 64*T1 expires. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] annex A and section 17.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_CR_TI_008 | Consider transaction terminated after 64*T1 expires (no Rx final response) |
| Ensure that the SUT, when a BYE client transaction is in the Trying
state, considers the transaction terminated after 64*T1 duration expires without receiving any final response. Config: A SUT: User Agent Status: Recommended Ref: RFC3261 [1] annex A and sections 17.1.3. and 9.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ CC/ OE/ SIP_CC_OE/ SIP_CC_OE_SM_V |
|
| SIP_CC_OE_SM_V_001_A | Tx 491 Request Pending on Rx re-INVITE |
| Ensure that the SUT, having sent an INVITE, on receipt of a re-INVITE
on this dialog, sends a Request Pending (491 Request Pending) response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 14.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_SM_V_001_B | Tx 491 Request Pending (remove To-TAG) |
| Ensure that the SUT, having sent an INVITE, on receipt of a re-INVITE
on this dialog, sends a Request Pending (491 Request Pending) response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 14.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_SM_V_001_C | Tx 491 Request Pending (stablish call, call hold) |
| Ensure that the SUT, having sent an INVITE, on receipt of a re-INVITE
on this dialog, sends a Request Pending (491 Request Pending) response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 14.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_OE_SM_V_002 | Tx 491 Request Pending (Proceeding state) |
| Ensure that the SUT when an INVITE client transaction is in the
Proceeding state, on receipt of an re-INVITE on this dialog, sends a Request Pending (491 Request Pending) response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 14.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ CC/ TE |
Checks TE part of CC signaling |
| ETSI/ CC/ TE/ SIP_CC_TE |
|
| ETSI/ CC/ TE/ SIP_CC_TE/ SIP_CC_TE_CE_V |
|
| SIP_CC_TE_CE_V_001 | Tx Success/prov. on Rx INVITE Rq |
| Ensure the SUT on receipt of an INVITE request, sends a Success (200
OK) or a prov. (101-199) response. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 8, 8.2, and 13.3.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_002 | Tx 416 Unsupported URI scheme (PICS) |
| Ensure that the SUT on receipt of an INVITE request with a Request-URI
set with a scheme that it does not support, sends a Unsupported URI scheme (416 Unsupported URI scheme) response. Config: A, E SUT: User Agent Status: PICS: A.18/4.14 Status/Sending Ref: RFC3261 [1] section 8.2.2.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_002_b | Tx 416 Unsupported URI scheme (b) |
| Ensure that the SUT on receipt of an INVITE request with a Request-URI
set with a scheme that it does not support, sends a Unsupported URI scheme (416 Unsupported URI scheme) response. Config: A, E SUT: User Agent Status: PICS: A.18/4.14 Status/Sending Ref: RFC3261 [1] section 8.2.2.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_003 | Tx 404 Not Found on Rx INVITE Rq |
| Ensure that the SUT on receipt of an INVITE request with a Request-URI
set with an address that it does not accept sends a Not Found (404 Not Found) response. Config: A SUT: User Agent Status: PICS: A.18/5.14 Status/Sending Ref: RFC3261 [1] section 8.2.2.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_004 | Set Timestamp header when answer 100 Trying |
| Ensure that the SUT on receipt of an INVITE request with a Timestamp
header, when it answers with a provisional response Trying (100 Trying), set a Timestamp header with an increased value of the received Timestamp in its response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 8 and 8.2.6.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_004_a | Set Timestamp header when answer 100 Trying |
| Ensure that the SUT on receipt of an INVITE request with a Timestamp
header, when it answers with a provisional response Trying (100 Trying), set a Timestamp header with an increased value of the received Timestamp in its response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 8 and 8.2.6.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_005 | Tx 487 Request Terminated (Expires header=0) |
| Ensure that the SUT on receipt of an INVITE request including an
Expires header set to 0, sends a Request Terminated (487 Request Terminated) response. Config: A SUT: User Agent Status: PICS: A.18/4.23 Status/Sending Ref: RFC3261 [1] section 13.3.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_006 | Include initial offer session description (no message body) |
| Ensure that the SUT on receipt of an INVITE request including no
message body, includes in its first 2xx response an initial offer session description . User Action: Answer call. Test case will tear down call automatically when finished. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 13.2.1 and 13.3.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_006_PRACK | Include initial offer session description (no message body) |
| Ensure that the SUT on receipt of an INVITE request including no
message body, includes in its first 2xx response an initial offer session description . User Action: Answer call. Test case will tear down call automatically when finished. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 13.2.1 and 13.3.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_007 | Include answer in first 2xx response (initial offer description) |
| Ensure that the SUT on receipt of an INVITE request including an
initial offer session description in its message body, includes the answer in its first 2xx response a session description . Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 13.2.1 and 13.3.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_008 | Include initial offer session description in first 2xx response (Contect-Disposition header) |
| Ensure that the SUT on receipt of an INVITE request including a
message body with a Content-Disposition header not set to session value, includes in its first 2xx response an initial offer session description. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 13.2.1 and 13.3.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_009 | Include initial offer session description (Content-disposiotion=optional) |
| Ensure that the SUT on receipt of an INVITE request including a Content-Language header value that it cannot understood and a Content-Disposition header including a handling set to offer session description. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 13.2.1, 13.3.1 and 20.11. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_010 | Tx 415 Unsupported Media Type (empty Content-Disposition) |
| Ensure that the SUT on receipt of an INVITE request including a Content-Language header value that it cannot understood, a Content-Disposition header including a handling empty sends an Unsupported Media Type (415 Unsupported Media Type) response with an Accept header that lists the types of all bodies it understands. Config: A SUT: User Agent Status: PICS: A.18/4.13 Status/Sending Ref: RFC3261 [1] sections 8.2.3, 13.2.1, 13.3.1 and 20.11. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_011 | Tx 415 Unsupported Media Type (Content-Disposition=required, disposition-types=session) |
| Ensure that the SUT on receipt of an INVITE request including a
Content-Language header value that it cannot understood, a Content-Disposition with a handling set to required and a disposition-types set to session, sends an Unsupported Media Type (415 Unsupported Media Type) response with an Accept header that lists the types of all bodies it understands. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 8.2.3, 21.4.13, 13.2.1, 13.3.1 and 20.11. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_012 | Tx 415 Unsupported Media Type (Content-Encoding=content coding values) |
| Ensure that the SUT on receipt of an INVITE request including a
Content-Encoding header set to content coding values that it does not support, sends an Unsupported Media Type (415 Unsupported Media Type) response with an Accept-Encoding header that lists the types of coding that it understands. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 8.2.3, 21.4.13, 13.2.1, 13.3.1 and 20.11. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_013 | Tx 488 Not Acceptable Here (session description not acceptable) |
| Ensure that the SUT on receipt of an INVITE request including a session description that it can understand but it cannot accept, a Content-Disposition with a handling set to required and a disposition-types set to session, sends a Not Acceptable Here (488 Not Acceptable Here) response including a Warning header . Config: A SUT: User Agent Status: Recommended Ref: RFC3261 [1] sections 13.3.1.3 and 21.4.13. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_014 | Tx Success/provisional (From, Call-ID,CSeq, Via) |
| Ensure that the SUT on receipt of an INVITE request, sends a Success
(200 OK) or a provisional (101-199) response including the headers From, Call-ID, CSeq and Via headers copy from the INVITE request. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 8.2.6.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_015 | Tx Succes/provisional (same URI, additional TAG for To) |
| Ensure that the SUT on receipt of an INVITE request with no TAG set on
the To header, sends a Success (200 OK) or a provisional (101-199) response including the same URI and an additional TAG for the To header. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 8.2.6.2, 12.2.2 and 13.3.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_016_Orig | Tx Success/provisional (same URI, same TAG for To) |
| Ensure that the SUT on receipt of an INVITE request with a TAG set on
the To header, sends a Success (200 OK) or a provisional (101-199) response including the same URI and the same TAG for the To header. Config: A, E SUT: User Agent Status: Recommended Ref: RFC3261 [1] section 8.2.6.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_016 | Tx Success/provisional (same URI, same TAG for To) (active call, Tx re-INVITE) |
| Ensure that the SUT on receipt of an INVITE request with a TAG set on
the To header, sends a Success (200 OK) or a provisional (101-199) response including the same URI and the same TAG for the To header. * Uses new media as defined in SDP_M_Attribute_New_TESTER, SDP_M_Format_New_TESTER Config: A, E SUT: User Agent Status: Recommended NOTE: v4.1.1 changed from Mandatory to Recommended. Renamed this test from CC_TE_CE_V_016_New to SIP_CC_TE_CE_V_016. Ref: RFC3261 [1] section 8.2.6.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_017 | Tx Success/provisional (single Contact header) |
| Ensure that the SUT on receipt of an INVITE request, sends a
Success (200 OK) or a provisional (101-199) response including a single Contact header. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 12.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_018 | Tx Success/provisional (Record-Route header, same order) |
| Ensure that the SUT on receipt of an INVITE request including a Record-Route header, sends a Success (200 OK) or a provisional (101-199) response including a Record-Route header copy from the INVITE request, in the same order. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 12.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_019 | Tx Success/Provisional (Record-Route header, unknown parameters) |
| Ensure that the SUT on receipt of an INVITE request including a
Record-Route header with parameters that it does not understand, sends a Success (200 OK) or a provisional (101-199) response including a Record-Route header copy from the INVITE request, with the unknown parameters. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 12.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_020 | Tx Success/provisional (From, no TAG) |
| Ensure that the SUT on receipt of an INVITE request including From
header without tag, sends a Success (200 OK) or a provisional (101-199) response including a From header without tag. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 12.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_021 | Tx Success (Allow, Supported) |
| Ensure that the SUT having received an INVITE request, sends a Success
(200 OK) including an Allow and a Supported headers. Config: A SUT: User Agent Status: Recommended Ref: RFC3261 [1] section 13.3.1.4. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_022 | Repeat last response (same branch parameter, sent-by value) (Proceeding state) |
| Ensure that the SUT when a server INVITE transaction is in the
Proceeding state, on receipt of an INVITE request, including a Via header set with the same branch parameter and sent-by value in the topmost list value, repeats its last response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 17.2.1 and 17.2.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_023 | Repeat last response (no branch parameter) (Proceeding state) |
| Ensure that the SUT when a server INVITE transaction is in the Proceeding state, on receipt of an INVITE request, including a Via header set with no branch parameter but with the Request-URI, To tag, From tag, Call-ID, CSeq and top Via identical as in the first INVITE request, repeats its last response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 17.2.1 and 17.2.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_024 | Repeat last response (different branch parameter, no magic cookie) (Proceeding state) |
| Ensure that the SUT when a server INVITE transaction is in the
Proceeding state, on receipt of an INVITE request, including a Via header set with a branch parameter without the magic cookie z9hG4bK but with the Request-URI, To tag, From tag, Call-ID, CSeq and top Via identical as in the first INVITE request, repeats its last response Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 17.2.1 and 17.2.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_025 | Repeat last response (same branch parameter, sent-by value) (Completed state) |
| Ensure that the SUT when a server INVITE transaction is in the
Completed state, on receipt of an INVITE request, including a Via header set with the same branch parameter and sent-by value in the topmost list value, repeats its last response. Config: A SUT: User Agent Status: Recommended Ref: RFC3261 [1] sections 17.2.1 and 17.2.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_026 | Repeat last response (no branch parameter) (Completed state) |
| Ensure that the SUT when a server INVITE transaction is in the
Completed state, on receipt of an INVITE request, including a Via header set with no branch parameter but with the Request-URI, To tag, From tag, Call-ID, CSeq and top Via identical as in the first INVITE request, repeats its last response. Config: A SUT: User Agent Status: Recommended Ref: RFC3261 [1] sections 17.2.1 and 17.2.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_027 | Repeat last response (different branch parameter, no magic cookie) (Completed state) |
| Ensure that the SUT when a server INVITE transaction is in the
Completed state, on receipt of an INVITE request, including a Via header set with a branch parameter without the magic cookie top Via identical as in the first INVITE request, repeats its last response. Config: A SUT: User Agent Status: Recommmended Ref: RFC3261 [1] sections 17.2.1 and 17.2.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_028 | Tx 482 Loop Detected (different branch parameter, magic cookie) |
| Ensure that the SUT when a server INVITE transaction is in the
Proceeding state, on receipt of an INVITE request, including a Via header set with a different branch parameter starting with the magic cookie z9hG4bK but with the Request-URI, To tag, >From tag, Call-ID and CSeq identical as in the first INVITE request, sends a Loop Detected (482 Loop Detected) response. Config: A SUT: User Agent Status: Recommended Ref: RFC3261 [1] sections 8.2.2.2, 17.2.1 and 17.2.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_029 | Tx 482 Loop Detected (identical branch parameter, magic cookie, different sent-by value) |
| Ensure that the SUT when a server INVITE transaction is in the
Proceeding state, on receipt of an INVITE request, including a Via header set to an identical branch parameter starting with the magic cookie To tag, From tag, Call-ID and CSeq identical as in the first INVITE request, sends a Loop Detected (482 Loop Detected) response. Config: A SUT: User Agent Status: PICS: A.18/4.19 Status/Sending Ref: RFC3261 [1] sections 8.2.2.2, 17.2.1 and 17.2.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_030 | Tx 482 Loop Detected (different value) |
| Ensure that the SUT when a server INVITE transaction is in the
Proceeding state, on receipt of an INVITE request, including a top Via header set to a different value but with the Request-URI, To tag, From tag, Call-ID and CSeq identical as in the first INVITE request, sends a Loop Detected (482 Loop Detected) response Config: A SUT: User Agent Status: PICS: A.18/4.19 Status/Sending Ref: RFC3261 [1] sections 8.2.2.2, 17.2.1 and 17.2.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_031 | Tx 420 Bad Extension (options in Unsupported header) |
| Ensure that the SUT on receipt of an INVITE request with a Require
header set to an option value that the SUT does not support, sends a Bad Extension (420 Bad Extension) response including those options in the Unsupported header. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 8.2.2.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_032 | Enter Completed state (after Tx 4XX response) |
| Ensure that the SUT when a server INVITE transaction is in the Proceeding state, after sending a 4XX response, enters in the Completed state. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 17.2.3.1 and 13.3.1.4, figure 7. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_033 | Enter Confirmed transaction state |
| Ensure that the SUT when a server INVITE transaction is in the Completed state, on receipt of an ACK request, enters in the Confirmed transaction state. User Action: None Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 17.2.3.1 and 13.3.1.4, figure 7. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_034 | Tx 401 Unauthorized (no Authorization header in INVITE) |
| Ensure that the SUT when a server INVITE request not including
an Authorization header field, sends an Unauthorized (401 Unauthorized) response, containing a WWW-Authenticate header. User Action: No action. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 22.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_035 | Tx 401 Unauthorized (realm, nonce HTTP parameters) |
| Ensure that the SUT when a server INVITE request not including
an Authorization header field, sends an Unauthorized (401 Unauthorized) response, containing a WWW-Authenticate header including proper value for realm and nonce HTTP parameters. User Action: No action. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 22.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_V_036 | Tx Success after Tx 401 Unauthorized on Rx INVITE (valid Authorization header field) |
| Ensure that the SUT having sent an Unauthorized (401 Unauthorized)
response to an INVITE request, on receipt of an INVITE request including a valid Authorization header field, sends a Success (200 OK) response. User Action: Answer Call. Test case will tear down call automatically when finished. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 22.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ CC/ TE/ SIP_CC_TE/ SIP_CC_TE_CE_I |
|
| SIP_CC_TE_CE_I_001 | Enter Confirmed transaction state (Proxy-Require header) |
| Ensure that the SUT when a server INVITE transaction is in the
Completed state, on receipt of an ACK request including a Proxy-Require header set with an option-tag that it does not support, enters in the Confirmed transaction state. Pre-condition: User Action: Answer Call. Test case will tear down call automatically when finished. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 17.2.3 and 8.2.2.3, figure 7. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_I_002 | Enter Confirmed transaction state (Require header) |
| Ensure that the SUT when a server INVITE transaction is in the
Completed state, on receipt of an ACK request including a Require header set with an option-tag that it does not support, enters in the Confirmed transaction state. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 17.2.3 and 8.2.2.3, figure 7. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ CC/ TE/ SIP_CC_TE/ SIP_CC_TE_CE_TI |
|
| SIP_CC_TE_CE_TI_001 | Repeat response on timeout (timer G=T1) (unreliable transport) |
| If an unreliable transport is used, ensure that the SUT, when an
INVITE server transaction is in the Completed state repeats its response on the timeout condition of timer G set with a value of T1. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] annex A and section 17.2.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_TI_002 | No repeat response on timeout (timer G=T1) (reliable transport (TCP)) |
| If a reliable transport (TCP) is used, ensure that the SUT, when an
INVITE server transaction is in the Completed state does not repeat its response on the timeout condition of timer G set with a value of T1. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] annex A and section 17.2.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_TI_003 | Repeat response (timer G=MIN (2*T1,T2) value expires) (unreliable transport) |
| If an unreliable transport is used, ensure that the SUT, when an
INVITE server transaction is in the Completed state and having already sent twice times its response, repeats it after timer G set MIN(2*T1,T2) value expires. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] annex A and section 17.2.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_TI_004 | Repeat response (timer G= MIN (4*T1, T2) value expires) (unreliable transport) |
| If an unreliable transport is used, ensure that the SUT, when an
INVITE server transaction is in the Completed state and having already sent three times its response, repeats it after timer G set the MIN(4*T1,T2) value expires. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] annex A and section 17.2.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_TI_005 | Enter Terminated state (timer H=64*T1 expires) |
| Ensure that the SUT, when an INVITE server transaction is in the
Completed state and, enters in the Terminated state after timer H set to 64*T1 expires. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] annex A and section 17.2.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_TI_006 | No repeat response (timer H=64*T1 value expires) |
| If an unreliable transport is used, ensure that the SUT, when an
INVITE server transaction is in the Completed state and, does not repeat its response after timer H set to 64*T1 value expires. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] annex A and section 17.2.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_TI_007 | Enter Terminated state (time l=T4 value expires) (unreliable transport) |
| If an unreliable transport is used, ensure that the SUT, when an
INVITE server transaction is in the Confirmed state, enters in the Terminated state after timer I set to T4 value expires. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] annex A and section 17.2.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_TI_008 | Enter immediately Terminated state (reliable transport) |
| If a reliable transport is used, ensure that the SUT, when an INVITE
server transaction is in the Confirmed state, enters immediately in the Terminated state. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] annex A and section 17.2.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_TI_009 | Repeat 2xx response (T1 expires) |
| Ensure that the SUT, when it has answered to an INVITE request with
2xx response, repeats it after T1 duration expires without receiving an ACK request. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] annex A and section 13.3.1.4. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_TI_010 | Repeat 2xx response (2*T1 expires) |
| Ensure that the SUT, when it has already answered two times to an
INVITE request with a 2xx response, repeats it after 2*T1 duration expires without receiving an ACK request. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] annex A and section 13.3.1.4. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_TI_011 | No repeat 2xx response (T2 expires) |
| Ensure that the SUT, does not repeat its 2XX response to an INVITE
request after 64*T1 duration expires without receiving an ACK request. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] annex A and section 13.3.1.4. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CE_TI_012 | Tx BYE Rq (no ACK to 2xx response, 64*T1) |
| Ensure that the SUT, when it has receive no ACK to its 2xx responses
during a duration of 64*T1 seconds, sends a BYE request. Config: A SUT: User Agent Status: Recommended Ref: RFC3261 [1] annex A and section 13.3.1.4. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ CC/ TE/ SIP_CC_TE/ SIP_CC_TE_CR_V |
|
| SIP_CC_TE_CR_V_001 | Tx Success (established session) |
| Ensure that the SUT while a session has been established, on receipt
of a BYE request sends a Success (200 OK) response. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 15. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CR_V_002 | Tx Success (early stage dialog) |
| Ensure that the SUT while a dialog is in an early stage, on receipt of
a BYE request sends a Success (200 OK) response. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 15 and 12. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CR_V_003 | Tx Success (confirmed stage dialog) |
| Ensure that the SUT while a dialog is in a confirmed stage, on receipt
of a BYE request sends a Success (200 OK) response. User Action: Answer call. Test case will tear down automatically when finished. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 15 and 12. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CR_V_004 | Tx Success (not understandable header) |
| Ensure that the SUT once a dialog has been established, on receipt of
a BYE request including a header that it does not understand sends a Success (200 OK) response. Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 8.2.2 and 15.1.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CR_V_005 | Tx 420 Bad Extension (Unsupported=option-tag) |
| Ensure that the SUT, once a dialog has been established, on receipt of a BYE request including a Require header set with an option-tag that it does not support, sends a Bad Extension (420 Bad Extension) response including a Unsupported set with this option-tag. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 8.2.2 and 15.1.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CR_V_006 | Tx Success (From,Call-ID CSeq, Via) (established dialog) |
| Ensure that the SUT, once a dialog has been established, on receipt of a BYE request, sends a Success (200 OK) response with From, Call-ID, CSeq and Via headers set to the same value as in the request Config: A, E SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 8.2.6.2 and 15.1.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CR_V_007 | Tx 481 Call/Transaction does not exist (no established dialog) |
| Ensure that the SUT, while no dialog has been established, on receipt of a BYE request, sends a Call/Transaction does not exist (481 Call/Transaction does not exist). Config: A SUT: User Agent Status: PICS: A.20/4 11 Status/Sending Ref: RFC3261 [1] section 15.1.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CR_V_008 | Tx 481 Call/Transaction does not exist (no TAG) |
| Ensure that the SUT, while a dialog has been established, on receipt of a BYE request without TAG in the To header, sends a Call/Transaction does not exist (481 Call/Transaction does not exist). Config: A SUT: User Agent Status: PICS: A.20/4 11 Status/Sending Ref: RFC3261 [1] section 15.1.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CR_V_009 | Tx Success (same CSeq value) (established dialog) |
| Ensure that the SUT, once a dialog has been established, on receipt of a BYE request including a CSeq header set with a more than one higher value as in the previous request, sends a Success (200 OK) response with the same CSeq value. Config: A SUT: User Agent Status: Recommended Ref: RFC3261 [1] section 12.2.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CR_V_010 | Tx BYE Rq (To=From of previous Rx Rq) (established dialog) |
| Ensure that the SUT once a dialog has been established, to release it sends a BYE request with a To header set to the same value as in the From header of the previous received request. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 12.2.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CR_V_011 | Tx BYE Rq (From=To of last Tx response) (established dialog) |
| Ensure that the SUT once a dialog has been established, to release it sends a BYE request with a From header set to the same value as in the To header of the last sent response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 12.2.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CR_V_012 | Tx BYE Rq (Request-URI=Contact-URI, no Route) (established dialog) |
| Ensure that the SUT once a dialog has been established with an INVITE request including no Record-Route header set, to release it sends a BYE request with the Request-URI set to the Contact URI included in the original INVITE request and with no Route header set. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 12.2.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CR_V_013 | Tx BYE Rq, no lr parameter (Route=reverse order list of Record-Route) (established dialog) |
| Ensure that the SUT once a dialog has been established with an INVITE request including a Record-Route header set to a list in which the last element does not contain the lr parameter, to release the call, sends a BYE request with the Request-URI set to the Contact URI and a Route header set to the list in a reverse order of the Record-Route included in the original INVITE request. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 12.2.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CR_V_014 | Tx BYE, lr parameter (Request-URI=lr parameter, Route=remainder list) (established dialog) |
| Ensure that the SUT once a dialog has been established with an INVITE request including a Record-Route header set to a list in which the last element contains a lr parameter, to release the call, sends a BYE request with the Request-URI set to this element and a Route header set to the remainder list in a reverse order of the received Record-Route appended with the received Contact URI. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 12.2.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CR_V_015 | Tx Success on receipt of CANCEL |
| Ensure that the SUT when a server INVITE transaction is in the Proceeding state, on receipt of a CANCEL, sends a Success (200 Success) response. Config: A SUT: User Agent Status: Recommended Ref: RFC3261 [1] section 9.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CR_V_016 | Tx 487 Request Terminated on Rx CANCEL |
| Ensure that the SUT when a server INVITE transaction is in the
Proceeding state, on receipt of a CANCEL answers to the original INVITE, request with a Request Terminated (487 Request Terminated) response. Config: A SUT: User Agent Status: PICS: A.18/23 Status/Sending Ref: RFC3261 [1] section 9.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CR_V_017 | Tx 481 Call Leg/Transaction Does Not Exist (different branch parameter) |
| Ensure that the SUT when a server INVITE transaction is in the Proceeding state, on receipt of a CANCEL request including a Via header set with a different branch parameter starting with the magic cookie z9hG4bK but with the Request-URI, To tag, From tag, Call-ID and CSeq identical as in the original INVITE request, sends a Call Leg/Transaction Does Not Exist (481 Call Leg/Transaction Does Not Exist) response. Config: A SUT: User Agent Status: PICS: A.21/4.11 Status/Sending Ref: RFC3261 [1] section 9.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CR_V_018 | Tx 481 Call Leg/Transaction Does Not Exist (identical branch parameter) |
| Ensure that the SUT when a server INVITE transaction is in the Proceeding state, on receipt of a CANCEL request including a Via header set to an identical branch parameter starting with the magic cookie z9hG4bK and a different sent-by value, but with the Request-URI, To tag, From tag, Call-ID and CSeq identical as in the original INVITE request, sends a Call Leg/Transaction Does Not Exist (481 Call Leg/Transaction Does Not Exist) response. Config: A SUT: User Agent Status: PICS: A.21/4.11 Status/Sending Ref: RFC3261 [1] section 9.2 and 17.2.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CR_V_019 | Tx 481 Call Leg/Transaction Does Not Exist (top Via=different value) |
| Ensure that the SUT when a server INVITE transaction is in the Proceeding state, on receipt of a CANCEL request, including a top Via header set to a different value but with the Request-URI, To tag, From tag, Call-ID and CSeq identical as in the original INVITE request, sends a Call Leg/Transaction Does Not Exist (481 Call Leg/Transaction Does Not Exist) response. Config: A SUT: User Agent Status: PICS: A.21/4.11 Status/Sending Ref: RFC3261 [1] section 9.2 and 17.2.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CR_V_020 | Repeat last response before timer J fires (same branch parameter) |
| Ensure that the SUT, having already answer to a BYE request, on receipt of a BYE request, before timer J fires, including a Via header set with the same branch parameter in the topmost list value, repeats its last response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 17.2.3, 17.2.2, 12.2.1.1 and 15.1.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CR_V_021 | Repeat last response before timer J fires (no branch parameter) |
| Ensure that the SUT, having already answer to a BYE request, on receipt of a BYE request, before timer J fires, including a Via header set with no branch parameter but with the Request-URI, To tag, From tag, Call-ID and CSeq identical as in the first BYE request, repeats its last response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 17.2.3, 17.2.2 and 15.1.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CR_V_022 | Repeat last response before timer J fires (different branch parameter) |
| Ensure that the SUT, having already answer to a BYE request, on receipt of a BYE request, before timer J fires, including a Via header set with a different branch parameter but with the Request-URI, To tag, >From tag, Call-ID and CSeq identical as in the first BYE request, repeats its last response. Config: A SUT: User Agent Status: Void NOTE: This test deprecated in v4.1.1 Ref: RFC3261 [1] sections 17.2.3, 17.2.2, 12.2.1.1 and 15.1.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ CC/ TE/ SIP_CC_TE/ SIP_CC_TE_CR_I |
|
| SIP_CC_TE_CR_I_001 | Tx 500 Server Internal Error (CSeq=lower value) |
| Ensure that the SUT on receipt of a BYE request with a CSeq number set
to a lower value than in the preceding INVITE request, sends a 500 (Server Internal Error) response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 12.2.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CR_I_002 | Tx Success (Require=not supported option-tag) |
| Ensure that the SUT when a server INVITE transaction is in the
Proceeding state, on receipt of a CANCEL request including a Require header set with an option-tag that it does not support, sends a Success (200 OK) response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 8.2.2.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CR_I_003 | Tx Success (Proxy-Require=not supported option-tag) |
| Ensure that the SUT when a server INVITE transaction is in the
Proceeding state, on receipt of a CANCEL request including a Proxy-Require header set with an option-tag that it does not support, sends a Success (200 OK) response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 8.2.2.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CR_I_004 | Tx 481 Call/transaction Does Not Exist (Rx CANCEL, no session initiated) |
| Ensure that the SUT while no session has been initiated, on receipt of a CANCEL request, sends a Call/transaction Does Not Exist (481 Call/ transaction Does Not Exist) response. Config: A SUT: User Agent Status: PICS: A.21/4.11 Status/Sending Ref: RFC3261 [1] sections 9.2 and 15.1.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_CR_I_005 | Tx 481 Call/transaction Does Not Exist (Rx BYE, session released) |
| Ensure that the SUT, while a session has been released, on receipt of
a BYE request, sends a Call/transaction Does Not Exist (481 Call/transaction Does Not Exist) response. Config: A SUT: User Agent Status: PICS: A.21/4.11 Status/Sending Ref: RFC3261 [1] section 15.1.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ CC/ TE/ SIP_CC_TE/ SIP_CC_TE_CR_TI |
|
| SIP_CC_TE_CR_TI_001 | Retransmit response until timer J=64*T1 expires |
| If an unreliable transport is used, ensure that the SUT, when a BYE server transaction is in the Completed state, on receipt of the repetitions of the BYE request, retransmits its response until the timer J set to 64 * T1 expires. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] annex A and section 17.2.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ CC/ TE/ SIP_CC_TE/ SIP_CC_TE_SM_V |
|
| SIP_CC_TE_SM_V_001 | Tx Success (higher CSeq, new complete session description) |
| Ensure that the SUT while a session has been established, on receipt
of a re-INVITE request with a higher CSeq and a new complete session description sends a Success (200 OK) response including the last received CSeq. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 14. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_SM_V_002 | Tx Success (no session description) |
| Ensure that the SUT while a session has been established, on receipt
of a re-INVITE request with no session description sends a Success (200 OK) response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 14. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_TE_SM_V_003 | Tx BYE Rq (after Tx Success to re-INVITE, no Rx ACK Msg) |
| Ensure that the SUT having sent a Success (200 OK) response to a re-INVITE request and receiving no ACK message, sends a BYE request for the dialog. Config: A SUT: User Agent Status: Recommended Ref: RFC3261 [1] section 14. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ CC/ TE/ SIP_CC_TE/ SIP_CC_TE_SM_I |
|
| SIP_CC_TE_SM_I_001 | Tx 500 Server Internal Error (Retry-After=randomly chosen value 0 & 10 seconds) |
| Ensure that the IUT when an INVITE server transaction is in the
Proceeding state (no final response sent), on receipt of a re-INVITE with a higher CSeq values, sends a Server Internal Error (500 Server Internal Error) response including a Retry-After header set to a randomly chosen value between 0 and 10 seconds. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 14.2 paragraph 2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ CC/ PR |
Checks PR part of CC signaling |
| ETSI/ CC/ PR/ SIP_CC_PR_MP_RQ_V |
|
| SIP_CC_PR_MP_RQ_V_001A | Tx 416 Unsupported URI Scheme (Request-URI scheme not understandable) |
| Ensure that the SUT on receipt of an INVITE request with a Request-URI
with a scheme that it does not understand, sends a Unsupported URI Scheme (416 Unsupported URI Scheme) request failure response. Config: B SUT: Proxy Status: Recommended Ref: RFC3261 [1] section 16.3 item 2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_001B | Tx 416 Unsupported URI Scheme (CANCEL not correspond to scheme) |
| Ensure that the SUT on receipt of a CANCEL request that does not
correspond to an existing context with a Request-URI with a scheme that it does not understand, sends a Unsupported URI Scheme (416 Unsupported URI Scheme) request failure response. User Action: None. Config: B SUT: Proxy Status: Recommended Ref: RFC3261 [1] section 16.3 item 2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_002 | Tx 483 Too many hops (INVITE Rq, Max-Forward=0) |
| Ensure that the SUT on receipt of an INVITE request including a
Max-Forwards header set to 0, sends a Too many hops (483 Too many hops) request failure response. User Action: None. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.3 item 3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_003 | Tx 420 Bad Extension (INVITE Rq, Proxy-Require=not understandable value) |
| Ensure that the SUT on receipt of an INVITE request including a
Proxy-Require header set to a value it does not understand, sends a Bad Extension (420 Bad Extension) request failure response including a list of the options that it does not support in the Unsupported header. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.3 item 5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_004 | Fwd INVITE Rq (remove maddr & not default port/transport parameter) |
| Ensure that the SUT on receipt of an INVITE request with the
Request-URI with a maddr parameter indicating a value the proxy is responsible for and the request was received using the port and transport indicated, removes the maddr and any non default port or transport parameter from the request and forwards the message. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.4. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_005 | Fwd INVITE Rq (remove value from Rq) |
| Ensure that the SUT on receipt of an INVITE request including a Route
header with the first value indicates the SUT, removes that value from the request and forwards the message. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.4. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_006 | Fwd INVITE Rq to target (proxy responsible for value in maddr parameter) |
| Ensure that the SUT on receipt of an INVITE request with the
Request-URI with a maddr parameter, indicating a value the proxy is responsible for, forwards the message to the target indicated in the Request-URI. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_007 | Fwd INVITE Rq to target (proxy not responsible for domain in Request-URI) |
| Ensure that the SUT on receipt of an INVITE request with the
Request-URI, indicating a domain the proxy is not responsible for, forwards the message to the target indicated in the Request-URI. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_008 | Tx 485 Ambiguous (no sufficient info in Request-URI) |
| Ensure that the SUT on receipt of an INVITE request, which Request-URI
does not contain sufficient information to determine the target set, sends back an Ambiguous (485 Ambiguous) request failure response. Config: B SUT: Proxy Status: Recommended Ref: RFC3261 [1] section 16.5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_009 | Tx 404 Not found (no resource at proxy) |
| Ensure that the SUT on receipt of an INVITE request with a
Request-URI, indicating a resource, which does not exist at this proxy, sends back a Not found (404 Not found) request failure response. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_011 | Fwd INVITE Rq (Max-Forward=5) |
| Ensure that the SUT on receipt of an INVITE request including a
Max-Forwards header set to 5, forwards it after having decreasing this counter of one. Config: B SUT: Proxy Status: Mandatory Ref: 16.6 item 3 [1] ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) / IETF SIP RFC3261 12.2.2 [1] | |
| SIP_CC_PR_MP_RQ_V_012 | Fwd INVITE Rq (Max-Forwards=1) |
| Ensure that the SUT on receipt of an INVITE request including a
Max-Forwards header set to 1, forwards it after having decreasing the Max-Forwards by one [i.e. setting it to 0]. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.6 item 3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_013 | Fwd INVITE Rq, add Max-Forwards (no Max-Forwards) |
| Ensure that the SUT on receipt of an INVITE request, without a
Max-Forwards header, forwards it after having added a Max-Forwards header. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.6 item 3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_014 | Fwd INVITE Rq, Max-Forwards=70 (no Max-Forwards) |
| Ensure that the SUT on receipt of an INVITE request, without a
Max-Forwards header, forwards it after having added a Max-Forwards header with the value set to 70. Config: B SUT: Proxy Status: Recommended Ref: RFC3261 [1] section 16.6 item 3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_015 | Fwd INVITE Rq (no lr parameter) |
| Ensure that the SUT on receipt of an INVITE request with a Route
header, and the first URI of this Route does not contain a lr parameter, put the Request-URI into the last position of the Route header, and put the first value of the Route header into the Request-URI, and then forwards the message. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.6 item 6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_016 | Fwd INVITE Rq (lr parameter) |
| Ensure that the SUT on receipt of an INVITE request with a Route
header, and the first URI of this Route containing a lr parameter, forwards the message to the address in the first element of Route header. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] sections 16.6 item 7. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_017 | Fwd INVITE Rq to address in Request-URI (no Route) |
| Ensure that the SUT on receipt of an INVITE request without a Route
header, forwards the message to the address in the Request-URI. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.6 item 7. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_018 | Fwd INVITE Rq (protocol name/version=SIP/2.0, branch parameter) |
| Ensure that the SUT on receipt of an INVITE request forwards the
message after having inserted in first position a Via header set to its location with a protocol name set to SIP, a protocol version set to 2.0 and a branch parameter beginning with the received list of Via headers. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.6, item 8 and 8.1.1.7. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_019 | Fwd ACK Rq (remove maddr & not default port/transport parameter) |
| Ensure that the SUT on receipt of an ACK request with the Request-URI
with a maddr parameter indicating a value the proxy is responsible for and the request was received using the port and transport indicated, removes the maddr and any non default port or transport parameter from the request and forwards the message. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.4. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_020 | Fwd ACK Rq(remove Route first value) |
| Ensure that the SUT on receipt of an ACK request including a Route
header with the first value indicates the SUT, removes that value from the request and forwards the message. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.4. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_021 | Fwd ACK Rq (proxy not responsible for maddr parameter value in Request-URI) |
| Ensure that the SUT on receipt of an ACK request with the Request-URI
with a maddr parameter, indicating a value the proxy is not responsible for, forwards the message to the target indicated in the Request-URI. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_022 | Fwd ACK Rq (proxy not responsible for domain in Request-URI) |
| Ensure that the SUT on receipt of an ACK request with the Request-URI,
indicating a domain the proxy is not responsible for, forwards the message to the target indicated in the Request-URI. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_023 | Fwd ACK Rq (Max-Forwards=5) |
| Ensure that the SUT on receipt of an ACK request including a
Max-Forwards header set to 5, forwards after having decreasing this counter of one. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.6 item 3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_024 | Fwd ACK Rq (Max-Forwards=1) |
| Ensure that the SUT on receipt of an ACK request including a
Max-Forwards header set to 1, forwards it after having decreasing the Max-Forwards by one [i.e. setting it to 0]. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.6 item 3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_025 | Fwd ACK Rq (no Max-Forwards) |
| Ensure that the SUT on receipt of an ACK request without a
Max-Forwards header, forwards it after having added a Max-Forwards header. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.6 item 3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_026 | Fwd ACK Rq,(Max-Forwards value=70) |
| Ensure that the SUT on receipt of an ACK request without a
Max-Forwards header, forwards it after having added a Max-Forwards header with the value set to 70. Config: B SUT: Proxy Status: Recommended Ref: RFC3261 [1] section 16.6 item 3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_027 | Fwd ACK Rq (no lr parameter) |
| Ensure that the SUT on receipt of an ACK request with a Route header,
and the first URI of this Route does not contain a lr parameter, put the Request-URI into the last position of the Route header, and put the first value of the Route header into the Request-URI, and then forwards the message to the address in the Request-URI. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.6 item 6 and 7. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_029 | Fwd ACK Rq (no Route) |
| Ensure that the SUT on receipt of an ACK request without a Route
header, forwards the message to the address in the Request-URI. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.6 item 7. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_030 | Fwd ACK Rq (protocol name/version=SIP/2.0, branch parameter) |
| Ensure that the SUT on receipt of an ACK request forwards the message
after having inserted in first position a Via header - set to its location with a protocol name set to SIP, a protocol version set to 2.0 and a branch parameter beginning with - to the received list of Via headers. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.6 item 8, and 8.1.1.7. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_031 | Tx 416 Unsupported URI Scheme (Request-URI scheme not understood) |
| Ensure that the SUT on receipt of a CANCEL request that does not
correspond to an existing context with a Request-URI with a scheme that it does not understand, sends a Unsupported URI Scheme (416 Unsupported URI Scheme) request failure response. Config: B SUT: Proxy Status: Recommended Ref: RFC3261 [1] section 16.3, item 2 and 16.10. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_032 | Tx 483 Too many hops (CANCEL Rq, Max-Forwards=0) |
| Ensure that the SUT on receipt of a CANCEL request that does not
correspond to an existing context including a Max-Forwards header set to 0, sends a Too many hops (483 Too many hops) request failure response. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.3, item 3 and 16.10. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_033 | Tx 420 Bad Extension (CANCEL Rq, Proxy-Require=not understandable value) |
| Ensure that the SUT on receipt of a CANCEL request that does not
correspond to an existing context including a Proxy-Require header set to a value that it does not understand, sends a Bad Extension (420 Bad Extension) request failure response including a list of the options that it does not support in the Unsupported header. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.3 item 5, and 16.10. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_034 | Fwd CANCEL Rq (remove maddr/non default port or transport parameter) |
| Ensure that the SUT on receipt of a CANCEL request that does not
correspond to an existing context with the Request-URI with a maddr parameter indicating a value the proxy is responsible for and the request was received using the port and transport indicated, removes the maddr and any non default port or transport parameter from the request and forwards the message. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.4 and 16.10. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_035 | Fwd CANCEL Rq (remove Route first value) |
| Ensure that the SUT on receipt of a CANCEL request that does not
correspond to an existing context including a Route header with the first value indicates the SUT, removes that value from the request and forwards the message. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.4 and 16.10. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_036 | Fwd CANCEL Rq (proxy not responsible for value in maddr parameter) |
| Ensure that the SUT on receipt of a CANCEL request that does not
correspond to an existing context with the Request-URI with a maddr parameter, indicating a value the proxy is not responsible for, forwards the message to the target indicated in the Request-URI. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] sections 16.5 and 16.10. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_037 | Fwd CANCEL Rq (proxy not responsible for domain in Request-URI) |
| Ensure that the SUT on receipt of a CANCEL request that does not
correspond to an existing context with the Request-URI, indicating a domain the proxy is not responsible for, forwards the message to the target indicated in the Request-URI. *Note* - Be sure configuration variable PX_Proxy_Resource_Not_Exist is set to a resource which does not exist. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.5 and 16.10. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_038 | Tx 485 Ambiguous on Rx CANCEL Rq |
| Ensure that the SUT on receipt of a CANCEL request that does not
correspond to an existing context but does not sufficient information to determine the target set, sends back a Ambiguous (485 Ambiguous) request failure response. Config: B SUT: Proxy Status: Recommended Ref: RFC3261 [1] section 16.5 and 16.10. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_039 | Tx 404 Not found on Rx CANCEL Rq (Request-URI resource not in proxy) |
| Ensure that the SUT on receipt of a CANCEL request that does not
correspond to an existing context with the Request-URI, indicating a resource, which does not exist at this proxy, sends back a Not found (404 Not found) request failure response. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.5 and 16.10. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_040 | Tx 480 Temporarily Unavailable on Rx CANCEL Rq (no target to Fwd) |
| Ensure that the SUT on receipt of a CANCEL request that does not
correspond to an existing context but does not find any target to forward, sends back a Temporary Unavailable (480 Temporary Unavailable) request failure response. Config: B SUT: Proxy Status: Recommended Ref: RFC3261 [1] section 16.5 and 16.10. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_041 | Fwd CANCEL Rq (Max-Forwards=5) |
| Ensure that the SUT on receipt of a CANCEL request that does not
correspond to an existing context including a Max-Forwards header set to 5, forwards it after having decreasing this counter of one. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] sections 16.6, item 3 and 16.10. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_042 | Fwd CANCEL Rq (Max-Forwards=1) |
| Ensure that the SUT on receipt of a CANCEL request that does not
correspond to an existing context including a Max-Forwards header set to 1, forwards it after having decreasing this counter of one. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] sections 16.6, item 3 and 16.10. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_043 | Fwd CANCEL Rq (no Max-Forwards) |
| Ensure that the SUT on receipt of a CANCEL request that does not
correspond to an existing context, without a Max-Forwards header, forwards it after having added a Max-Forwards header. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.6, item 3 and 16.10. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_044 | Fwd CANCEL Rq (Max-Forwards=70) |
| Ensure that the SUT on receipt of a CANCEL request that does not
correspond to an existing context, without a Max-Forwards header, forwards it after having added a Max-Forwards header with the value set to 70. Config: B SUT: Proxy Status: Recommended Ref: RFC3261 [1] section 16.6, item 3 and 16.10. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_045 | Fwd CANCEL Rq (Route, no lr parameter) |
| Ensure that the SUT on receipt of a CANCEL request that does not
correspond to an existing context with a Route header, and the first URI of this route does not contain a lr parameter, put the Request-URI into the last position of the Route header, and put the first value of the Route header into the Request-URI, and then forwards the message to the address in the Request-URI. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.6, item 6 and 7 and 16.10. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_046 | Fwd CANCEL Rq (Route, lr parameter) |
| Ensure that the SUT on receipt of a CANCEL request that does not
correspond to an existing context with a Route header, and the first URI of that containing a lr parameter, forwards the message to the address in the first element of Route header. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.6, item 7 and 16.10. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_047 | Fwd CANCEL Rq to address in Request-URI (no Route) |
| Ensure that the SUT on receipt of a CANCEL request that does not
correspond to an existing context without a Route header, forwards the message to the address in the Request-URI. Config: B SUT: Proxy Status: Recommended Ref: RFC3261 [1] section 16.6, item 7 and 16.10. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_048 | Fwd CANCEL Rq (protocol name/version=SIP/2.0, branch parameter) |
| Ensure that the SUT on receipt of a CANCEL request that does not
correspond to an existing context forwards the message after having inserted in first position a Via header - set to its location with a protocol name set to SIP, a protocol version set to 2.0 and a branch parameter beginning with to the received list of Via headers. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.6, item 8, 8.1.1.7 and 16.10. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_049 | Tx 416 Unsupported URI Scheme on Rx BYE Rq (Request-URI scheme not understood) |
| Ensure that the SUT on receipt of a BYE request with a Request-URI
with a scheme that it does not understand, sends a Unsupported URI Scheme (416 Unsupported URI Scheme) request failure response. Config: B SUT: Proxy Status: Recommended Ref: RFC3261 [1] section 16.3 item 2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_050 | Tx 483 Too many hops on Rx BYE Rq (Max-Forwards=0) |
| Ensure that the SUT on receipt of a BYE request including a
Max-Forwards header set to 0, sends a Too many hops (483 Too many hops) request failure response. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.3 item 3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_051 | Tx 420 Bad Extension on Rx BYE (Proxy-Require value not understood) |
| Ensure that the SUT on receipt of a BYE request including a
Proxy-Require header set to a value that it does not understand, sends a Bad Extension (420 Bad Extension) request failure response including a list of the options that it does not support in the Unsupported header. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.3 item 5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_052 | Fwd BYE Rq (remove maddr/non default port or transport) |
| Ensure that the SUT on receipt of a BYE request with the Request-URI
with a maddr parameter indicating a value the proxy is responsible for and the request was received using the port and transport indicated, removes the maddr and any non default port or transport parameter from the request and forwards the message. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.4. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_053 | Fwd BYE Rq (remove first value in Route) |
| Ensure that the SUT on receipt of a BYE request including a Route
header with the first value indicates the SUT, removes that value from the request and forwards the message. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.4. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_054 | Fwd BYE Rq (proxy not responsible for value in maddr parameter) |
| Ensure that the SUT on receipt of a BYE request with the Request-URI
with a maddr parameter, indicating a value the proxy is not responsible for, forwards the message to the target indicated in the Request-URI. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_055 | Fwd BYE Rq (proxy not responsible for domain in Request-URI) |
| Ensure that the SUT on receipt of a BYE request with the Request-URI,
indicating a domain the proxy is not responsible for, forwards the message to the target indicated in the Request-URI. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_056 | Tx 485 Abiguous on Rx BYE Rq |
| Ensure that the SUT on receipt of a BYE request but does not contain
sufficient information to determine the target set, sends back a Ambiguous (485 Ambiguous) request failure response. Config: B SUT: Proxy Status: Recommended Ref: RFC3261 [1] section 16.5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_057 | Tx 404 Not found on Rx BYE Rq (Request-URI resource not in proxy) |
| Ensure that the SUT on receipt of a BYE request with the Request-URI,
indicating a resource, which does not exist at this proxy, sends back a Not found (404 Not found) request failure response. *Note* - Be sure configuration variable PX_Proxy_Resource_Not_Exist is set to a resource which does not exist. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_058 | Tx 480 Temporarily Unavailable on Rx BYE Rq (no target to Fwd) |
| Ensure that the SUT on receipt of a BYE request but does not find any
target to forward, sends back a Temporary Unavailable (480 Temporary Unavailable) request failure response. Config: B SUT: Proxy Status: Recommended Ref: RFC3261 [1] section 16.5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_059 | Fwd BYE Rq (Max-Forwards=5) |
| Ensure that the SUT on receipt of a BYE request including a
Max-Forwards header set to 5, forwards it after having decreasing this counter of one. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.6 item 3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_060 | Fwd BYE Rq (Max-Forwards=1) |
| Ensure that the SUT on receipt of a BYE request including a
Max-Forwards header set to 1, forwards it after having decreasing the Max-Forwards by one [i.e. setting it to 0]. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.6 item 3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_061 | Fwd BYE Rq (no Max-Forwards) |
| Ensure that the SUT on receipt of a BYE request, without a
Max-Forwards header, forwards it after having added a Max-Forwards header. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.6 item 3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_062 | Fwd BYE Rq (max-Forwards=70) |
| Ensure that the SUT on receipt of a BYE request, without a
Max-Forwards header, forwards it after having added a Max-Forwards header with the value set to 70. Config: B SUT: Proxy Status: Recommended Ref: RFC3261 [1] section 16.6 item 3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_063 | Fwd BYE Rq (Route, no lr parameter) |
| Ensure that the SUT on receipt of a BYE request with a Route header,
and the first URI of this route does not contain a lr parameter, put the Request-URI into the last position of the Route header, and put the first value of the Route header into the Request-URI, and then forwards the message to the address in the Request-URI. Config: B SUT: Proxy Status: Mandaory Ref: RFC3261 [1] section 16.6, item 6 and 7. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_064 | Fwd BYE Rq (Route, lr parameter) |
| Ensure that the SUT on receipt of a BYE request with a Route header,
and the first URI of that containing a lr parameter, forwards the message to the address in the first element of Route header. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.6, item 7. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_065 | Fwd BYE Rq (no Route) |
| Ensure that the SUT on receipt of a BYE request without a Route
header, forwards the message to the address in the Request-URI. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.6, item 7. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_066 | Fwd BYE Rq (protocol name/version=SIP/2.0, branch parameter) |
| Ensure that the SUT on receipt of a BYE request forwards the message
after having inserted in first position a Via header - set to its location with a protocol name set to SIP, a protocol version set to 2.0 and a branch parameter beginning with Precondition: User Action: None. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.6, item 8 and 8.1.1.7. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_V_067 | Fwd INVITE Rq (determined target=two URIs) |
| Ensure that the SUT on receipt of an INVITE request and the determined
target set is containing two URIs forwards the message(forking) to both URIs. Precondition: User Action: The proxy must be configured to send out a forked INVITE. L1 is the sender of the INVITE. The proxy must be configured to fork this INVITE to the URIs on L2 and L3. Also links L1, L2 and L3 must be configured. Config: B SUT: Proxy Status: PICS: A.77/1.4 Ref: RFC3261 [1] section 16.6, item 7 and 10 and section 16.5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ CC/ PR/ SIP_CC_PR_MP_RQ_I |
|
| SIP_CC_PR_MP_RQ_I_001 | Remove not allowed parameter before Fwd INVITE Rq |
| Ensure that the SUT on receipt of an INVITE request with the
Request-URI containing a not allowed parameter, removes this parameter from the Request-URI before forwarding that message. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.6, item 2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_I_002 | Remove not allowed parameter before Fwd ACK Rq |
| Ensure that the SUT on receipt of an ACK request, with the Request-URI
containing a not allowed parameter, removes that parameter from the Request-URI before forwarding that message. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.6, item 2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_I_003 | Remove not allowed parameter before Fwd CANCEL Rq |
| Ensure that the SUT on receipt of a CANCEL request with the
Request-URI containing a not allowed parameter, removes that parameter from the Request-URI before forwarding that message. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.6, item 2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RQ_I_004 | Remove not allowed parameter before Fwd BYE Rq |
| Ensure that the SUT on receipt of a BYE request with the Request-URI
containing a not allowed parameter, removes that parameter from the Request-URI before forwarding that message. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.6, item 2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ CC/ PR/ SIP_CC_PR_MP_RS_V |
|
| SIP_CC_PR_MP_RS_V_001 | Fwd Success (delete topmost Via) |
| Ensure that the SUT on receipt of a SUCCESS (200 OK) response with the
topmost Via header including its own location, deletes that header and forwards the message to the address indicated in the next Via header value. then tear down call with BYE on PCO2, followed by 200 OK on PCO1 ** Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.7 and 16.11. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_002 | No Fwd Success (topmost Via location not indicated) |
| Ensure that the SUT on receipt of a Success (200 OK) response with the
topmost Via header not indicating its own location, does not forward the message. User Action: None. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.11 and 18.1.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_004 | No Fwd Success (not matching to existing client transaction with single Via) |
| Ensure that the SUT, on receipt of a Success (200 OK) response that
does not match to an existing client transaction with a single Via header, does not forward the message. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.7, item 3 and 16.11. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_005 | Fwd Success (matching) |
| Ensure that the SUT, on receipt of a Success (200 OK) response that
matches to an existing client transaction, removes the topmost via from the response and forwards it to the address indicated in the next Via header. Pre-Condition: User Action: None. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.7 and 16.11. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_006 | Fwd 100 Trying (not matching) |
| Ensure that the SUT, on receipt of a Trying (100 Trying) provisional
response that does not match to an existing client transaction, removes the topmost via from the response and forwards it to the address indicated in the next Via header. Config: B SUT: Proxy (single) Status: Mandatory for Stateless Ref: RFC3261 [1] section 16.7 and 16.11. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_007 | Fwd 180 Ringing (not matching) |
| Ensure that the SUT, on receipt of a Ringing (180 Ringing) provisional
response that does not match to an existing client transaction, removes the topmost via from the response and forwards it to the address indicated in the next Via header. Config: B SUT: Proxy (single) Status: Mandatory for Stateless Ref: RFC3261 [1] section 16.7 and 16.11. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_008 | Fwd 302 Moved Temporarily (not matching) |
| Ensure that the SUT on receipt of a Moved Temporarily (302 Moved
Temporarily) Redirection response that does not match to an existing client transaction, removes the topmost via from the response and forwards it to the address indicated in the next Via header. Config: B SUT: Proxy (single) Status: Mandatory Ref: RFC3261 [1] section 16.7 and 16.11. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_009 | Fwd 410 Gone (not matching) |
| Ensure that the SUT on receipt of a Gone (410 Gone) Request failure
response that does not match to an existing client transaction, removes the topmost via from the response and forwards it to the address indicated in the next Via header. Config: B SUT: Proxy (single) Status: Mandatory Ref: RFC3261 [1] section 16.7 and 16.11. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_010 | Fwd 500 Server Internal Error (not matching) |
| Ensure that the SUT on receipt of a Server Internal Error (500 Server
Internal Error) server failure response that does not match to an existing client transaction, removes the topmost via from the response and forwards it to the address indicated in the next Via header. Config: B SUT: Proxy (single) Status: Mandatory Ref: RFC3261 [1] section 16.7 and 16.11. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_011 | Fwd 603 Decline (not matching) |
| Ensure that the SUT on receipt of a Decline (603 Decline) Global
failure response that does not match to an existing client transaction, removes the topmost via from the response and forwards it to the address indicated in the next Via header. Config: B SUT: Proxy (single) Status: Mandatory Ref: RFC3261 [1] section 16.7 and 16.11. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_012 | Fwd 180 Ringing (proxy INVITE, matching) |
| Ensure that the SUT having already proxy an INVITE, on receipt of a
Ringing (180 Ringing) provisional response matching to an existing client transaction, removes the topmost via from the response and forwards it to the address indicated in the next Via header. Config: B SUT: Proxy (single) Status: Mandatory for Stateful Proxy Ref: RFC3261 [1] section 16.7 item 5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_013 | Fwd 302 Moved Temporarily (proxy INVITE, matching, proxy not responsible for URI) |
| Ensure that the SUT having already proxy an INVITE, on receipt of a
Moved Temporarily (302 Moved Temporarily) Redirection response matching to an existing client transaction and the Request-URI indicating a URI the proxy is not responsible for, removes the topmost via from the response and forwards it to the address indicated in the next Via header. Config: B SUT: Proxy Status: Mandatory for Stateful Proxy Ref: RFC3261 [1] section 16.7 item 5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_014 | Fwd 410 Gone (proxy INVITE, matching) |
| Ensure that the SUT having already proxy an INVITE, on receipt of a
Gone (410 Gone) Request failure response matching to an existing client transaction, removes the topmost via from the response and forwards it to the address indicated in the next Via header. Config: B SUT: Proxy Status: Mandatory for Stateful Proxy Ref: RFC3261 [1] section 16.7 item 5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_015 | Fwd 500 Server Internal Error (proxy INVITE, matching) |
| Ensure that the SUT having already proxy an INVITE, on receipt of a
Server Internal Error (500 Server Internal Error) server failure response matching to an existing client transaction, removes the topmost via from the response and forwards it to the address indicated in the next Via header. Config: B SUT: Proxy Status: Mandatory for Stateful Proxy Ref: RFC3261 [1] section 16.7 item 5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_016 | Generate 500 Server Internal Error & Fwd 503 Service Unavailable (proxy INVITE, matching) |
| Ensure that the SUT having already proxy an INVITE, on receipt of a
Service Unavailable (503 Service Unavailable) server failure response matching to an existing client transaction, generates a Server Internal Error (500 Server Internal Error) server failure response, and forwards it. Config: B SUT: Proxy Status: Recommended for Stateful Proxy Ref: RFC3261 [1] section 16.7, item 5 and 6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_017 | Fwd 603 Decline (proxy INVITE, matching) |
| Ensure that the SUT having already proxy an INVITE, on receipt of a
Decline (603 Decline) Global failure response matching to an existing client transaction, removes the topmost via from the response and forwards it to the address indicated in the next Via header. Config: B SUT: Proxy Status: Mandatory for Stateful Proxy Ref: RFC3261 [1] section 16.7 item 5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_018 | Fwd 200 response (on Rx 302, already Rx 200) |
| Ensure that the SUT, after forking an INVITE to two locations and
having received a 302 response from one client transaction, on receipt of a 200 response from the other client transaction, forwards the 200 response. Config: D SUT: Forking Proxy Status: Mandatory for a Stateful Proxy that is able to fork Ref: RFC3261 [1] section 16.7 item 6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_019 | Fwd 302 response (on Rx 302, already Rx 302) |
| Ensure that the SUT, after forking an INVITE to two locations and
having received a 302 response from one client transaction, on receipt of a 302 response from the other client transaction, forwards the 302 response. Config: D SUT: Forking Proxy Status: Mandatory for a Stateful Proxy that is able to fork Ref: RFC3261 [1] section 16.7 item 6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_020 | Fwd 302 response (on Rx 486, already Rx 302) |
| Ensure that the SUT, after forking an INVITE to two locations and
having received a 302 response from one client transaction, on receipt of a 486 response from the other client transaction, forwards the 302 response. Config: D SUT: Forking Proxy Status: Recommended for a Stateful Proxy that is able to fork Ref: RFC3261 [1] section 16.7 item 6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_021 | Fwd 302 response (on Rx 500, already Rx 302) |
| Ensure that the SUT, after forking an INVITE to two locations and
having received a 302 response from one client transaction, on receipt of a 500 response from the other client transaction, forwards the 302 response. Config: D SUT: Forking Proxy Status: Recommended for a Stateful proxy that is able to fork Ref: RFC3261 [1] section 16.7 item 6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_022 | Fwd 603 response (on Rx 603, already Rx 302) |
| Ensure that the SUT, after forking an INVITE to two locations and
having received a 302 response from one client transaction, on receipt of a 603 response from the other client transaction, forwards the 603 response. Config: D SUT: Forking Proxy Status: Mandatory for a Stateful Proxy that is able to fork Ref: RFC3261 [1] section 16.7 item 6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_023 | Tx 200 response (on Rx 200, already Rx 486) |
| Ensure that the SUT, after forking an INVITE to two locations and
having received a 486 response from one client transaction, on receipt of a 200 response from the other client transaction, forwards the 200 response. Config: D SUT: Forking Proxy Status: Mandatory for a Stateful Proxy that is able to fork Ref: RFC3261 [1] section 16.7 item 6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_024 | Fwd 302 response (on Rx 302, already Rx 486) |
| Ensure that the SUT, after forking an INVITE to two locations and
having received a 486 response from one client transaction, on receipt of a 302 response from the other client transaction, forwards the 302 response. Config: D SUT: Forking Proxy Status: Recommended for a Stateful Proxy that is able to fork Ref: RFC3261 [1] section 16.7 item 6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_025 | Fwd 486 response (on Rx 486, already Rx 486) |
| Ensure that the SUT, after forking an INVITE to two locations and
having received a 486 response from one client transaction, on receipt of a 486 response from the other client transaction, forwards the 486 response. Config: D SUT: Forking Proxy Status: Mandatroy for a Stateful Proxy that is able to fork Ref: RFC3261 [1] section 16.7 item 6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_026 | Fwd 401 response (on Rx 401 response, already Rx 486 400) |
| Ensure that the SUT, after forking an INVITE to two locations and
having received a 486 400 response from one client transaction, on receipt of a 401 response from the other client transaction, forwards the 401 response. Config: D SUT: Forking Proxy Status: Recommended for a Stateful Proxy that is able to fork Ref: RFC3261 [1] section 16.7 item 6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_027 | Fwd 407 response (on Rx 407 response, already Rx 486) |
| Ensure that the SUT, after forking an INVITE to two locations and
having received a 486 response from one client transaction, on receipt of a 407 response from the other client transaction, forwards the 407 response. Config: D SUT: Forking Proxy Status: Recommended for a Stateful Proxy that is able to fork Ref: RFC3261 [1] section 16.7 item 6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_028 | Fwd 415 response (on Rx 415 response, already Rx 486) |
| Ensure that the SUT, after forking an INVITE to two locations and
having received a 486 response from one client transaction, on receipt of a 415 response from the other client transaction, forwards the 415 response. Config: D SUT: Forking Proxy Status: Recommended for a Stateful Proxy that is able to fork Ref: RFC3261 [1] section 16.7 item 6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_029 | Fwd 420 response (on Rx 420 response, already Rx 486) |
| Ensure that the SUT, after forking an INVITE to two locations and
having received a 486 response from one client transaction, on receipt of a 420 response from the other client transaction, forwards the 420 response. Config: D SUT: Forking Proxy Status: Recommended for a Stateful Proxy that is able to fork Ref: RFC3261 [1] section 16.7 item 6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_030 | Fwd 484 response (on Rx 484 response, already Rx 486) |
| Ensure that the SUT, after forking an INVITE to two locations and
having received a 486 response from one client transaction, on receipt of a 484 response from the other client transaction, forwards the 484 response. Config: D SUT: Forking Proxy Status: Recommended for a Stateful Proxy that is able to fork Ref: RFC3261 [1] section 16.7 item 6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_031 | Fwd 486 response (on Rx 500 response, already Rx 486) |
| Ensure that the SUT, after forking an INVITE to two locations and
having received a 486 response from one client transaction, on receipt of a 500 response from the other client transaction, forwards the 486 response. Config: D SUT: Forking Proxy Status: Recommended for a Stateful Proxy that is able to fork Ref: RFC3261 [1] section 16.7 item 6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_032 | Fwd 603 response (on Rx 603 response, already Rx 486) |
| Ensure that the SUT, after forking an INVITE to two locations and
having received a 486 response from one client transaction, on receipt of a 603 response from the other client transaction, forwards the 603 response. Config: D SUT: Forking Proxy Status: Mandator for a Stateful Proxy that is able to fork Ref: RFC3261 [1] section 16.7 item 6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_033 | Fwd 401 response with WWW/Proxy-Authenticate (on Rx 401 response, already Rx 401) |
| Ensure that the SUT, after forking an INVITE to two locations and
having received a 401 response from one client transaction, on receipt of a 401 response from the other client transaction, forwards the 401 response including all WWW-Authenticate and Proxy-Authenticate headers collected from the received responses. Config: D SUT: Forking Proxy Status: Mandatory for a Stateful Proxy that is able to fork Ref: RFC3261 [1] section 16.3 item 7. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_034 | Fwd 407 response with Proxy-Authenticate (on Rx 407 response, already Rx 407) |
| Ensure that the SUT, after forking an INVITE to two locations and
having received a 407 response from one client transaction, on receipt of a 407 response from the other client transaction, forwards the 407 response including all Proxy-Authenticate headers collected from the received responses. Config: D SUT: Forking Proxy Status: Mandatory for a Stateful Proxy that is able to fork Ref: RFC3261 [1] section 16.3 item 7. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_035 | Fwd 200 response (on Rx 200 response, already Rx 500) |
| Ensure that the SUT, after forking an INVITE to two locations and
having received a 500 response from one client transaction, on receipt of a 200 response from the other client transaction, forwards the 200 response. Config: D SUT: Forking Proxy Status: Recommended for a Stateful Proxy that is able to fork Ref: RFC3261 [1] section 16.7 item 6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_036 | Fwd 302 response (on Rx 302 response, already Rx 500) |
| Ensure that the SUT, after forking an INVITE to two locations and
having received a 500 response from one client transaction, on receipt of a 302 response from the other client transaction, forwards the 302 response. Config: D SUT: Forking Proxy Status: Recommended for a Stateful Proxy that is able to fork Ref: RFC3261 [1] section 16.7 item 6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_037 | Fwd 486 response (on Rx 486 response, already Rx 500) |
| Ensure that the SUT, after forking an INVITE to two locations and
having received a 500 response from one client transaction, on receipt of a 486 response from the other client transaction, forwards the 486 response. Config: D SUT: Forking Proxy Status: Recommended for a Stateful Proxy that is able to fork Ref: RFC3261 [1] section 16.7 item 6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_038 | Fwd 500 response (on Rx 500 response, already Rx 503) |
| Ensure that the SUT, after forking an INVITE to two locations and
having received a 503 response from one client transaction, on receipt of a 500 response from the other client transaction, forwards the 500 response. Config: D SUT: Forking Proxy Status: Recommended for a Stateful Proxy that is able to fork Ref: RFC3261 [1] section 16.7 item 6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_039 | Fwd 500 response (on Rx 503 response, already Rx 503) |
| Ensure that the SUT, after forking an INVITE to two locations and
having received a 503 response from one client transaction, on receipt of a 503 response from the other client transaction, forwards the 500 response. Config: D SUT: Forking Proxy Status: Recommended for a Stateful Proxy that is able to fork Ref: RFC3261 [1] section 16.7 item 6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_040 | Fwd 603 response (on Rx 603 response, already Rx 300) |
| Ensure that the SUT, after forking an INVITE to two locations and
having received a 300 response from one client transaction, on receipt of a 603 response from the other client transaction, forwards the 603 response. Config: D SUT: Forking Proxy Status: Mandatory for a Stateful Proxy that is able to fork Ref: RFC3261 [1] section 16.7 item 6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_041 | Fwd 180 response (on Rx 180 response, already Rx 302) |
| Ensure that the SUT, after forking an INVITE to two locations and
having received a 302 response from one client transaction, on receipt of a 180 response from the other client transaction, forwards the 180 response. Config: D SUT: Forking Proxy Status: Mandatory for a Stateful Proxy that is able to fork Ref: RFC3261 [1] section 16.7 item 6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_042 | Fwd 180 response (on Rx 180 response, already Rx 486) |
| Ensure that the SUT, after forking an INVITE to two locations and
having received a 486 response from one client transaction, on receipt of a 180 response from the other client transaction, forwards the 180 response. Config: D SUT: Forking Proxy Status: Mandatory for a Stateful Proxy that is able to fork Ref: RFC3261 [1] section 16.7 item 6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_043 | Fwd 180 response (on Rx 180 response, already Rx 500) |
| Ensure that the SUT, after forking an INVITE to two locations and
having received a 500 response from one client transaction, on receipt of a 180 response from the other client transaction, forwards the 180 response. Config: D SUT: Forking Proxy Status: Mandatory for a Stateful proxy that is able to fork Ref: RFC3261 [1] section 16.7 item 6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_044 | Fwd 182 response (on Rx 182 response, already Rx & Fwd 180) |
| Ensure that the SUT, after forking an INVITE to two locations and
having received (and forwarded) a 180 response from one client transaction, on receipt of a 182 response from the other client transaction, forwards the 182 response. Config: D SUT: Forking Proxy Status: Mandatory for a Stateful Proxy that is able to fork Ref: RFC3261 [1] section 16.7 item 6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_045 | Fwd 200 response (on Rx 200 response, already Rx & Fwd 180) |
| Ensure that the SUT, after forking an INVITE to two locations and
having received (and forwarded) a 180 response from one client transaction, on receipt of a 200 response from the other client transaction, forwards the 200 response. Config: D SUT: Forking Proxy Status: Mandatory for a Stateful Proxy that is able to fork Ref: RFC3261 [1] section 16.7 item 6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_046 | Fwd 200 response (on Rx 200 response, already Rx & Fwd 180) |
| Ensure that the IUT, after forking an INVITE to two locations and
having received (and forwarded) a 180 response from one client transaction, on receipt of a 200 response from the other client transaction, sends a CANCEL request to the first client transaction with the same Call-ID, From header, To header, Request-URI, CSeq number as in the previous INVITE, with a single Via header same as topmost Via of the previous INVITE and the CSeq method set to CANCEL Config: D SUT: Forking Proxy Status: Mandatory for a Stateful Proxy that is able to fork Ref: RFC 3261 [1] section 16.7, item 10. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_047 | Fwd 302 response (delayed) (on Rx 302 response, already Rx & Fwd 180) |
| Ensure that the IUT, after forking an INVITE to two locations and
having received (and forwarded) a 180 response from one client transaction, on receipt of a 302 response from the other client transaction, does not forward the 302 response immediately. Config: D SUT: Forking Proxy Status: Mandatory for a Stateful Proxy that is able to fork Ref: RFC 3261 [1] section 16.7, item 6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_048 | Fwd 486 response (delayed) (on Rx 486 response, already Rx & Fwd 180) |
| Ensure that the IUT, after forking an INVITE to two locations and
having received (and forwarded) a 180 response from one client transaction, on receipt of a 486 response from the other client transaction, does not forward the 486 response immediately Config: D SUT: Forking Proxy Status: Mandatory for a Stateful Proxy that is able to fork Ref: RFC 3261 [1] section 16.7, item 6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_049 | Fwd 500 response (delayed) (on Rx 500 response, already Rx & Fwd 180) |
| Ensure that the IUT, after forking an INVITE to two locations and
having received (and forwarded) a 180 response from one client transaction, on receipt of a 500 response from the other client transaction, does not forward the 500 response immediately Config: D SUT: Forking Proxy Status: Mandatory for a Stateful Proxy that is able to fork Ref: RFC 3261 [1] section 16.7, item 6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_050 | Fwd 200 response (on Rx 200 response, already Rx & Fwd 180) |
| Ensure that the IUT, after forking an INVITE to two locations and
having received (and forwarded) a 180 response from one client transaction, on receipt of a 603 response from the other client transaction, sends a CANCEL request to the first client transaction with the same Call-ID, From header, To header, Request-URI, CSeq number as in the previous INVITE, with a single Via header same as topmost Via of the previous INVITE and the CSeq method set to CANCEL. Config: D SUT: Forking Proxy Status: Mandatory for a Stateful Proxy that is able to fork Ref: RFC 3261 [1] section 16.7, item 10. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_051 | Fwd 200 response (on Rx 200 response, already Rx & Fwd 180) |
| Ensure that the IUT, after forking an INVITE to two locations and
having received (and forwarded) a 200 response from one client transaction, on receipt of a 180 response from the other client transaction, sends a CANCEL request to that client transaction with the same Call-ID, From header, To header, Request-URI, CSeq number as in the previous INVITE, with a single Via header same as topmost Via of the previous INVITE and the CSeq method set to CANCEL. Config: D SUT: Forking Proxy Status: Mandatory for a Stateful Proxy that is able to fork Ref: RFC 3261 [1] section 16.7, item 10. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_052 | Fwd 200 response (on Rx 200 response, already Rx & Fwd 180) |
| Ensure that the IUT, after forking an INVITE to two locations and
having received (and forwarded) a 603 response from one client transaction, on receipt of a 180 response from the other client transaction, sends a CANCEL request to that client transaction with the same Call-ID, From header, To header, Request-URI, CSeq number as in the previous INVITE, with a single Via header same as topmost Via of the previous INVITE and the CSeq method set to CANCEL. Config: D SUT: Forking Proxy Status: Mandatory for a Stateful Proxy that is able to fork Ref: RFC 3261 [1] section 16.7, item 10. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_MP_RS_V_053 | Fwd 200 response (on Rx 200 response, already Rx & Fwd 180) |
| Ensure that the IUT, after forking an INVITE to two locations and
having received a 603 response from one client transaction, and having sent a CANCEL to the second client transaction, on receipt of a 487 response from the other client transaction, forwards the 603 response. Config: D SUT: Forking Proxy Status: Mandatory for a Stateful Proxy that is able to fork Ref: RFC 3261 [1] sections 16.7, item 10, and 16.7, item 5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ CC/ PR/ SIP_CC_PR_TR_CL_V |
|
| SIP_CC_PR_TR_CL_V_001 | Tx CANCEL (identical Request-URI,Call-ID, To, From CSeq, INVITE Proceeding state) |
| Ensure that the SUT, on receipt of a CANCEL at server side matching to
a response context and the related client transaction is in the INVITE Proceeding state, sends a CANCEL from the related pending client transaction with the Request-URI, Call-ID, To, From headers, CSeq number identical as in the INVITE request to be cancelled and the CSeq method set to CANCEL. Config: B SUT: Proxy Status: Mandatory for Stateful Proxy Ref: RFC3261 [1] sections 16.10 and 9.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_CL_V_002 | Tx CANCEL (identical Via, INVITE Proceeding state) |
| Ensure that the SUT, on receipt of a CANCEL at server side matching to
a response context and the related client transaction is in the INVITE Proceeding state, sends a CANCEL from the related pending client transaction with the Via header identical as in topmost Via header in the INVITE request to be cancelled. Config: B SUT: Proxy Status: Mandatory for Stateful Proxy Ref: RFC3261 [1] sections 16.10 and 9.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_CL_V_003 | No Tx CANCEL (client transaction in INVITE Calling state) |
| Ensure that the SUT, on receipt of a CANCEL at server side matching to
a response context, but the related client transaction is in the INVITE Calling state, does not send a CANCEL. Config: B SUT: Proxy Status: Mandatory for Stateful Proxy Ref: RFC 3261 [1] sections 16.10 and 9.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_CL_V_004 | Tx CANCEL (on Rx provisional response, INVITE Calling state) |
| Ensure that the SUT, having received a CANCEL request matching to a
response context while the related client transaction is in the INVITE Calling state, on receipt of a provisional response, sends a CANCEL from the related client transaction. Config: B SUT: Proxy Status: Mandatory for Stateful Proxy Ref: RFC3261 [1] sections 16.10 and 9.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_CL_V_005 | No Tx CANCEL (on Rx final response, already Rx CANCEL) |
| Ensure that the SUT, having received a CANCEL request matching to a
response context while the related client transaction is in the INVITE Calling state, on receipt of a final response, does not send a CANCEL from the related client transaction. Config: B SUT: Proxy Status: Mandatory for Stateful Proxy Ref: RFC3261 [1] sections 16.10 and 9.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_CL_V_006 | Tx ACK Rq (on Rx 302 Moved Temporarily, INVITE Client Calling state) |
| Ensure that the SUT in the INVITE Client Calling state on receipt of a
Moved Temporarily (302 Moved Temporarily) Redirection response matching to an existing client transaction, responds with an ACK request, with the same Call-ID, From header, Request-URI, CSeq number as in the previous INVITE, with a single Via header same as topmost Via of the previous INVITE and the To header the same value as the To header in the received response and the CSeq method set to ACK. Config: B SUT: Proxy Status: Mandatory for a Stateful Proxy Ref: RFC3261 [1] sections 16.7 and 17.1.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_CL_V_007 | Tx ACK Rq (on Rx 410 Gone, INVITE Client Calling state) |
| Ensure that the SUT in the INVITE Client Calling state on receipt of a
Gone (410 Gone) Request failure response matching to an existing client transaction, responds with an ACK request, with the same Call-ID, From header, Request-URI, CSeq number as in the previous INVITE, with a single Via header same as topmost Via of the previous INVITE and the To header the same value as the To header in the received response and the CSeq method set to ACK. Config: B SUT: Proxy Status: Mandatory for a Stateful Proxy Ref: RFC3261 [1] sections 16.7 and 17.1.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_CL_V_008 | Tx ACK Rq (on Rx 503 Service Unavailable, INVITE Client Calling state) |
| Ensure that the SUT in the INVITE Client Calling state on receipt of a
Service Unavailable (503 Service Unavailable) server failure response matching to an existing client transaction, responds with an ACK request, with the same Call-ID, From header, Request-URI, CSeq number as in the previous INVITE, with a single Via header same as topmost Via of the previous INVITE and the To header the same value as the To header in the received response and the CSeq method set to ACK. Config: B SUT: Proxy Status: Mandatory for a Stateful Proxy Ref: RFC3261 [1] sections 16.7 and 17.1.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_CL_V_009 | Tx ACK Rq (on Rx 603 Decline, INVITE Client Calling state) |
| Ensure that the SUT in the INVITE Client Calling state on receipt of a
Decline (603 Decline) Global failure response matching to an existing client transaction, responds with an ACK request, with the same Call-ID, From header, Request-URI, CSeq number as in the previous INVITE, with a single Via header same as topmost Via of the previous INVITE and the To header the same value as the To header in the received response and the CSeq method set to ACK. User Action: None. Config: B SUT: Proxy Status: Mandatory for a Stateful Proxy Ref: RFC3261 [1] sections 16.7 and 17.1.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_CL_V_010 | Enter Proceeding state (on Rx 100 Trying, INVITE client in Calling state) |
| Ensure that the SUT, when an INVITE client transaction is in the
Calling state, on receipt of a Trying (100 Trying) response enters in the Proceeding state. User Action: None. Config: B SUT: Proxy Status: Mandatory for Stateful Proxy Ref: RFC3261 [1] section 17.1.1.2 and figure 5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_CL_V_011 | Enter Proceeding state (on Rx 183 Session Progress, INVITE client in Calling state) |
| Ensure that the SUT, when an INVITE client transaction is in the
Calling state, on receipt of a Session Progress (183 Session Progress) response enters in the Proceeding state. User Action: None. Config: B SUT: Proxy Status: Mandatory for Stateful Proxy Ref: RFC3261 [1] section 17.1.1.2 and figure 5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_CL_V_012 | Tx 407 Proxy Authentication Required (on Rx INVITE) |
| Ensure that the SUT on receipt of an INVITE request not including a
Proxy-Authorization header field, sends a Proxy Authentication Required (407 Proxy Authentication Required) response, containing a Proxy-Authenticate header. Pre-condition: User Action: Proxy Authentication must be set to ON. Config: B SUT: Proxy Status: Mandatory for Stateful Proxy Ref: RFC3261 [1] section 22.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_CL_V_013 | Tx 407 Proxy Authentication Required (realm, nonce HTTP parameters, on Rx INVITE) |
| Ensure that the SUT on receipt of an INVITE request not including a
Proxy-Authorization header field, sends a Proxy Authentication Required (407 Proxy Authentication Required) response, containing a Proxy-Authenticate header including proper value for realm and nonce HTTP parameters. Pre-condition: User Action: Proxy Authentication must be set to ON. Config: B SUT: Proxy Status: Mandatory for Stateful Proxy Ref: RFC3261 [1] section 22.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_CL_V_014 | Fwd INVITE (on Rx INVITE with valid Proxy-Authenticate) |
| Ensure that the SUT having sent a Proxy Authentication Required (407
Proxy Authentication Required) response to an INVITE request, on receipt of an INVITE required including a valid Proxy-Authenticate header field, forwards the INVITE. Pre-condition: User Action: Proxy Authentication must be set to ON. Config: B SUT: Proxy Status: Mandatory for Stateful Proxy Ref: RFC3261 [1] section 22.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ CC/ PR/ SIP_CC_PR_TR_CL_TI |
|
| SIP_CC_PR_TR_CL_TI_001 | Repeat INVITE Rq (timer A=T1, unreliable transport (UDP)) |
| If an unreliable transport (UDP) is used, ensure that the SUT, when an
INVITE client transaction is in the Calling state repeats its INVITE request on the timeout condition of timer A set with a value of T1. User Action: None. Config: B SUT: Proxy Status: Mandatory for Stateful Proxy Ref: RFC3261 [1] annex A and section 17.1.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_CL_TI_002 | Repeat INVITE Rq (timer A=T1, reliable transport (TCP)) |
| If a reliable transport (TCP) is used, ensure that the SUT, when an
INVITE client transaction is in the Calling state does not repeat its INVITE request on the timeout condition of timer A set with a value of T1. User Action: None. Config: B SUT: Proxy Status: Recommended for Stateful Proxy Ref: RFC3261 [1] annex A and section 17.1.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_CL_TI_003 | Wait for timer A=2*T1, Tx INVITE (already repeated INVITE, unreliable transport (UDP) |
| If an unreliable transport (UDP) is used, ensure that the SUT, when an
INVITE client transaction is in the Calling state having already repeated its INVITE wait for a timer A set with a value of 2*T1 before sending it again. User Action: None. Config: B SUT: Proxy Status: Mandatory for Stateful Proxy Ref: RFC3261 [1] annex A and section 17.1.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_CL_TI_004 | Retransmit INVITE Rq (double intervals, unreliable transport (UDP)) |
| If an unreliable transport (UDP) is used, ensure that the SUT, when an
INVITE client transaction is in the Calling state retransmits its INVITE request with intervals that double after each transmission. User Action: None. Config: B SUT: Proxy Status: Mandatory for Stateful Proxy Ref: RFC3261 [1] annex A and section 17.1.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_CL_TI_005 | No Tx ACK, transaction terminated (timer B=64*T1 expires) |
| Ensure that the SUT, when an INVITE client transaction is in the
Calling state, when timer B set to a value of 64*T1 expires, considers the transaction terminated and does not send an ACK. User Action: None. Config: B SUT: Proxy Status: Mandatory for Stateful Proxy Ref: RFC3261 [1] annex A and section 17.1.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_CL_TI_007 | No repeat INVITE Rq (INVITE client in Proceeding state) |
| Ensure that the SUT, when an INVITE client transaction is in the
Proceeding state, does not repeat its INVITE request. User Action: None. Config: B SUT: Proxy Status: Recommended for Stateful Proxy Ref: RFC3261 [1] annex A and section 17.1.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_CL_TI_008 | Repeat ACK (on Rx matching final response, INVITE in Completed state |
| If an unreliable transport is used, ensure that the SUT, when an
INVITE client transaction is in the Completed state, on receipt of a final response that matches the transaction, repeats its ACK request until timer D set to at least 32 second expires. User Action: None. Config: B SUT: Proxy Status: Recommended for Stateful Proxy Ref: RFC3261 [1] annex A and section 17.1.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_CL_TI_009 | No repeat ACK (on Rx matching final response, INVITE in Completed state) |
| If a reliable transport is used, ensure that the SUT, when an INVITE
client transaction is in the Completed state, on receipt of a final response that matches the transaction, does not repeats its ACK request. User Action: None. Config: B SUT: Proxy Status: REcommended for Stateful Proxy Ref: RFC3261 [1] annex A and section 17.1.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_CL_TI_010 | No repeat ACK (different Via branch parameter, INVITE in Completed state) |
| If an unreliable transport is used, ensure that the SUT, when an
INVITE client transaction is in the Completed state, on receipt of new final responses with different Via branch parameter value, does not repeat its ACK request until timer D set to at least 32 second expires. User Action: None. Config: B SUT: Proxy Status: Recommended for Stateful Proxy Ref: RFC3261 [1] annex A and section 17.1.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_CL_TI_012 | Repeat BYE Rq (timer E=T1 value expires, BYE in Trying state, unreliable transport) |
| If an unreliable transport is used, ensure that the SUT, when a BYE
client transaction is in the Trying state having sent a BYE request, repeats its request after timer E set to T1 value expires. User Action: None. Config: B SUT: Proxy Status: Mandatory for Stateful Proxy Ref: RFC3261 [1] annex A and section 17.1.2.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_CL_TI_013 | Repeat BYE Rq (timer E=MIN(2*T1,T2), BYE in Trying state, unreliable transport) |
| If an unreliable transport is used, ensure that the SUT, when a BYE
client transaction is in the Trying state having sent twice times a BYE request, repeats its request after timer E set to the MIN(2*T1,T2) value expires. User Action: None. Config: B SUT: Proxy Status: Manatory for Stateful Proxy Ref: RFC3261 [1] annex A and section 17.1.2.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_CL_TI_014 | Repeat BYE Rq (timer E=MIN(4*T1,T2) , BYE in Trying state, unreliable transport) |
| If an unreliable transport is used, ensure that the SUT, when a BYE
client transaction is in the Trying state having sent three times a BYE request, repeats its request after timer E set to the MIN(4*T1,T2) value expires. User Action: None. Config: B SUT: Proxy Status: Mandatory for Stateful Proxy Ref: RFC3261 [1] annex A and section 17.1.2.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_CL_TI_015 | No repeat BYE Rq (timer F=64*T1 expires , BYE in Trying state, unreliable transport) |
| If an unreliable transport is used, ensure that the SUT, when a BYE
client transaction is in the Trying state does not repeat a BYE request, after timer F set to 64*T1 expires. User Action: None. Config: B SUT: Proxy Status: Recommended for Stateful Proxy Ref: RFC3261 [1] annex A and section 17.1.2.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_CL_TI_016 | Repeat BYE Rq (timer E in Trying state=T1 value expires, BYE in Proceeding state) |
| Ensure that the SUT, when a BYE client transaction is in the
Proceeding state, repeats its BYE request after timer E set in Trying state to T1 value expires. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] annex A and section 17.1.2.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_CL_TI_017 | Repeat BYE Rq (timer E=T2 value expires, BYE in Proceeding state) |
| Ensure that the SUT, when a BYE client transaction is in the
Proceeding state and BYE request have been already repeated in this state, repeats its BYE request after timer E set to T2 value expires. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] annex A and section 17.1.2.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_CL_TI_018 | No Repeat BYE Rq (timer F=64*T1 expires, BYE in Proceeding state) |
| Ensure that the SUT, when a BYE client transaction is in the
Proceeding state, does not repeat a BYE request on an established dialog, after timer F set to 64*T1 expires. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] annex A and section 17.1.2.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_CL_TI_019 | Consider transaction terminated (no Rx final response, 64*T1 expires, BYE in Trying state) |
| Ensure that the SUT, when a BYE client transaction is in the Trying
state, considers the transaction terminated after 64*T1 duration expires without receiving any final response. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] annex A, and sections 17.1.2.2 and 9.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ CC/ PR/ SIP_CC_PR_TR_SE_V |
|
| SIP_CC_PR_TR_SE_V_001 | Tx 100 Trying (on Rx INVITE Rq) |
| Ensure that the SUT on receipt of an INVITE request, sends a
provisional (100 Trying) response. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] section 16.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_V_002 | Tx 100 Trying (From, Call-ID, CSeq, Via copied from INVITE Msg) |
| Ensure that the SUT, on receipt of an INVITE request, sends a
provisional (100 Trying) response including the headers From, Call-Id, CSeq and Via copied from the INVITE message. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] section 16.2 and 8.2.6.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_V_003 | Tx 100 Trying (same URI, no tag in To) |
| Ensure that the SUT, on receipt of an INVITE request with no tag set
on the To header, sends a provisional (100 Trying) response including the same URI and no tag in the To header. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] section 16.2, 8.2.6.2 and 17.2.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_V_004 | Tx 100 Trying (same URI, tag in To) |
| Ensure that the SUT, on receipt of an INVITE request with a tag set on
the To header, sends a provisional (100 Trying) response including the same URI and the tag in the To header. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] section 16.2, 8.2.6.2 and 17.2.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_V_005 | Tx 100 Trying (Timestamp) |
| Ensure that the SUT, on receipt of an INVITE request with a Timestamp
header, sends a provisional (100 Trying) response with a Timestamp header. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] section 16.2 and 8.2.6.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_V_006 | Rx INVITE, Repeat response (same branch parameter & sent-by value) (INVITE Proceeding) |
| Ensure that the SUT in a server INVITE Proceeding state, on receipt of
an INVITE request, including a Via header set with the same branch parameter and sent-by value in the topmost list value, repeats its last response. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] sections 17.2.1 and 17.2.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_V_007 | Rx INVITE, Repeat response (no branch parameter) (INVITE Proceeding) |
| Ensure that the SUT in a server INVITE Proceeding state, on receipt of
an INVITE request, including a Via header set with no branch parameter but with the Request-URI, To tag, >From tag, Call-ID, CSeq and top Via header identical as in the first INVITE request, repeats its last response. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] sections 17.2.1 and 17.2.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_V_008 | Rx INVITE, repeat response(different branch parameter,no magic cookie,INVITE Proceeding) |
| Ensure that the SUT in a server INVITE Proceeding state, on receipt of
an INVITE request, including a Via header set with a different branch parameter without the magic cookie Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] sections 17.2.1 and 17.2.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_V_009 | Rx INVITE, repeat response (same branch parameter & sent-by value, INVITE Completed) |
| Ensure that the SUT in a server INVITE Completed state, on receipt of
an INVITE request, including a Via header set with the same branch parameter and sent-by value in the topmost list value, repeats its last response. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] sections 17.2.1 and 17.2.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_V_010 | Rx INVITE, repeat response (no branch parameter, INVITE Completed) |
| Ensure that the SUT in a server INVITE Completed state, on receipt of
an INVITE request, including a Via header set with no branch parameter but with the Request-URI, To tag, >From tag, Call-ID, CSeq and top Via header identical as in the first INVITE request, repeats its last response. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] sections 17.2.1 and 17.2.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_V_011 | Rx INVITE, repeat response (different branch parameter,no magic cookie, INVITE Completed) |
| Ensure that the SUT in a server INVITE Completed state, on receipt of
an INVITE request, including a Via header set with a different branch parameter without the magic cookie To tag, From tag, Call-ID, CSeq and top Via header identical as in the first INVITE request, repeats its last response. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] sections 17.2.1 and 17.2.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_V_012 | Rx BYE, repeat response (same branch parameter & sent-by value, BYE Proceeding) |
| Ensure that the SUT in a server BYE Proceeding state, on receipt of a
BYE request, including a Via header set with the same branch parameter and sent-by value in the topmost list value, repeats its last response. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] sections 17.2.2 and 17.2.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_V_013 | Rx BYE, repeat response (no branch parameter, BYE Proceeding) |
| Ensure that the SUT in a server BYE Proceeding state, on receipt of a
BYE request, including a Via header set with no branch parameter but with the Request-URI, To tag, From tag, Call-ID, CSeq and top Via header identical as in the first BYE request, repeats its last response. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] sections 17.2.2 and 17.2.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_V_014 | Rx BYE, repeat response (different branch parameter, no magic cookie, BYE Proceeding) |
| Ensure that the SUT in a server BYE Proceeding state, on receipt of a
BYE request, including a Via header set with a different branch parameter without the magic cookie z9hG4bK but with the Request-URI, To tag, >From tag, Call-ID, CSeq and top Via header identical as in the first BYE request, repeats its last response. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] sections 17.2.2 and 17.2.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_V_015 | Rx BYE, repeat response (same branch parameter & sent-by value, BYE Completed) |
| Ensure that the SUT in a server BYE Completed state, on receipt of a
BYE request, including a Via header set with the same branch parameter and sent-by value in the topmost list, repeats its last response. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] sections 17.2.2 and 17.2.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_V_016 | Rx BYE, repeat response (no branch parameter, BYE Completed) |
| Ensure that the SUT in a server BYE Completed state, on receipt of a
BYE request, including a Via header set with no branch parameter but with the Request-URI, To tag, From tag, Call-ID, CSeq and top Via header identical as in the first BYE request, repeats its last response. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] sections 17.2.2 and 17.2.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_V_017 | Rx BYE, repeat response (different branch parameter, no magic cookie, BYE Completed) |
| Ensure that the SUT in a server BYE Completed state, on receipt of a
BYE request, including a Via header set with a different branch parameter without the magic cookie >From tag, Call-ID, CSeq and top Via header identical as in the first BYE request, repeats its last response. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] sections 17.2.2 and 17.2.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_V_018 | Rx CANCEL, Tx Success (same branch parameter & sent-by value) |
| Ensure that the SUT in a server INVITE Proceeding state, on receipt of
a CANCEL, including a Via header set with the same branch parameter and sent-by value with the topmost Via value INVITE to be cancelled, sends a Success (200 Success) response to the CANCEL request. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] sections 16.10 and 9.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_V_019 | Rx CANCEL, Tx 487 Request Teminated (same branch parameter & sent-by value) |
| Ensure that the SUT in a server INVITE Proceeding state, on receipt of
a CANCEL, including a Via header set with the same branch parameter and sent-by value with the topmost Via value INVITE to be cancelled, answers to the original INVITE request with a Request Terminated (487 Request Terminated) response. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] section 9.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_V_020 | Rx CANCEL, Tx Success (no branch parameter) |
| Ensure that the SUT in a server INVITE Proceeding state, on receipt of
a CANCEL, including a Via header set with no branch parameter but with the Request-URI, To tag, From tag, Call-ID, CSeq number and top Via header identical as in the INVITE to be cancelled, sends a Success (200 Success) response to the CANCEL request. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] sections 16.10 and 9.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_V_021 | Rx CANCEL, Tx 487 Request Terminated (no branch parameter) |
| Ensure that the SUT in a server INVITE Proceeding state, on receipt of
a CANCEL, including a Via header set with no branch parameter but with the Request-URI, To tag, From tag, Call-ID, CSeq number and top Via header identical as in the INVITE to be cancelled, answers to the original INVITE, request with a Request Terminated (487 Request Terminated) response. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] section 9.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_V_022 | Rx CANCEL, Tx Success (different branch parameter, no magic cookie) |
| Ensure that the SUT in a server INVITE Proceeding state, on receipt of
a CANCEL, including a Via header set with a different branch parameter without the magic cookie >From tag, Call-ID, CSeq number and top Via header identical as in the INVITE to be cancelled, sends a Success (200 Success) response to the CANCEL request. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] sections 16.10 and 9.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_V_023 | Rx CANCEL, Tx 487 Request Teminated (different branch parameter, no magic cookie) |
| Ensure that the SUT in a server INVITE Proceeding state, on receipt of
a CANCEL, including a Via header set with a different branch parameter without the magic cookie >From tag, Call-ID, CSeq number and top Via header identical as in the INVITE to be cancelled, answers to the original INVITE, request with a Request Terminated (487 Request Terminated) response. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] section 9.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_V_024 | Rx ACK, no Fwd Msg (same branch parameter & sent-by value, unreliable transport) |
| If an unreliable transport is used, ensure that the SUT in a server
INVITE Confirmed state, on receipt of an ACK request, including a Via
header set with the same branch parameter and sent-by value in the topmost list value, does not forward the message. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] sections 17.2.1 and 17.2.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_V_025 | Rx ACK, no Fwd Msg (no branch parameter, unreliable transport) |
| If an unreliable transport is used, ensure that the SUT in a server
INVITE Confirmed state, on receipt of an ACK request, including a Via
header set with no branch parameter but with the Request-URI, To tag, >From tag, Call-ID, CSeq number and top Via header identical as in the first INVITE request, does not forward the message. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] sections 17.2.1 and 17.2.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_V_026 | Rx ACK, no Fwd Msg (different branch parameter, no magic cookie, unreliable transport) |
| If an unreliable transport is used, ensure that the SUT in a server
INVITE Confirmed state, on receipt of an ACK request, including a Via
header set with a different branch parameter without the magic cookie To tag, From tag, Call-ID, CSeq number and top Via header identical as in the first INVITE request, does not forward the message. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] section 17.2.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_V_027 | Enter Completed state after Tx 4XX response (INVITE Proceeding) |
| Ensure that the SUT in a server INVITE Proceeding state, after sending
a 4XX response, enters in the Completed state. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] sections 17.2.3.1 and 13.3.1.4, figure 7. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_V_028 | Enter Confirmed state on Rx ACK Rq (INVITE Completed) |
| Ensure that the SUT in a server INVITE Completed state, on receipt of
an ACK request, enters in the Confirmed state. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] sections 17.2.3.1 and 13.3.1.4, figure 7. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_V_029 | Tx 481 Call/Transaction does not exist on Rx BYE Rq (no dialog established) |
| Ensure that the SUT, while no dialog has been established, on receipt
of a BYE request, sends a Call/Transaction does not exist (481 Call/Transaction does not exist). Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] section 15.1.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ CC/ PR/ SIP_CC_PR_TR_SE_TI |
|
| SIP_CC_PR_TR_SE_TI_001 | Repeat response (timer G=T1, unreliable transport) |
| If an unreliable transport is used, ensure that the SUT, when an
INVITE server transaction is in the Completed state repeats its response on the timeout condition of timer G set with a value of T1. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] annex A and section 17.2.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_TI_002 | No repeat response (timer G=T1, reliable transport (TCP)) |
| If a reliable transport (TCP) is used, ensure that the SUT, when an
INVITE server transaction is in the Completed state does not repeat its response on the timeout condition of timer G set with a value of T1. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] annex A and section 17.2.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_TI_003 | Repeat response (timer G=MIN(2*T1,T2value expires, unreliable transport) |
| If an unreliable transport is used, ensure that the SUT, when an
INVITE server transaction is in the Completed state and having already sent twice times its response, repeats it after timer G set MIN(2*T1,T2) value expires. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] annex A and section 17.2.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_TI_004 | Repeat response (timer G=MIN(4*T1,T2value expires, unreliable transport) |
| If an unreliable transport is used, ensure that the SUT, when an
INVITE server transaction is in the Completed state and having already sent three times its response, repeats it after timer G set the MIN(4*T1,T2) value expires. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] annex A and section 17.2.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_TI_005 | Enter Terminated state (timer H=64*T1 value expires) |
| Ensure that the SUT, when an INVITE server transaction is in the
Completed state and, enters in the Terminated state after timer H set to 64*T1 value expires. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] annex A and section 17.2.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_TI_006 | No repeat response (timer H=64*T1 value expires, unreliable transport) |
| If an unreliable transport is used, ensure that the SUT, when an
INVITE server transaction is in the Completed state and, does not repeats its response after timer H set to 64*T1 value expires. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] annex A and section 17.2.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_TI_007 | Enter Terminated state (timer l=T4 value expires, unreliable transport) |
| If an unreliable transport is used, ensure that the SUT, when an
INVITE server transaction is in the Confirmed state, enters in the Terminated state after timer I set to T4 value expires. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] annex A and section 17.2.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_TI_008 | Enter immediatelyTerminated state (reliable transport) |
| If a reliable transport is used, ensure that the SUT, when an INVITE
server transaction is in the Confirmed state, enters immediately in the Terminated state. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] annex A and section 17.2.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_PR_TR_SE_TI_009 | Retransmit response until timer J=64*T1 expires on Rx BYE Rq repetitions |
| If an unreliable transport is used, ensure that the SUT, when a BYE
server transaction is in the Completed state, on receipt of the repetitions of the BYE request, retransmits its response until the timer J set to 64*T1 expires. Pre-condition: Proxy SUT is in the idle state. User Action: None. Config: B SUT: Proxy Ref: RFC3261 [1] annex A and section 17.2.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ CC/ RD |
Checks RD part of CC signaling |
| ETSI/ CC/ RD/ SIP_CC_RD_CE_V |
|
| SIP_CC_RD_CE_V_001 | Tx 3XX redirection (Contact=callee registered location,To= received value & addiotional TAG) |
| Ensure that the SUT on receipt of an INVITE request, sends a 3XX
redirection response to the caller including a Contact header set to the registered location of the callee and the To header set to the received value with an additional TAG. Config: C SUT: Redirect Ref: RFC3261 [1] sections 8.3 and 8.2.6.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_RD_CE_V_002 | Tx 3XX redirection (copy received Via into response) |
| Ensure that the SUT on receipt of an INVITE request, sends a 3XX
redirection response to the caller after having copy the received Via header into the response. User Action: None. Config: C SUT: Redirect Ref: RFC3261 [1] sections 8.3 and 8.2.6.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_RD_CE_V_003 | Accept ACK Rq after Tx 3XX redirection |
| Ensure that the SUT, having sent a 3XX redirection response, accepts
an ACK request. User Action: None. Config: C SUT: Redirect Ref: RFC3261 [1] section 8.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_RD_CE_V_004 | Tx 3XX redirection (Contact=locations list callee previously registered) |
| Ensure that the SUT on receipt of an INVITE request, send a 3XX
redirection response to the caller including a Contact header set to the list of locations of the callee previously registered. User Action: None. Config: C SUT: Redirect Ref: RFC3261 [1] section 8.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_RD_CE_V_005 | Tx 3XX redirection (Require=not understandable value) |
| Ensure that the SUT on receipt of an INVITE request including a
Require header set to a value that it does not understand, sends a 3XX redirection response to the caller. User Action: None. Config: C SUT: Redirect Ref: RFC3261 [1] section 8.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_RD_CE_V_006 | Tx 480 Temporarily Unavailable (registration expired for UA) |
| Ensure that the SUT on receipt of an INVITE request for a UA for which
the registration has expired, sends a Temporarily Unavailable (480 Temporarily Unavailable) request failure response to the caller. User Action: None. Config: C SUT: Redirect Ref: RFC3261 [1] sections 8.3 and 21.4.18. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_RD_CE_V_007 | Tx 404 Not found (Rx INVITE for unknown UA) |
| Ensure that the SUT on receipt of an INVITE request for an unknown UA,
sends a Not found (404 Not Found) request failure response to the caller. User Action: None. Config: C SUT: Redirect Ref: RFC3261 [1] sections 8.3 and 21.4.5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_RD_CE_V_008 | Rx INVITE, Tx 401 Unauthorized/407 Proxy Authentication Required |
| Ensure that the SUT on receipt of an INVITE request not including
an Authorization or Proxy-Authorization header field, sends an Unauthorized (401 Unauthorized) or Proxy Authentication Required (407 Proxy Authentication Required) response, containing a WWW-Authenticate header or a Proxy-Authenticate header. Note: **In SIP configuration, set SUT Authentication on, and IP_Register_With_Proxy = FALSE** Config: C SUT: Redirect Ref: RFC3261 [1] sections 10.3, item 3 and 22.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_RD_CE_V_009 | Rx INVITE, Tx 401 Unauthorized/407 Proxy Authentication Required (realm, nonce HTTP) |
| Ensure that the receipt of an INVITE request not including an
Authorization or a Proxy-Authorization header fields, sends an Unauthorized (401 Unauthorized) or Proxy Authentication Required (407 Proxy Authentication Required) response, containing a WWW-Authenticate or a Proxy-Authenticate header including proper value for realm and nonce HTTP parameters. User Action: None. Config: C SUT: Redirect Ref: RFC3261 [1] section 22.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_RD_CE_V_010 | Tx 3XX rediection (valid Authorization/Proxy-Authorization in INVITE) |
| Ensure that the SUT having sent an Unauthorized (401 Unauthorized) or
a Proxy Authentication Required (407 Proxy Authentication Required) response to an INVITE request, on receipt of an INVITE request including a valid Authorization or Proxy-Authorization header field, sends a 3XX redirection . User Action: None. Config: C SUT: Redirect Ref: RFC3261 [1] section 22.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ CC/ RD/ SIP_CC_RD_CR_V |
|
| SIP_CC_RD_CR_V_001 | Rx INVITE followed by CANCEL, Tx 200 OK |
| Ensure that the SUT on receipt of an INVITE request immediately
followed by a CANCEL request with the same Call-ID, To, From, top Via header, Request URI and CSeq, sends an OK (200 OK) response to the caller. Pre-condition: Redirect SUT is in the idle state. User Action: None. Config: A SUT: Redirect Ref: RFC3261 [1] section 8.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_RD_CR_V_002 | Tx 481 Call Leg/Transaction Does Not Exist (Call-ID not matching in CANCEL) |
| Ensure that the SUT on receipt of a CANCEL request whose Call-ID does
not match a pending request, sends a Call Leg/Transaction Does Not Exist (481 Call Leg/Transaction Does Not Exist) request failure to the caller. Pre-condition: Redirect SUT is in the idle state. User Action: None. Config: A SUT: Redirect Ref: RFC3261 [1] sections 8.3 and 21.4.19. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_CC_RD_CR_V_003 | Rx BYE, Tx 3XX redirection (Contact=callee registered location) |
| Ensure that the SUT on receipt of a BYE request, sends a 3XX
redirection response to the caller including a Contact header set to the registered location of the callee. User Action: None. Config: A SUT: Redirect Ref: RFC3261 [1] sections 8.3 and 8.2.6.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ QC |
Checks QC signaling |
| ETSI/ QC/ OE |
|
| ETSI/ QC/ OE/ SIP_QC_OE_V |
|
| SIP_QC_OE_V_001 | Tx OPTIONS Rq (To, From, CSeq, Call-ID, Max-Forwards & Via) |
| Ensure that the SUT, to query for capabilities sends an OPTIONS
request including at least To, From, CSeq, Call-ID, Max-Forwards and Via headers. User Action: Send OPTIONS from SUT to TESTER Config: SUT: User Agent Ref: RFC3261 [1] sections 11 and 8.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_OE_V_002 | Tx OPTIONS Rq (Request-URI=same URI of To) |
| Ensure that the SUT, to query for capabilities sends an OPTIONS
request with a Request-URI set to the same URI value of the To header. Config: SUT: User Agent Ref: RFC3261 [1] sections 11 and 8.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_OE_V_003 | Tx OPTIONS Rq (From with TAG parameter) |
| Ensure that the SUT, to query for capabilities sends an OPTIONS
request including a From header with a TAG parameter. Config: SUT: User Agent Ref: RFC3261 [1] sections 11 and 8.1.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_OE_V_004 | Tx OPTIONS Rq (CSeq matches "OPTIONS") |
| Ensure that the SUT, to query for capabilities sends an OPTIONS
request including a CSeq header with a method that matches "OPTIONS". Config: SUT: User Agent Ref: RFC3261 [1] sections 11 and 8.1.1.5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_OE_V_005 | Tx OPTIONS Rq (Max-Forwards=70) |
| Ensure that the SUT, to query for capabilities sends an OPTIONS
request including a Max-Forward header set to 70. Config: SUT: User Agent Ref: RFC3261 [1] sections 11 and 8.1.1.6. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_OE_V_007 | Tx OPTIONS Rq (protocol name/version=SIP/2.0 in Via, branch parameter) |
| Ensure that the SUT, to query for capabilities sends an OPTIONS
request including a Via header with a protocol name set to SIP, a protocol version set to 2.0 and a branch parameter set to a value beginning with "z9hG4bK". Config: SUT: User Agent Ref: RFC3261 [1] sections 11 and 8.1.1.7. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_OE_V_008 | Tx OPTIONS Rq (Accept=Msg body type expected in response) |
| Ensure that the SUT, to query for capabilities sends an OPTIONS
request including an Accept header set to the type of message body expected in the response. Config: SUT: User Agent Ref: RFC3261 [1] section 11.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_OE_V_009 | Rx Success after Tx OPTIONS |
| Ensure that the SUT having sent an OPTIONS request is able to receive
a Success (200 OK) response. Config: SUT: User Agent Ref: RFC3261 [1] section 11.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_OE_V_010 | Rx 486 Busy here after Tx OPTIONS |
| Ensure that the SUT having sent an OPTIONS request is able to receive
a Busy here (486 Busy here) response. Config: SUT: User Agent Ref: RFC3261 [1] section 11.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_OE_V_011 | Rx Success (Allow, Accept, Acept-Encoding, Accept-Language, Supported) |
| Ensure that the SUT having sent an OPTIONS request is able to receive
a Success (200 OK) response including Allow, Accept, Accept-Encoding, Accept-Language and Supported header. Config: SUT: User Agent Ref: RFC3261 [1] section 11.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_OE_V_012 | Repeat OPTIONS Rq (Authorization header, incremented CSeq value) |
| Ensure that the SUT having sent an OPTIONS request, on receipt of an
Unauthorized (401 Unauthorized) response including a WWW-Authenticate header, repeats its OPTIONS request with an Authorization header and with an incremented Cseq value. Config: SUT: User Agent Ref: RFC3261 [1] sections 11 and 22.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_OE_V_013 | Repeat OPTIONS Rq (Authorization, username, realm nonce, digest-uri, response HTTP) |
| Ensure that the SUT having sent an OPTIONS request, on receipt of an
Unauthorized (401 Unauthorized) response including a WWW-Authenticate header, repeats its OPTIONS request with an Authorization header including proper values for username, realm nonce, digest-uri and response HTTP parameters. Config: SUT: User Agent Ref: RFC3261 [1] sections 11 and 22.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_OE_V_014 | Repeat OPTIONS Rq (Proxy-Authenticate header, incremented CSeq value) |
| Ensure that the SUT having sent an OPTIONS request, on receipt of a
Proxy Authentication Required (407 Proxy Authentication Required) response including a Proxy-Authenticate header, repeats its OPTIONS request with a Proxy-Authenticate header and with an incremented Cseq value. Config: SUT: User Agent Ref: RFC3261 [1] sections 11 and 22.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_OE_V_015 | Repeat OPTIONS Rq (Proxy-Authenticate, username, realm nonce, digest-uri, response HTTP) |
| Ensure that the SUT having sent an OPTIONS request, on receipt of a
Proxy Authentication Required (407 Proxy Authentication Required) response including a Proxy-Authenticate header, repeats its OPTIONS request with a Proxy-Authenticate header including proper values for username, realm nonce, digest-uri and response HTTP parameters. Config: SUT: User Agent Ref: RFC3261 [1] sections 11 and 22.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ QC/ OE/ SIP_QC_OE_TI |
|
| SIP_QC_OE_TI_001 | Repeat OPTIONS Rq (timer E=T1 value expires, unreliable transport) |
| If an unreliable transport is used, ensure that the SUT, having sent
an OPTIONS request, repeats its request after timer E set to T1 value expires. Config: SUT: User Agent Ref: RFC3261 [1] annex A and section 17.1.2.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_OE_TI_002 | Repeat OPTIONS Rq (timer E=MIN(2*T1,T2) value expires, unreliable transport) |
| If an unreliable transport is used, ensure that the SUT, having sent
twice times an OPTIONS request, repeats its request after timer E set to MIN(2*T1,T2) value expires. Config: SUT: User Agent Ref: RFC3261 [1] annex A and section 17.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_OE_TI_003 | Repeat OPTIONS Rq (timer E=MIN(4*T1,T2) value expires, unreliable transport) |
| If an unreliable transport is used, ensure that the SUT, having sent
three times an OPTIONS request, repeats its request after timer E set to MIN(4*T1,T2) value expires. Config: SUT: User Agent Ref: RFC3261 [1] annex A and section 17.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_OE_TI_004 | Repeat OPTIONS Rq (timer F=64*T1 expires, unreliable transport) |
| If an unreliable transport is used, ensure that the SUT does not
repeat an OPTIONS request, repeats after timer F set to 64*T1 expires. Config: SUT: User Agent Ref: RFC3261 [1] annex A and section 17.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_OE_TI_005 | Repeat OPTIONS Rq (timer E=T1 value expires, OPTIONS in Proceeding state) |
| Ensure that the SUT, when an OPTIONS client transaction is in the
Proceeding state, repeats its OPTIONS request after timer E set to T1 value expires. Config: SUT: User Agent Ref: RFC3261 [1] annex A and section 17.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_OE_TI_006 | Repeat OPTIONS Rq (timer E=T2 value expires, OPTIONS in Proceeding state) |
| Ensure that the SUT, when an OPTIONS client transaction is in the
Proceeding state and its OPTIONS request after timer E set to T2 value expires. Config: SUT: User Agent Ref: RFC3261 [1] annex A and section 17.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_OE_TI_007 | No Repeat OPTIONS Rq (timer F=64*T1 value expires, OPTIONS in Proceeding state) |
| Ensure that the SUT, when an OPTIONS client transaction is in the
Proceeding state, does not repeat its OPTIONS request, after timer F set to 64*T1 value expires. Config: SUT: User Agent Ref: RFC3261 [1] annex A and section 17.1.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ QC/ TE |
Checks TE part of QC signaling |
| ETSI/ QC/ TE/ SIP_QC_TE_V |
|
| SIP_QC_TE_V_001 | Rx OPTIONS Rq, Tx Success |
| Ensure that the SUT on receipt of an OPTIONS request, sends a Success
(200 OK). Config: SUT: User Agent Ref: RFC3261 [1] sections 11.2 and 8.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_TE_V_002 | Rx OPTIONS Rq, Tx Success (From, Call-ID, CSeq, Via) |
| Ensure that the SUT on receipt of an OPTIONS request, sends a Success
(200 OK) including the headers From, Call-ID, CSeq and Via headers copy from the OPTIONS request. **NOTE: Test Unsupported in this Release** User Action: Config: SUT: User Agent Ref: RFC3261 [1] sections 11.2 and 8.2.6.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_TE_V_003 | Rx OPTIONS Rq (no TAG), Tx Success (same URI, additional TAG for To) |
| Ensure that the SUT on receipt of an OPTIONS request with no TAG set
on the To header, sends a Success (200 OK) including the same URI and an additional TAG for the To header. Config: SUT: User Agent Ref: RFC3261 [1] sections 11.2 and 8.2.6.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_TE_V_004 | Rx OPTIONS Rq (TAG), Tx Success (same URI, same TAG for To) |
| Ensure that the SUT on receipt of an OPTIONS request with a TAG set on
the To header, sends a Success (200 OK) including the same URI and the same TAG for the To header. Config: SUT: User Agent Ref: RFC3261 [1] sections 11.2 and 8.2.6.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_TE_V_005 | Rx OPTIONS Rq,Tx Success (Allow, Accept, Accept-Encoding, Accept-Language, Supported) |
| Ensure that the SUT on receipt of an OPTIONS request, sends a Success
(200 OK) including Allow, Accept, Accept-Encoding, Accept-Language and Supported headers. Config: SUT: User Agent Ref: RFC3261 [1] section 11.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_TE_V_006 | Rx OPTIONS Rq , Tx Success (Accept="application/sdp", Msg body) |
| Ensure that the SUT on receipt of an OPTIONS request with an Accept
header set to "application/sdp", sends a Success (200 OK) including a message Body. Config: SUT: User Agent Ref: RFC3261 [1] section 11.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_TE_V_007 | Rx OPTIONS Rq, Tx Success (no Accept, Msg body) |
| Ensure that the SUT on receipt of an OPTIONS request with no Accept
header, sends a Success (200 OK) including a message Body. Config: SUT: User Agent Ref: RFC3261 [1] section 11.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_TE_V_008 | Rx OPTIONS Rq, Tx 401 Unauthorized (no Authorization header) |
| Ensure that the SUT on receipt of an OPTIONS request not including an
Authorization header field, sends an Unauthorized (401 Unauthorized) response, containing a WWW-Authenticate header. Config: SUT: User Agent Ref: RFC3261 [1] sections 11 and 22.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_TE_V_009 | Rx OPTIONS Rq, Tx 401 Unauthorized (proper value for realm, nonce, HTTP parameters) |
| Ensure that the SUT on receipt of an OPTIONS request not including an
Authorization header field, sends an Unauthorized (401 Unauthorized) response, containing a WWW-Authenticate header including proper value for realm and nonce HTTP parameters. Config: SUT: User Agent Ref: RFC3261 [1] sections 11 and 22.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_TE_V_010 | Rx OPTIONS with valid Authorization after Tx 401 Unauthorized, Tx Success |
| Ensure that the SUT having sent an Unauthorized (401 Unauthorized)
response to an OPTIONS request, on receipt of a OPTIONS request including a valid Authorization header field, sends a Success (200 OK) response. Config: SUT: User Agent Ref: RFC3261 [1] sections 11 and 22.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ QC/ PR |
Checks PR part of QC signaling |
| SIP_QC_PR_V_001 | Tx Success (OPTIONS addressing Request-URi without user part) |
| Ensure that the SUT on receipt of an OPTIONS request addressing itself
with a Request-URI without user part, sends a Success (200 OK). Config: SUT: Proxy Ref: RFC3261 [1] section 11. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_PR_V_002 | Fwd OPTIONS to target in Request-URI ( Request-URI addressing another UA) |
| Ensure that the SUT on receipt of an OPTIONS request identified by a
Request-URI addressing another UA, forwards the message to the target indicated in the Request-URI. Config: SUT: Proxy Ref: RFC3261 [1] sections 11.2 and 8.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_PR_V_003 | Tx Success, no user part (From, Call-ID, CSeq, Via, OPTIONS) |
| Ensure that the SUT on receipt of an OPTIONS request addressing itself
with a Request-URI without user part, sends a Success (200 OK) including the headers From, Call-ID, CSeq and Via headers copy from the OPTIONS request. Config: SUT: User Agent Ref: RFC3261 [1] sections 11.2 and 8.2.6.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_PR_V_004 | Tx Success, no user part (same URI, additional TAG for To) |
| Ensure that the SUT on receipt of an OPTIONS request, addressing
itself with a Request-URI without user part, with no TAG set on the To header, sends a Success (200 OK) including the same URI and an additional TAG for the To header. Config: SUT: Proxy Ref: RFC3261 [1] sections 11.2 and 8.2.6.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_PR_V_005 | Tx Success, no user part (same URI, same TAG for To) |
| Ensure that the SUT on receipt of an OPTIONS request, addressing
itself with a Request-URI without user part, with a TAG set on the To header, sends a Success (200 OK) including the same URI and the same TAG for the To header. Config: SUT: Proxy Ref: RFC3261 [1] sections 11.2 and 8.2.6.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_PR_V_006 | Tx Success, no user part (Allow, Accept-Encoding, Accept-Language, Supported) |
| Ensure that the SUT on receipt of an OPTIONS request addressing itself
with a Request-URI without user part, sends a Success (200 OK) including Allow, Accept, Accept-Encoding, Accept-Language and Supported headers. Config: SUT: Proxy Ref: RFC3261 [1] section 11.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_PR_V_007 | Tx Success, no user part, Accept="application/sdp" (Msg body) |
| Ensure that the SUT on receipt of an OPTIONS request, addressing
itself with a Request-URI without user part, with an Accept header set to "application/sdp", sends a Success (200 OK) including a message Body. Config: SUT: Proxy Ref: RFC3261 [1] section 11.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_PR_V_008 | Tx Success, no user part, no Accept (Msg body) |
| Ensure that the SUT on receipt of an OPTIONS request, addressing
itself with a Request-URI without user part, with no Accept header, sends a Success (200 OK) including a message Body. Config: SUT: Proxy Ref: RFC3261 [1] section 11.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_PR_V_009 | Fwd OPTIONS((forking) to both URIs) (target with 2 URIs) |
| Ensure that the SUT on receipt of an OPTIONS request and the
determined target set is containing two URIs forwards the message (forking) to both URIs. Config: SUT: Proxy Ref: RFC3261 [1] section 11.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_PR_V_010 | No Fwd additional 200 response (forked OPTIONS, Rx & Tx 200 response from 1 client) |
| response from one client transaction, on receipt of a 200 response
from the other client transaction, does not forward the additional 200 response. Config: SUT: Proxy Ref: RFC3261 [1] section 11.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_PR_V_011 | Tx 407 Proxy Authentication Required, no user part (Proxy -Authenticate header) |
| Ensure that the SUT on receipt of an OPTIONS request, addressing
itself with a Request-URI without user part, not including a Proxy-Authorization header field, sends a Proxy Authentication Required (407 Proxy Authentication Required) response, containing a Proxy-Authenticate header. Config: SUT: Proxy Ref: RFC3261 [1] section 22.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_PR_V_012 | Tx 407 Proxy Authentication Required, no user part (realm, nonce HTTP parameters) |
| Ensure that the SUT on receipt of an OPTIONS request, addressing
itself with a Request-URI without user part, not including a Proxy-Authorization header field, sends a Proxy Authentication Required (407 Proxy Authentication Required) response, containing a Proxy-Authenticate header including proper value for realm and nonce HTTP parameters. Config: SUT: Proxy Ref: RFC3261 [1] section 22.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_QC_PR_V_013 | Rx OPTIONS with valid Proxy-Authenticate header, Tx Success (no user part) |
| Ensure that the SUT having sent a Proxy Authentication Required (407
Proxy Authentication Required) response to an OPTIONS request, addressing itself with a Request_URI without user part, on receipt of an OPTIONS request including a valid Proxy-Authenticate header field, for sends a Success (200 OK) response. Config: SUT: Proxy Ref: RFC3261 [1] section 22.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ MG |
Checks MG signaling |
| ETSI/ MG/ RT |
Checks RT part of MG signaling |
| ETSI/ MG/ RT/ SIP_MG_RT_V |
|
| SIP_MG_RT_V_001 | Ignore non-understood uri-parameter & consider Rx Success |
| Ensure that the SUT, having sent a REGISTER request, on receipt of a
valid Success (200 OK) response including non-understood uri-parameter in SIP-URI of the contact header, ignores it and considers to have received a Success (200 OK). Config: A SUT: User Agent Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RT_V_002 | Consider Rx Success, (header parameters in SIP-URI of Contact header are in Success) |
| Ensure the the SUT, having sent a REGISTER request, on receipt of a
valid Success (200 OK) response including header parameters in the SIP-URI of the Contact header, considers to have received a Success (200 OK). Config: A SUT: User Agent Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RT_V_003 | Consider Rx Success, (non-defined last 2 digits in 299 OK) |
| Ensure that the SUT, having sent a REGISTER request, on receipt of a
valid Success (299 OK) respone with non-defined last two digits considers to have received a Success (200 OK). Config: A SUT: User Agent Ref: RFC3261 [1] section 7.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RT_V_004 | Consider Rx Success, (unknown reason phrase in 200 PERFECT) |
| Ensure that the SUT, having sent a REGISTER request, on receipt of a
valid Success (200 PERFECT) response with an unknown reason phrase considers to have received a Success (200 OK). Config: A SUT: User Agent Ref: RFC3261 [1] section 7.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RT_V_005 | Rx Success (upper & lower cases in headers) |
| Ensure that the SUT, having sent a REGISTER request, is able to
receive a Success (200 OK) response including headers named with upper and lower cases. Config: A SUT: User Agent Ref: RFC3261 [1] section 7.3.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RT_V_006 | Rx Success (header=values with several leading white space & extended over multiple lines) |
| Ensure that the SUT, having sent a REGISTER request, is able to
receive a Success (20 OK) response including a header set with values preceded by several leading white space and properly extended over multiple lines. Config: A SUT: User Agent Ref: RFC3261 [1] section 25.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RT_V_007 | Rx Success (headers=short field names) |
| Ensure that the SUT, having sent a REGISTER request, is able to
receive a Success (200 OK) response including headers set with short field names. Config: A SUT: User Agent Ref: RFC3261 [1] sections 25.1 and 7.3.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RT_V_008 | Ignore CRLF before start & consider Rx Success (REGISTER sent over TCP) |
| Ensure that the SUT, having sent a REGISTER request over a
stream-oriented (TCP) transport, on receipt of a Success (200 OK) response with several CRLF before the start ignores them and considers to have received a Success (200 OK). Config: A SUT: User Agent Ref: RFC3261 [1] section 7.5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ MG/ RT/ SIP_MG_RT_I |
|
| SIP_MG_RT_I_001 | Consider Rx Success (Success with transport parameters in From & To) |
| Ensure that the SUT, having sent a REGISTER request, on receipt of a
Success (200 OK) response with transport parameters in the From and To headers considers to have received a Success (200 OK). Config: A SUT: User Agent Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RT_I_002 | Ignore ttl parameter in From & To & consider Rx Success |
| Ensure that the SUT, having sent a REGISTER request, on receipt of a
Succcess (200 OK) response with a ttl parameter in the From and To headers ignores them and considers to have received a Success (200 OK). Config: A SUT: User Agent Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RT_I_003 | Ignore URI with header parameter in To & From & consider Rx Success |
| Ensure that the SUT, having sent a REGISTER request, on receipt of a
Success (200 OK) response with an URI including a header parameter in the To and From headers ignores them and considers to have received a Success (200 OK). Config: A SUT: User Agent Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RT_I_004 | Ignore method parameters in From & To & consider Rx Success |
| Ensure that the SUT, having sent a REGISTER request, on receipt of a
Success (200 OK) response with a method parameters in the To and From headers ignores them and considers to have received a Success (200 OK). Config: A SUT: User Agent Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RT_I_005 | Ignore Contact in 183 Session Progress & accept Success |
| Ensure that the SUT, having sent a REGISTER request, on receipt of a
Session Progress (183 Session Progress) response with a Contact header ignores it and accepts the following Success (200 OK). Config: A SUT: User Agent Ref: RFC3261 [1] section 20, table 2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ MG/ RR |
Checks RR part of MG signaling |
| ETSI/ MG/ RR/ SIP_MG_RR_V |
|
| SIP_MG_RR_V_001 | Tx Success (escaped characters in SIP-URI of Contact) |
| Ensure the SUT on receipt of a REGISTER request including escaped characters in the SIP-URI of the Contact header, sends a Success (200 OK) response. Config: B or C SUT: Proxy or Redirect Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RR_V_002 | Tx Success (escaped delimiters in SIP-URI of Contact) |
| Ensure that the SUT on receipt of a REGISTER request including escaped
delimiters in SIP-URI of the Contact header, sends a Success (200 OK) response. Config: B or C SUT: Proxy or Redirect Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RR_V_003 | Tx Success (ignore non-understood uri-parameters in SIP-URI of Contact) |
| Ensure that the SUT on receipt of a REGISTER request including
non-understood uri- parameters in SIP-URI of the Contact header, ignores it and sends a Success (200 OK) response. Config: B or C SUT: Proxy or Redirect Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RR_V_004 | Tx Success (header parameter in SIP-URI of Contact) |
| Ensure that the SUT on receipt of a REGISTER request including a
header parameter in the SIP-URI of the Contact header, sends a Success (200 OK) response. Config: B or C SUT: Proxy or Redirect Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RR_V_005 | Tx Success (method parameter in SIP-URI of Contact=REGISTER) |
| Ensure that the SUT on receipt of a REGISTER request including a
method parameter set to REGISTER in the SIP-URI of Contact header, sends a Success (200 OK) response. Config: B or C SUT: Proxy or Redirect Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RR_V_006 | Tx Success (ignore unknown header in REGISTER) |
| Ensure that the SUT on receipt of a REGISTER request including an
unknown header, ignores them and sends a Success (200 OK) response. Config: B or C SUT: Proxy or Redirect Ref: RFC3261 [1] section 8.2.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RR_V_007 | Tx Success (headers wih upper & lower cases) |
| Ensure that the SUT on receipt of a REGISTER request including headers
named with upper and lower cases, sends a Success (200 OK) response. Config: B or C SUT: Proxy or Redirect Ref: RFC3261 [1] section 7.3.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RR_V_008 | Tx Success (headers=values with several leading white space & extended over multiple lines) |
| Ensure that the SUT on receipt of a REGISTER request including headers
set with values preceded by several leading white space and properly extended over multiple lines, sends a Success (200 OK) response. Config: B or C SUT: Proxy or Redirect Ref: RFC3261 [1] section 7.3.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RR_V_009 | Tx Success (Contact=multiple values seperated by comma) |
| Ensure that the SUT on receipt of a REGISTER request including a
Contact header set with multiple values separated by a comma, sends a Success (200 OK) response. Config: B or C SUT: Proxy or Redirect Ref: RFC3261 [1] section 7.3.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RR_V_010 | Tx Success (multiple Contact headers) |
| Ensure that the SUT on receipt of a REGISTER request including
multiple Contact headers, sends a Success (200 OK) response. Config: B or C SUT: Proxy or Redirect Ref: RFC3261 [1] section 7.3.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RR_V_011 | Tx Success (expires parameter with upper 6 lower cases of Contact) |
| Ensure that the SUT on receipt of a REGISTER request including an
expires parameter named with upper and lower cases of Contact header, sends a Success (200 OK) response. Config: B or C SUT: Proxy or Redirect Ref: RFC3261 [1] section 7.3.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RR_V_012 | Tx Success (headers=short names) |
| Ensure that the SUT on receipt of a REGISTER request including headers
set with short names, sends a Success (200 OK) response. Config: B or C SUT: Proxy or Redirect Ref: RFC3261 [1] section 7.3.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RR_V_013 | Tx Success (REGISTER Rx over TCP with several CRLF before start-line) |
| Ensure that the SUT, on receipt of a REGISTER request over a
stream-oriented (TCP) transport with several CRLF before the start-line, sends a Success (200 OK) response. Pre-condition: SUT is in the idle state. User Action: No action. Test case will tear down call automatically when finished. Config: B or C SUT: Proxy or Redirect Ref: RFC3261 [1] section 7.5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ MG/ RR/ SIP_MG_RR_I |
|
| SIP_MG_RR_I_001 | Tx Success (ignore Request line SIP-version in lower cases) |
| Ensure that the SUT on receipt of a REGISTER request including a Request line SIP-Version in lower cases ignores it and sends a Success (200 OK) response. Config: B or C SUT: Register Ref: RFC3261 [1] section 7.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RR_I_002 | Tx Success (ignore ttl parameter in From & To) |
| Ensure that the SUT on receipt of a REGISTER request including a ttl
parameter in the From and To headers ignores them and sends a Success (200 OK) response. Config: B or C SUT: Register Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RR_I_003 | Tx Success (ignore header parameters in SIP-URI of From & To) |
| Ensure that the SUT on receipt of a REGISTER request including
header parameters in the SIP-URI of the From and To headers ignores them and sends a Success (200 OK) response. Config: B or C SUT: Register Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RR_I_004 | Tx Success (ignore method parameters in SIP-URI of From & To=INVITE) |
| Ensure that the SUT on receipt of a REGISTER request including method
parameters set to INVITE in the SIP-URI of the From and To headers ignores them and sends a Success (200 OK) response. Pre-condition: SUT is in the idle state. User Action: No action. Test case will tear down call automatically when finished. Config: B or C SUT: Proxy or Redirect Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RR_I_005 | Tx Success (ignore Alert-Info header) |
| Ensure that the SUT on receipt of a REGISTER request including an
Alert-Info header ignores it and sends a Success (200 OK) response Pre-condition: SUT is in the idle state. User Action: No action. Test case will tear down call automatically when finished. Config: B or C SUT: Proxy or Redirect Ref: RFC3261 [1] section 7.3.2 and 20, table 2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RR_I_006 | Tx 400 Bad Request (no CSeq header in REGISTER) |
| Ensure that the SUT on receipt of a REGISTER request without CSeq
header sends a Bad Request (400 Bad Request) response Pre-condition: SUT is in the idle state. User Action: No action. Test case will tear down call automatically when finished. Config: B or C SUT: Proxy or Redirect Ref: RFC3261 [1] section 21.4.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ MG/ OE |
Checks OE part of MG signaling |
| ETSI/ MG/ OE/ SIP_MG_OE_V |
|
| SIP_MG_OE_V_001 | Rx 200 OK, Tx ACK Rq (ignore non-understood uri-parameter in SIP-URI of From) |
| Ensure that the SUT, when an INVITE client transaction is in the
Calling state, on receipt of a Success (200 OK) response including non-understood uri-parameters in SIP-URI of the From header, ignores it and sends an ACK request. Config: A SUT: User Agent Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_OE_V_002 | Rx 200 OK, Tx ACK Rq (header parameters in SIP-URI of Contact) |
| Ensure that the SUT, when an INVITE client transaction is in the
Calling state, on receipt of a Success (200 OK) response including header parameters in the SIP-URI of the Contact header, sends an ACK request. Config: A SUT: User Agent Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_OE_V_003 | Rx 299 OK, Tx ACK Rq (non-defined last 2 digits) |
| Ensure that the SUT, when an INVITE client transaction is in the
Calling state, on receipt of a Success (299 OK) response with non-defined last two digits, sends an ACK request. Config: A SUT: User Agent Ref: RFC3261 [1] section 7.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_OE_V_004 | Rx 200 PERFECT, Tx ACK Rq (unknown reason phrase) |
| Ensure that the SUT, when an INVITE client transaction is in the
Calling state, on receipt of a Success (200 PERFECT) response with an unknown reason phrase, sends an ACK request. Config: A SUT: User Agent Ref: RFC3261 [1] section 7.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_OE_V_005 | Rx 200 OK, Tx ACK Rq (headers with upper & lower cases) |
| Ensure that the SUT, when an INVITE client transaction is in the
Calling state, on receipt of a Success (200 OK) response including headers named with upper and lower cases, sends an ACK request. Config: A SUT: User Agent Ref: RFC3261 [1] section 7.3.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_OE_V_006 | Rx 200 OK, Tx ACK Rq (values with leading white space & extended over multiple lines) |
| Ensure that the SUT, when an INVITE client transaction is in the
Calling state, on receipt of a Success (200 OK) response including headers set with values preceded by several leading white space and properly extended over multiple lines, sends an ACK request. Config: A SUT: User Agent Ref: RFC3261 [1] section 7.3.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_OE_V_007 | Rx 200 OK, Tx ACK Rq (headers=short names) |
| Ensure that the SUT, when an INVITE client transaction is in the
Calling state, on receipt of a Success (200 OK) response including a headers set with short names, sends an ACK request. Config: A SUT: User Agent Ref: RFC3261 [1] section 7.3.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_OE_V_008 | Rx BYE, Tx Success (escaped characters in SIP-URI of From) (dialog established) |
| Ensure that the SUT, once a dialog has been established, on receipt of
a BYE request including escaped characters in the SIP-URI of the From header, sends a Success (200 OK) response. Config: A SUT: User Agent Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_OE_V_009 | Rx BYE, Tx Success (escaped delimiters in SIP-URI of From) (dialog established) |
| Ensure that the SUT, once a dialog has been established, on receipt of
a BYE request including escaped delimiters in the SIP-URI of the From header, sends a Success (200 OK) response. Config: A SUT: User Agent Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_OE_V_010 | Tx Success (non-understood uri-parameters in SIP-URI of BYE Request-URI) (dialog established) |
| Ensure that the SUT, once a dialog has been established, on receipt of a BYE request including non-understood uri-parameters in the SIP-URI of the BYE Request-URI, sends a Success (200 OK) response. Config: A SUT: User Agent Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_OE_V_011 | Rx BYE, Tx Success (ignore unknown header) (dialog established) |
| Ensure that the SUT, once a dialog has been established, on receipt of a BYE request including an unknown header, ignores it and sends a Success (200 OK) response. Config: A SUT: User Agent Ref: RFC3261 [1] section 8.2.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_OE_V_012 | Rx BYE, Tx Success (headers with upper & lower cases) (dialog established) |
| Ensure that the SUT, once a dialog has been established, on receipt of
a BYE request including headers named with upper and lower cases sends a Success (200 OK) response. Config: A SUT: User Agent Ref: RFC3261 [1] section 7.3.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_OE_V_013 | Rx Bye, Tx Success (headers=values with leading white space & extended over multiple lines) |
| Ensure that the SUT, once a dialog has been established, on receipt of
a BYE request including headers set with values preceded by several leading white space and properly extended over multiple lines, sends a Success (200 OK) response. Config: A SUT: User Agent Ref: RFC3261 [1] section 7.3.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_OE_V_014 | Rx BYE, Tx Success (headers=short names) (dialog established) |
| Ensure that the SUT, once a dialog has been established, on receipt of
a BYE request including headers set with short names, sends a Success (200 OK) response. Config: A SUT: User Agent Ref: RFC3261 [1] section 7.3.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_OE_V_015 | Rx 65.535 bytes Success, Tx ACK Rq (session description parameters acceptable) |
| Ensure that the SUT, when an INVITE client transaction is in the
Calling state, on receipt of a 65.535 bytes long Success (200 OK) response including session description parameters that it can accept, transported by UDP, sends an ACK request. Config: A SUT: User Agent Ref: RFC3261 [1] section 18.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ MG/ OE/ SIP_MG_OE_I |
|
| SIP_MG_OE_I_001 | Rx Success, ignore transport parameters in From & To, Tx ACK (INVITE client TR in Calling state) |
| Ensure that the SUT, when an INVITE client transaction is in the the
Calling state, on receipt of a Success (200 OK) response including transport parameters in the From and To headers, ignores them and sends an ACK request. Config: A SUT: User Agent Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_OE_I_002 | Rx Success, ignore ttl parameters in From & To, Tx ACK (INVITE client tr in Calling state) |
| Ensure that the SUT, when an INVITE client transaction is in the
Calling state, on receipt of a Success (200 OK) response with a ttl parameter in the >From and To headers, ignores them and sends an ACK request. Config: A SUT: User Agent Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_OE_I_003 | Rx Success, ignore URI header parameter in From & To, Tx ACK (INVITE client tr in Calling state) |
| Ensure that the SUT, when an INVITE client transaction is in the
Calling state, on receipt of a Success (200 OK) response with an URI including a header parameter in the To and From headers ignores them and sends an ACK request. Config: A SUT: User Agent Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_OE_I_004 | Rx Success, ignore method parameter in From & To, Tx ACK (INVITE client tr in Calling state) |
| Ensure that the SUT, when an INVITE client transaction is in the
Calling state, on receipt of a Success (200 OK) response with a method parameter in the To and From headers ignores them and sends an ACK request. Config: A SUT: User Agent Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_OE_I_005 | Rx BYE, ignore maddr parameters in From & To, Tx Success (dialog established) |
| Ensure that the SUT, once a dialog has been established, on receipt of
a BYE request including maddr parameters in the From and To headers ignores them and sends a Success (200 OK) response without maddr parameter. Config: A SUT: User Agent Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_OE_I_006 | Rx BYE, ignore SIP-URI header parameters of From & To, Tx Success (dialog established) |
| Ensure that the SUT, once a dialog has been established, on receipt of
a BYE request including header parameters in the SIP-URI of the From and To headers ignores them and sends a Success (200 OK) response. Config: A SUT: User Agent Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_OE_I_007 | Rx BYE, ignore method parameters=CANCEL parameter in SIP-URI of From & To, Tx Success (dialog established) |
| Ensure that the SUT, once a dialog has been established, on receipt of
a BYE request including method parameters set to CANCEL parameter in the SIP-URI of the From and To headers ignores them and sends a Success (200 OK) response. Config: A SUT: User Agent Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_OE_I_008 | Rx BYE, ignore In-Reply-To header, Tx Success (dialog established) |
| Ensure that the SUT, once a dialog has been established, on receipt of
a BYE request including an In-Reply-To header ignores it and sends a Success (200 OK) response . Config: A SUT: User Agent Ref: RFC3261 [1] sections 7.3.2 and 20, table 2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_OE_I_009 | Rx Success, shorter body, no Tx ACK (INVITE client TR in Calling state, UDP used) |
| Ensure that the SUT, when an INVITE client transaction is in the
Calling state while a message-oriented (UDP) transport is used, on receipt of a Success (200 OK) response including a body part shorter than the length indicated in the Content-Length header field, discards it and does not send a ACK request. Config: A SUT: User Agent Ref: RFC3261 [1] section 18.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_OE_I_010 | Rx Success, longer body part, ignore extra bytes, Tx ACK (INVITE client TR in Calling state, UDP used) |
| Ensure that the SUT, when an INVITE client transaction is in the
Calling state while a message-oriented (UDP) transport is used, on receipt of a Success (200 OK) response including a body part longer than the length indicated in the Content-Length header field, ignores extra bytes and sends a ACK request. Config: A SUT: User Agent Ref: RFC3261 [1] section 18.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ MG/ TE |
Checks TE part of MG signaling |
| ETSI/ MG/ TE/ SIP_MG_TE_V |
|
| SIP_MG_TE_V_001 | Rx INVITE, Tx Success with 1xx response (escaped characters in SIP-URI of Contact) |
| Ensure that the SUT on receipt of an INVITE request including escaped
characters in the SIP-URI of the Contact header, sends a Success (200 OK) response proceeded optionally by informational (1xx) response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_TE_V_002 | Rx INVITE, Tx Success with 1xx response (escaped delimiters in SIP-URI of Contact) |
| Ensure that the SUT on receipt of an INVITE request including
escaped delimiters in the SIP-URI of the Contact header, sends a Success (200 OK) response preceded optionally by informational (1XX) response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_TE_V_003 | Rx INVITE, Tx Success with 1xx response (non-understood uri-parameters in SIP-URI of Contact) |
| Ensure that the SUT on receipt of an INVITE request including
non-understood uri-parameters in the SIP-URI of the Contact header, sends a Success (200 OK) response preceded optionally by informational (1XX) response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_TE_V_004 | Rx INVITE, Tx Success with 1xx response (header parameter in SIP-URI of Contact) |
| Ensure that the SUT on receipt of an INVITE request including a header parameter in the SIP-URI of the Contact header, sends a Success (200 OK) response preceded optionally by informational (1XX) response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_TE_V_005 | Rx INVITE, Tx Success with 1xx response (method parameter=INVITE in SIP-URI of Contact) |
| Ensure that the SUT on receipt of an INVITE request including a method parameter set to INVITE in the SIP-URI of the Contact header, sends a Success (200 OK) response preceded optionally by informational (1XX) response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_TE_V_006 | Rx Rq with non supported methos, Tx 405 Method Not Allowed (Allow header lists set of method supported) |
| Ensure that the SUT on receipt of a request including a
non-supported Method, sends a Method not allowed (405 Method Not Allowed) response including an Allow header that lists the set of method supported. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 8.2.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_TE_V_007 | Rx INVITE, ignore unknown header, Tx Success with 1XX response |
| Ensure that the SUT on receipt of an INVITE request including an unknown header, ignores them and sends a Success (200 OK) response preceded optionally by informational (1XX) response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 8.2.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_TE_V_008 | Rx INVITE, Tx Success with 1XX response (headers with upper & lower cases) |
| Ensure that the SUT on receipt of an INVITE request including headers named with upper and lower cases, sends a Success (200 OK) response preceded optionally by informational (1XX) response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 7.3.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_TE_V_009 | Rx INVITE, Tx Success with 1XX response (headers=several leading white space extended over multiple lines) |
| Ensure that the SUT on receipt of an INVITE request including headers
set with values preceded by several leading white space and properly extended over multiple lines, sends a Success (200 OK) response preceded optionally by informational (1XX) response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 7.3.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_TE_V_010 | Rx INVITE, Tx Success with 1XX response (Via=multiple values seperated by comma) |
| Ensure that the SUT on receipt of an INVITE request including a Via header set with multiple values separated by a comma, sends a Success (200 OK) response preceded optionally by informational (1XX) response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 7.3.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_TE_V_011 | Rx INVITE, Tx Success with 1XX response (multiple Via headers) |
| Ensure that the SUT on receipt of an INVITE request including
multiple Via headers, sends a Success (200 OK) response preceded optionally by informational (1XX) response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 7.3.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_TE_V_012 | Rx INVITE, Tx Success with 1XX response (branch parameter with upper & lower cases of Via header) |
| Ensure that the SUT on receipt of an INVITE request including a branch parameter named with upper and lower cases of Via header, sends a Success (200 OK) response preceded optionally by informational (1XX) response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 7.3.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_TE_V_013 | Rx INVITE, Tx Success with 1XX response (headers=short names) |
| Ensure that the SUT on receipt of an INVITE request including
headers set with short names, sends a Success (200 OK) response preceded optionally by informational (1XX) response . Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 7.3.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_TE_V_014 | Rx 65.535 byte INVITE, Tx Success with 1XX response (acceptable session description parameters transported by UDP) |
| Ensure that the SUT on receipt of a 65.535 bytes long INVITE request
including session description parameters that it can accept, transported by UDP, sends a Success (200 OK) response, preceded optionally by informational (1XX) response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 18.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_TE_V_014_jim | Rx 65.535 byte INVITE, Tx Success with 1XX response (acceptable session description parameters transported by UDP) |
| Ensure that the SUT on receipt of a 65.535 bytes long INVITE request
including session description parameters that it can accept, transported by UDP, sends a Success (200 OK) response, preceded optionally by informational (1XX) response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 18.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_TE_V_015 | Rx INVITE, Tx Success with 1XX response (several CRLF before start-line, TCP transport) |
| Ensure that the SUT, on receipt of a INVITE request over a
stream-oriented (TCP) transport with several CRLF before the start-line, sends a Success (200 OK) response preceded optionally by informational (1XX) response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 7.5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ MG/ TE/ SIP_MG_TE_I |
|
| SIP_MG_TE_I_001 | Rx INVITE, Tx Success with 1XX response (SIP-Version in lowercase) |
| Ensure that the SUT on receipt of an INVITE request with
SIP-Version in lowercase, sends a Success (200 OK) response preceded optionally by informational (1xx) response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 7.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_TE_I_002 | Rx INVITE, ignore maddr parameter in From & To, Tx Success with 1XX response |
| Ensure that the SUT on receipt of an INVITE request including a
maddr parameter in the From and To headers, ignores them and sends a Success (200 OK) response, preceded optionally by informational (1XX) response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_TE_I_003 | Rx INVITE, ignore maddr parameter in SIP-URI of From & To, Tx Success with 1XX response |
| Ensure that the SUT on receipt of an INVITE request including
header parameters in the SIP-URI of the From and To headers, ignores them and sends a Success (200 OK) response, preceded optionally by informational (1XX) response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_TE_I_004 | Rx INVITE, ignore method parameters=CANCEL in SIP-URI of From & To, Tx Success with 1XX response |
| Ensure that the SUT on receipt of an INVITE request including
method parameters set to CANCEL in the SIP-URI of the From and To headers, ignores them and sends a Success (200 OK) response, preceded optionally by informational (1XX) response Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_TE_I_005 | Rx INVITE, Tx 400 Bad Request (no Call-ID header) |
| Ensure that the SUT on receipt of an INVITE request without
Call-ID header sends a Bad Request (400 Bad Request) response. Config: A SUT: User Agent Status: Recommended Ref: RFC3261 [1] section 21.4.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_TE_I_006 | Rx INVITE, ignore Retry-After header field, Tx Success with 1XX response |
| Ensure that the SUT on receipt of an INVITE request including
header field Retry-After, ignores it and sends a Success (200 OK) response, preceded optionally by informational (1XX) response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 7.3.2 and 20, table 2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_TE_I_007 | Rx INVITE, Tx 400 Bad Request (shorter body part, UDP transport used) |
| Ensure that the SUT, on receipt of an INVITE request, while a message-oriented (UDP) transport is used, including a body part shorter than the length indicated in the Content-Length header field, sends a Bad Request (400 Bad Request) response. Config: A SUT: User Agent Status: Recommended Ref: RFC3261 [1] section 18.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_TE_I_008 | Rx INVITE, Tx Success with 1XX response (longer body part, UDP transport used) |
| Ensure that the SUT, on receipt of an INVITE request, while a message-oriented (UDP) transport is used, including a body part longer than the length indicated in the Content-Length header field, ignores extra bytes and sends a Success (200 OK) response, preceded optionally by informational (1XX) response . Config: A SUT: User Agent Status: Recommended Ref: RFC3261 [1] section 18.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ MG/ PR |
Checks PR part of MG signaling |
| ETSI/ MG/ PR/ SIP_MG_PR_V |
|
| SIP_MG_PR_V_001 | Fwd INVITE Rq (escaped characters in SIP-URI of Contact) |
| Ensure that the SUT on receipt of an INVITE request including escaped
characters in the SIP-URI of the Contact header forwards the message. Config: B SUT: Proxy Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_PR_V_002 | Fwd INVITE Rq (escaped delimiters in SIP-URI of Contact) |
| Ensure that the SUT on receipt of an INVITE request including escaped
delimiters in the SIP-URI of the Contact header forwards the message. Config: B SUT: Proxy Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_PR_V_003 | Fwd INVITE Rq (non-understood uri-parameters in SIP-URI of Contact) |
| Ensure that the SUT on receipt of an INVITE request including
non-understood uri-parameters in the SIP-URI of the Contact header forwards the message. Config: B SUT: Proxy Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_PR_V_004 | Fwd INVITE Rq (header parameter in SIP-URI of Contact) |
| Ensure that the SUT on receipt of an INVITE request including a header
parameter in the SIP-URI of the Contact header forwards the message. Config: B SUT: Proxy Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_PR_V_005 | Fwd INVITE Rq (method parameter=INVITE in SIP-URI of Contact) |
| Ensure that the SUT on receipt of an INVITE request including a method
parameter set to INVITE in the SIP-URI of the Contact header forwards the message. Config: B SUT: Proxy Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_PR_V_006 | Fwd INVITE Rq, no remove/modify unknown header |
| Ensure that the SUT on receipt of an INVITE request including unknown
header forwards the message without removing or modifying those fields. Config: B SUT: Proxy Ref: RFC3261 [1] section 8.2.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_PR_V_007 | Fwd INVITE Rq (headers named with upper & lower cases) |
| Ensure that the SUT on receipt of an INVITE request including headers
named with upper and lower cases forwards the message. Config: B SUT: Proxy Ref: RFC3261 [1] section 7.3.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_PR_V_008 | Fwd INVITE Rq (headers with several leading white space extended over multiple lines) |
| Ensure that the SUT on receipt of an INVITE request including headers
set with values preceded by several leading white space and properly extended over multiple lines forwards the message. Pre-condition: User Action: No action. Test case will tear down call automatically when finished. Config: B SUT: Proxy Ref: RFC3261 [1] section 7.3.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_PR_V_009 | Fwd INVITE Rq (Via=multiple values seperated by comma) |
| Ensure that the SUT on receipt of an INVITE request including a Via
header set with multiple values separated by a comma forwards the message after having inserted its own Via header value without changing the order of these field values. Pre-condition: SUT is in the idle state. User Action: No action. Test case will tear down call automatically when finished. Config: B SUT: Proxy Ref: RFC3261 [1] sections 7.3.1 and 10.46.4. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_PR_V_010 | Fwd INVITE Rq (multiple Via headers) |
| Ensure that the SUT on receipt of an INVITE request including multiple
Via headers forwards the message after having inserted its own Via header value but without changing the order of these fields. Pre-condition: SUT is in the idle state. User Action: No action. Test case will tear down call automatically when finished. Config: B SUT: Proxy Ref: RFC3261 [1] sections 7.3.1 and 10.46.4. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_PR_V_011 | Fwd INVITE Rq (branch parameter names with upper & lower case in Via) |
| Ensure that the SUT on receipt of an INVITE request including a branch
parameter named with upper and lower cases in Via header forwards the message. Pre-condition: SUT is in the idle state. User Action: No action. Test case will tear down call automatically when finished. Config: B SUT: Proxy Ref: RFC3261 [1] section 7.3.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_PR_V_012 | Rx 299 OK with non-defined last 2 digits, Fwd Msg (after having Fwded INVITE Rq) |
| Ensure that the SUT after having forwarded an INVITE request, on
receipt of a Success (299 OK) response with non-defined last two digits forwards the message. Pre-condition: SUT is in the idle state. User Action: No action. Test case will tear down call automatically when finished. Config: B SUT: Proxy Ref: RFC3261 [1] section 7.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_PR_V_013 | Rx 200 PERFECT with unknown reason phrase, Fwd Msg (after having Fwded INVITE Rq) |
| Ensure that the SUT after having forwarded an INVITE request, on
receipt of a Success (200 PERFECT) response with an unknown reason phrase forwards the message. Pre-condition: SUT is in the idle state. User Action: No action. Test case will tear down call automatically when finished. Config: B SUT: Proxy Ref: RFC3261 [1] section 7.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_PR_V_014 | Fwd INVITE Rq (headers=short names) |
| Ensure that the SUT on receipt of an INVITE request including headers
set with short names forwards the message. Pre-condition: SUT is in the idle state. User Action: No action. Test case will tear down call automatically when finished. Config: B SUT: Proxy Ref: RFC3261 [1] section 7.3.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_PR_V_015 | Fwd 65.535 bytes long INVITE Rq |
| Ensure that the SUT on receipt of a 65.535 bytes long INVITE request
forwards the message. Pre-condition: SUT is in the idle state. Config: B SUT: Proxy Ref: RFC3261 [1] section 18.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_PR_V_016 | Fwd INVITE Rq (TCP transport with several CRLF before start-line) |
| Ensure that the SUT, on receipt of a INVITE request over a
stream-oriented (TCP) transport with several CRLF before the start-line, forwards the message. Pre-condition: SUT is in the idle state. User Action: No action. Test case will tear down call automatically when finished. Config: B SUT: Proxy Ref: RFC3261 [1] section 7.5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ MG/ PR/ SIP_MG_PR_I |
|
| SIP_MG_PR_I_001 | Fwd INVITE Rq (SIP version in lower case) |
| Ensure that the SUT on receipt of an INVITE request with SIP version
in lower case forwards the message. Pre-condition: SUT is in the idle state. User Action: No action. Test case will tear down call automatically when finished. Config: B SUT: Proxy Ref: RFC3261 [1] section 7.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_PR_I_002 | Ignore transport parameter in From & To, Fwd INVITE Rq |
| Ensure that the SUT, on receipt of an INVITE request including a
transport parameter in the >From and To headers, ignores them and forwards the message. Pre-condition: SUT is in the idle state. User Action: No action. Test case will tear down call automatically when finished. Config: B SUT: Proxy Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_PR_I_003 | Ignore header parameters in SIP-URI of From & To, Fwd INVITE Rq |
| Ensure that the SUT, on receipt of an INVITE request including header
parameters in the SIP-URI of the >From and To headers, ignores them and forwards the message. Config: B SUT: Proxy Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_PR_I_004 | Ignore method parameters=CANCEL in SIP-URI of From & To, Fwd INVITE Rq |
| Ensure that the SUT, on receipt of an INVITE request including method
parameters set to CANCEL in the SIP-URI of the From and To headers, ignores them and forwards the message. Pre-condition: SUT is in the idle state. User Action: No action. Test case will tear down call automatically when finished. Config: B SUT: Proxy Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_PR_I_005 | Rx INVITE Rq without Call-Id, Tx 400 Bad Request |
| Ensure that the SUT, on receipt of an INVITE request without Call-Id
header sends a Bad Request (400 Bad Request) response. Pre-condition: SUT is in the idle state. User Action: No action. Test case will tear down call automatically when finished. Config: B SUT: Proxy Ref: RFC3261 [1] section 21.4.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_PR_I_006 | Ignore header field Retry-After, Fwd INVITE Rq |
| Ensure that the SUT on receipt of an INVITE request including header
field Retry-After, ignores it and forwards the message. Pre-condition: SUT is in the idle state. User Action: No action. Test case will tear down call automatically when finished. Config: B SUT: Proxy Ref: RFC3261 [1] sections 7.3.2 and 20, table 2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_PR_I_007 | Rx INVITE Rq, Tx 400 Bad Request (UDP transport, shorter body part than Content-Length) |
| Ensure that the SUT, on receipt of an INVITE request, while a
message-oriented (UDP) transport is used, including a body part shorter than the length indicated in the Content-Length header field, sends a Bad Request (400 Bad Request) response. Pre-condition: SUT is in the idle state. User Action: No action. Test case will tear down call automatically when finished. Config: B SUT: Proxy Ref: RFC3261 [1] section 18.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_PR_I_008 | Ignore extra bytes, Fwd INVITE Rq (UDP transport, longer body part than Content-Length) |
| Ensure that the SUT, on receipt of an INVITE request, while a
message-oriented (UDP) transport is used, including a body part longer than the length indicated in the Content-Length header field, ignores extra bytes and forwards the message. Pre-condition: SUT is in the idle state. User Action: No action. Test case will tear down call automatically when finished. Config: B SUT: Proxy Ref: RFC3261 [1] section 18.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_PR_I_009 | No Fwd 200 OK (UDP transport, shorter body part than Content-Length) |
| Ensure that the SUT, while a message-oriented (UDP) transport is used,
on receipt of a Success (200 OK) response including a body part shorter than the length indicated in the Content-Length header field, discards it and does not forward it. Pre-condition: SUT is in the idle state. User Action: No action. Test case will tear down call automatically when finished. Config: B SUT: Proxy Ref: RFC3261 [1] section 18.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_PR_I_010 | Ignore extra bytes, Fwd 200 OK (UDP, longer body part than Content-Length, INVITE client in Calling state) |
| Ensure that the SUT, when an INVITE client transaction is in the
Calling state while a message-oriented (UDP) transport is used, on receipt of a Success (200 OK) response including a body part longer than the length indicated in the Content-Length header field, ignores extra bytes and forwards it. Pre-condition: SUT is in the idle state. User Action: No action. Test case will tear down call automatically when finished. Config: B SUT: Proxy Ref: RFC3261 [1] section 18.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ MG/ RD |
Checks RD part of MG signaling |
| ETSI/ MG/ RD/ SIP_MG_RD_V |
|
| SIP_MG_RD_V_001 | Rx INVITE Rq, Tx 3XX redirection response to caller (escaped characters in SIP-URI of Contact) |
| Ensure that the SUT on receipt of an INVITE request including escaped
characters in the SIP-URI of the Contact header, sends a 3XX redirection response to the caller. Pre-condition: User Action: No action. Test case will tear down call automatically when finished. Config: C SUT: Redirect Server Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RD_V_002 | Rx INVITE Rq, Tx 3XX redirection response to caller (escaped delimiters in SIP-URI of Contact) |
| Ensure that the SUT, on receipt of an INVITE request including escaped
delimiters in the SIP-URI of the Contact header, sends a 3XX redirection response to the caller. Pre-condition: User Action: No action. Test case will tear down call automatically when finished. Config: C SUT: Redirect Server Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RD_V_003 | Rx INVITE Rq, Tx 3XX redirection response to caller (non-understood uri-parameters in SIP-URI of Contact) |
| Ensure that the SUT, on receipt of an INVITE request including
non-understood uri-parameters in the SIP-URI of the Contact header, sends a 3XX redirection response to the caller. Pre-condition: User Action: No action. Test case will tear down call automatically when finished. Config: C SUT: Redirect Server Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RD_V_004 | Rx INVITE Rq, Tx 3XX redirection response to caller (header parameter in SIP-URI of Contact) |
| Ensure that the SUT, on receipt of an INVITE request including a
header parameter in the SIP-URI of the Contact header, sends a 3XX redirection response to the caller. Pre-condition: User Action: No action. Test case will tear down call automatically when finished. Config: C SUT: Redirect Server Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RD_V_005 | Rx INVITE Rq, Tx 3XX redirection response to caller (method parameter=INVITE in SIP-URI of Contact) |
| Ensure that the SUT, on receipt of an INVITE request including a
method parameter set to INVITE in the SIP-URI of the Contact header, sends a 3XX redirection response to the caller. Pre-condition: User Action: No action. Test case will tear down call automatically when finished. Config: C SUT: Redirect Server Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RD_V_006 | Rx INVITE Rq, Tx 3XX redirection response to caller (unknown header) |
| Ensure that the SUT, on receipt of an INVITE request including an
unknown header, sends a 3XX redirection response to the caller. Pre-condition: User Action: No action. Test case will tear down call automatically when finished. Config: C SUT: Redirect Server Ref: RFC3261 [1] section 8.2.2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RD_V_007 | Rx INVITE Rq, Tx 3XX redirection response to caller (headers with upper & lower cases) |
| Ensure that the SUT, on receipt of an INVITE request including headers
named with upper and lower cases, sends a 3XX redirection response to the caller. Pre-condition: User Action: No action. Test case will tear down call automatically when finished. Config: C SUT: Redirect Server Ref: RFC3261 [1] section 7.3.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RD_V_008 | Rx INVITE Rq, Tx 3XX redirection response to caller (several leading white space extended over multiple lines) |
| Ensure that the SUT, on receipt of an INVITE request including headers
set with values preceded by several leading white space and properly extended over multiple lines, sends a 3XX redirection response to the caller. Pre-condition: User Action: No action. Test case will tear down call automatically when finished. Config: C SUT: Redirect Server Ref: RFC3261 [1] section 7.3.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RD_V_009 | Rx INVITE Rq, Tx 3XX redirection response to caller (Via=multiple values seperated by comma) |
| Ensure that the SUT, on receipt of an INVITE request including a Via
header set with multiple values separated by a comma, sends a 3XX redirection response including the received Via header values, without changing their order, to the caller. Pre-Condition: User Action: No action. Test case will tear down call automatically when finished. Config: C SUT: Redirect Server Ref: RFC3261 [1] sections 7.3.1 and 10.46.4. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RD_V_010 | Rx INVITE Rq, Tx 3XX redirection response to caller (multiple Via headers) |
| Ensure that the SUT, on receipt of an INVITE request including
multiple Via headers, sends a 3XX redirection response including the received Via header values, without changing their order, to the caller. Config: C SUT: Redirect Server Ref: RFC3261 [1] sections 7.3.1 and 10.46.4. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RD_V_011 | Rx INVITE Rq, Tx 3XX redirection response to caller (branch parameter with upper & lower cases in Via) |
| Ensure that the SUT, on receipt of an INVITE request including a
branch parameter named with upper and lower cases in Via header, sends a 3XX redirection to the caller. Config: C SUT: Redirect Server Ref: RFC3261 [1] section 7.3.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RD_V_012 | Rx INVITE Rq, Tx 3XX redirection response to caller (headers=short names) |
| Ensure that the SUT, on receipt of an INVITE request including headers
set with short names, sends a 3XX redirection to the caller. Pre-Condition: User Action: No action. Test case will tear down call automatically when finished. Config: C SUT: Redirect Server Ref: RFC3261 [1] section 7.3.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RD_V_013 | Rx 65.535 bytes long INVITE Rq, Tx 3XX redirection response to caller |
| Ensure that the SUT on receipt of a 65.535 bytes long INVITE request
sends a 3XX redirection to the caller. Config: C SUT: Redirect Server Ref: RFC3261 [1] section 18.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RD_V_014 | Rx INVITE Rq, Tx 3XX redirection response to caller (TCP transport with several CRLF before start-line) |
| Ensure that the SUT, on receipt of a INVITE request over a
stream-oriented (TCP) transport with several CRLF before the start-line, sends a 3XX redirection to the caller. Config: C SUT: Redirect Server Ref: RFC3261 [1] section 7.5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| ETSI/ MG/ RD/ SIP_MG_RD_I |
|
| SIP_MG_RD_I_001 | Rx INVITE Rq, Tx 3XX redirection response to caller (SIP version in lower case) |
| Ensure that the SUT on receipt of an INVITE request with SIP
version in lowercase, sends a 3XX redirection response to the caller. Config: C SUT: Redirect Server Ref: RFC3261 [1] section 7.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RD_I_002 | Rx INVITE Rq, ignore transport parameter in From & To, Tx 3XX redirection to caller |
| Ensure that the SUT, on receipt of an INVITE request including a
transport parameter in the >From and To headers, ignores them and sends a 3XX redirection to the caller. Config: C SUT: Redirect Server Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RD_I_003 | Rx INVITE Rq, ignore header parameters in SIP-URI of From & To, Tx 3XX redirection to caller |
| Ensure that the SUT, on receipt of an INVITE request including header
parameters in the SIP-URI of the >From and To headers, ignores them and sends a 3XX redirection to the caller. Config: C SUT: Redirect Server Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RD_I_004 | Rx INVITE Rq, ignore method parameters=CANCEL in SIP-URI of From & To, Tx 3XX redirection to caller |
| Ensure that the SUT, on receipt of an INVITE request including method
parameters set to CANCEL in the SIP-URI of the From and To headers, ignores them and sends a 3XX redirection to the caller. Config: C SUT: Redirect Server Ref: RFC3261 [1] section 19.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RD_I_005 | Rx INVITE Rq without Call-Id, Tx 400 Bad Request |
| Ensure that the SUT, on receipt of an INVITE request without Call-Id
header sends a Bad Request (400 Bad Request) response. SUT: Redirect Server Ref: RFC3261 [1] section 21.4.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RD_I_006 | Rx INVITE Rq, ignore header field Rety-After, Tx 3XX redirection to caller |
| Ensure that the SUT on receipt of an INVITE request including header
field Retry-After, ignores it and sends a 3XX redirection to the caller. Config: C SUT: Redirect Server Ref: RFC3261 [1] sections 7.3.2 and 20, table 2. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RD_I_007 | Rx INVITE Rq, Tx 400 Bad Request (UDP with shorter body part than Content-Length) |
| Ensure that the SUT, on receipt of an INVITE request, while a
message-oriented (UDP) transport is used, including a body part shorter than the length indicated in the Content-Length header field, sends a Bad Request (400 Bad Request) response. Config: C SUT: Redirect Server Ref: RFC3261 [1] section 18.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_MG_RD_I_008 | Rx INVITE Rq, Tx 3XX redirection to caller (UDP with longer body part than Content-Length) |
| Ensure that the SUT, on receipt of an INVITE request, while a
message-oriented (UDP) transport is used, including a body part longer than the length indicated in the Content-Length header field, ignores extra bytes and sends a 3XX redirection to the caller. Config: C SUT: Redirect Server Ref: RFC3261 [1] section 18.3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| SIP_Torture_Tests | |
| SIP_Torture_Tests/ RFC4475 |
SIPPING Torture tests |
| Test_3_1_1_1 | A short tortuous INVITE |
| his short, relatively human-readable message contains: o line folding all over o escaped characters within quotes o an empty subject o LWS between colons, semicolons, header field values, and other fields o both comma separated and separate listing of header field values o mix or short and long form for the same header field name o unknown header fields o unknown header field with a value that would be syntactically invalid if it were defined in terms of generic-param o unusual header field ordering o unusual header field name character case o unknown parameters of a known header field o uri parameter with no value o header parameter with no value o integer fields (Max-Forwards and CSeq) with leading zeros All elements should treat this as a well-formed request. Precondition: User Action: No action Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_1_2 | Wide range of valid characters |
| This message exercises a wider range of characters in several
key syntactic elements than implementations usually see. Of particular note: o The Method contains non-alpha characters from token. Note that % is not an escape character for this field. A method of IN%56ITE is an unknown method. It is not the same as a method of INVITE o The Request-URI contain unusual, but legal, characters o A branch parameter contains all non-alphanum characters from token o The To header field values quoted-string contains quoted-pair expansions, including a quoted NULL character o The name part of name-addr in the From header field value contains multiple tokens (instead of a quoted string) with all non-alphanum characters from the token production rule. That value also has an unknown header parameter whose name contains the non-alphanum token characters and whose value is a non-ascii range UTF-8 encoded string. The tag parameter on this value contains the non-alphanum token characters o The Call-ID header field value contains the non-alphanum characters from word. Notice that in this production: * % is not an escape character. (It is only an escape character in productions matching the rule escaped) * does not start a quoted-string. None of , or imply that there will be a matching symbol later in the string * The characters []{}()<> do not have any grouping semantics. They are not required to appear in balanced pairs o There is an unknown header field (matching extension-header) with non-alphanum token characters in its name and a UTF8-NONASCII value Precondition: User Action: No action Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_1_3 | Valid use of the % escaping mechanism |
| This INVITE exercises the % HEX HEX escaping mechanism in
several places. The request is syntactically valid. Interesting features include: o The request-URI has sips:user@example.com embedded in its userpart. What that might mean to example.net is beyond the scope of this document. o The From and To URIs have escaped characters in their userparts. o The Contact URI has escaped characters in the URI parameters. Note that the name uri-parameter has a value of value%41 which is NOT equivalent to valueA. Per [RFC2396], unescaping URI components is never performed recursively. Precondition: User Action: No Action Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_1_4 | This register request contains several URIs with nulls in the |
| userpart. The message is well formed - parsers must accept
this message. Implementations must take special care when unescaping the AOR in this request to not prematurely shorten the username. This request registers two distinct contact URIs. Precondition: User Action: No Action Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_1_5 | Use of % when it is not an escape |
| Most of the places % can appear in a SIP message, it is not an
escape character. This can surprise the unwary implementor. The following well-formed request has these properties: o The request method is unknown. It is NOT equivalent to REGISTER o The display-name portion of the To and From header fields is "%Z%45". Note that this is not the same as %ZE o This message has two Contact header field values, not three. %lt;sip:alias2@host2.example.com%gt; is a C%6Fntact header field value Precondition: User Action: No Action Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_1_6 | Message with no LWS between display name and < |
| This OPTIONS request is not valid per the grammar in RFC 3261.
since there is no LWS between the quoted string in the display name and < in the From header field value. This has been identified as a specification bug that will be removed when RFC 3261 is revised. Elements should accept this request as well formed. Precondition: User Action: No Action Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_1_7 | Long values in header fields |
| This well-formed request contains header fields with many values
and values that are very long. Features include: o The To header field has a long display name, and long uri parameter names and values o The From header field has long header parameter names and values, in particular a very long tag o The Call-ID is one long token Precondition: User Action: No Action Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_1_8 | Extra trailing octets in a UDP datagram |
| This message contains a single SIP REGISTER request, which
ostensibly arrived over UDP in a single datagram. The packet contained extra octets after the body (which in this case has zero length). Those octets happen to look like a SIP INVITE request, but (per section 18.3 of [RFC3261]) they are just spurious noise that must be ignored. request normally and ignore the extra bits that look like an INVITE request. If the element is a proxy choosing to forward the REGISTER, the INVITE octets would not appear in the forwarded request. Precondition: User Action: No Action Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_1_9 | Semicolon separated parameters in URI user part |
| This request has a semicolon-separated parameter contained in
the "user" part of the Request-URI (whose value contains an escaped @ symbol). Receiving elements will accept this as a well formed message. The Request-URI will parse such that the user part is "user;par=u@example.net". Precondition: User Action: No Action Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_1_10 | Varied and unknown transport types |
| This request contains Via header field values with all
known transport types and exercises the transport extension mechanism. Parsers must accept this message as well formed. Elements receiving this message would process it exactly as if the 2nd and subsequent header field values specified UDP (or other transport). Precondition: User Action: No Action Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_1_11 | Multipart MIME message |
| This MESSAGE request contains two body parts. The second part
is binary encoded and contains null (0x00) characters. Receivers must take care to frame the received message properly. application above the parser does not support multipart/signed. messages, are available in the security call flow examples document [SIP-SEC]. Precondition: In configuration settins change PX_CONTENT_TYPE_TESTER to multipart/mixed User Action: Off hook phone when it rings Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_1_12 | Unusual reason phrase |
| This 200 response contains a reason phrase other than OK.
The reason phrase is intended for human consumption, and may contain any string produced by / UTF8-NONASCII / UTF8-CONT / SP / HTAB) characters.This response is well formed. A parser must accept this message. Precondition: User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_1_13 | Empty Reason Phrase |
| This well formed response contains no reason phrase. A parser
must accept this message. The space character after the reason code is required. If it were not present, this message could be rejected as invalid (a liberal receiver would accept it anyway). Precondition: User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_2_1 | Extraneous header field separators |
| The Via and header field of this request contains
additional semicolons and commas without parameters or values. The Contact header field contains additional semicolons without parameters. This message is syntactically invalid. Request error. Precondition: User Action: Off hook phone when it rings Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_2_2 | Content length larger than message |
| This is a request message with a Content Length that is larger
than the length of the body. should respond with a 400 Bad Request error. If this message were received over a stream-based transport such as TCP, there is not much you can do but wait for more data on the stream and close the connection if none is forthcoming in a reasonable period of time. Precondition: User Action: Off hook phone when it rings Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_2_3 | Negative Content-Length |
| This request has a negative value for Content-Length. An element receiving this message should respond with an error. This request appeared over UDP, so the remainder of the datagram can simply be discarded. If a request like this arrives over TCP, the framing error is not recoverable and the connection should be closed. The same behavior is appropriate for messages that arrive without a numeric value in the Content-Length header field such as: Content-Length: five User Action: Off hook phone when it rings Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_2_4_a | Request scalar fields with overlarge values |
| This request contains several scalar header field values
outside their legal range. o the Max-Forwards value is >255. o the Expires value is >2**32-1. o the Contact expires parameter value is >2**32-1. Request due to the CSeq error. If only the Max-Forwards field were in error, the element could choose process the request as if the field were absent. If only the expiry values were in error, the element could treat them as if they contained the default values for expiration (3600 in this case). Other scalar request fields that may contain aberrant values include, but are not limited to, the Contact q value, the Timestamp value, and the Via ttl parameter. User Action: No Action Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_2_4_b | Request scalar fields with overlarge values |
| This request contains several scalar header field values
outside their legal range. o the Max-Forwards value is >255. o the Expires value is >2**32-1. o the Contact expires parameter value is >2**32-1. Request due to the CSeq error. If only the Max-Forwards field were in error, the element could choose process the request as if the field were absent. If only the expiry values were in error, the element could treat them as if they contained the default values for expiration (3600 in this case). Other scalar request fields that may contain aberrant values include, but are not limited to, the Contact q value, the Timestamp value, and the Via ttl parameter. User Action: No Action Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_2_4_c | Request scalar fields with overlarge values |
| This request contains several scalar header field values
outside their legal range. o the Max-Forwards value is >255. o the Expires value is >2**32-1. o the Contact expires parameter value is >2**32-1. Request due to the CSeq error. If only the Max-Forwards field were in error, the element could choose process the request as if the field were absent. If only the expiry values were in error, the element could treat them as if they contained the default values for expiration (3600 in this case). Other scalar request fields that may contain aberrant values include, but are not limited to, the Contact q value, the Timestamp value, and the Via ttl parameter. User Action: No Action Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_2_4_d | Request scalar fields with overlarge values |
| This request contains several scalar header field values
outside their legal range. o the Max-Forwards value is >255. o the Expires value is >2**32-1. o the Contact expires parameter value is >2**32-1. Request due to the CSeq error. If only the Max-Forwards field were in error, the element could choose process the request as if the field were absent. If only the expiry values were in error, the element could treat them as if they contained the default values for expiration (3600 in this case). Other scalar request fields that may contain aberrant values include, but are not limited to, the Contact q value, the Timestamp value, and the Via ttl parameter. User Action: No Action Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_2_5 | Response scalar fields with overlarge values |
| their legal range. o The Retry-After field is unreasonably large (note that RFC 3261 does not define a legal range for this field). o The Warning field has a warning-value with more than 3 digits Precondition: User Action: After starting test, have the SUT send an INVITE or REGISTER Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_2_6 | Unterminated quoted string in display-name |
| This is a request with an unterminated quote in the display name
of the To field. An element receiving this request should return an 400 Bad Request error. Precondition: User Action: No Action Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_2_7 | <> enclosing Request-URI |
| This INVITE request is invalid because the Request-URI has
been enclosed within in <>. 400 Bad Request. Elements attempting to be liberal with what they accept may choose to ignore the brackets. If the element forwards the request, it must not include the brackets in the messages it sends. Precondition: User Action: Off hook phone when it rings Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_2_8 | Malformed SIP Request-URI (embedded LWS) |
| Request. (like sip) where that would not introduce ambiguity. Precondition: User Action: No Action Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_2_9 | Multiple SP separating Request-Line elements |
| the start line. is liberal in what it accepts may ignore these extra SP characters while processing the request. If the element forwards the request, it must not include these extra SP characters in the messages it sends. Precondition: User Action: Off hook phone when it rings Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_2_10 | SP characters at end of Request-Line |
| field and the CRLF terminating the Request-Line. is liberal in what it accepts may ignore these extra SP characters while processing the request. If the element forwards the request, it must not include these extra SP characters in the messages it sends. Precondition: User Action: No Action Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_2_11 | Escaped headers in SIP Request-URI |
| Request. An element could choose to be liberal in what it accepts
and ignore the escaped headers. If the element is a proxy, the escaped headers must not appear in the Request-URI of forwarded request (and most certainly must not be translated into the actual header of the forwarded request). Precondition: User Action: Off hook phone when it rings Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_2_12 | Invalid timezone in Date header field |
| This INVITE is invalid as it contains a non GMT time zone in the
SIP Date header field. element shouldnt do that unless the contents of the Date header field were actually important to its processing). An element wishing to be liberal in what it accepts could ignore this value altogether if it wasnt going to use the Date header field anyhow. Otherwise, it could attempt to interpret this date and adjust it to GMT. RFC 3261 explicitly defines the only acceptable timezone designation as valid. Precondition: User Action: Off hook phone when it rings Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_2_13 | Failure to enclose name-addr URI in <> |
| This REGISTER request is malformed. The SIP URI contained in
the Contact Header field has an escaped header, so the field must be in name-addr form (which implies the URI must be enclosed in <>). with a 400 Bad Request. An element choosing to be liberal in what it accepts could infer the angle brackets since there is no ambiguity in this example. In general, that wont be possible. Precondition: User Action: No Action Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_2_14 | Spaces within addr-spec |
| This request is malformed since the addr-spec in the To header
field contains spaces. Parsers receiving this request must not break. It is reasonable to reject this request with a 400 Bad Request response. Elements attempting to be liberal may ignore the spaces. Precondition: User Action: No Action Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_2_15 | Non-token characters in display-name |
| This OPTIONS request is malformed since the display names in the
To and From header fields contain non-token characters but are unquoted. Request response. the missing quotes. If this element were a proxy, it must not propagate the error into the request it forwards. As a consequence, if the fields are covered by a signature, theres not much point in trying to be liberal - the message should be simply rejected. Precondition: User Action: No Action Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_2_16 | Unknown protocol version |
| To an element implementing [RFC3261], this request is malformed
due to its high version number. The element should respond to the request with a 505 Version Not Supported error. Precondition: User Action: No Action Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_2_17 | Start line and CSeq method mismatch |
| This request has mismatching values for the method in the start
line and the CSeq header field. Any element receiving this request will respond with a 400 Bad Request. Precondition: User Action: No Action Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_2_18 | Unknown Method with CSeq method mismatch |
| This message has an unknown method, and a CSeq method tag which
does not match it. Any element receiving this response will should respond with a 501 Not Implemented. A 400 Bad Request is also acceptable, but choosing a 501 (particularly at proxies) has better future-proof characteristics. Precondition: User Action: No Action Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_1_2_19 | Overlarge response code |
| This response has a response code larger than 699. An
element receiving this response should simply drop it. Precondition: User Action: Make a call from the User Agent SUT to the TESTER Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_2_1 | Missing transaction identifier |
| This request indicates support for RFC 3261-style
transaction identifiers by providing the z9hG4bK prefix to the branch parameter, but it provides no identifier. A parser must not break when receiving this message. An element receiving this request could reject the request with a 400 Response (preferably statelessly, as other requests from the source are likely to also have a malformed branch parameter), or it could fall back to the RFC 2543 style transaction identifier. Precondition: User Action: No Action Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_3_1 | Missing Required Header Fields |
| An element receiving this message must not break because of
the missing information. Ideally, it will respond with a 400 Bad Request error. Precondition: User Action: No Action Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_3_2 | Request-URI with unknown scheme |
| This OPTIONS contains an unknown URI scheme in the Request-URI.
A parser must accept this as a well-formed SIP request. An element receiving this request will reject it with a 416 Unsupported URI Scheme response. Precondition: User Action: Request_URI_Invalid_URI_Scheme_TESTER_CFG must be set to a value the SUT can respond to with 416. Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_3_3 | Request-URI with known but atypical scheme |
| that does not commonly appear Request-URIs of SIP requests. A
parser must accept this as a well-formed SIP request. request-URI, it is appropriate to treat it as unknown and return a 416 Unsupported URI Scheme response. If the element might accept some URIs with this scheme, then a 404 Not Found is appropriate for those URIs it doesnt accept. Precondition: User Action: Request_URI_Invalid_URI_Scheme_TESTER_CFG must be set to a value the SUT can respond to with 404 or 416. Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_3_4 | Unknown URI schemes in header fields |
| This message contains registered schemes in the To, From and
Contact header fields of a request. The message is syntactically valid. Parsers must not fail when receiving this message. Precondition: User Action: No Action Config: B SUT: Proxy Ref: rfc4475.txt | |
| Test_3_3_5 | Proxy-Require and Require |
| This request tests proper implementation of SIPs Proxy-Require
and Require extension mechanisms. Extension response containing an Unsupported header field listing these features from either the Require or Proxy-Require header field depending on the role in which the element is responding. Precondition: User Action: No Action Config: B SUT: Proxy Ref: rfc4475.txt | |
| Test_3_3_6 | Unknown Content-Type |
| This INVITE request contains a body of unknown type. It
is syntactically valid. A parser must not fail when receiving it. INVITE. An endpoint receiving this request would reject it with a 415 Unsupported Media Type error. Precondition: User Action: Off hook phone when it rings Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_3_7 | Unknown authorization scheme |
| This REGISTER request contains an Authorization header field with
an unknown scheme. The request is well-formed. A parser must not fail when receiving it. forwards the request, it will include this Authorization header field unmodified in the forwarded messages. authentication will simply ignore the Authorization header field, processing this registration as if the field were not present. A registrar that does care about challenge-response authentication will reject this request with a 401, issuing a new challenge with a scheme it understands. request. A 405 Method Not Allowed is appropriate. Precondition: User Action: No Action Config: A or B SUT: User Agent or Proxy Ref: rfc4475.txt | |
| Test_3_3_8 | Multiple values in single value required fields |
| The message contains a request with multiple Call-ID, To,
From, Max-Forwards and CSeq values. An element receiving this request must not break. Request error. Precondition: User Action: Off hook phone when it rings Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_3_9 | Multiple Content-Length values |
| Multiple conflicting Content-Length header field values appear
in this request. >From a framing perspective, this situation is equivalent to an invalid Content-Length value (or no value at all). request appeared over UDP, so the remainder of the datagram can simply be discarded. If a request like this arrives over TCP, the framing error is not recoverable and the connection should be closed. Precondition: User Action: No Action Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_3_10 | 200 OK Response with broadcast Via header field value |
| This message is a response with a 2nd Via header field
values sent-by containing 255.255.255.255. The message is well formed - parsers must not fail when receiving it. discard it. User Action: Make a call from the User Agent SUT to the TESTER Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_3_11 | Max-Forwards of zero |
| This is a legal SIP request with the Max-Forwards header field
value set to zero. A proxy should not forward the request and respond 483 (Too Many Hops). An endpoint should process the request as if the Max-Forwards field value were still positive. Precondition: User Action: No Action Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_3_12 | REGISTER with a contact header parameter |
| This register request contains a contact where the
unknownparam parameter must be interpreted as being a contact-param and not a url-param. "unknownparam" as a url-parameter for this binding. Likewise, "unknownparam" must not appear as part of the binding during subsequent fetches. parameter names. Precondition: User Action: No Action Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_3_13 | REGISTER with a url parameter |
| This register request contains a contact where the URI has an
unknown parameter. registration must include "unknownparam" as a url-parameter. Precondition: User Action: No Action Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_3_14 | REGISTER with a url escaped header |
| This register request contains a contact where the URI has an
escaped header. registration must include the escaped Route header in the contact URI for this binding. Precondition: User Action: No Action Config: A SUT: User Agent Ref: rfc4475.txt | |
| Test_3_3_15 | Unacceptable Accept offering |
| This request indicates the response must contain a body in an
unknown type. In particular, since the Accept header field does not contain application/sdp, the response may not contain an SDP body. The recipient of this request could respond with a 406 Not Acceptable with a Warning/399 indicating that a response cannot be formulated in the formats offered in the Accept header field. It is also appropriate to respond with a 400 Bad Request since all SIP UAs supporting INVITE are required to support application/sdp. Precondition: User Action: No Action Config: A SUT: User Agent Ref: rfc4475.txt | |
| SIP_Torture_Tests/ RFC5118 |
|
| Test_4_1 | Valid SIP Message with an IPv6 Reference |
| appears in the Request-URI, Via header field and Contact header
field. Precondition: User Action: No action Config: A SUT: User Agent Ref: RFC5118.txt | |
| Test_4_2 | Invalid SIP Message with an IPv6 Reference |
| appears in the Request-URI does not contain the mandated delimeters
for an IPv6 reference ("[" amd "]"). A SIP implementation receiving
this request should respond with a 400 Bad Request error. Precondition: User Action: No action Config: A SUT: User Agent Ref: RFC5118.txt | |
| Test_4_3 | Port Ambiguous in a SIP URI |
| Precondition: User Action: No action Config: A SUT: User Agent Ref: RFC5118.txt | |
| Test_4_4 | Port Unambiguous in a SIP URI |
| Precondition: User Action: No action Config: A SUT: User Agent Ref: RFC5118.txt | |
| Test_4_5 | IPv6 Reference Delimeters in Via Header |
| Precondition: User Action: No action Config: A SUT: User Agent Ref: RFC5118.txt | |
| Test_4_6 | SIP Request with IPv6 Addresses in Session Description Protocol (SDP) Body |
| Precondition: User Action: No action Config: A SUT: User Agent Ref: RFC5118.txt | |
| Test_4_7 | Multiple IP Addresses in SIP Headers |
| Precondition: User Action: No action Config: A SUT: User Agent Ref: RFC5118.txt | |
| Test_4_8 | Multiple Ip Addresses in SDP |
| Precondition: User Action: No action Config: A SUT: User Agent Ref: RFC5118.txt | |
| Test_4_9 | Ipv4-Mapped IPv6 Addresses |
| Precondition: User Action: No action Config: A SUT: User Agent Ref: RFC5118.txt | |
| Test_4_10 | IPv6 Reference Bug is RFC 3261 ABNF |
| Precondition: User Action: No action Config: A SUT: User Agent Ref: RFC5118.txt | |
| MISC | Different extra test cases |
| SIP_mg_te_v_014_back | Rx Other side of SIP_mg_te_v_014 |
| Rx Other side of SIP_mg_te_v_014 | |
| SIP_UA_3262_HV_002 | Ensure that the IUT, SHOULD only put Rack in PRACK method but NOT others |
| Config: A SUT: User Agent Status: Mandatory Ref: RFC3262 section 7.1. / ACATS SIPv1.2 | |
| RAW_001 | Enter Proceeding state on receipt of 199 Unknown |
| state, on receipt of a Unknown (199 Unknown) response enters in the
Proceeding state. User Action: Place a call from the SUT to the Tester. Test case will tear down call automatically. Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 8.1.3.2 and 13.2.2.1, figure 5. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| RAW_002 | Send a Raw Packet |
| Send a Raw Packet | |
| REINVITE_01 | Subscr A dial star code, SUT detect it & Fwd to TESTER using SIP INVITE, Subscr A connect to IVR by TESTER(1) |
| code and forwards call to TESTER (behaving as external feature
server) using SIP INVITE. The TESTER connects subscriber A to IVR where IVR greets subscriber and prompts subscriber to speak the name of the destination say "John Doe". subscriber A to "John Doe". Once "John Doe" phone is answers, the TESTER sends "RE-INVITE" to the subscriber A to connect "John Doe" SDP to Subscriber A followed by receiving 200 Ok from Subscriber A. Eventually John Doe sends BYE to the feature server. ---------------INVITE----> <--- 100 Trying --------- <---- 180 Ringing ------- <----- 200 OK ----------- ------ ACK --------------> ----------- INVITE ( no SDP) ------> From : Caller A To : Caller B <--- 100 Trying --------- <--- 200 OK User B SDP -------- ----- 200 OK ( User A SDP) -------> -------- ACK ( User A SDP) -----> <----- ACK------------------------ Wait for delay ( 1 minute) <------- BYE ----------------- --------- 200 OK BYE ---------> <---- BYE ------------------------ ----- 200 OK BYE -----------------> | |
| REINVITE_02 | Subscr A dial star code, SUT detect it & Fwd to TESTER using SIP INVITE, Subscr A connect to IVR by TESTER(2) |
| code and forwards call to TESTER (behaving as external feature
server) using SIP INVITE. The TESTER connects subscriber A to IVR where IVR greets subscriber and prompts subscriber to speak the name of the destination say "John Doe". subscriber A to "John Doe". Once "John Doe" phone is answers, the TESTER sends "RE-INVITE" to the subscriber A to connect "John Doe" SDP to Subscriber A followed by receiving 200 Ok from Subscriber A. Eventually John Doe sends BYE to the feature server. ---------------INVITE----> <--- 100 Trying --------- <---- 180 Ringing ------- <----- 200 OK ----------- ------ ACK --------------> ----------- INVITE ( no SDP) ------> From : Caller A To : Caller B <--- 100 Trying --------- <--- 200 OK User B SDP -------- ----- 200 OK ( User A SDP) -------> -------- ACK ( User A SDP) -----> <----- ACK------------------------ Wait for delay ( 1 minute) <------- BYE ----------------- --------- 200 OK BYE ---------> <---- BYE ------------------------ ----- 200 OK BYE -----------------> | |
| Mail_Demo | This test suite is used to show the email capability within SAFIRE |
| B2B_ACK_200 | B2B take INVITE in Link 2, modify it & Tx out Link 1. Expect 200 OK on Link 1 & Tx out on Link 2 |
| it out Link 1. It then expects a 200 OK on Link 1 which will be sent
out on Link 2. This test could be used in conjunction with CC_PR_MP_RQ_V_024. Config: B SUT: Proxy Status: Mandatory Ref: RFC3261 [1] section 16.6 item 3. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| B2B_ERR_404 | B2B Fwd INVITE from Link 1 to Link 2. 404 error returned, B2B Fwd response back to Link 1 |
| It then checks that when a 404 error is returned, the B2B forwards the
response back to Link 1. Config: B SUT: B2BUA Status: Ref: | |
| B2B_ERR_488 | B2B Fwd INVITE from Link 1 to Link 2. 48488 error returned, B2B Fwd response back to Link 1 |
| It then checks that when a 48488 error is returned, the B2B forwards
the response back to Link 1. Config: B SUT: B2BUA Status: Ref: | |
| PING_01 | Send PING |
| Config: E SUT: User Agent Status: Ref: | |
| Authentication_PING_01 | Send PING, then REGISTER with authentication |
| Config: E SUT: User Agent Status: Ref: | |
| SIP_INVITE_Flooding_V_1 | Loop around sending INVITES |
| User Action: Config: E SUT: User Agent Status: Ref: | |
| SIP_REGISTER_Flooding_V_1 | Loop around sending INVITES |
| User Action: Config: E SUT: User Agent Status: Ref: | |
| SIP_BYE_Flooding_V_1 | Loop around sending INVITES |
| User Action: Config: E SUT: User Agent Status: Ref: | |
| User_Defined_001 | Demonstrate user defined fields |
| Config: A SUT: User Agent Status: Mandatory Ref: RFC3261 [1] sections 8, 8.2, and 13.3.1.1. / ACATS SIPv1.2 (ETSI TS 102 027-2 v4.1.1 (2006-07)) | |
| Test_All_Signals | |
| Test_All_Messages | |
| Mime_Test | |
| Mime_Test_A | |
| Mime_Test_Receive | |
| Internal_Proxy_Test | |
| SIP_WiPro_Incoming_001 | Receive INVITE from SUT, send a 100 |
| Receive INVITE from SUT, send a 100 | |
| SIP_WiPro_Outgoing_001 | Tx INVITE, receive 200 |
| SIP_Wipro_Transfer_Call | Transfer existing call to another extension |
| User Action: No action Config: C Ref: | |
| SIP_Wipro_Call_Hold | UA 1 initiates call to UA2, puts call on hold, resumes call, then clears out |
| User Action: No action Config: C Ref: | |
| RTP_TEST | |
| RTP_Gen_01 | Send RTP Traffic |
| Config: E SUT: User Agent Status: Ref: | |
| RTP_Gen_02 | Send RTP Traffic |
| Config: E SUT: User Agent Status: Ref: | |
| RTP_Gen_03 | Send RTP Traffic |
| Config: E SUT: User Agent Status: Ref: | |
| RTP_Gen_04 | Send RTP Video Traffic to an EyeBeam Softphone with Video capabilities while sending an audio stream |
| Config: E SUT: User Agent Status: Ref: | |
| Incoming_call | Testing if a complete call can be placed frome the SUT. has been established, to release it sends |
| a BYE request with a To header set to the same value as in the last
received final response. User Action: Place a call from the SUT to the Tester. Terminate the call from the SUT to the Tester. Test case will tear down call automatically. Config: DTAG config SUT: User agent conected via Proxy Status: Tailored scenario for DTAG SIP conformance testing workshop | |
| Outgoing_call | testing of the complete incoming call placed from the UA to the Tester |
| User Action: The Call is placed from the Tester to SUT. SUT-UA has to
take the call and than go on hook to terminate the call. Config: DTAG SUT: UA connected via a proxy | |
| Variable | Default Value | Description |
|---|---|---|
| IP_Address_SUT_Link1 | "192.168.1.41" | IP address of SUT (without port) primary link - Use Colons if IPv6 |
| IP_Address_SUT_Link2 | "192.168.1.41" | IP address of SUT (without port), secondary link for use with Proxy testing - Use Colons if IPv6 |
| IP_Address_SUT_Link3 | "192.168.1.41" | IP address of SUT (without port), third link for use with Proxy testing - Use Colons if IPv6 |
| IP_Address_TESTER_Link1 | "192.168.1.87" | IP address of Tester (without port) primary link - Use Colons if IPv6 |
| IP_Address_TESTER_Link2 | "192.168.1.88" | IP address of Tester (without port), secondary link for use with Proxy testing - Use Colons if IPv6 |
| IP_Address_TESTER_Link3 | "192.168.1.89" | IP address of Tester (without port), third link for use with Proxy testing - Use Colons if IPv6 |
| IP_Address_TESTER_Media1 | "" | Use to override Media IP address. If empty, uses IP_Address_TESTER_Link1 |
| IP_Address_TESTER_Media2 | "" | Use to override Media IP address. If empty, uses IP_Address_TESTER_Link1 |
| IP_Address_TESTER_Media3 | "" | Use to override Media IP address. If empty, uses IP_Address_TESTER_Link1 |
| IP_Domain_SUT_Link1 | "example.com" | Domain name of SUT (without port) primary link |
| IP_Domain_SUT_Link2 | "example.com" | Domain name of SUT (without port) secondary link for use with Proxy testing |
| IP_Domain_SUT_Link3 | "example.com" | Domain name of SUT (without port), third link for use with Proxy testing |
| IP_Domain_TESTER_Link1 | "example.com" | Domain name of Tester (without port) primary link |
| IP_Domain_TESTER_Link2 | "example.com" | Domain name of Tester (without port), secondary link for use with Proxy testing |
| IP_Domain_TESTER_Link3 | "example.com" | Domain name of Tester (without port), third link for use with Proxy testing |
| IP_Domain_Use_Domain | FALSE | Set to TRUE if need to use Domain in messages |
| IP_Register_With_Proxy | FALSE | Set to TRUE if register with Proxy is required |
| IP_Use_Alternate_Request_URI | FALSE | Set to TRUE if alternate URI is to be used |
| IP_Include_Port_In_URI | TRUE | Set to FALSE if URI should not have IP Port |
| IP_DeRegister_On_Exit | FALSE | Set to TRUE if de-register with Proxy is desired |
| IP_SIP_Port_SUT | "5060" | Port to use for testing |
| IP_SIP_Port_TESTER | "5060" | Port to use for testing |
| IP_Transport_Mode | Transport_Param_UDP | Transport used for SIP |
| PHONE_Number_SUT | "sip:9876" | Phone number of SUT |
| PHONE_Number_SUT_Invalid | "sip:9999" | Invalid phone number of SUT |
| PHONE_Number_TESTER_UA1 | "sip:4321" | Phone number of Tester |
| PHONE_Number_TESTER_UA2 | "sip:9876" | Phone number of Tester used for proxy test |
| PHONE_Number_TESTER_UA3 | "sip:9057403002" | Phone number of Tester used for proxy test |
| PHONE_Contact_Screen_Name_UA1 | "UA1" | (null) |
| PHONE_Contact_Screen_Name_UA2 | "UA2" | (null) |
| PHONE_Contact_Screen_Name_UA3 | "UA3" | (null) |
| PING_Firewall | FALSE | Set to TRUE if PING is to be sent to obtain firewall info |
| PX_IMS_MODE | FALSE | Set to TRUE if using IMS headers |
| PX_3GPP_MODE | FALSE | (null) |
| PX_Algorithm | "MD5" | (null) |
| PX_AUTH_Authentication_Mode | 0 | Set Authorization/Proxy_Authorization header. |
| PX_AUTH_UA1_NONCE | "" | (null) |
| PX_AUTH_UA1_CNONCE | "135945015" | (null) |
| PX_AUTH_UA1_PASS | "1234" | (null) |
| PX_AUTH_UA1_QOP | "auth" | (null) |
| PX_AUTH_UA1_REALM | "" | (null) |
| PX_AUTH_UA1_USER | "9057403000" | (null) |
| PX_AUTH_UA2_CNONCE | "135945016" | (null) |
| PX_AUTH_UA2_PASS | "1234" | (null) |
| PX_AUTH_UA2_QOP | "auth" | (null) |
| PX_AUTH_UA2_REALM | "" | (null) |
| PX_AUTH_UA2_USER | "9057403001" | (null) |
| PX_AUTH_UA3_CNONCE | "135945016" | (null) |
| PX_AUTH_UA3_PASS | "1234" | (null) |
| PX_AUTH_UA3_QOP | "auth" | (null) |
| PX_AUTH_UA3_REALM | "" | (null) |
| PX_AUTH_UA3_USER | "9057403002" | (null) |
| PX_Accept_Contact_TESTER | "Accept-Contact: sip:sales@val... | Accept-Contact Tester |
| PX_Accept_Encoding_TESTER | "" | Accept-Encoding Tester - nt-im-2.0 |
| PX_Accept_Language_TESTER | "Accept-Language: en" | Accept-Language Tester as English |
| PX_Acceptable_Payload_1 | "Session Description Protocol:... | Acceptable payload #1 |
| PX_Acceptable_Payload_2 | "Session Description Protocol:... | Acceptable payload #2 |
| PX_Allow_TESTER | "Allow: INVITE, ACK, BYE, CANC... | Allow header |
| PX_Authorization_TESTER | "Authorization: Digest usernam... | Authorization header sent in REGISTER |
| PX_Auto_Trigger_OFF_HOOK | FALSE | Automatically tear down active call |
| PX_Auto_Trigger_ON_HOOK | FALSE | Automatically answer ringing call |
| PX_Auto_Trigger_RESET_SUT | FALSE | Automatically reset SUTs current state |
| PX_CSeq_Base_TESTER | 100 | Base for starting CSeq |
| PX_Call_ID_Base_TESTER | "c3eF6f58-363323Cd-8058EB88-" | Call-ID minus last 8 digits that are randomly generated |
| PX_Contact_3XX_TESTER | "sip:1111@192.168.1.2:5060" | Contact used in 3XX responses |
| PX_Contact_Phone_TESTER | "sip:+19725552222@gw1.atlanta.... | Contact URI in user=phone form |
| PX_Content_Disposition_Empty_TESTER | "Content-Disposition: session;... | Empty Content disposition |
| PX_Content_Disposition_Invalid_TESTER | "Content-Disposition: xyz" | Invalid Content disposition |
| PX_Content_Disposition_Optional_TESTER | "Content-Disposition: session;... | Optional Content disposition |
| PX_Content_Disposition_TESTER | "Content-Disposition: session;... | Content disposition Tester |
| PX_Content_Disposition_Mixed_TESTER | "Content-Disposition: session;... | Content disposition Tester |
| PX_Content_Encoding_Invalid_TESTER | "Content-Encoding: xyz" | Invalid content encoding |
| PX_Content_Encoding_TESTER | "Content-Encoding: gzip" | Content encoding |
| PX_Content_Language_Invalid_TESTER | "Content-Language: zzz" | (null) |
| PX_Content_Language_TESTER | "Content-Language: en" | (null) |
| PX_Content_Type_DTMF_TESTER | "Content-Type: application/dtm... | DTMF Content-type |
| PX_Content_Type_TESTER | "Content-Type: application/sdp... | Content-type used by Tester |
| PX_Content_Type_Text_TESTER | "Content-Type: text/plain" | (null) |
| PX_Content_Type_Mixed_TESTER | "Content-Type: multipart/mixed... | (null) |
| PX_Content_Type_Unacceptable_TESTER | "Content-Type: application/pkc... | Unacceptable Content-Type |
| PX_Content_Type_Stream_TESTER | "Content-Type: application/oct... | Application/octet-stream Content-Type |
| PX_Use_Mixed_Stream_Payload | TRUE | (null) |
| PX_Mixed_Text_Payload_1 | "Hello" | (null) |
| PX_Mixed_Text_Payload_2 | "World!" | (null) |
| PX_Mixed_Stream_Payload_2 | '3082015206092A864886F70D01070... | (null) |
| PX_DomainName_SUT_Home_Registrar | "registrar.home1.net" | Used in 3GPP environment |
| PX_DomainName_SUT_Visited_PCSCF | "pcscf1.visited1.net" | Used in 3GPP environment |
| PX_Firewall_Mode_On | FALSE | Set to TRUE when Tester is outside the firewall where the SUT resides |
| PX_IP_Address_Different_Via_Sentby | "123.123.123.123" | UDP/TCP port for different Via sent-by field |
| PX_IP_Address_Firewall_TESTER | "68.163.247.247" | Use for SIP messages when PX_Firewall_Mode_On is TRUE |
| PX_IP_Address_SUT_Invalid | "99.99.99.99" | (null) |
| PX_IP_Address_SUT_Visited_PCSCF | "192.168.1.201" | Used in 3GPP environment |
| PX_IP_SIP_Port_Different_Via_Sentby | "1234" | (null) |
| PX_Private_User_Identity_UE1 | "user1_private@home1.net" | Used in 3GPP environment |
| PX_Proxy_Domain_Not_Responsible | "@anydomain.com" | Domain Proxy is not responsible for |
| PX_Proxy_No_Target | "sip:12@domain" | Proxy target does not exist |
| PX_Proxy_Require_TESTER | "" | (null) |
| PX_Proxy_Require_TESTER_Not_Supported | "Proxy-Require: abc" | Not supported require |
| PX_Proxy_Resource_Not_Exist | "sip:user@domain" | Proxy resource does not exist |
| PX_Proxy_TESTER | "sip:9999@192.168.1.2" | (null) |
| PX_Public_User_Identity_UE1 | "user1_public1@home1.net" | Used in 3GPP environment |
| PX_Reply_With_Contact_Field | TRUE | If true, use IP address for replies in Contact |
| PX_Record_Route_1 | "sip:p1@192.168.1.2" | Record route 1 |
| PX_Record_Route_1_LR | "sip:p1@192.168.1.2;lr" | Record route 1 LR |
| PX_Record_Route_2 | "sip:p2@192.168.1.2" | Record route 2 |
| PX_Record_Route_2_LR | "sip:p2@192.168.1.2;lr" | Record route 2 LR |
| PX_Remove_Branch_RFC_2543_Compatible_Mode | FALSE | Set to TRUE if no branch is required in Via as per 17.2.3 |
| PX_Use_Accept_Encoding | TRUE | (null) |
| PX_Use_Proxy_Require | TRUE | (null) |
| PX_Use_Virtual_UA | FALSE | (null) |
| PX_Virtual_UA_Code | 0 | (null) |
| PX_Use_X_NT_GUID | FALSE | (null) |
| PX_Use_X_NT_Location | FALSE | (null) |
| PX_Ignore_Port_Failure | FALSE | Set to TRUE to ignore port failures |
| PX_Two_Port_Router_Mode | TRUE | Set to TRUE if SUT can register twice for 2-port router |
| PX_Total_Flooding_Count | 10 | (null) |
| Record_Route_TESTER | "" | Record-route |
| Register_Description_TESTER | "login" | Description contact header for REGISTER messages |
| Register_Expires_TESTER | "expires=86200" | Expires contact header for REGISTER messages |
| Reject_Contact_TESTER | "Reject-Contact: sales@xyz.com... | Reject-Contact Tester |
| Request_Disposition_Fork_TESTER | "Request-Disposition: fork" | Request Disposition Fork |
| Request_Disposition_Queue_TESTER | "Request-Disposition: queue" | Request Disposition Queue |
| Request_Invalid_PX_Proxy_Require_TESTER | "Proxy-Require: whatever" | Invalid Proxy-Request header value |
| Request_Invalid_Require_TESTER | "Require: whatever" | Invalid Request header value |
| Request_URI_Invalid_URI_TESTER | "sip:INVALID@123.123.123.123" | Invalid URI |
| Request_URI_Invalid_URI_Scheme_TESTER_CFG | "nobodyKnowsThisScheme:" | Bad URI scheme on Tester Link1 |
| Request_URI_Bad_URI_Scheme_TESTER_CFG | "invalid_uri_scheme:" | Bad URI scheme on Tester Link1 |
| Request_URI_Bad_URI_Scheme_TESTER_CFG_Secondary | "invalid_uri_scheme2" | Bad URI scheme on Tester Link2 |
| Request_URI_FreeForm_URI_TESTER_CFG | "Bedrock_Phonebook:Fn!Fred;Ln!... | Bad URI scheme on Tester Link1 |
| Require_Replaces_TESTER | "Require: replaces" | (null) |
| Require_TESTER | "" | Require |
| Require_TESTER_Invalid | "xyz" | Invalid Require |
| RTP_Send_Audio_Stream | FALSE | (null) |
| RTP_Use_Audio_Encryption | FALSE | (null) |
| RTP_Tx_Audio_Key | "123451234512345" | Transmit Security Key |
| RTP_Rx_Audio_Key | "123451234512345" | Receive Security Key |
| RTP_PayLoad_Audio_File | "C:\\SAFIRE\\USERS\\larry\\RTP... | This is the file to play as the RTP Audio Stream |
| RTP_PayLoad_Audio_Type | 100 | (null) |
| RTP_PayLoad_Audio_Size | 160 | (null) |
| RTP_Payload_Audio_Packet_Interval | 20 | delay between packets in milli-seconds |
| RTP_Send_Video_Stream | TRUE | (null) |
| RTP_Use_Video_Encryption | FALSE | (null) |
| RTP_Tx_Video_Key | "123451234512345" | Transmit Security Key |
| RTP_Rx_Video_Key | "123451234512345" | Receive Security Key |
| RTP_PayLoad_Video_File | "C:\\SAFIRE\\USERS\\larry\\RTP... | This is the file to play as the RTP Video Stream |
| RTP_PayLoad_Video_Type | 115 | (null) |
| RTP_PayLoad_Video_Size | 1024 | (null) |
| RTP_Payload_Video_Packet_Interval | 20 | delay between packets in milli-seconds |
| SDP_C_Address_Type_TESTER | "IP4" | Address type Tester - IP4 or IP6 |
| SDP_C_Network_Type_TESTER | "IN" | Network type Tester |
| SDP_M_Attribute_1_TESTER | "a=rtpmap:0 pcmu/8000/1" | Media PCM µ Law Attribute Tester |
| SDP_M_Attribute_2_TESTER | "a=rtpmap:8 pcma/8000/1" | Media PCM A Law Attribute Tester |
| SDP_M_Attribute_3_TESTER | "a=rtpmap:18 g729/8000/1" | Media G729 Attribute Tester |
| SDP_M_Attribute_4_TESTER | "a=rtpmap:4 g723.1/8000/1" | Media G723.1 Attribute Tester |
| SDP_M_Attribute_New_TESTER | "a=rtpmap:96 eg711u/8000" | Media new Attribute Tester |
| SDP_M_Attribute_OnHold_TESTER | "a=sendonly" | Media send-only Attribute Tester |
| SDP_M_Attribute_Unacceptable_TESTER | "a=rtpmap:18 g730/8000/1" | Media Attribute Unacceptable Tester |
| SDP_M_Format_1_TESTER | "0" | Media µ Law Tester |
| SDP_M_Format_2_TESTER | "8" | Media A Law Tester |
| SDP_M_Format_3_TESTER | "18" | Media G729 Tester |
| SDP_M_Format_4_TESTER | "4" | Media new |
| SDP_M_Format_New_TESTER | "96" | (null) |
| SDP_M_Port_TESTER | "5008" | Media Port Tester |
| SDP_M_Protocol_TESTER | "RTP/AVP" | Media Protocol Tester |
| SDP_Media_Law | SDP_Media_Law_Preset_1 | Use Media type corresponding to Preset_N e.g. Set to SDP_Media_Law_Preset_1 for SDP_M_Format_1_TESTER & SDP_M_Attribute_1_TESTER Or SDP_Media_Law_Preset_4 for SDP_M_Format_4_TESTER & SDP_M_Atrribute_4_TESTER |
| SDP_O_Address_Type_TESTER | "IP4" | IP address type Tester |
| SDP_O_Network_Type_TESTER | "IN" | Network type Tester |
| SDP_O_Session_ID_TESTER | "8521" | Session ID of Tester |
| SDP_O_Username_TESTER | "Valid8.com-UserAgent" | Username of Tester |
| SDP_O_Version_Number_TESTER | "32" | Version Number of Tester |
| SDP_S_Session_Name_TESTER | "SIP-Call" | Session Name Tester |
| SIP_Torture_Test_Long_Call_Id | "kl24ahsd546folnyt2vbak9sad98u... | (null) |
| SIP_Torture_Test_String_2_2_Line_1 | "INVITE sip:user@company.com S... | Torture-test string |
| SIP_Torture_Test_String_2_2_Line_2 | "To: sip:j_user@company.com" | Torture-test string |
| SIP_Torture_Test_String_2_2_Line_3 | "From: sip:caller@university.e... | Torture-test string |
| SIP_Torture_Test_String_2_2_Line_4 | "Max-Forward: 6" | Torture-test string |
| SIP_Torture_Test_String_2_2_Line_5 | "Call-ID: 0ha0isndaksdj@10.1.1... | Torture-test string |
| SIP_Torture_Test_String_2_2_Line_6 | "Require: newfeature1, newfeat... | Torture-test string |
| SIP_Torture_Test_String_2_2_Line_7 | "Proxy-Require: newfeature3, n... | Torture-test string |
| SIP_Torture_Test_String_2_2_Line_8 | "CSeq: 8 INVITE" | Torture-test string |
| SIP_Version_TESTER | SIP_Version_2 | Version used (only supports V2) |
| Supported_TESTER | "" | Supported SIP Tester |
| Supported_TESTER_UE1 | "path" | (null) |
| T_CALL_ACTIVE_VAL | 5000 | Call duration, time to wait for a response during an Active call |
| T_INTERVAL_TIMER_VAL | 1000 | Time to wait for possible INVITE retransmission |
| T_NOACT_VAL | 10000 | Time to wait for No activity |
| T_T1_VAL | 550 | T1 timer |
| T_T1_VAL_MAX | 1000 | T1 timer max value |
| T_T1_VAL_MIN | 300 | T1 timer min value |
| T_T2_VAL | 4000 | T2 timer, response timeout |
| T_T4_VAL | 5000 | T4 timer, clean up timeout |
| T_TIMER_E_VAL | 500 | Timer E value |
| T_TRANSACTION_TIMER_VAL | 32000 | Timer B (rfc-3261) time to wait for transaction |
| T_WAIT_ACK_VAL | 5000 | Time to wait for ACK request |
| T_WAIT_AUTOANSWER_VAL | 1000 | Time to wait for possible autoanswer |
| T_WAIT_BYE_VAL | 30000 | Time to wait for BYE request |
| T_WAIT_CANCEL_VAL | 30000 | Time to wait for CANCEL request |
| T_WAIT_INVITE_VAL | 30000 | Time to wait for INVITE request |
| T_WAIT_NEXT_PROV_RESPONSE_VAL | 3000 | Time to wait for next provisional response |
| T_WAIT_OPTIONS_VAL | 30000 | Time to wait for OPTIONS request |
| T_WAIT_REGISTER_VAL | 30000 | Time to wait for REGISTER request |
| T_WAIT_REGISTER_INTERVAL_VAL | 500 | Time to wait for Retransmission of REGISTER request BZ 372 |
| T_WAIT_RESPONSE_VAL | 30000 | Time to wait for any response after an INVITE |
| T_WAIT_RESPONSE_BYE_VAL | 30000 | Time to wait for response after a BYE |
| T_WAIT_SEND_CANCEL | 100 | Time to wait before sending a CANCEL |
| T_WAIT_FLOOD_SEND_VAL | 10 | ??????? is it in mms |
| Tag2_TESTER | "tag=b4cih" | TAG used by the Tester |
| Tag_TESTER | "tag=a3bhg" | TAG used by the Tester |
| Timestamp_TESTER | 54 | Timestamp value |
| UNACCEPTABLE_PAYLOAD | "Unacceptable Description" | Unacceptable payload |
| Unknown_Header_TESTER | "Invalid: 6" | Unknown header |
| Unsupported_TESTER | "REGISTER" | Used to generated unsupported method message |
| User_Agent_TESTER | "User-Agent: VALID8 PCC 3.0.31... | Used to generate unsupported method message |
| Via_Multiple_Header_TESTER | "123.123.123.123:5060" | Used in Test Scenario MG_TE_V_010 |
| WWW_Authenticate_TESTER | "WWW-Authenticate: Digest real... | WWW-Authenticate header to be sent by the Tester |
| X_NT_GUID_TESTER | "x-nt-GUID: f984b8e13343e9e9af... | (null) |
| X_NT_Location2_TESTER | "x-nt-location: 71414" | (null) |
| X_NT_Location_TESTER | "x-nt-location: 71414" | (null) |
| Subscription_TESTER | "presence" | (null) |
| User_Defined_1_Prefix | "" | (null) |
| User_Defined_2_Prefix | "" | (null) |
| Mime_File | "C:\\gradient.jpg" | (null) |
| Mime_Type | "image/jpg" | (null) |
| TRIG_Reset_SUT_String | "c:\\\\trigger_reset_SUT.bat" | Name of user-defined batch file to trigger phone reset |
| SrcRTP_Audio_Port | 5062 | (null) |
| SrcRTP_Video_Port | 5064 | (null) |
| KeepAlive | TRUE | (null) |
| Test_Terminate_With_ACK | TRUE | How TESTER checks if SUT is in terminated state TRUE send ACK; FALSE send CANCEL |
| Copyright © ACATS Forum 2008 on behalf of the test suite author. All rights reserved. Specifications may change subject to requirements. |
| 22 Jan 2009 | Produced by SAFIRE V20.05.14.01 www.SAFIRE-World.com |
Test Suite Overview |