|
1 To: <recyclebin@msexchange2k.closedtest.intra> |
|
2 Subject: Test message No.8 - Long message (206KB) |
|
3 From: Test message <abf75@dial.pipex.com> |
|
4 Date: Thu, 20 Jan 2001 11:24:11 GMT |
|
5 |
|
6 INTRODUCTION |
|
7 |
|
8 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
9 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
10 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
11 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
12 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
13 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
14 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
15 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
16 |
|
17 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
18 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
19 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
20 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
21 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
22 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
23 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
24 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
25 |
|
26 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
27 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
28 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
29 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
30 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
31 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
32 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
33 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
34 |
|
35 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
36 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
37 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
38 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
39 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
40 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
41 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
42 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
43 |
|
44 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
45 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
46 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
47 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
48 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
49 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
50 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
51 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
52 |
|
53 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
54 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
55 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
56 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
57 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
58 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
59 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
60 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
61 |
|
62 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
63 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
64 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
65 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
66 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
67 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
68 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
69 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
70 |
|
71 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
72 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
73 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
74 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
75 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
76 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
77 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
78 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
79 |
|
80 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
81 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
82 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
83 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
84 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
85 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
86 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
87 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
88 |
|
89 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
90 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
91 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
92 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
93 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
94 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
95 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
96 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
97 |
|
98 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
99 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
100 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
101 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
102 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
103 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
104 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
105 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
106 |
|
107 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
108 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
109 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
110 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
111 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
112 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
113 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
114 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
115 |
|
116 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
117 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
118 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
119 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
120 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
121 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
122 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
123 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
124 |
|
125 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
126 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
127 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
128 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
129 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
130 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
131 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
132 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
133 |
|
134 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
135 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
136 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
137 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
138 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
139 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
140 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
141 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
142 |
|
143 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
144 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
145 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
146 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
147 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
148 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
149 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
150 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
151 |
|
152 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
153 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
154 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
155 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
156 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
157 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
158 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
159 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
160 |
|
161 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
162 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
163 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
164 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
165 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
166 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
167 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
168 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
169 |
|
170 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
171 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
172 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
173 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
174 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
175 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
176 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
177 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
178 |
|
179 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
180 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
181 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
182 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
183 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
184 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
185 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
186 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
187 |
|
188 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
189 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
190 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
191 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
192 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
193 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
194 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
195 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
196 |
|
197 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
198 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
199 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
200 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
201 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
202 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
203 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
204 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
205 |
|
206 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
207 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
208 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
209 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
210 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
211 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
212 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
213 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
214 |
|
215 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
216 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
217 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
218 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
219 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
220 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
221 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
222 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
223 |
|
224 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
225 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
226 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
227 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
228 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
229 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
230 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
231 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
232 |
|
233 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
234 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
235 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
236 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
237 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
238 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
239 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
240 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
241 |
|
242 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
243 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
244 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
245 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
246 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
247 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
248 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
249 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
250 |
|
251 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
252 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
253 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
254 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
255 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
256 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
257 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
258 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
259 |
|
260 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
261 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
262 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
263 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
264 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
265 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
266 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
267 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
268 |
|
269 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
270 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
271 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
272 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
273 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
274 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
275 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
276 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
277 |
|
278 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
279 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
280 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
281 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
282 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
283 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
284 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
285 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
286 |
|
287 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
288 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
289 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
290 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
291 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
292 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
293 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
294 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
295 |
|
296 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
297 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
298 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
299 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
300 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
301 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
302 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
303 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
304 |
|
305 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
306 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
307 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
308 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
309 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
310 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
311 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
312 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
313 |
|
314 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
315 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
316 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
317 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
318 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
319 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
320 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
321 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
322 |
|
323 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
324 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
325 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
326 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
327 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
328 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
329 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
330 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
331 |
|
332 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
333 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
334 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
335 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
336 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
337 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
338 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
339 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
340 |
|
341 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
342 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
343 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
344 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
345 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
346 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
347 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
348 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
349 |
|
350 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
351 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
352 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
353 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
354 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
355 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
356 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
357 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
358 |
|
359 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
360 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
361 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
362 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
363 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
364 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
365 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
366 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
367 |
|
368 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
369 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
370 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
371 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
372 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
373 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
374 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
375 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
376 |
|
377 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
378 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
379 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
380 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
381 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
382 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
383 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
384 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
385 |
|
386 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
387 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
388 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
389 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
390 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
391 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
392 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
393 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
394 |
|
395 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
396 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
397 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
398 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
399 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
400 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
401 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
402 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
403 |
|
404 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
405 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
406 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
407 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
408 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
409 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
410 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
411 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
412 |
|
413 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
414 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
415 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
416 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
417 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
418 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
419 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
420 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
421 |
|
422 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
423 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
424 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
425 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
426 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
427 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
428 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
429 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
430 |
|
431 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
432 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
433 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
434 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
435 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
436 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
437 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
438 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
439 |
|
440 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
441 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
442 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
443 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
444 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
445 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
446 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
447 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
448 |
|
449 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
450 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
451 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
452 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
453 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
454 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
455 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
456 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
457 |
|
458 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
459 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
460 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
461 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
462 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
463 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
464 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
465 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
466 |
|
467 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
468 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
469 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
470 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
471 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
472 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
473 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
474 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
475 |
|
476 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
477 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
478 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
479 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
480 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
481 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
482 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
483 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
484 |
|
485 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
486 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
487 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
488 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
489 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
490 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
491 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
492 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
493 |
|
494 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
495 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
496 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
497 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
498 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
499 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
500 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
501 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
502 |
|
503 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
504 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
505 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
506 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
507 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
508 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
509 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
510 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
511 |
|
512 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
513 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
514 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
515 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
516 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
517 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
518 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
519 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
520 |
|
521 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
522 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
523 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
524 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
525 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
526 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
527 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
528 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
529 |
|
530 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
531 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
532 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
533 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
534 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
535 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
536 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
537 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
538 |
|
539 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
540 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
541 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
542 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
543 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
544 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
545 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
546 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
547 |
|
548 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
549 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
550 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
551 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
552 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
553 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
554 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
555 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
556 |
|
557 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
558 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
559 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
560 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
561 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
562 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
563 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
564 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
565 |
|
566 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
567 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
568 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
569 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
570 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
571 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
572 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
573 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
574 |
|
575 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
576 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
577 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
578 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
579 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
580 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
581 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
582 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
583 |
|
584 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
585 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
586 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
587 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
588 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
589 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
590 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
591 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
592 |
|
593 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
594 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
595 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
596 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
597 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
598 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
599 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
600 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
601 |
|
602 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
603 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
604 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
605 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
606 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
607 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
608 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
609 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
610 |
|
611 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
612 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
613 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
614 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
615 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
616 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
617 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
618 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
619 |
|
620 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
621 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
622 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
623 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
624 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
625 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
626 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
627 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
628 |
|
629 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
630 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
631 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
632 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
633 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
634 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
635 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
636 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
637 |
|
638 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
639 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
640 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
641 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
642 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
643 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
644 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
645 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
646 |
|
647 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
648 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
649 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
650 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
651 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
652 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
653 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
654 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
655 |
|
656 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
657 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
658 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
659 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
660 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
661 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
662 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
663 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
664 |
|
665 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
666 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
667 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
668 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
669 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
670 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
671 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
672 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
673 |
|
674 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
675 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
676 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
677 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
678 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
679 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
680 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
681 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
682 |
|
683 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
684 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
685 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
686 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
687 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
688 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
689 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
690 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
691 |
|
692 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
693 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
694 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
695 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
696 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
697 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
698 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
699 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
700 |
|
701 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
702 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
703 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
704 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
705 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
706 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
707 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
708 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
709 |
|
710 v |
|
711 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
712 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
713 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
714 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
715 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
716 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
717 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
718 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
719 |
|
720 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
721 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
722 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
723 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
724 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
725 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
726 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
727 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
728 |
|
729 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
730 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
731 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
732 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
733 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
734 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
735 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
736 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
737 |
|
738 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
739 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
740 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
741 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
742 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
743 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
744 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
745 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
746 |
|
747 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
748 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
749 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
750 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
751 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
752 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
753 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
754 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
755 |
|
756 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
757 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
758 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
759 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
760 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
761 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
762 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
763 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
764 |
|
765 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
766 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
767 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
768 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
769 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
770 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
771 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
772 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
773 |
|
774 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
775 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
776 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
777 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
778 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
779 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
780 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
781 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
782 |
|
783 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
784 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
785 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
786 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
787 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
788 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
789 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
790 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
791 |
|
792 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
793 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
794 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
795 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
796 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
797 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
798 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
799 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
800 |
|
801 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
802 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
803 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
804 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
805 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
806 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
807 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
808 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
809 |
|
810 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
811 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
812 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
813 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
814 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
815 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
816 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
817 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
818 |
|
819 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
820 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
821 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
822 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
823 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
824 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
825 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
826 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
827 |
|
828 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
829 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
830 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
831 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
832 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
833 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
834 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
835 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
836 |
|
837 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
838 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
839 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
840 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
841 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
842 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
843 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
844 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
845 |
|
846 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
847 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
848 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
849 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
850 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
851 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
852 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
853 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
854 |
|
855 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
856 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
857 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
858 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
859 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
860 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
861 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
862 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
863 |
|
864 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
865 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
866 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
867 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
868 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
869 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
870 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
871 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
872 |
|
873 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
874 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
875 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
876 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
877 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
878 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
879 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
880 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
881 |
|
882 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
883 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
884 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
885 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
886 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
887 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
888 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
889 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
890 |
|
891 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
892 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
893 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
894 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
895 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
896 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
897 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
898 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
899 |
|
900 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
901 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
902 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
903 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
904 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
905 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
906 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
907 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
908 |
|
909 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
910 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
911 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
912 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
913 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
914 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
915 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
916 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
917 |
|
918 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
919 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
920 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
921 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
922 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
923 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
924 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
925 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
926 |
|
927 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
928 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
929 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
930 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
931 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
932 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
933 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
934 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
935 |
|
936 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
937 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
938 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
939 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
940 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
941 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
942 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
943 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
944 |
|
945 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
946 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
947 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
948 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
949 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
950 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
951 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
952 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
953 |
|
954 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
955 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
956 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
957 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
958 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
959 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
960 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
961 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
962 |
|
963 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
964 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
965 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
966 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
967 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
968 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
969 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
970 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
971 |
|
972 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
973 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
974 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
975 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
976 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
977 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
978 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
979 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
980 |
|
981 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
982 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
983 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
984 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
985 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
986 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
987 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
988 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
989 |
|
990 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
991 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
992 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
993 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
994 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
995 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
996 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
997 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
998 |
|
999 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1000 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1001 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1002 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1003 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1004 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1005 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1006 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1007 |
|
1008 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1009 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1010 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1011 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1012 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1013 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1014 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1015 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1016 |
|
1017 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1018 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1019 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1020 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1021 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1022 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1023 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1024 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1025 |
|
1026 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1027 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1028 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1029 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1030 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1031 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1032 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1033 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1034 |
|
1035 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1036 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1037 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1038 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1039 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1040 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1041 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1042 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1043 |
|
1044 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1045 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1046 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1047 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1048 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1049 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1050 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1051 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1052 |
|
1053 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1054 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1055 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1056 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1057 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1058 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1059 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1060 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1061 |
|
1062 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1063 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1064 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1065 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1066 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1067 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1068 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1069 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1070 |
|
1071 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1072 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1073 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1074 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1075 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1076 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1077 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1078 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1079 |
|
1080 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1081 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1082 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1083 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1084 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1085 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1086 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1087 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1088 |
|
1089 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1090 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1091 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1092 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1093 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1094 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1095 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1096 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1097 |
|
1098 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1099 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1100 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1101 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1102 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1103 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1104 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1105 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1106 |
|
1107 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1108 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1109 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1110 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1111 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1112 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1113 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1114 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1115 |
|
1116 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1117 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1118 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1119 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1120 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1121 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1122 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1123 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1124 |
|
1125 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1126 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1127 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1128 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1129 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1130 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1131 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1132 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1133 |
|
1134 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1135 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1136 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1137 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1138 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1139 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1140 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1141 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1142 |
|
1143 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1144 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1145 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1146 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1147 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1148 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1149 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1150 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1151 |
|
1152 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1153 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1154 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1155 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1156 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1157 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1158 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1159 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1160 |
|
1161 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1162 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1163 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1164 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1165 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1166 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1167 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1168 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1169 |
|
1170 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1171 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1172 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1173 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1174 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1175 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1176 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1177 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1178 |
|
1179 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1180 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1181 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1182 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1183 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1184 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1185 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1186 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1187 |
|
1188 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1189 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1190 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1191 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1192 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1193 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1194 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1195 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1196 |
|
1197 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1198 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1199 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1200 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1201 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1202 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1203 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1204 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1205 |
|
1206 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1207 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1208 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1209 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1210 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1211 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1212 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1213 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1214 |
|
1215 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1216 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1217 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1218 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1219 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1220 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1221 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1222 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1223 |
|
1224 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1225 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1226 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1227 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1228 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1229 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1230 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1231 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1232 |
|
1233 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1234 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1235 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1236 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1237 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1238 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1239 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1240 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1241 |
|
1242 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1243 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1244 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1245 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1246 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1247 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1248 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1249 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1250 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1251 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1252 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1253 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1254 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1255 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1256 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1257 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1258 |
|
1259 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1260 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1261 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1262 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1263 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1264 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1265 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1266 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1267 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1268 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1269 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1270 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1271 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1272 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1273 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1274 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1275 |
|
1276 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1277 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1278 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1279 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1280 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1281 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1282 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1283 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1284 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1285 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1286 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1287 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1288 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1289 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1290 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1291 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1292 |
|
1293 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1294 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1295 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1296 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1297 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1298 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1299 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1300 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1301 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1302 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1303 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1304 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1305 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1306 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1307 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1308 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1309 |
|
1310 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1311 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1312 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1313 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1314 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1315 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1316 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1317 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1318 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1319 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1320 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1321 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1322 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1323 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1324 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1325 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1326 |
|
1327 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1328 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1329 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1330 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1331 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1332 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1333 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1334 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1335 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1336 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1337 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1338 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1339 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1340 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1341 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1342 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1343 |
|
1344 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1345 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1346 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1347 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1348 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1349 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1350 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1351 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1352 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1353 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1354 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1355 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1356 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1357 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1358 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1359 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1360 |
|
1361 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1362 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1363 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1364 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1365 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1366 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1367 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1368 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1369 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1370 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1371 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1372 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1373 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1374 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1375 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1376 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1377 |
|
1378 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1379 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1380 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1381 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1382 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1383 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1384 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1385 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1386 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1387 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1388 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1389 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1390 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1391 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1392 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1393 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1394 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1395 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1396 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1397 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1398 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1399 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1400 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1401 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1402 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1403 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1404 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1405 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1406 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1407 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1408 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1409 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1410 |
|
1411 |
|
1412 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1413 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1414 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1415 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1416 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1417 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1418 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1419 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1420 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1421 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1422 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1423 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1424 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1425 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1426 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1427 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1428 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1429 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1430 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1431 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1432 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1433 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1434 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1435 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1436 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1437 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1438 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1439 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1440 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1441 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1442 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1443 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1444 |
|
1445 |
|
1446 |
|
1447 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1448 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1449 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1450 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1451 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1452 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1453 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1454 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1455 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1456 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1457 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1458 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1459 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1460 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1461 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1462 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1463 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1464 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1465 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1466 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1467 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1468 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1469 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1470 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1471 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1472 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1473 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1474 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1475 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1476 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1477 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1478 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1479 |
|
1480 |
|
1481 |
|
1482 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1483 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1484 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1485 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1486 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1487 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1488 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1489 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1490 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1491 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1492 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1493 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1494 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1495 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1496 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1497 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1498 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1499 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1500 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1501 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1502 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1503 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1504 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1505 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1506 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1507 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1508 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1509 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1510 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1511 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1512 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1513 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1514 |
|
1515 |
|
1516 |
|
1517 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1518 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1519 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1520 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1521 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1522 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1523 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1524 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1525 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1526 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1527 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1528 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1529 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1530 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1531 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1532 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1533 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1534 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1535 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1536 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1537 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1538 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1539 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1540 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1541 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1542 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1543 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1544 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1545 The existing MTM used to perform logging in order to generate a Log-Id necessary for keeping track with status reports. However the CDMA specification |
|
1546 defines a Message Identifier that gets generated from the stack, therefore logging in CDMA only occurs in the SMS Stack and not in the Server MTM. This |
|
1547 leads to the restriction of messaging to perform any logging. But this can be an acceptable loss as the only state that the stack will not be able to know is |
|
1548 the re-schedule, but that information can be regarded as non-essential, since the fact that the message is rescheduled can be found in the TMsvEntry. |
|
1549 |
|
1550 |
|
1551 |
|
1552 End of message. |
|
1553 |