Some employees are having problems with Teams calling as an unexpected side effect of the recent Duck ID platform transition. Specifically, the impacted individuals may experience the following problems:

• Inbound calls to you are failing.
• Your dial pad has unexpectedly disappeared.
• When you try to call a non-UO phone number, the call fails and/or you get the following error message: "Couldn't complete the call. With your calling license, you can only call people within your organization. Talk to your IT admin to change your license."
• You're unable to participate in call queues that you belong to.

If you're having such problems with Teams calling, UO staff can address them if you submit a ticket at Microsoft Teams support (select "Audio calling or Teams calling with dial pad"). UO staff are also working to proactively determine who is impacted and restore service for them. Over 80 people are currently affected.

In addition, UO staff continue looking for a permanent solution to prevent more accounts from being affected, working with our new Duck ID system vendor. This morning's intended fix didn't work as expected.

About 80 employees are having problems with Teams calling as an unexpected side effect of the recent Duck ID platform transition. Specifically, the impacted individuals may experience the following problems:

• Inbound calls to you are failing.
• Your dial pad has unexpectedly disappeared.
• When you try to call a non-UO phone number, you get the following error message: "Couldn't complete the call. With your calling license, you can only call people within your organization. Talk to your IT admin to change your license."
• You're unable to participate in call queues that you belong to.

UO staff expect to restore service on Thursday, March 16.

Some employees are having problems with Teams calling as an unexpected side effect of the recent Duck ID platform transition. Specifically, people may experience the following symptoms:

• Inbound calls to you suddenly start failing.
• Your dial pad unexpectedly disappears.
• When you try to call a non-UO phone number, you get the following error message: "Couldn't complete the call. With your calling license, you can only call people within your organization. Talk to your IT admin to change your license."
• You're unable to participate in call queues that you belong to.

If you're having such problems with Teams calling, UO staff can address them if you submit a ticket at Microsoft Teams support (select "Audio calling or Teams calling with dial pad"). UO staff are also working to proactively determine who is impacted and restore service for them.

Some employees are having problems with Teams calling as an unexpected side effect of the recent Duck ID platform transition. Specifically, people may experience the following symptoms:

• Inbound calls to you suddenly start failing.
• Your dial pad unexpectedly disappears.
• When you try to call a non-UO phone number, you get the following error message: "Couldn't complete the call. With your calling license, you can only call people within your organization. Talk to your IT admin to change your license."

If you're having such problems with Teams calling, UO staff can address them if you submit a ticket at Microsoft Teams support (select "Audio calling or Teams calling with dial pad"). UO staff are also working to proactively determine who is impacted and restore service for them.

The new Cisco voicemail system was unavailable for about three and a half hours today (Thursday, January 19). Service was restored around 1:45pm. This impacted only people who use the new Cisco utility voice phone system.

The new Cisco voicemail system was unavailable for about three and a half hours today (Thursday, January 19). Service has now been restored. This impacted only people who use the new Cisco utility voice phone system.

Voicemail for the legacy Avaya phone system experienced an extended unplanned outage today (Friday, Oct. 14) from about 6:00 a.m. to 3:15 p.m. Pacific Time. UO staff believe that voicemail messages left during that time have been lost. (Voicemail for Teams calling was unaffected by this outage.)