ActiveSync & Google Apps

[Pablo]

For those w/o an Exchange Server, is the new ActiveSync feature in the latest release compatible with Google Apps for Business?

 

If not, is there a way to achieve the same result, e.g. possibly through Google's Directory Sync (from Google: If you have an on-premise LDAP directory server, you can use Google Apps Directory Sync to automatically import users and groups into the Google Admin Control Panel. Google Apps Directory Sync is a client application that sets up rules for synchronizing Microsoft Active Directory, IBM Lotus Domino, and other LDAP servers with the Google Admin Control Panel. After creating your rules, you run the synchronization on your command line interface.)?

[Harlow Tech]

I tried to set this up and just got an error, filed a support request on their main site no response yet.

 

Daniel

[Pablo]

I tried to set this up and just got an error, filed a support request on their main site no response yet.

 

Daniel

 

Any luck?

[Pablo]

After learning that Google has decided to extend its support of ActiveSync, I tried using my Google Apps for Business account's credentials, but get the following errors:

 

When I set the Exchange Server address to https://m.google.com, the log read:

 

 

[5] 2013/04/20 10:55:01: Activesync: Start syncing.

[8] 2013/04/20 10:55:01: HTTP client: Connect to 74.125.142.193:443, pending requests 0

[9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: send_client_hello(03015172ba56e7 ... 652e636f6d)

[9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: process_server_hello(030151 0000000)

[9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] process_certificate(000 ... d57e98)

[9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] process_server_hello_done()

[9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] rsa_n(da62984092 ... 3f40db94e4c5b3)

[9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] rsa_e(010001)

[9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] Pre Master Secret(030108d ... 31254da5e)

[9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] Block Padded(000209b38cc1cd3 ... 254da5e)

[9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] Encrypted Pre Master(1029e9e7 ... 37cfa54414f)

[9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] Client Random(5172b ... 891)

[9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] Server Random(517 ... 77ba)

[9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] Master Secret(462b ... a6da5)

[9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] send_client_key_exchange(008010 ... 54414f)

[9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] send_change_cipher_spec(01)

[9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] perform_change_cipher_spec(0005)

[9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] Key Block(3aa9b ... c6e22)

[9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] Client Write MAC Secret(3aa ... 1f03e)

[9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] Server Write MAC Secret(cf97 ... 06)

[9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] Client Write Key(5a8 ... a95)

[9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] Server Write Key(9ff ... e22)

[9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] send_finished(3ffa ... 89)

[9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] process_change_cipher_spec(01)

[9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] process_finished(e8c ... da5)

[8] 2013/04/20 10:55:04: HTTP client: Connect to 74.125.142.193:443, pending requests 0

[9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: send_client_hello(0301 ... 36f6d)

[9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: process_server_hello(03015172b ... 0400000000)

[9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] process_certificate(00063a0 ... 57e98)

[9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] process_server_hello_done()

[9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] rsa_n(da6298 ... e4c5b3)

[9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] rsa_e(010001)

[9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] Pre Master Secret(0301eb ... 176)

[9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] Block Padded(00025 ... 4176)

[9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] Encrypted Pre Master(63f0fa ... dfa4)

[9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] Client Random(517 ... 140)

[9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] Server Random(5172ba ... a0b)

[9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] Master Secret(e586 ... 45f8a)

[9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] send_client_key_exchange(008 ... dfa4)

[9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] send_change_cipher_spec(01)

[9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] perform_change_cipher_spec(0005)

[9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] Key Block(17f64ad ... 248)

[9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] Client Write MAC Secret(17f6 ... e6)

[9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] Server Write MAC Secret(74 ... d14)

[9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] Client Write Key(50b ... d3f)

[9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] Server Write Key(1b ... 48)

[9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] send_finished(42 ... ee2)

[9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] process_change_cipher_spec(01)

[9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] process_finished(21 ... cb8)

[5] 2013/04/20 10:55:04: Activesync Status Error: Failure 2. Status = 8

 

Then, when I set the Exchange Server address to http://m.google.com, the log read:

 

 

[5] 2013/04/20 10:57:19: Activesync: Start syncing.

[8] 2013/04/20 10:57:19: HTTP client: Connect to 74.125.142.193:80, pending requests 0

[5] 2013/04/20 10:57:19: Activesync: Syncing failed 1. Error code = 302

 

Finally, when I left the Exchange Server address emtpy, the log read:

 

[5] 2013/04/20 11:09:01: Activesync: Start discovery.

[8] 2013/04/20 11:09:02: HTTP client: Connect to 0.0.0.0:80, pending requests 0[5] 2013/04/20 11:09:03: Activesync: Redirection.

[5] 2013/04/20 11:09:03: Activesync: Start discovery.

[2] 2013/04/20 11:09:03: HTTP address is empty

[Vodia Telephone System]

[5] 2013/04/20 10:55:04: Activesync Status Error: Failure 2. Status = 8

 

That status for Sync means:

 

Object not found. The client issued a Fetch or Change operation that has an ItemID (section 2.2.3.84) value that is no longer valid on the server (for example, the item was deleted).

 

Is it possible there were no contacts there?

 

Also I don't know why auto-discovery fails when you leave the address blank? Do they say anything about auto-discovery? Also if not what address do they want to use for activesync. Sometimes the obvious well known address, like you are using, is correct but sometimes its completely different, in which case it has to be found out, especially if it doesn't respond to auto-discovery.

[Pablo]

[5] 2013/04/20 10:55:04: Activesync Status Error: Failure 2. Status = 8

 

That status for Sync means:

 

Object not found. The client issued a Fetch or Change operation that has an ItemID (section 2.2.3.84) value that is no longer valid on the server (for example, the item was deleted).

 

Is it possible there were no contacts there?

 

Also I don't know why auto-discovery fails when you leave the address blank? Do they say anything about auto-discovery? Also if not what address do they want to use for activesync. Sometimes the obvious well known address, like you are using, is correct but sometimes its completely different, in which case it has to be found out, especially if it doesn't respond to auto-discovery.

 

Does the PBX have an Exchange Web Services URL (Example: https://ExchangeMail.domain.com/EWS/Exchange.asmx); or the equivalent?

[Pablo]

[5] 2013/04/20 10:55:04: Activesync Status Error: Failure 2. Status = 8

 

That status for Sync means:

 

Object not found. The client issued a Fetch or Change operation that has an ItemID (section 2.2.3.84) value that is no longer valid on the server (for example, the item was deleted).

 

Is it possible there were no contacts there?

 

Also I don't know why auto-discovery fails when you leave the address blank? Do they say anything about auto-discovery? Also if not what address do they want to use for activesync. Sometimes the obvious well known address, like you are using, is correct but sometimes its completely different, in which case it has to be found out, especially if it doesn't respond to auto-discovery.

 

 

What's this mean?: [5] 2013/04/22 13:58:26: Activesync: Syncing failed 1. Error code = 401

I received this 401 error code when I tried a different URL as the Exchange Server URL: https://www.google.com/m8/feeds (which I read about in this article: Google Contacts API version 3.0)

[Vodia Telephone System]

Unauthorized User.

 

Are you sure your username and password are correctly saved before synching?

[Pablo]

Unauthorized User.

 

Are you sure your username and password are correctly saved before synching?

 

 

Just to be sure; I logged into the extension's web portal; deleted the (i) username, (ii) password, and (iii) Exchange server address; clicked save; and logged out. I waited 15 minutes, then logged back in and entered all the relevant info., including https://m.google.com;'>https://m.google.com; but, on the PBX, still receive Activesync Status Error: Failure 2. Status = 8

The weird part, is that from my point of view, it appears that https://m.google.com is the correct Exchange server address. When I first used that address, my Google Apps domain quarantined the PBX until I approved it w/in my Google Apps domain's Mobile Settings.

Within the Google Apps domain's Mobile Settings, the PBX is listed as an active sync device. When I click to read the device's details, it shows the following:

Status: Approved

Name: Pablo Carranza

Email: pablo@pcatty.com

Device ID: v140Device

First Sync: 4/20/13 10:51 AM

Last Sync: 4/22/13 1:20 PM

OS: Unknown

Type: Google Sync

User Agent: Mozilla/4.0 (compatible; PBX),gzip(gfe)