Professional Documents
Culture Documents
37,50,77,79
VLR : 491720438173
Missing TC description
1-> 14,27,42,43,44,46,47,50,55,56,58,59,61->85,88,92,97->134,137,140->143,145-
>155,158,162->165
--------------------------------------------------------------------------
'TEST CASE NAME: TO09.0140-2G Combined Attach of a non VoLTE Nokia 3+2 UC Slave
Card being APD
Test Case Title: Attached to 2G of HPLMN using Slave APD activated subscriber
PRE-REQUISITES:
- we have to verify if the subscriber is provisioing with non VoLTE Nokia 3+2 UC
Slave Card
- UC 3+2 slave card should be APD device
- RSI should be "NN" state and EUINTERNET PDP context should not be selected
- Take fresh Subscriber Profile logs in PGW GUI
EXECUTION STEPS:
EXPECTED RESULTS:
- Take Subscriber post profile log in PGW CLI along with IMSI
---------------------------------------------------------------------------------
TEST CASE NAME: TO09.145- non VoLTE Nokia UC 3+2 Group - Call Forwarding change via
SCI - UC Slave Membe
Test Case Title: Change SS CF via Slave UC 3+2 group will refect all group
subscribers
PRE-REQUISITES:
EXECUTION STEPS:
EXPECTED RESULTS:
- NT HLR FE updates all 3 UC members of the non VoLTE Nokia UC 3+2 group
- TAS reads the MMTEL data via Restore Data message from Master.
- Take Subscriber post profile log in PGW CLI along with IMSI
-----------------------------------------------------------------------------------
----
TEST CASE NAME: TO09.146- non VoLTE Nokia UC 3+2 Group - Call Forwarding change via
SCI from UC Slave 1, UC Slave 2 has ODB BAOC + ODB BAIC
Test Case Title: CF change via SCI from UC Slave 1, But UC Slave 2 has ODB BAOC +
ODB BAIC
PRE-REQUISITES:
- we have to choose Non Volte UC 3+2 group slave 1 ,2 and CLI cards
- we have to check before execution steps check all activation and barring status
- Slave 2 has been ODB BAOC + ODB BAIC in Slave 2 provisioining
- CLI cards not be activated any Services
EXECUTION STEPS:
EXPECTED RESULTS:
- NT HLR FE updates all 3 UC members of the non VoLTE Nokia UC 3+2 group
- TAS reads the MMTEL data via Restore Data message from Master.
- Take Subscriber post profile log in PGW CLI along with IMSI
-----------------------------------------------------------------------------------
---------------------------
TEST CASE NAME: TO09.147 - non VoLTE Nokia UC 3+2 Group - Call Forwarding change
via SCI - CLI Member
Test Case Title: CF change via SCI from UC CLI Slave card
PRE-REQUISITES:
EXECUTION STEPS:
EXPECTED RESULTS:
TEST CASE NAME: TO09.148-non VoLTE Nokia UC 3+2 Group - Call Barring change via SCI
- UC Slave Member
Test Case Title: Call Barring change via SCI interface from UC Slave card
PRE-REQUISITES:
- we have to choose Non Volte UC 3+2 group slave card and should be activated
Barring
- we have to check status of SS and ODB Barring and forwarding all group cards
- Take fresh Subscriber Profile logs in PGW GUI
EXECUTION STEPS:
- We have to change SS Call barring number for UC Slave card in PGW GUI
EXPECTED RESULTS:
- HSS sends notification to TAS. TAS reloads the MMTEL data update via Restore Data
Message
- Take Subscriber post profile log in PGW CLI along with IMSI
Test Case Title: Call Barring change via SCI interface from UC CLI Slave card
PRE-REQUISITES:
- we have to choose Non Volte UC 3+2 group slave card and should be activated
Barring
- we have to check status of SS and ODB Barring and forwarding all group cards
- Take fresh Subscriber Profile logs in PGW GUI
EXECUTION STEPS:
- We have to change SS Call barring number for UC CLI Slave card in PGW GUI
- We will get error during modification
EXPECTED RESULTS:
- NT HLR FE will reject the SCI request with an appropriate Error Code.
- Take Subscriber post profile log in PGW CLI along with IMSI
TEST CASE NAME: TO09.150-Nokia VoLTE Ultracard 3+2 group - UC Slave - CB change via
UT
Test Case Title: Call Barring change via UT interface from UC Slave card
PRE-REQUISITES:
- we have to choose Non Volte UC 3+2 group slave card and should be activated
Barring
- we have to check status of SS and ODB Barring and forwarding all group cards
- we have to verify all group of cards status of CB and CF status
- Take fresh Subscriber Profile logs in PGW GUI
EXECUTION STEPS:
- We have to change SS Call barring number via UT interface for UC Slave card in
PGW GUI
EXPECTED RESULTS: