Partner Config Guide Microsoft OCS 2007 RCC

BroadSoft Partner Configuration Guide

Microsoft OCS 2007

December 2009 Document Version 1.8

220 Perry Parkway Gaithersburg, MD USA 20877 Tel +1 301.977.9440 Fax +1 301.977.8846

WWW.BROADSOFT.COM

BroadWorks® Guide

Copyright Notice Copyright© 2009 BroadSoft, Inc.

All rights reserved.

Any technical documentation that is made available by BroadSoft, Inc. is proprietary and confidential and is considered the copyrighted work of BroadSoft, Inc.

This publication is for distribution under BroadSoft non-disclosure agreement only. No part of this publication may be duplicated without the express written permission of BroadSoft, Inc. 220 Perry Parkway, Gaithersburg, MD 20877.

BroadSoft reserves the right to make changes without prior notice.

Trademarks BroadWorks® and BroadWorks Assistant–Enterprise™, BroadWorks Call Center™, BroadWorks Communicator™, BroadWorks Receptionist™, and BroadWorks Deployment Studio™ are trademarks of BroadSoft, Inc.

Microsoft, MSN, Windows, and the Windows logo are registered trademarks of Microsoft Corporation. Other product names mentioned in this document may be trademarks or registered trademarks of their respective companies and are hereby acknowledged.

This document is printed in the United States of America.

BROADSOFT PARTNER CONFIGURATION GUIDE – MICROSOFT OCS 2007 20-BD5251-00

©2009 BROADSOFT, INC. PAGE 2

Document Revision History

Version Reason for Change

1.1 Initial version for Microsoft OCS 2007 Release 14.sp7 testing.

1.2 Edited and published document.

1.3 Updated for Release 16.0 UC-Connect Configuration.


1.5 Updated issues section.


1.7 Added Acme Packet SBC configuration instructions for domain mapping between OCS and BroadWorks when OCS domain does not match the BroadWorks user domain.




Table of Contents

1 Overview .......................................................................................................................................... 6

2 Interoperability Status ................................................................................................................... 7

2.1 Verified Versions ........................................................................................................................... 7 2.2 Interface Capabilities Supported .................................................................................................. 7 2.3 Known Issues ............................................................................................................................ 10

3 Solution Configuration ................................................................................................................ 12

4 BroadWorks Configuration......................................................................................................... 14

4.1 BroadWorks UC-Connect Configuration .................................................................................. 14 4.1.1 BroadWorks XSP System CLI Configuration .................................................................. 14 4.1.2 BroadWorks UC-Connect CAP CLI Configuration ......................................................... 14

4.2 BroadWorks Application Server Configuration ........................................................................ 15 4.2.1 BroadWorks Application Server CLI Configuration ......................................................... 15 4.2.2 BroadWorks Application Server CLI Configuration Example ......................................... 15 4.2.3 BroadWorks Application Server User Configuration ...................................................... 15

5 Microsoft OCS 2007 RCC Configuration .................................................................................. 17

5.1 Microsoft OCS 2007 User Configuration .................................................................................. 18 5.2 Microsoft OCS 2007 Route Configuration ................................................................................ 19 5.3 Microsoft OCS 2007 Authenticated Host Configuration .......................................................... 20 5.4 Microsoft OCS 2007 OCS Front End Server Transport Configuration ................................... 21

6 Solution for Non-Matching User IDs ......................................................................................... 22

6.1 Option 1: Modify the BroadWorks User ID .............................................................................. 22 6.2 Option 2: Use Acme Packet to Map between User IDs ......................................................... 22

6.2.1 Many-to-One Domain Mapping ....................................................................................... 22 6.2.2 One-to-One Domain Mapping ......................................................................................... 27

References ............................................................................................................................................. 29



Table of Figures

Figure 1 Solution Configuration ............................................................................................................... 12 Figure 2 BroadWorks User ID/Microsoft OC Sign-in .............................................................................. 13 Figure 3 BroadWorks Application Server User Configuration ................................................................ 16 Figure 4 Microsoft OCS 2007 User Configuration .................................................................................. 18 Figure 5 Microsoft OCS 2007 Route Configuration ................................................................................ 19 Figure 6 Microsoft OCS 2007 Authenticated Host Configuration .......................................................... 20 Figure 7 Microsoft OCS 2007 OCS Front End Server Transport Configuration ................................... 21



1 Overview

This document describes the configuration procedures required for the Microsoft Office Communications Server (OCS) 2007 to be interoperable with BroadWorks.

The integrated solution allows the Microsoft Office Communicator (OC) client to perform remote call control of office phones registered with BroadWorks.

Microsoft OCS can be deployed as a premise-based or hosted solution. Hosted OCS is a component of Microsoft Hosted Messaging and Collaboration (HMC 4.5) solution. The configuration description provided in this document applies to both the premise-based and hosted deployment models.

It is assumed that Microsoft OCS 2007 and BroadWorks are already installed and working independently. This document describes only the configuration required to link these components as a solution. Build-up of the individual components is outside the scope of this document.

This guide describes the specific configuration items that are important for use with BroadWorks. It does not describe the purpose and use of all Microsoft OCS configuration items. For those details, see the Microsoft® Office Communications Server 2007 Administration Guide [1].



2 Interoperability Status

This section provides the known interoperability status of the Microsoft OCS 2007 with BroadWorks. This includes the version(s) tested and known issues.

Interoperability testing validates that the device interfaces properly with BroadWorks via the SIP interface. Qualitative aspects of the device or device capabilities not affecting the SIP interface such as display features and performance are not covered by interoperability testing. Requests for information and/or issues regarding these aspects should be directed to Microsoft.

2.1 Verified Versions The following table identifies the verified versions of Microsoft OCS 2007and BroadWorks along with the month/year the testing occurred. If the device has undergone more than one test cycle, versions for each test cycle are listed, with the most recent listed first.

Generally, maintenance releases of the validated version are considered compatible. Contact Microsoft for any questions concerning maintenance and compatible releases.

NOTE: Interoperability testing is normally performed with the latest generally available (GA) device firmware/software and the latest GA BroadWorks release and service pack at the time the testing occurs. If there is a need to use a non-verified mix of BroadWorks and device software versions, customers can mitigate their risk by self-testing the combination using the BroadWorks Microsoft Office Communicator 2007 RCC Interoperability Test Plan [6].

Verified Versions Table

Date (mm/yyyy)

BroadWorks Release

Microsoft OCS 2007 Version

Microsoft OCS 2007 Compatible Versions

10/2008 14.sp7 OCS 2007 OCS 2007 R2

2.2 Interface Capabilities Supported Microsoft OCS has completed interoperability testing with BroadWorks using the BroadWorks Microsoft Office Communicator 2007 RCC Interoperability Test Plan [6]. The results from the latest testing are summarized in the following table.

The BroadWorks Microsoft Office Communicator RCC test plan is composed of sections, each covering distinct functional areas, such as Call Origination, Transfer, and Conference. Each section is composed of one or more section items in turn composed of one or more test cases. The test plan exercises the RCC interface between Microsoft OCS and BroadWorks with the intent to ensure interoperability.

The Supported column identifies the Microsoft OCS/BroadWorks solution support for each of the items covered in the test plan packages, with the following designations:

Yes Test item is supported.

No Test item is not supported.

NT Test item was not tested.

Caveats or clarifications are identified in the Comments column.



BroadWorks Microsoft OC Test Plan Support Table

Test Plan Section Test Plan Section Items Supported Comments

OC Sign In Sign In Yes

Sign In; Invalid Login Yes

Sign In; with Active Call No Not supported by OC (no call window)

Call Origination Using OC

Intragroup Yes

Intragroup OC Yes

Intergroup Yes

PSTN Yes

Call Origination Using OC

Intragroup Yes

Intragroup OC Yes

Intergroup Yes

PSTN Yes

Call Termination Using OC

Intragroup Yes

Intergroup Yes

PSTN Yes

Call Termination Using Phone

Intragroup Yes

Intergroup Yes

PSTN Yes

Dial Patterns Extension Yes

National (10-Digit) Yes

National Toll (11-Digit) Yes

Operator Yes

International Yes

FAC (*XX) Yes

Speed Dial 8 (X) Yes

Speed Dial 100 (#XX) No Not supported by OC

Call Origination Methods

Digit Typing Yes

Contact List Yes

Recent Contacts List Yes

Smart Tag NT

Outlook NT

IM to RCC Escalation Yes



BroadWorks Microsoft OC Test Plan Support Table

Calling Line ID Intragroup Yes

Intergroup Yes

Intergroup Anonymous No Not supported by OC

PSTN Yes

PSTN Anonymous No Not supported by OC

Redirect Redirect to Mobile Yes

Redirect to Voice Mail Yes

Call Hold OC Hold/Retrieve Yes

Phone Hold/Retrieve Yes

Call Origination – Second Call

OC Originate Second Call Yes

Phone Originate Second Call Yes

Call Waiting OC Answer Second Call Yes

Phone Answer Second Call Yes

Blind Transfer OC Blind Transfer Yes

Phone Blind Transfer Yes

Transfer Failure No Not supported by BroadWorks

Blind Personal Transfer

OC Blind Personal Transfer Yes

Consultative Transfer OC Consultative Transfer Yes

Phone Consultative Transfer Yes

Ad-Hoc Conference OC Ad-Hoc Conference No Not supported by OC

Phone Ad-Hoc Local Conference No Not supported by OC

Phone Ad-Hoc Network Conference Yes

Call Forward Sync OC Enabled Call Forward Sync to BroadWorks No Not supported by

BroadWorks UC-Connect

BroadWorks Call Forward Sync to OC No Not supported by

BroadWorks UC-Connect

Do Not Disturb Sync OC Do Not Disturb Sync to BroadWorks No Not supported by OC

BroadWorks Do Not Disturb Sync to OC No Not supported by OC

DTMF Tones OC DTMF Tones No Not supported by BroadWorks

BroadWorks Features Voice Messaging Yes

Remote Office Yes

Shared Call Appearance Yes



2.3 Known Issues This section lists the known interoperability issues between BroadWorks and specific partner release(s). Issues identified during interoperability testing and known issues identified in the field are listed.

The following table provides a description of each issue and, where possible, identifies a workaround. The verified partner device versions are listed with an “X” indicating that the issue occurs in the specific release. The issues identified are device deficiencies or bugs, so typically not BroadWorks release dependent.

The Issue Number is a BroadSoft ExtraView partner issue number if the testing was performed by BroadSoft. If the testing was performed by the partner or a third party, the partner may or may not supply a tracking number.

For more information on any issues related to the particular partner device release, see the partner release notes.

Issue Number Issue Description Microsoft Version

OC

S 2007

EV 69845 Three-Way Conference fails, resulting in the conferenced party ending up on hold.

In Three-Way Conference scenarios where the phone controls and mixes the conference locally, the original called party ends up on hold when the Three-Way Conference should be active. In this scenario, the Microsoft OC client is requested to display two active calls, which it does not support, so it automatically puts the first call on hold.

Workaround: Configure the phone for network conference. In this configuration, BroadWorks mixes the conference.

X

EV 69846 Caller ID incorrect on blind transfer calls.

For scenarios in which A calls B and A blind transfers B to C, the caller ID to C shows A rather than B.

Workaround: None.

X



Issue Number Issue Description Microsoft Version

EV 93073 UC-Connect - MOC Client does not ignore call.

Pressing the “Ignore button” on the incoming call toast does not stop the phone from ringing.

Workaround: None.

Comments: This is a limitation/not supported feature of the RCC enabled User MOC client. Clicking ignore on the toast window will not have any effect. This is also true for the MOC’s DND feature. See http://technet.microsoft.com/en-us/magazine/2009.03.rcc.aspx?pr=blog#id0110047 for details. The RCC limitation is excerpted following.

“RCC provides an easy way for achieving integration with an existing PBX deployment. However, an RCC-enabled user's capabilities are limited by what the wired PBX phone can do. For example, an Enterprise Voice user can leverage native OCS support for outside voice capabilities and make and receive VoIP calls from both inside and outside the organization. Enterprise Voice scenario also enables several presence features that OCS provides (such as Presence access levels to Team, allowing urgent interruptions during Do Not Disturb). An RCC-only user will not have access to these features. In addition, other features, such as escalating two-party conferences to a multi-party conference, are also only supported with Enterprise Voice users. In an RCC system, the PBX is the master of the call-handling rules. Therefore, any settings or rules that divert calls automatically or send these to a shared line are actually controlled at the PBX. New features available to an Enterprise Voice user, such as Simultaneous Ringing and the Delegation feature introduced with OCS 2007 R2 are not available for an RCC-only user.”

X

EV 102879 Presence Status Changes to “Available” while still in a call.

This is observed when an OC user is in a call and closes the OC conversation window, the OC status changes to “Available”. However, the OC user is still in a call. The presence status does not reflect the user’s true presence status, “In a call”.

Workaround: None.

X

EV 97667 MCA call causes first call to go on hold.

This issue is related to EV 69845. In SCA MCA scenarios when the user initiates a call from an alternate appearance, this causes a second RCC call to be presented to MOC. MOC automatically puts the first call on hold as it does not allow two active calls.

Workaround: There is no true workaround, but to avoid the scenario do not enable MCA on the BroadWorks SCA feature.

X



http://technet.microsoft.com/en-us/magazine/2009.03.rcc.aspx?pr=blog#id0110047

http://technet.microsoft.com/en-us/magazine/2009.03.rcc.aspx?pr=blog#id0110047

3 Solution Configuration

The solution diagram in Figure 1 shows the test environment of the integrated components: Microsoft OCS 2007 and BroadWorks. The Microsoft OCS server in the diagram represents either the hosted HMC 4.5 or premise-based OCS solutions. Note that the desk phone in the following solution diagram would normally be behind an SBC in a deployed scenario, but that interface has been omitted from the diagram.

The solution message flow is explained as follows. For remote call control performed by Mike using his Microsoft Office Communicator client, a CSTA message is generated and sent over SIP by OCS to the CSTA gateway. The UC-Connect application on the BroadWorks XSP performs the CSTA gateway function which converts the CSTA message to CAP; BroadWorks then performs the requested function, for example, alerting Mike’s desk phone.

Likewise, when Mike receives a call, BroadWorks generates a CAP message indicating an incoming call and sends it to the UC-Connect server. The UC-Connect server converts the CAP message to CSTA over SIP and sends the message to OCS, resulting in a pop-up toast on Mike’s computer for the incoming call.

The BroadWorks XSP can optionally be fronted by the Acme Packet SD for TLS termination and/or NAT traversal. The TLS and NAT Traversal configuration are outside the scope of this document. Refer to the Acme Packet Net-Net® Session Director Configuration Guide [8] and the BroadSoft Partner Configuration Guide Acme Packet Net-Net® Session Director [9] for SD configuration detail. Note that each CSTA session traversing the Acme Packet SD consumes a SD session license.

Figure 1 Solution Configuration



As stipulated in the BroadWorks UC-Connect Product Description [5] (section 6.3.3) the Microsoft Office Communicator (MOC) sign-in address must match the BroadWorks user ID. Figure 2 shows an example of matched MOC sign-in address and BroadWorks user ID.

In some cases it is not feasible to match the MOC sign-in address with the BroadWorks user ID. This may occur in situations where the OCS active directory and BroadWorks users have already been created and are in use before implementing this solution. Section 6 Solution for Non-Matching User IDs discusses options for handling non-matching user IDs.

Figure 2 BroadWorks User ID/Microsoft OC Sign-in

The following sections describe how to configure the solution components to enable this configuration. Note that it is assumed that Microsoft OCS 2007 and BroadWorks are already installed, configured, and working independently as those configuration details are not provided here.



4 BroadWorks Configuration

This section identifies the BroadWorks configuration required to integrate Microsoft OCS 2007 for third-party call control. A detailed description for enabling BroadWorks for third-party call control can be obtained from the BroadWorks External Portal Integration Guide [7]. This configuration is not unique to the Microsoft OCS 2007 integration, but is provided here for completeness.

4.1 BroadWorks UC-Connect Configuration The BroadWorks UC-Connect Application resides on the BroadWorks Xtended Service Platform (XSP) which is introduced in Release 16. For details of the BroadWorks UC-Connect, see BroadWorks UC-Connect Product Description Guide [5].

The UC-Connect performs CSTA-to-CAP translation and can be configured through BroadWorks CLI.

4.1.1 BroadWorks XSP System CLI Configuration

This table identifies the steps required to configure the BroadWorks XSP to integrate with BroadWorks Application Server.

Step Command Purpose

Step 1 Go to System Default configuration.

XSP_CLI/System/CommunicationUtility/DefaultSettings>

From the XSP cli, traverse to the default system configuration level.

Step 2 Set Deploy mode.

XSP_CLI/System/CommunicationUtility/DefaultSettings>set mode NS 64.215.212.64

The mode attribute (Application Server or Network Server) refers to the integration scheme used to integrate with the Application Server clusters. In Network Server (NS) mode, Network Server lookups are used to dynamically resolve the Application Server clusters.

Note that all Application Server clusters must use the same OCI port when using the Network Server (NS) mode.

4.1.2 BroadWorks UC-Connect CAP CLI Configuration

This table identifies the steps required to configure the CAP attributes of the BroadWorks UC-Connect Application.


Step 1 Go to CAP configuration.

XSP_CLI/Applications/UC-Connect_16.0_1.226/CAP>

From the XSP cli, traverse to the UC-Connect CAP configuration level.

Step 2 Set CAP Port.

Port <BroadWorks-OCS-port>

Identifies the TCP port of the BroadSoft Open Client Server (OCS). CAP message are sent to this port. The default BroadWorks OCS port is 2208.



4.2 BroadWorks Application Server Configuration The following subsections describe the BroadWorks Application Server steps necessary to enable third-party call control. The BroadWorks XSP directs CAP messages to the BroadWorks Application Server. The configuration described following includes identifying the BroadWorks XSP address in the external authentication table and ensuring the Client License 16 service is assigned to each BroadWorks user enabled with the Microsoft OC client.

4.2.1 BroadWorks Application Server CLI Configuration


Step 1 Go to External Authentication config.

AS_CLI> system;NetworkAccessLists;ExtAuth

AS_CLI/System/NetworkAccessLists/ExtAuth>

From the Application Server cli, traverse to the External Authentication configuration level.

Step 2 Add BroadWorks XSP address(es).

AS_CLI/System/NetworkAccessLists/ExtAuth> add <bw-xsp-address> UC-Connect

Add each BroadWorks XSP Server address to the external authentication table to allow CAP logins from the XSP to bypass authentication.

4.2.2 BroadWorks Application Server CLI Configuration Example

AS_CLI/System/NetworkAccessLists/ExtAuth> get Net Address Description ========================= 64.215.212.77 UC-Connect

4.2.3 BroadWorks Application Server User Configuration

To enable Microsoft OC remote call control, the Client License 16 service must be assigned to each BroadWorks user as shown in the following screen shot. There is no further configuration required for the Client License 16 service.



Figure 3 BroadWorks Application Server User Configuration



5 Microsoft OCS 2007 RCC Configuration

Microsoft OCS 2007 RCC is configured through Windows Administration Tools. The following configuration example is based upon an installation of Microsoft OCS 2007 Standard Edition, referred to as OCS in the following sections.

The capabilities of the OCS RCC have been verified for use with BroadWorks based on the settings described in the following section. For more information on the meaning, purpose, and applicability of the individual configuration items see the Microsoft® Office Communications Server 2007 Enterprise Voice Planning and Deployment Guide [2].

In this section, CSTA Gateway refers to the BroadWorks UC-Connect server.



5.1 Microsoft OCS 2007 User Configuration To configure a user for Remote Call Control feature, select the target user as shown in the following screen shot. Navigate to User Option and click on the radio button to enable Remote Call Control.

Configure the following:

Server URI: Configure a Server URI for the user. This Server URI points to the CSTA Gateway. The Server URI must be in SIP URI form.

Line URI: Configure a Line URI for the user. The Line URI identifies the user’s E.164 telephone number. The Line URI must be in TEL URI format.

Figure 4 Microsoft OCS 2007 User Configuration



5.2 Microsoft OCS 2007 Route Configuration SIP traffic from Office Communicator goes through OCS and is proxied by OCS to the CSTA gateway. The FQDN of the CSTA gateway is identified in the OCS Server URI field. For each Server URI, a route must be configured with the destination address to which OCS must proxy the CSTA remote call control messages.

For each route to a CSTA Gateway, configure the following:

Match URI Domain: The syntax sip*@[CSTA Gateway FQDN] indicates that this route will be used for any number (*) where the domain matches the FQDN for the CSTA gateway.

Next Hop IP Address: The IP address of the CSTA Gateway.

Next Hop Port: The CSTA Gateway port for SIP traffic.

Next Hop Transport protocol: The transport protocol from OCS to the CSTA gateway. The transport must be TCP unless Acme Packet is inserted to provide TLS termination.

Figure 5 Microsoft OCS 2007 Route Configuration



5.3 Microsoft OCS 2007 Authenticated Host Configuration If TCP is used as the transport protocol between OCS and the CSTA gateway, a host authorization entry must also be added so that the Office Communication Server treats the CSTA gateway as authenticated. To add the CSTA GW as an authenticated server, refer to the following screen shot.

Figure 6 Microsoft OCS 2007 Authenticated Host Configuration



5.4 Microsoft OCS 2007 OCS Front End Server Transport Configuration The OCS Front End Server transport setting identifies the transports available for the OC client. The default transport is TLS. To optionally enable TCP transport, refer to the following example.

Figure 7 Microsoft OCS 2007 OCS Front End Server Transport Configuration



6 Solution for Non-Matching User IDs

The configuration described throughout this document requires the BroadWorks User ID and MOC Sign-In address to match. This section identifies solution configuration options when they do not.

6.1 Option 1: Modify the BroadWorks User ID For deployments in which the OCS Active Directory and the BroadWorks users have already been created independently and the user IDs do not match, the simplest option is to change the BroadWorks user ID to match the MOC sign-in address. The primary advantage to this option is that no additional equipment is required.

This option will not accommodate every deployment scenario, but is an option to consider especially if the service provider does not enable BroadWorks end user logins, as in some SIP trunking deployments, since the end users would not need to be notified of the change.

6.2 Option 2: Use Acme Packet to Map between User IDs The Acme Packet SD can be inserted between OCS and UC-Connect to map non-matching user IDs between the systems.

Acme Packet can be configured with Header Manipulation Rules (HMRs) to perform mapping of the URI domains. The SD can also be configured to map the URI user portion if the user portions are different AND the MOC username is being mapped to the user’s phone number.

6.2.1 Many-to-One Domain Mapping

A common deployment scenario requires many-to-one domain mapping. This involves multi-enterprise OCS domains mapping to a single BroadWorks domain, as shown in the following table.

Many-to-One Domain Map

MOC Sign-on Address BroadWorks User ID

[email protected] [email protected]


[email protected] [email protected] The many-to-one domain mapping scenario may also require mapping the OCS username to the user’s number, if the BroadWorks user ID is created as phone-number@domain, as shown in the following table.

Many-to-One Domain Map with Username to Number Map







The Acme Packet SD can be configured to handle the many-to-one mapping scenarios described above. Section 6.2.1.1 Many-to-One Domain Mapping with Username to Number Map Example provides an Acme Packet configuration example of the HMRs required to perform the many-to-one domain map with username to number map.

6.2.1.1 Many-to-One Domain Mapping with Username to Number Map Example

This mapping converts between an OCS sign-in address such as [email protected] and a corresponding BroadWorks user ID [email protected].

This mapping requires the SBC to supply the OCS user id information as URI parameters in the SIP CONTACT for SIP requests to BroadWorks UC-Connect. The requests from UC-Connect to the SBC will then contain the OCS user id information as URI parameters in the REQUEST-URI. .As a result, the SBC is able to reconstruct the request before sending it to OCS.

The following sections provide configuration details for creating the Acme Packet HMRs to perform the mapping. HMR 1 performs the required manipulation for requests from OCS to BroadWorks. HMR 2 performs the required manipulation for requests from BroadWorks to OCS.

6.2.1.1.1 HMR 1: OCS Acme BroadWorks HMR 1 enables the Acme Packet SD to make changes on SIP FROM and CONTACT headers for SIP requests from OCS to BroadWorks.

6.2.1.1.1.1 HMR 1 Processing Summary For SIP requests from OCS, the Acme Packet SD performs the following to create the request bound for BroadWorks:

Inserts the user portion and the host portion of the OCS FROM header URI as two URI parameters in the CONTACT Header: ocsOrigUser and ocsOrigHost.

Replaces the user portion of the CONTACT header URI with the OCS TO header user portion.

Replaces the user portion of the FROM header URI with the OCS TO header user portion.

Replaces the host portion of the FROM header URI with “ims.com”. Note that the host portion mapping is a static mapping.

6.2.1.1.1.2 HMR 1 Before and After This section shows the SIP headers before and after Acme Packet SD applies HMR 1.

SIP headers before applying manipulation rule From: "Feng Wei"<sip:[email protected]>;tag=f1594ad0e7;epid=3708cdf21c Contact: <sip:[email protected];opaque=user:epid:IKBNv8UyJlegSCoHEcarNgAA;gruu>

SIP headers after applying manipulation rule From: "Feng Wei" <sip:[email protected]>;tag=f1594ad0e7;epid=3708cdf21c Contact: <sip:[email protected]:5060;opaque=user:epid:IKBNv8UyJlegSCoHEcarNgAA;gruu;ocsOrigUser=fwei;ocsOrigHost=broadsoftuc.com;transport=tcp



mailto:[email protected]

mailto:[email protected]

6.2.1.1.1.3 HMR 1 Configuration This section shows the HMR1 Configuration in detail. /********************************** * HMR 1.) OCS ==> Acme ==> UC-Connect **********************************/ sip-manipulation name toUC-Connect description OCS ==> Acme ==> UC-Connect header-rule name toURI header-name To action store comparison-type pattern-rule match-value [0-9]{11} msg-type request new-value methods header-rule name frURI header-name From action manipulate comparison-type case-sensitive match-value msg-type request new-value methods element-rule name origOcsUser parameter-name type uri-user action store match-val-type any comparison-type case-sensitive match-value new-value element-rule name origOcsHost parameter-name type uri-host action store match-val-type any comparison-type case-sensitive match-value new-value element-rule name imsUser parameter-name type uri-user action replace match-val-type any comparison-type case-sensitive match-value new-value $toURI.$0 element-rule name imsHost parameter-name type uri-host action replace match-val-type any comparison-type case-sensitive match-value new-value ims.com header-rule name AddOcsOrigUri header-name Contact action manipulate



comparison-type boolean match-value msg-type request new-value methods element-rule name addOcsOrigUserParam parameter-name ocsOrigUser type uri-param action add match-val-type any comparison-type boolean match-value $frURI.$origOcsUser new-value $frURI.$origOcsUser.$0 element-rule name addOcsOrigHostParam parameter-name ocsOrigHost type uri-param action add match-val-type any comparison-type boolean match-value $frURI.$origOcsHost new-value $frURI.$origOcsHost.$0 element-rule name changeUser parameter-name type uri-user action replace match-val-type any comparison-type boolean match-value new-value $toURI.$0

6.2.1.1.2 HMR 2: BroadWorks Acme OCS HMR 2 enables the Acme Packet SD to make changes on SIP REQUEST-URI and TO headers for SIP requests from BroadWorks to OCS.

6.2.1.1.2.1 HMR 2 Procedure Summary For SIP requests from BroadWorks, the Acme Packet SD performs the following to create the request bound for OCS:

Replaces the user portion and the host portion of the REQUEST URI with the ocsOrigUser and ocsOrigHost parameter values respectively.

Removes the ocsOrigUser and ocsOrigHost parameters from the REQUEST URI.

Replaces the user portion and the host portion of the TO header with the ocsOrigUser and ocsOrigHost parameter values respectively.

6.2.1.1.2.2 HMR 2 Before and After This section shows the SIP headers before and after Acme Packet SD applies HMR 2.

SIP headers before applying manipulation rule. INFO sip:[email protected]:5060;opaque=user:epid:IKBNv8UyJlegSCoHEcarNgAA;gruu;ocsOrigUser=fwei;ocsOrigHost=broadsoftuc.com;transport=tcp SIP/2.0 To: "Feng Wei"<sip:[email protected]>;tag=f1594ad0e7;epid=3708cdf21c

SIP headers after applying manipulation rule



INFO sip:[email protected];opaque=user:epid:IKBNv8UyJlegSCoHEcarNgAA;gruu SIP/2.0 To: "Feng Wei"<sip:[email protected]>;tag=f1594ad0e7;epid=3708cdf21c

6.2.1.1.2.3 HMR 2 Configuration This session shows the HMR 2 configuration in detail.

/******************************************** * HMR 2.) UC-Connect ==> Acme ==> OCS ******************************************** sip-manipulation name toOCS description UC-Connect ==> Acme ==> OCS header-rule name RURI header-name request-uri action manipulate comparison-type case-sensitive match-value msg-type request new-value methods element-rule name origOcsUser parameter-name ocsOrigUser type uri-param action store match-val-type any comparison-type case-sensitive match-value new-value element-rule name origOcsHost parameter-name ocsOrigHost type uri-param action store match-val-type any comparison-type case-sensitive match-value new-value element-rule name ruriUser parameter-name type uri-user action replace match-val-type any comparison-type boolean match-value $RURI.$origOcsUser new-value $RURI.$origOcsUser.$0 element-rule name ruriHost parameter-name type uri-host action replace match-val-type any comparison-type boolean match-value $RURI.$origOcsHost new-value $RURI.$origOcsHost.$0 element-rule name delOcsOrigUser parameter-name ocsOrigUser type uri-param action delete-element match-val-type any comparison-type case-sensitive match-value



new-value element-rule name delOcsOrigHost parameter-name ocsOrigHost type uri-param action delete-element match-val-type any comparison-type case-sensitive match-value new-value header-rule name toURI header-name To action manipulate comparison-type case-sensitive match-value msg-type request new-value methods element-rule name toUser parameter-name type uri-user action replace match-val-type any comparison-type boolean match-value $RURI.$origOcsUser new-value $RURI.$origOcsUser.$0 element-rule name toHost parameter-name type uri-host action replace match-val-type any comparison-type boolean match-value $RURI.$origOcsHost new-value $RURI.$origOcsHost.$0

6.2.2 One-to-One Domain Mapping

A less common deployment scenario requires one-to-one domain mapping as shown in the following table. The Acme Packet SD is capable of handling this scenario also but requires more detailed HMRs and is not as easily scalable since SBC modifications are required for every enterprise.

One-to-One Domain Map








Another less common deployment scenario (to be avoided if possible) requires one-to-one or arbitrary domain mapping and arbitrary user portion mapping. The following table shows mapping of arbitrary domains and user portions. This mapping is complex and is not resolvable using only HMRs on the Acme Packet SD.

Arbitrary Domain Map with Arbitrary Username Map










References

[1] Microsoft, Inc. July, 2007. Microsoft® Office Communications Server 2007 Administration Guide. Available from Microsoft at www.microsoft.com.

[2] Microsoft, Inc. July, 2007. Microsoft® Office Communications Server 2007 Enterprise Voice Planning and Deployment Guide. Available from Microsoft at www.microsoft.com.

[3] Microsoft, Inc. October, 2007. PBX Telephony Features (CSTA/RCC) Specification for Microsoft Office Communicator 2007. Available from Microsoft at www.microsoft.com.

[4] Microsoft, Inc. July, 2007. Integrating Telephony with Office Communications Server 2007. Available from Microsoft at www.microsoft.com.

[5] BroadSoft, Inc. BroadWorks UC-Connect Product Description. Available from BroadSoft at www.broadsoft.com/xchange.

[6] BroadSoft, Inc. BroadWorks Microsoft Office Communicator 2007 RCC Interoperability Test Plan, Release 15.0. Available from BroadSoft at www.broadsoft.com/xchange.

[7] BroadSoft, Inc. BroadWorks External Portal Integration Guide, Release 15.0. Available from BroadSoft at www.broadsoft.com/xchange.

[8] Acme Packet, Inc. February, 2008. Acme Packet Net-Net® Session Director Configuration Guide, Release Version 5.1. Available from Acme Packet at www.acmepacket.com.

[9] BroadSoft, Inc. BroadSoft Partner Configuration Guide Acme Packet Net-Net® Session Director. Available from BroadSoft at www.broadsoft.com/xchange.

http://www.microsoft.com/




http://www.broadsoft.com/xchange



http://www.acmepacket.com/


Documents

Partner Config Guide Microsoft OCS 2007 RCC