Valid8.com VoIP SIP P25 ISSI Conformance Test Suite, for use with SIP ISSI Signaling Tester
TEST SUITE OVERVIEW
References
Archive/Projectvoip/sip_issi_ts
Version19171599
Date25 May 2010
Number of Scenarios214
Number of Groups32
Average per Group6
GROUP/SCENARIOTEST PURPOSE
RFSSRFSS ISSI Tests
RFSS/
HOME		Tests that test a HOME RFSS
RFSS/
HOME/
Individual_SU_Registration_Procs		These tests demonstrate that a mobility object (SU) can be registered in a
SIP_ISSI_Home_4_1_001SU Registration - Successful (SU presence confirmed) - Home
procedure. The SU is subsequently registered with its Home RFSS via a Serving RFSS.
Applicable ISSI Conformance Test RFSS Roles: Serving, Home (to Serving),Home (Multi-Segment)
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
u-id of the SU : 000011
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_4_2_001SU Registration - Successful (SU presence not confirmed) - Home
initiates the ISSI SU registration procedure for that SU with the presence of the
SU not confirmed. Upon completion of the test, the Serving RFSS is still
registered with the Home RFSS for the specified SU.
Home (Multi-Segment)
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
u-id of the SU : 000011
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_4_3_001SU Registration - Unsuccessful (Target RFSS is not home to the SU, SU presence confirmed) - Home
procedure. The request of the Serving RFSS is sent to a Home RFSS that is not
home to the specified SU.
confirmed.
Home (Multi-Segment)
for the specified SU.
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
u-id of the SU : 000011
for the specified SU.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_4_3_002SU Registration - Unsuccessful (Target RFSS is not home to the SU, SU presence not confirmed) - Home
procedure. The request of the Serving RFSS is sent to a Home RFSS that is not
home to the specified SU.
confirmed.
NOTE – the field “r-presence” is absent or set to "not confirmed".
Home (Multi-Segment)
for the specified SU.
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
u-id of the SU : 000011
for the specified SU.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_4_4_001SU Registration – Unsuccessful (Denied by Home RFSS, SU presence confirmed)-Home
for the SU. The request of the Serving RFSS is sent to the Home RFSS which
denies registration of the SU due to local policy.
confirmed.
Home (Multi-Segment)
for the specified SU.
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
u-id of the SU : 000011
for the specified SU.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_4_4_002SU Registration – Unsuccessful (Denied by Home RFSS, SU presence not confirmed)-Home
for the SU. The request of the Serving RFSS is sent to the Home RFSS which
denies registration of the SU due to local policy.
confirmed.
Home (Multi-Segment)
for the specified SU.
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
u-id of the SU : 000011
for the specified SU.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_4_5_001SU Registration – Unsuccessful (SU presence confirmation not required)-Home
not confirmed for the SU. The request of the Serving RFSS is sent to the Home
RFSS which rejects it because the Home RFSS believes the SU is currently
registered to a different RFSS than the registering RFSS.
Home (Multi-Segment)
specified SU.
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
u-id of the SU : 000011
for the specified SU.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
RFSS/
HOME/
Group_Registration_Procs		These tests demonstrate that a mobility object (SG) can be registered in a
SIP_ISSI_Home_5_1_001SG Registration – Successful - Home
to the SG’s Home RFSS.
Home (Multi-Segment)
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
g-id of the group : 0064
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_5_2_001SG Registration – Unsuccessful (Target RFSS not Home to the SG)- Home
registration message (RFSS 2) is not configured to be the home of the SG.
RFSS 2 responds to RFSS 1 with the appropriate failure response.
Home (Multi-Segment)
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
g-id of the group : 0064
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_5_3_001SG Registration – Unsuccessful (Denied by Home RFSS)- Home
to the SG s Home RFSS. The SGs Home RFSS disallows the SG registration
with the appropriate error message.
Home (Multi-Segment)
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
g-id of the group : 0064
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
RFSS/
HOME/
Individual_SU_De_Registration_Procs		These tests demonstrate that a mobility object (SU) can be de-registered in a
SIP_ISSI_Home_6_1_001SU De-registration – Successful (Serving RFSS initiated)- Home
RFSS.
Home (Multi-Segment)
Home RFSS.
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
u-id of the SU : 000011
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_6_2_001SU De-registration – Successful (Home RFSS initiated)- Home
Home (Multi-Segment)
RFSS.
Home rfss-id : 01
Home system-id : 001
Home wacn-id : 00001
Serving rfss-id : 02
Serving system-id : 002
Serving wacn-id : 00002
u-id of the SU : 000011
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_6_3_001SU De-registration – (Serving RFSS not allowed)- Home
sent to the Home RFSS of the SU. However, the Home RFSS of the SU no
longer considers the SU as being registered with the Serving RFSS and
responds with the appropriate error message.
Home (Multi-Segment)
specified SU.
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
u-id of the SU : 000011
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
RFSS/
HOME/
Group_De_registration_Procs		These tests demonstrate that a mobility object (SG) can be de-registered in a
SIP_ISSI_Home_7_1_001SG De-registration – Successful (Serving RFSS initiated)- Home
SG’s Home RFSS.
Home (Multi-Segment)
specified SG.
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
g-id of the group : 0064
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_7_2_001SG De-registration – (Serving RFSS not allowed)- Home
RFSS. The SG’s Home RFSS does not consider the SG to be registered in the
Serving RFSS and responds with the appropriate error message.
Home (Multi-Segment)
specified SG.
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
g-id of the group : 0064
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
RFSS/
HOME/
SU_Individual_Roamed_Procs		To demonstrate that a mobility object (SU) in a Serving RFSS can roam to
SIP_ISSI_Home_8_1_001SU Roamed procedure - Successful (Home initiated)- Home
RFSS triggers the roamed procedure from the Home RFSS to the Serving RFSS.
Home (Multi-Segment)
Home rfss-id : 01
Home system-id : 001
Home wacn-id : 00001
Serving rfss-id : 02
Serving system-id : 002
Serving wacn-id : 00002
u-id of the SU : 000011
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_8_2_001SU Roamed Procedure – (Serving RFSS Not Registered for SU)- Home
Serving RFSS believes it no longer has the SU registered in its serving domain.
After a triggering event, the Home RFSS initiates a roamed procedure for the SU.
The request from the Home RFSS is sent to the initial Serving RFSS which has
no reference to the SU in its serving domain.
Home (Multi-Segment)
Home rfss-id : 01
Home system-id : 001
Home wacn-id : 00001
Serving rfss-id : 02
Serving system-id : 002
Serving wacn-id : 00002
u-id of the SU : 000011
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
RFSS/
HOME/
Call_Setup_Unconfirmed_Group_Call		An RFSS can set up an unconfirmed group call for a specified SG.
SIP_ISSI_Home_9_1_001Group call setup – Successful- Home
Serving RFSSs triggers it to initiate an unconfirmed group call.
Home (Multi-Segment)
Serving RFSS 1 rfss-id : 01
Serving RFSS 1 system-id : 001
Serving RFSS 1 wacn-id : 00001
Home RFSS 2 rfss-id : 02
Home RFSS 2 system-id : 002
Home RFSS 2 wacn-id : 00002
Serving RFSS 3 rfss-id : 03
Serving RFSS 3 system-id : 003
Serving RFSS 3 wacn-id : 00003
g-id of the group : 0064
specified SG. 2- The Serving RFSS has an “Unconfirmed Group Call” RTP call segment
established with the Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_9_2_001Group call setup – Unsuccessful (Forbidden by the Home RFSS, SG
not registered)- Home.
Upon its local policy, the SG’s Home RFSS considers that the SG’s Serving
RFSS is no longer registered for the SG. The Serving RFSS initiates an
unconfirmed group call request to the SG’s Home RFSS. The Home RFSS
responds to the request with an appropriate error message.
Home (Multi-Segment)
specified SG.
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
g-id of the group : 0064
the specified SG.
2- The Serving RFSS does NOT have an RTP call segment established with
the Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_9_3_001Group call setup – Unsuccessful (SG not known to the Home RFSS)- Home
NOT home to the SG. The Serving RFSS initiates an unconfirmed group call
request to the non-Home RFSS. The non-Home RFSS responds with an
appropriate error message.
Home (Multi-Segment)
specified SG.
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
g-id of the group : 0064
the specified SG. 2- The Serving RFSS does NOT have an RTP call segment established with
this Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_9_4_001Group call setup – Unsuccessful (SG not known to Serving RFSS)- Home
invites one of the SG’s Serving RFSSs to join the group call but the SG is no
longer known in that Serving RFSS.
Home (Multi-Segment)
Home rfss-id : 01
Home system-id : 001
Home wacn-id : 00001
Serving rfss-id : 02
Serving system-id : 002
Serving wacn-id : 00002
g-id of the group : 0064
the specified SG.
2- The Serving RFSS does NOT have an RTP call segment established with
the Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_9_5_001Group Call setup - Successful (Two RFSS with call request having
equal priority)- Home.
and the Home RFSS initiate an unconfirmed group call for the same SG with
equal priorities.
Home (Multi-Segment)
Serving RFSS 1 rfss-id : 01
Serving RFSS 1 system-id : 001
Serving RFSS 1 wacn-id : 00001
Home RFSS 2 rfss-id : 02
Home RFSS 2 system-id : 002
Home RFSS 2 wacn-id : 00002
Serving RFSS 3 rfss-id : 03
Serving RFSS 3 system-id : 003
Serving RFSS 3 wacn-id : 00003
g-id of the group : 0064
priority of the call request initiated by the RFSS 1, RFSS 2, RFSS 3 : 8;a
specified SG.
2- The Serving RFSS has established a group call segment with the Home
RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_9_6_001Group Call setup – Successful (Two RFSS with call request having
different priority)- Home.
time the SG’s Serving RFSS and the SG’s Home RFSS initiate an unconfirmed
group call for the SG. The SU in the Home RFSS’s call request has a lower
priority than the Serving RFSS’s call request.
Home (Multi-Segment)
Serving RFSS 1 rfss-id : 01
Serving RFSS 1 system-id : 001
Serving RFSS 1 wacn-id : 00001
Home RFSS 2 rfss-id : 02
Home RFSS 2 system-id : 002
Home RFSS 2 wacn-id : 00002
Serving RFSS 3 rfss-id : 03
Serving RFSS 3 system-id : 003
Serving RFSS 3 wacn-id : 00003
g-id of the group : 0064
priority of the call request initiated by Serving RFSS 1 and Home RFSS 2: 8;a
priority of the call request initiated by Serving RFSS 3: 10;a
specified SG.
2- The Serving RFSS has established a group call segment with the Home
RFSS for the higher priority call request.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_9_7_001Group Call setup – Unsuccessful (Canceled by Home RFSS)- Home
RFSS initiates and then cancels an unconfirmed group call.
Home (Multi-Segment).
essentially equivalent can be provided via the BYE message. Accordingly, a
Home RFSS which does not support the CANCEL functionality in this test may
still be claimed as conformant to this PCP. This test is deemed “Not Applicable”
to such a Home RFSS.
such a case, this test becomes not applicable.
Home rfss-id : 01
Home system-id : 001
Home wacn-id : 00001
Serving rfss-id : 02
Serving system-id : 002
Serving wacn-id : 00002
g-id of the group : 0064
specified SG.
2- The Serving RFSS does NOT have an unconfirmed group call segment
established with the Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_9_8_001Group call setup – Unsuccessful (Canceled by Serving RFSS)- Home
RFSS initiates and then cancels an unconfirmed group call.
Home (Multi-Segment)
essentially equivalent can be provided via the BYE message. Accordingly, a
Serving RFSS which does not support the CANCEL functionality in this test may
still be claimed as conformant to this PCP. This test is deemed “Not Applicable”
to such a Serving RFSS.
a case, this test becomes not applicable.
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
g-id of the group : 0064
specified SG. 2- The Serving RFSS does NOT have the specified unconfirmed group call
segment established with the Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_9_9_001Group Call setup – Successful (Protected mode
requested)- Home.
initiates a group call.
considered SG, and the calling SU requests the protected mode. In this
case, the call is setup with the protected option.
Applicable ISSI Conformance Test RFSS Roles: Serving, Home (to Serving),
Home (Multi-Segment)
RFSS.
Serving RFSS 1 rfss-id : 01
Serving RFSS 1 system-id : 001
Serving RFSS 1 wacn-id : 00001
Home RFSS 2 rfss-id : 02
Home RFSS 2 system-id : 002
Home RFSS 2 wacn-id : 00002
Serving RFSS 3 rfss-id : 03
Serving RFSS 3 system-id : 003
Serving RFSS 3 wacn-id : 00003
g-id of the group : 0064
specified SG.
2- The Serving RFSS has a Group call segment established in protected
mode with the Home RFSS
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_9_9_002Group Call setup – Successful (Protected mode
requested)- Home.
initiates a group call.
considered SG, and the calling SU requests the unprotected mode. In this
case, the call is setup with the unprotected option.
Applicable ISSI Conformance Test RFSS Roles: Serving, Home (to Serving),
Home (Multi-Segment)
RFSS.
Serving RFSS 1 rfss-id : 01
Serving RFSS 1 system-id : 001
Serving RFSS 1 wacn-id : 00001
Home RFSS 2 rfss-id : 02
Home RFSS 2 system-id : 002
Home RFSS 2 wacn-id : 00002
Serving RFSS 3 rfss-id : 03
Serving RFSS 3 system-id : 003
Serving RFSS 3 wacn-id : 00003
g-id of the group : 0064
specified SG.
2- The Serving RFSS has a Group call segment established in unprotected
mode with the Home RFSS
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_9_10_001Group call setup – Unsuccessful (Protected audio call
cannot be granted)- Home.
pass the test:
configured to refuse the protected mode for the considered SG.
Only the first case is described in section 9.10.5. In the second case, the cprotected
parameter is set to 0 and the p-25-condition-code and P25-conditiontext
in the 403 Forbidden message will be set to “2C” and "Unprotected audio call
not granted", respectively.
RFSS.
Serving RFSS 1 rfss-id : 01
Serving RFSS 1 system-id : 001
Serving RFSS 1 wacn-id : 00001
Home RFSS 2 rfss-id : 02
Home RFSS 2 system-id : 002
Home RFSS 2 wacn-id : 00002
g-id of the group : 0064
specified SG.
2- The Serving RFSS does NOT have the specified group call segment
established with the Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_9_10_002Group call setup – Unsuccessful (Unprotected audio call
cannot be granted)- Home.
pass the test:
configured to refuse the unprotected mode for the considered SG.
Only the first case is described in section 9.10.5. In the second case, the cprotected
parameter is set to 0 and the p-25-condition-code and P25-conditiontext
in the 403 Forbidden message will be set to “2C” and "Unprotected audio call
not granted", respectively.
RFSS.
Serving RFSS 1 rfss-id : 01
Serving RFSS 1 system-id : 001
Serving RFSS 1 wacn-id : 00001
Home RFSS 2 rfss-id : 02
Home RFSS 2 system-id : 002
Home RFSS 2 wacn-id : 00002
g-id of the group : 0064
specified SG.
2- The Serving RFSS does NOT have the specified group call segment
established with the Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
RFSS/
HOME/
Call_Teardown_Group_Call
SIP_ISSI_Home_10_1_001Group Call Teardown - Successful (Triggered by Serving RFSS)- Home
RFSS initiates a group call. The SG’s Serving RFSS terminates the group call
segment with the Home RFSS due to loss of RTP connectivity or local policy.
Home (Multi-Segment)
2- The Serving RFSS has established a group call segment with the Home
RFSS.
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
g-id of the group : 0064
specified SG.
2- The Serving RFSS does NOT have the specified call segment established
with the Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_10_2_001Group call Teardown – Successful (Triggered by Home RFSS)- Home
RFSS successfully initiates a group call. After the setup, the SG’s Home RFSS
terminates the group call segment with the SG’s Serving RFSS due to ISSI
hangtime expiry, loss of RTP connectivity with the SG’s serving RFSS or local
policy.
Home (Multi-Segment)
2- The Serving RFSS has established a group call segment with the Home
RFSS.
Home rfss-id : 01
Home system-id : 001
Home wacn-id : 00001
Serving rfss-id : 02
Serving system-id : 002
Serving wacn-id : 00002
g-id of the group : 0064
specified SG.
2- The Serving RFSS does NOT have the specified call segment established
with the Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
RFSS/
HOME/
Basic_Group_Call_Trans_Ctrl_Procs		After the setup of an unconfirmed group call, the conformance to the basic
SIP_ISSI_Home_11_1_001Group call transmission – Successful (Serving RFSS starts and stops
talk spurt)- Home.
Serving RFSSs. One Serving RFSS initiates transmission (talk spurts) and then
stops transmitting. The audio is successfully transmitted through the Home
RFSS and to the other Serving RFSS.
Home (Multi-Segment)
2- The Serving RFSS has established a group call segment with the Home
RFSS.
3- The Serving RFSS is idle with respect to sending ISSI voice traffic on this
call segment.
Serving RFSS 1 rfss-id : any
Serving RFSS 1 system-id : any
Serving RFSS 1 wacn-id : any
Home RFSS 2 rfss-id : any
Home RFSS 2 system-id : any
Home RFSS 2 wacn-id : any
Serving RFSS 3 rfss-id : any
Serving RFSS 3 system-id : any
Serving RFSS 3 wacn-id : any
g-id of the group : any
wacn-id of the initiating SU : 00002
system-id of the initiating SU : 002
u-id of the initiating SU : 000001
transmit priority : 00
g-id of the group : 0064
specified SG.
2- The Serving RFSS continues to have the specified call segment
established with the Home RFSS.
3- The Serving RFSS 1 has successfully forwarded audio on the specified
call segment in accordance with this test.
4- The Serving RFSS 3 has successfully received audio on the specified call
segment in accordance with this test.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_11_2_001Group call transmission – Unsuccessful (Denied by Home RFSS)- Home
RFSS denies the transmission.
Home (Multi-Segment)
essential to the transmission control capabilities of the RFSS. Accordingly, a
Home RFSS which does not generate the Deny message as described in this
test may still be claimed as conformant to this PCP. This test is deemed “Not
Applicable” to such a Home RFSS.
specified SG.
2- The Serving RFSS has established a group call segment with the Home
RFSS.
3- The Serving RFSS is idle with respect to sending ISSI voice traffic on this
call segment.
Serving rfss-id : any
Serving system-id : any
Serving wacn-id : any
Home rfss-id : any
Home system-id : any
Home wacn-id : any
g-id of the group : any
wacn-id of the initiating SU : 00002
system-id of the initiating SU : 002
u-id of the initiating SU: 000001
transmit priority : 00
specified SG.
2- The Serving RFSS has the specified call segment established with the
Home RFSS.
3- The Serving RFSS is idle with respect to sending ISSI voice traffic on this
call segment.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_11_3_001Group call Mute and Unmute – Successful (Home RFSS initiated)- Home
RFSS. The Serving RFSS starts transmitting and after a while, the Home RFSS
mutes and then unmutes the transmission. The purpose of this test is to check
that the first Serving RFSS stops sending audio when the Home RFSS sends a
Mute request and resumes transmitting audio when the Home RFSS sends an
Unmute request.
Home (Multi-Segment)
necessarily essential to the transmission control capabilities of an RFSS.
Accordingly, a Home RFSS which does not generate the Mute Request in this
test may still be claimed as conformant to this PCP. This test is deemed “Not
Applicable” to such a Home RFSS.
2- The Serving RFSS has established a group call segment with the Home
RFSS.
3- The Serving RFSS is idle with respect to sending ISSI voice traffic.
Serving rfss-id : any
Serving system-id : any
Serving wacn-id : any
Home rfss-id : any
Home system-id : any
Home wacn-id : any
g-id of the group : any
wacn-id of the initiating SU : 00002
system-id of the initiating SU : 002
u-id of the initiating SU : 000001
transmit priority : 00
specified SG.
2- The Serving RFSS still has the specified call segment established with the
Home RFSS.
3- The Serving RFSS has successfully stopped sending audio when the
Home RFSS told it to mute an active transmission and then re-started
sending audio when the Home RFSS told it to unmute the transmission.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_11_4_001Group call Mute and Unmute – Successful (Serving RFSS initiated)- Home
RFSS. The Home RFSS starts transmitting from one SU and after a while, the
Serving RFSS mutes and unmutes the transmission. The purpose of this test is
to check that the Home RFSS stops sending audio when the Serving RFSS
sends a Mute request and resumes transmitting audio when the Serving RFSS
sends an Unmute request.
Home (Multi-Segment)
essential to the transmission control capabilities of the RFSS. Accordingly, a
Serving RFSS which does not generate the Mute message as described in this
test may still be claimed as conformant to this PCP. This test is deemed “Not
Applicable” to such a Serving RFSS.
2- The Serving RFSS has established a group call segment with the Home
RFSS.
3- The Serving RFSS is idle with respect to sending ISSI voice traffic.
Home rfss-id : any
Home system-id : any
Home wacn-id : any
Serving rfss-id : any
Serving system-id : any
Serving wacn-id : any
g-id of the group : any
wacn-id of the initiating SU : 00002
system-id of the initiating SU : 002
u-id of the initiating SU : 000001
transmit priority : 00
specified SG.
2- The Serving RFSS still has the specified call segment established with the
Home RFSS.
3- The Serving RFSS has successfully sent the ISSI Mute/Unmute
messages on the specified call segment in accordance with this test.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_11_5_001Heartbeat – Successful- Home
RTP session is set up for the unconfirmed group call relative to the SG. The SG’s
Home RFSS and the SG’s Serving RFSS send RTP Heartbeats periodically.
Home (Multi-Segment)
2- The Serving RFSS has established a group call segment with the Home
RFSS.
The Serving RFSS is idle with respect to sending ISSI voice traffic.
Serving rfss-id : any
Serving system-id : any
Serving wacn-id : any
Home rfss-id : any
Home system-id : any
Home wacn-id : any
g-id of the group : any
specified SG.
2- The Serving RFSS still has the specified call segment established with the
Home RFSS.
3- The Serving RFSS has successfully received the Home RTP Heartbeat
message on the specified call segment.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_11_6_001Heartbeat Query – Successful (Serving RFSS initiated)- Home
RTP session is set up for the unconfirmed group call relative to the SG. The SG’s
Serving RFSS sends a Heartbeat Query to the SG’s Home RFSS. The purpose
of this test is to verify that the Home RFSS correctly responds to a Heartbeat
Query message.
Home (Multi-Segment).
RFSS, and is not necessarily essential to the transmission control capabilities of
the RFSS. Accordingly, a Serving RFSS which does not generate the Heartbeat
Query message as described in this test may still be claimed as conformant to
this PCP. This test is deemed “Not Applicable” to such a Serving RFSS.
2- The Serving RFSS has established a group call segment with the Home
RFSS.
3- The Serving RFSS is idle with respect to sending ISSI voice traffic.
Serving rfss-id : any
Serving system-id : any
Serving wacn-id : any
Home rfss-id : any
Home system-id : any
Home wacn-id : any
g-id of the group : any
specified SG.
2- The Serving RFSS still has the specified call segment established with the
Home RFSS.
3- The Serving RFSS has successfully received the Home RTP Heartbeat
response message on the specified call segment.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_11_7_001Heartbeat Query – Successful (Home RFSS initiated)- Home
RTP session is set up for the unconfirmed group call relative to the SG.
Immediately after the establishment of the RTP session, the SG’s Home RFSS is
required to send a Heartbeat Query to the SG’s Serving RFSS.
Home (Multi-Segment)
2- The Serving RFSS has established a group call segment with the Home
RFSS.
3- The Serving RFSS is idle with respect to sending ISSI voice traffic.
Home rfss-id : any
Home system-id : any
Home wacn-id : any
Serving rfss-id : any
Serving system-id : any
Serving wacn-id : any
g-id of the group : any
specified SG.
2- The Serving RFSS still has the specified call segment established with the
Home RFSS.
3- The Serving RFSS has successfully received the Home RTP Heartbeat
Query message on the specified call segment.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_11_8_001Group Call transmission – Successful (Without PTT Transmit Request
at the beginning)- Home.
RFSSs is successful. The first Serving RFSS sends multiple PTT Transmit
Progress messages with no request at the beginning of the talk-spurt, and then
stops transmitting.
Home (Multi-Segment)
Request message is optional, and is not necessarily essential to the transmission
control capabilities of the Serving RFSS. Accordingly, a Serving RFSS which
does not generate the PTT Transmit Progress message as described in this test
may still be claimed as conformant to this PCP. This test is deemed “Not
Applicable” to such a Serving RFSS.
2- The Serving RFSS has established a group call segment with the Home
RFSS.
3- The Serving RFSS is idle with respect to sending ISSI voice traffic.
Serving RFSS 1 rfss-id : any
Serving RFSS 1 system-id : any
Home RFSS 2 rfss-id : any
Home RFSS 2 system-id : any
Home RFSS 2 wacn-id : any
Serving RFSS 3 rfss-id : any
Serving RFSS 3 system-id : any
Serving RFSS 3 wacn-id : any
g-id of the group : any
wacn-id of the initiating SU : 00002
system-id of the initiating SU : 002
u-id of the initiating SU : 000001
transmit priority : 00
specified SG.
2- The Serving RFSS still has the specified call segment established with the
Home RFSS.
3- Serving RFSS 1 has successfully forwarded audio on the specified call
segment in accordance with this test.
4- Serving RFSS 3 has successfully received audio on the specified call
segment in accordance with this test.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_11_9_001Group call transmissions – Successful (with losing audio)- Home
RFSS. The Home RFSS starts transmitting from one SU and after a while, the
Home RFSS starts transmitting from a second SU with a higher priority. The
purpose of this test is to check that the losing audio bit is enabled in the first
group call messages during the second group call transmission.
Home (multi-segment)
not necessarily essential to the transmission control capabilities of the Home
RFSS. Accordingly, a Home RFSS which does not allow simultaneous voice
transmissions on a group as described in this test may still be claimed as
conformant to this PCP. This test is deemed “Not Applicable” to such a Home
RFSS.
2- The Serving RFSS has established a group call segment with the Home
RFSS.
3- The Serving RFSS is idle with respect to sending ISSI voice traffic.
Home rfss-id : any
Home system-id : any
Home wacn-id : any
Serving rfss-id : any
Serving system-id : any
Serving wacn-id : any
g-id of the group : any
wacn-id of SU A : 00001
system-id of SU A : 001
u-id of SU A : 000001
wacn-id of SU B : 00002
system-id of SU B : 002
u-id of SU B : 000002
transmit priority of SU A and SU B: 00
specified SG.
2- The Serving RFSS still has the specified call segment established with the
Home RFSS.
3- The Serving RFSS has successfully received audio on the specified call
segment in accordance with its RFSS role and this test.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
RFSS/
HOME/
Call_Setup_For_Unit_to_Unit_Call		An RFSS can set up an SU-to-SU call.
SIP_ISSI_Home_12_0_001_SU_TestSU call – Successful- Home
Home (to Home), Home (Multi-Segment)
applicable SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the specified SU.
2- The Serving RFSS has established an SU-to-SU call segment with the
appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_1_001SU-to-SU call setup – Successful (Availability Check option enabled)- Home
RFSS. The Calling Home RFSS, the Called Home RFSS and the Called Serving
RFSS do not reject the request. All RFSSs have available RF resources and
RTP resources to set up the SU-to-SU call.
pass this test. This test implements variation:
1- The Calling Serving RFSS initiates the call with the “availability check”
option enabled and the called SU is able to support call with “availability
check”.
Home (to Home), Home (Multi-Segment)
applicable SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the specified SU.
2- The Serving RFSS has established an SU-to-SU call segment with the
appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_1_002SU-to-SU call setup – Successful (Availability Check option disabled)- Home
RFSS. The Calling Home RFSS, the Called Home RFSS and the Called Serving
RFSS do not reject the request. All RFSSs have available RF resources and
RTP resources to set up the SU-to-SU call.
pass this test. This test implements variation:
2- The Calling Serving RFSS initiates the call with the “availability check”
option disabled and the called SU is only able to support call with
availability check.
Home (to Home), Home (Multi-Segment)
applicable SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the specified SU.
2- The Serving RFSS has established an SU-to-SU call segment with the
appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_1_003SU-to-SU call setup – Successful (Availability Check option enabled)- Home
RFSS. The Calling Home RFSS, the Called Home RFSS and the Called Serving
RFSS do not reject the request. All RFSSs have available RF resources and
RTP resources to set up the SU-to-SU call.
pass this test. This test implements variation:
1- The Calling Serving RFSS initiates the call with the “availability check”
option enabled and the called SU is able to support call with “availability
check”.
Home (to Home), Home (Multi-Segment)
applicable SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the specified SU.
2- The Serving RFSS has established an SU-to-SU call segment with the
appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_1_004SU-to-SU call setup – Successful (Availability Check option disabled)- Home
RFSS. The Calling Home RFSS, the Called Home RFSS and the Called Serving
RFSS do not reject the request. All RFSSs have available RF resources and
RTP resources to set up the SU-to-SU call.
pass this test. This test implements variation:
2- The Calling Serving RFSS initiates the call with the “availability check”
option disabled and the called SU is only able to support call with
availability check.
Home (to Home), Home (Multi-Segment)
applicable SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the specified SU.
2- The Serving RFSS has established an SU-to-SU call segment with the
appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_2_001SU-to-SU call setup – Successful (Direct Call option, Availability Check option enabled)- Home
in a Called Serving RFSS. The Calling Home RFSS, the Called Home RFSS and
the Called Serving RFSS do not reject the request coming from the Calling
Serving RFSS to initiate the SU-to-SU call. All RFSSs have available RF
resources and RTP resources to set up the SU-to-SU call.
pass this test. This test implements variation:
1- The Calling Serving RFSS initiates the call with the “Availability Check”
option enabled but the called SU is only able to support Direct Call.
Home (to Home), Home (Multi-Segment)
RFSS for the specified SU.
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the specified SU.
2- The Serving RFSS has established an SU-to-SU call segment with the
appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_2_002SU-to-SU call setup – Successful (Direct Call option, Availability Check option disabled)- Home
in a Called Serving RFSS. The Calling Home RFSS, the Called Home RFSS and
the Called Serving RFSS do not reject the request coming from the Calling
Serving RFSS to initiate the SU-to-SU call. All RFSSs have available RF
resources and RTP resources to set up the SU-to-SU call.
pass this test. This test implements variation:
2- The Calling Serving RFSS initiates the call with the “Availability Check”
option disabled and the called SU is able to support Direct Call.
Home (to Home), Home (Multi-Segment)
RFSS for the specified SU.
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the specified SU.
2- The Serving RFSS has established an SU-to-SU call segment with the
appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_2_003SU-to-SU call setup – Successful (Direct Call option, Availability Check option enabled)- Home
in a Called Serving RFSS. The Calling Home RFSS, the Called Home RFSS and
the Called Serving RFSS do not reject the request coming from the Calling
Serving RFSS to initiate the SU-to-SU call. All RFSSs have available RF
resources and RTP resources to set up the SU-to-SU call.
pass this test. This test implements variation:
1- The Calling Serving RFSS initiates the call with the “Availability Check”
option enabled but the called SU is only able to support Direct Call.
Home (to Home), Home (Multi-Segment)
RFSS for the specified SU.
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the specified SU.
2- The Serving RFSS has established an SU-to-SU call segment with the
appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_2_004SU-to-SU call setup – Successful (Direct Call option, Availability Check option disabled)- Home
in a Called Serving RFSS. The Calling Home RFSS, the Called Home RFSS and
the Called Serving RFSS do not reject the request coming from the Calling
Serving RFSS to initiate the SU-to-SU call. All RFSSs have available RF
resources and RTP resources to set up the SU-to-SU call.
pass this test. This test implements variation:
2- The Calling Serving RFSS initiates the call with the “Availability Check”
option disabled and the called SU is able to support Direct Call.
Home (to Home), Home (Multi-Segment)
RFSS for the specified SU.
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the specified SU.
2- The Serving RFSS has established an SU-to-SU call segment with the
appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_3_001SU-to-SU call setup – Successful (Full Duplex/Half Duplex, Available Check option enabled, SU Direct Call only)- Home
SU call addressed to an SU registered in the Called Serving RFSS. The Calling
Home RFSS, the Called Home RFSS and the Called Serving RFSS do not reject
the request coming from the Calling Serving RFSS to initiate the SU-to-SU call.
All RFSSs have available RF resources and RTP resources for the SU-to-SU
call. The Calling SU and Called SU both support the full duplex and half duplex
modes.
pass this test. This test implements variation:
1- The Calling Serving RFSS initiates the call with the “Availability Check”
option enabled but the called SU is only able to support Direct Call.
Home (to Home), Home (Multi-Segment)
applicable SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the specified SU.
2- The Serving RFSS has established an SU-to-SU call segment with the
appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_3_002SU-to-SU call setup – Successful (Full Duplex/Half Duplex, Available Check option disabled, SU Direct Call only)- Home
SU call addressed to an SU registered in the Called Serving RFSS. The Calling
Home RFSS, the Called Home RFSS and the Called Serving RFSS do not reject
the request coming from the Calling Serving RFSS to initiate the SU-to-SU call.
All RFSSs have available RF resources and RTP resources for the SU-to-SU
call. The Calling SU and Called SU both support the full duplex and half duplex
modes.
pass this test. This test implements variation:
2- The Calling Serving RFSS initiates the call with the “Availability Check”
option disabled and the called SU is able to support Direct Call.
Home (to Home), Home (Multi-Segment)
applicable SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the specified SU.
2- The Serving RFSS has established an SU-to-SU call segment with the
appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_3_003SU-to-SU call setup – Successful (Full Duplex/Half Duplex, Available Check option disabled, SU supports Availability Check)- Home
SU call addressed to an SU registered in the Called Serving RFSS. The Calling
Home RFSS, the Called Home RFSS and the Called Serving RFSS do not reject
the request coming from the Calling Serving RFSS to initiate the SU-to-SU call.
All RFSSs have available RF resources and RTP resources for the SU-to-SU
call. The Calling SU and Called SU both support the full duplex and half duplex
modes.
pass this test. This test implements variation:
3- The Calling Serving RFSS initiates the call without the “Availability Check”
option enabled but the called SU is able to support call with availability
check.
Home (to Home), Home (Multi-Segment)
applicable SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the specified SU.
2- The Serving RFSS has established an SU-to-SU call segment with the
appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_4_001SU-to-SU call setup – Successful (initiated in full duplex, setup in half
duplex, Availability Check enabled, SU only supports Direct Call)- Home.
addressed to an SU registered in the Called Serving RFSS. The Calling Home
RFSS, the Called Home RFSS and the Called Serving RFSS do not reject the
request coming from the Calling Serving RFSS to initiate the SU-to-SU call. All
RFSSs have available RF resources and RTP resources for the SU-to-SU call.
The Calling SU both support the full duplex and half duplex modes. The Called
SU supports only half-duplex mode.
pass this test. This test implements variation:
1- The Calling Serving RFSS initiates the call with the “Availability Check”
option enabled but the called SU is only able to support Direct Call.
cases, the SIP Ringing message is never sent out and the field “c-pref” is present
in the appropriate SIP INVITE and 200 OK message as described in BACA-A
and specifically tested in sections 12.1and 12.2.
Home (to Home), Home (Multi-Segment)
applicable SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the specified SU.
2- The Serving RFSS has established an SU-to-SU call segment with the
appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_4_002SU-to-SU call setup – Successful (initiated in full duplex, setup in half
duplex, Availability Check disabled, SU supports Direct Call)- Home.
addressed to an SU registered in the Called Serving RFSS. The Calling Home
RFSS, the Called Home RFSS and the Called Serving RFSS do not reject the
request coming from the Calling Serving RFSS to initiate the SU-to-SU call. All
RFSSs have available RF resources and RTP resources for the SU-to-SU call.
The Calling SU both support the full duplex and half duplex modes. The Called
SU supports only half-duplex mode.
pass this test. This test implements variation:
2- The Calling Serving RFSS initiates the call with the “Availability Check”
option disabled and the called SU is able to support Direct Call.
cases, the SIP Ringing message is never sent out and the field “c-pref” is present
in the appropriate SIP INVITE and 200 OK message as described in BACA-A
and specifically tested in sections 12.1and 12.2.
Home (to Home), Home (Multi-Segment)
applicable SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the specified SU.
2- The Serving RFSS has established an SU-to-SU call segment with the
appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_4_003SU-to-SU call setup – Successful (initiated in full duplex, setup in half
duplex, Availability Check disabled, SU supports Availability check)- Home.
addressed to an SU registered in the Called Serving RFSS. The Calling Home
RFSS, the Called Home RFSS and the Called Serving RFSS do not reject the
request coming from the Calling Serving RFSS to initiate the SU-to-SU call. All
RFSSs have available RF resources and RTP resources for the SU-to-SU call.
The Calling SU both support the full duplex and half duplex modes. The Called
SU supports only half-duplex mode.
pass this test. This test implements variation:
3- The Calling Serving RFSS initiates the call without the “Availability Check”
option enabled but the called SU is able to support call with availability
check.
cases, the SIP Ringing message is never sent out and the field “c-pref” is present
in the appropriate SIP INVITE and 200 OK message as described in BACA-A
and specifically tested in sections 12.1and 12.2.
Home (to Home), Home (Multi-Segment)
applicable SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the specified SU.
2- The Serving RFSS has established an SU-to-SU call segment with the
appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_5_001SU-to-SU call setup – Successful (Protected mode requested)- Home
addressed to an SU registered in the Called Serving RFSS. All RFSSs have
available RF resources and RTP resources for the SU-to-SU call. The Called
Home RFSS determines whether the call is protected or not.
pass this test. This test implements variation:
1- The Called Home RFSS is configured to accept the protected mode for
the called SU, and the calling SU requests the protected mode. In this
case, the call is set up with the protected option.
Home (to Home), Home (Multi-Segment)
applicable SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the specified SU.
2- The Serving RFSS has established an SU-to-SU call segment in protected
mode or not protected mode with the appropriate Home RFSS depending
on the considered test case.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_5_002SU-to-SU call setup – Successful (Unprotected mode)- Home
addressed to an SU registered in the Called Serving RFSS. All RFSSs have
available RF resources and RTP resources for the SU-to-SU call. The Called
Home RFSS determines whether the call is protected or not.
pass this test. This test implements variation:
2- The Called Home RFSS is configured to accept the unprotected mode for
the called SU, and the calling SU requests the unprotected mode. In this
case, the call is set up with the unprotected option.
Home (to Home), Home (Multi-Segment)
applicable SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the specified SU.
2- The Serving RFSS has established an SU-to-SU call segment in protected
mode or not protected mode with the appropriate Home RFSS depending
on the considered test case.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_6_001SU-to-SU call setup (RF resources initially unavailable in Called
Serving RFSS, Availability Check enabled, SU only supports Direct Call)- Home.
registered in the Called Serving RFSS. The Calling Home RFSS, the Called
Home RFSS and the Called Serving RFSS do not reject the request coming from
the Calling Serving RFSS to initiate the SU-to-SU call. All RFSSs have available
RTP resources to set up a call segment. The Called Serving RFSS initially does
not have RF resources available.
pass this test. This test implements variation:
1- The Calling Serving RFSS initiates the call with the “Availability Check”
option enabled but the called SU is only able to support Direct Call.
cases, the SIP Ringing message is never sent out and the field “c-pref” is present
in the appropriate SIP INVITE and 200 OK message as described in BACA-A
and specifically tested in sections 12.1and 12.2.
Home (to Home), Home (Multi-Segment)
applicable SU.
2- The Called Serving RFSS does not have RF resources available.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the specified SU.
2- The Serving RFSS has established an SU-to-SU call segment with the
appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_6_002SU-to-SU call setup (RF resources initially unavailable in Called
Serving RFSS, Availability Check disabled, SU supports Direct Call)- Home.
registered in the Called Serving RFSS. The Calling Home RFSS, the Called
Home RFSS and the Called Serving RFSS do not reject the request coming from
the Calling Serving RFSS to initiate the SU-to-SU call. All RFSSs have available
RTP resources to set up a call segment. The Called Serving RFSS initially does
not have RF resources available.
pass this test. This test implements variation:
2- The Calling Serving RFSS initiates the call with the “Availability Check”
option disabled and the called SU is able to support Direct Call.
cases, the SIP Ringing message is never sent out and the field “c-pref” is present
in the appropriate SIP INVITE and 200 OK message as described in BACA-A
and specifically tested in sections 12.1and 12.2.
Home (to Home), Home (Multi-Segment)
applicable SU.
2- The Called Serving RFSS does not have RF resources available.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the specified SU.
2- The Serving RFSS has established an SU-to-SU call segment with the
appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_6_003SU-to-SU call setup (RF resources initially unavailable in Called
Serving RFSS, Availability Check disabled, SU supports Availability Check)- Home.
registered in the Called Serving RFSS. The Calling Home RFSS, the Called
Home RFSS and the Called Serving RFSS do not reject the request coming from
the Calling Serving RFSS to initiate the SU-to-SU call. All RFSSs have available
RTP resources to set up a call segment. The Called Serving RFSS initially does
not have RF resources available.
pass this test. This test implements variation:
3- The Calling Serving RFSS initiates the call without the “Availability Check”
option enabled but the called SU is able to support call with availability
check.
cases, the SIP Ringing message is never sent out and the field “c-pref” is present
in the appropriate SIP INVITE and 200 OK message as described in BACA-A
and specifically tested in sections 12.1and 12.2.
Home (to Home), Home (Multi-Segment)
applicable SU.
2- The Called Serving RFSS does not have RF resources available.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the specified SU.
2- The Serving RFSS has established an SU-to-SU call segment with the
appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_7_001SU-to-SU call setup (Call canceled by the Calling Serving RFSS,
Availability Check enabled, SU only supports Direct Call)- Home.
in the Called Serving RFSS. The Calling Serving RFSS cancels immediately after
initiating the call.
pass this test. This test implements variation:
1- The Calling Serving RFSS initiates the call with the “Availability Check”
option enabled but the called SU is only able to support Direct Call.
cases, the SIP Ringing message is never sent out and the field “c-pref” is present
in the appropriate SIP INVITE and 200 OK message as described in BACA-A
and specifically tested in sections 12.1and 12.2.
Home (to Home), Home (Multi-Segment)
applicable SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the specified SU.
2- The Serving RFSS has NOT established an SU-to-SU call segment with
the appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_7_002SU-to-SU call setup (Call canceled by the Calling Serving RFSS,
Availability Check disabled, SU supports Direct Call)- Home.
in the Called Serving RFSS. The Calling Serving RFSS cancels immediately after
initiating the call.
pass this test. This test implements variation:
2- The Calling Serving RFSS initiates the call with the “Availability Check”
option disabled and the called SU is able to support Direct Call.
cases, the SIP Ringing message is never sent out and the field “c-pref” is present
in the appropriate SIP INVITE and 200 OK message as described in BACA-A
and specifically tested in sections 12.1and 12.2.
Home (to Home), Home (Multi-Segment)
applicable SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the specified SU.
2- The Serving RFSS has NOT established an SU-to-SU call segment with
the appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_7_003SU-to-SU call setup (Call canceled by the Calling Serving RFSS,
Availability Check disabled, SU supports Availability Check)- Home.
in the Called Serving RFSS. The Calling Serving RFSS cancels immediately after
initiating the call.
pass this test. This test implements variation:
3- The Calling Serving RFSS initiates the call without the “Availability Check”
option enabled but the called SU is able to support call with availability
check.
cases, the SIP Ringing message is never sent out and the field “c-pref” is present
in the appropriate SIP INVITE and 200 OK message as described in BACA-A
and specifically tested in sections 12.1and 12.2.
Home (to Home), Home (Multi-Segment)
applicable SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the specified SU.
2- The Serving RFSS has NOT established an SU-to-SU call segment with
the appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_8_001SU-to-SU call setup (Calls with different priorities,
Availability Check enabled, SU only supports Direct Call)- Home.
in the Called Serving RFSS. While awaiting the response for the call, the Called
RFSS initiates an SU-to-SU call addressed to the Calling SU. The SU-to-SU call
initiated by the Called RFSS has higher priority than the SU-to-SU call originated
by the Calling RFSS. The collision between the two calls is detected and
mitigated by the Called Serving RFSS.
pass this test. This test implements variation:
1- The Calling Serving RFSS initiates the call with the “Availability Check”
option enabled but the called SU is only able to support Direct Call.
cases, the SIP Ringing message is never sent out and the field “c-pref” is present
in the appropriate SIP INVITE and 200 OK message as described in BACA-A
and specifically tested in sections 12.1and 12.2.
considers that the call to be declined is the one initiated for the SU having the
lowest SUID.
Home (to Home), Home (Multi-Segment)
applicable SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the specified SU.
2- The Serving RFSS has established the higher priority SU-to-SU call
segment with the appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_8_002SU-to-SU call setup (Calls with different priorities,
Availability Check enabled, SU only supports Direct Call)- Home.
in the Called Serving RFSS. While awaiting the response for the call, the Called
RFSS initiates an SU-to-SU call addressed to the Calling SU. The SU-to-SU call
initiated by the Called RFSS has higher priority than the SU-to-SU call originated
by the Calling RFSS. The collision between the two calls is detected and
mitigated by the Called Serving RFSS.
pass this test. This test implements variation:
2- The Calling Serving RFSS initiates the call with the “Availability Check”
option disabled and the called SU is able to support Direct Call.
cases, the SIP Ringing message is never sent out and the field “c-pref” is present
in the appropriate SIP INVITE and 200 OK message as described in BACA-A
and specifically tested in sections 12.1and 12.2.
considers that the call to be declined is the one initiated for the SU having the
lowest SUID.
Home (to Home), Home (Multi-Segment)
applicable SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the specified SU.
2- The Serving RFSS has established the higher priority SU-to-SU call
segment with the appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_8_003SU-to-SU call setup (Calls with different priorities,
Availability Check enabled, SU only supports Direct Call)- Home.
in the Called Serving RFSS. While awaiting the response for the call, the Called
RFSS initiates an SU-to-SU call addressed to the Calling SU. The SU-to-SU call
initiated by the Called RFSS has higher priority than the SU-to-SU call originated
by the Calling RFSS. The collision between the two calls is detected and
mitigated by the Called Serving RFSS.
pass this test. This test implements variation:
3- The Calling Serving RFSS initiates the call without the “Availability Check”
option enabled but the called SU is able to support call with availability
check.
cases, the SIP Ringing message is never sent out and the field “c-pref” is present
in the appropriate SIP INVITE and 200 OK message as described in BACA-A
and specifically tested in sections 12.1and 12.2.
considers that the call to be declined is the one initiated for the SU having the
lowest SUID.
Home (to Home), Home (Multi-Segment)
applicable SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the specified SU.
2- The Serving RFSS has established the higher priority SU-to-SU call
segment with the appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_9_001SU-to-SU call setup (Calling SU not registered in the Calling Home
RFSS)- Home.
registered in the Calling Home RFSS.
Home (Multi-Segment)
Home RFSS for the Calling SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
u-id of the calling SU : 000011
u-id of the called SU : 000012
segment with the Calling Home RFSS.
2- The Calling Serving RFSS considers the Calling SU NOT registered.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_10_001SU-to-SU call setup (Called SU not registered in the Called Home
RFSS)- Home.
registered in the Called Home RFSS.
Home (to Home), Home (Multi-Segment)
RFSS for the specified SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
u-id of the calling SU : 000011
u-id of the called SU : 000012
Home RFSS for the Calling SU.
2- The Serving RFSS has NOT established an SU-to-SU call segment with
the appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_11_001SU-to-SU call setup (Calling SU not authorized to make a call)- Home
authorized by the Calling Home RFSS to make this call.
Home (Multi-Segment)
Home RFSS for the specified SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
u-id of the calling SU : 000011
u-id of the called SU : 000012
Home RFSS for the specified SU.
2- The Calling Serving RFSS has NOT established an SU-to-SU call
segment with the Calling Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_12_001SU-to-SU call setup (Called SU not authorized to respond to a call)- Home
configured to refuse the considered call with the cause reflecting that the called
SU is not authorized to receive the call.
Home (to Home), Home (Multi-Segment)
RFSS for the specified SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
u-id of the calling SU : 000011
u-id of the called SU : 000012
Home RFSS for the Calling SU.
2- The Serving RFSS has NOT established an SU-to-SU call segment with
the appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_13_001SU-to-SU call setup (Protected audio call cannot be
granted)- Home.
detects that the request with the chosen mode cannot be granted.
pass the test. This test performs the following variation:
1- The calling SU requests protected mode. In this case, the Called Home
RFSS is configured to not accept protected mode.
NOTE:
Only the first case is described in section 12.13.5. In the second case, the cprotected
parameter is set to 0 or is not present and the p25-condition-code and
P25-condition-text in the 403 Forbidden message will be set to “2C” and
"Unprotected audio call not granted", respectively.
Applicable ISSI Conformance Test RFSS Roles: Serving, Home (to Serving),
Home (to Home), Home (Multi-Segment)
of the applicable SU.
2- The Called Serving RFSS considers itself registered with the Home RFSS
of the applicable SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
u-id of the calling SU : 000011
u-id of the called SU : 000012
Home RFSS for the Calling SU.
2- The Serving RFSS has NOT established an SU-to-SU call segment with
the appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_13_002SU-to-SU call setup (unprotected audio call cannot be
granted)- Home.
detects that the request with the chosen mode cannot be granted.
pass the test. This test performs the following variation:
2- The calling SU requests unprotected mode. In this case, the Called Home
RFSS is configured to not accept unprotected mode.
NOTE:
Only the first case is described in section 12.13.5. In the second case, the cprotected
parameter is set to 0 or is not present and the p25-condition-code and
P25-condition-text in the 403 Forbidden message will be set to “2C” and
"Unprotected audio call not granted", respectively.
Applicable ISSI Conformance Test RFSS Roles: Serving, Home (to Serving),
Home (to Home), Home (Multi-Segment)
of the applicable SU.
2- The Called Serving RFSS considers itself registered with the Home RFSS
of the applicable SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
u-id of the calling SU : 000011
u-id of the called SU : 000012
Home RFSS for the Calling SU.
2- The Serving RFSS has NOT established an SU-to-SU call segment with
the appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_14_001SU-to-SU call setup (Calling SU unknown to Calling Home RFSS)- Home
to the Calling Home RFSS.
Home (Multi-Segment)
applicable SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
u-id of the calling SU : 000011
u-id of the called SU : 000012
Home RFSS for the Calling SU.
2- The Serving RFSS has NOT established an SU-to-SU call segment with
the appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_15_001SU-to-SU call setup (Called SU unknown to Called Home RFSS)- Home
to the Called Home RFSS.
Home (to Home), Home (Multi-Segment)
applicable SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the Calling SU.
2- The Serving RFSS has NOT established an SU-to-SU call segment with the
appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_16_001SU-to-SU call setup (Called SU not registered to Called Serving
RFSS)- Home.
registered to the Called Serving RFSS.
Home (to Home), Home (Multi-Segment)
Home RFSS for the specified SU.
2- The Called Serving RFSS considers itself NOT registered with the Called
Home RFSS for the specified SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
Home RFSS for the Calling SU.
2- The Serving RFSS has NOT established an SU-to-SU call segment with
the appropriate Home RFSS.
3- The Called Serving RFSS considers itself NOT registered with the Called
Home RFSS for the Called SU.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_17_001SU-to-SU call setup (Calling SU radio inhibited – case 1)- Home
detects that the Calling SU is radio inhibited.
Home (Multi-Segment)
RFSS for the specified SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
u-id of the calling SU : 000011
u-id of the called SU : 000012
Home RFSS for the Calling SU.
2- The Serving RFSS has NOT established an SU-to-SU call segment with
the appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_18_001SU-to-SU call setup (Calling SU radio inhibited – case 2)- Home
detects, while awaiting a final response on the Called Home RFSS, that the
Calling SU is radio inhibited.
Home (to Home), Home (Multi-Segment)
RFSS for the specified SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
u-id of the calling SU : 000011
u-id of the called SU : 000012
Home RFSS for the Calling SU.
2- The Serving RFSS has NOT established an SU-to-SU call segment with
the appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_19_001SU-to-SU call setup (Called SU radio inhibited – case 1)- Home
detects that the Called SU is radio inhibited.
Home (to Home), Home (Multi-Segment)
RFSS for the specified SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
u-id of the calling SU : 000011
u-id of the called SU : 000012
Home RFSS for the Calling SU.
2- The Serving RFSS has NOT established an SU-to-SU call segment with
the appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_20_001SU-to-SU call setup (Called SU radio inhibited – case 2)- Home
detects while awaiting a final response on the Called Serving RFSS that the
Called SU is radio inhibited.
Home (to Home), Home (Multi-Segment)
RFSS for the specified SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
Home RFSS for the Calling SU.
2- The Serving RFSS has NOT established an SU-to-SU call segment with
the appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_21_001SU-to-SU call setup (Called Serving RFSS does not have available
RTP resources)- Home.
Called Serving RFSS. The Called Serving RFSS does not have available RTP
resources to set up RTP sessions.
Home (to Home), Home (Multi-Segment)
applicable SU.
2- The Called Serving RFSS does NOT have RTP resources available to
establish an ISSI SU-to-SU call.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the specified SU.
2- The Serving RFSS has NOT established an SU-to-SU call segment with
the appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_22_001SU-to-SU call setup (Called SU is busy)- Home
Called Serving RFSS. The Calling Home RFSS, the Called Home RFSS and the
Called Serving RFSS do not reject the call request. All RFSSs have available RF
resources and RTP resources to set up the SU-to-SU call. The Called Serving
RFSS does not accept the call because the requested SU is busy. The Called
Serving RFSS responds with an appropriate error message.
Home (to Home), Home (Multi-Segment)
applicable SU.
2- The Called Serving RFSS considers the Called SU busy.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the specified SU.
2- The Serving RFSS has NOT established an SU-to-SU call segment with
the appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_23_001SU Roaming (Called SU)- Home
the call, a New Called Serving RFSS registers for the SU triggering the Roamed
procedure.
Home (Multi-Segment)
of the applicable SU.
2- The Called Serving RFSS has successfully established an SU-to-SU call
segment with the Home RFSS.
3- The New Called Serving RFSS considers itself NOT registered with the
Home RFSS for the SU.
New Called Serving rfss-id : 01
New Called Serving system-id : 001
New Called Serving wacn-id : 00001
Called and calling Home rfss-id : 02
Called and calling Home system-id : 002
Called and calling Home wacn-id : 00002
Called Serving rfss-id : 03
Called Serving system-id : 003
Called Serving wacn-id : 00003
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the SU.
2- The Called Serving RFSS does NOT have an SU-to-SU call segment
established with the Home RFSS.
3- The New Called Serving RFSS considers itself registered with the Home
RFSS for the SU.
4- The New Called Serving RFSS has established an SU-to-SU call segment
with the Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_24_001SU Roaming (Called SU)- Home
the call, a New Calling Serving RFSS registers for the SU triggering the Roamed
procedure.
Home (Multi-Segment)
of the applicable SU.
2- The Calling Serving RFSS has successfully established an SU-to-SU call
segment with the Home RFSS.
3- The New Calling Serving RFSS considers itself NOT registered for the
SU.
New Calling Serving rfss-id : 01
New Calling Serving system-id : 001
New Calling Serving wacn-id : 00001
Calling and called Home rfss-id : 02
Calling and called Home system-id : 002
Calling and called Home wacn-id : 00002
Calling Serving rfss-id : 03
Calling Serving system-id : 003
Calling Serving wacn-id : 00003
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the SU.
2- The Calling Serving RFSS does NOT have an SU-to-SU call segment
established with the Home RFSS.
3- The New Calling Serving RFSS considers itself registered with the Home
RFSS for the SU.
4- The New Calling Serving RFSS has established an SU-to-SU call
segment with the Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_25_001SU Roaming (No RF resources available in the New Called Serving
RFSS)- Home.
the call, a New Called Serving RFSS registers for the SU triggering the Roamed
procedure. The New Called Serving RFSS has no RF resource available and the
SU-to-SU call is terminated.
Home (Multi-Segment)
of the applicable SU.
2- The Called Serving RFSS has successfully established an SU-to-SU call
segment with the Home RFSS.
3- The New Called Serving RFSS is NOT registered for the SU.
4- The New Called Serving RFSS does NOT have RF resources available.
New Called Serving rfss-id : 01
New Called Serving system-id : 001
New Called Serving wacn-id : 00001
Called and calling Home rfss-id : 02
Called and calling Home system-id : 002
Called and calling Home wacn-id : 00002
Called Serving rfss-id : 03
Called Serving system-id : 003
Called Serving wacn-id : 00003
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the SU.
2- The Called Serving RFSS does NOT have an SU-to-SU call segment
established with the Home RFSS.
3- The New Called Serving RFSS considers itself registered with the Home
RFSS for the SU.
4- The New Called Serving RFSS does NOT have an SU-to-SU call segment
established with the Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_12_26_001SU Roaming (No RF resources available in the New Calling Serving
RFSS)
the call, a New Calling Serving RFSS registers for the SU triggering the Roamed
procedure. The New Calling Serving RFSS has no RF resources available and
the SU-to-SU call is terminated.
Home (Multi-Segment)
of the applicable SU.
2- The Calling Serving RFSS has successfully established an SU-to-SU call
segment with the Home RFSS.
3- The New Calling Serving RFSS is NOT registered for the SU.
4- The New Calling Serving RFSS does NOT have RF resources available.
New Calling Serving rfss-id : 01
New Calling Serving system-id : 001
New Calling Serving wacn-id : 00001
Calling and called Home rfss-id : 02
Calling and called Home system-id : 002
Calling and called Home wacn-id : 00002
Calling Serving rfss-id : 03
Calling Serving system-id : 003
Calling Serving wacn-id : 00003
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the SU.
2- The Calling Serving RFSS does NOT have an SU-to-SU call segment
established with the Home RFSS.
3- The New Calling Serving RFSS considers itself registered with the Home
RFSS for the SU.
4- The New Calling Serving RFSS does NOT have an SU-to-SU call
segment established with the Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
RFSS/
HOME/
Call_Teardown_Unit_to_Unit_Call
SIP_ISSI_Home_13_1_001SU Roaming (No RF resources available in the New Calling Serving
RFSS)- Home.
Called Serving RFSS. The SU-to-SU call setup is successful. The Calling
Serving RFSS terminates the call.
Home (to Home), Home (Multi-Segment)
applicable SU.
2- The Serving RFSS has successfully established an SU-to-SU call
segment with the appropriate Home RFSS.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the applicable SU.
2- The Serving RFSS does NOT have an SU-to-SU call segment established
with the appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_13_1_002SU Roaming (No RF resources available in the New Calling Serving
RFSS)- Home.
Called Serving RFSS. The SU-to-SU call setup is successful. The Calling
Serving RFSS terminates the call.
Home (to Home), Home (Multi-Segment)
applicable SU.
2- The Serving RFSS has successfully established an SU-to-SU call
segment with the appropriate Home RFSS.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the applicable SU.
2- The Serving RFSS does NOT have an SU-to-SU call segment established
with the appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_13_2_001SU-to-SU call termination (Called Serving RFSS initiated)- Home
in the Called Serving RFSS. The SU-to-SU call setup is successful. The Called
Serving RFSS releases the SU-to-SU call.
Home (to Home), Home (Multi-Segment)
applicable SU.
2- The Serving RFSS has successfully established an SU-to-SU call
segment with the appropriate Home RFSS.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
RFSS for the applicable SU.
2- The Serving RFSS does NOT have an SU-to-SU call segment established
with the appropriate Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
RFSS/
HOME/
Basic_SU_to_SU_Call_Transmission_Ctrl_Procs		After the setup of a unit to unit call, the conformance to the basic transmission
SIP_ISSI_Home_14_1_001SU to SU Voice Transmission (Serving RFSS originated)- Home
Serving RFSS. The Calling Serving RFSS starts and then stops a voice
transmission.
Home (to Home), Home (Multi-Segment)
applicable SU.
2- The Serving RFSS has successfully established an SU-to-SU call
segment with the appropriate Home RFSS.
Calling Serving rfss-id : any
Calling Serving system-id : any
Calling Serving wacn-id : any
Calling Home rfss-id : any
Calling Home system-id : any
Calling Home wacn-id : any
Called Home rfss-id : any
Called Home system-id : any
Called Home wacn-id : any
Called Serving rfss-id : any
Called Serving system-id : any
Called Serving wacn-id : any
wacn-id of the calling SU: 00002
system-id of the calling SU: 002
u-id of the calling SU : 000001
transmit priority : 00
RFSS for the applicable SU.
2- The Serving RFSS has an SU-to-SU call segment established with the
appropriate Home RFSS.
3- The Serving RFSS is idle with respect to ISSI audio traffic on the SU-to-
SU call segment.
4- The Calling Serving RFSS has successfully forwarded audio on the
specified call segment in accordance with this test.
5- The Called Serving RFSS has successfully received audio on the
specified call segment in accordance with this test.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_14_2_001SU to SU Voice transmission (Serving RFSS originated with no PTT
Transmit Request)- Home.
an SU registered in a Called Serving RFSS. The Calling Serving RFSS starts
and then stops the transmission but does not exert the PTT Transmit Request at
the beginning of the transmission.
Home (to Home), Home (Multi-Segment)
Request message is optional, and is not necessarily essential to the transmission
control capabilities of the Serving RFSS. Accordingly, a Serving RFSS which
does not generate the PTT Transmit Progress message as described in this test
may still be claimed as conformant to this PCP. This test is deemed “Not
Applicable” to such a Serving RFSS.
applicable SU.
2- The Serving RFSS has successfully established an SU-to-SU call
segment with the appropriate Home RFSS.
Calling Serving rfss-id : any
Calling Serving system-id : any
Calling Serving wacn-id : any
Calling Home rfss-id : any
Calling Home system-id : any
Calling Home wacn-id : any
Called Home rfss-id : any
Called Home system-id : any
Called Home wacn-id : any
Called Serving rfss-id : any
Called Serving system-id : any
Called Serving wacn-id : any
wacn-id of the calling SU: 00002
system-id of the calling SU: 002
u-id of the calling SU : 000001
transmit priority : 00
RFSS for the applicable SU.
2- The Serving RFSS has an SU-to-SU call segment established with the
appropriate Home RFSS.
3- The Serving RFSS is idle with respect to ISSI audio traffic on the SU-to-
SU call segment.
4- The Called Serving RFSS has successfully received audio on the
specified call segment in accordance with this test.
5- The Calling Serving RFSS has successfully forwarded audio on the
specified call segment in accordance with this test.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_14_3_001RTP Heartbeat- Home
RFSS, Calling Home RFSS, Called Home RFSS and a Called Serving RFSS.
The Calling Serving RFSS, Calling Home RFSS, Called Home RFSS and the
Called Serving RFSS send the RTP Heartbeat message periodically.
Home (to Home), Home (Multi-Segment)
applicable SU.
2- The Serving RFSS has successfully established an SU-to-SU call
segment with the appropriate Home RFSS.
3- The Serving RFSS is idle with respect ISSI voice traffic on the SU-to-SU
call segment.
Calling Serving rfss-id : any
Calling Serving system-id : any
Calling Serving wacn-id : any
Calling Home rfss-id : any
Calling Home system-id : any
Calling Home wacn-id : any
Called Home rfss-id : any
Called Home system-id : any
Called Home wacn-id : any
Called Serving rfss-id : any
Called Serving system-id : any
Called Serving wacn-id : any
RFSS for the applicable SU.
2- The Serving RFSS has an SU-to-SU call segment established with the
appropriate Home RFSS.
3- The Serving RFSS has successfully received the RTP Heartbeat message
on the SU-to-SU call segment.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
RFSS/
HOME/
Serving_Query_Procedures		A Serving RFSS can require knowledge of an SUs profile.
SIP_ISSI_Home_15_1_001Serving Query – Successful (Serving RFSS is registered for the SU)- Home
the Home RFSS of the SU.
Home (Multi-Segment)
applicable SU.
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
u-id of the SU : 000011
applicable SU.
2- The Serving RFSS has successfully received the SIP “OK 200” (Serving
Query response) message from the Home RFSS.
Config: A
SIP_ISSI_Home_15_2_001Serving Query – Successful (Serving RFSS not registered for the SU)- Home
Home RFSS.
Home (Multi-Segment)
of the SU.
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
u-id of the SU : 000011
for the applicable SU.
2- The Serving RFSS has successfully received the “OK 200” (Serving Query
response) message from the Home RFSS.
SIP_ISSI_Home_15_3_001Serving Query – Failure (RFSS not authorized)- Home
a request to the SU’s Home. However the Serving RFSS is not authorized to
receive information about this SU.
Home (Multi-Segment)
of the SU.
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
u-id of the SU : 000011
for the applicable SU.
2- The Serving RFSS has successfully received the SIP “403 FORBIDDEN”
response message from the Home RFSS.
SIP_ISSI_Home_15_4_001Serving Query - Failure (wrong Home RFSS)- Home
sends a request to a Home RFSS that is not the Home RFSS of the SU. The
Home RFSS responds with an appropriate error message.
Home (Multi-Segment)
of the SU.
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
u-id of the SU : 000011
for the applicable SU.
2- The Serving RFSS has successfully received the SIP “404 NOT FOUND”
response message from the Home RFSS.
RFSS/
HOME/
Home_Query_Procedures		A Home RFSS can confirm the registration of an SU.
SIP_ISSI_Home_16_1_001SU Home Query – Failure (unknown SU)-Home
The request is sent to the Serving RFSS. The response of the Serving RFSS is
tested in the case where the SU is no longer being served by this Serving RFSS
(for example, an SU is no longer registered in this RFSS).
Home (Multi-Segment)
1- The Serving RFSS considers itself NOT registered with this Home RFSS
for the requested SU.
Home rfss-id : 01
Home system-id : 001
Home wacn-id : 00001
Serving rfss-id : 02
Serving system-id : 002
Serving wacn-id : 00002
u-id of the SU : 000011

User Action: SU to send Register
1- The Serving RFSS considers itself NOT registered with the Home RFSS
for the requested SU.
2- The Serving RFSS has successfully received the SIP “REGISTER” (Home
Query) message from the Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_16_2_001SU Home Query – Successful (“Force” parameter enabled)-Home
In the event that the “Force” qualifier is enabled in the request to the Serving
RFSS, the response of the Serving RFSS is tested. The Serving RFSS has the
SU profile information.
Home (Multi-Segment)
1- The Serving RFSS considers itself registered with this Home RFSS for the
requested SU.
Home rfss-id : 01
Home system-id : 001
Home wacn-id : 00001
Serving rfss-id : 02
Serving system-id : 002
Serving wacn-id : 00002
u-id of the SU : 000011

User Action: SU to send Register
1- The Serving RFSS considers itself registered with the Home RFSS for the
requested SU.
2- The Serving RFSS subsequently initiates an SU registration to the Home
RFSS as described in test case 4.1.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_16_3_001SU Home Query – Successful (“Confirm” parameter enabled)-Home
Home RFSS, the response of the Serving RFSS is tested. The Serving RFSS
gets active confirmation that the SU is located in its area.
Home (Multi-Segment)
1- The Serving RFSS considers itself registered with the Home RFSS for the
requested SU.
2- The Serving RFSS considers the requested SU present and reachable.
Home rfss-id : 01
Home system-id : 001
Home wacn-id : 00001
Serving rfss-id : 02
Serving system-id : 002
Serving wacn-id : 00002
u-id of the SU : 000011

User Action: SU to send Register
1- The Serving RFSS considers itself registered with the Home RFSS for the
requested SU.
2- The Serving RFSS considers the requested SU present and reachable.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_16_4_001SU Home Query – Successful (“Force”/“Confirm” parameters reset)-Home
particular SU. In the event that neither the “Force” qualifier nor the “Confirm”
qualifier is enabled in the request sent by the Home RFSS to the Serving RFSS,
the response of the Serving RFSS is tested. The Serving RFSS is registered for
the SU.
Home (Multi-Segment)
1- The Serving RFSS considers itself registered with the Home RFSS for the
requested SU.
Home rfss-id : 01
Home system-id : 001
Home wacn-id : 00001
Serving rfss-id : 02
Serving system-id : 002
Serving wacn-id : 00002
u-id of the SU : 000011

User Action: SU to send Register
1- The Serving RFSS considers itself registered with the Home RFSS for the
requested SU.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
RFSS/
HOME/
Home_Query_Procedures_SG		A Home RFSS can confirm the registration of an SG.
SIP_ISSI_Home_17_1_001SG Home Query – Failure (Serving RFSS not registered for SG) - Home
for an SG. The request is sent to the SG’s Serving RFSS. The response of the
SG’s Serving RFSS is tested in the case where the SG object is no longer being
served by this Serving RFSS (for example, the SG no longer has any affiliated
SUs in this RFSS).
Home (Multi-Segment)
to the Home RFSS.
Home rfss-id : 01
Home system-id : 001
Home wacn-id : 00001
Serving rfss-id : 02
Serving system-id : 002
Serving wacn-id : 00002
g-id of the SG : 0064
the requested SG.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_17_2_001SG Home Query – Successful (“Force” parameter enabled) - Home
In the event that the “Force” qualifier is enabled in the request to the Serving
RFSS, the response of the Serving RFSS is tested. The Serving RFSS has the
SG profile information.
Home (Multi-Segment)
this Home RFSS.
Home rfss-id : 01
Home system-id : 001
Home wacn-id : 00001
Serving rfss-id : 02
Serving system-id : 002
Serving wacn-id : 00002
g-id of the SG : 0064
Post-Conditions: Serving: 1- The Serving RFSS considers itself registered to the Home RFSS for the
requested SG.
2- The Serving RFSS subsequently initiates an SG registration to the Home
RFSS as described in test case 5.10.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_17_3_001Home Query for SG – Successful (“Confirm” parameter enabled) - Home
In the event that the “Confirm” qualifier is enabled in the request sent by the
Home RFSS, the response of the Serving RFSS is tested. The Serving RFSS
obtains active confirmation that at least one SU is affiliated to the SG.
Home (Multi-Segment)
this Home RFSS.
2- The Serving RFSS considers one or more SU(s) in the SG present and
reachable.
Home rfss-id : 01
Home system-id : 001
Home wacn-id : 00001
Serving rfss-id : 02
Serving system-id : 002
Serving wacn-id : 00002
g-id of the SG : 0064
requested SG.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_17_4_001SG Home Query – Successful (“Force”/“Confirm” parameters reset) - Home
In the event that neither the “Force” qualifier nor the “Confirm” qualifier is enabled
in the request sent by the Home RFSS to the Serving RFSS, the response of the
Serving RFSS is tested. The Serving RFSS is registered for the SG.
Applicable ISSI Conformance Test RFSS Roles: Serving, Home (to Serving),
Home (Multi-Segment)
Home RFSS.
Minimum RFSS Parameter Configuration:
Home rfss-id : 01
Home system-id : 001
Home wacn-id : 00001
Serving rfss-id : 02
Serving system-id : 002
Serving wacn-id : 00002
g-id of the SG : 0064
Post-Conditions: Serving: 1- The Serving RFSS considers itself registered to the Home RFSS for the
requested SG.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
RFSS/
HOME/
Call_Control_Confirmed_Group_Call		An SG’s RFSSs can set up a confirmed group call.
SIP_ISSI_Home_18_1_001Confirmed Group Call setup – Successful (RF Resources Available)- Home
initiates a confirmed group call.
Home (Multi-Segment)
RFSS.
Serving RFSS 1 rfss-id : 01
Serving RFSS 1 system-id : 001
Serving RFSS 1 wacn-id : 00001
Home RFSS 2 rfss-id : 02
Home RFSS 2 system-id : 002
Home RFSS 2 wacn-id : 00002
Serving RFSS 3 rfss-id : 03
Serving RFSS 3 system-id : 003
Serving RFSS 3 wacn-id : 00003
g-id of the group : 0064
specified SG.
2- The Serving RFSS has a Group call segment established with the Home
RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_18_2_001Confirmed Group Call setup – Successful (RF Resources unavailable)- Home
initiates a confirmed group call. The second Serving RFSS has no RF resources
available.
Home (Multi-Segment)
RFSS.
2- The second Serving RFSS (RFSS 3) does NOT have RF resources
available.
Serving RFSS 1 rfss-id : 01
Serving RFSS 1 system-id : 001
Serving RFSS 1 wacn-id : 00001
Home RFSS 2 rfss-id : 02
Home RFSS 2 system-id : 002
Home RFSS 2 wacn-id : 00002
Serving RFSS 3 rfss-id : 03
Serving RFSS 3 system-id : 003
Serving RFSS 3 wacn-id : 00003
g-id of the group : 0064
specified SG.
2- The Serving RFSS has a “Confirmed Group Call” RTP call segment
established with the Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
RFSS/
HOME/
Transmission_Ctrl_Confirmed_Group_Call		 After the successful setup of a confirmed group call, the conformance to the transmission control procedures for confirmed group
SIP_ISSI_Home_19_1_001Confirmed group call Voice Transmission - Successful (Serving RFSS
initiated)- Home.
SG is successful. The first Serving RFSS initiates transmission and then stops
transmitting.
Home (Multi-Segment)
RFSS.
2- The Serving RFSS has successfully established a “Confirmed Group” RTP
call segment with the Home RFSS.
Serving RFSS 1 rfss-id : any
Serving RFSS 1 system-id : any
Serving RFSS 1 wacn-id : any
Home RFSS 2 rfss-id : any
Home RFSS 2 system-id : any
Home RFSS 2 wacn-id : any
Serving RFSS 3 rfss-id : any
Serving RFSS 3 system-id : any
Serving RFSS 3 wacn-id : any
g-id of the group : any
wacn-id of the initiating SU : 00002
system-id of the initiating SU : 002
u-id of the initiating SU : 000001
transmit priority : 00
specified SG.
2- The Serving RFSS has a Group call segment established with the Home
RFSS.
3- The Serving RFSS 1 has successfully forwarded audio on the specified
call segment in accordance with its RFSS role and this test.
4- The Serving RFSS 3 has successfully received audio on the specified call
segment in accordance with its RFSS role and this test.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
RFSS/
HOME/
Advanced_RTP_Resource_Management
SIP_ISSI_Home_20_1_001Group call setup – Successful (Home RFSS RTP resources initially
unavailable)- Home.
RFSS of the SG. The Home RFSS has no RTP resources available so it cannot
set up the RTP session, but it accepts setting up the SIP session. Later, RTP
resources become available at the SG’s Home RFSS which triggers an RTP
session setup from the SG’s Home RFSS.
Home (Multi-Segment)
RFSS.
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
g-id of the group : 0064
specified SG.
2- The Serving RFSS has an RTP call segment established with the Home
RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_20_2_001Group call setup – Successful (Serving RFSS RTP resources initially unavailable)- Home
unconfirmed (or a confirmed) group call with a Serving RFSS. The Serving RFSS
has no RTP resources available at the beginning of the test so it cannot set up
the RTP session, but it accepts setting up the SIP session. Later, RTP resources
at the Serving RFSS become available which triggers an RTP session setup from
the Serving RFSS to the Home RFSS.
Home (Multi-Segment
RFSS.
2- The Serving RFSS does NOT have RTP resources available for the call.
Home rfss-id : 01
Home system-id : 001
Home wacn-id : 00001
Serving rfss-id : 02
Serving system-id : 002
Serving wacn-id : 00002
g-id of the group : 0064
specified SG.
2- The Serving RFSS has an RTP call segment established with the Home
RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_20_3_001Confirmed group call setup – Successful (Serving RFSS RF resources
initially unavailable)- Home.
registered for the SG. The SG’s Serving RFSS has no RF resources available.
Later, the Serving RFSS has available RF resources which triggers a SIP INVITE
to the Home RFSS.
Home (Multi-Segment)
applicable SG.
2- The Serving RFSS does NOT have RF resources available for the call.
Home rfss-id : 01
Home system-id : 001
Home wacn-id : 00001
Serving rfss-id : 02
Serving system-id : 002
Serving wacn-id : 00002
g-id of the group : 0064
specified SG.
2- The Serving RFSS has an RTP call segment established with the Home
RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_20_4_001Modification of priority for a group call initiated by a Home RFSS- Home
Home RFSS and a Serving RFSS is successful. The SG’s Home RFSS modifies
the priority of the group call such that it becomes an emergency group call.
Home (Multi-Segment)
Home rfss-id : 01
Home system-id : 001
Home wacn-id : 00001
Serving rfss-id : 02
Serving system-id : 002
Serving wacn-id : 00002
g-id of the group : 0064
RFSS.
2- The Serving RFSS considers the priority of the established group call
segment with the Home RFSS to be “emergency”.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_20_5_001Modification of priority for a group call by a Serving RFSS- Home
Home RFSS and a Serving RFSS is successful. The SG’s Serving RFSS
modifies the priority of the group call such that it becomes an emergency group
call.
Home (Multi-Segment)
RFSS.
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
g-id of the group : 0064
RFSS.
2- The Serving RFSS considers the priority of the established group call
segment with the Home RFSS to be “emergency”.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_20_6_001Group call setup: Home RFSS RTP resources initially available and finally unavailable- Home
Serving RFSS. The Serving RFSS has RTP resources available so the setup is
successful. Later, RTP resources become unavailable at the Home RFSS.
Applicable ISSI Conformance Test RFSS Roles: Serving, Home (to Serving),
Home (Multi-Segment)
Home rfss-id : 01
Home system-id : 001
Home wacn-id : 00001
Serving rfss-id : 02
Serving system-id : 002
Serving wacn-id : 00002
g-id of the group : 0064
RFSS.
2- The Serving RFSS still has the SIP session relative to the initial group call
segment setup with the Home RFSS.
3- The Serving RFSS does NOT have an RTP group call segment
established with the Home RFSS for the specified SIP session.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_20_7_001Group call setup : Serving RFSS RTP resources initially available and finally unavailable- Home
group call with the SG’s Home RFSS. The Home RFSS has RTP resources
available so the setup is successful. Later, RTP resources become unavailable
at the Serving RFSS.
Home (Multi-Segment)
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
g-id of the group : 0064
RFSS.
2- The Serving RFSS still has the SIP session relative to the initial group call
segment set up with the Home RFSS.
3- The Serving RFSS does NOT have an RTP group call segment
established with the Home RFSS with regards to the specified SIP
session.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Home_20_8_001SIP Heartbeat (Group call)- Home
between the Home RFSS and the Serving RFSS for the SG is successfully set
up but no RTP session between the two RFSSs is set up.
Home (Multi-Segment)
RFSS.
2- The Serving RFSS has established a SIP session with the Home RFSS.
3- The Serving RFSS does NOT have an RTP group call segment
established with the Home RFSS for the specified SIP session.
Home rfss-id : 01
Home system-id : 001
Home wacn-id : 00001
Serving rfss-id : 02
Serving system-id : 002
Serving wacn-id : 00002
g-id of the group : 0064
RFSS.
2- The Serving RFSS still has the SIP session relative to the initial group call
segment set up with the Home RFSS.
3- The Serving RFSS does NOT have an RTP group call segment
established with the Home RFSS with regards to the specified SIP
session.
4- The Serving RFSS has successfully received the SIP Heartbeat message
from the Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
RFSS/
SERVING		Tests that test a Serving RFSS
RFSS/
SERVING/
Individual_SU_Registration_Procs		These tests demonstrate that a mobility object (SU) can be registered in a
SIP_ISSI_Serving_4_1_001SU Registration - Successful (SU presence confirmed) - Serving
An event occurs in a Serving RFSS which triggers an ISSI SU registration
procedure. The SU is subsequently registered with its Home RFSS via a Serving RFSS.
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
u-id of the SU : 000011

User Action: SU to send Register
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_4_2_001SU Registration - Successful (SU presence not confirmed) - Serving
A Serving RFSS currently registered with the Home RFSS for a specified SU,
initiates the ISSI SU registration procedure for that SU with the presence of the
SU not confirmed. Upon completion of the test, the Serving RFSS is still
registered with the Home RFSS for the specified SU.
Home (Multi-Segment)
SU.
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
u-id of the SU : 000011

User Action: SU to send Register
specified SU.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_4_3_001SU Registration - Unsuccessful (Target RFSS is not home to the SU, SU presence confirmed) - Serving
procedure. The request of the Serving RFSS is sent to a Home RFSS that is not
home to the specified SU.
confirmed.
Home (Multi-Segment)
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
u-id of the SU : 000011

User Action: SU to send Register
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_4_3_002SU Registration - Unsuccessful (Target RFSS is not home to the SU, SU presence not confirmed) - Serving
procedure. The request of the Serving RFSS is sent to a Home RFSS that is not
home to the specified SU.
confirmed.
NOTE – the field “r-presence” is absent or set to "not confirmed".
Home (Multi-Segment)
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
u-id of the SU : 000011

User Action: SU to send Register
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_4_4_001SU Registration – Unsuccessful (Denied by Home RFSS, SU presence confirmed) - Serving
for the SU. The request of the Serving RFSS is sent to the Home RFSS which
denies registration of the SU due to local policy.
confirmed.
Home (Multi-Segment)
the Serving RFSS.
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
u-id of the SU : 000011
specified SU.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_4_4_002SU Registration – Unsuccessful (Denied by Home RFSS, SU presence not confirmed) - Serving
for the SU. The request of the Serving RFSS is sent to the Home RFSS which
denies registration of the SU due to local policy.
confirmed.
Home (Multi-Segment)
the Serving RFSS.
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
u-id of the SU : 000011
specified SU.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_4_5_001SU Registration – Unsuccessful (SU presence confirmation not required) - Serving
not confirmed for the SU. The request of the Serving RFSS is sent to the Home
RFSS which rejects it because the Home RFSS believes the SU is currently
registered to a different RFSS than the registering RFSS.
Home (Multi-Segment)
RFSS than the registering RFSS.
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
u-id of the SU : 000011
RFSS than the registering RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
RFSS/
SERVING/
Group_Registration_Procs		These tests demonstrate that a mobility object (SG) can be registered in a
SIP_ISSI_Serving_5_1_001SG Registration – Successful - Serving
An event in a Serving RFSS triggers an SG registration from the Serving RFSS
to the SG’s Home RFSS.
Home (Multi-Segment)
specified SG
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
g-id of the group : 0064

User Action: SU to send Register
SG.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_5_2_001SG Registration – Unsuccessful (Target RFSS not Home to the SG) - Serving
RFSS 1 attempts to register for an SG. The target RFSS specified in the
registration message (RFSS 2) is not configured to be the home of the SG.
RFSS 2 responds to RFSS 1 with the appropriate failure response.
Home (Multi-Segment)
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
g-id of the group : 0064

User Action: SU to send Register
specified SG.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_5_3_001SG Registration – Unsuccessful (Denied by Home RFSS) - Serving
An event in a Serving RFSS triggers an SG registration from the Serving RFSS
to the SG s Home RFSS. The SG s Home RFSS disallows the SG registration
with the appropriate error message.
Home (Multi-Segment)
SG by the Serving RFSS.
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
g-id of the group : 0064

User Action: SU to send Register
specified SG.
2- The Home RFSS considers itself NOT home to the specified SG.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
RFSS/
SERVING/
Individual_SU_De_Registration_Procs		These tests demonstrate that a mobility object (SU) can be de-registered in a
SIP_ISSI_Serving_6_1_001SU De-registration – Successful (Serving RFSS initiated) - Serving
An event triggers a Serving RFSS to de-register an SU from the SU’s Home
RFSS.
Home (Multi-Segment)
SU.
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
u-id of the SU : 000011

User Action: Event to trigger Serving to send De-Register
specified SU.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_6_2_001SU De-registration – Successful (Home RFSS initiated) - Serving
An event triggers a Home RFSS to de-register an SU from a Serving RFSS.
Home (Multi-Segment)
SU.
Home rfss-id : 01
Home system-id : 001
Home wacn-id : 00001
Serving rfss-id : 02
Serving system-id : 002
Serving wacn-id : 00002
u-id of the SU : 000011

User Action: none
specified SU.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_6_3_001SU De-registration – (Serving RFSS not allowed) - Serving
An event within the Serving RFSS triggers the de-registration message to be
sent to the Home RFSS of the SU. However, the Home RFSS of the SU no
longer considers the SU as being registered with the Serving RFSS and
responds with the appropriate error message.
Home (Multi-Segment)
specified SU.
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
u-id of the SU : 000011

User Action: Event to trigger Serving to send De-Register
specified SU.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
RFSS/
SERVING/
Group_De_registration_Procs		These tests demonstrate that a mobility object (SG) can be de-registered in a
SIP_ISSI_Serving_7_1_001SG De-registration – Successful (Serving RFSS initiated) - Serving
An event within a Serving RFSS initiates the de-registration for an SG to the
SG’s Home RFSS.
Home (Multi-Segment)
SG.
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
g-id of the group : 0064

User Action: Event to trigger Serving to send De-Register
specified SG.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_7_2_001SG De-registration – (Serving RFSS not allowed) - Serving
An event triggers a Serving RFSS to de-register an SG from the SG’s Home
RFSS. The SG’s Home RFSS does not consider the SG to be registered in the
Serving RFSS and responds with the appropriate error message.
Home (Multi-Segment)
specified SG.
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
g-id of the group : 0064

User Action: Generate an event to trigger Serving to send De-Register
specified SG.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
RFSS/
SERVING/
SU_Individual_Roamed_Procs		To demonstrate that a mobility object (SU) in a Serving RFSS can roam to
SIP_ISSI_Serving_8_1_001SU Roamed procedure - Successful (Home initiated) - Serving
A Serving RFSS is registered for a specified SU. An event within the SU’s Home
RFSS triggers the roamed procedure from the Home RFSS to the Serving RFSS.
Home (Multi-Segment)
SU.
Home rfss-id : 01
Home system-id : 001
Home wacn-id : 00001
Serving rfss-id : 02
Serving system-id : 002
Serving wacn-id : 00002
u-id of the SU : 000011

User Action: None
specified SU.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_8_2_001SU Roamed Procedure – (Serving RFSS Not Registered for SU) - Serving
A Serving RFSS is registered for an SU with the Home RFSS. At some point, the
Serving RFSS believes it no longer has the SU registered in its serving domain.
After a triggering event, the Home RFSS initiates a roamed procedure for the SU.
The request from the Home RFSS is sent to the initial Serving RFSS which has
no reference to the SU in its serving domain.
Home (Multi-Segment)
SU.
Home rfss-id : 01
Home system-id : 001
Home wacn-id : 00001
Serving rfss-id : 02
Serving system-id : 002
Serving wacn-id : 00002
u-id of the SU : 000011

User Action: None
specified SU.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
RFSS/
SERVING/
Call_Setup_Unconfirmed_Group_Call		An RFSS can set up an unconfirmed group call for a specified SG.
SIP_ISSI_Serving_9_1_001Group call setup – Successful - Serving
Serving RFSSs triggers it to initiate an unconfirmed group call.
Home (Multi-Segment)
Serving RFSS 1 rfss-id : 01
Serving RFSS 1 system-id : 001
Serving RFSS 1 wacn-id : 00001
Home RFSS 2 rfss-id : 02
Home RFSS 2 system-id : 002
Home RFSS 2 wacn-id : 00002
Serving RFSS 3 rfss-id : 03
Serving RFSS 3 system-id : 003
Serving RFSS 3 wacn-id : 00003
g-id of the group : 0064

User Action: Generate event within one of the Serving RFSSs triggers it to initiate an unconfirmed group call.
specified SG. 2- The Home RFSS has an “Unconfirmed Group Call” RTP call segment
established with the Serving RFSS(s).
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_9_1_002Group call setup – Successful - Serving
Serving RFSSs triggers it to initiate an unconfirmed group call.
Home (Multi-Segment)
Serving RFSS 1 rfss-id : 01
Serving RFSS 1 system-id : 001
Serving RFSS 1 wacn-id : 00001
Home RFSS 2 rfss-id : 02
Home RFSS 2 system-id : 002
Home RFSS 2 wacn-id : 00002
Serving RFSS 3 rfss-id : 03
Serving RFSS 3 system-id : 003
Serving RFSS 3 wacn-id : 00003
g-id of the group : 0064

User Action: Generate event within one of the Serving RFSSs triggers it to initiate an unconfirmed group call.
specified SG. 2- The Home RFSS has an “Unconfirmed Group Call” RTP call segment
established with the Serving RFSS(s).
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_9_2_001Group call setup – Unsuccessful (Forbidden by the Home RFSS, SG
not registered) - Serving.
RFSS is no longer registered for the SG. The Serving RFSS initiates an
unconfirmed group call request to the SG’s Home RFSS. The Home RFSS
responds to the request with an appropriate error message.
Applicable ISSI Conformance Test RFSS Roles: Serving, Home (to Serving),
Home (Multi-Segment)
specified SG.
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
g-id of the group : 0064

User Action: Generate event within one of the Serving RFSSs triggers it to initiate an unconfirmed group call.
2- The Home RFSS does NOT have an RTP call segment established with
the Serving RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_9_3_001Group call setup – Unsuccessful (SG not known to the Home RFSS) - Serving
NOT home to the SG. The Serving RFSS initiates an unconfirmed group call
request to the non-Home RFSS. The non-Home RFSS responds with an
appropriate error message.
Home (Multi-Segment)
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
g-id of the group : 0064

User Action: Generate event within one of the Serving RFSSs triggers it to initiate an unconfirmed group call.
2- The Home RFSS does NOT have an RTP call segment established with
the Serving RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_9_4_001Group call setup – Unsuccessful (SG not known to Serving RFSS) - Serving
invites one of the SG’s Serving RFSSs to join the group call but the SG is no
longer known in that Serving RFSS.
Home (Multi-Segment)
SG.
Home rfss-id : 01
Home system-id : 001
Home wacn-id : 00001
Serving rfss-id : 02
Serving system-id : 002
Serving wacn-id : 00002
g-id of the group : 0064

User Action: none
2- The Home RFSS does NOT have an RTP call segment established with
the Serving RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_9_5_001Group Call setup - Successful (Two RFSS with call request having
equal priority) - Serving.
and the Home RFSS initiate an unconfirmed group call for the same SG with
equal priorities.
Home (Multi-Segment)
SG.
Serving RFSS 1 rfss-id : 01
Serving RFSS 1 system-id : 001
Serving RFSS 1 wacn-id : 00001
Home RFSS 2 rfss-id : 02
Home RFSS 2 system-id : 002
Home RFSS 2 wacn-id : 00002
Serving RFSS 3 rfss-id : 03
Serving RFSS 3 system-id : 003
Serving RFSS 3 wacn-id : 00003
g-id of the group : 0064
priority of the call request initiated by the RFSS 1, RFSS 2, RFSS 3 : 8;a

User Action: Serving RFSS initiates an unconfirmed group call for the SG
2- The Home RFSS has established a group call segment with the Serving
RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_9_5_002Group Call setup - Successful (Two RFSS with call request having
equal priority) - Serving.
and the Home RFSS initiate an unconfirmed group call for the same SG with
equal priorities.
Home (Multi-Segment)
SG.
Serving RFSS 1 rfss-id : 01
Serving RFSS 1 system-id : 001
Serving RFSS 1 wacn-id : 00001
Home RFSS 2 rfss-id : 02
Home RFSS 2 system-id : 002
Home RFSS 2 wacn-id : 00002
Serving RFSS 3 rfss-id : 03
Serving RFSS 3 system-id : 003
Serving RFSS 3 wacn-id : 00003
g-id of the group : 0064
priority of the call request initiated by the RFSS 1, RFSS 2, RFSS 3 : 8;a

User Action: Serving RFSS initiates an unconfirmed group call for the SG
2- The Home RFSS has established a group call segment with the Serving
RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_9_6_001Group Call setup – Successful (Two RFSS with call request having
different priority) - Serving.
time the SG’s Serving RFSS and the SG’s Home RFSS initiate an unconfirmed
group call for the SG. The SU in the Home RFSS’s call request has a lower
priority than the Serving RFSS’s call request.
Applicable ISSI Conformance Test RFSS Roles: Serving, Home (to Serving),
Home (Multi-Segment)
Serving RFSS 1 rfss-id : 01
Serving RFSS 1 system-id : 001
Serving RFSS 1 wacn-id : 00001
Home RFSS 2 rfss-id : 02
Home RFSS 2 system-id : 002
Home RFSS 2 wacn-id : 00002
Serving RFSS 3 rfss-id : 03
Serving RFSS 3 system-id : 003
Serving RFSS 3 wacn-id : 00003
g-id of the group : 0064
priority of the call request initiated by Serving RFSS 1 and Home RFSS 2: 8;a
priority of the call request initiated by Serving RFSS 3: 10;a

User Action: Serving RFSS initiates an unconfirmed group call for the SG
2- The Serving RFSS has established a group call segment with the Home
RFSS for the higher priority request.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_9_6_002Group Call setup – Successful (Two RFSS with call request having
different priority) - Serving.
time the SG’s Serving RFSS and the SG’s Home RFSS initiate an unconfirmed
group call for the SG. The SU in the Home RFSS’s call request has a lower
priority than the Serving RFSS’s call request.
Applicable ISSI Conformance Test RFSS Roles: Serving, Home (to Serving),
Home (Multi-Segment)
Serving RFSS 1 rfss-id : 01
Serving RFSS 1 system-id : 001
Serving RFSS 1 wacn-id : 00001
Home RFSS 2 rfss-id : 02
Home RFSS 2 system-id : 002
Home RFSS 2 wacn-id : 00002
Serving RFSS 3 rfss-id : 03
Serving RFSS 3 system-id : 003
Serving RFSS 3 wacn-id : 00003
g-id of the group : 0064
priority of the call request initiated by Serving RFSS 1 and Home RFSS 2: 8;a
priority of the call request initiated by Serving RFSS 3: 10;a

User Action: Serving RFSS initiates an unconfirmed group call for the SG
2- The Serving RFSS has established a group call segment with the Home
RFSS for the higher priority request.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_9_7_001Group Call setup – Group Call setup – Unsuccessful (Canceled by Home RFSS) - Serving
RFSS initiates and then cancels an unconfirmed group call.
Home (Multi-Segment).
essentially equivalent can be provided via the BYE message. Accordingly, a
Home RFSS which does not support the CANCEL functionality in this test may
still be claimed as conformant to this PCP. This test is deemed “Not Applicable”
to such a Home RFSS.
such a case, this test becomes not applicable.
Home rfss-id : 01
Home system-id : 001
Home wacn-id : 00001
Serving rfss-id : 02
Serving system-id : 002
Serving wacn-id : 00002
g-id of the group : 0064

User Action: none
2- The Home RFSS does NOT have an unconfirmed group call segment
established with the Serving RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_9_8_001Group call setup – Unsuccessful (Canceled by Serving RFSS) - Serving
RFSS initiates and then cancels an unconfirmed group call.
Home (Multi-Segment)
essentially equivalent can be provided via the BYE message. Accordingly, a
Serving RFSS which does not support the CANCEL functionality in this test may
still be claimed as conformant to this PCP. This test is deemed “Not Applicable”
to such a Serving RFSS.
a case, this test becomes not applicable.
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
g-id of the group : 006

User Action: Serving RFSS initiates and then cancels an unconfirmed group call.
2- The Home RFSS does NOT have the specified unconfirmed group call
segment established with the Serving RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_9_9_001Group Call setup – Successful (Protected mode
requested) - Serving.
initiates a group call.
considered SG, and the calling SU requests the protected mode. In this
case, the call is setup with the protected option.
Applicable ISSI Conformance Test RFSS Roles: Serving, Home (to Serving),
Home (Multi-Segment)
requested SG.
2- The Home RFSS is configured to accept or not the protected mode for the
considered SG depending on the considered test case.
Serving RFSS 1 rfss-id : 01
Serving RFSS 1 system-id : 001
Serving RFSS 1 wacn-id : 00001
Home RFSS 2 rfss-id : 02
Home RFSS 2 system-id : 002
Home RFSS 2 wacn-id : 00002
Serving RFSS 3 rfss-id : 03
Serving RFSS 3 system-id : 003
Serving RFSS 3 wacn-id : 00003
g-id of the group : 0064

User Action: 1st Serving RFSS initiates a group call.
specified SG.
2- The Home RFSS has a Group call segment established in protected mode
with the Serving RFSS(s)
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_9_9_002Group Call setup – Successful (Protected mode
requested) - Serving.
initiates a group call.
considered SG, and the calling SU requests the protected mode. In this
case, the call is setup with the protected option.
Applicable ISSI Conformance Test RFSS Roles: Serving, Home (to Serving),
Home (Multi-Segment)
requested SG.
2- The Home RFSS is configured to accept or not the protected mode for the
considered SG depending on the considered test case.
Serving RFSS 1 rfss-id : 01
Serving RFSS 1 system-id : 001
Serving RFSS 1 wacn-id : 00001
Home RFSS 2 rfss-id : 02
Home RFSS 2 system-id : 002
Home RFSS 2 wacn-id : 00002
Serving RFSS 3 rfss-id : 03
Serving RFSS 3 system-id : 003
Serving RFSS 3 wacn-id : 00003
g-id of the group : 0064

User Action: 1st Serving RFSS initiates a group call.
specified SG.
2- The Home RFSS has a Group call segment established in protected mode
with the Serving RFSS(s)
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_9_9_003Group Call setup – Successful (Protected mode
requested) - Serving.
initiates a group call.
considered SG, and the calling SU requests the unprotected mode. In this
case, the call is setup with the unprotected option.
Applicable ISSI Conformance Test RFSS Roles: Serving, Home (to Serving),
Home (Multi-Segment)
requested SG.
2- The Home RFSS is configured to accept or not the protected mode for the
considered SG depending on the considered test case.
Serving RFSS 1 rfss-id : 01
Serving RFSS 1 system-id : 001
Serving RFSS 1 wacn-id : 00001
Home RFSS 2 rfss-id : 02
Home RFSS 2 system-id : 002
Home RFSS 2 wacn-id : 00002
Serving RFSS 3 rfss-id : 03
Serving RFSS 3 system-id : 003
Serving RFSS 3 wacn-id : 00003
g-id of the group : 0064

User Action: Serving RFSS 1 initiates a group call.
specified SG.
2- The Home RFSS has a Group call segment established in unprotected mode
with the Serving RFSS(s)
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_9_9_004Group Call setup – Successful (Protected mode
requested) - Serving.
initiates a group call.
considered SG, and the calling SU requests the unprotected mode. In this
case, the call is setup with the unprotected option.
Applicable ISSI Conformance Test RFSS Roles: Serving, Home (to Serving),
Home (Multi-Segment)
requested SG.
2- The Home RFSS is configured to accept or not the protected mode for the
considered SG depending on the considered test case.
Serving RFSS 1 rfss-id : 01
Serving RFSS 1 system-id : 001
Serving RFSS 1 wacn-id : 00001
Home RFSS 2 rfss-id : 02
Home RFSS 2 system-id : 002
Home RFSS 2 wacn-id : 00002
Serving RFSS 3 rfss-id : 03
Serving RFSS 3 system-id : 003
Serving RFSS 3 wacn-id : 00003
g-id of the group : 0064

User Action: Serving RFSS 1 initiates a group call.
specified SG.
2- The Home RFSS has a Group call segment established in unprotected mode
with the Serving RFSS(s)
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_9_10_001Group call setup – Unsuccessful (Protected audio call
cannot be granted) - Serving.
pass the test:
1- The calling SU requests the protected mode and the Home RFSS is
configured to refuse the protected mode for the considered SG.
Only the first case is described in section 9.10.5. In the second case, the cprotected
parameter is set to 0 and the p-25-condition-code and P25-conditiontext
in the 403 Forbidden message will be set to “2C” and "Unprotected audio call
not granted", respectively.
requested SG.
2- The Home RFSS is configured to refuse the protected mode for the considered SG depending on the considered
test case.
Serving RFSS 1 rfss-id : 01
Serving RFSS 1 system-id : 001
Serving RFSS 1 wacn-id : 00001
Home RFSS 2 rfss-id : 02
Home RFSS 2 system-id : 002
Home RFSS 2 wacn-id : 00002
g-id of the group : 0064

User Action: Serving RFSS initiates a group call.
SG.
2- The Home RFSS does NOT have the specified group call segment
established with the Serving RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_9_10_002Group call setup – Unsuccessful (Protected audio call
cannot be granted) - Serving.
pass the test:
2- The calling SU requests the unprotected mode and the Home RFSS is
configured to refuse the unprotected mode for the considered SG.
Only the first case is described in section 9.10.5. In the second case, the cprotected
parameter is set to 0 and the p-25-condition-code and P25-conditiontext
in the 403 Forbidden message will be set to “2C” and "Unprotected audio call
not granted", respectively.
requested SG.
2- The Home RFSS is configured to refuse the unprotected mode for the considered SG depending on the considered
test case.
Serving RFSS 1 rfss-id : 01
Serving RFSS 1 system-id : 001
Serving RFSS 1 wacn-id : 00001
Home RFSS 2 rfss-id : 02
Home RFSS 2 system-id : 002
Home RFSS 2 wacn-id : 00002
g-id of the group : 0064

User Action: Serving RFSS initiates a group call.
SG.
2- The Home RFSS does NOT have the specified group call segment
established with the Serving RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
RFSS/
SERVING/
Call_Teardown_Group_Call
SIP_ISSI_Serving_10_1_001Group Call Teardown - Successful (Triggered by Serving RFSS) - Serving
RFSS initiates a group call. The SG’s Serving RFSS terminates the group call
segment with the Home RFSS due to loss of RTP connectivity or local policy.
Home (Multi-Segment)
2- The Home RFSS has established a group call segment with the Serving
RFSS.
Serving rfss-id : 01
Serving system-id : 001
Serving wacn-id : 00001
Home rfss-id : 02
Home system-id : 002
Home wacn-id : 00002
g-id of the group : 0064

User Action: Serving RFSS teardowns a group call.
2- The Home RFSS does NOT have the specified call segment established
with the Serving RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_10_2_001Group Call Teardown - Successful (Triggered by Serving RFSS) - Serving
RFSS successfully initiates a group call. After the setup, the SG’s Home RFSS
terminates the group call segment with the SG’s Serving RFSS due to ISSI
hangtime expiry, loss of RTP connectivity with the SG’s serving RFSS or local
policy.
Home (Multi-Segment)
2- The Home RFSS has established a group call segment with the Serving
RFSS.
Home rfss-id : 01
Home system-id : 001
Home wacn-id : 00001
Serving rfss-id : 02
Serving system-id : 002
Serving wacn-id : 00002
g-id of the group : 0064

User Action: Serving RFSS sets up initial group call.
2- The Home RFSS does NOT have the specified call segment established
with the Serving RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
RFSS/
SERVING/
Basic_Group_Call_Trans_Ctrl_Procs		After the setup of an unconfirmed group call, the conformance to the basic
SIP_ISSI_Serving_11_1_001Group call transmission – Successful (Serving RFSS starts and stops
talk spurt) - Serving.
Serving RFSSs. One Serving RFSS initiates transmission (talk spurts) and then
stops transmitting. The audio is successfully transmitted through the Home
RFSS and to the other Serving RFSS.
Home (Multi-Segment)
2- The Home RFSS has established a group call segment with the Serving
RFSS(s).
3- The Home RFSS is idle with respect to sending ISSI voice traffic on this
call segment.
Serving RFSS 1 rfss-id : any
Serving RFSS 1 system-id : any
Serving RFSS 1 wacn-id : any
Home RFSS 2 rfss-id : any
Home RFSS 2 system-id : any
Home RFSS 2 wacn-id : any
Serving RFSS 3 rfss-id : any
Serving RFSS 3 system-id : any
Serving RFSS 3 wacn-id : any
g-id of the group : any
wacn-id of the initiating SU : 00002
system-id of the initiating SU : 002
u-id of the initiating SU : 000001
transmit priority : 00
g-id of the group : 0064

User Action: One Serving RFSS initiates transmission (talk spurts)
2- The Home RFSS continues to have the specified call segment established
with the Serving RFSS(s).
3- The Home RFSS has successfully received audio on the specified call
segment in accordance with its RFSS role and this test.
4- The Home RFSS has successfully forwarded audio on the specified call
segment in accordance with its RFSS role and this test.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_11_2_001Group call transmission – Unsuccessful (Denied by Home RFSS) - Serving
RFSS denies the transmission.
Home (Multi-Segment)
essential to the transmission control capabilities of the RFSS. Accordingly, a
Home RFSS which does not generate the Deny message as described in this
test may still be claimed as conformant to this PCP. This test is deemed “Not
Applicable” to such a Home RFSS.
2- The Home RFSS has established a group call segment with the Serving
RFSS. 3- The Home RFSS is idle with respect to sending ISSI voice traffic on this
call segment.
Serving rfss-id : any
Serving system-id : any
Serving wacn-id : any
Home rfss-id : any
Home system-id : any
Home wacn-id : any
g-id of the group : any
wacn-id of the initiating SU : 00002
system-id of the initiating SU : 002
u-id of the initiating SU: 000001
transmit priority : 00

User Action: a Serving RFSS initiates/attempts transmission (talk spurts)
2- The Home RFSS has the specified call segment established with the
Serving RFSS.
3- The Home RFSS is idle with respect to sending ISSI voice traffic on this
call segment.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_11_3_001Group call Mute and Unmute – Successful (Home RFSS initiated) - Serving
RFSS. The Serving RFSS starts transmitting and after a while, the Home RFSS
mutes and then unmutes the transmission. The purpose of this test is to check
that the first Serving RFSS stops sending audio when the Home RFSS sends a
Mute request and resumes transmitting audio when the Home RFSS sends an
Unmute request.
Home (Multi-Segment)
necessarily essential to the transmission control capabilities of an RFSS.
Accordingly, a Home RFSS which does not generate the Mute Request in this
test may still be claimed as conformant to this PCP. This test is deemed “Not
Applicable” to such a Home RFSS.
2- The Home RFSS has established a group call segment with the Serving
RFSS(s).
3- The Home RFSS is idle with respect to sending ISSI voice traffic.
Serving rfss-id : any
Serving system-id : any
Serving wacn-id : any
Home rfss-id : any
Home system-id : any
Home wacn-id : any
g-id of the group : any
wacn-id of the initiating SU : 00002
system-id of the initiating SU : 002
u-id of the initiating SU : 000001
transmit priority : 00

User Action: none
2- The Home RFSS still has the specified call segment established with the
Serving RFSS(s).
3- The Home RFSS has successfully received audio on the specified call
segment in accordance with its RFSS role and this test.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_11_4_001Group call Mute and Unmute – Successful (Serving RFSS initiated) - Serving
RFSS. The Home RFSS starts transmitting from one SU and after a while, the
Serving RFSS mutes and unmutes the transmission. The purpose of this test is
to check that the Home RFSS stops sending audio when the Serving RFSS
sends a Mute request and resumes transmitting audio when the Serving RFSS
sends an Unmute request.
Home (Multi-Segment)
essential to the transmission control capabilities of the RFSS. Accordingly, a
Serving RFSS which does not generate the Mute message as described in this
test may still be claimed as conformant to this PCP. This test is deemed “Not
Applicable” to such a Serving RFSS.
2- The Home RFSS has established a group call segment with the Serving
RFSS.
3- The Home RFSS is idle with respect to sending ISSI voice traffic.
Home rfss-id : any
Home system-id : any
Home wacn-id : any
Serving rfss-id : any
Serving system-id : any
Serving wacn-id : any
g-id of the group : any
wacn-id of the initiating SU : 00002
system-id of the initiating SU : 002
u-id of the initiating SU : 000001
transmit priority : 00

User Action: a Serving RFSS sends a Mute request and then an unmute request
2- The Home RFSS still has the specified call segment established with the
Serving RFSS.
3- The Home has successfully stopped sending audio and then re-started
sending audio when the Serving RFSS told it to mute an active
transmission and later to unmute the same transmission.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_11_5_001Heartbeat – Successful - Serving
RTP session is set up for the unconfirmed group call relative to the SG. The SG’s
Home RFSS and the SG’s Serving RFSS send RTP Heartbeats periodically.
Home (Multi-Segment)
2- The Home RFSS has established a group call segment with the Serving
RFSS.
3- The Home RFSS is idle with respect to sending ISSI voice traffic.
Serving rfss-id : any
Serving system-id : any
Serving wacn-id : any
Home rfss-id : any
Home system-id : any
Home wacn-id : any
g-id of the group : any

User Action: a Serving RFSS sends Heartbeats periodically
2- The Home RFSS still has the specified call segment established with the
Serving RFSS.
3- The Home RFSS has successfully received the Serving RTP Heartbeat
message on the specified call segment.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_11_6_001Heartbeat Query – Successful (Serving RFSS initiated) - Serving
RTP session is set up for the unconfirmed group call relative to the SG. The SG’s
Serving RFSS sends a Heartbeat Query to the SG’s Home RFSS. The purpose
of this test is to verify that the Home RFSS correctly responds to a Heartbeat
Query message.
Home (Multi-Segment).
RFSS, and is not necessarily essential to the transmission control capabilities of
the RFSS. Accordingly, a Serving RFSS which does not generate the Heartbeat
Query message as described in this test may still be claimed as conformant to
this PCP. This test is deemed “Not Applicable” to such a Serving RFSS.
2- The Home RFSS has established a group call segment with the Serving
RFSS.
3- The Home RFSS is idle with respect to sending ISSI voice traffic.
Serving rfss-id : any
Serving system-id : any
Serving wacn-id : any
Home rfss-id : any
Home system-id : any
Home wacn-id : any
g-id of the group : any

User Action: a Serving RFSS sends Heartbeat Query Message
2- The Home RFSS still has the specified call segment established with the
Serving RFSS.
3- The Home RFSS has successfully received the Serving RTP Heartbeat
Query message on the specified call segment.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_11_7_001Heartbeat Query – Successful (Home RFSS initiated) - Serving
RTP session is set up for the unconfirmed group call relative to the SG.
Immediately after the establishment of the RTP session, the SG’s Home RFSS is
required to send a Heartbeat Query to the SG’s Serving RFSS.
Home (Multi-Segment)
2- The Home RFSS has established a group call segment with the Serving
RFSS.
3- The Home RFSS is idle with respect to sending ISSI voice traffic.
Home rfss-id : any
Home system-id : any
Home wacn-id : any
Serving rfss-id : any
Serving system-id : any
Serving wacn-id : any
g-id of the group : any

User Action: none
2- The Home RFSS still has the specified call segment established with the
Serving RFSS.
3- The Home RFSS has successfully received the Serving RTP Heartbeat
response message on the specified call segment.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_11_8_001Group Call transmission – Successful (Without PTT Transmit Request
at the beginning) - Serving.
RFSSs is successful. The first Serving RFSS sends multiple PTT Transmit
Progress messages with no request at the beginning of the talk-spurt, and then
stops transmitting.
Home (Multi-Segment)
Request message is optional, and is not necessarily essential to the transmission
control capabilities of the Serving RFSS. Accordingly, a Serving RFSS which
does not generate the PTT Transmit Progress message as described in this test
may still be claimed as conformant to this PCP. This test is deemed “Not
Applicable” to such a Serving RFSS.
2- The Home RFSS has established a group call segment with the Serving
RFSS(s).
3- The Home RFSS is idle with respect to sending ISSI voice traffic.
Serving RFSS 1 rfss-id : any
Serving RFSS 1 system-id : any
Serving RFSS 1 wacn-id : any
Home RFSS 2 rfss-id : any
Home RFSS 2 system-id : any
Home RFSS 2 wacn-id : any
Serving RFSS 3 rfss-id : any
Serving RFSS 3 system-id : any
Serving RFSS 3 wacn-id : any
g-id of the group : any
wacn-id of the initiating SU : 00002
system-id of the initiating SU : 002
u-id of the initiating SU : 000001
transmit priority : 00

User Action: First Serving RFSS send multiple PTT Transmit Progress messages.
2- The Home RFSS still has the specified call segment established with the
Serving RFSS.
3- The Home RFSS has successfully received audio on the specified call
segment in accordance with its RFSS role and this test.
4- The Home RFSS has successfully forwarded audio on the specified call
segment in accordance with its RFSS role and this test.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_11_9_001Group call transmissions – Successful (with losing audio) - Serving
RFSS. The Home RFSS starts transmitting from one SU and after a while, the
Home RFSS starts transmitting from a second SU with a higher priority. The
purpose of this test is to check that the losing audio bit is enabled in the first
group call messages during the second group call transmission.
Home (multi-segment)
not necessarily essential to the transmission control capabilities of the Home
RFSS. Accordingly, a Home RFSS which does not allow simultaneous voice
transmissions on a group as described in this test may still be claimed as
conformant to this PCP. This test is deemed “Not Applicable” to such a Home
RFSS.
2- The Home RFSS has established a group call segment with the Serving
RFSS.
3- The Home RFSS is idle with respect to sending ISSI voice traffic.
Minimum RFSS Parameter Configuration :
Home rfss-id : any
Home system-id : any
Home wacn-id : any
Serving rfss-id : any
Serving system-id : any
Serving wacn-id : any
g-id of the group : any
wacn-id of SU A : 00001
system-id of SU A : 001
u-id of SU A : 000001
wacn-id of SU B : 00002
system-id of SU B : 002
u-id of SU B : 000002
transmit priority of SU A and SU B: 00

User Action: none.
2- The Home RFSS still has the specified call segment established with the
Serving RFSS.
3- The Home RFSS has successfully sent audio on the specified call
segment in accordance with its RFSS role and this test.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
RFSS/
SERVING/
Call_Setup_For_Unit_to_Unit_Call		An RFSS can set up an SU-to-SU call.
SIP_ISSI_Serving_12_1_001SU-to-SU call setup – Successful (Availability Check option enabled) - Serving
RFSS. The Calling Home RFSS, the Called Home RFSS and the Called Serving
RFSS do not reject the request. All RFSSs have available RF resources and
RTP resources to set up the SU-to-SU call.
pass this test. This test implements variation:
1- The Calling Serving RFSS initiates the call with the “availability check”
option enabled and the called SU is able to support call with “availability
check”.
Home (to Home), Home (Multi-Segment)
applicable SU.
2- The Calling Home RFSS holds a record indicating that the applicable SU
supports either Availability Check or Direct Call.
3- The Called Home RFSS holds a record indicating that the applicable SU
supports Availability Check only.
1- The Calling Home RFSS holds a record indicating that the applicable SU
supports either Availability Check or Direct Call.
2- The Called Home RFSS holds a record indicating that the applicable SU
supports Availability Check only.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012

User Action: Calling Serving RFSS initiates the call.
the specified SU.
2- The Home RFSS has established an SU-to-SU call segment with the
appropriate Serving RFSS.
1- The Home RFSS has established an SU-to-SU call segment with its Home
RFSS counterpart.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_1_002SU-to-SU call setup – Successful (Availability Check option disabled) - Serving
RFSS. The Calling Home RFSS, the Called Home RFSS and the Called Serving
RFSS do not reject the request. All RFSSs have available RF resources and
RTP resources to set up the SU-to-SU call.
pass this test. This test implements variation:
2- The Calling Serving RFSS initiates the call with the “availability check”
option disabled and the called SU is only able to support call with
availability check.
Home (to Home), Home (Multi-Segment)
applicable SU.
2- The Calling Home RFSS holds a record indicating that the applicable SU
supports either Availability Check or Direct Call.
3- The Called Home RFSS holds a record indicating that the applicable SU
supports Availability Check only.
1- The Calling Home RFSS holds a record indicating that the applicable SU
supports either Availability Check or Direct Call.
2- The Called Home RFSS holds a record indicating that the applicable SU
supports Availability Check only.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012

User Action: Calling Serving RFSS initiates the call.
the specified SU.
2- The Home RFSS has established an SU-to-SU call segment with the
appropriate Serving RFSS.
1- The Home RFSS has established an SU-to-SU call segment with its Home
RFSS counterpart.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_2_001SU-to-SU call setup – Successful (Direct Call option, Availability Check option enabled) - Serving
in a Called Serving RFSS. The Calling Home RFSS, the Called Home RFSS and
the Called Serving RFSS do not reject the request coming from the Calling
Serving RFSS to initiate the SU-to-SU call. All RFSSs have available RF
resources and RTP resources to set up the SU-to-SU call.
pass this test. This test implements variation:
1- The Calling Serving RFSS initiates the call with the “Availability Check”
option enabled but the called SU is only able to support Direct Call.
Home (to Home), Home (Multi-Segment)
the specified SU;
2- The Calling Home RFSS holds a record indicating that the applicable SU
supports either Availability Check or Direct Call.
3- The Called Home RFSS holds a record indicating that the applicable SU
supports Direct Call only.
1- The Calling Home RFSS holds a record indicating that the applicable SU
supports either Availability Check or Direct Call.
2- The Called Home RFSS holds a record indicating that the applicable SU
supports Direct Call only.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012

User Action: Calling Serving RFSS initiates the call.
the specified SU.
2- The Home RFSS has established an SU-to-SU call segment with the
appropriate Serving RFSS.
1- The Home RFSS has established an SU-to-SU call segment with its Home
RFSS counterpart.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_2_002SU-to-SU call setup – Successful (Direct Call option, Availability Check option disabled) - Serving
in a Called Serving RFSS. The Calling Home RFSS, the Called Home RFSS and
the Called Serving RFSS do not reject the request coming from the Calling
Serving RFSS to initiate the SU-to-SU call. All RFSSs have available RF
resources and RTP resources to set up the SU-to-SU call.
pass this test. This test implements variation:
2- The Calling Serving RFSS initiates the call with the “availability check”
option disabled and the called SU is only able to support call with
availability check.
Home (to Home), Home (Multi-Segment)
the specified SU;
2- The Calling Home RFSS holds a record indicating that the applicable SU
supports either Availability Check or Direct Call.
3- The Called Home RFSS holds a record indicating that the applicable SU
supports Direct Call only.
1- The Calling Home RFSS holds a record indicating that the applicable SU
supports either Availability Check or Direct Call.
2- The Called Home RFSS holds a record indicating that the applicable SU
supports Direct Call only.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012

User Action: Calling Serving RFSS initiates the call.
the specified SU.
2- The Home RFSS has established an SU-to-SU call segment with the
appropriate Serving RFSS.
1- The Home RFSS has established an SU-to-SU call segment with its Home
RFSS counterpart.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_3_001SU-to-SU call setup – Successful (Full Duplex/Half Duplex, Available Check option enabled, SU Direct Call only)- - Serving
SU call addressed to an SU registered in the Called Serving RFSS. The Calling
Home RFSS, the Called Home RFSS and the Called Serving RFSS do not reject
the request coming from the Calling Serving RFSS to initiate the SU-to-SU call.
All RFSSs have available RF resources and RTP resources for the SU-to-SU
call. The Calling SU and Called SU both support the full duplex and half duplex
modes.
pass this test. This test implements variation:
1- The Calling Serving RFSS initiates the call with the “Availability Check”
option enabled but the called SU is only able to support Direct Call.
Home (to Home), Home (Multi-Segment)
applicable SU;
2- The Calling Home RFSS holds a record indicating that the applicable SU
supports Availability Check or Direct Call according to the considered test
case described in 12.3.1 and both Full-Duplex and Half-Duplex.
3- The Called Home RFSS holds a record indicating that the applicable SU
supports Availability Check or Direct Call according to the considered test
case described in 12.3.1 and both Full-Duplex and Half-Duplex.
1- The Calling Home RFSS holds a record indicating that the applicable SU
supports Availability Check or Direct Call according to the considered test
case described in 12.3.1 and both Full-Duplex and Half-Duplex.
2- The Called Home RFSS holds a record indicating that the applicable SU
supports Availability Check or Direct Call according to the considered test
case described in 12.3.1 and both Full-Duplex and Half-Duplex.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012

User Action: Calling Serving RFSS initiates the call.
the specified SU.
2- The Home RFSS has established an SU-to-SU call segment with the
appropriate Serving RFSS.
Home (to Home) and Home (Multi-Segment):
1- The Home RFSS has established an SU-to-SU call segment with its Home
RFSS counterpart.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_3_002SU-to-SU call setup – Successful (Full Duplex/Half Duplex, Available Check option disabled, SU Direct Call only)- - Serving
SU call addressed to an SU registered in the Called Serving RFSS. The Calling
Home RFSS, the Called Home RFSS and the Called Serving RFSS do not reject
the request coming from the Calling Serving RFSS to initiate the SU-to-SU call.
All RFSSs have available RF resources and RTP resources for the SU-to-SU
call. The Calling SU and Called SU both support the full duplex and half duplex
modes.
pass this test. This test implements variation:
2- The Calling Serving RFSS initiates the call with the “Availability Check”
option disabled and the called SU is able to support Direct Call.
Home (to Home), Home (Multi-Segment)
applicable SU;
2- The Calling Home RFSS holds a record indicating that the applicable SU
supports Availability Check or Direct Call according to the considered test
case described in 12.3.1 and both Full-Duplex and Half-Duplex.
3- The Called Home RFSS holds a record indicating that the applicable SU
supports Availability Check or Direct Call according to the considered test
case described in 12.3.1 and both Full-Duplex and Half-Duplex.
1- The Calling Home RFSS holds a record indicating that the applicable SU
supports Availability Check or Direct Call according to the considered test
case described in 12.3.1 and both Full-Duplex and Half-Duplex.
2- The Called Home RFSS holds a record indicating that the applicable SU
supports Availability Check or Direct Call according to the considered test
case described in 12.3.1 and both Full-Duplex and Half-Duplex.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012

User Action: Calling Serving RFSS initiates the call.
the specified SU.
2- The Home RFSS has established an SU-to-SU call segment with the
appropriate Serving RFSS.
Home (to Home) and Home (Multi-Segment):
1- The Home RFSS has established an SU-to-SU call segment with its Home
RFSS counterpart.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_3_003SU-to-SU call setup – Successful (Full Duplex/Half Duplex, Available Check option disabled, SU supports Availability Check)- - Serving
SU call addressed to an SU registered in the Called Serving RFSS. The Calling
Home RFSS, the Called Home RFSS and the Called Serving RFSS do not reject
the request coming from the Calling Serving RFSS to initiate the SU-to-SU call.
All RFSSs have available RF resources and RTP resources for the SU-to-SU
call. The Calling SU and Called SU both support the full duplex and half duplex
modes.
pass this test. This test implements variation:
3- The Calling Serving RFSS initiates the call without the “Availability Check”
option enabled but the called SU is able to support call with availability
check.
Home (to Home), Home (Multi-Segment)
applicable SU;
2- The Calling Home RFSS holds a record indicating that the applicable SU
supports Availability Check or Direct Call according to the considered test
case described in 12.3.1 and both Full-Duplex and Half-Duplex.
3- The Called Home RFSS holds a record indicating that the applicable SU
supports Availability Check or Direct Call according to the considered test
case described in 12.3.1 and both Full-Duplex and Half-Duplex.
1- The Calling Home RFSS holds a record indicating that the applicable SU
supports Availability Check or Direct Call according to the considered test
case described in 12.3.1 and both Full-Duplex and Half-Duplex.
2- The Called Home RFSS holds a record indicating that the applicable SU
supports Availability Check or Direct Call according to the considered test
case described in 12.3.1 and both Full-Duplex and Half-Duplex.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012

User Action: Calling Serving RFSS initiates the call.
the specified SU.
2- The Home RFSS has established an SU-to-SU call segment with the
appropriate Serving RFSS.
Home (to Home) and Home (Multi-Segment):
1- The Home RFSS has established an SU-to-SU call segment with its Home
RFSS counterpart.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_4_001SU-to-SU call setup – Successful (initiated in full duplex, setup in half
duplex, Availability Check enabled, SU only supports Direct Call) - Serving.
addressed to an SU registered in the Called Serving RFSS. The Calling Home
RFSS, the Called Home RFSS and the Called Serving RFSS do not reject the
request coming from the Calling Serving RFSS to initiate the SU-to-SU call. All
RFSSs have available RF resources and RTP resources for the SU-to-SU call.
The Calling SU both support the full duplex and half duplex modes. The Called
SU supports only half-duplex mode.
pass this test. This test implements variation:
1- The Calling Serving RFSS initiates the call with the “Availability Check”
option enabled but the called SU is only able to support Direct Call.
cases, the SIP Ringing message is never sent out and the field “c-pref” is present
in the appropriate SIP INVITE and 200 OK message as described in BACA-A
and specifically tested in sections 12.1and 12.2.
Home (to Home), Home (Multi-Segment)
applicable SU.
2- The Calling Home RFSS holds a record indicating that the applicable SU
supports Availability Check or Direct Call according to the considered test
case described in 12.3.1 and both Full-Duplex and Half-Duplex.
3- The Called Home RFSS holds a record indicating that the applicable SU
supports Availability Check or Direct Call according to the considered test
case described in 12.3.1 and only Half-Duplex.
1- The Calling Home RFSS holds a record indicating that the applicable SU
supports Availability Check or Direct Call according to the considered test
case described in 12.3.1 and both Full-Duplex and Half-Duplex.
2- The Called Home RFSS holds a record indicating that the applicable SU
supports Availability Check or Direct Call according to the considered test
case described in 12.3.1 and only Half-Duplex.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
the specified SU.
2- The Home RFSS has established an SU-to-SU call segment with the
appropriate Serving RFSS.
1- The Home RFSS has established an SU-to-SU call segment with its Home
RFSS counterpart.
Config: A
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_4_002SU-to-SU call setup – Successful (initiated in full duplex, setup in half
duplex, Availability Check disabled, SU supports Direct Call) - Serving.
addressed to an SU registered in the Called Serving RFSS. The Calling Home
RFSS, the Called Home RFSS and the Called Serving RFSS do not reject the
request coming from the Calling Serving RFSS to initiate the SU-to-SU call. All
RFSSs have available RF resources and RTP resources for the SU-to-SU call.
The Calling SU both support the full duplex and half duplex modes. The Called
SU supports only half-duplex mode.
pass this test. This test implements variation:
2- The Calling Serving RFSS initiates the call with the “Availability Check”
option disabled and the called SU is able to support Direct Call.
cases, the SIP Ringing message is never sent out and the field “c-pref” is present
in the appropriate SIP INVITE and 200 OK message as described in BACA-A
and specifically tested in sections 12.1and 12.2.
Home (to Home), Home (Multi-Segment)
applicable SU.
2- The Calling Home RFSS holds a record indicating that the applicable SU
supports Availability Check or Direct Call according to the considered test
case described in 12.3.1 and both Full-Duplex and Half-Duplex.
3- The Called Home RFSS holds a record indicating that the applicable SU
supports Availability Check or Direct Call according to the considered test
case described in 12.3.1 and only Half-Duplex.
1- The Calling Home RFSS holds a record indicating that the applicable SU
supports Availability Check or Direct Call according to the considered test
case described in 12.3.1 and both Full-Duplex and Half-Duplex.
2- The Called Home RFSS holds a record indicating that the applicable SU
supports Availability Check or Direct Call according to the considered test
case described in 12.3.1 and only Half-Duplex.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
the specified SU.
2- The Home RFSS has established an SU-to-SU call segment with the
appropriate Serving RFSS.
1- The Home RFSS has established an SU-to-SU call segment with its Home
RFSS counterpart.
Config: A
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_4_003SU-to-SU call setup – Successful (initiated in full duplex, setup in half
duplex, Availability Check disabled, SU supports Availability check) - Serving.
addressed to an SU registered in the Called Serving RFSS. The Calling Home
RFSS, the Called Home RFSS and the Called Serving RFSS do not reject the
request coming from the Calling Serving RFSS to initiate the SU-to-SU call. All
RFSSs have available RF resources and RTP resources for the SU-to-SU call.
The Calling SU both support the full duplex and half duplex modes. The Called
SU supports only half-duplex mode.
pass this test. This test implements variation:
3- The Calling Serving RFSS initiates the call without the “Availability Check”
option enabled but the called SU is able to support call with availability
check.
cases, the SIP Ringing message is never sent out and the field “c-pref” is present
in the appropriate SIP INVITE and 200 OK message as described in BACA-A
and specifically tested in sections 12.1and 12.2.
Home (to Home), Home (Multi-Segment)
applicable SU.
2- The Calling Home RFSS holds a record indicating that the applicable SU
supports Availability Check or Direct Call according to the considered test
case described in 12.3.1 and both Full-Duplex and Half-Duplex.
3- The Called Home RFSS holds a record indicating that the applicable SU
supports Availability Check or Direct Call according to the considered test
case described in 12.3.1 and only Half-Duplex.
1- The Calling Home RFSS holds a record indicating that the applicable SU
supports Availability Check or Direct Call according to the considered test
case described in 12.3.1 and both Full-Duplex and Half-Duplex.
2- The Called Home RFSS holds a record indicating that the applicable SU
supports Availability Check or Direct Call according to the considered test
case described in 12.3.1 and only Half-Duplex.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
the specified SU.
2- The Home RFSS has established an SU-to-SU call segment with the
appropriate Serving RFSS.
1- The Home RFSS has established an SU-to-SU call segment with its Home
RFSS counterpart.
Config: A
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_5_001SU-to-SU call setup – Successful (Protected mode requested) - Serving
addressed to an SU registered in the Called Serving RFSS. All RFSSs have
available RF resources and RTP resources for the SU-to-SU call. The Called
Home RFSS determines whether the call is protected or not.
pass this test. This test implements variation:
1- The Called Home RFSS is configured to accept the protected mode for
the called SU, and the calling SU requests the protected mode. In this
case, the call is set up with the protected option.
Home (to Home), Home (Multi-Segment)
applicable SU;
2- The unit to unit call for the called SU is configured for the protected or
unprotected mode in the Called Home RFSS, depending on the
considered test case.
1- The unit to unit call for the called SU is configured for the protected or
unprotected mode in the Called Home RFSS, depending on the
considered test case.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
the specified SU.
2- The Home RFSS has established an SU-to-SU call segment in protected
mode or not protected mode with the appropriate Serving RFSS
depending on the considered test case.
1- The Home RFSS has established an SU-to-SU call segment in protected
mode or not protected mode with its Home RFSS counterpart depending
on the considered test case.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_5_002SU-to-SU call setup – Successful (Unprotected mode) - Serving
addressed to an SU registered in the Called Serving RFSS. All RFSSs have
available RF resources and RTP resources for the SU-to-SU call. The Called
Home RFSS determines whether the call is protected or not.
pass this test. This test implements variation:
2- The Called Home RFSS is configured to accept the unprotected mode for
the called SU, and the calling SU requests the unprotected mode. In this
case, the call is set up with the unprotected option.
Home (to Home), Home (Multi-Segment)
applicable SU;
2- The unit to unit call for the called SU is configured for the protected or
unprotected mode in the Called Home RFSS, depending on the
considered test case.
1- The unit to unit call for the called SU is configured for the protected or
unprotected mode in the Called Home RFSS, depending on the
considered test case.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
the specified SU.
2- The Home RFSS has established an SU-to-SU call segment in protected
mode or not protected mode with the appropriate Serving RFSS
depending on the considered test case.
1- The Home RFSS has established an SU-to-SU call segment in protected
mode or not protected mode with its Home RFSS counterpart depending
on the considered test case.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_6_001SU-to-SU call setup (RF resources initially unavailable in Called
Serving RFSS, Availability Check enabled, SU only supports Direct Call) - Serving.
registered in the Called Serving RFSS. The Calling Home RFSS, the Called
Home RFSS and the Called Serving RFSS do not reject the request coming from
the Calling Serving RFSS to initiate the SU-to-SU call. All RFSSs have available
RTP resources to set up a call segment. The Called Serving RFSS initially does
not have RF resources available.
pass this test. This test implements variation:
1- The Calling Serving RFSS initiates the call with the “Availability Check”
option enabled but the called SU is only able to support Direct Call.
cases, the SIP Ringing message is never sent out and the field “c-pref” is present
in the appropriate SIP INVITE and 200 OK message as described in BACA-A
and specifically tested in sections 12.1and 12.2.
Home (to Home), Home (Multi-Segment)
the applicable SU.
2- The Home RFSS holds a record indicating that the applicable SU supports
Availability Check or Direct Call according to the considered test case
described in 12.3.1.
Home (to Home)
The Home RFSS holds a record indicating that the applicable SU supports
Availability Check or Direct Call according to the considered test case
described in 12.3.1.
Minimum RFSS Parameter Configuration :
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
the specified SU.
2- The Home RFSS has established an SU-to-SU call segment with the
appropriate Serving RFSS.
1- The Home RFSS has established an SU-to-SU call segment with its Home
RFSS counterpart.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_6_002SU-to-SU call setup (RF resources initially unavailable in Called
Serving RFSS, Availability Check disabled, SU supports Direct Call) - Serving.
registered in the Called Serving RFSS. The Calling Home RFSS, the Called
Home RFSS and the Called Serving RFSS do not reject the request coming from
the Calling Serving RFSS to initiate the SU-to-SU call. All RFSSs have available
RTP resources to set up a call segment. The Called Serving RFSS initially does
not have RF resources available.
pass this test. This test implements variation:
2- The Calling Serving RFSS initiates the call with the “Availability Check”
option disabled and the called SU is able to support Direct Call.
cases, the SIP Ringing message is never sent out and the field “c-pref” is present
in the appropriate SIP INVITE and 200 OK message as described in BACA-A
and specifically tested in sections 12.1and 12.2.
Home (to Home), Home (Multi-Segment)
the applicable SU.
2- The Home RFSS holds a record indicating that the applicable SU supports
Availability Check or Direct Call according to the considered test case
described in 12.3.1.
The Home RFSS holds a record indicating that the applicable SU supports
Availability Check or Direct Call according to the considered test case
described in 12.3.1.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
the specified SU.
2- The Home RFSS has established an SU-to-SU call segment with the
appropriate Serving RFSS.
1- The Home RFSS has established an SU-to-SU call segment with its Home
RFSS counterpart.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_6_003SU-to-SU call setup (RF resources initially unavailable in Called
Serving RFSS, Availability Check disabled, SU supports Availability Check) - Serving.
registered in the Called Serving RFSS. The Calling Home RFSS, the Called
Home RFSS and the Called Serving RFSS do not reject the request coming from
the Calling Serving RFSS to initiate the SU-to-SU call. All RFSSs have available
RTP resources to set up a call segment. The Called Serving RFSS initially does
not have RF resources available.
pass this test. This test implements variation:
3- The Calling Serving RFSS initiates the call without the “Availability Check”
option enabled but the called SU is able to support call with availability
check.
cases, the SIP Ringing message is never sent out and the field “c-pref” is present
in the appropriate SIP INVITE and 200 OK message as described in BACA-A
and specifically tested in sections 12.1and 12.2.
Home (to Home), Home (Multi-Segment)
the applicable SU.
2- The Home RFSS holds a record indicating that the applicable SU supports
Availability Check or Direct Call according to the considered test case
described in 12.3.1.
The Home RFSS holds a record indicating that the applicable SU supports
Availability Check or Direct Call according to the considered test case
described in 12.3.1.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
the specified SU.
2- The Home RFSS has established an SU-to-SU call segment with the
appropriate Serving RFSS.
1- The Home RFSS has established an SU-to-SU call segment with its Home
RFSS counterpart.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_7_001SU-to-SU call setup (Call canceled by the Calling Serving RFSS,
Availability Check enabled, SU only supports Direct Call) - Serving.
in the Called Serving RFSS. The Calling Serving RFSS cancels immediately after
initiating the call.
pass this test. This test implements variation:
1- The Calling Serving RFSS initiates the call with the “Availability Check”
option enabled but the called SU is only able to support Direct Call.
cases, the SIP Ringing message is never sent out and the field “c-pref” is present
in the appropriate SIP INVITE and 200 OK message as described in BACA-A
and specifically tested in sections 12.1and 12.2.
Applicable ISSI Conformance Test RFSS Roles: Serving, Home (to Serving),
Home (to Home), Home (Multi-Segment)
applicable SU.
2- The Home RFSS holds a record indicating that the applicable SU supports
Availability Check or Direct Call according to the considered test case
described in 12.3.1.
1- The Home RFSS holds a record indicating that the applicable SU supports
Availability Check or Direct Call according to the considered test case
described in 12.3.1.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
the specified SU.
2- The Home RFSS has NOT established an SU-to-SU call segment with the
appropriate Serving RFSS.
1- The Home RFSS has NOT established an SU-to-SU call segment with the
Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_7_002SU-to-SU call setup (Call canceled by the Calling Serving RFSS,
Availability Check disabled, SU supports Direct Call) - Serving.
in the Called Serving RFSS. The Calling Serving RFSS cancels immediately after
initiating the call.
pass this test. This test implements variation:
2- The Calling Serving RFSS initiates the call with the “Availability Check”
option disabled and the called SU is able to support Direct Call.
cases, the SIP Ringing message is never sent out and the field “c-pref” is present
in the appropriate SIP INVITE and 200 OK message as described in BACA-A
and specifically tested in sections 12.1and 12.2.
Applicable ISSI Conformance Test RFSS Roles: Serving, Home (to Serving),
Home (to Home), Home (Multi-Segment)
applicable SU.
2- The Home RFSS holds a record indicating that the applicable SU supports
Availability Check or Direct Call according to the considered test case
described in 12.3.1.
1- The Home RFSS holds a record indicating that the applicable SU supports
Availability Check or Direct Call according to the considered test case
described in 12.3.1.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
the specified SU.
2- The Home RFSS has NOT established an SU-to-SU call segment with the
appropriate Serving RFSS.
1- The Home RFSS has NOT established an SU-to-SU call segment with the
Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_7_003SU-to-SU call setup (Call canceled by the Calling Serving RFSS,
Availability Check disabled, SU supports Availability Check) - Serving.
in the Called Serving RFSS. The Calling Serving RFSS cancels immediately after
initiating the call.
pass this test. This test implements variation:
3- The Calling Serving RFSS initiates the call without the “Availability Check”
option enabled but the called SU is able to support call with availability
check.
cases, the SIP Ringing message is never sent out and the field “c-pref” is present
in the appropriate SIP INVITE and 200 OK message as described in BACA-A
and specifically tested in sections 12.1and 12.2.
Applicable ISSI Conformance Test RFSS Roles: Serving, Home (to Serving),
Home (to Home), Home (Multi-Segment)
applicable SU.
2- The Home RFSS holds a record indicating that the applicable SU supports
Availability Check or Direct Call according to the considered test case
described in 12.3.1.
1- The Home RFSS holds a record indicating that the applicable SU supports
Availability Check or Direct Call according to the considered test case
described in 12.3.1.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
the specified SU.
2- The Home RFSS has NOT established an SU-to-SU call segment with the
appropriate Serving RFSS.
1- The Home RFSS has NOT established an SU-to-SU call segment with the
Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_8_001SU-to-SU call setup (Calls with different priorities,
Availability Check enabled, SU only supports Direct Call) - Serving.
in the Called Serving RFSS. While awaiting the response for the call, the Called
RFSS initiates an SU-to-SU call addressed to the Calling SU. The SU-to-SU call
initiated by the Called RFSS has higher priority than the SU-to-SU call originated
by the Calling RFSS. The collision between the two calls is detected and
mitigated by the Called Serving RFSS.
pass this test. This test implements variation:
1- The Calling Serving RFSS initiates the call with the “Availability Check”
option enabled but the called SU is only able to support Direct Call.
cases, the SIP Ringing message is never sent out and the field “c-pref” is present
in the appropriate SIP INVITE and 200 OK message as described in BACA-A
and specifically tested in sections 12.1and 12.2.
considers that the call to be declined is the one initiated for the SU having the
lowest SUID.
Home (to Home), Home (Multi-Segment))
applicable SU;
2- The Home RFSS holds a record indicating that the applicable SU supports
Availability Check or Direct Call according to the considered test case
described in 12.3.1.
Home (to Home):
1- The Home RFSS holds a record indicating that the applicable SU supports
Availability Check or Direct Call according to the considered test case
described in 12.3.1.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
with higher priority.
the specified SU.
2- The Home RFSS has established the higher priority SU-to-SU call
segment with the appropriate Serving RFSS.
1- The Home RFSS has established the higher priority SU-to-SU call
segment with its Home RFSS counterpart.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_8_002SU-to-SU call setup (Calls with different priorities,
Availability Check enabled, SU only supports Direct Call) - Serving.
in the Called Serving RFSS. While awaiting the response for the call, the Called
RFSS initiates an SU-to-SU call addressed to the Calling SU. The SU-to-SU call
initiated by the Called RFSS has higher priority than the SU-to-SU call originated
by the Calling RFSS. The collision between the two calls is detected and
mitigated by the Called Serving RFSS.
pass this test. This test implements variation:
2- The Calling Serving RFSS initiates the call with the “Availability Check”
option disabled and the called SU is able to support Direct Call.
cases, the SIP Ringing message is never sent out and the field “c-pref” is present
in the appropriate SIP INVITE and 200 OK message as described in BACA-A
and specifically tested in sections 12.1and 12.2.
considers that the call to be declined is the one initiated for the SU having the
lowest SUID.
Home (to Home), Home (Multi-Segment))
applicable SU;
2- The Home RFSS holds a record indicating that the applicable SU supports
Availability Check or Direct Call according to the considered test case
described in 12.3.1.
Home (to Home):
1- The Home RFSS holds a record indicating that the applicable SU supports
Availability Check or Direct Call according to the considered test case
described in 12.3.1.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
with higher priority.
the specified SU.
2- The Home RFSS has established the higher priority SU-to-SU call
segment with the appropriate Serving RFSS.
1- The Home RFSS has established the higher priority SU-to-SU call
segment with its Home RFSS counterpart.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_8_003SU-to-SU call setup (Calls with different priorities,
Availability Check enabled, SU only supports Direct Call) - Serving.
in the Called Serving RFSS. While awaiting the response for the call, the Called
RFSS initiates an SU-to-SU call addressed to the Calling SU. The SU-to-SU call
initiated by the Called RFSS has higher priority than the SU-to-SU call originated
by the Calling RFSS. The collision between the two calls is detected and
mitigated by the Called Serving RFSS.
pass this test. This test implements variation:
3- The Calling Serving RFSS initiates the call without the “Availability Check”
option enabled but the called SU is able to support call with availability
check.
cases, the SIP Ringing message is never sent out and the field “c-pref” is present
in the appropriate SIP INVITE and 200 OK message as described in BACA-A
and specifically tested in sections 12.1and 12.2.
considers that the call to be declined is the one initiated for the SU having the
lowest SUID.
Home (to Home), Home (Multi-Segment))
applicable SU;
2- The Home RFSS holds a record indicating that the applicable SU supports
Availability Check or Direct Call according to the considered test case
described in 12.3.1.
Home (to Home):
1- The Home RFSS holds a record indicating that the applicable SU supports
Availability Check or Direct Call according to the considered test case
described in 12.3.1.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
with higher priority.
the specified SU.
2- The Home RFSS has established the higher priority SU-to-SU call
segment with the appropriate Serving RFSS.
1- The Home RFSS has established the higher priority SU-to-SU call
segment with its Home RFSS counterpart.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_9_001SU-to-SU call setup (Calling SU not registered in the Calling Home
RFSS) - Serving.
registered in the Calling Home RFSS.
Home (Multi-Segment)
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
u-id of the calling SU : 000011
u-id of the called SU : 000012
with the Calling Serving RFSS.
2- The Calling Home RFSS considers the Calling SU NOT registered.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_10_001SU-to-SU call setup (Called SU not registered in the Called Home
RFSS) - Serving.
registered in the Called Home RFSS.
Home (to Home), Home (Multi-Segment)
Calling SU.
2- The Called Home RFSS considers the Called SU NOT registered.
1- The Called Home RFSS considers the Called SU NOT registered.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
u-id of the calling SU : 000011
u-id of the called SU : 000012
for the Calling SU.
2- The Home RFSS has NOT established an SU-to-SU call segment with the
appropriate Serving RFSS.
3- The Called Home RFSS considers the Called SU NOT registered.
1- The Home RFSS has NOT established an SU-to-SU call segment with its
Home RFSS counterpart.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_11_001SU-to-SU call setup (Calling SU not authorized to make a call) - Serving
authorized by the Calling Home RFSS to make this call.
Home (Multi-Segment)
for the specified SU.
2- The Calling Home RFSS considers the Calling SU NOT authorized to
make the considered call.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
u-id of the calling SU : 000011
u-id of the called SU : 000012
for the specified SU.
2- The Calling Home RFSS has NOT established an SU-to-SU call segment
with the Calling Serving RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_12_001SU-to-SU call setup (Called SU not authorized to respond to a call) - Serving
configured to refuse the considered call with the cause reflecting that the called
SU is not authorized to receive the call.
Home (to Home), Home (Multi-Segment)
for the Calling SU.
2- The Called Home RFSS considers the Called Serving RFSS registered for
the Called SU.
3- The Called Home RFSS considers the Called SU NOT authorized to
respond to the considered call.
1- The Called Home RFSS considers the Called SU NOT authorized to
respond to the considered call.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
u-id of the calling SU : 000011
u-id of the called SU : 000012
for the Calling SU.
2- The Called Home RFSS considers the Called SU registered.
3- The Home RFSS has NOT established an SU-to-SU call segment with the
appropriate Serving RFSS.
1- The Home RFSS has NOT established an SU-to-SU call segment with its
Home RFSS counterpart.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_13_001SU-to-SU call setup (Protected audio call cannot be
granted) - Serving.
detects that the request with the chosen mode cannot be granted.
pass the test. This test performs the following variation:
1- The calling SU requests protected mode. In this case, the Called Home
RFSS is configured to not accept protected mode.
NOTE:
Only the first case is described in section 12.13.5. In the second case, the cprotected
parameter is set to 0 or is not present and the p25-condition-code and
P25-condition-text in the 403 Forbidden message will be set to “2C” and
"Unprotected audio call not granted", respectively.
Applicable ISSI Conformance Test RFSS Roles: Serving, Home (to Serving),
Home (to Home), Home (Multi-Segment)
for the Calling SU.
2- The Called Home RFSS considers the Called Serving RFSS registered for
the Called SU.
3- The Called Home RFSS considers the Called SU NOT authorized to
respond to the considered call.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
u-id of the calling SU : 000011
u-id of the called SU : 000012
for the Calling SU.
2- The Home RFSS has NOT established an SU-to-SU call segment with the
appropriate Serving RFSS.
Home (to Home) and Home (Multi-Segment):
1- The Home RFSS has NOT established an SU-to-SU call segment with its
Home RFSS counterpart.
2- The Called Home RFSS considers the Called Serving RFSS registered for
the Called SU.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_13_002SU-to-SU call setup (unprotected audio call cannot be
granted) - Serving.
detects that the request with the chosen mode cannot be granted.
pass the test. This test performs the following variation:
2- The calling SU requests unprotected mode. In this case, the Called Home
RFSS is configured to not accept unprotected mode.
NOTE:
Only the first case is described in section 12.13.5. In the second case, the cprotected
parameter is set to 0 or is not present and the p25-condition-code and
P25-condition-text in the 403 Forbidden message will be set to “2C” and
"Unprotected audio call not granted", respectively.
Applicable ISSI Conformance Test RFSS Roles: Serving, Home (to Serving),
Home (to Home), Home (Multi-Segment)
for the Calling SU.
2- The Called Home RFSS considers the Called Serving RFSS registered for
the Called SU.
3- The Called Home RFSS considers the Called SU NOT authorized to
respond to the considered call.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
u-id of the calling SU : 000011
u-id of the called SU : 000012
for the Calling SU.
2- The Home RFSS has NOT established an SU-to-SU call segment with the
appropriate Serving RFSS.
Home (to Home) and Home (Multi-Segment):
1- The Home RFSS has NOT established an SU-to-SU call segment with its
Home RFSS counterpart.
2- The Called Home RFSS considers the Called Serving RFSS registered for
the Called SU.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_14_001SU-to-SU call setup (Calling SU unknown to Calling Home RFSS) - Serving
to the Calling Home RFSS.
Home (Multi-Segment)
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
u-id of the calling SU : 000011
u-id of the called SU : 000012
appropriate Serving RFSS.
2- The Calling Home RFSS considers itself NOT home to the Calling SU.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_15_001SU-to-SU call setup (Called SU unknown to Called Home RFSS) - Serving
to the Called Home RFSS.
Applicable ISSI Conformance Test RFSS Roles: Serving, Home (to Serving),
Home (to Home), Home (Multi-Segment)
SU.
2- The Called Home RFSS considers itself NOT home to the Called SU.
Home (to Home):
1- The Called Home RFSS considers itself NOT home to the Called SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
u-id of the calling SU : 000011
u-id of the called SU : 000012
the Calling SU.
2-The Home RFSS has NOT established an SU-to-SU call segment with the
appropriate Serving RFSS.
3- The Called Home RFSS considers itself NOT home to the Called SU.
1- The Home RFSS has NOT established an SU-to-SU call segment with its
Home RFSS counterpart.
2- The Called Home RFSS considers itself NOT home to the Called SU.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_16_001SU-to-SU call setup (Called SU not registered to Called Serving
RFSS) - Serving.
registered to the Called Serving RFSS.
Home (to Home), Home (Multi-Segment)
applicable SU.
1- The Home RFSS considers the applicable SU to be registered.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
for the Calling SU.
2- The Home RFSS has NOT established an SU-to-SU call segment with the
appropriate Serving RFSS.
3- The Called Home RFSS considers the Called Serving RFSS NOT
registered for the Called SU.
Home RFSS counterpart.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_17_001SU-to-SU call setup (Calling SU radio inhibited – case 1) - Serving
detects that the Calling SU is radio inhibited.
Home (Multi-Segment)
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
u-id of the calling SU : 000011
u-id of the called SU : 000012
for the Calling SU.
2- The Home RFSS has NOT established an SU-to-SU call segment with the
appropriate Serving RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_18_001SU-to-SU call setup (Calling SU radio inhibited – case 2) - Serving
detects, while awaiting a final response on the Called Home RFSS, that the
Calling SU is radio inhibited.
Home (to Home), Home (Multi-Segment)
for the Calling SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
u-id of the calling SU : 000011
u-id of the called SU : 000012
for the Calling SU.
2- The Home RFSS has NOT established an SU-to-SU call segment with the
appropriate Serving RFSS.
3- The Calling Home detects that the Calling SU is radio inhibited.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_19_001SU-to-SU call setup (Called SU radio inhibited – case 1) - Serving
detects that the Called SU is radio inhibited.
Home (to Home), Home (Multi-Segment)
for the Calling SU.
2- The Called Home RFSS considers the Called Serving RFSS registered for
the Called SU.
3- The Called Home RFSS detects that the Called SU is radio inhibited.
Home (to Home):
1- The Called Home RFSS detects that the Called SU is radio inhibited.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
u-id of the calling SU : 000011
u-id of the called SU : 000012
for the Calling SU.
2- The Called Home RFSS considers the Called SU registered.
3- The Home RFSS has NOT established an SU-to-SU call segment with the
appropriate Serving RFSS.
Home (to Home) and Home (Multi-Segment):
1- The Home RFSS has NOT established an SU-to-SU call segment with its
Home RFSS counterpart.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_20_001SU-to-SU call setup (Called SU radio inhibited – case 2) - Serving
detects while awaiting a final response on the Called Serving RFSS that the
Called SU is radio inhibited.
Home (to Home), Home (Multi-Segment)
for the Calling SU.
2- The Called Home RFSS considers the Called Serving RFSS registered for
the Called SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
for the Calling SU.
2- The Home RFSS has NOT established an SU-to-SU call segment with the
appropriate Serving RFSS.
3- The Called Home detects that the Called SU is radio inhibited.
1- The Home RFSS has NOT established an SU-to-SU call segment with its
Home RFSS counterpart.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_21_001SU-to-SU call setup (Called Serving RFSS does not have available
RTP resources) - Serving.
Called Serving RFSS. The Called Serving RFSS does not have available RTP
resources to set up RTP sessions.
Home (to Home), Home (Multi-Segment)
applicable SU.
Home (to Home):
2- The Home RFSS considers the applicable SU to be registered.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
the specified SU.
2- The Home RFSS has NOT established an SU-to-SU call segment with the
appropriate Serving RFSS.
Home (to Home) and Home (Multi-Segment):
1- The Home RFSS has NOT established an SU-to-SU call segment with its
Home RFSS counterpart.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_22_001SU-to-SU call setup (Called SU is busy) - Serving
Called Serving RFSS. The Calling Home RFSS, the Called Home RFSS and the
Called Serving RFSS do not reject the call request. All RFSSs have available RF
resources and RTP resources to set up the SU-to-SU call. The Called Serving
RFSS does not accept the call because the requested SU is busy. The Called
Serving RFSS responds with an appropriate error message.
Home (to Home), Home (Multi-Segment)
applicable SU.
Home (to Home):
1- The Home RFSS considers the applicable SU to be registered.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
the specified SU.
2- The Home RFSS has NOT established an SU-to-SU call segment with the
appropriate Serving RFSS.
Home (to Home) and Home (Multi-Segment):
1- The Home RFSS has NOT established an SU-to-SU call segment with the
Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_23_001SU Roaming (Called SU) - Serving
the call, a New Called Serving RFSS registers for the SU triggering the Roamed
procedure.
Applicable ISSI Conformance Test RFSS Roles: Serving, Home (to Serving),
Home (Multi-Segment)
SU.
2- The Home RFSS has successfully established an SU-to-SU call segment
with the Called Serving RFSS.
3- The Home RFSS considers the New Called Serving RFSS NOT registered
for the SU.
New Called Serving rfss-id : 01
New Called Serving system-id : 001
New Called Serving wacn-id : 00001
Called and calling Home rfss-id : 02
Called and calling Home system-id : 002
Called and calling Home wacn-id : 00002
Called Serving rfss-id : 03
Called Serving system-id : 003
Called Serving wacn-id : 00003
u-id of the calling SU : 000011
u-id of the called SU : 000012
the SU.
2- The Home RFSS does NOT have an SU-to-SU call segment established
with the Called Serving RFSS.
3- The Home RFSS considers the New Called Serving RFSS registered for
the SU.
4- The Home RFSS has established an SU-to-SU call segment with the New
Called Serving RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_24_001SU Roaming (Called SU) - Serving
the call, a New Calling Serving RFSS registers for the SU triggering the Roamed
procedure.
Applicable ISSI Conformance Test RFSS Roles: Serving, Home (to Serving),
Home (Multi-Segment)
SU.
2- The Home RFSS has successfully established an SU-to-SU call segment
with the Calling Serving RFSS.
3- The Home RFSS considers the New Calling Serving RFSS NOT
registered for the SU.
4- The Home RFSS does NOT have an SU-to-SU call segment established
with the New Calling Serving RFSS.
New Calling Serving rfss-id : 01
New Calling Serving system-id : 001
New Calling Serving wacn-id : 00001
Calling and called Home rfss-id : 02
Calling and called Home system-id : 002
Calling and called Home wacn-id : 00002
Calling Serving rfss-id : 03
Calling Serving system-id : 003
Calling Serving wacn-id : 00003
u-id of the calling SU : 000011
u-id of the called SU : 000012
the SU.
2- The Home RFSS does NOT have an SU-to-SU call segment established
with the Calling Serving RFSS.
3- The Home RFSS considers the New Calling Serving RFSS registered for
the SU.
4- The Home RFSS has established an SU-to-SU call segment with the New
Calling Serving RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_25_001SU Roaming (No RF resources available in the New Called Serving
RFSS) - Serving.
the call, a New Called Serving RFSS registers for the SU triggering the Roamed
procedure. The New Called Serving RFSS has no RF resource available and the
SU-to-SU call is terminated.
Home (Multi-Segment)
SU.
2- The Home RFSS has successfully established an SU-to-SU call segment
with the Called Serving RFSS.
3- The Home RFSS considers the New Called Serving RFSS NOT registered
for the SU.
New Called Serving rfss-id : 01
New Called Serving system-id : 001
New Called Serving wacn-id : 00001
Called and calling Home rfss-id : 02
Called and calling Home system-id : 002
Called and calling Home wacn-id : 00002
Called Serving rfss-id : 03
Called Serving system-id : 003
Called Serving wacn-id : 00003
u-id of the calling SU : 000011
u-id of the called SU : 000012
the SU.
2- The Home RFSS does NOT have an SU-to-SU call segment established
with the Called Serving RFSS.
3- The Home RFSS considers the New Called RFSS registered for the SU.
4- The Home RFSS does NOT have an SU-to-SU call segment established
with the New Called Serving RFSS.
can, for instance, retry to invite the new Called Serving RFSS or terminate the
call.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_12_26_001SU Roaming (No RF resources available in the New Calling Serving
RFSS) - Serving.
the call, a New Calling Serving RFSS registers for the SU triggering the Roamed
procedure. The New Calling Serving RFSS has no RF resources available and
the SU-to-SU call is terminated.
Home (Multi-Segment)
SU.
2- The Home RFSS has successfully established an SU-to-SU call segment
with the Calling Serving RFSS.
3- The Home RFSS considers the New Calling Serving RFSS NOT
registered for the SU.
New Calling Serving rfss-id : 01
New Calling Serving system-id : 001
New Calling Serving wacn-id : 00001
Calling and called Home rfss-id : 02
Calling and called Home system-id : 002
Calling and called Home wacn-id : 00002
Calling Serving rfss-id : 03
Calling Serving system-id : 003
Calling Serving wacn-id : 00003
u-id of the calling SU : 000011
u-id of the called SU : 000012
the SU.
2- The Home RFSS does NOT have an SU-to-SU call segment established
with the Calling Serving RFSS.
3- The Home RFSS considers the New Calling RFSS registered for the SU.
4- The Home RFSS does NOT have an SU-to-SU call segment established
with the New Calling Serving RFSS.
5- Upon local policy, the Home RFSS can, for instance, retry to invite the
new Calling Serving RFSS or terminate the call.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
RFSS/
SERVING/
Call_Teardown_Unit_to_Unit_Call
SIP_ISSI_Serving_13_01_001SU-to-SU call termination (Calling Serving RFSS initiated) - Serving
Called Serving RFSS. The SU-to-SU call setup is successful. The Calling
Serving RFSS terminates the call.
Home (to Home), Home (Multi-Segment)
the applicable SU.
2- The Home RFSS has successfully established an SU-to-SU call segment
with the appropriate Serving RFSS.
1- The Home RFSS has successfully established an SU-to-SU call segment
with its Home RFSS counterpart for the call.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
the applicable SU.
2- The Home RFSS does NOT have an SU-to-SU call segment established
with the appropriate Serving RFSS.
Home (to Home) and Home (Multi-Segment):
1- The Home RFSS does NOT have an SU-to-SU call segment established
with its Home RFSS counterpart.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_13_02_001SU-to-SU call termination (Called Serving RFSS initiated) - Serving
in the Called Serving RFSS. The SU-to-SU call setup is successful. The Called
Serving RFSS releases the SU-to-SU call.
Home (to Home), Home (Multi-Segment)
the applicable SU.
2- The Home RFSS has successfully established an SU-to-SU call segment
with the appropriate Serving RFSS.
1- The Home RFSS has successfully established an SU-to-SU call segment
with its Home RFSS counterpart for the call.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
the applicable SU.
2- The Home RFSS does NOT have an SU-to-SU call segment established
with the appropriate Serving RFSS.
Home (to Home) and Home (Multi-Segment):
1- The Home RFSS does NOT have
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
RFSS/
SERVING/
Basic_SU_to_SU_Call_Transmission_Ctrl_Procs		After the setup of a unit to unit call, the conformance to the basic transmission
SIP_ISSI_Serving_14_01_001SU to SU Voice Transmission (Serving RFSS originated) - Serving
Serving RFSS. The Calling Serving RFSS starts and then stops a voice
transmission.
Home (to Home), Home (Multi-Segment)
the applicable SU.
2- The Home RFSS has successfully established an SU-to-SU call segment
with the appropriate Serving RFSS.
1- The Home RFSS has successfully established an SU-to-SU call segment
with its Home RFSS counterpart for the call.
Calling Serving rfss-id : any
Calling Serving system-id : any
Calling Serving wacn-id : any
Calling Home rfss-id : any
Calling Home system-id : any
Calling Home wacn-id : any
Called Home rfss-id : any
Called Home system-id : any
Called Home wacn-id : any
Called Serving rfss-id : any
Called Serving system-id : any
Called Serving wacn-id : any
wacn-id of the calling SU: 00002
system-id of the calling SU: 002
u-id of the calling SU : 000001
transmit priority : 00
the applicable SU.
2- The Home RFSS has an SU-to-SU call segment established with the
appropriate Serving RFSS.
3- The Home RFSS has successfully received audio on the specified call
segment in accordance with its RFSS role and this test.
4- The Home RFSS has successfully forwarded audio on the specified call
segment in accordance with its RFSS role and this test.
5- The Home RFSS is idle with respect to ISSI audio traffic on the SU-to-SU
call segment.
Home (to Home) and Home (Multi-Segment):
1- The Home RFSS has an SU-to-SU call segment established with its Home
RFSS counterpart.
2- The Home RFSS has successfully received audio on the specified call
segment in accordance with its RFSS role and this test.
3- The Home RFSS has successfully forwarded audio on the specified call
segment in accordance with its RFSS role and this test.
4- The Home RFSS is idle with respect to ISSI audio traffic on the SU-to-SU
call segment.
Config: A
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_14_02_001SU to SU Voice Transmission (Serving RFSS originated) - Serving
Serving RFSS. The Calling Serving RFSS starts and then stops a voice
transmission.
Home (to Home), Home (Multi-Segment)
the applicable SU.
2- The Home RFSS has successfully established an SU-to-SU call segment
with the appropriate Serving RFSS.
1- The Home RFSS has successfully established an SU-to-SU call segment
with its Home RFSS counterpart for the call.
Calling Serving rfss-id : any
Calling Serving system-id : any
Calling Serving wacn-id : any
Calling Home rfss-id : any
Calling Home system-id : any
Calling Home wacn-id : any
Called Home rfss-id : any
Called Home system-id : any
Called Home wacn-id : any
Called Serving rfss-id : any
Called Serving system-id : any
Called Serving wacn-id : any
wacn-id of the calling SU: 00002
system-id of the calling SU: 002
u-id of the calling SU : 000001
transmit priority : 00
the applicable SU.
2- The Home RFSS has an SU-to-SU call segment established with the
appropriate Serving RFSS.
3- The Home RFSS has successfully received audio on the specified call
segment in accordance with its RFSS role and this test.
4- The Home RFSS has successfully forwarded audio on the specified call
segment in accordance with its RFSS role and this test.
5- The Home RFSS is idle with respect to ISSI audio traffic on the SU-to-SU
call segment.
Home (to Home) and Home (Multi-Segment):
1- The Home RFSS has an SU-to-SU call segment established with its Home
RFSS counterpart.
2- The Home RFSS has successfully received audio on the specified call
segment in accordance with its RFSS role and this test.
3- The Home RFSS has successfully forwarded audio on the specified call
segment in accordance with its RFSS role and this test.
4- The Home RFSS is idle with respect to ISSI audio traffic on the SU-to-SU
call segment.
Config: A
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_Serving_14_03_001RTP Heartbeat - Serving
RFSS, Calling Home RFSS, Called Home RFSS and a Called Serving RFSS.
The Calling Serving RFSS, Calling Home RFSS, Called Home RFSS and the
Called Serving RFSS send the RTP Heartbeat message periodically.
Home (to Home), Home (Multi-Segment)
the applicable SU.
2- The Home RFSS has successfully established an SU-to-SU call segment
with the appropriate Serving RFSS.
3- The Home RFSS is idle with respect ISSI voice traffic on the SU-to-SU call
segment.
1- The Home RFSS has successfully established an SU-to-SU call segment
with its Home RFSS counterpart for the call.
2- The Home RFSS is idle with respect ISSI voice traffic on the SU-to-SU call
segment.
Calling Serving rfss-id : any
Calling Serving system-id : any
Calling Serving wacn-id : any
Calling Home rfss-id : any
Calling Home system-id : any
Calling Home wacn-id : any
Called Home rfss-id : any
Called Home system-id : any
Called Home wacn-id : any
Called Serving rfss-id : any
Called Serving system-id : any
Called Serving wacn-id : any
the applicable SU.
2- The Home RFSS has an SU-to-SU call segment established with the
appropriate Serving RFSS.
3- The Home RFSS has successfully received the RTP Heartbeat message
on the SU-to-SU call segment.
Home (to Home) and Home (Multi-Segment):
1- The Home RFSS has an SU-to-SU call segment established with its Home
RFSS counterpart.
2- The Home RFSS has successfully received the RTP Heartbeat message
on the SU-to-SU call segment.
Config: A
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
RFSS/
Supplementary_Data
RFSS/
Supplementary_Data/
Home_Tests
RFSS/
Supplementary_Data/
Home_Tests/
SUtoSU_Supplementary_Data_Procedures		These tests describe SU to SU Supplementary Data Procedures for the short
SIP_ISSI_SUPDAT_Home_4_1_001Supplementary data request successfully delivered - Home
Called Serving RFSS. The Calling Home RFSS, the Called Home RFSS and the
Called Serving RFSS do not reject the service.
A particular supplementary data service corresponds to one instance of test
having its own pass/fail criteria.
The various instances of test corresponds the following cases:
a) The Calling Serving RFSS initiated the call alert SD service.
b) The Calling Serving RFSS initiated the short message SD service.
c) The Calling Serving RFSS initiated the status query SD service.
d) The Calling Serving RFSS initiated the status update SD service
e) The Calling Serving RFSS initiated the basic radio unit monitor SD service
f) The Calling Serving RFSS initiated the enhanced radio unit monitor SD
service
g) The Calling Serving RFSS initiated the radio check SD service
h) The Calling Serving RFSS initiated the radio detach SD service
i) The Calling Serving RFSS initiated the radio inhibit SD service
j) The Calling Serving RFSS initiated the radio un-inhibit SD service
Only the instance of tests corresponding to the short message SD service is
shown in the section “Signaling parameters” of the tests described in the 4.1.5
section.
Home (to Home), Home (Multi-Segment)
applicable SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
g-id of the calling SU : 0063
g-id of the called SU : 0064
exchange (SD request and SD response) with the appropriate Home
RFSS.
Config: A
Ref: 08-092 - ISSI - Supplementary Data Conformance Test 2008-12-12
SIP_ISSI_SUPDAT_B2B_Home_4_1_001Supplementary data request successfully delivered - Home
SIP_ISSI_SUPDAT_Serving_4_1_001.
Home (to Home), Home (Multi-Segment)
applicable SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
g-id of the calling SU : 0063
g-id of the called SU : 0064
exchange (SD request and SD response) with the appropriate Home
RFSS.
Config: A
Ref: 08-092 - ISSI - Supplementary Data Conformance Test 2008-12-12
RFSS/
Supplementary_Data/
Serving_Tests
RFSS/
Supplementary_Data/
Serving_Tests/
SUtoSU_Supplementary_Data_Procedures		These tests describe SU to SU Supplementary Data Procedures for the short
SIP_ISSI_SUPDAT_Serving_4_1_001Supplementary data request successfully delivered - Serving
Called Serving RFSS. The Calling Home RFSS, the Called Home RFSS and the
Called Serving RFSS do not reject the service.
A particular supplementary data service corresponds to one instance of test
having its own pass/fail criteria.
The various instances of test corresponds the following cases:
a) The Calling Serving RFSS initiated the call alert SD service.
b) The Calling Serving RFSS initiated the short message SD service.
c) The Calling Serving RFSS initiated the status query SD service.
d) The Calling Serving RFSS initiated the status update SD service
e) The Calling Serving RFSS initiated the basic radio unit monitor SD service
f) The Calling Serving RFSS initiated the enhanced radio unit monitor SD
service
g) The Calling Serving RFSS initiated the radio check SD service
h) The Calling Serving RFSS initiated the radio detach SD service
i) The Calling Serving RFSS initiated the radio inhibit SD service
j) The Calling Serving RFSS initiated the radio un-inhibit SD service
Only the instance of tests corresponding to the short message SD service is
shown in the section “Signaling parameters” of the tests described in the 4.1.5
section.
Home (to Home), Home (Multi-Segment)
Calling SU.
Calling Serving rfss-id : 01
Calling Serving system-id : 001
Calling Serving wacn-id : 00001
Calling Home rfss-id : 02
Calling Home system-id : 002
Calling Home wacn-id : 00002
Called Home rfss-id : 03
Called Home system-id : 003
Called Home wacn-id : 00003
Called Serving rfss-id : 04
Called Serving system-id : 004
Called Serving wacn-id : 00004
u-id of the calling SU : 000011
u-id of the called SU : 000012
g-id of the calling SU : 0063
g-id of the called SU : 0064
1- The Calling Home RFSS considers the Serving RFSS registered for the
Calling SU.
2- The Called Home RFSS considers the Serving RFSS registered for the
Called SU.
1- The Home RFSS considers the Serving RFSS registered for the Called
SU.
Config: A
Ref: 08-092 - ISSI - Supplementary Data Conformance Test 2008-12-12
RFSS/
Replicator_Scenarios
Replicator_Home_4_1
Config: A
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
Scenario_20100401_102500Generated scenario for trace file: C: iltered.pcap
Generated scenario for trace file: C: iltered.pcap
RFSS/
MISC
SIP_ISSI_Home_GroupCall_SG_1Group 1 call setup – Successful- Home
SIP_ISSI_Home_GroupCall_SG_1_file5_newGroup 1 call setup – Successful- Home
SIP_ISSI_Home_GroupCall_SG_2Group 2 call setup – Successful- Home
SIP_ISSI_Home_GroupCall_SG_1_Two_Audio_files_With_TimingGroup call setup – Successful- Home
Serving RFSS triggers it to initiate an unconfirmed group call.
Home (Multi-Segment)
Serving RFSS 1 rfss-id : 01
Serving RFSS 1 system-id : 001
Serving RFSS 1 wacn-id : 00001
Home RFSS 2 rfss-id : 02
Home RFSS 2 system-id : 002
Home RFSS 2 wacn-id : 00002
Serving RFSS 3 rfss-id : 03
Serving RFSS 3 system-id : 003
Serving RFSS 3 wacn-id : 00003
g-id of the group : 0064
specified SG. 2- The Serving RFSS has an “Unconfirmed Group Call” RTP call segment
established with the Home RFSS.
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)
SIP_ISSI_MISC_MESSAGE_01Message
SUT: Home RFSS
Ref: TIA-102.BACA-A, TIA-102.CACC (jan 2009)

VariableDefault ValueDescription
Deregister_After_Each_TestTRUESet to TRUE to Deregister after each test.
Dst_SubscriberUnitID"sip:00004004000012@p25dr;user...The Subscriber Unit ID for the Called Serving RFSS for SU to SU calls.
Dst_SubscriberUnitDomain"04.004.00004.p25dr"The Subscriber Unit domain name for the Called Serving RFSS for SU to SU calls.
Dst_SubscriberUnitIP"192.168.0.12"The Subscriber Unit ip address for the Called Serving RFSS for SU to SU calls.
Group_ID1"0001"Group ID 1
Group_ID2"0002"Group ID 2
Group_ID3"0003"Group ID 3
Group_ID_Invalid"9999"Invalid Group ID for tests like Home_5_2
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_Use_DomainTRUE Set to TRUE if need to use Domain in messages
IP_Include_Port_In_URITRUE Set to FALSE if URI should not have IP Port
IP_Register_With_ProxyFALSE Set to TRUE if register with Proxy is required
IP_SIP_Port_SUT"5060" Port to use for testing
IP_SIP_Port_TESTER"5060" Port to use for testing
IP_SIP_Port_SUT_Link2"5060" Port to use for testing. Limited availability
IP_SIP_Port_TESTER_Link2"5060" Port to use for testing. Limited availability
Network_ID"01"Network ID
PX_Accept_Encoding_TESTER"" Accept-Encoding Tester - nt-im-2.0
PX_Accept_Language_TESTER"Accept-Language: en" Accept-Language Tester as English
PX_Algorithm"MD5"(null)
PX_Allow_TESTER"Allow: INVITE, ACK, BYE, CANC... Allow header
PX_Auto_Trigger_OFF_HOOKFALSE Automatically tear down active call
PX_Auto_Trigger_ON_HOOKFALSE Automatically answer ringing call
PX_Auto_Trigger_RESET_SUTFALSE Automatically reset SUTs current state
PX_Content_Disposition_TESTER"Content-Disposition: session;... Content disposition Tester
PX_Content_Type_TESTER"Content-Type: application/sdp... Content-type used by Tester
PX_Content_Type_Text_TESTER"Content-Type: text/plain"(null)
PX_CSeq_Base_TESTER100 Base for starting CSeq
PX_Ignore_Port_FailureFALSESet to TRUE to ignore port failures
Register_Expires_TESTER"86200" Expires value for REGISTER messages
RFSS_ID_SUT"f1"RFSS ID e.g. 02
RFSS_ID_TESTER"f2"RFSS ID e.g. 01
RFSS_ID_TESTER2"03"RFSS ID e.g. 01
RFSS_ID_Invalid"ff"Invalid RFSS ID used in error tests.
RFSS_Mode1RFSS mode. 1=ITT, 2=RC
RTP_IMBE_File_1_Name"eads_ref.imbe"Filename to play after Delay time
RTP_IMBE_File_1_Pre_Delay2000Delay time (ms) before playing file
RTP_IMBE_File_1_Post_Delay4000Delay time (ms) after playing file
RTP_IMBE_File_2_Name"itt_ref.imbe"Filename to play after Delay time
RTP_IMBE_File_2_Pre_Delay2000Delay time (ms) before playing file
RTP_IMBE_File_2_Post_Delay4000Delay time (ms) after playing file
RTP_IMBE_File_3_Name""Filename to play after Delay time
RTP_IMBE_File_3_Pre_Delay2000Delay time (ms) before playing file
RTP_IMBE_File_3_Post_Delay4000Delay time (ms) after playing file
RTP_IMBE_File_4_Name""Filename to play after Delay time
RTP_IMBE_File_4_Pre_Delay2000Delay time (ms) before playing file
RTP_IMBE_File_4_Post_Delay4000Delay time (ms) after playing file
RTP_IMBE_File_5_Name""Filename to play after Delay time
RTP_IMBE_File_5_Pre_Delay2000Delay time (ms) before playing file
RTP_IMBE_File_5_Post_Delay4000Delay time (ms) after playing file
SDP_C_Address_Type_TESTER"IP4" Address type Tester - IP4 or IP6
SDP_C_Address_Type_TESTER2"IP4" Address type Tester - IP4 or IP6
SDP_C_Network_Type_TESTER"IN" Network type Tester
SDP_C_Network_Type_TESTER2"IN" Network type Tester
SDP_M_Attribute_1_TESTER"a=rtpmap:100 X-TIA-P25-IMBE/8... P25 attribute
SDP_M_Attribute_1_TESTER2"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_2_TESTER2"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_3_TESTER2"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_4_TESTER2"a=rtpmap:4 g723.1/8000/1" Media G723.1 Attribute Tester
SDP_M_Format_1_TESTER"100" Media µ Law Tester
SDP_M_Format_1_TESTER2"100" Media µ Law Tester
SDP_M_Format_2_TESTER"8" Media A Law Tester
SDP_M_Format_2_TESTER2"8" Media A Law Tester
SDP_M_Format_3_TESTER"18" Media G729 Tester
SDP_M_Format_3_TESTER2"18" Media G729 Tester
SDP_M_Format_4_TESTER"4" Media new
SDP_M_Format_4_TESTER2"4" Media new
SDP_M_Format_New_TESTER"96"(null)
SDP_M_Format_New_TESTER2"96"(null)
SDP_M_Port_TESTER"5008" Media Port Tester
SDP_M_Port_TESTER2"5018" Media Port Tester
SDP_M_Protocol_TESTER"RTP/AVP" Media Protocol Tester
SDP_M_Protocol_TESTER2"RTP/AVP" Media Protocol Tester
SDP_Media_LawSDP_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_Address_Type_TESTER2"IP4" IP address type Tester
SDP_O_Network_Type_TESTER"IN" Network type Tester
SDP_O_Network_Type_TESTER2"IN" Network type Tester
SDP_O_Session_ID_TESTER"8521" Session ID of Tester
SDP_O_Session_ID_TESTER2"8522" Session ID of Tester
SDP_O_Username_TESTER"Valid8.com-Simulator" Username of Tester
SDP_O_Username_TESTER2"Valid8.com-Simulator" Username of Tester
SDP_O_Version_Number_TESTER"32" Version Number of Tester
SDP_O_Version_Number_TESTER2"32" Version Number of Tester
SDP_S_Session_Name_TESTER"SIP-Call" Session Name Tester
SDP_S_Session_Name_TESTER2"SIP-Call" Session Name Tester
SIP_Version_TESTERSIP_Version_2 Version used (only supports V2)
SrcRTP_Audio_Port5062(null)
SrcRTP_Audio_Port25062(null)
SrcRTP_Video_Port5064(null)
Subscriber_Group_ID_Error_5_2"sip:000020020088"Unsuccessful; RFSS is not home to the SG. Used in test 5_2
Subscriber_Group_ID_Error_5_3"sip:000020020099"Unsuccessful; SG registration is denied. Used in test 5_3
Subscriber_Unit_ID_Error_4_3"sip:00002002000008"Unsuccessful; RFSS is not home to the SU. Used in test 4_3
Subscriber_Unit_ID_Error_4_4"sip:00002002000099"Unsuccessful; SU registration is denied. Used in test 4_4
Subscriber_Unit_ID_Error_4_5"sip:00002002000099"Unsuccessful; SU is currently registered to a different RFSS. Used in test 4_5
Subscriber_Unit_ID_Error_15_3"sip:00002002000008"Unsuccessful; Tester is not authorized to receive query info for SU. Used in test 15_3
Subscriber_Unit_ID_Error_15_4"sip:00002002000099"Unsuccessful; SUT is not home to the SU. Used in test 15_4
Supported_TESTER"" Supported SIP Tester
Supported_TESTER_UE1"path"(null)
System_ID_SUT"001"System ID e.g. 002
System_ID_TESTER"002"System ID e.g. 001
System_ID_TESTER2"003"System ID e.g. 001
Tag_TESTER"tag=a3bhg" TAG used by the Tester link 1
Tag2_TESTER"tag=b4cih" TAG used by the Tester link 2
Test_Spec_VersionTIA_102_CACC_Jan_2009 Which version of the Conformance Tests to run.
T_CALL_ACTIVE_VAL5000 Call duration, time to wait for a response during an Active call
Timestamp_TESTER54 Timestamp value
T_INTERVAL_TIMER_VAL1000 Time to wait for possible INVITE retransmission
T_LENGTH_TO_SEND5000 Length of time to send RTP DTMF
T_NOACT_VAL10000 Time to wait for No activity
TRIG_Reset_SUT_String"c:\\\\trigger_reset_SUT.bat" Name of user-defined batch file to trigger phone reset
T_T1_VAL550 T1 timer
T_T1_VAL_MAX1000 T1 timer max value
T_T1_VAL_MIN300 T1 timer min value
T_T2_VAL4000 T2 timer, response timeout
T_T4_VAL5000 T4 timer, clean up timeout
T_TIMER_E_VAL500 Timer E value
T_TRANSACTION_TIMER_VAL32000 Timer B (rfc-3261) time to wait for transaction
T_WAIT_ACK_VAL5000 Time to wait for ACK request
T_WAIT_AUTOANSWER_VAL1000 Time to wait for possible autoanswer
T_WAIT_BYE_VAL30000 Time to wait for BYE request
T_WAIT_CANCEL_VAL30000 Time to wait for CANCEL request
T_WAIT_FLOOD_SEND_VAL10??????? is it in mms
T_WAIT_INVITE_VAL30000 Time to wait for INVITE request
T_WAIT_NEXT_PROV_RESPONSE_VAL3000 Time to wait for next provisional response
T_WAIT_OK_VAL30000 Time to wait for OK
T_WAIT_OPTIONS_VAL30000 Time to wait for OPTIONS request
T_WAIT_REGISTER_INTERVAL_VAL500 Time to wait for Retransmission of REGISTER request BZ 372
T_WAIT_REGISTER_VAL30000 Time to wait for REGISTER request
T_WAIT_RESPONSE_BYE_VAL30000 Time to wait for response after a BYE
T_WAIT_RESPONSE_VAL30000 Time to wait for any response after an INVITE
T_WAIT_SEND_CANCEL100 Time to wait before sending a CANCEL
T_WAIT_TRYING_VAL30000 Time to wait for TRYING
UNACCEPTABLE_PAYLOAD"Unacceptable Description" Unacceptable payload
Unit_ID1"000011"Unit ID 1
Unit_ID2"000012"Unit ID 2
Unit_ID3"000013"Unit ID 3
Unit_ID_Calling_SU"000011"Unit ID of Calling SU for 12.1 test
Unit_ID_Called_SU"000012"Unit ID of Called SU for 12.1 test
Unsupported_TESTER"REGISTER" Used to generated unsupported method message
User_Agent_TESTER"User-Agent: VALID8 RFSS ISSI ... Used to generate unsupported method message
User_Defined_1_Prefix""(null)
User_Defined_2_Prefix""(null)
USE_RTP_TQAFALSETrue = USE RTP TQA for Media
Via_bid";branch=z9hG4bK89a7" branch ID in Via
Via_Multiple_Header_TESTER"123.123.123.123:5060" Used in Test Scenario MG_TE_V_010
WACN_ID_SUT"00001"WACN ID e.g. 00002
WACN_ID_TESTER"00002"WACN ID e.g. 00001
WACN_ID_TESTER2"00003"WACN ID e.g. 00001

Copyright © ACATS Forum 2008 on behalf of the test suite author. All rights reserved. Specifications may change subject to requirements.

17 Jun 2010Produced by SAFIRE V20.05.14.01
www.SAFIRE-World.com		 Test Suite Overview