Mercurial Mercurial > oss > MCL > sf > app > messaging / diff
summary | shortlog | changelog | graph | tags | bookmarks | branches | files | changeset | file | latest | revisions | annotate | diff | comparison | raw | help
Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
email/pop3andsmtpmtm/smtpservermtm/test/data/RFC82208.TXT
changeset 0 72b543305e3a 
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/email/pop3andsmtpmtm/smtpservermtm/test/data/RFC82208.TXT	Thu Dec 17 08:44:11 2009 +0200
@@ -0,0 +1,1553 @@
+To: <recyclebin@msexchange2k.closedtest.intra>
+Subject: Test message No.8 - Long message (206KB)
+From: Test message <abf75@dial.pipex.com>
+Date: Thu, 20 Jan 2001 11:24:11 GMT
+
+INTRODUCTION
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+v
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+
+
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification
+ defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This 
+leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is 
+the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry.
+
+
+
+End of message.
+
MCL/sf/app/messaging