Upcoming Enhancements to Microsoft Teams Meeting Chat Controls

on
There are many kinds of meetings, and Teams is a great tool to have virtual meetings in. As an example, it is possible to get to the chat of the meeting and start the discussion up front or continue the discussions or ask follow up questions after the meeting is over.  But sometimes, there are scenarios where organizer would want to keep the chat closed for comments outside of the meeting timeframe. And here is a new feature coming our way, to control exactly that behavior. The Teams admin center will soon allow setting up policies that will enhance your control over meeting chats. These new options are designed to give administrators more flexibility in managing how and when participants can interact via chat during meetings. These options will be available across all platforms, including Teams for Windows and Mac desktops, Teams on the web, and Teams for iOS/Android. This update is part of the Microsoft 365 Roadmap   If you are an admin, here is where you can find and contro...

Batteling the Mediation server (or; this time we blame Cisco)

on
I'm sorry I haven't posted in a wile. But I have been busy doing other implementations. The two last days however, have been more quiet (Easter is almost upon us in Norway). I have now tried to install a mediation server, and connect the OCS world to the rest of the world through a SIP trunk to CUCM (v7).

Installing the mediation server, adding a certificate, and configuring dialing rules and routes was pretty easy. I've made one simple rule for internal dialing with 4 extensions, and one for the rest of the world (for testing purposes limited to dialing the Norwegian dial plan).

Setting up the trunk on CUCM seemed fairly easy to, but I do however have on problem with the configuration I set up. And if any of you out there have a solution to it, please let me know :)

Dialing from a Cisco phone to a pure MOCS extension is working with RTP in both directions. But when dialing from MOCS and out, all calls are blocked with a 503 (Service unavailable) message from the CUCM. I can see the call in CUCM's traces), and I see the same when tracing on the Mediation server.

I've searched around, and tried to figure out what is wrong. The only thing I think might be it is a problem related to how the OCS uses + in front of numbers when calling. There is a fix for this in OCS 2007, but it is not released for R2 (at least yet).

I have verified translation patterns, css and partitons on CUCM. And the digit analyzer is giving me an OK.

Does anyone out there know the reason for the 503 error code? (The SIP trunk is unsecured and is set to use MTP)