Mino – The UC Guy

Microsoft Unified Communications Blog

Posts Tagged ‘OCS 2007 R2’

OCS Response Group Service failed to start with Error event ID 31193

Posted by Mino on October 14, 2009

We have OCS 2007 R2 Pool with 2 front end servers enterprise edition, let us say that the FQDN of the servers are OCSFE01.contoso.com, OCSFE02.contoso.com and the Pool name is OCSPOOL.contoso.com.

I created the certificate request for the front end servers using the OCS wizard where I added the Pool name in the CN and in the SAN also , then I clicked the check box of add local machine name to the SAN certificate.

Then I try to enable the OCS Services and I found that the OCS Response Group Service failed to start with the below error:

Log Name:      Office Communications Server
Source:        OCS Response Group Service
Event ID:      31193
Task Category: (2001)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      OCSFE01.contoso.com
Description:
The provided certificate is not valid.

There was a problem validating certificate: Identity check failed for outgoing message. The expected DNS identity of the remote endpoint was ‘OCSPOOL.contoso.com’ but the remote endpoint provided DNS claim ‘OCSFE01.contoso.com’. If this is a legitimate remote endpoint, you can fix the problem by explicitly specifying DNS identity ‘OCSFE01.contoso.com’ as the Identity property of EndpointAddress when creating channel proxy.

 

How to Resolve:

The problem is in SAN certificate for the frontend servers you need to make sure that the last DNS entry in the SAN list matches the certificate subject name, which should be your pool name.

And since I clicked the checkbox of add local machine name to the SAN , so it added the FQDN of the machine as the last entry in the SAN and this was the problem.

So make sure that the CN should be the pool name ocspool.contoso.com and the last name in the SAN should also be pool name ocspool.contoso.com

 

Update : this is a known issue that  has been fixed with Hotfix in KB 969695

Advertisements

Posted in Certificates, Common Errors, Front End Server, OCS 2007 R2 | Tagged: , , , , , , | Leave a Comment »

PreCallDiagnostic Tool

Posted by Mino on September 21, 2009

The PreCallDiagTool is an application that reports expected audio quality as it relates to the network effect. The tool should be installed on any desktop or laptop PC that suffers from inconsistent network connection quality. The PreCallDiagTool can provide a quick check of the current network conditions and also preserve a history of quality data to let users profile their network performance over time or other conditions. The tool is particularly useful for home/mobile users and users using WIFI access points.

The tool is available for download here: http://www.microsoft.com/downloads/details.aspx?FamilyID=f16ab4c2-353f-4c9b-b353-22a656c03c9b

Monitor

Posted in communicator client, Mediation Server, Miscellaneous, OCS 2007 R2, OCS Tools Kit, Phone Edition | Tagged: , , , , , , | Leave a Comment »

OCS R2 Updates about the Firewall Requirements for External User Access

Posted by Mino on February 25, 2009

One of the main topics that has been giving me hard times when communicating with a firewall System Admin would be why would the OCS AV Edge Server need a Publicely routable IP , and how secure it is to open 10,000 ports  ( 50,000 – 59,999 ) TCP/UDP ?

usually we used to get Microsoft articles and explain more about the STUN protocol and why It cant work behind NAT and then how to secure the Edge .

But now with the R2 I have good good news for the Firewall Admin team  :

1- If you are implementing a Single Consolidated Edge Server then you can work with NAT IP rather than the publicely routable real IP which was required before . Only Only if this is a Single consolidated Edge

2- the 50,000 – 59,999 UDP/TCP ports which are required to be open , are only required if you are planning to have fedration with other orginizations . if there is no fedration in your plan then no need to open these ports .

I hope you are happy now Firewall Admin team  J

Firewall Requirements for External User Access

 

 Publicly Routable IP Address

In any location with multiple Edge Servers deployed behind a load balancer, the external firewall cannot function as a network address translation (NAT). However, in a site with only a single Edge Server deployed, the external firewall can be configured as a NAT.

If you do so, configure the NAT as a destination network address translation (DNAT) for inbound traffic—in other words, configure any firewall filter used for traffic from the Internet to the Edge Server with DNAT, and configure any firewall filter for traffic going from the Edge Server to the Internet (outbound traffic) as a source network address translation (SNAT). The inbound and outbound filters must map to the same public IP address and the same private IP address, as shown in the figure below.

The A/V Edge Service requires the port range from 50,000 through 59,999 to be open only for the sharing of audio/video with federated organizations.

  • If you will be federating with organizations that run Office Communications Server 2007 and earlier, you must open this port range for both RTP/TCP and RTP/UDP, and for both inbound and outbound connections.
  • If you will be federating only with organizations that run Office Communications Server 2007 R2, you need only to open this port range for RTP/TCP, only for outbound connections.
  • Otherwise, if you will not be sharing audio/video over a federated relationship, you can close this port range.

  dd441361_6b3a5ede-4253-4874-b096-2e969bf52626en-usoffice_131

Source : http://technet.microsoft.com/en-us/library/dd441361(office.13).aspx

Posted in A/V Edge Server, Common Errors, Consolidated Edge, Edge Server, Miscellaneous, OCS 2007 R2 | Tagged: , , , , , , , , , , | 1 Comment »

Plantronics Strengthens Unified Communications Portfolio With Its First Phone Handset Optimized for Microsoft Office Communicator 2007

Posted by Mino on February 5, 2009

New Wideband Handset Eases Unified Communications Adoption by Providing a Familiar Option to Professionals

tn-501514_audio1100m_jpeg

.Audio 1100M USB Handset Optimized for Microsoft Office Communicator

SANTA CRUZ, CA–(Marketwire – February 3, 2009) – Plantronics, Inc. (NYSE: PLT) today expanded its growing portfolio of Unified Communication products Optimized for Microsoft Office Communicator with the new wideband .Audio™ 1100M USB phone handset. Plantronics’ unified communication product portfolio also includes corded and wireless headsets, giving IT purchasers a broad selection of PC audio products as they deploy Microsoft Office Communicator 2007.

The Plantronics .Audio 1100M USB phone handset is optimized for Office Communicator 2007 to provide the functionality of a familiar phone interface for business users adopting PC telephony. The .Audio 1100M features a standard, 10-key dial pad combined with call-answer and call-end keys, a visual ring indicator, a speakerphone activation key and ringer volume control. A headset jack is also available on the handset for users who want a hands-free option.

The Plantronics MCD 100 USB speakerphone, also announced today, is an option for those conducting group conference calls via Office Communicator 2007. It provides 360-degree room coverage so more than one person can participate in a PC-based audio conference. To achieve call clarity, the MCD 100 includes acoustic echo cancellation, noise suppression and equalizer algorithms embedded within the product.

 Pricing and Availability

All Optimized for Microsoft Office Communicator Plantronics products are now available and may be purchased through authorized Plantronics resellers. The .Audio 1100M, a USB phone handset, has an MSRP of $79.00. The MCD 100, a USB speakerphone, has an MSRP of $179.00. Announced in September 2008, the .Audio 630M, a multi-purpose binaural headset featuring stereo, has an MSRP of $49.95. The .Audio 615M, a monaural headset, has an MSRP of $44.95. The SupraPlus Wideband USB monaural noise canceling headset has a MSRP of $169.00.

Posted in Miscellaneous, Phone Edition | Tagged: , , , | Leave a Comment »

Communicator 2007 R2 Custom Tabs Custom Tab not showing up

Posted by Mino on February 5, 2009

Issue: Custom Tab not showing up
OCS Platform: OCS 2007 R2 Standard running on Windows 2008
OS/Client Running Windows Vista x32 with MOC 2007 R2.
Application: Response Group app.. Configured my MOC user as a a formal
agent

 

as per the Microsoft R2 guide for the Custom tabs I Created local tab.xml file and configured registry to point to it per
MS documentation:

Registry key :   TabURL REG_SZ file:///c:\Tabs.xml.

 

and the XML file was like the below 

<?xml version=”1.0″?>
<tabdata>
<tab>
<image>https://ocsfe.linkdev.com/rgs/clients/RgsOcTab.png</image>
<userid>true</userid>
<name>Response Group Tab</name>
<tooltip>Response Group Tab</tooltip>

<Contenturl>https://ocsfe.linkdev.com/rgs/clients/Tab.aspx</contenturl>
<contactid>true</contactid>
<accessibility>both</accessibility>
<siteid>1</siteid>
</tab>
</tabdata>

I am able to browse to both the PNG and tab.aspx using I.E without
prompts or warnings. Has anyone run across this?

 

 

The Problem was simply with the below line :
<contactid>false</contactid>

 

In the original Microsoft guide it is mentioned to write <contactid>true</contactid> in the XML file , simply change it to false and it will work fine.

Posted in communicator client, OCS 2007 R2 | Tagged: , , , | 7 Comments »

Microsoft UC Virtual Technology Solutions Professional ( TSP )

Posted by Mino on February 4, 2009

CONGRATULATIONS

Today We have Passed Microsoft assessment and Became officially UC Voice Partner  to be listed on Microsoft website http://www.microsoft.com/uc/partners/voice.mspx

Yes Officially on Microsoft UC Page along with Nortel , Siemens ,Gold System and other Big Boys

We are also officially now part of highest UC technical program, Microsoft Technical Adoption Program (TAP).

More Info here: http://msdn.microsoft.com/en-us/isv/bb190413.aspx

Also our team has been selected by name from Microsoft MEA to become some of few virtual resources within the Microsoft Virtual Technology Solutions Professional (TSP), to deliver on the same level of quality on critical workloads within the MEA region.

Special thanks for Katherine Green and Keith Hanna from Microsoft for their time and support

Let Everyone Know …They are playing with the Big Boys now

Posted in Miscellaneous | Tagged: , , , , , | 1 Comment »

OCS 2007 R2 Response Group Service

Posted by Mino on February 4, 2009

Below are some snapshots from our LAB to represent how the response group service will look like from the agent side.

I have configured a group with memebers , also i have configured a call workflow to ask whether for English language or arabic language .

In the below snapshot , both fady and Rami are two help desk agents who are logged in . when the call comes both parties recieve the call.

rg11

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

when Rami answers the call , it gives him information about the call flow that the client used in order to get connected to him . on the other hand Fady recieves a confirmation that Rami has answered the call .

rg31

Posted in OCS 2007 R2 | Tagged: , , , , , , , | 6 Comments »

OCS Integration with AVAYA ( 1 of 2 )

Posted by Mino on February 1, 2009

Hi all,

As i have promissed you that I will be back with lots of great information regarding the AVAYA integration.

here we go , i was working with a huge client in Dubai where he has just purchased an AVAYA IP-PBX along with Sip Enablement Server ( SES ) and AVAYA Application Enablement Server ( AES ) .

ok first of all lets us all memorize these two terms , AVAYA SES and AVAYA AES because we will be talking about them both allot.

There are two stories for the AVAYA-Microsoft integration , the AVAYA story and the Microsoft story. we will talk about both stories and the integration idea from each vendor , the limititions from each way of integration along with the pros and cons.

Microsoft Story :

For Microsoft the integration with AVAYA is simply by dealing with them as two separate IP-PBX where Microsoft has an extensions of 3xxx for example and AVAYA with extensions of 7xxx .where you need to create a SIP trunk between both of them to be able to call from here to there and vise verse.

This assures microsoft that the call processing will happen in the Mediation server , which is the target of Microsoft in order to help its users to move to the Microsoft IP PBX concept bit by bit.

for this type of integration you will need AVAYA SIP enablement server only which shall give the AVAYA communication manager the SIP capability to communicate with other system , in this SES we will configure a sip trunk for the 3xxx extensions to route to the mediation Server over TCP-IP port 5060 or through TLS over 5061 after you configure the certificate on the SES Server.

below is a diagram for this type of integration .

avaya-direct-sip

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Good Thing :

1- AVAYA SES is not costy at all  , 2-Full featured OCS capabilities including conferencing,  3- you can do dual forking workarround by adding AVAYA extensions as the similtaniously ring another number in OCS

Bad thing:

no dual forking between AVAYA and OCS which means that each person will have two extensions .

in my oppenion , no Big deal …the client was so happy with this scenario because the second AVAYA scenario will cost him 60$ per users license plus it will not provide him with all capabilities of OCS ( the conferencing for example is dimmed )

in the Second article we will discuss the second way of integration through the AVAYA AES Server

Posted in AVAYA | Tagged: , , , , , , | 2 Comments »

The Speech Server Scoop on OCS 2007 R2

Posted by Mino on October 15, 2008

The GotSpeach Guy Wrote on his Blog

Ok the word is getting out now about Office Communications Server 2007 R2 so I thought I would give you some details on how this will affect Speech Server developers.

First let me say that there are no changes for Speech Server in OCS R2. It will still be a separate install and the bits will be the same. You will still use Visual Studio 2005 and all of the development tools are the same.

Now for the cool news about the R2 release.

R2 will include the new UC Managed API 2.0. The API shows the new approach for developing Speech Applications going forward: speech technology will be an integrated developer capability in the whole of the UC platform. The UCMA 2.0 API does consist of 3 API major pieces – Core (including a SIP signaling stack and a media stack), a managed server Speech API and UC Workflow Activities that are built on top of both the core and server speech managed APIs. All together make the one UC Managed API 2.0.

The UCMA 2.0 Server Speech SDK will support 12 languages with both ASR and TTS: US English, Canadian French, Mexican Spanish, Brazilian Portuguese, UK English, German German, French French, Italian, Japanese, Mandarin (simplified/mainland plus traditional Taiwanese), Korean.

And get this – it will support Visual Studio 2008! Actually the UC Workflow Activities support both activities for speech as well as for IM automated agents (a.k.a. bots).

More info –

  1. You can develop Speech Server (2007) applications just like you have in the past (using VS 2005)
  2. You can now develop speech “bots” using the new Workflow Activities on top of the UCMA 2.0, or in managed code only using the Core and Speech APIs, if you are really hard core.
  3. The UCMA Speech SDK will be missing some of the tools that you are currently used to having. For example there is no grammar tool but SRGS grammars are still supported and you can use the existing Grammar Editor (in VS2005) to create grammars, or use your favorite XML editor.
  4. Conversational grammars may or may not work due to changes in the way the engine works.
  5. OCS 2007 R2 has no VXML support on top of UCMA 2.0. This might change for the future ’14’ release. SALT definitely is dropped from the roadmap.
  6. The UCMA is much closer to SIP but will still be familiar to you. It will be able to manipulate the SIP stack and the media stack as well.
  7. In the next ’14’ release (the one after R2) Speech Server will no longer be a standalone install but will be an integral part of OCS.

You are probably wondering how you can get your hands on Office Communicator 2007 R2?
The official Launch Date will be early February. Till then there only is a very small private beta.

There however is a Developer program called Metro (http://www.discovermetro.net) for managed Microsoft accounts.

Managed ISVs and Corporate developers just need to get in touch with your Microsoft (Partner) Account Manager asking if you can be admitted to this Metro program. The Metro program gives access to Hyper-V images of a complete developer OCS 2007 R2 setup, including speech, training across the world in the complete platform, and a (email only) help desk, in exchange for a commitment to build applications on the UC (OCS 2007 R2 and Exchange) platform.

I am really excited about this as it will allow us Speech Server developers better access to the core OCS components and will give us a new way to develop speech applications. For now the best approach will probably be to keep developing the way you have in the past and start experimenting with the new stuff before settling on it for all of your development. Or at least that is the approach I plan on using.

Gold Systems (the company I work for) has OCS R2 up and running in production and we are very excited about the new release

I’ll blog more on the UCMA later.

Posted in Miscellaneous | Tagged: , , , , , , , , | 2 Comments »