962421 - [MADAI] Support SMS Feature for MADAI

Status: RESOLVED DUPLICATE of bug 972175

(Firefox OS Graveyard :: General, defect, P1)

Description

[[e-mail]]

User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; Trident/4.0; CNS_UA; AD_LOGON=4C47452E4E4554; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.2; .NET4.0C; .NET4.0E; CNS_UA; AD_LOGON=4C47452E4E4554)

Steps to reproduce:

Unique Message Identification is requirement of vendor.

Please check below.
1. The device shall identify duplicate message using "Originating Address" and "Message Center Time Stamp".
2. The device shall send Ack for the duplicate message and discard it.

It is some kinds of duplicated message reject process.




Actual results:

Currently, 
I guess message may replaced to new message because of 
"Bug 736708- B2G SMS: Support Replace Short Message Type"


Expected results:

When received new message, check two parameter's from existing stored message : the same sender address(TP-OA) and TP-SCTS (sc time stamp) 
if new message has same sender address and TP-SCTS from old one, the received new message is determined as duplicated message 
and then discard it and send Ack to NW because We want to store one unique message.

Comment 1

[[e-mail]]

Is b2g support any duplicated-message reject process separate with Bug 736708?

Comment 2

[Wayne Chang [:wchang]]

This looks like bug 972175, which is a non-standard operator specific requirement.
I am closing off this one as a dupe to the other bug, which should be taken care of by a partner given the nature of this requirement.