Avaya Calling for Microsoft Teams: cannot load contacts 3

[lcgmx]

Hi, I configured IPO - Spaces - Teams

Avaya calling loads on teams app, Single sign on works fine but I cannot load contact neither from IPOffice nor from Office.

On spaces, on the domain, Apps - Avaya Calling for teams I have tried with different options:

1) empty public settings
{
}

2) just office settings
{
"Client_Settings_File_Address": []
}

any help will be apreciated

 

[PhonesTech]

Hi LCGmx, It's a known limitation. see attached from the

https://support.avaya.com/css/public/documents/101078726

page 11.

 

[Fr0gg3r - MaartenS]

Hi,

I don't believe this is one of the limitations.
The limitations are in regard to loading contacts of the IP Office system itself.

The contacts of the AD should get loaded.

I have the plugin running on 2 different Teams / Azure environments.
On one of them the AD contacts do get loaded, on the other one the AD contacts do not get loaded.

I still haven't figured out why they can't load...

If I figure it out I'll post it, but I'm not actively chasing it at the moment.

.

 

[sizbut]

The usual reason Workplace doesn't load IP Office contacts is not using HTTPS. It is possible to get Workplace working using just HTTP, but some of the features need it to be using HTTPS.

Stuck in a never ending cycle of file copying.

 

[lcgmx]

Thanks PhonesTech. I haven´t read that little note about ipo contacts on page 11. but still the main problem is office 365 contacts. I could go without IPO contacts if I could have office 365 contacts.


When I load Teams -> open Avaya calling tab - > dial an extension number then Teams signals workplace to start, and once it is up the number is dialed by workplace.
So Avaya calling is integrated with workplace.

what is not clear is why office contacts do not load.

 

[lcgmx]

the error on Temas desktop show the ID of An avaya applicaiton on Azure. this is not configured during the integration steps. I think this ID is loaded by the manifest file of avaya calling and is a general setup. why it fails in some scenarios?

{
"timestamp": "2024-05-15T03:12:11.250Z",
"kind": 3,
"topic": "t",
"name": "getServerSideToken",
"data": "Failed to retrieve token: {\"headers\":{\"normalizedNames\":{},\"lazyUpdate\":null},\"status\":503,\"statusText\":\"OK\",\"url\":\"

https://callassist.avayacloud.com/a...me\":\"HttpErrorResponse\",\"message\":\"Http

failure response for

https://callassist.avayacloud.com/api/mso/auth/token:

503 OK\",\"error\":{\"error\":\"invalid_client\",\"error_description\":\"AADSTS7000222: The provided client secret keys for app '75608085-bcdd-461a-ba74-227654123bfa' are expired. Visit the Azure portal to create new keys for your app:

https://aka.ms/NewClientSecret,

or consider using certificate credentials for added security:

https://aka.ms/certCreds.

Trace ID: 7ff55646-832b-4792-951c-2639ac94d500 Correlation ID: 9f28e45a-c299-4451-9e94-97acca13315d Timestamp: 2024-05-15 03:12:10Z\",\"error_codes\":[7000222],\"timestamp\":\"2024-05-15 03:12:10Z\",\"trace_id\":\"7ff55646-832b-4792-951c-2639ac94d500\",\"correlation_id\":\"9f28e45a-c299-4451-9e94-97acca13315d\",\"error_uri\":\"

https://login.microsoftonline.com/error?code=7000222\"}}",

"id": 3060
},
{
"timestamp": "2024-05-15T03:12:11.250Z",
"kind": 3,
"topic": "t",
"name": "pullContacts",
"data": "invalid_client",
"id": 3061
},
{
"timestamp": "2024-05-15T03:12:11.251Z",
"kind": 3,
"topic": "GlobalErrorHandler",
"name": "Error in console",
"data": "invalid_client",
"id": 3062
}

 

[lcgmx]

final update.

I opened a service request and it was a problem with avaya app at Microsoft market place level. they fix it there and then it was fixed for my customers solution and to my lab solution.