Microsoft Copilot is all around...

on
  As the debut of Microsoft 365 Copilot approaches, there are a lot of Copilot features set to be introduced across the Microsoft 365 ecosystem. Here are a few noteworthy additions: Microsoft has unveiled a series of innovative features in the upcoming releases of Windows 11, some of them are already released, and some are currently available in preview builds. The Windows 11 Copilot, conveniently located in the taskbar, eliminates the need to open your Edge browser. It is seamlessly integrated with Bing Enterprise Chat (BEC) and ChatGPT, making it really easy to get started on your creative journey. Included in Windows 11 is the new co-creator feature in Paint. This feature, also in preview, is integrated with DALL-E and provides a swift and straightforward method for creating illustrations and images. If you possess a knack for crafting descriptions, you can generate quite impressive imagery. Another AI-powered feature is image creation directly from BEC. This feature, also integrate
0

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)

Comments

Anonymous said…
Hey I have exactly the same config and problem. Still working on it. I will post if I find the solution.
April 17, 2009 at 7:14 AM
Anonymous said…
Right - Looked into this one some more. Just as with you, Call routing was confirmed and working at both ends. OCS to CUCM and CUCM to OCS confirmed with Dialling Analyser and Route Helper.

Calls were also working from CUCM to an OCS Endpoint. Calls from OCS to a CUCM Endpoint werent working (the dreaded 503 service unavailable). After trolling the RTMT logs from the Cisco end I noticed that SIP was working fine initially then it was trying to communicate with the "Communication Server" listening IP on the mediation server. Basically I had two IP's one on each NIC for the Mediation Server. The IP's were on the same Subnet.
Changed the Medation serbver to use a single IP address for the gatway and the OCS pool. No more 503.
I havent tried to re-configure back to seperate cards and IP's yet. Just happy to be Rid of the 503 for now. Give it a shot and let me know if you had the same issue.
April 17, 2009 at 12:10 PM
Lasse Nordvik Wedø said…
Thank you for your tip, I have the same configuration on my mediation server (Two nic's on the same subnet). I will try it out when I return at work later next week (I am at a customers site in the beginning of this week). I'll put a post or a comment on how things work out.
April 19, 2009 at 9:19 PM
Anonymous said…
The reason CUCM fails the call is most likely because it was receiving a SIP INVITE from the inside OCS interface. CUCM would have given a 503 because the inside interface is not defined on CUCM as a SIP trunk. CUCM needs the SIP trunk configured to receive the invite.

Does anyone know why OCS R2 Mediation does not use its outside interface when sending the SIP invite to CUCM?

Sounds like a Microsoft bug?
April 20, 2009 at 3:14 PM
Luke E. Babarinde, CISSP said…
I had the same problem and traced it back to a particular Windows Update... http://support.microsoft.com/?kbid=956829

Uninstalling that update fixed my 503 problem.
June 26, 2009 at 12:28 AM
Unknown said…
I have CUCM 7.1.2 setup with OCS R2. We cannot receive calls the outside the OCS client. Any help or documentation for the CUCM would be appreciated.

Thanks.
August 3, 2009 at 9:15 PM
Lasse Nordvik Wedø said…
Could you be more spesific on your problems? Any logs? Any error messages? What call scenarios do work?
August 3, 2009 at 9:25 PM
Anonymous said…
I've had a similar problem. I had 2 IPs configured, 1 for server listening and 1 for gateway listening. I just changed it to use a single IP and it now works.
Hope this helps.
October 21, 2009 at 9:04 PM
Post a Comment