eSpace mobile is unable to receive push messages in the backstage of the IOS system

Publication Date:  2017-12-29 Views:  364 Downloads:  0
Issue Description

[Topology]ECS standard topology

[version information]ECS V300R001C00SPC200, eSpace mobile V3.10.3

[Issue phenomenon]eSpace mobile is unable to receive push messages in the backstage of the IOS system.

Handling Process

1.Firstly, verify that the configuration is correct based on the EC product document message push configuration

http://support.huawei.com/ehedex/hdx.do?lib=DOC1000108680CEF0630B&docid=DOC1000108680&v=05&tocLib=DOC1000108680CEF0630B&tocV=05&id=EN-US_TOPIC_0027401135&tocURL=resources%2Fftrg_u1900%2Fen-us_topic_0027401135.html&p=t&fe=1&ui=3&keyword=push&clientWidth=1703&browseTime=1514531610353

 

 2.And then check whether license is satisfied

 3.Analysis from the Mobile log is that MAA does not send push message

 4.According to the release time of the version, it is possible to speculate that the push certificate may expire, and the analysis of the MAA and eSever log confirmation is the reason for this problem

 5.Download the document according to the links below, replace the old expired push certificate with the new push certificate, then manually set espaceIOS12345 under the BMU certificate password, restart the MAA service to take effect.

http://support.huawei.com/enterprise/en/bulletins-product/NEWS1000010503

 

 

Root Cause

Due to the expiration of the Apple Push certificate, the client is unable to receive push messages in the background using the eSpace client using the IOS cell phone.

 

Solution

Replacing an expired push certificate to solve customer problems for new certificate.

Suggestions

1. It is suggested that tell customer the certificate out-of-service time etc after the project is delivered

2. It is suggested that the alarm in the software can reflect the specific causes of the problem and facilitate the investigation.

END