Avaya IX Workplace Application on Apple IPhone With IP Office R11.1 1

[CASSBusinessSystems]

Anybody else having an issue answering calls with Avaya IX Workplace on Apple IPhone when the phone is locked? To answer the call, users need to unlock the phone first. We haven't come across this problem on Android. Apple IOS software version is 13.4.1 and the IX Workplace version is 3.8.4. IP Office version is R11.1. Just wondering if anyone else has come across this.

Thanks in advance.

 

[Albus2]

No, that working fine here.
Same latest versions for IPO, iPhone and IX Workplace. I'm also using Apple Push Notificeation. This means it is an IX Workplace call and not a simple mobile call via twinning.
CallKit is implemented, i.e. the call is offered even to the lockscreen.

 

[Aldridge85]

Hi Albus2

Does APN work on 500V2 11.1? In System Status i get 2 errors, 'Apple Push Notification Service unavailable' & 'Push Notification authorization failure:System ID is not provisioned'

I don't think there is a Sys ID on 500V2?

Thanks

 

[Albus2]

I think there is a potential problem with APN. It *may* result in reboots when a iPhone registers.
I know some installations where it works and others with this problems. So better try to activate it out of hours.
We had the idea it may have to do with non standard characters in the Profilename (System, Avaya Cloud Service) better avoid Symbols, Umlauts, Withespace, ect.

To activate, you need an API key and Secret which is created on Zang.io
Enter it in the Security Settings, then activate under System, Avaya Cloud Account and also Avaya Push Notification.

Its not Server edition only, its also for 500v2.

 

[CASSBusinessSystems]

Good catch, Albus. Callkit wasn't implemented. With it enabled, all is working great now. Thank you!

Full Disclosure, I am really fuzzy with iOS.

@Aldridge - Your domain is registered in accounts.zang.io? And that domain is set under System > Avaya Cloud Services > Zang Domain? Also the API keys and secret are in your security settings?

 

[Aldridge85]

Hi guys

Sorry for the late reply, thanks for the info, I've checked and the domain is registered in accounts.zang.io, i can log in to the IX app with my email so it's pulling the settings file ok. I've also checked security settings and i definitely have the Zang API and secret keys in there, I've set the domain name in the in Manager under Zang Domain but still get the same errors as above in system status. I'm confused as to why it says System ID is not provisioned? It's like it acting as if it's Server Edition.

 

[CASSBusinessSystems]

The domain name resolves to your IP Office IP address, right?

 

[Bucky101]

FYI have tried this on an 11.1, get a reboot loop when the Enable APN tick box is ticked in system
Security settings contain the API and key

 

[Albus2]

@Bucky101
Thank you. So it's not just me. I have a ticket open for it but slow progress...

 

[Bucky101]

oh cool, same. If i trace HTTP i see
Bootup
9125mS PRN: +++ START OF ALARM LOG DUMP +++
9125mS PRN: ALARM: 20/04/2020 16:16:03 S-Edition Primary 11.1.0.0.0 build 237 <Crash with unknown cause. > CRIT RAISED pid=25527 d=5 stack=f7720430 f720d227 f720ea63 f724efd5 f725626c
9125mS PRN: ALARM: 20/04/2020 16:16:33 S-Edition Primary 11.1.0.0.0 build 237 <Crash with unknown cause. > CRIT RAISED pid=32592 d=5 stack=f76e1430 f71ce227 f71cfa63 f720ffd5 f7218aad
9125mS PRN: ALARM: 20/04/2020 16:17:04 S-Edition Primary 11.1.0.0.0 build 237 <Crash with unknown cause. > CRIT RAISED pid=6592 d=5 stack=f774e430 f723b227 f723ca63 f727cfd5 f7285aad
9125mS PRN: ALARM: 20/04/2020 16:17:34 S-Edition Primary 11.1.0.0.0 build 237 <Crash with unknown cause. > CRIT RAISED pid=12798 d=5 stack=f7755430 f7242227 f7243a63 f7283fd5 f728caad
9125mS PRN: ALARM: 20/04/2020 16:18:05 S-Edition Primary 11.1.0.0.0 build 237 <Crash with unknown cause. > CRIT RAISED pid=19202 d=5 stack=08569800 08569b0b 08ee354a 08ee370d 08ee3757
9125mS PRN: ALARM: 20/04/2020 16:18:27 S-Edition Primary 11.1.0.0.0 build 237 <Crash with unknown cause. > CRIT RAISED pid=25502 d=5 stack=f771a430 f7207227 f7208a63 f7248fd5 f7251aad
9125mS PRN: ALARM: 20/04/2020 16:18:48 S-Edition Primary 11.1.0.0.0 build 237 <Crash with unknown cause. > CRIT RAISED pid=30367 d=5 stack=f7798430 f7285227 f7286a63 f72c6fd5 f72cfaad
9125mS PRN: ALARM: 20/04/2020 16:19:09 S-Edition Primary 11.1.0.0.0 build 237 <Crash with unknown cause. > CRIT RAISED pid=3190 d=5 stack=f730bffa f730ddda 085561f9 08556464 094034b0
9125mS PRN: ALARM: 20/04/2020 16:19:30 S-Edition Primary 11.1.0.0.0 build 237 <Crash with unknown cause. > CRIT RAISED pid=7703 d=5 stack=f77d7430 f72c4227 f72c5a63 f7305fd5 f730d26c
9125mS PRN: ALARM: 20/04/2020 16:19:55 S-Edition Primary 11.1.0.0.0 build 237 <Crash with unknown cause. > CRIT RAISED pid=12431 d=5 stack=f77b3430 f72a0227 f72a1a63 f72e1fd5 f72eaaad
9125mS PRN: ALARM: 20/04/2020 16:20:16 S-Edition Primary 11.1.0.0.0 build 237 <Crash with unknown cause. > CRIT RAISED pid=17863 d=5 stack=f7712430 f71ff227 f7200a63 f7240fd5 f7249200
9125mS PRN: ALARM: 20/04/2020 16:20:50 S-Edition Primary 11.1.0.0.0 build 237 <Crash with unknown cause. > CRIT RAISED pid=22627 d=5 stack=08569800 08569b0b 08ee354a 08ee370d 08ee3757
9125mS PRN: ALARM: 20/04/2020 16:21:14 S-Edition Primary 11.1.0.0.0 build 237 <Crash with unknown cause. > CRIT RAISED pid=29748 d=5 stack=f7751430 f723e227 f723fa63 f727ffd5 f7288aad
9125mS PRN: ALARM: 20/04/2020 16:21:35 S-Edition Primary 11.1.0.0.0 build 237 <Crash with unknown cause. > CRIT RAISED pid=2358 d=5 stack=f77a4430 f7291227 f7292a63 f72d2fd5 f72dbaad
9126mS PRN: ALARM: 19/05/2020 14:28:01 S-Edition Primary 11.1.0.0.0 build 237 <Crash with unknown cause. > CRIT RAISED pid=529 d=5 stack=f7235edb f7237dda 085561f9 08556464 094034b0
21421mS HTTP: PushNotificationAuthorizationHandler::EC-256 Private key has to be generated
21848mS HTTP: Public IP=127.0.0.1 Private IP=Not set
26422mS HTTP: PushNotificationAuthorizationHandler::System ID generated is edb21880-8f3a-11e3-be89-005056aaac81.contoso.com.au
26429mS HTTP: PushNotificationAuthorizationHandler:Generated Private/Public EC-256 key Pair
26429mS HTTP: HTTPZangPushNotificationSyncSessionIO: SetState Init ZANG
26429mS HTTP: PushNotificationAuthorizationHandler: Zang Sync session is started
26429mS HTTP: HTTPZangPushNotificationSyncSessionIO: trying DNS query accounts.zang.io
26429mS HTTP: HTTPZangPushNotificationSyncSessionIO: SetState FQDN resolution
26431mS HTTP: HTTPZangPushNotificationSyncSessionIO: waiting to receive response from DNS
26440mS HTTP: Public IP=127.0.0.1 Private IP=Not set
26463mS HTTP: Public IP=10.0.11.2 Private IP=Not set
26828mS HTTP: Public IP=127.0.0.1 Private IP=Not set
27179mS HTTP: Public IP=10.0.11.2 Private IP=Not set
27180mS HTTP: HTTPZangPushNotificationSyncSessionIO: received response from DNS query - address 216.58.200.115
27180mS HTTP: HTTPZangPushNotificationSyncSessionIO: SetState Init profile settings
27182mS HTTP: HTTPZangPushNotificationSyncSessionIO: sending request to /api/1.0/users/self/companies/admin
27182mS HTTP: HTTPZangPushNotificationSyncSessionIO: SetState Read Company Id
27234mS HTTP: Public IP=127.0.0.1 Private IP=Not set
27634mS HTTP: Public IP=127.0.0.1 Private IP=Not set
27810mS HTTP: PushNotificationAuthorizationHandler :: System-ID is set from APNS Config as edb21880-8f3a-11e3-be89-005056aaac81.contoso.com.au
27810mS HTTP: PushNotificationAuthorizationHandler::EC-256 Public key is set from APNS Config
27810mS HTTP: PushNotificationAuthorizationHandler::EC-256 Private key is set from APNS Config
28005mS HTTP: HTTPZangPushNotificationSyncSessionIO: SetState Get current Push Notification
28007mS HTTP: HTTPZangPushNotificationSyncSessionIO: sending request to /api/1.0/companies/agxzfm9uZXNuYTIwMTRyFAsSB0NvbXBhbnkYgIDAn9r01AgM/products/APNP/public_application_setting
28007mS HTTP: HTTPZangPushNotificationSyncSessionIO: SetState Read current Push Notification
28039mS HTTP: Public IP=127.0.0.1 Private IP=Not set
28424mS HTTP: Public IP=127.0.0.1 Private IP=Not set
28514mS HTTP: HTTPZangPushNotificationSyncSessionIO: Received Invalid Request error response. State -5
28514mS HTTP: HTTPZangPushNotificationSyncSessionIO: SetState Parse System-ID
28515mS HTTP: HTTPZangPushNotificationSyncSessionIO: Generate new settings as current Push Notification Profile Settings not found
28515mS HTTP: HTTPZangPushNotificationSyncSessionIO: SetState Post public profile

********** SysMonitor v11.1.0.0.0 build 237 [connected to 192.168.222.250 (IPOSE-PRI (Server Edition(P)))] **********

********** contact lost with 192.168.222.250 at 14:28:27 19/5/2020 - reselect = 1 **********
******************************************************************

 

[BrianCosta]

@CASSBusinessSystems: Hi, I have the same problem on the iPhone, I see that you solve it by implemented and enabled call kit on the IOS, can you tell me how to implement this feature on IOS to solve the lock screen Problem on the IOS?

Thanks on Advice

 

[BrianCosta]

Hi All,,

I face the Same Problem described above:

Anybody else having an issue answering calls with Avaya IX Workplace on Apple IPhone when the phone is locked? To answer the call, users need to unlock the phone first. We haven't come across this problem on Android. Apple IOS software version is 13.4.1 and the IX Workplace version is 3.8.4. IP Office version is R11.1. Just wondering if anyone else has come across this.

Thanks in advance.

 

[BrianCosta]

@CASSBusinessSystems: Hi, I have the same problem on the iPhone, I see that you solve it by implemented and enabled call kit on the IOS, can you tell me how to implement this feature on IOS to solve the lock screen Problem on the IOS?

Thanks on Advice

 

[stressed_technician]

Hi All

Has anyone been able to fix this issue? I'm getting the same errors on one IPO v2 11.1.0.1 Build 95 but on another system it is fine.
It looks as though when it tries to write the APN, Zang doesn't like it.
The one which is working fine has no iOS devices connected to it currently but when I look in Zang I can see the Avaya push notification app has been created.
I can see a 400 bad request coming back from Zang on the system that is having problems.


13:44:45 2709206mS HTTP: HTTPZangPushNotificationSyncSessionIO: sending request to /api/1.0/companies/agxzfm9uZXNuYTIwMTRyFAsSB0NvbXBhbnkYgICw4OrRnAoM/products/APNP/profile_setting
13:44:45 2709206mS HTTP: HTTPZangPushNotificationSyncSessionIO: SetState Sent profile settings
13:44:45 2709621mS HTTP: SecureRx Src: 142.250.66.243(443)-(4109)
HTTP/1.1 400 Bad Request
X-XSS-Protection: 1; mode=block;
X-Content-Type-Options: nosniff
Content-Security-Policy: frame-ancestors 'self'
Strict-Transport-Security: max-age=3600; includeSubDomains
Vary: Accept, Accept-Language, Cookie
Content-Language: en
X-Robots-Tag: noindex, nofollow, noarchive
Allow: GET, POST, DELETE, HEAD, OPTIONS
X-Frame-Options: self
Content-Type: application/json
SE-APP-VERSION: v-2b7891aad
X-Cloud-Trace-Context: a5660e998de35fec6bdd1866fb0b91d2
Date: Sun, 20 Sep 2020 03:44:46 GMT
Server: Google Frontend
Content-Length: 103

 

[Albus2]

11.1 SP has a fix for the reboot problem. Therefore, I recomend to upgrade.
This reboot however was a result of a missing JSON string at Avayacloud.com where the IPO shall create a JSON sring with a asecret after the system is linked to Avayacloud.com using the API key.

At Avayacloud.com, under Company and Apps, you shall add the App Avaya Mobile Push Notification Service. Then the system shall write its JSON here.
I could not find this step in any manual.

There is also a SOLN available about problem seen in SSA regarding failure to reach Zang.io and similar messages.
It shows some Sysmon traces with HTTP where we can guess there is only communication in one direction. And so te 'solution' is to look after the network and firewall. But it doesn't say what exactely it was.

 

[stressed_technician]

Thanks Albus2
I was able to fix it. I reset the security settings on the system that was having problems.
The system which worked without an issue was upgraded from 11.04 whereas the system which experienced an issue was upgraded from 9.1
Thanks.