Homepage | Products | OX Knowledge Base | Support | Try Now | Contact | Company
OX Logo
Page 1 of 3 123 LastLast
Results 1 to 10 of 30
  1. #1
    Join Date
    Mar 2009
    Location
    Austria
    Posts
    139

    Default Mobility Oxtender and N900

    Hi,

    Did anynone try to use the SYNC Function with the Nokia N900?
    Is there any trick to make it work?

    Thank you for your help

    wbrgds

    Lukasz

  2. #2
    Join Date
    Feb 2007
    Location
    Germany
    Posts
    3,695

    Default

    Hi Lukasz,

    afaik the nokia "sync" application is an SyncML implementation. You need an ActiveSync client like Mail For Exchange to use the mobility oxtender.

    http://wiki.maemo.org/N900_Email_Opt...ange_.28MfE.29

    Greetings

  3. #3
    Join Date
    Mar 2009
    Location
    Austria
    Posts
    139

    Default

    Thank you...but the Nokia N900 has the SYNCml as well as an MfE Sync compatible with Exchange 2003 and 2007 - but it is not working yet with the OX Server,

    wbrgds

    Lukasz

  4. #4
    Join Date
    Feb 2007
    Location
    Germany
    Posts
    3,695

    Default

    Have you configured MfE? What version is available on the n900? What error is thrown by MfE?

    Greetings

  5. #5
    Join Date
    Mar 2009
    Location
    Austria
    Posts
    139

    Default

    I suppose that there is still a problem at the Nokia developers side.....
    i know that the server is working with my IPhone and other Nokia Phones.

    So, configuration:

    EMAIL: OK
    USER: OK
    PASS: OK
    DOMÄNE: defaultcontext

    SERVER: MYOXSERVERNAME
    PORT: 443
    SECURE: YES

    I tried also port 80
    Certs are installed!

    then I can choose what to sync.

    MfE is trying to establish the first connection and all that happens is:
    "Fehler bei der Kommunikation mit dem Exchange Server"

    Taht's it?!

    However, help is deeply appreciated

    Thank you so far

    wbrgds

    Lukasz

  6. #6
    Join Date
    Feb 2007
    Location
    Germany
    Posts
    3,695

    Default

    Hi,

    is it possible to access the Open-Xchange Server via the mobile phones browser? Looks like a connection issue. Is there anything at the OX logs?

    Greetings

  7. #7
    Join Date
    Mar 2009
    Location
    Austria
    Posts
    139

    Default

    Yes, access is possible, IMAP and POP is working.
    Which logs should I look at?

    THANK YOU!

  8. #8
    Join Date
    Feb 2007
    Location
    Germany
    Posts
    3,695

    Default

    open-xchange.log.0 when trying to synchronize, also try to access http://server.ox/Microsoft-Server-ActiveSync

    Greetings

  9. #9
    Join Date
    Mar 2009
    Location
    Austria
    Posts
    139

    Default

    hi, when I try to access the link, i get the 405 METHOD NOT ALLOWED error - so it is accessible, i suppose?

    Here are the last lines of the log file you asked for, I tried twice to start the inital sync:
    Jan 19, 2010 10:11:06 AM com.openexchange.usm.eas.servlet.EASServlet doPost
    INFO: Invalid request: Missing or duplicate required parameter User
    Jan 19, 2010 10:11:39 AM com.openexchange.sessiond.impl.SessionHandler clearSession
    INFO: Session closed. ID: 4b8fa9d356a54c22bcc5dfc97c4e67bb
    Jan 19, 2010 10:11:48 AM com.openexchange.ajp13.najp.AJPv13TaskWatcher$Task RunCallable handleExceededTask
    INFO: Sending KEEP-ALIVE for AJP Listener "AJPListener-0006631"
    Jan 19, 2010 10:11:48 AM com.openexchange.ajp13.najp.AJPv13TaskWatcher$Task RunCallable handleExceededTask
    INFO: Sending KEEP-ALIVE for AJP Listener "AJPListener-0006520"
    Jan 19, 2010 10:11:48 AM com.openexchange.ajp13.najp.AJPv13TaskWatcher$Task RunCallable keepAlive
    INFO: Flushed empty GET-BODY request to socket "/127.0.0.1:45720" to initiate a KEEP-ALIVE poll.
    Jan 19, 2010 10:11:48 AM com.openexchange.ajp13.najp.AJPv13TaskWatcher$Task RunCallable keepAlive
    INFO: Flushed empty GET-BODY request to socket "/127.0.0.1:54877" to initiate a KEEP-ALIVE poll.
    Jan 19, 2010 10:11:48 AM com.openexchange.ajp13.najp.AJPv13TaskWatcher$Task RunCallable keepAlive
    INFO: Swallowed empty REQUEST-BODY from socket "/127.0.0.1:45720" initiated by former KEEP-ALIVE poll.
    Jan 19, 2010 10:11:48 AM com.openexchange.ajp13.najp.AJPv13TaskWatcher$Task RunCallable keepAlive
    INFO: Swallowed empty REQUEST-BODY from socket "/127.0.0.1:54877" initiated by former KEEP-ALIVE poll.
    Jan 19, 2010 10:12:32 AM com.openexchange.usm.eas.servlet.EASServlet doPost
    INFO: Invalid request: Missing or duplicate required parameter User
    Jan 19, 2010 10:12:48 AM com.openexchange.ajp13.najp.AJPv13TaskWatcher$Task RunCallable handleExceededTask
    INFO: Sending KEEP-ALIVE for AJP Listener "AJPListener-0006631"
    Jan 19, 2010 10:12:48 AM com.openexchange.ajp13.najp.AJPv13TaskWatcher$Task RunCallable keepAlive
    INFO: Flushed empty GET-BODY request to socket "/127.0.0.1:45720" to initiate a KEEP-ALIVE poll.
    Jan 19, 2010 10:12:48 AM com.openexchange.ajp13.najp.AJPv13TaskWatcher$Task RunCallable keepAlive
    INFO: Swallowed empty REQUEST-BODY from socket "/127.0.0.1:45720" initiated by former KEEP-ALIVE poll.

    Thank you,

    wbrgds

    Lukasz

  10. #10
    Join Date
    Feb 2007
    Location
    Germany
    Posts
    3,695

    Default

    Hi,

    okay that looks like the device does not send correct data. Either caused by wrong configuration or an implementation flaw.
    Can you sniff the traffic when trying to synchronize the device? You might want to disable SSL for this.

    Greetings

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •