© 2008 The Calendaring and Scheduling Consortium, Inc.
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from the address below.
The Calendaring and Scheduling Consortium, Inc.
4390 Chaffin Lane
McKinleyville
California 95519
United States of America
www.calconnect.org
This document incorporates by reference the CalConnect Intellectual Property Rights, Appropriate Usage, Trademarks and Disclaimer of Warranty for External (Public) Documents as located at
.
This was the first Mobile Calendar Interoperability testing event held by CalConnect. There was a predetermined set of objects to test. It was determined early one that the testing document was quite comprehensive and would never be completed in the two days we had for interop testing. Therefore, the testing parties elected to choose several items from each testing group for interoperability testing. You can find the full test suite at the following url:
Two servers and one phone device were tested. For purposes of anonymity, the names of the vendors are not referenced in this document.
Part I — Calendar Tests
OK except for:
Server to client alarm issue: Server created an alarm on device side regardless if server event has an alarm. This is the default behavior by design and alarms can be turned off by changing server configurations.
Truncation issue: On device modify the location only. When sync’d back to server, the location was restored with the long original value. The un-modified title was truncated on server. Seems to be a bug on server. Need more investigation.
Device does not support priority.
OK
OK
OK
X-PHONEOWNER issue in device vCalendar:
Device in some cases put X-PHONEOWNER as one parameter of the attendee indicating that the attendee is the phone owner. X-PHONEOWNER doesn’t have a value and this breaks the server parser. Server should handle this.
OK except for:
Client to Server alarm issue: Server didn’t create an alarm on server side regardless if device event has an alarm. Device did include alarm in the vCalendar, however importing the vCalendar to a calendaring client supporting vcalendar didn’t result in an alarm either. Need more investigation. Following is the vCalendar from device.
can only be done if device supports setting an access level or priority
Device not supporting priority.
OK
Device can’t display the multi-byte characters (no font, normal). Chars were sent back to server correctly when modified.
OK
OK
OK
OK except for truncation issue:
Sync server day event to device, title and location were truncated. Modify title on device and sync, event remains same on server and device change is rolled back. Modify location on device, changes are propagated to server but title is also truncated on server. Seems to be a bug on server. Need more investigation.
Recurrence issue: Server only sends one instance of the event to device. This was because that server splits the recurrence and only sends the instances within sync range to device.
OK
Not supported by device.
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
This section was not tested extensively but the basics worked. The server splits the recurrence and only sends the instances within sync range to device.
OK except for:
Owner email wrong: owner email was , however it was shown as . Seems to be server bug.
Owner email was not first on the attendee list. Need to find out whether it is server or client bug.
Client doesn’t support attendance status. Server should put the info into the meeting description as is done for Windows Mobile Smartphone.
An attempt was made to interoperate between the device and our servers but this proved to not be very fruitful at this event. The device vendor did advise the server vendor on the one defect found for their server: Phone was in different time zone from server. Created a contact on the phone with a birthday, adding birthday to the phone calendar. Synced to server. Contact on server had the birthday on the correct day but the calendar on the server had the birthday on the wrong day, due to time zone adjustment.
Also, a mobile OS contacts (which was the area the device vendor was testing informally) do not match up to other servers’ format for contact data (e.g.a calendaring client supporting vCalendar) especially where differentiations like Mobile (w) and Mobile (h) are concerned.
Mobile IOP test suite is very comprehensive. It is very difficult to do all tests.
week GSM signal at IOP place — difficult to test
new device is disabled by default in our Server. It was necessary to enable it.
DirectPUSH fails after couple of minutes with, it works fine with different device
we don’t know yet if it is client or server issue
Birthday problem:
create new Contact with birthday and let device to create event in your calendar
synchronize it to server
open Calendar in client (EST) which is in different timezone than mobile device (GMT)
Result: birthday is one day early
we are not sure, if it is correct or not
general question: how to present all day events in different timezones
The first mobile interop testing was a success. We learned a couple of things. First, we need to ensure we are located in a facility that has good cell coverage. The room we occupied had occasional issues with cell phone coverage. The best approach would be to test rooms we will be utilizing prior to starting the event so we can ensure we have adequate coverage.
The other thing we determined was the test scenario document has too many items to test in two days. We are not even sure we can test everything within three days. What was done this time was the vendors chose to test specific items from each group in an effort to try to cover as much as possible. For future testing, we may choose to break down the testing into specific areas. In other words, we may test section one during one event, section two during the next event, and so on. Or we may determine which items are the most critical to testing, and focus on them during the next events. This will be decided before the next Mobile interoperability test event is held.
Our thanks to the participating vendors.
Respectfully submitted by Pat Egen, CalConnect Interop Manager.