Troubleshooting WorxMail APNs

Troubleshooting WorxMail APNs

3:09 PM
Troubleshooting WorxMail APNs -

WorxMail APNs Troubleshooting

To a real-time e-mail sync with experience have WorxMail, you must WorxMail with APNs to enable. You can find the same steps here to enable.

post configurations when you perform any problems with WorxMail APNs message, this blog will help you to debug the problem.

using make to start safely, have you take care of the requirements made necessary for WorxMail APNs

Reference Documentation .:

  1. http://docs.citrix.com/en-us/worx-mobile-apps/10/xmob-worx-mail/xmob-worx-push-notifications.html
  2. https://www.citrix.com/blogs/2015/06/11/mobility-experts-a-step-by-step-guide-to-configuring-worxmail-apns
  3. http://support.citrix.com/article/CTX0971
  4. http://support.citrix.com/article/CTX201026

There are several moving parts, the badge in WorxMail APNs notification update process involved.

  1. WorxMail with the right push notification configurations.
  2. iOS device.
  3. APNs server
  4. Citrix push registry cloud server
  5. Exchange Web Services
  6. Citrix listener service cloud servers.

To have the APNs work on WorxMail, we need all of the above parts setup and communicating properly. During the first time usage (FTU) establishment of WorxMail is WorxMail communicate with Exchange Server to synchronize email with Active Sync protocol

Quick river .:

Step 1:

under the FTU setup when the WorxMail configured with APNs, as prescribed in the above articles setting then first WorxMail will register for remote notifications with APNs server and turn device (WorxMail) gets from APNs Server a device token. Now WorxMail will register with Citrix Push registration server to the device token received, again WorxMail is registered with EWS for subscription ID (for a push event). In the process of registering with EWS site EWS is the request with 401 authentication challenge now responds WorxMail the authentication request with credentials that it has from the FTU. Following the successful EWS Authentication is a subscription id WorxMail (mapped to the device ID) return

Level 2 :. Every time a new email arrives in the inbox of the end user is an EWS push notification to send the subscribed units of Citrix listener service, Citrix listener service will be notified to send a message to the APNs Apple server. Apple server in-turn will notify the unit and update the badge WorxMail still.

After you have done all the configuration on which WorxMail, Post downloading Worxmail have configured, but you see no push notification badge update under checkpoints WorxMail come, then troubleshoot the problem will be helpful

point 1 :. to start WorxMail logs from the device for analysis, to collect. Once you have the logs to extract them in a folder, navigate to the folder WorxMail and search for "CtxLog_MailConfiguration" log file.

WM1

Once you open "CtxLog_MailConfiguration" log file associated with - you should push notifications listener service token (token contains alphanumeric characters 64 characters) can see. This token value should not "zero". If you set this token value to zero, then you can directly confirm away that WorxMail APNs not working

WM2

Point 2: WorxMail requests for APNs token

[1945001Navigieren] to diagnosis folder inside the WorxMail folder and open the current log file. As per flow is first WorxMail Request for APNs token. To confirm that the WorxMail have received the token, you should look for the following set of protocols which confirms that the WorxMail is able to obtain the device token from APNs

2015- 09-19T18 :. 50: 02859-0400 WorxMail INFO (4) requesting iOS device token
2015-09-19T18: 50: 02884-0400 WorxMail INFO (4) didRegisterForRemoteNotificationsWithDeviceToken - receiving device APNS token
2015-09-19T18: 50: 02884-0400 WorxMail INFO (4) obtaining device token successfully

Received token (for reference only)

deviceActiveSyncId = 56eeb7223240dbb63b124273a25fb3c6a0bf7932827965de08585cdaf78fb54;
deviceNotificationId = 1fe3ff5c6684581af6922f0cff92376dc468216bca7ea87531877b0980daf5b3;
= EMAILID 796b83a75c32179d4b025afbf187872d31fb5ec9be3ac2f3feae9336d77b0378;
},URL=https://us-east-1.pushreg.xm.citrix.com/tenant/123456780

Checkpoints:

  1. If you from the WorxMail received not the device see token, make sure WorxMail is able to reach the Apple Push Notification Server
  2. If They have. WorxMail network policies to "tunnel to the internal network," make sure your NetScaler is able to achieve the Citrix Push registration listener service.
  3. If your NetScaler server can not respond to the push registry listener server, try splitting allow tunnel to the NetScaler policy so that the WorxMail can use the device DNS to discuss the APNs

show. 3: WorxMail register with Push Registry Service

Add to WorxMail protocols, you can see when the WorxMail with push listener service registered (in this case, the push registry server URL "https: // us -east-1.pushreg.xm.citrix.com ") with device IDs that it has received in the previous step. If the WorxMail can reach https://us-east-1.pushreg.xm.citrix.com, then you can see the Device Registration

Note . Push your registration service URL could. otherwise based on the configuration that you in WorxMail MDX guidelines have
2015-09-19T18: 50: 0204-0400 WorxMail INFO (4) commission status = ProvisionStatusRegisteringForPushNotifications
2015-09-19T18: 50: 03312-0400 WorxMail INFO (4) device Registration successfully with tokens from the server fce470ad6f11f0d3d9494e65c19868bda92091dff1dae38c4a4234e58f7e5dce

checkpoints:

  1. If you happen to the push registration server can not be seen on the device registration, then make sure WorxMail is able to speak URL to Citrix push registry (*. pushreg.xm.citrix.com).
  2. If you WorxMail network policies to "tunnel to internal network" then make sure that your NetScaler can be reached able Citrix Push registration listener service.
  3. If your NetScaler servers at the push registration server can not talk, try enable split tunneling on the NetScaler policy so that the WorxMail can use the device DNS, talk registration server to push

Note (Imp.): if you have tunnel from Split, then you need to add the Citrix push registration server (us-east-1.pushreg.xm.citrix.com:443) on as expected background network services (MDX Policy) for WorxMail synchronization function.

Point 4: WorxMail Subscription EWS

WorxMail is registered with the EMS server, as part of EWS a 401 authentication will provide challenge that will try WorxMail to react with the credentials. After successful authentication EWS a subscription ID WorxMail offer. You can confirm the following protocols, see the subscription ID in

2015-09-19T18 :. 50: 03313-0400 WorxMail INFO (4) EWS operation name = SubscribeToPushbaseEventNotification
2015-09-19T18: 50: 03314-0400 WorxMail INFO (4) Commission Status = ProvisionStatusSubscribingForPushNotifications
2015-09-19T18: 50: 03.846- 0400 WorxMail INFO (4) inner block closure for operation = SubscribeToPushbaseEventNotification
2015-09-19T18: 50: 03846-0400 WorxMail INFO (4) receive an HTTP status code 0 for operation = SubscribeToPushbaseEventNotification
2015-09-19T18: 50: 03,846 -0400 WorxMail INFO (4) Received response string contents for operation = SubscribeToPushbaseEventNotification
2015-09-19T18: 50: 03848-0400 WorxMail INFO (4) EWS Subscribe event notification successfully
2015-09-19T18 to press: 50: 03848-0400 WorxMail DETAIL (5) subscriptionId : - GQBmdGxwZXgwMWNhczAzLmNpdHJpdGUubmV0EAAAABEsUvAkwt1IsKpqHhaQgA5F4ZVHnWDSCA ==

points to Check:

  1. ensure WorxMail be reached by the Exchange server EWS site.
  2. Ensure EWS site same with the same authentication method as Active Sync server is enabled. Basic authentication, NTLM authentication, etc.
  3. Verify certificate that is bound to the EWS website, familiar

Point 5 :. WorxMail receives inbox folderID and the number of unread EWS

Post Authentication EWS site, WorxMail will get the folder ID that is enabled for push notifications. .: 50: 03848-0400 WorxMail INFO (4) EWS operation name = GetFolder
[1945013SiekönnendasgleichemitdemfolgendenSatzvonProtokollen

2015-09-19T18 confirm] 2015-09-19T18: 50: 03,849 -0400 WorxMail INFO (4) commission status = ProvisionStatusGettingFolderIdForPushNotification
2015-09-19T18: 50: 04436-0400 WorxMail INFO (4) Within final block for operation = GetFolder
2015-09-19T18: 50: 04437-0400 WorxMail INFO (4) receive an HTTP status code 0 for operation = GetFolder
2015-09-19T18: 50: 04,437 -0400 WorxMail INFO (4) Received string content answer for operation = GetFolder
2015-09-19T18: 50: 04438-0400 WorxMail INFO (4) Got folderId inbox
2015-09-19T18: 50: 04439-0400 WorxMail DETAIL (5) folder ID: - AQAWAGNocmlzLmJ1cmtlQGNpdHJpeC5jb20ALgAAA4tYHB9LXmFGujrRkElxHqIBAH2WBaHLe7JPv8/7wkthmdIAAAEPU8YAAAA=

Item 6: WorxMail updates the listener service

WorxMail turn update the listener service

2015-09-19T18 :. 50: 04442-0400 WorxMail INFO (4) Commission Status = ProvisionStatusUpdatingListenerServiceForPushNotifications
2015-09-19T18: 50 :. 04.752-0400 WorxMail INFO (4) call success factor for listener service updat e

Checkpoints:

  1. Make sure Exchange server is able to Citrix reach listener service

More important (* mailboxlistener.xm.citrix.com.). Points:

are
  1. WorxMail with APNs only at the time of the FTU. For some reason, when APNs not work you need to download the application again and then reconfigure that of the FTU.
  2. For some reason, when WorxMail contact EWS site not for large amount of time, then the Exchange server will terminate the subscription ID, then WorxMail a new connection is initiated again for a new subscription ID Request ,

If you need more help on the same, you can always Citrix Support @ https://www.citrix.com/support.html

Next
« Prev Post
Previous
Next Post »
0 Komentar

Subscribe to: Post Comments (Atom)