SIP_EXT_TS: Valid8.com/ACATS SIP Extensions Conformance Test Suite V.17.06, for use with SIP Signaling Tester
TEST SUITE OVERVIEW

References	ETSI TS 102 027-2 v3.1.1 (2004-11)) / IETF SIP RFC3261
Archive/Project	voip/sip_ext_ts
Version	19171599
Date	09 Aug 2008
Number of Scenarios	1301
Number of Groups	68
Average per Group	19

GROUP/SCENARIO	TEST PURPOSE

SIP_Extensions
SIP_Extensions/ SIP_UA_PRACK
SIP_Extensions/ SIP_UA_PRACK/ SIP_UA_3262_HV
SIP_UA_3262_HV_001	Ensure that the IUT, when it binds RSeq header in a reliable provisional response it SHOULD have value from 1 to 2**32-1
	Config: A SUT: User Agent Status: Mandatory Ref: RFC3262 section 7.1. / ACATS SIPv1.2
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
SIP_UA_3262_HV_003	Ensure that the IUT, SHOULD only put RSeq into 1XX reliable provisional respond and optional in INVITE but NOT other methods
	Config: A SUT: User Agent Status: Mandatory Ref: RFC3262 section 7.1. / ACATS SIPv1.2
SIP_UA_3262_HV_004	Ensure that the IUT, when it bind Rack header in PRACK, it MUST contain two numbers,
	with first number from the RSeq header in the provisional response and the second is the CSeq in the response. Config: A SUT: User Agent Status: Mandatory Ref: RFC3262 section 7.1. / ACATS SIPv1.2
SIP_UA_3262_HV_005	Ensure that the IUT, when it bind Rack header in PRACK, it MUST contain a method tag with value INVITE
	Config: A SUT: User Agent Status: Mandatory Ref: RFC3262 section 7.1. / ACATS SIPv1.2
SIP_UA_3262_HV_006	Ensure that the IUT, when it respond 405 to PRACK method, it MUST have Allow header field in 405
	Config: A SUT: User Agent Status: Mandatory Ref: RFC3262 sections 4 and 6. / ACATS SIPv1.2
SIP_UA_3262_HV_007	Ensure that the IUT, when it responds PRACK, it MUST copy Call-ID header field into the PRACK method
	Config: A SUT: User Agent Status: Mandatory Ref: RFC3262 sections 4 and 6. / ACATS SIPv1.2
SIP_UA_3262_HV_008	Ensure that the IUT, when it responds PRACK, it MUST copy CSeq header field into the PRACK method
	Config: A SUT: User Agent Status: Mandatory Ref: RFC3262 sections 4 and 6. / ACATS SIPv1.2
SIP_UA_3262_HV_009	Ensure that the IUT, when it responds PRACK, it MUST copy From header field into the PRACK method
	Config: A SUT: User Agent Status: Mandatory Ref: RFC3262 sections 4 and 6. / ACATS SIPv1.2
SIP_UA_3262_HV_010	Ensure that the IUT, when it responds PRACK, it MUST have Max-Forwards header field in the PRACK method
	Config: A SUT: User Agent Status: Mandatory Ref: RFC3262 sections 4 and 6. / ACATS SIPv1.2
SIP_UA_3262_HV_011	Ensure that the IUT, when it responds 407 to PRACK, it MUST have Proxy-Authenticate header field in 407
	User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 sections 4 and 6. / ACATS SIPv1.2
SIP_UA_3262_HV_012	Ensure that the IUT, when it responds PRACK, it MUST copy To header field into the PRACK method
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 sections 4 and 6. / ACATS SIPv1.2
SIP_UA_3262_HV_013	Ensure that the IUT, when it responds PRACK, it MUST copy Via header field into the PRACK method
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 sections 4 and 6. / ACATS SIPv1.2
SIP_UA_3262_HV_014	Ensure that the IUT, when it responds 420 to PRACK, it MUST have Unsupported header field in 420
	User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 sections 4 and 6. / ACATS SIPv1.2
SIP_UA_3262_HV_015	Ensure that the IUT, when it responds 401 to PRACK, it MUST have WWW-Authenticate header field in 401
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 sections 4 and 6. / ACATS SIPv1.2
SIP_Extensions/ SIP_UA_PRACK/ SIP_UA_3262_V
SIP_UA_3262_V_001	Ensure that the IUT responds to INVITE reliably using a non-100 provisional respond MUST contain with
	Supported or Require header with value 100rel. User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 3. / ACATS SIPv1.2
SIP_UA_3262_V_002	Ensure that the IUT SHOULD NOT respond reliably for any other methods but INVITE
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 3. / ACATS SIPv1.2
SIP_UA_3262_V_003	Ensure that the IUT, when it receives INVITE with Require header field with option tag 100rel, it MUST send
	non-100 provisional respond reliably if any. User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 3. / ACATS SIPv1.2
SIP_UA_3262_V_004	Ensure that the IUT, when it receives INVITE with Require header field with option tag 100rel, it MUST reject
	it with 420 Bad Extension and include an Unsupported header with 100rel if it does NOT willing to accept reliable provisional respond. User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 3. / ACATS SIPv1.2
SIP_UA_3262_V_005	Ensure that the IUT, when it receives INVITE without either Supported or Require header in INVITE,
	it SHOULD NOT send non-100 provisional respond reliably. Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 3. / ACATS SIPv1.2
SIP_UA_3262_V_006	Ensure that the IUT, it MUST NOT send 100 Trying respond reliably
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 3. / ACATS SIPv1.2
SIP_UA_3262_V_007	Ensure that the IUT, when it sends non-100 provisional respond reliably, the respond MUST contain a Require header field with 100rel and MUST include an RSeq header field
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 3. / ACATS SIPv1.2
SIP_UA_3262_V_008	Ensure that the IUT, when it sends non-100 provisional respond reliably, the RSeq header field MUST have value between 1 to 2**31-1
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 3. / ACATS SIPv1.2
SIP_UA_3262_V_009	Ensure that the IUT, when it receives different non-100 provisional respond reliably for different Request with the RSeq header field with same value, it should proceed like different transaction
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 3. / ACATS SIPv1.2
SIP_UA_3262_V_009_a	Ensure that the IUT, when it receives different non-100 provisional respond reliably for different Request with the RSeq header field with same value, it should proceed like different transaction
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 3. / ACATS SIPv1.2
SIP_UA_3262_V_010	Ensure that the IUT, when it receives PRACK method, it will check the CSeq, From, To, Call-ID headers to match the provisional respond. If not matched, it should returns 481
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 3. / ACATS SIPv1.2
SIP_UA_3262_V_011	Ensure that the IUT, when it receives PRACK method, it will also check the RAck headers to match the provisional respond. If not matched, it should returns 481
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 3. / ACATS SIPv1.2
SIP_UA_3262_V_011_a	Ensure that the IUT, when it receives PRACK method, it will also check the RAck headers to match the provisional respond. If not matched, it should returns 481
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 3. / ACATS SIPv1.2
SIP_UA_3262_V_012	Ensure that the IUT, when it receives a non-100 provisional respond reliably, it SHOULD respond a PRACK
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 3. / ACATS SIPv1.2
SIP_UA_3262_V_013	Ensure that the IUT, when it sends a reliable non-100 provisional respond SHOULD start timer at T1 seconds and doubles for each retransmission until receive matched PRACK
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 3. / ACATS SIPv1.2
SIP_UA_3262_V_014	Ensure that the IUT, when it sends a reliable non-100 provisional respond SHOULD start timer at T1 seconds and doubles for each retransmission until 100rel retry counts is reached or hit 64*T1 seconds when no PRACK is returned, and it should reject the original request with a 5XX response
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 3. / ACATS SIPv1.2
SIP_UA_3262_V_015	Ensure that the IUT, after it receives PRACK, it SHOULD consider the PRACK matches if CSeq-num, and respond-num in the Rack header field of PRACK matches the CSeq, the sequence number from the CSeq and sequence number from the RSeq of the reliable provisional response
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 3. / ACATS SIPv1.2
SIP_UA_3262_V_016	Ensure that the IUT, when it receives a PRACK request that does not match any unacknowledged reliable provisional response (e.g. RAck is not matched), it MUST respond with a 481
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 3. / ACATS SIPv1.2
SIP_UA_3262_V_017	Ensure that the IUT, when it receives a PRACK request that does match an unacknowledged reliable provisional response, it MUST respond with a 2XX response
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 3. / ACATS SIPv1.2
SIP_UA_3262_V_018	Ensure that the IUT, may resend reliable provisional response, but MUST NOT resend it before the first one is acknowledged by PRACK
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 3. / ACATS SIPv1.2
SIP_UA_3262_V_019	Ensure that the IUT, when it sends subsequent reliable provisional response, the RSeq header field for the same request MUST be greater by exactly one
	Pre-Condition: User Action: Do not answer the phone. Let it ring. Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 3. / ACATS SIPv1.2
SIP_UA_3262_V_020	Ensure that the IUT, when it receives subsequent reliable provisional response, the RSeq header field for the same request is not greater by exactly one, 4XX should be returned
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 3. / ACATS SIPv1.2
SIP_UA_3262_V_021	Ensure that the IUT, when it receives subsequent reliable provisional response, the RSeq header field for the same request is correct, it should PRACK it again
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 3. / ACATS SIPv1.2
SIP_UA_3262_V_022	Ensure that the IUT, when it sends final responds 2XX before it gets PRACK, it should stop retransmitting the unacknowledged reliable provisional respond
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 3. / ACATS SIPv1.2
SIP_UA_3262_V_023	Ensure that the IUT, when it wants to insist on reliable delivery of provisional response, it should inserts a Require header with option tag 100rel in the INVITE request
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 4. / ACATS SIPv1.2
SIP_UA_3262_V_024	Ensure that the IUT, MUST NOT bind Require header with value 100rel in any other request but INVITE
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 4. / ACATS SIPv1.2
SIP_UA_3262_V_025	Ensure that the IUT, when it tells UAS it does support reliable provisional response but not insist on using it, it MUST put Supported header field with value 100rel in all the INVITE requests
	Pre-Condition: IUT must be configured to support reliable provisional response (PRACK) but not require it. User Action: Configure IUT to support PRACK but not require it. Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 4. / ACATS SIPv1.2
SIP_UA_3262_V_026	Ensure that the IUT, when it receives a provisional response for initial request that contains a Require header with 100rel, it should consider the response is to be sent reliably
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 4. / ACATS SIPv1.2
SIP_UA_3262_V_027	Ensure that the IUT, when it receives 100 Trying with a Require header with 100rel, it SHOULD NOT consider this is reliably provisional respond
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 4. / ACATS SIPv1.2
SIP_UA_3262_V_027_a	Ensure that the IUT, when it receives 100 Trying with a Require header with 100rel, it SHOULD NOT consider this is reliably provisional respond
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 4. / ACATS SIPv1.2
SIP_UA_3262_V_028	Ensure that the IUT, when it receives retransmitted reliable provisional response after it sends PRACK, it SHOULD NOT retransmit PRACK and retransmissions of reliable provisional response MUST be discarded
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 4. / ACATS SIPv1.2
SIP_UA_3262_V_029	Ensure that the IUT, when it receives an INVITE contains no offer, it MUST has an offer in reliable message send back
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 4. / ACATS SIPv1.2
SIP_UA_3262_V_030	Ensure that the IUT, when it receives an INVITE contains an offer, it MAY generate an answer in a reliable provisional response, the early media should be established before the completion of the call (reception of 2xx)
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 5. / ACATS SIPv1.2
SIP_UA_3262_V_031	Ensure that the IUT, when it sends INVITE without an offer and receives a reliable provisional response with an offer, it MUST generate an answer in the PRACK
	Pre-Condition: IUT must not send SDP on INVITE message User Action: Configure the IUT to not send SDP/offer on the INVITE message. Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 5. / ACATS SIPv1.2
SIP_UA_3262_V_032	Ensure that the IUT, when it sends INVITE contains an offer, it MAY generate additional offer in the PRACK if receives an answer in a reliable provisional response
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Optional Ref: RFC3262 section 5. / ACATS SIPv1.2
SIP_UA_3262_V_033	Ensure that the IUT, when it receives INVITE without an offer and receives PRACK with an offer, it MUST generate an answer in the 2XX to the PRACK
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 5. / ACATS SIPv1.2
SIP_UA_3262_V_034	Ensure that the IUT, when it sends a reliable provisional response with a session description and is unacknowledged when the INVITE is accepted, it MUST delay sending the 2XX until the PRACK acks the provisional response
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 5. / ACATS SIPv1.2
SIP_Extensions/ SIP_UA_PRACK/ SIP_UA_3262_I
SIP_UA_3262_I_001	Ensure that the IUT, when it receives a reliable provisional responds with RSeq with value 0, it should returns 4XX respond
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 7.1. / ACATS SIPv1.2
SIP_UA_3262_I_001_a	Ensure that the IUT, when it receives a reliable provisional responds with RSeq with value 0, it should returns 4XX respond
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 7.1. / ACATS SIPv1.2
SIP_UA_3262_I_001_b	Ensure that the IUT, when it receives a reliable provisional responds with RSeq with value 0, it should returns 4XX respond
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 7.1. / ACATS SIPv1.2
SIP_UA_3262_I_001_NoResp	Ensure that the IUT, when it receives a reliable provisional responds with RSeq with value 0, it should ignore it
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 7.1. / ACATS SIPv1.2
SIP_UA_3262_I_002	Ensure that the IUT, when it receives a method that is not reliable provisional respond (e.g. 2XX) with RSeq header field, it should be ignored
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Optional Ref: RFC3262 section 7.1. / ACATS SIPv1.2
SIP_UA_3262_I_003	Ensure that the IUT, when it receives PRACK with RAck header field with only one number and the method, it should returns 4XX respond
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 7.1. / ACATS SIPv1.2
SIP_UA_3262_I_004	Ensure that the IUT, when it bind Rack header in PRACK, it MUST contain two numbers, with first number mismatched, it should returns 481
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 7.1. / ACATS SIPv1.2
SIP_UA_3262_I_005	Ensure that the IUT, when it bind Rack header in PRACK, it MUST contain two numbers, with second number mismatched, it should returns 481
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 7.1. / ACATS SIPv1.2
SIP_UA_3262_I_006	Ensure that the IUT, when it bind Rack header in PRACK, it MUST contain two numbers, and method name “invite" (in lower case), it should returns 481
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 7.1. / ACATS SIPv1.2
SIP_UA_3262_I_007	Ensure that the IUT, when it receives non-100 provisional respond reliably, the RSeq header field value of 0, it should return 4XX
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 3. / ACATS SIPv1.2
SIP_UA_3262_I_007_NoResp	Ensure that the IUT, when it receives a reliable provisional responds with RSeq with value 0, it should ignore it and then recover with a good response
	Pre-Condition: User Action: Config: SUT: IUT responds Status: Mandatory Ref: RFC3262 section 7.1. / ACATS SIPv1.2
SIP_Extensions/ SIP_Session_Timer
SIP_Extensions/ SIP_Session_Timer/ SIP_UA_timer_HV
SIP_UA_timer_HV_001	Ensure that the IUT, ONLY binds Session-Expires header into INVITE or UPDATE request,
	Config: A SUT: User Agent Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 4. / ACATS SIPv1.2
SIP_UA_timer_HV_002	Ensure that the IUT, the minimum value set into Min-SE header field is 90s
	User Action: Make a call from the SUT to the TESTER Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 7.1. / ACATS SIPv1.2
SIP_UA_timer_HV_003	Ensure that the IUT, MAY send INVITE with Min-SE header in initial INVITE
	Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 7.1. / ACATS SIPv1.2
SIP_UA_timer_HV_004	Ensure that the IUT, the recommend value set into Session-Expires header is 1800 seconds
	User Action: Make a call from the SUT to the TESTER Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 7.1. / ACATS SIPv1.2
SIP_UA_timer_HV_005	Ensure that the IUT, when it MUST NOT set Session-Expires header value less than value in Min-SE header
	User Action: Make a call from the SUT to the TESTER Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 7.1. / ACATS SIPv1.2
SIP_UA_timer_HV_006	Ensure that the IUT, when it constructs Session-Expires header, it MUST have a value and optionally with refresher parameter of value uas or uac
	User Action: Make a call from the SUT to the TESTER Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt sections 4 and 6. / ACATS SIPv1.2
SIP_UA_timer_HV_007	Ensure that the IUT, when it constructs 422 respond to INVITE or UPDATE because Session-Expires too small, it MUST have Min-SE header field in 422 respond
	Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 5. / ACATS SIPv1.2
SIP_UA_timer_HV_008	Ensure that the IUT, when it constructs 422 respond to INVITE or UPDATE because Session-Expires too small, it MUST use context Session Interval Too Small
	Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 6. / ACATS SIPv1.2
SIP_UA_timer_HV_009	Ensure that the IUT, when it MUST NOT bind Min-SE in other respond rather than 422
	User Action: None Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 5. / ACATS SIPv1.2
SIP_UA_timer_HV_010	Ensure that the IUT, when it SHOULD have Support header field with value timer in the INVITE when it
	Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt sections 4 and 6. / ACATS SIPv1.2
SIP_UA_timer_HV_011	Ensure that the IUT, when it responds 407 to PRACK, it MUST have Proxy-Authenticate header field in 407
	Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt sections 4 and 6. / ACATS SIPv1.2
SIP_UA_timer_HV_012	Ensure that the IUT, when it responds PRACK, it MUST copy To header field into the PRACK method
	Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt sections 4 and 6. / ACATS SIPv1.2
SIP_UA_timer_HV_013	Ensure that the IUT, when it responds PRACK, it MUST copy Via header field into the PRACK method
	Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt sections 4 and 6. / ACATS SIPv1.2
SIP_UA_timer_HV_014	Ensure that the IUT, when it responds 420 to PARCK, it MUST have Unsupported header field in 420
	User Action: Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt sections 4 and 6. / ACATS SIPv1.2
SIP_UA_timer_HV_015	Ensure that the IUT, when it responds 401 to PARCK, it MUST have WWW-Authenticate header field in 401
	Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt sections 4 and 6. / ACATS SIPv1.2
SIP_Extensions/ SIP_Session_Timer/ SIP_UA_timer_V
SIP_UA_timer_V_001	Ensure that the IUT, when it sends INVITE request, it SHOULD include a Supported header field with option tag timer to indicate it support the session timer
	Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 3. / ACATS SIPv1.2
SIP_UA_timer_V_002	Ensure that the IUT SHOULD use Min-SE header field to establish the lower bound for the session refresh interval
	Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 3. / ACATS SIPv1.2
SIP_UA_timer_V_003	Ensure that the IUT, when it receives 422 response for the request due to the Session-Expires interval is too low, the respond contains a Min-SE header field to identify the minimum session interval is too short, it SHOULD try again including Min-SE header with the largest Min-SE header field it observed in all 422 response it received previously
	Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 3. / ACATS SIPv1.2
SIP_UA_timer_V_004	Ensure that the IUT, before the session expiration (which states in Session-Expires header field), if it is active refresher, it MUST generate a session refresh request, which is a re-INVITE or UPDATE request for the current dialog
	The IUT should have a small session expiration value or this test will take a very long time to execute. Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 3. / ACATS SIPv1.2
SIP_UA_timer_V_005	Ensure that the IUT, before the session expiration (which states in Session-Expires header field), if it is active refresher, it SHOULD send a BYE to terminate the session after time out for the respond of a re-INIVTE or UPDATE request
	The IUT should have a small session expiration value or this test will take a very long time to execute. User Action: Make a call from the SUT to the TESTER Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 3. / ACATS SIPv1.2
SIP_UA_timer_V_006	Ensure that the IUT, when it receives a refresh request, it SHOULD treat it same as the initial request but only will extend the session
	Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 3. / ACATS SIPv1.2
SIP_UA_timer_V_007	Ensure that the IUT, when it supports session timer, it MUST include a Supported header field in each request (except ACK) with option tag timer
	Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 3. / ACATS SIPv1.2
SIP_UA_timer_V_008	Ensure that the IUT, when it supports session timer, it MAY include a Min-SE header field in initial INVITE
	Config: SUT: Status: Recommend Ref: Draft-ietf-sip-session-timer-15.txt section 7.1. / ACATS SIPv1.2
SIP_UA_timer_V_009	Ensure that the IUT, when it MAY include Session-Expires header field and a Min-SE header field in the initial INVITE, but the value of Session-Expires MUST be greater than or equal to the value of Min-SE
	Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 7.1. / ACATS SIPv1.2
SIP_UA_timer_V_010	Ensure that the IUT, when it supports session timer, it receives INVITE with Min-SE header ONLY (No Session-Expires header field) it should treat it valid, i.e the session has minimum value but never time out
	IUT should be configured to support session timer and with a small timeout value. User Action: Make a call from the SUT to the TESTER Config: SUT: Status: Recommend Ref: Draft-ietf-sip-session-timer-15.txt section 7.1. / ACATS SIPv1.2
SIP_UA_timer_V_011	Ensure that the IUT, when it supports session timer, it receives INVITE with Session-Expires header ONLY (No Min-SE header field) it should treat it valid, i.e the session has minimum value of 90 seconds and maximum value states in Session-Expires header field
	IUT should be configured to support session timer and with a small timeout value. User Action: Make a call from the SUT to the TESTER Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 7.1. / ACATS SIPv1.2
SIP_UA_timer_V_012	Ensure that the IUT, when it receives 2XX Response with Require header field containing value timer, it MUST look for the session-Expires header and set the session timer correctly
	Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 7.2. / ACATS SIPv1.2
SIP_UA_timer_V_013	Ensure that the IUT, when it receives 2XX Response with NO Session-Expires header field, it does NOT need to send refresh request
	Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 7.2. / ACATS SIPv1.2
SIP_UA_timer_V_014	Ensure that the IUT, when it does need to do session refresh, it MUST compute the session expiration for that session, which is the time of reception of the last 2XX response to a session refresh plus the session interval for that session
	Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 7.2. / ACATS SIPv1.2
SIP_UA_timer_V_015	Ensure that the IUT, when it retrys the INVITE request after gets respond 422, it SHOULD create the new re-INVITE with same value of the Call-ID, To, and From of the previous request, but the CSeq SHOULD be one higher than the previous
	Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 7.3. / ACATS SIPv1.2
SIP_UA_timer_V_016	Ensure that the IUT, when it retrys the INVITE request after gets respond 422, it SHOULD create the new re-INVITE with same value of the Supported, Require and Proxy-Require (if any) of the previous request
	Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 7.4. / ACATS SIPv1.2
SIP_UA_timer_V_017	Ensure that the IUT, when it refreshs a session within a dialog, the Session-Expires header field SHOULD equal to the maximum of the Min-SE header field and the current session interval
	The IUT should be configured for a small timeout value or this test will take a long time. User Action: Make a call from the SUT to the TESTER Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 7.4. / ACATS SIPv1.2
SIP_UA_timer_V_018	Ensure that the IUT, when it does refresh, it SHOULD construct the re-INVITE or UPDATE request with refresher parameter set to the correct value based on the initial refresher negotiation
	Config: SUT: Status: Recommend Ref: Draft-ietf-sip-session-timer-15.txt section 7.4. / ACATS SIPv1.2
SIP_UA_timer_V_019	Ensure that the IUT, when it does refresh, it SHOULD use UPDATE request rather than re-INVITE if it is supported
	Config: SUT: Status: Recommend Ref: Draft-ietf-sip-session-timer-15.txt section 7.4. / ACATS SIPv1.2
SIP_UA_timer_V_020	Ensure that the IUT, when it receives INVITE does NOT have Min-SE header but with Session-Expires header, it SHOULD assume the Min-SE header value is 90 second by default
	Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 8.1. / ACATS SIPv1.2
SIP_UA_timer_V_021	Ensure that the IUT, when it receives INVITE does NOT have Min-SE header but with Session-Expires header with value less than 90 seconds, it SHOULD assume the Min-SE header value is 90 second by default and return 422 responds with Min-SE header set to appropriate value
	Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 9. / ACATS SIPv1.2
SIP_UA_timer_V_022	Ensure that the IUT, when it receives INVITE does have Min-SE header but with Session-Expires header with value less than the value of Min-SE, it SHOULD assume the Min-SE header value is 90 second by default and return 422 responds with Min-SE header set to appropriate value
	Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 9. / ACATS SIPv1.2
SIP_UA_timer_V_023	Ensure that the IUT, when it responds 2XX respond to the INVITE, it MAY reduce Session-Expires value but NOT less than the Min-SE value, and it MUST NOT increase the value of the Session-Expires header field
	Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 9. / ACATS SIPv1.2
SIP_UA_timer_V_024	Ensure that the IUT, when it does support session timer and wants to insist it is refresher when it sends INVITE request, it SHOULD put refresher parameter with value uac
	Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 9. / ACATS SIPv1.2
SIP_UA_timer_V_025	Ensure that the IUT, when it does support session timer and wants to insist it UAS refresher when it sends INVITE request, it SHOULD put refresher parameter with value uas
	Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 9. / ACATS SIPv1.2
SIP_UA_timer_V_026	Ensure that the IUT, when it does support session timer, it sends INVITE without refresher parameter and receives 2XX responds with refresher parameter set to uac, it SHOULD perform the refresh request
	Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 9. / ACATS SIPv1.2
SIP_UA_timer_V_027	Ensure that the IUT, when it does support session timer, it sends INVITE without refresher parameter and receives 2XX responds with refresher parameter set to uas, it SHOULD wait for the refresh request
	Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 9. / ACATS SIPv1.2
SIP_UA_timer_V_028	Ensure that the IUT, when it does support session timer, it receives INVITE without refresher parameter, if it insists to be refresher, it SHOULD send 2XX responds with refresher parameter set to uas and with Require header field with value timer
	Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 9. / ACATS SIPv1.2
SIP_UA_timer_V_029	Ensure that the IUT, when it does support session timer, it receives INVITE without refresher parameter, if it insists that UAC to be refresher, it SHOULD send 2XX responds with refresher parameter set to uac and with Require header field with value timer
	**NOTE: Implementation Postponed.** Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 9. / ACATS SIPv1.2
SIP_Extensions/ SIP_Session_Timer/ SIP_UA_timer_I
SIP_UA_timer_I_001	Ensure that the IUT, when it receives INVITE with Session-Expires header field with value of 80 and no Min-SE header, it should return 422
	Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 7.1. / ACATS SIPv1.2
SIP_UA_timer_I_002	Ensure that the IUT, when it receives INVITE with Session-Expires header field with value of 100 and Min-SE header field value of 120, it should return 422
	Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 7.1. / ACATS SIPv1.2
SIP_UA_timer_I_003	Ensure that the IUT, when it receives INVITE with Session-Expires header field but no Supported header field with option tag timer, it should return 400
	Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 7.1. / ACATS SIPv1.2
SIP_UA_timer_I_004	Ensure that the IUT, when it receives INVITE with Min-SE header field but no Supported header field with option tag timer, it should return 400
	Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 7.1. / ACATS SIPv1.2
SIP_UA_timer_I_005	Ensure that the IUT, when it is active refresher for the session, and it receives refresh request, it MAY reject it using 400
	Config: SUT: Status:Optional Ref: Draft-ietf-sip-session-timer-15.txt section 7.1. / ACATS SIPv1.2
SIP_UA_timer_I_006	Ensure that the IUT, when it receives 2XX Response with Require header field containing value timer but no Session-Expires header field, it should return 400
	Config: SUT: Status:Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 7.1. / ACATS SIPv1.2
SIP_UA_timer_I_007	Ensure that the IUT, when it gets the re-INVITE request after gets respond 422, with same value of the Call-ID, To, and From of the previous request, as well as CSeq, it HOULD return 4XX (481 or 400)
	Config: SUT: Status:Mandatory Ref: Draft-ietf-sip-session-timer-15.txt section 7.3. / ACATS SIPv1.2
SIP_Extensions/ Remote_Party_ID_Privacy_Test
SIP_Extensions/ Remote_Party_ID_Privacy_Test/ SIP_UA_RPID_HV
SIP_UA_RPID_HV_001	Ensure that the IUT, when it constructs Remote-Party-ID header, it MUST add
	the addr-spec in the <> in the header and optionally put display-name (which is a text string) into it as well. Config: A SUT: User Agent Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 6.1. / ACATS SIPv1.2
SIP_UA_RPID_HV_002	Ensure that the IUT, when it constructs Remote-Party-ID header, it MAY optionally add screen token with value either yes or no into the header
	User Action: Config: SUT: Status: Optional Ref: Draft-ietf-sip-privacy-04.txt section 6.1. / ACATS SIPv1.2
SIP_UA_RPID_HV_003	Ensure that the IUT, when it constructs Remote-Party-ID header, it MAY optionally add party token with value either
	calling or called into the header, however it MUST NOT be more than one party type in the same Remote-Party-ID header. User Action: Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 6.1. / ACATS SIPv1.2
SIP_UA_RPID_HV_004	Ensure that the IUT, when it constructs Remote-Party-ID header, it MAY optionally add id-type token
	with value either subscriber or user into the header. User Action: Config: SUT: Status: Optional Ref: Draft-ietf-sip-privacy-04.txt section 6.1. / ACATS SIPv1.2
SIP_UA_RPID_HV_005	Ensure that the IUT, when it constructs Remote-Party-ID header, it MAY optionally add privacy token with value full, name, uri, or quoted string
	User Action: Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 6.1. / ACATS SIPv1.2
SIP_Extensions/ Remote_Party_ID_Privacy_Test/ SIP_UA_RPID_V
SIP_UA_RPID_V_001	Ensure that the IUT, when it constructs INVITE, and UPDATE, request, it CAN includes a Calling
	subscriber Remote-Party-ID header to identify the originator of the call. User Action: Config: SUT: Status:Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 5. / ACATS SIPv1.2
SIP_UA_RPID_V_002	Ensure that the IUT, when it constructs INVITE and UPDATE request with Remote-Party-ID header for the calling subscriber,
	it MUST contain an addr-spec identifying the caller and MAY contain a *display-name* for the caller as well. User Action: Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 5. / ACATS SIPv1.2
SIP_UA_RPID_V_003	Ensure that the IUT, when it constructs INVITE and UPDATE request, with Remote-Party-ID header, it CAN put privacy
	token into the header and set to uri if it does NOT want the number being displayed. User Action: Config: SUT: Status:Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 5. / ACATS SIPv1.2
SIP_UA_RPID_V_004	Ensure that the IUT, when it constructs INVITE and UPDATE request, with Remote-Party-ID header, it CAN put privacy token
	into the header and set to name if it does NOT want the *display-name* being displayed. User Action: Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 5. / ACATS SIPv1.2
SIP_UA_RPID_V_005	Ensure that the IUT, when it constructs INVITE and UPDATE request, with Remote-Party-ID header, it CAN put privacy
	token into the header and set to full if it does NOT want both number and *display-name* being displayed. User Action: Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 5. / ACATS SIPv1.2
SIP_UA_RPID_V_006	Ensure that the IUT, when it constructs INVITE and UPDATE request, with Remote-Party-ID header, it CAN put privacy token
	into the header and set to off if it does want the both number and *display-name* being displayed. User Action: Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 5. / ACATS SIPv1.2
SIP_UA_RPID_V_007	Ensure that the IUT, when it receives INVITE and UPDATE request with Remote-Party-ID header of the originator,
	if it supports this extension, it SHOULD NOT provide the identity of originator to the user if privacy token is set to uri. User Action: Verify that the identity of the caller IS NOT displayed on the IUT after the call is answered. Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 5. / ACATS SIPv1.2
SIP_UA_RPID_V_008	Ensure that the IUT, when it receives INVITE and UPDATE request with Remote-Party-ID header of the originator,
	if it supports this extension, it SHOULD provide the identity and *display-name* of originator to the user if privacy token is set to off. User Action: Verify that the identity of the caller IS displayed on the IUT after the call is answered. Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 5. / ACATS SIPv1.2
SIP_UA_RPID_V_009	Ensure that the IUT, when it receives INVITE and UPDATE request with Remote-Party-ID header of the originator, if it supports
	this extension, it SHOULD NOT provide the *display-name* of originator to the user if privacy token is set to name. User Action: Verify that the identity of the caller IS NOT displayed on the IUT after the call is answered. Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 5. / ACATS SIPv1.2
SIP_UA_RPID_V_010	Ensure that the IUT, when it receives INVITE and UPDATE request with Remote-Party-ID header of the originator, if it supports
	this extension, it SHOULD NOT provide the identity and *display-name* of originator to the user if privacy token is NOT set to full. User Action: Verify that the identity of the caller IS NOT displayed on the IUT after the call is answered. Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 5. / ACATS SIPv1.2
SIP_UA_RPID_V_011	Ensure that the IUT, when it receives INVITE and UPDATE request with Remote-Party-ID header of the originator, if it supports
	this extension, it SHOULD include a called subscriber Remote-Party-ID identifying the called party in the first non-100 response with identity information set to *subscriber*. User Action: Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 5. / ACATS SIPv1.2
SIP_UA_RPID_V_012	Ensure that the IUT, when it receives INVITE and UPDATE request with Remote-Party-ID header of the
	originator, if it supports this extension, it SHOULD include a called subscriber Remote-Party-ID identifying the called party in the first non-100 response as well as the privacy token set to uri if it does NOT want the called party identity being displayed at this time. User Action: IUT should be configured for privacy level of uri. Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 5. / ACATS SIPv1.2
SIP_UA_RPID_V_013	Ensure that the IUT, when it receives INVITE and UPDATE request with Remote-Party-ID header of the originator,
	if it supports this extension, it SHOULD include a called subscriber Remote-Party-ID identifying the called party in the first non-100 response as well as the privacy token set to name if it does NOT want the called party *display-name* being displayed at this time. User Action: IUT should be configured for privacy level of name. Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 5. / ACATS SIPv1.2
SIP_UA_RPID_V_014	Ensure that the IUT, when it receives INVITE and UPDATE request with Remote-Party-ID header of the originator,
	if it supports this extension, it SHOULD include a called subscriber Remote-Party-ID identifying the called party in the first non-100 response as well as the privacy token set to full if it does NOT want the called party identity and *display-name* being displayed at this time. User Action: IUT should be configured for privacy level of full. Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 5. / ACATS SIPv1.2
SIP_UA_RPID_V_015	Ensure that the IUT, when it receives INVITE and UPDATE request with Remote-Party-ID header of the originator,
	if it supports this extension, it SHOULD include a called subscriber Remote-Party-ID identifying the called party in the first non-100 response as well as the privacy token set to off if it does want the called party identity and *display-name* being displayed at this time. User Action: IUT should be configured for privacy level of full. Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 5. / ACATS SIPv1.2
SIP_UA_RPID_V_016	Ensure that the IUT, when it receives INVITE and UPDATE request with Remote-Party-ID header of the originator,
	if it supports this extension, it SHOULD include a called subscriber Remote-Party-ID identifying the called party in the final response (2XX) as well as the privacy token set to uri if it does NOT want the connected party identity being displayed at this time. User Action: IUT should be configured for privacy level of uri. Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 5. / ACATS SIPv1.2
SIP_UA_RPID_V_017	Ensure that the IUT, when it receives INVITE and UPDATE request with Remote-Party-ID header of the originator,
	if it supports this extension, it SHOULD include a called subscriber Remote-Party-ID identifying the called party in the final response (2XX) as well as the privacy token set to name if it does NOT want the connected party *display-name* being displayed at this time. Pre-Condition: User Action: IUT should be configured for privacy level of name. Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 5. / ACATS SIPv1.2
SIP_UA_RPID_V_018	Ensure that the IUT, when it receives INVITE and UPDATE request with Remote-Party-ID header of the originator,
	if it supports this extension, it SHOULD include a called subscriber Remote-Party-ID identifying the called party in the final response (2XX) as well as the privacy token set to full if it does NOT want the connected party identity and *display-name* being displayed at this time. User Action: IUT should be configured for privacy level of full. Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 5. / ACATS SIPv1.2
SIP_UA_RPID_V_019	Ensure that the IUT, when it receives INVITE and UPDATE request with Remote-Party-ID header of the originator,
	if it supports this extension, it SHOULD include a called subscriber Remote-Party-ID identifying the called party in the final response (2XX) as well as the privacy token set to off if it does want the connected party identity and *display-name* being displayed User Action: IUT should be configured for privacy level of off. Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 5. / ACATS SIPv1.2
SIP_UA_RPID_V_020	Ensure that the IUT, when it receives final responds (2XX) with Remote-Party-ID header of the connected-to
	party with the privacy token, if it supports this extension, it SHOULD NOT send the connected-to party identity to the originator user privacy token is set to uri. User Action: User must verify that the identify of the called party is not displayed when the system answers the call. Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 5. / ACATS SIPv1.2
SIP_UA_RPID_V_021	Ensure that the IUT, when it receives final response (2XX) with Remote-Party-ID header of the connected-to party
	with the privacy token, if it supports this extension, it SHOULD NOT send the connected-to party *display-name* to the originator user privacy token is set to name. User Action: User must verify that the identify of the called party is not displayed when the system answers the call. Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 5. / ACATS SIPv1.2
SIP_UA_RPID_V_022	Ensure that the IUT, when it receives final responds (2XX) with Remote-Party-ID header of the connected-to party with
	the privacy token, if it supports this extension, it SHOULD NOT send the connected-to party identity and *display-name* to the originator user privacy token is set to full. User Action: User must verify that the identify of the called party is not displayed when the system answers the call. Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 5. / ACATS SIPv1.2
SIP_UA_RPID_V_023	Ensure that the IUT, when it receives non-100 provisional respond with Remote-Party-ID header of the called party with the privacy token, if it supports this extension, it SHOULD send the connected-to party identity and “display-name" to the originator user privacy token is set to off
	User Action: User must verify that the identify of the called party is displayed when the system answers the call. Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 5. / ACATS SIPv1.2
SIP_UA_RPID_V_024	Ensure that the IUT, ONLY should bind Remote-Party-ID header in INVITE and UPDATE methods but NOT others
	User Action: Answer call. Hang up call Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 6. / ACATS SIPv1.2
SIP_UA_RPID_V_025	Ensure that the IUT, ONLY should bind Remote-Party-ID header in to the responds of INVITE and UPDATE methods but NOT others
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 6.2. / ACATS SIPv1.2
SIP_Extensions/ Remote_Party_ID_Privacy_Test/ SIP_UA_RPID_I
SIP_UA_RPID_I_001	Ensure that the IUT, when it receives INVITE and UPDATE request with Remote-Party-ID header but without addr-spec, it should return 400
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 6.1. / ACATS SIPv1.2
SIP_UA_RPID_I_002	Ensure that the IUT, when it receives 200 final responds with Remote-Party-ID header with party token set to “connected", it should accept the respond and proceed correctly
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 6.1. / ACATS SIPv1.2
SIP_UA_RPID_I_003	Ensure that the IUT, when it receives INVITE and UPDATE Request with Remote-Party-ID header with party token set to connected (without double quote), it SHOULD return 400
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 6.1. / ACATS SIPv1.2
SIP_UA_RPID_I_004	Ensure that the IUT, when it receives INVITE and UPDATE request with Remote-Party-ID header with id-type token set to “supervisor", it should accept the respond and proceed correctly
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 6.1. / ACATS SIPv1.2
SIP_UA_RPID_I_005	Ensure that the IUT, when it receives INVITE and UPDATE request with Remote-Party-ID header with id-type token set to supervisor (without double quote), it should return 400
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 6.1. / ACATS SIPv1.2
SIP_UA_RPID_I_006	Ensure that the IUT, when it receives INVITE and UPDATE request with Remote-Party-ID header with privacy token set to “whatever", it should accept the respond and proceed correctly
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 6.1. / ACATS SIPv1.2
SIP_UA_RPID_I_007	Ensure that the IUT, when it receives INVITE and UPDATE request with Remote-Party-ID header with privacy token set to whatever, it should return 400
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-ietf-sip-privacy-04.txt section 6.1. / ACATS SIPv1.2
SIP_UA_RPID_I_008	Ensure that the IUT, when it receives INVITE and UPDATE request with Remote-Party-ID header with two id-type tokens set to subscriber and user respectively , it should reject the request with 400
	Pre-Condition: User Action: Config: SUT: Status: Optional Ref: Draft-ietf-sip-privacy-04.txt section 6.1. / ACATS SIPv1.2
SIP_Extensions/ Diversion_Header_Test
SIP_Extensions/ Diversion_Header_Test/ SIP_UA_DIV_HV
SIP_UA_DIV_HV_001	Ensure that the IUT, when it constructs Diversion header, it MUST add the
	name-addr to the Diversion header. Config: A SUT: User Agent Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_HV_002	Ensure that the IUT, when it constructs Diversion header, it MUST contain a diversion-reason with a reason value
	Config: A SUT: User Agent Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_HV_003	Ensure that the IUT, when it constructs Diversion header, it MUST add diversion-reason parameter with value unknown if the diversion reason is unknown (e.g. call is diverted from analog trunk)
	Config: A SUT: User Agent Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_HV_004	Ensure that the IUT, when it constructs Diversion header, it MUST add diversion-reason parameter with value user-busy if the diversion triggered because of user busy
	Config: A SUT: User Agent Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_HV_005	Ensure that the IUT, when it constructs Diversion header, it MUST add diversion-reason parameter with value unavailable if the diversion triggered because user is not presented
	Config: A SUT: User Agent Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_HV_006	Ensure that the IUT, when it constructs Diversion header, it MUST add diversion-reason parameter with value unconditional if the diversion is configured as call forward all
	Config: A SUT: User Agent Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_HV_007	Ensure that the IUT, when it constructs Diversion header, it MUST add diversion-reason parameter with value no-answer if the diversion is triggered by user not answer
	Config: A SUT: User Agent Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_HV_008	Ensure that the IUT, when it constructs Diversion header, it MUST add diversion-reason parameter with value time-of-day if the diversion is triggered because of time of the day
	Config: A SUT: User Agent Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_HV_009	Ensure that the IUT, when it constructs Diversion header, it MUST add diversion-reason parameter with value deflection if the diversion is triggered because of the deflection
	Config: A SUT: User Agent Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_HV_010	Ensure that the IUT, when it constructs Diversion header, it MUST add diversion-reason parameter with value do-not-disturb if the diversion configured as do not disturb
	Config: A SUT: User Agent Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_HV_011	Ensure that the IUT, when it constructs Diversion header, it MUST add diversion-reason parameter with value out-of-service if the is triggered because of out of service
	Config: A SUT: User Agent Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_HV_012	Ensure that the IUT, when it constructs Diversion header, it MUST add diversion-reason parameter with value away if the diversion is triggered by configured as away
	Config: A SUT: User Agent Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_HV_013	Ensure that the IUT, when it constructs Diversion header, it MUST add diversion-reason parameter with value follow-me if the diversion is triggered by configured as follow-me option
	Config: A SUT: User Agent Status: Optional Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_HV_014	Ensure that the IUT, when it constructs diversion-reason value that is NOT defined in the session 5, it MUST put the string into double quote
	Config: A SUT: User Agent Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_HV_015	Ensure that the IUT, when it constructs Diversion header, it MAY optionally add diversion-counter parameter “counter" with counter value within 2 digits
	User Action: Configure the SUT to forward all calls to another extension. This should force a 302/3XX response with a diversion header Config: A SUT: User Agent Status: Optional Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_HV_016	Ensure that the IUT, when it constructs Diversion header, it MAY optionally add diversion-privacy parameter “privacy" with value full if not allowed to display both Name and Number
	Config: A SUT: User Agent Status: Optional Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_HV_017	Ensure that the IUT, when it constructs Diversion header, it MAY optionally add diversion-privacy parameter “privacy" with value name if not allowed to display Name only
	Config: A SUT: User Agent Status: Optional Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_HV_018	Ensure that the IUT, when it constructs Diversion header, it MAY optionally add diversion-privacy parameter “privacy" with value uri if not allowed to display Number
	Config: A SUT: User Agent Status: Optional Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_HV_019	Ensure that the IUT, when it constructs Diversion header, it MAY optionally add diversion-privacy parameter “privacy" with value off if both Name and Number are allowed to be displayed
	Config: A SUT: User Agent Status: Optional Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_HV_020	Ensure that the IUT, when it constructs Diversion header, it MAY optionally add diversion-privacy parameter “privacy" with value of quoted string if the value is not defined in this draft
	Config: A SUT: User Agent Status: Optional Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_HV_021	Ensure that the IUT, when it constructs Diversion header, it MAY optionally add diversion-screen parameter “screen" with value yes if the number is screened by the network (e.g. in the case of interworking with PSTN network.)
	Config: A SUT: User Agent Status: Optional Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_HV_022	Ensure that the IUT, when it constructs Diversion header, it MAY optionally add diversion-screen parameter “screen" with value no if the number is NOT screened by the network (e.g. in the case of interworking with Q.sig network.)
	Config: A SUT: User Agent Status: Optional Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_HV_023	Ensure that the IUT, when it constructs Diversion header, it MAY optionally add diversion-screen parameter “screen" with value of quoted string if the value is not defined in this draft
	Config: A SUT: User Agent Status: Optional Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_HV_024	Ensure that the IUT, when it constructs Diversion header, it MAY optionally add diversion-screen parameter “limit" with value two digits value to state the forwarding hop limitation
	User Action: Configure the SUT to forward all calls to another extension. This should force a 302/3XX response with a diversion header Config: A SUT: User Agent Status: Optional Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_HV_025	Ensure that the IUT, when it constructs Diversion header, it MAY optionally add diversion-extension as quoted-string if not defined in session 5
	Config: A SUT: User Agent Status: Optional Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_HV_026	Ensure that the IUT, when it constructs Diversion header only in INVITE methods and 3XX respond but NOT other methods and responds
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_HV_027	Ensure that the IUT, when it receiving a 3XX message with 6 contact headers, it should use the most top list one and send new request downstream and put the rest in a correct order table and hunt down the list till it success
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_HV_028	Ensure that the IUT, when it receiving a 3XX message with 7 contact headers, it should use the most top list one and send new request downstream and put the rest in a correct order table and hunt down the list till it success
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_Extensions/ Diversion_Header_Test/ SIP_UA_DIV_V
SIP_UA_DIV_V_001	Ensure that the IUT, when receives respond 302 that has Diversion header with one URI with diversion-reason “user-busy", the diversion information should correctly reflect to the new request, for example a Q.sig call or a new INVITE
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 7. / ACATS SIPv1.2
SIP_UA_DIV_V_002	Ensure that the IUT, when receives respond 302 that has Diversion header with one URI with diversion-reason “unconditional", the diversion information should correctly reflect to the new request, for example a Q.sig call or a new INVITE
	User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 7. / ACATS SIPv1.2
SIP_UA_DIV_V_003	Ensure that the IUT, when receives respond 302 that has Diversion header with one URI with diversion-reason “no-answer", the diversion information should correctly reflect to the new request, for example a Q.sig call or a new INVITE
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 7. / ACATS SIPv1.2
SIP_UA_DIV_V_004	Ensure that the IUT, when receives respond 302 that has Diversion header with one URI with diversion-reason “unknown", the diversion information should correctly reflect to the new request, for example a Q.sig call or a new INVITE
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 7. / ACATS SIPv1.2
SIP_UA_DIV_V_005	Ensure that the IUT, when receives respond 302 that has Diversion header with one URI with diversion-reason “unavaliable", the diversion information should correctly reflect to the new request, for example a Q.sig call or a new INVITE
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 7. / ACATS SIPv1.2
SIP_UA_DIV_V_006	Ensure that the IUT, when receives respond 302 that has Diversion header with one URI with diversion-reason “time-of-day", the diversion information should correctly reflect to the new request, for example a Q.sig call or a new INVITE
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 7. / ACATS SIPv1.2
SIP_UA_DIV_V_007	Ensure that the IUT, when receives respond 302 that has Diversion header with one URI with diversion-reason “do-not-disturb", the diversion information should correctly reflect to the new request, for example a Q.sig call or a new INVITE
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 7. / ACATS SIPv1.2
SIP_UA_DIV_V_008	Ensure that the IUT, when receives respond 302 that has Diversion header with one URI with diversion-reason “out-of-service", the diversion information should correctly reflect to the new request, for example a Q.sig call or a new INVITE
	User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 7. / ACATS SIPv1.2
SIP_UA_DIV_V_009	Ensure that the IUT, when receives respond 302 that has Diversion header with one URIs with diversion-reason “away", the diversion information should correctly reflect to the new request, for example a Q.sig call or a new INVITE
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 7. / ACATS SIPv1.2
SIP_UA_DIV_V_010	Ensure that the IUT, when receives respond 302 that has Diversion header with one URIs with diversion-reason “follow-me", the diversion information should correctly reflect to the new request, for example a Q.sig call or new INVITE
	User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 7. / ACATS SIPv1.2
SIP_UA_DIV_V_011	Ensure that the IUT, when receives respond 302 that has Diversion header with one URIs with diversion-reason “deflection", the diversion information should correctly reflect to the new INVITE request, for example a Q.sig call or new INVITE
	User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 7. / ACATS SIPv1.2
SIP_UA_DIV_V_012	Ensure that the IUT, when receives respond 302 that has Diversion header with one URIs with diversion-reason “whatever", the diversion information should correctly reflect to the new request, for example a Q.sig call or new INVITE
	User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 7. / ACATS SIPv1.2
SIP_UA_DIV_V_013	Ensure that the IUT, when receives respond 302 that has three Diversion headers with URIs with diversion-reason “whatever", “away", “user-busy", the diversion information should correctly reflect to the new request, for example a Q.sig call or new INVITE
	User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 7. / ACATS SIPv1.2
SIP_UA_DIV_V_014	Ensure that the IUT, when receives respond 302 that has three Diversion headers with URIs with diversion-reasons, diversion-privacy with value full, the diversion information should correctly reflect to the new request, for example a Q.sig call or new INVITE
	User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 7. / ACATS SIPv1.2
SIP_UA_DIV_V_015	Ensure that the IUT, when receives respond 302 that has three Diversion headers with URIs with diversion-reasons, diversion-privacy with value name, the diversion information should correctly reflect to the new request, for example a Q.sig call or new INVITE
	User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 7. / ACATS SIPv1.2
SIP_UA_DIV_V_016	Ensure that the IUT, when receives respond 302 that has three Diversion headers with URIs with diversion-reasons, diversion-privacy with value uri, the diversion information should correctly reflect to the new request, for example a Q.sig call or new INVITE
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 7. / ACATS SIPv1.2
SIP_UA_DIV_V_017	Ensure that the IUT, when receives respond 302 that has three Diversion headers with URIs with diversion-reasons, diversion-privacy with value off, the diversion information should correctly reflect to the new request, for example a Q.sig call or new INVITE
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 7. / ACATS SIPv1.2
SIP_UA_DIV_V_018	Ensure that the IUT, when receives respond 302 that has three Diversion headers with URIs with diversion-reasons, diversion-counter set to 3, the diversion information should correctly reflect to the new request, for example a Q.sig call or new INVITE
	User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 7. / ACATS SIPv1.2
SIP_UA_DIV_V_019	Ensure that the IUT, when receives respond 302 that has three Diversion headers with URIs with diversion-reasons, diversion-limit and diversion-extension with values, the diversion information should correctly reflect to the new request, for example a Q.sig call or new INVITE
	User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 7. / ACATS SIPv1.2
SIP_UA_DIV_V_020	Ensure that the IUT, SHOULD NOT add Diversion header for normal call routing to the Request-URI
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 4.1. / ACATS SIPv1.2
SIP_UA_DIV_V_021	Ensure that the IUT, when it triggers the diversion, Diversion header field with the previous Request-URI SHOULD be added to the forwarded 3XX respond
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt sections 4.1 and 6.1. / ACATS SIPv1.2
SIP_UA_DIV_V_022	Ensure that the IUT, when it triggers the diversion, Diversion header field with the previous Request-URI SHOULD be added to the forwarded request (e.g. nested Diversion)
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt sections 4.1 and 6.1. / ACATS SIPv1.2
SIP_UA_DIV_V_023	Ensure that the IUT, when it triggers the diversion, diversion-reason with reason value SHOULD be added to the forwarded 3XX respond
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt sections 4.1 and 6.1. / ACATS SIPv1.2
SIP_UA_DIV_V_024	Ensure that the IUT, after it receives a Request with Diversion headers, it MUST NOT be removed or changed in the forwarded response
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 4.1. / ACATS SIPv1.2
SIP_UA_DIV_V_025	Ensure that the IUT, when it receives a 3XX containing Diversion headers, it SHOULD copy the Diversion header into the downstream request
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 6.2. / ACATS SIPv1.2
SIP_UA_DIV_V_027	Ensure that the IUT, when it need to trigger the diversion beyond receiving a 3XX containing a Diversion header, and it SHOULD copy the Diversion header into the downstream request and add the most recent Diversion header on the top of the Diversion header list
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 6.2. / ACATS SIPv1.2
SIP_UA_DIV_V_028	Ensure that the IUT, when it receives INVITE with multiple Diversion headers, it SHOULD treat the most top Diversion header as the last diversion occurred and the most last Diversion header as the first diversion
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 6.2. / ACATS SIPv1.2
SIP_RD_DIV_V_001	Ensure that the IUT, when it receives a request as redirect server, it SHOULD return a 3XX containing a Contact with the diverts the request to, and Diversion header and diversion reason
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 6.3. / ACATS SIPv1.2
SIP_Extensions/ Diversion_Header_Test/ SIP_PS_DIV_V
SIP_PS_DIV_V_001	Ensure that the IUT, when it is a non-recursing SIP proxy, it SHOULD forward the 3XX containing the Diversion header upstream unchanged
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 6.4. / ACATS SIPv1.2
SIP_PS_DIV_V_002	Ensure that the IUT, when it is a recursing SIP proxy, if it receives a request it SHOULD return a 3XX contain a Contact which diverts the request to a different endpoint and add a Diversion header containing the Request-URI from the incoming request and the reason for the diversion
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 6.4. / ACATS SIPv1.2
SIP_PS_DIV_V_003	Ensure that the IUT, when it is a recursing SIP proxy, if it receives a request it SHOULD forwarded request in order to divert the request to a different endpoint and add a Diversion header containing the Request-URI from the incoming request and the reason for the diversion
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 6.4. / ACATS SIPv1.2
SIP_Extensions/ Diversion_Header_Test/ SIP_UA_DIV_I
SIP_UA_DIV_I_001	Ensure that the IUT, when it receives 3XX responds with Diversion header and with diversion-reason set to whatever (without quote), it should return 400
	Pre-Condition: User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_I_002	Ensure that the IUT, when it receives 3XX responds with Diversion header and with diversion-counter set to 100, it should return 400
	User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_I_003	Ensure that the IUT, when it receives 3XX responds with Diversion header and with diversion-limit set to 100, it should return 400
	User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_I_004	Ensure that the IUT, when it receives 3XX responds with Diversion header and with diversion-privacy set to whatever (without quote), it should return 400
	User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_I_005	Ensure that the IUT, when it receives 3XX responds with Diversion header and with diversion-screen set to whatever (without quote), it should return 400
	User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_I_006	Ensure that the IUT, when it receives 3XX responds with Diversion header and with diversion-extension set to whatever (without quote), it should return 400
	User Action: Config: SUT: Status: Mandatory Ref: Draft-levy-sip-diversion-08.txt section 5. / ACATS SIPv1.2
SIP_UA_DIV_I_007	Ensure that the IUT, when it receives 3XX responds with Diversion header and with diversion-reason set to “diversion-reason: whatever" it should proceed correctly
	User Action: Config: SUT: Status:Mandatory Ref: 5
SIP_UA_DIV_I_008	Ensure that the IUT, when it receives 3XX responds with Diversion header and with diversion-reason set to “NO-ANSWER", it should still proceed correctly
	User Action: Config: SUT: Status:Mandatory Ref: 5
SIP_UA_DIV_I_009	Ensure that the IUT, when it receives 3XX responds with Diversion header and with diversion-reason without any value, it should return 4XX
	User Action: Config: SUT: Status:Mandatory Ref: 5
SIP_UA_DIV_I_010	Ensure that the IUT, when it receives 3XX responds with Diversion header and with diversion-reason set to “no%answer", it should return 4XX
	User Action: Config: SUT: Status:Mandatory Ref: 5
SIP_UA_DIV_I_011	Ensure that the IUT, when it receives 3XX responds with Diversion header and with diversion-reason set to “no answer", it should still return 4XX
	User Action: Config: SUT: Status:Mandatory Ref: 5
SIP_Extensions/ Redirection_Status_Code_Test
SIP_Extensions/ Redirection_Status_Code_Test/ SIP_UA_3XX_HV
SIP_UA_3XX_HV_001_DF2a	Ensure that the IUT, when receives respond 302 that has Diversion header with one URI with reason user-busy, the diversion information should correctly reflect to the new request, for example a Q.sig call
	User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_3XX_HV_002_DF2a	Ensure that the IUT, when receives respond 302 that has Diversion header with one URI with reason unconditional, the diversion information should correctly reflect to the new request, for example a Q.sig call
	User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_3XX_HV_003_DF2a	Ensure that the IUT, when receives respond 302 that has Diversion header with one URI with reason no-answer, the diversion information should correctly reflect to the new request, for example a Q.sig call
	User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_3XX_HV_004_DF2a	Ensure that the IUT, when receives respond 302 that has Diversion header with one URI with reason unknown, the diversion information should correctly reflect to the new request, for example a Q.sig call
	User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_3XX_HV_005_DF2a	Ensure that the IUT, when receives respond 302 that has Diversion header with one URI with reason user-busy, the diversion information should correctly reflect to the new INVITE request
	User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_3XX_HV_006_DF2a	Ensure that the IUT, when receives respond 302 that has Diversion header with one URI with reason unconditional, the diversion information should correctly reflect to the new INVITE request
	User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_3XX_HV_007_DF2a	Ensure that the IUT, when receives respond 302 that has Diversion header with one URI with reason no-answer, the diversion information should correctly reflect to the new INVITE request
	User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_3XX_HV_008_DF2a	Ensure that the IUT, when receives respond 302 that has Diversion header with one URI with reason unknown, the diversion information should correctly reflect to the new INVITE request
	User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_3XX_HV_009_DF2a	Ensure that the IUT, when receives respond 302 that has Diversion header with two URIs with reason “unconditional" and "user-busy", the diversion information should correctly reflect to the new INVITE request
	Pre-Condition: User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_3XX_HV_009a_DF2a	Ensure that the IUT, when receives respond 302 that has Diversion header with two URIs with reason “no-answer" and "unknown", the diversion information should correctly reflect to the new INVITE request
	Pre-Condition: User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_3XX_HV_010_DF2a	Ensure that the IUT, when receives respond 302 that has Diversion header with two URIs with reason “unconditional" and "user-busy", the diversion information should correctly reflect to the new request, for example a Q.sig Call
	Pre-Condition: User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_3XX_HV_010a_DF2a	Ensure that the IUT, when receives respond 302 that has Diversion header with two URIs with reason “no-answer" and "unknown", the diversion information should correctly reflect to the new request, for example a Q.sig Call
	Pre-Condition: User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_3XX_HV_011_DF2a	Ensure that the IUT, when receives respond 302 that has Diversion header with three URIs with reason “unconditional", "user-busy", "no-answer", the diversion information should correctly reflect to the new INVITE request
	User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_3XX_HV_012_DF2a	Ensure that the IUT, when receives respond 302 that has Diversion header with three URIs with reason “unconditional", "user-busy", "no-answer", the diversion information should correctly reflect to the new request, e.g. a Q.sig Call
	User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_3XX_HV_001	Ensure that the IUT, when receives respond 302 that has Diversion header with one URI with reason user-busy, the diversion information should correctly reflect to the new request, for example a Q.sig call
	User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_3XX_HV_002	Ensure that the IUT, when receives respond 302 that has Diversion header with one URI with reason unconditional, the diversion information should correctly reflect to the new request, for example a Q.sig call
	User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_3XX_HV_003	Ensure that the IUT, when receives respond 302 that has Diversion header with one URI with reason “no-answer", the diversion information should correctly reflect to the new request, for example a Q.sig call
	User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_3XX_HV_004	Ensure that the IUT, when receives respond 302 that has Diversion header with one URI with reason “unknown", the diversion information should correctly reflect to the new request, for example a Q.sig call
	User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_3XX_HV_005	Ensure that the IUT, when receives respond 302 that has Diversion header with one URI with reason “user-busy", the diversion information should correctly reflect to the new INVITE request
	User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_3XX_HV_006	Ensure that the IUT, when receives respond 302 that has Diversion header with one URI with reason “unconditional", the diversion information should correctly reflect to the new INVITE request
	User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_3XX_HV_007	Ensure that the IUT, when receives respond 302 that has Diversion header with one URI with reason “no-answer", the diversion information should correctly reflect to the new INVITE request
	User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_3XX_HV_008	Ensure that the IUT, when receives respond 302 that has Diversion header with one URI with reason “unknown", the diversion information should correctly reflect to the new INVITE request
	User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_3XX_HV_009	Ensure that the IUT, when receives respond 302 that has Diversion header with two URIs with reason “unconditional", the diversion information should correctly reflect to the new INVITE request
	Pre-Condition: User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_3XX_HV_010	Ensure that the IUT, when receives respond 302 that has Diversion header with two URIs with reason “unknown", the diversion information should correctly reflect to the new request, for example a Q.sig call
	User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_3XX_HV_011	Ensure that the IUT, when receives respond 302 that has Diversion header with three URIs with reason “unconditional", the diversion information should correctly reflect to the new INVITE request
	User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_3XX_HV_012	Ensure that the IUT, when receives respond 302 that has Diversion header with three URIs with reason “unknown", the diversion information should correctly reflect to the new request, for example a Q.sig call
	User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_Extensions/ Redirection_Status_Code_Test/ SIP_RD_3XX_HV
SIP_RD_3XX_HV_001	Ensure that the IUT, should treat “expires" parameter of a Contact header field value and Expires header field are same when receives either one in the respond of 302
	Pre-Condition: User Action: Config: SUT: Status:Mandatory Ref: 8.3
SIP_Extensions/ Redirection_Status_Code_Test/ SIP_UA_300_V
SIP_UA_300_V_001_DF2a	Ensure that the IUT, when receive a redirection respond 300, it should use the URI(s) in the Contact header field to formulate one or more new requests. The Request-URI of the new request uses the value of the Contact header field in the respond
	Pre-Condition: User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_300_V_002_DF2a	Ensure that the IUT, when processing 300 responses MUST NOT add any given URI to the target set more than once
	User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_300_V_004_DF2a	Ensure that the IUT, when receive a redirection respond 300 with multiple contacts with q value in the Contact header
	, it can use the prefer contact and redirect its request to that location. Pre-Condition: User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_300_V_005_DF2a	Ensure that the IUT, when receive a redirection respond 300, it should try the next perfer contact address UA prefers, if a failure for a paticular contact address. A new client transaction should be created
	Pre-Condition: User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_300_V_006_DF2a	Ensure that the IUT, when receive a redirection respond 300, it should try the next prefer contact address in the list in afailure, until the list is exhausted
	if the list is exhausted, then the request has failed. Pre-Condition: User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_300_V_007_DF2a	Ensure that the IUT, when receive a redirection respond 300, it should consider as a failure for a particular contact address if failure code returns (codes gretater than 399)
	Pre-Condition: User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_300_V_008_DF2a	Ensure that the IUT, when receive a redirection respond 300, in order to create a request based on 300 UAC MUST copy the entire URI from the target set into the Request-URI, except
	for the "method-param" and "header" URI parameters. Pre-Condition: User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_300_V_009_DF2a	Ensure that the IUT, when receive a redirection respond 300, if the header field can accept a comma-separated list of values, then the new header field value MAY be appended to any existing values in the original redirected request. If the header field does not accept multiple value, the value in the original redirected request MAY be overwritten by the header field value communicated in the contact address
	Pre-Condition: User Action: Config: SUT: Status:Mandatory Ref: 8.1.3.4
SIP_UA_300_V_010_DF2a	Ensure that the IUT, when receive a redirection respond 300, it is RECOMMENNDED that the UAC reused the same To, From, and Call-ID used in the original redirected request, but the UAC MAY also choose to updated the Call-ID header field value of new requests
	Pre-Condition: User Action: Config: SUT: Status:Recommend Ref: 8.1.3.4
SIP_UA_300_V_011_DF2a	Ensure that the IUT, when receive a redirection respond 300, once the new request has been constructed, it is sent using a new client transaction, and therefore MUST have a new branch ID in the top Via field
	User Action: Config: SUT: Status:Mandatory Ref: 8.1.3.4
SIP_UA_300_V_012_DF2a	Ensure that the IUT, when receive a redirection respond 300, it should re-use the header fields (except method) and bodies of the original request to construct
	the new request. Pre-Condition: User Action: Config: SUT: Status:Recommend Ref: 8.1.3.4
SIP_UA_300_V_013_DF2a	Ensure that the IUT, when receive a redirection respond 300, UAs respond may contain several Contact fields or a list of addresses in a Contact field in the new request
	User Action: Config: SUT: Status:Recommend Ref: 8.1.3.4, 21.3.1
SIP_UA_300_V_001	Ensure that the IUT, when receive a redirection respond 300, it should use the URI(s) in the Contact header field to formulate one or more new requests. The Request-URI of the new request uses the value of the Contact header field in the respond
	Pre-Condition: User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_300_V_002	Ensure that the IUT, when processing 300 responses MUST NOT add any given URI to the target set more than once
	User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_300_V_003	Ensure that the IUT, when processing 300 responses MUST NOT add any given URI to the target set more than once
	Pre-Condition: User Action: Config: SUT: Status:Recommend Ref: 8.1.3.4
SIP_UA_300_V_004	Ensure that the IUT, when receive 300 with multiple contacts with q value in Contact header, UA can use the prefer contact and redirect its request to that location
	Pre-Condition: User Action: Config: SUT: Status:Mandatory Ref: 8.1.3.4
SIP_UA_300_V_005	Ensure that the IUT, when receive a redirection respond 300, it should try the next prefer contact address UA prefers if a failure for a particular contact address. A new client transaction should be created to deliver a new request
	Pre-Condition: User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.1.3.4
SIP_UA_300_V_006	Ensure that the IUT, when receive a redirection respond 300, it should try the next prefer contact address in the list in a failure, until the list is exhausted. If the list is exhausted, then the request has failed
	User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.1.3.4
SIP_UA_300_V_007	Ensure that the IUT, when receive a redirection respond 300, it should consider as a failure for a particular contact address if failure code returns (codes greater than 399)
	User Action: Config: SUT: Status:Mandatory Ref: 8.1.3.4
SIP_UA_300_V_008	Ensure that the IUT, when receive a redirection respond 300, in order to create a request based on 300, UAC MUST copy the entire URI from the target set into the Request-URI, except for the “method-param" and “header" URI parameters
	Pre-Condition: User Action: Config: SUT: Status:Mandatory Ref: 8.1.3.4
SIP_UA_300_V_009	Ensure that the IUT, when receive a redirection respond 300, if the header field can accept a comma-separated list of values, then the new header field value MAY be appended to any existing values in the original redirected request. If the header field does not accept multiple value, the value in the original redirected request MAY be overwritten by the header field value communicated in the contact address
	**NOTE: Implementation Postponed.** Pre-Condition: User Action: Config: SUT: Status:Mandatory Ref: 8.1.3.4
SIP_UA_300_V_010	Ensure that the IUT, when receive a redirection respond 300, it is RECOMMENNDED that the UAC reused the same To, From, and Call-ID used in the original redirected request, but the UAC MAY also choose to updated the Call-ID header field value of new requests
	Pre-Condition: User Action: Config: SUT: Status:Mandatory Ref: 8.1.3.4
SIP_UA_300_V_011	Ensure that the IUT, when receive a redirection respond 300, once the new request has been constructed, it is sent using a new client transaction, and therefore MUST have a new branch ID in the top Via field
	User Action: Config: SUT: Status:Mandatory Ref: 8.1.3.4
SIP_UA_300_V_012	Ensure that the IUT, when receive a redirection respond 300, it should re-use the header fields (except method) and bodies of the original request to construct the new request
	User Action: Config: SUT: Status:Mandatory Ref: 8.1.3.4
SIP_UA_300_V_013	Ensure that the IUT, when receive a redirection respond 300, UAs respond may contain several Contact fields or a list of addresses in a Contact field in the new request
	User Action: Config: SUT: Status:Recommend Ref: 8.1.3.4, 21.3.1
SIP_Extensions/ Redirection_Status_Code_Test/ SIP_UA_301_V
SIP_UA_301_V_001_DF2a	Ensure that the IUT, when receive a redirection respond 300, it should use the URI(s) in the Contact header field to formulate one or more new requests. The Request-URI of the new request uses the value of the Contact header field in the respond
	Pre-Condition: User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_301_V_002_DF2a	Ensure that the IUT, when processing 301 responses MUST NOT add any given URI to the target set more than once
	User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_301_V_004_DF2a	Ensure that the IUT, when receive a redirection respond 301 with multiple contacts with q value in the Contact header
	, it can use the prefer contact and redirect its request to that location. Pre-Condition: User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_301_V_005_DF2a	Ensure that the IUT, when receive a redirection respond 301, it should try the next perfer contact address UA prefers, if a failure for a paticular contact address. A new client transaction should be created
	Pre-Condition: User Action: User must make a call to the tester. Config: SUT: Status:Mandatory Ref: 8.3
SIP_UA_301_V_006_DF2a	Ensure that the IUT, when receive a redirection respond 301, it should try the next prefer contact address in the list in afailure, until the list is exhausted