Tickets :: [#4464] Alert 222 NEXT MESSAGE in SyncML

6.0.0-beta1

9/24/25

Summary	Alert 222 NEXT MESSAGE in SyncML
Queue	Synchronization
Type	Enhancement
State	Resolved
Priority	1. Low
Owners	karsten (at) horde (dot) org
Requester	alex.masidlover (at) axiomtech (dot) co (dot) uk
Created	09/25/2006 (6939 days ago)
Due
Updated	10/28/2006 (6906 days ago)
Assigned	09/27/2006 (6937 days ago)
Resolved	10/28/2006 (6906 days ago)
Milestone
Patch	No

10/28/2006 02:50:05 PM	Karsten Fourmont	Comment #5 State ⇒ Resolved	Reply to this comment
There's an update for the NextMessage issue in cvs now. This should fix it.

10/26/2006 07:09:54 AM	Karsten Fourmont	Comment #4	Reply to this comment
So the NEXT_ALERT seems to be fixed. But there are still issues with the packet length. Those were reported on the list as well. I 'll look into this.

09/29/2006 12:04:50 PM	alex (dot) masidlover (at) axiomtech (dot) co (dot) uk	Comment #3 New Attachment: syncml_12.xml	Reply to this comment
Have tested against m600i - first attempt failed. Server produced its first full data response and sent it, phone then didn't respond - I've had this happen with my hacked fix and I think it might be the m600i rather than horde... The last log lines from the server are: Sep 29 12:47:23 HORDE [debug] [horde] SyncML: add: 20060809T174831Z-5148-1001-1-1@enoch [on line 268 of "/usr/share/php/SyncML/Sync.php"] Sep 29 12:47:23 HORDE [debug] [horde] SyncML: max message size reached cursize=6731 [on line 281 of "/usr/share/php/SyncML/Sync.php"] Sep 29 12:47:23 HORDE [debug] [horde] SyncML: SyncML: return message completed [on line 377 of "/usr/share/php/SyncML.php"] I've also attached the last packet from each of the server and client (accidentally deleted the wbxml unfortunately - only had the raw XML) and a packet from the middle of a succesful session. However the second attempt worked perfectly - many thanks. Unfortunately the phone is packed up to be returned (I unpacked it for the tests) however I plan on ordering myself a sim free one in a few weeks so will be using it daily when that happens and will report if the first issue recurrs.

09/29/2006 11:06:18 AM	Karsten Fourmont	Comment #2	Reply to this comment
Enhanced this patch to produce valid status response. It's in CVS right now. Please test.

09/27/2006 11:57:20 AM	Jan Schneider	Assigned to Karsten Fourmont State ⇒ Assigned

09/25/2006 06:49:37 PM	alex (dot) masidlover (at) axiomtech (dot) co (dot) uk	Comment #1 Priority ⇒ 1. Low Type ⇒ Enhancement Summary ⇒ Alert 222 NEXT MESSAGE in SyncML Queue ⇒ Synchronization New Attachment: alert_222_example.xml State ⇒ New	Reply to this comment
The Alert 222 (NEXT MESSAGE) is sent by the SonyEricsson m600i and is not handled by the current implementation of Alert.php. I have attached the example request from the device - if you need the server response that generated this request then I can provide that too. In the meantime I have modified SyncML/Command/Alert.php to contain the following at the top of the handleCommand function: if($this->_alert == ALERT_NEXT_MESSAGE) { return; } and the synchronisation simply continues.