TeleDNA SMSC Acceptance Test Plan Unitech

Acceptance Test Plan
Short Message Service Centre (SMSC)

to Unitech Wireless
Page 1 of 30
Creation and Revision History:
Date Author Subject/Comment Version

15 Aug 2009 TeleDNA Initial Creation 1.0
Page 2 of 30
1. Hardware test cases ................................................................................................... 4
2. System Test ................................................................................................................. 8
3. Sign off sheet ............................................................................................................. 29
Page 3 of 30
1. Hardware test cases
Test Case 1: Hardware Check
Test Description:
This test is to verify the number of servers and other hardware quantities including cable
connections.
Test Procedure:
• Verify the number of Servers, Switches etc against the approved BoM
• Verify cabling and power supply.
Expected Result:
• All Hardware quantities are as per the approved BoM
• All the LAN cable, Power Supply connections are proper.
Test Case Sign-OFF Unitech TeleDNA Date

Passed
Failed
Test Case 2: Hardware Power ON & Booting
Test Description:
This test is to verify the system hardware is successfully powered ON
Test Procedure:
• Switch on the Power supply from Mains
• Boot up the servers.
Expected Result:
• All servers should power ON properly
• System should boot properly.

Passed
Failed
Test Case 3: Power Redundancy
Page 4 of 30
Test Description:
This test is to verify that the servers are connected with redundant power and failure of a single
power channel does not power down the entire server.
Test Procedure:
• Ensure that both the power supplies are connected to all the servers and powered on.
• Switch off power channel A
• Switch on power channel A
• Switch off power channel B
• Switch on power channel B
Expected Result:
• Redundant power supply will take over and provide the power to the servers.
• The server does not switch off in case of a single power channel failure.

Passed
Failed
Page 5 of 30
Test case 4: System health diagnostics and performance monitoring
Test Description:
This test is to verify that TeleDNA SMSC provides interface for system health diagnostics and
performance monitoring.
Test Procedure:
• Login to the SMSC Portal as administrator with valid username and password.
• Access the MIS Reports page and verify the following
o Short Message Delivery Failure Statistics
o General SMSC statistics
o Hourly CDR based statistics
Expected Result:
• The Network Errors and System Errors can be verified using the “Short Message
Delivery Failure Statistics”.
• The performance of the SMSC can be monitored using the “General SMSC statistics”
and “Hourly CDR based statistics” reports.

Passed
Failed
Test case 5: User authority/ Administration Management
Test Description:
This test is to verify that the SMSC has an Administration Account who can create users and
assign specific access to the users.
Test Procedure:
• Login to the SMSC Portal as Administrator with valid user name and password.
• Create Support User from the Portal and assign access to specific option to the Support
User.
• Login to the SMSC Portal as Support User with the username and password created by
the admin and verify that only the options provided to the Support User are accessible.
Expected Results:
• Support User login is created and assigned options are visible to the Support User.

Passed
Failed
Page 6 of 30
Test case 6: Log/ Audit
Test Description:
This test is to verify that the SMSC generates a Log for the activities performed by the Users of the
SMSC Portal.
Test Procedure:
• Login to the SMSC Portal as Support User with valid user name and password.
• Provision a subscriber using SMSC Portal.
• Verify the Audit Log file generated for this Support User
Expected Results:
• Audit Log contains the activities performed by the Support User.

Passed
Failed
Page 7 of 30
2. System Test
Test case 7: System Status Check
Test Description:
This test is to verify that the status of SMSC Servers and SIGTRAN Association can be viewed
through SMSC Portal.
Test Procedure:
• Access “RAMTÆSystem Health Check” for viewing the status of ESME-Gw Servers.
• Access “RAMTÆ System Health Check” for” for viewing the status of SMS-Proc Servers.
• Access “RAMTÆ System Health Check” for” for viewing the status of SIGTRAN-Gw
Servers.
• Ping the nodes connected to the SMSC and verify that the nodes are reachable by issuing
the command “ping IP-Address”.
Expected Results:
• The status of SMSC Servers and can be viewed.
• All the nodes connected to the SMSC are reachable.

Passed
Failed
Test case 8: Charging Management
Test Description:
This test is to verify successful charging for prepaid numbers for successful delivery of messages
to valid mobile numbers.
Test Procedure:
• Send a message from Mobile-A to Mobile-B.
Expected Result:
• Message is delivered to Mobile-B
• Mobile-A is charged.

Passed
Failed
Page 8 of 30
Test case 9: Defining a New Level (No. series) or GT in the MAP and SMPP
files
Test Description:
This test is to verify that new level or GT can be configured in the SMSC using SMSC Portal.
Test Procedure:
• Login to the SMSC Portal as Administrator using valid username and password.
• Access “SMSC Administration ÆNetwork range Configuration Æ Current Operator NID
• Modify an existing ESME-A in the SMSC and configure the newly added range.
• Provision Mobile-A (belonging to the newly added range) in the SMSC.
• Submit a message from ESME-A to Mobile-A.
Expected Result:
• Message is delivered to Mobile-A.

Passed
Failed
Page 9 of 30
Test case 10: SMS from Prepaid and Postpaid roamed out subscriber
Test Description:
This test is to verify that prepaid and post-paid roamed out subscribers are able to send messages
and charged appropriately.
Test Procedure:
• Ensure Mobile –A and Mobile-B are roaming out of the HPLMN.
• Send a message from Mobile-A to Mobile-C.
• Send a message from Mobile-B to Mobile-C.
Expected Result:
• Message is successfully delivered to Mobile-C in both the cases.
• Mobile-A is charged as per the roaming plan.
• SMSC generates a Postpaid CDR with calling number as Mobile-B, called number as
Mobile-C, originating MSC address, destination MSC address.
• Billing Server will charge Mobile-B based on the information provided in CDR.

Passed
Failed
Test case 11: MO SMS to Local, National and International subscribers
Test Description:
This test is to verify that prepaid and post-paid subscribers are able to send messages to local,
national and international mobile phones and charged appropriately.
Test Procedure:
• Send a message from Mobile-A to Local, National and International numbers.
• Send a message from Mobile-B to Local, National and International numbers.
Expected Result:
• Message is successfully delivered to Local, National and International numbers in both the
cases.
• SMSC will send a appropriate parameter to IN for Charging
• SMSC generates Postpaid CDRs with calling number as Mobile-B, called number as
Local, National and International numbers respectively along with originating MSC address
and destination MSC address.
• Billing Server will charge Mobile-B based on the information provided in CDRs.

Passed
Failed
Page 10 of 30
Test Case 12: MO SMS to temporarily unavailable subscribers stored in the
SMSC.
Test Description:
This test is to verify that the messages sent to temporarily unavailable subscribers stored in the
SMSC.
Test Procedure:
• Send a message from Mobile-A to switched off Subscriber
• Login to SMSC Portal as Administrator using valid username and password.
• Access “SMSC Administration ÆMessage Query”
• Provide the source address as Mobile-A and click on submit.
• Verify that the messages submitted to Subscribers
• Verify that the messages submitted to Local, National and International numbers are
available in the SMSC Database.
Expected Result:
• The messages submitted to temporarily unavailable subscribers are available in the SMSC
Database.

Passed
Failed
Test Case 13: MO SMS to subscribers available sometime after message

submission
Test Description:
This test is to verify that the messages sent to temporarily unavailable mobile phones are delivered
successfully after switching the mobiles on.
Test Procedure:
• Send a message from Mobile-A to switch off Subscriber
• Switch on the local, national and international numbers 5 minutes after the message
submission.
Expected Result:
• The messages submitted to Local, National and International numbers are delivered
successfully.

Passed
Failed
Test Case 14: MO SMS up to 160 characters
Test Description:
This test is to verify successful delivery of short messages which are less than or equal to 160
characters to valid mobile numbers.
Page 11 of 30
Test Procedure:
• Send MO message less than or equal to 160 characters from Mobile-A to Mobile-B.
Expected Result:

Passed
Failed
Test Case 15: MO SMS more than 160 characters
Test Description:
This test is to verify that the short message more than 160 characters is delivered to the
destination mobile.
Test Procedure:
• Compose a message on Mobile-A with more than 160 chars (around 200 chars).
• Send the composed message from Mobile-A to Mobile-B.
Expected Result:
• Message is delivered to Mobile-B.
• SMSC generates CDR with the status of the message as Delivered with composed
message length

Passed
Failed
Page 12 of 30
Test Case 16: MO-SMS to wrong subscriber number (1-digit missing)
Test Description:
This test is to verify messages not delivered to the mobile numbers with 1 digit missing
Test Procedure:
• Send MO message from Mobile-A to Mobile-B with one digit of Mobile-B missing.
Expected Result:
• Message will not be delivered to Mobile-B.
• SMSC generates CDR with the status of the message as Undelivered.

Passed
Failed
Test Case 17: MO SMS without Delivery Report
Test Description:
This test is to verify successful delivery of messages to mobile numbers without delivery report
enabled.
Test Procedure:
• Disable delivery report in Mobile -A
• Send MO message from Mobile-A to Mobile-B.
Expected Result:
• Delivery Report is not delivered to Mobile-A.

Passed
Failed
Page 13 of 30
Test Case 18: MO SMS with Delivery Report
Test Description:
This test is to verify successful delivery of messages to mobile numbers with delivery report
enabled.
Test Procedure:
• Enable delivery report in Mobile -A
• Send MO message from Mobile-A to Mobile-B.
Expected Result:
• Message is delivered to Mobile-B.
• Delivery report is delivered to Mobile-A.

Passed
Failed
Test Case 19: Barring of other operator subscribers to use SMSC
Test Description:
This test is to verify that only UNITECH subscribers can use UNITECH-SMSC.
Test Procedure:
• Ensure Mobile-A is other operator subscriber.
• Ensure that only UNITECH mobile ranges are configured in the SMSC as current operator
ranges.
• Change the Service Center Address in the handset of Mobile-A to UNITECH Service
Center Address.
• Send a message from Mobile-A to any number.
Expected Result:
• Message is not accepted by the SMSC.
• SMSC generates CDR with the status of the message as Undelivered

Passed
Failed
Page 14 of 30
Test Case 20: MO SMS during originator busy for Voice and MT SMS during
recipient busy for Voice
Test Description:
This test is to verify that the SMSC is capable of performing MO SMS during originator busy for
Voice and MT SMS during recipient busy for Voice.
Test Procedure:
• Call from Mobile-A to Mobile-B.
• Send Message from Mobile-A to Mobile-B
Expected Result:
• Message from Mobile-A is delivered to Mobile-B

Passed
Failed
Test Case 21: Test for destination address restriction on Content Provider
Test Description:
This test is to verify the non delivery of the short message when the ESME sends messages to a
Mobile range not allowed.
Test Procedure:
• Ensure ESME-A provisioned in SMSC and do not configure Mobile-A NID range for
EMSE-A.
• Send Message from ESME-A to Mobile-A.
Expected Result:
• Message will not be delivered to Mobile-A

Passed
Failed
Page 15 of 30
Test Case 22 : Regional Barring
Test Description:
This test is to verify for that subscribers can be barred from sending the messages from a
particular MSC region.
Test Procedure:
• Login to SMSC portal using Administrator using valid login and password.
• Using “SMSC Administration-->Regional Barring --> MSC Wise”
• Ensure that Mobile-A is under MSC-1 and Mobile-B is not under MSC-1.
• Send message from Mobile-A to Mobile-B
Expected Result:
• Message is not delivered to Mobile-B

Passed
Failed
Test Case 23: Alternate Routing
Test Description:
This test is to verify delivery of short message over alternating routing.
Test Procedure:
• Bring down the association of one STP.
• Send message from Mobile-A to Mobile-B.
Expected Result:

Passed
Failed
Page 16 of 30
Test Case 24: Sending Message from Portal (Admin)
Test Description:
This test is to verify SMSC provides Portal interface for sending messages.
Test Procedure:
• Login to the SMSC Portal as Admin with valid username and password.
• Click on the link “SMSC Administration-->Admin Send SMS”.
• Send Message to Mobile-A
Expected Result:

Passed
Failed
Test case 25: Viewing a Message
Test Description:
This test is to verify SMSC supports to view messages accepted by the SMSC.
Test Procedure:
• Send Message to Mobile-A to Mobile-B.
• Access “SMSC Æ Message Query”, provide Mobile-A as source address, Mobile-B as
destination address and click on submits
Expected Result:
• Status of Messages sent from Mobile-A to Mobile-B will be displayed.

Passed
Failed
Test case 26: Accept/ Delete Message
Test Description:
This test is to verify SMSC supports deletion of pending messages.
Test Procedure:
• Switch off Mobile-B.
• Send Message from Mobile-A to Mobile-B.
• Access “SMSC Æ Message Query”, provide Mobile-A as source addresses, Mobile-B as
destination address and click on submits.
• The message sent from Mobile-A to Mobile-B is displayed.
• Select message and click on delete button.
Page 17 of 30
Expected Result:
• Message will be deleted from the SMSC and not delivered to Mobile-B.

Passed
Failed
Test case 27: Display filtered list of messages
Test Description:
This test is to verify that SMSC is capable of displaying messages based on filters.
Test Procedure:
• Send Message to Mobile-A to Mobile-B, Mobile-C and Mobile-D.
• Login to the SMSC Portal as Administrator with valid username and password.
• Access “SMSCÆ Message Query”, provide Mobile-A as source address and click on
submits
Expected Result:
• Message details of all the messages originated from Mobile-A will be displayed.

Passed
Failed
Test case 28: Subscriber Management
Test Description:
This test is to verify the creation/ deletion/ modification/ viewing of subscribers in SMSC.
Test Procedure:
• Login to Admin page of SMSC GUI using valid user name and password.
• Provisioning-->Mobile Subscriber Provisioning-->Add Subscriber
• Provisioning-->Mobile Subscriber Provisioning-->Modify Subscriber
• Provisioning-->Mobile Subscriber Provisioning-->Delete Subscriber
• Provisioning--> General Reports -->Single Subscriber Details
Expected Result:
• SMSC Administrator is able to create/ delete/ modify/ view subscribers on the SMSC.

Passed
Page 18 of 30
Failed
Test case 29: Check for alarm generation on SMSC GUI
Test Description:
This test is to verify that the SMSC supports alarm generation, display of alarms through Portal &
Email
Test Procedure:
• Configure a valid e-mail id on the SMSC to which the alarm has to be transferred.
• Bring down one SMS-Proc Server.
• Access “RAMT ->System Health Check->SMSC Alarms
Expected Result:
• Alarms are displayed on the SMSC Portal.

Passed
Failed
Test case 30: Hardware Alarms
Test Description:
This test is to verify that the servers are capable of generating alarms if any of the redundant
power supply fails.
Test Procedure:
• Ensure that both the power supplies are connected to all the servers and powered on.
• Switch off power channel A.
• Switch on power channel A after few minutes.
Expected Result:
• Verify that the alarm LED is set on the servers when the power channel A is switched off.
• Verify that the alarm is cleared after the power channel A is switched on.

Passed
Failed
Page 19 of 30
Test case 31: Configuration Management
Test Description:
This test is to verify that the SMSC is capable of displaying the existing configurations and
modification of the configurations.
Test Procedure:
• Login to the SMSC Portal as Administrator with valid username and password.
• SMSC Portal displays the current setting for Delivery Report.
• Modify the Delivery Report option to enable.
• Send a message from Mobile-A to Mobile-B with delivery report enabled on Mobile-A.
• Modify the Delivery Report option to disable.
• Send a message from Mobile-A to Mobile-B with delivery report enabled on Mobile-A.
Expected Result:
• Message is delivered to Mobile-B and delivery report is delivered to Mobile-A.
• Message is delivered to Mobile-B and delivery report is not delivered to Mobile-A.
Passed
Failed
Test case 32: SSTP association Creation and troubleshooting the faults
related with the association
Test Description:
• This test is to verify SSTP association creation on the SMSC and to troubleshoot
the faults related with the association.
Test Procedure:
• Create a new SIGTRAN association in the SIGTRAN-GW Servers towards SSTP.

• Restart the SIGTRAN-GW Server to activate the newly created SIGTRAN association.
• Access “RAMTÆ System Health Check ÆSIGTRAN GW Server ÆSAssociation Status”
for viewing the status of SIGTRAN Association.
Expected Result:
• SIGTRAN association is created between SMSC and the SSTP.
• SIGTRAN status can be verified through the GUI and if the association is not established,
and the SCTP status is “Down”.

Passed
Failed
Page 20 of 30
Test case 33: SUA association redundancy
Test Description:
This test is to verify that the SMSC is connected to the SSTP with redundant SIGTRAN
associations.
Test Procedure:
• Ensure Association-A and Association-B are created between SMSC and SSTP and the
status is “UP”.
• Bring down Association-A on the SSTP.
Expected Result:
• Message is delivered to Mobile-B even if the Association-A is down.

Passed
Failed
Test case 34: Automatic transfer of billing files to billing server
Test Description:
This test is to verify that SMSC is capable of transferring the CDR files to the billing server as per
the time configured on the SMSC over FTP.
Test Procedure:
• Set the cronjob in the SMSC system as per the requirement to transfer the CDRs to Billing
System over FTP.
Expected Result:
• CDR files are transferred to billing server at regular intervals as configured.

Passed
Failed
Test case 35: Delivery of SMS from ESME to Mobile and Mobile to ESME
over SMPP v3.4
Test Description:
This test is to verify the following
1) Sending message from SMPP Application to Mobile.
2) Sending message from Mobile to SMPP Application with Notification Request.
3) Sending message from Mobile to SMPP Application without Notification Request.
Test Procedure:
a. Sending message from ESME-A to Mobile-A
Page 21 of 30
• Ensure ESME-A is provisioned in SMSC database as transceiver or transmitter.
• Ensure ESME-A is BINDed to SMSC.
• Ensure Mobile-A belongs to configured allowed NID range for the ESME.
• Send a message from ESME-A to Mobile-A.
b. Sending message from Mobile-A to ESME-A with notification request

• Ensure ESME-A is BINDed to SMSC
• Ensure delivery report option is enabled in Mobile-A.
• Send message from Mobile-A to ESME-A.
c. Sending message from Mobile-A to ESME-A with out notification request

• Ensure ESME-A is BINDed to SMSC.
• Ensure delivery report option is disabled in Mobile-A.
• Send message from Mobile-A to ESME-A.
Expected Result:
• Case a: Message is delivered to Mobile-A.
• Case b: Message is delivered to ESME-A and Delivery Report is sent to Mobile-A.
• Case c: Message is delivered to ESME-A and Delivery Report is not sent to Mobile-A.

Passed
Failed
Page 22 of 30
Test case 36: Sending Message using broadcast Mode
Test Description:
This test is to verify SMSC is capable of sending messages in broadcast mode.
Test Procedure:
• Access “SMSCÆSMS Broadcast”.
• Attach a file which contains Mobile-A, Mobile-B, Mobile-C and Mobile-D numbers
separated by new line character and file extension as “.txt”
• Compose the short message on SMSC Portal and click on submit.
Expected Result:
• Message is delivered to Mobile-A, Mobile-B, Mobile-C and Mobile-D.

Passed
Failed
Test case 37: Message Validity Period
Test Description:
This test is to verify expiry of message after validity of the message is over.
Test Procedure:
• Ensure that an ESME-A is BINDed to the SMSC as transceiver.
• Switch off Mobile-A
• Send a message from ESME-A to Mobile-A with validity period set to 5 minutes.
• Switch on the Mobile-A after 6 minutes.
Expected Result:
• Message is not delivered to Mobile-A.
• SMSC generates a CDR with status as Expired.

Passed
Failed
Test case 38: Delivery receipt to ESME
Test Description:
This test is to verify that the SMSC is capable of sending the Delivery Receipt to an ESME
Test Procedure:
• Ensure that ESME-A is BINDed to SMSC.
• Enable delivery receipt in ESME-A.
Page 23 of 30
• Send a message from ESME-A to Mobile-A
Expected Result:
• Delivery Receipt is sent to ESME-A.

Passed
Failed
Test case 39: Memory Capacity Exceeded Notification
Test Description:
This test is to verify that the SMSC is capable of intimating the HLR that the Memory Capacity on
the destination mobile is exceeded.
Test Procedure:
Case-1:
• Ensure that Mobile-B Memory Capacity has exceeded.
Case-2:
• Clear some messages from inbox of mobile-B.
Expected Result:
• Case-1: Memory capacity exceeded notification will be sent to the HLR.
• Case-2: Message will be delivered to Mobile-B.

Passed
Failed
Test case 40: Binary Data Support
Test Description:
This test is to verify delivery of binary data message.
Test Procedure:
• Ensure ESME-A is BINDed to the SMSC.
• Send a binary message (ring tone/ picture message) from ESME-A to Mobile-A.
Expected Result:
• Binary message is delivered to Mobile-A

Passed
Failed
Page 24 of 30
Test case 41: Address Validation and Translation
Test Description:
This test is to verify that the SMSC is capable of performing Address Validation and Translation.
Test Procedure:
Address Translation:
• Send message from Mobile-A to
a. Mobile-B without country code.
b. Mobile-B with leading “0” without country code.
c. Mobile-B with country code.
Expected Result:
• All the three messages are delivered to Mobile-B

Passed
Failed
Test case 42: Throughput Regulation
Test Description:
This test is to verify that the SMSC is capable of regulating the throughput.
Test Procedure:
• Ensure ESME-A is provisioned in the SMSC with licensing of 1 SMS/sec.
• Send 2 messages continuously within a second from ESME-A to Mobile-A.
Expected Result:
• Only one message is delivered to Mobile-A.
• The second message is throttled on the SMSC and appropriate response is sent back to
ESME.

Passed
Failed
Page 25 of 30
Test case 43: CDR generation in SMSC
Test Description:
This test is to verify that SMSC is capable of generating the CDRs for all transactions by capturing
the required parameters in the CDRs.
Test Procedure:
• Send a message from Mobile-A to Mobile-B
• Ensure Mobile-C is switched off.
• Ensure the retry attempt for absent subscriber is set to 1 attempt for 1 minute.
• Ensure Mobile D is an invalid Destination address
• Send a message from Mobile-A to Mobile-C. Wait for a minute.
• Send a message from Mobile-A to Mobile-D.
Expected Result:
• Message is delivered from Mobile-A to Mobile-B.
• Message is not delivered to Mobile-C and the message status is expired.
• Message is not delivered to Mobile-D and the message status is undelivered.
• CDRs are generated with source address, destination address; submit time, delivery time,
originating interface, destination interface, delivery status etc.

Passed
Failed
Test case 44: ASCII commands for administration and verification
Test Description:
This test is to verify that the SMSC is capable of supporting ASCII commands to verify the ESME
bind status.
Test Procedure:
• Ensure that the SMSC is operational and few ESMEs are provisioned in the SMSC.
• Execute the command “./display_esme_bind_status.sh” under “/home/sms/SMSC-VS-
2.0.7.0/bin” directory.
Expected Result:
• ESME bind status is stored in the file “ESMEGW-ESME-BIND-STATUS”.

Passed
Failed
Page 26 of 30
Test case 45: HTTP Provisioning Interface Support
Test Description:
This test is to verify that the SMSC is capable of provisioning subscribers through the provisioning
system.
Test Procedure:
• Ensure that Provisioning System is integrated with the SMSC.
• Ensure that Mobile-A is not provisioned in the SMSC.
• Send a provisioning request from the Provisioning System to the SMSC for Mobile-A
Expected Result:
• Mobile-A is provisioned in the SMSC and can send short messages.

Passed
Failed
Test case 46: ESME Provisioning
Test Description:
This test is to verify provisioning/configuration of ESMEs in SMSC
Test Procedure:
• Login to SMSC Portal as Administrator with valid user name and password.
• Access “SMSCÆProvisioning --> ESME Provisioning-->SMS Based ESME
Expected Result:
• SMSC Administrator is able to provision the ESMEs in SMSC.

Passed
Failed
Test case 47: Local language support on SMSC
Test Description:
This test is to verify that the short message can be sent to other mobiles in the local language
(Hindi) supported by the mobiles.
Test Procedure:
• Ensure Mobile-A and Mobile-B support the Hindi regional language.
• Compose a message on Mobile-A in Hindi language.
• Send the composed message from Mobile-A to Mobile-B.
Expected Result:
Page 27 of 30
• Hindi language message is delivered to the Mobile-B

Passed
Failed
Page 28 of 30
3. Sign off sheet
Test case No Passed Failed Unitech TeleDNA

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
Page 29 of 30
Summary:
Total number of test cases :

No of test cases Passed :
No of test cases Failed :
(End of Document)
Page 30 of 30

TeleDNA SMSC Acceptance Test Plan Unitech

Enviado por

Dados do documento

Descrição original:

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

TeleDNA SMSC Acceptance Test Plan Unitech

Enviado por

Direitos autorais:

Formatos disponíveis

Acceptance Test Plan

Short Message Service Centre (SMSC)

Date Author Subject/Comment Version

Test Case 1: Hardware Check

Test Case Sign-OFF Unitech TeleDNA Date

Test Case 2: Hardware Power ON & Booting

Test Case Sign-OFF Unitech TeleDNA Date

Test Case 3: Power Redundancy

Test Case Sign-OFF Unitech TeleDNA Date

Test Case Sign-OFF Unitech TeleDNA Date

Test case 5: User authority/ Administration Management

Test Case Sign-OFF Unitech TeleDNA Date

Test Case Sign-OFF Unitech TeleDNA Date

Test case 7: System Status Check

Test Case Sign-OFF Unitech TeleDNA Date

Test case 8: Charging Management

Test Case Sign-OFF Unitech TeleDNA Date

Test Case Sign-OFF Unitech TeleDNA Date

Test Case Sign-OFF Unitech TeleDNA Date

Test case 11: MO SMS to Local, National and International subscribers

Test Case Sign-OFF Unitech TeleDNA Date

Test Case Sign-OFF Unitech TeleDNA Date

Test Case 13: MO SMS to subscribers available sometime after message

Test Case Sign-OFF Unitech TeleDNA Date

Test Case 14: MO SMS up to 160 characters

Test Case Sign-OFF Unitech TeleDNA Date

Test Case 15: MO SMS more than 160 characters

Test Case Sign-OFF Unitech TeleDNA Date

Test Case Sign-OFF Unitech TeleDNA Date

Test Case 17: MO SMS without Delivery Report

Test Case Sign-OFF Unitech TeleDNA Date

Test Case Sign-OFF Unitech TeleDNA Date

Test Case 19: Barring of other operator subscribers to use SMSC

Test Case Sign-OFF Unitech TeleDNA Date

Test Case Sign-OFF Unitech TeleDNA Date

Test Case Sign-OFF Unitech TeleDNA Date

Test Case Sign-OFF Unitech TeleDNA Date

Test Case 23: Alternate Routing

Test Case Sign-OFF Unitech TeleDNA Date

Test Case Sign-OFF Unitech TeleDNA Date

Test case 25: Viewing a Message

Test Case Sign-OFF Unitech TeleDNA Date

Test case 26: Accept/ Delete Message

This test is to verify SMSC supports deletion of pending messages.

Test Case Sign-OFF Unitech TeleDNA Date

Test case 27: Display filtered list of messages

Test Case Sign-OFF Unitech TeleDNA Date

Test case 28: Subscriber Management

Test Case Sign-OFF Unitech TeleDNA Date

Test case 29: Check for alarm generation on SMSC GUI

Test Case Sign-OFF Unitech TeleDNA Date

Test case 30: Hardware Alarms

Test Case Sign-OFF Unitech TeleDNA Date

• Create a new SIGTRAN association in the SIGTRAN-GW Servers towards SSTP.

Test Case Sign-OFF Unitech TeleDNA Date

Test Case Sign-OFF Unitech TeleDNA Date

Test case 34: Automatic transfer of billing files to billing server

Test Case Sign-OFF Unitech TeleDNA Date

b. Sending message from Mobile-A to ESME-A with notification request

c. Sending message from Mobile-A to ESME-A with out notification request

Test Case Sign-OFF Unitech TeleDNA Date

Test Case Sign-OFF Unitech TeleDNA Date

Test case 37: Message Validity Period