Johann's Unified Communications : mediation

Cisco UC v4/5/6 supported for Direct-SIP with OCS R2

jkruse — Mon, 20 Apr 2009 08:46:34 GMT

The UC Open Interoperability Program has been updated and Cisco Unified Communications Manager (aka Call Manager) versions 4, 5 & 6 are now supported for Direct-SIP connectivity with OCS R2.

This means that back-end integration can be configured between Cisco UC and OCS without the need for a gateway, and without requiring multiple client applications or softphones to be installed on the desktop.

Office Communicator can make/receive phonecalls using Cisco UC as a “PSTN gateway”, but without the need for client plug-ins which can cause version incompatibilities.

So mobile/remote users get the advantages of software-based wideband audio/video/conferencing with VPN-less access via the OCS Edge Server (without requiring an ASA or the associated remote-client licences), and people at their desk can still use their Cisco “hard-phones”.

IP-PBX Vendor	Tested Product	Supported Configuration	Software Versions Tested	OCS 2007 R2	OCS 2007
Cisco	Cisco Unified Communications Manager	Direct SIP	4.2(3)_SR3a
			4.2(3)_SR4b
			5.1(1b)
			5.1(3e)
			6.1(1b)
			6.1(3a)

Known Limitations:

The PRACK message sent by CUCM 4.2(3) is malformed by missing the MAXFORWARDS header. As a result, this configuration requires PRACK to be disabled. By default, PRACK is disabled in CUCM 4.2(3)

For Office Communications Server 2007, this support requires update package for Communications Server 2007 Mediation Server: August 2008 .

OCS 2007 may not appropriately normalize the PAI in the 200 OK or UPDATE, resulting in OC displaying a non RFC3966 formatted global number and in failed RNL on OC. When calling from OC 2007 to a Cisco phone number, after the caller gets connected, the name of the person on the Cisco phone may not be shown on Communicator, and instead OC may display the E.164 number (without a "+") for the person on the Cisco phone. This is resolved in OCS 2007 R2

When calling from OC 2007 to a Cisco phone number, where the Cisco extension is disconnected or out of service, the Cisco IP-PBX may not notify OC 2007 in a timely manner. This has been remediated in OCS 2007 R2.

More information and updates at http://technet.microsoft.com/en-us/office/bb735838.aspx#direct, and example configuration for Call Manager 4 at http://communicationsserverteam.com/archive/2008/09/30/302.aspx

Configuring Cisco CallManager 4.2.1 for Direct-SIP with OCS

jkruse — Thu, 09 Apr 2009 04:19:11 GMT

There is a great post over at the OCS Team Blog outlining the steps required to configure a Direct SIP connection between OCS and Cisco CallManager 4.2.1.

It covers the configuration steps required for both OCS and CCM – check it out at http://communicationsserverteam.com/archive/2008/09/30/302.aspx

Direct SIP connectivity with OCS and Cisco UCM v4.2, 5.1 and 6.1

jkruse — Mon, 08 Sep 2008 11:36:30 GMT

Cisco Unified Communications Manager (aka CallManager) version 4.2, 5.1 and 6.1 (specific version/release below) is now certified for Direct SIP connectivity with Office Communications Server.

Direct SIP allows connectivity between the OCS mediation server and the Cisco IP-PBX without the need for a gateway, meaning that Office Communicator users can be enabled for Enterprise Voice (i.e. Office Communicator is a full soft-phone, not just click-to-call or RCC) without significant upgrades or hardware replacements.

More detail at http://technet.microsoft.com/en-us/office/bb735838.aspx

IP-PBX Vendor

Tested Product

Qualification Level

Software Version Tested

Vendor’s Web site

Cisco

Cisco Unified Communications Manager

Direct SIP

4.2[3]sr3a

5.1.3.3000-5 & 5.1.3.1000-12

6.1.1.3000-2

(requires update package for Communications Server 2007 Mediation Server: August 2008)

Cisco

Share this post :

Office Communications Server 2007 VoIP Test Set

jkruse — Tue, 15 Apr 2008 03:00:00 GMT

Microsoft Office Communications Server 2007 VoIP Test Set enables you to simulate a SIP endpoint to test connectivity.

VoIP Test Set for Office Communications Server 2007 supports emulation of a SIP endpoint to test connectivity. Emulation options include the following:

Client emulation - To emulate a Microsoft Office Communicator client, you specify a SIP-enabled user account to register with Office Communications Server. This can be useful for troubleshooting problems with incoming or outgoing Enterprise Voice calls. For example, an Office Communications Server engineer can use the tool in client emulation mode to quickly change user location profile information and validate that outbound routing is properly configured.
Server emulation - You can use VoIP Test Set to emulate a Mediation Server or a gateway. To emulate a server, you specify the IP address, port number, and other settings of the server to be emulated. This can be useful for emulating components during the setup of the Office Communications Server 2007 infrastructure to verify the functionality of components that have already been deployed. For example, you might use the tool to receive and make calls directly from an IP/PSTN gateway to ensure that it is completely functional before deploying the complete Office Communications Server 2007 infrastructure.

Download it from http://www.microsoft.com/downloads/details.aspx?FamilyID=7b6ab4f3-2949-4e97-856e-9c4ae323c75a&displaylang=en

Share this post :

Technorati Tags: ocs, download, testing, voip, mediation, sip, tools