All Things Unified

ABServer.exe –syncnow Script

Wes Glockzin — Tue, 24 Jan 2012 11:44:33 GMT

I recently worked with a customer that has a rather large OCS deployment. Five Edge servers, two Director servers and Seven Front End servers. They mainly leverage OCS for its IM/Presence and Live Meeting features. All users are remote so all logins are via the Edge servers. There was a need to manually run the “ABServer.exe –syncnow” on the particular server that has the ABService service running. Since they have seven Front Ends, a solution was found programmatically of determining what server was actually running the ABService and then running the “ABServer.exe –syncnow” switch at a predetermined time via task scheduler.

#Searches tasklist for "IMAGENAME eq abserver.exe" (ABServer service)
#If ABService is NOT found to be running, script ends
#If ABService is found to be running, script continues and executes: abserver.exe -syncnow

@echo off
tasklist /FI "IMAGENAME eq abserver.exe" /FO CSV > search.log

FINDSTR ABServer.exe search.log > found.log

FOR /F %%A IN (found.log) DO IF %%~zA EQU 0 GOTO end

exit

:end

@echo Running ABServer.exe -syncnow

cd "C:\Program Files\Microsoft Office Communications Server 2007 R2\Server\Core"

abserver.exe -syncnow

del search.log
del found.log

Technorati Tags: Office Communications Server 2007 R2,OCS,address book,abserver.exe

LYNC Meeting Policy and Outlook Add-on behavior

Wes Glockzin — Mon, 16 May 2011 08:19:54 GMT

You want to generate a new meeting ID as the default (authenticated meetings) and you run the LYNC Server Management cmdlet Set-CsMeetingConfiguration –DesignateAsPresenter None. However, it appears you still have to choose the “customize” checkbox before it will default to a private meeting. Without choosing customize it will still create a public meeting (using the static meet ID). If you click the customize box in the outlook add-in and click remember settings, add-in will create private meeting every time you schedule a meeting. If you don’t customize the options in the add-in or remove the checkbox it will create a public meeting with static meeting ID.

Using the LYNC Server Management Shell there are two switches for the cmdlet Set-CsMeetingConfiguration that can affect this.

EnableAssignedConferenceType – Indicates whether users are allowed to schedule public meetings. With a public meeting, the conference ID and the meeting link remain consistent each time the meeting is held. With a private meeting, the conference ID and meeting link change from meeting to meeting. The default value is True.
AssignedConferenceTypeByDefault – Determines whether new meetings will be configured, by default, as public meetings. Set this value to True to use public meetings by default; set this value to False to use private meetings by default. The default value is True.

If you set EnableAssignedConferenceType to false, there is now, no checkbox to customize settings

When EnableAssignedConferenceType is set to false, outlook will always create a new private meeting with different meeting id.

http://technet.microsoft.com/en-us/library/gg398648.aspx

Default setting of supporting SIP REFER and using an unsupported gateway with LYNC 2010

Wes Glockzin — Mon, 17 Jan 2011 15:57:33 GMT

I recently worked an issue where the default setting of “Enable refer support” caused a routing failure with an Enterprise Voice scenario. The customer is configured with a direct SIP trunk from their ISP that’s pointed to their Lync Mediation role. In this scenario, an inbound call from an external PSTN user hits the Exchange Unified Messaging 2010 (EUM) Auto Attendant (AA). The EUM AA was configured with a Lync Dial Plan. When the AA tried to connect the inbound caller to the Lync enabled internal user by the SIP REFER method, it failed to connect.

SIP Stack tracing from the Mediation Server logged the following SIP error:

SIP /2.0 400 Refer-To: user name not found

When reviewing a network capture from the Lync client, the VoIP call graph analysis showed the following:

|30.916 | REFER | |SIP Request

| |(5060) <------------------ (63788) |

|30.964 | 400 Refer-To: user name not found |SIP Status

| |(5060) ------------------> (63788) |

As stated before, the “Enable refer support” switch is enabled by default.

If you have deployed Lync with Enterprise Voice and utilize a “supported” gateway, SIP REFER works as expected. However, you are not using a “supported” gateway or have a SIP trunk being provided by a ISP that is not using a “supported” gateway or a gateway that does not support SIP REFER, you will need to disable the default setting for SIP REFER support. It is recommended that you verify whether or not the SIP trunk provider supports SIP REFER.

http://technet.microsoft.com/en-us/library/gg425831.aspx

Migrate custom Auto Attendant prompts to Exchange Unified Messaging 2010 SP1

Wes Glockzin — Mon, 22 Nov 2010 09:50:58 GMT

Recently I had an occasion to use the MigrationUMCustomPrompt.ps1 script that ships with EUM 2010 SP1. This script is tremendous as it requires no interaction or variables to be set. It took less than 5 minutes to migrate over 70 custom UM prompts from EUM 2007 SP2 to EUM 2010 SP1. This script is only supported when migrating to EUM 2010 SP1.

Move custom Auto Attendant prompts (EUM 2010 SP1)

Use the MigrateUMCustomPrompts.ps1 script to migrate a copy of all custom prompts for UM dial plans and auto attendants

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "UM prompts" entry in the Unified Messaging Permissions topic.

Click Start > All Programs > Microsoft Exchange Server 2010 > Exchange Management Shell.
In the Shell, at the prompt, type the path to the script. For example, type cd "D:\Program Files\Microsoft\Exchange Server\V14\Scripts", and then press Enter.
At the Shell prompt type ".\MigrateUMCustomPrompt, and then press Enter.

For more information about syntax and parameters, see Import-UMPrompt.

Calling an Auto Attendant associated with an OCS dial plan for a non OCS enabled user goes directly to voice mail

Wes Glockzin — Wed, 03 Nov 2010 15:34:22 GMT

I recently worked an issue where there were two dial plans defined in Exchange Unified Messaging, one for the Telephone (PBX) and the other for Office Communications Server (OCS). When a call was made to the Auto Attendant associated with the PBX Dial Plan and dial by name feature was used for a non OCS enabled user, the call was routed to the users phone device and if the user failed to answer, the call was ultimately routed to voice mail. If the user was enabled for OCS it failed to route the call. This is expected behavior as the Gateway is unable to interpret a users SIP URI. On the flipside, when a call was made to the Auto Attendant that was associated with the OCS Dial Plan and the dial by name feature was used for a OCS enabled user it would successfully route the call to the users phone device and if the user failed to answer, the call was ultimately routed to voice mail. However, if the user was a non OCS enabled user the call would be directly routed to voice mail with option to call the users phone device. The goal was to use a single Auto Attendant associated with a OCS Dial Plan as users were slowly migrated to Enterprise Voice. Below is what we did to get it working.

Symptoms

When a call is placed to the Auto Attendant associated with a OCS Dial Plan from either an internal or external user and dial by name is used for users that are not OCS enabled but have E164 numbers defined in Active Directory, the call is routed to voice mail with no option to call the end user.

Cause

UM:
- Both the OCS Dial Plan and Auto Attendant were configured with a default setting of only allowing caller to contact users within the dial plan
- No defined Dial Rule Groups
- No defined Dial Restrictions associated with any Dial Rule Groups
OCS:
- No route defined to allow E164 dialing

Resolution

UM:
- Allow caller to contact Anyone in the default GAL
- Dial Rule Group created and defined to allow ALL
- Allow ALL Dial Rule Group associated with Dial Restrictions
OCS:
- Created a route that allowed for E164 dialing

Migration and Co-existence with Exchange UM 2007 and Exchange UM 2010

Wes Glockzin — Fri, 29 Oct 2010 15:41:13 GMT

There are four main parts when planning either a migration from EUM 2007 to EUM 2010 and/or having a co-existence in place.

Associate Exchange UM 2010 with existing/legacy Exchange UM 2007 Dial Plan

Associate IP Gateway to Exchange UM 2010

Upgrade Dial Plan, IP Gateway, Mailbox Policies and Auto Attendants

Move custom Auto Attendant prompts

Associate Exchange UM 2010 with existing/legacy Exchange UM 2007 Dial Plan

Launch Exchange Management Console 2010
Expand Server Configuration
Click Unified Messaging and right click on the EUM 2010 server and choose properties
UM Settings Tab
Add existing 2007 Dial Plan

Associate IP Gateway to Exchange UM 2010

# Exchange UM 2010 will now take incoming calls from the IP gateway and differ all requests for Exchange UM 2007 users back to the IP Gateway
Replace the existing settings on the IP Gateway with the new Exchange UM 2010 FQDN/IP

# When Exchange UM 2010 differs calls to the Gateway it will be in a FQDN syntax and the IP Gateway will need to resolve that back to the Exchange UM 2007 server
Configure the IP Gateway to resolve DNS if co-existing with Exchange UM 2007

Upgrade Dial Plan, IP Gateway, Mailbox Policies and Auto Attendants

Open Exchange Management Shell 2010

# Upgrades existing UM Dial Plan to 2010
set-umdialplan -identity

# Upgrades existing UM IP Gateways to 2010
set-umipgateway -indentity

# Upgrades existing UM Mailbox Policy to 2010
set-ummailboxpolicy -indentity

# Upgrades existing UM Auto Attendants
set-umautoattendant -identity

Move custom Auto Attendant prompts (EUM 2010 RTM)

# This sets the variable for the path of where the .wav root directory is
[byte[]]$c = Get-content -Path "c:\" -Encoding Byte -ReadCount 0

# The actual command to import a .wav file to particular UM Auto Attendant
Import-UMPrompt -UMAutoAttendant " " -PromptFileName ".wav" -PromptFileData $c

Move custom Auto Attendant prompts (EUM 2010 SP1)

Use the MigrateUMCustomPrompts.ps1 script to migrate a copy of all custom prompts for UM dial plans and auto attendants

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "UM prompts" entry in the Unified Messaging Permissions topic.

Click Start > All Programs > Microsoft Exchange Server 2010 > Exchange Management Shell.
In the Shell, at the prompt, type the path to the script. For example, type cd "D:\Program Files\Microsoft\Exchange Server\V14\Scripts", and then press Enter.
At the Shell prompt type ".\MigrateUMCustomPrompt, and then press Enter.

For more information about syntax and parameters, see Import-UMPrompt.

When we dial the subscriber access number we get a message "Sorry the person you are trying to reach does not have a valid mailbox on our system."

Wes Glockzin — Tue, 26 Oct 2010 11:06:35 GMT

I recently worked an issue where the Dialogic DMG 1008 Media Gateway would send diversion to the Exchange UM 2010 SP1 server and the net result was when we dialed the subscriber access number, we were presented with a message of, "Sorry the person you are trying to reach does not have a valid mailbox on our system".

1550 = John Doe extension
4200 = SA extension

The snip below shows a diversion header of “tel:4200” from the gateway to the UM server. The UM server needs a diversion header with the users extension. There is not a mailbox setup in UM for the SA and thus the error you get trying to leave a voice mail. The current workaround is to configure the gateway to not send a diversion header. This is a known issue and has not been addressed in SP1.

| | | 172.16.50.27 |
0 |5.795 | INVITE SDP ( g711U g711A telephone-event CN) |SIP From: "JOHN DOE"

INVITE sip:4200@172.16.50.27;user=phone;transport=tcp SIP/2.0\\r\\n
From:\"JOHN DOE\";vnd.pimg.port=4;tag=6F533246313536410042A5DB\\r\\n
To:\\r\\n
Contact:\\r\\n
Diversion: ;reason=unconditional\\r\\n

Dialogic gateways provide some basic methods to manipulate CPID information by creating inbound TDM rules which manipulate the CPID information on the TDM side before it is converted to SIP and forwarded to UM. In the example below, we were able to set up an inbound TDM rule on the Dialogic gateway to strip away the redirecting party info if it matches 4200. This results in a regular SIP INVITE without a diversion header.

Exchange 2010 Unified Messaging SP1, UM rejects incoming call from gateway

Wes Glockzin — Tue, 07 Sep 2010 09:03:32 GMT

In Exchange 2010 UM SP1 we have changed our platform to UCMA. We are now doing more checks on incoming SIP requests to make sure it is compliant and to avoid any undesirable effects. As a result, an invalid end quote will cause a request to be denied by UM. This is a by design feature of SP1. The offending gateway will need to address the issue. In the below example, the gateway is adding the same diversion header twice, which does not seem necessary. Secondly, the diversion header format for display name is incorrect, it has a double end quote.

Symptoms

Event Error that is generated on Exchange 2010 UM SP1 server:
Event ID: 1021
The Unified Messaging server rejected an incoming call with the ID 82e08200-c7d109fd-f6246-1602010a@xxx.xxx.xxx.xxx. Reason: "Invalid Route header: mismatched character: expected: "", found: "EOF""

Cause

Diversion header value ends with two quotes, this is causing a parsing exception in the UM server.
Diversion: " Jane" ";privacy=off;reason=no-answer;screen=yes

Below is the actual SIP packet for the TCP stream of the VoIP call.
INVITE sip:23000@xxx.xxx.xxx.xxx:5065;transport=Tcp SIP/2.0
Date: xxx
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
From: "Doe, John" ;tag=1bc617fd-90a9-46cc-b09d-b00756bde849-61466154
Allow-Events: presence
P-Asserted-Identity: "Doe, John"
Supported: timer,resource-priority,replaces
Min-SE: 1800
Diversion: "Doe, Jane";privacy=off;reason=no-answer;screen=yes
Diversion: " Jane" ";privacy=off;reason=no-answer;screen=yes
Remote-Party-ID: "Doe, John" ;party=calling;screen=yes;privacy=off
Content-Length: 206
User-Agent: Cisco-CUCM7.0
To:
Contact:
Expires: 180
Content-Type: application/sdp
Call-ID: 73286400-c7d14b51-f6751-1602010a@xxx.xxx.xxx.xxx
Via: SIP/2.0/TCP xxx.xxx.xxx.xxx:5060;branch=z9hG4bK1419d12da18370
CSeq: 102 INVITE
Session-Expires: 1800
Max-Forwards: 70

Graph Analysis of VoIP call:

|Time | 00.0.0.00                             |
|         |                   | 00.0.00.00        |
|25.174   |         INVITE SDP ( g711U telephone-event)          |SIP From: "Doe, John" |         |(34715) ------------------> (5060)   |
|25.175   |         100 Trying|                   |SIP Status
|         |(34715) <------------------ (5060)   |
|25.215   |         302 Moved Temporarily          |SIP Status
|         |(34715) <------------------ (5060)   |
|25.217   |         ACK       |                   |SIP Request
|         |(34715) ------------------> (5060)   |
|25.218   |         INVITE SDP ( g711U telephone-event)          |SIP From: "Doe, John" |         |(34716) ------------------> (5065)   |
|25.219   |         100 Trying|                   |SIP Status
|         |(34716) <------------------ (5065)   |
|25.259   |         403 Forbidden                 |SIP Status
|         |(34716) <------------------ (5065)   |
|25.261   |         ACK       |                   |SIP Request
|         |(34716) ------------------> (5065)   |

Resolution

This is a by design feature of SP1 and the gateway (Cisco-CUCM7.0) vendor needs to address the issue.

OCS 2007 R2 Enterprise and Brocade/Foundry Load Balancers

Wes Glockzin — Fri, 03 Sep 2010 10:55:49 GMT

I worked a support case recently that involved an OCS 2007 R2 Enterprise deployment with two Front Ends and a two Edge array, load balanced by Brocade/Foundry Load Balancer. Example of the working configuration follows.

Basically, the internal facing edge VIP cannot have keepalives. The external facing edge VIP has to have keepalives extended (not the default 5sec, 5 retries.). The firewall also had limits set for failed attempts that were very restrictive and it also had snooper checks on the load balancer that kept putting the servers in failed state. We removed the snooper checks and increased the limits.

Actual customer IPs’ and FQDN’s have been changed.

INTERNAL FACING EDGE VIP

server real edge001

port ssl

port ssl no-health-check

port 3478

port 3478 no-health-check

port sips

port sips no-health-check

port 5062

port 5062 no-health-check

server real edge002

port ssl

port ssl no-health-check

port 3478

port 3478 no-health-check

port sips

port sips no-health-check

port 5062

port 5062 no-health-check

server virtual OcsEdge.xxx.com

tcp-age 30

sym-priority 4

predictor round-robin

port ssl sticky

port 3478 sticky

port sips sticky

port 5062 sticky

track-group sips 5062

bind ssl EDGE001-int ssl

bind 3478 EDGE001-int 3478

bind sips EDGE001-int sips

bind 5062 EDGE001-int 5062

bind ssl EDGE002-int ssl

bind 3478 EDGE002-int 3478

bind sips EDGE002-int sips

bind 5062 EDGE002-int 5062

EXTERNAL FACING EDGE VIP

server port 443

session-sync

tcp

tcp keepalive 30 3

server port 5061
session-sync
tcp
tcp keepalive 30 3

Real Server Config on Foundry:

server real EDGE002-ext-01 xxx.xxx.xxx.xxx
port ssl
port ssl keepalive
port sips
port sips keepalive

Vip config on Foundry:

server virtual sip.xxx.com xxx.xxx.xxx.xxx
tcp-age 30
sym-priority 4
predictor least-conn
port ssl sticky
port sips sticky
track-group ssl 5061
bind ssl EDGE002-ext-01 ssl
bind sips EDGE 002-ext-01 sips

bind ssl EDGE 001-ext-01 ssl
bind sips EDGE 001-ext-01 sips

other settings in the dmz

Firewall settings:

No snooper checks on the ports used in the load balancer. This was causing the server to fail and not come online with the lb.

Limits to failed attempted connections increased. We were reaching the limits for failed connections.

Live Meeting MSI (LMSETUP.msi / LMSETUP.exe) Install fails with "Turn Off Application Compatibility Engine" is set to Enabled on Windows 7 32bit

Wes Glockzin — Mon, 02 Aug 2010 14:08:37 GMT

The Live Meeting Console installation will fail when the Local Security Policy and/or Group Policy Key, “Turn Off Application Compatibility Engine” is set to Enabled. When installing drivers in the 32bit version for Live Meeting Console (which is not the case in the 64bit version, and thus no MODI drivers on 64bit) we use the “Windows Shim Infrastructure”. If you disable the shim engine with the group policy you disable this functionality.

If you disable the group policy you can see that the driver installer framework was able to continue as designed:

MSI (s) (FC:00) [15:02:44:872]: Doing action: MsiProcessDrivers

Action 15:02:44: MsiProcessDrivers.

Action start 15:02:44: MsiProcessDrivers.

MSI (s) (FC:00) [15:02:44:872]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'MsiProcessDrivers'

MSI (s) (FC:60) [15:02:44:919]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI61DD.tmp, Entrypoint: ProcessDriverPackages

DIFXAPP: 'Component' is 'COMP_RTYuv.dll'

DIFXAPP: Component state 0x2 -> 0xFFFFFFFF

DIFXAPP: 'ComponentId' is {8CEA3E98-7894-4EFC-A6CA-978A783819E8}

DIFXAPP: 'Flags' is 2

DIFXAPP: component path is

MSI (s) (FC!78) [15:02:45:044]: PROPERTY CHANGE: Adding NoOp_{8CEA3E98-7894-4EFC-A6CA-978A783819E8} property. Its value is 'TRUE'.

DIFXAPP: INFO - This is a no-op custom action for component COMP_RTYuv.dll. The NoOp_{8CEA3E98-7894-4EFC-A6CA-978A783819E8} property has been set to TRUE.

Action ended 15:02:45: MsiProcessDrivers. Return value 1.

The Application Compatibility Engine needs to be turned on to install this application on 32bit Windows 7.