OCS 2007 as main call manager

I always has this in my mind using only OCS as the call manager (without using any PBX system). This question has makes me to setup a lab with OCS 2007 Front-end server and Mediation server and a simple media gateway. In the lab I've tested the with 2 types of incoming lines (PRI and normal PSTN lines). I would said anyone can try out this setup via normal PSTN line.

In the lab I can see the difference of using the 2 types of media gateway. Using PRI would be more direct and simple configuration on the media gateway (as media gateway guide has it all). But when using PSTN line media gateway (i guest is lower end), there are more configure step required on the media gateway.

Using the lower end media gateway there are some featues likes call ID (caller phone no.) was not able to pass over to OCS. I've checked with some media gateway expert, it seem the information (Caller ID information) would not pass over due to the limitation of the devices. I still exploring the possibility of using the lower end unit to have the same features as the PRI line.

Problem with user not able to login via CWA

For those who encounter this error during logging from CWA "Cannot sign in due to a server error. Please try again. If the problem persists, contact your system administrator."

This problem might be related to the CWAService account password expire. In the default configuration after your installation the CWAService account don't have the "Password Never Expire" option checked. You will need to set the password for the CWAService to never expire. Once this is configure, you will be able to login to CWA again

How to integrate OCS 2007 with Cisco Call Manager 4.x?

It is easier to integrate with Cisco Call Manager 5.x and above version as CCM support SIP trunk to OCS 2007 server or via IP-IP gateway (router). I'm not sure Microsoft has release any supported documment on CCM integration with OCS 2007 or not. But I've tested the integration in a production environment.

For my this implementation; I've use Dialogic media gateway 2000 series (DMG2030). In a standard CCM 4.x environment, there will be a voice router which will be the interface with the service provider. The connections between router and CCM/media gateway will be using E1 link.

There will be some configuration need to be done at CCM as to route the inter-call between OCS client and cisco phone client.

OCS 2007 with Panasonic PBX TDA100

How simple is it for Panasonic PBX to move to IP base telephony platform via Microsoft OCS. We've successfully implemented Microsoft OCS 2007 with integration with Panasonic PBX model TDA100.

The situation is we've a requirement from the customer to remain the single line phone and its fax mahine as it is. Others user will be using the new OCS to makes voice call.

PBX information as followed:

Model: Panasonic TDA100 version 007-001

Region: 009-009

MPR (ML) card: 3.2002

PRI card: PRI30 version 2.009

The PBX is using two PRI (ISDN card), for incoming source from service provider and the second PRI card for connection to media gateway. The PRI card has to be enable QSIG signalling to communicate with the media gateway (as media gateway will require min. QSIG signalling). With this, the normal fax machine will still able to be connected to the PBX system.

During the implementation, the two connections (service provider and to media gateway) are require to use coaxial cable (with BNC connector as standard). Due to media gateway are having RJ45 connection only, we uses balun which conver the coaxial (BNC 75ohm) to RJ45 connection (RJ45 120ohm).

PBX is configured as slave as accepting the source from service provider and media gateway would need to be configured as master.

Dialogic Media Gateway connects IP system to PSTN at Siemens Subsidary

Unified Messaging continues moves in Europe and Dialogic has made it in one of another UM success recently. HEC GmbH, a consulting subsadary of Siemens improving their efficiency of its client communications by moving to UM. Initially the company concerned about the need to connect its IP infrastructure to PSTN, but its parent company (acting as system integrator) advised using media gateway from Dialogic (Media Gateway 3000 series). The connection was made quickly and easily.

Andreas Essing, (Director of the Microsoft Infrastructure Consulting Business at Siemens IT solutions and Services, Siemens AG) who help with the implemnetation and installation commented that "working with dialogic impressed us in terms of its high-grade product and excellent support during each phase of the project. we are already looking forward to being able to build on this positive experience in the future".

For more details, read the case study.

Microsoft - Aspect in Contact Center

Last week, Microsoft has announced a multiyear global strategic alliance with Aspect Software to bring Unified Communications and Software Powered Voice to contact center sector. Understanding on the announcement; Aspect will integrate its.NET-based contact center suite (Aspect Unified IP) with Office Communication Server. This will certainly useful to both new and existing Aspect customers. In the announcement there is a missing component which addressing Microsoft’s Contact Center strategy via Unified Communication.

We still have not heard Microsoft will offer in terms of a contact center solution as a part of in conjunctions with its OCS offering. It’s clearly Microsoft recognizes how important it is to have some sort of contact center solution offering for customer that are looking into an Enterprise Unified Communication Voice solution but yet still has not disclosed any sort of contact center strategy to date.

Microsoft has several options clearly working with Nortel, a leader in the contact center space to provide the needs to contact center capabilities is one of the option. While Microsoft made it clear that the investment in aspect does not impact its relationship with Nortel. I’m pretty sure Nortel folks aren’t exited with this news. Another option is to acquiring a company in the contact center market, such as Aspect or possibly Interactive Intelligence. Of course there still some rumors that Microsoft will acquire Siemens Enterprise Communications, Nortel, or any others which if true, would provide Microsoft with the needed contact center capabilities and expertise. These are still rumors and so far no truth to any of them yet.

I believes that there’s a good change that Microsoft will leverage both Nortel and Aspect’s expertise and than offer its own contact center offering, (may be competing with both companies). Regardless what route Microsoft is moving to, it’s important that they articulate iuts contact center strategy for those companies that are looking to OCS as an enterprise voice solution.

Microsoft Office Communicator License Expired

I think some of you might encounter this pop-up error “Microsoft Office Communicator 2007 cannot start. The product license may be expired because you are using a pre-release or evaluation copy of the program, or the product key information may have been modified in your Windows registry. Please run Setup to uninstall and then reinstall Communicator.”

This error means the Microsoft Office Communicator has expire or caused by the package install method. You may require to reinstall with the Office communicator again. Get the CD from your MSFT Select CD pack or from you Microsoft Reseller or you may download from MSDN.

Some deployment applications use transforms with the MSI that have included the ProductID property. This ProductID value is set to "none" in the registry key below. This will then trigger the timer for evaluation. Once the timer expired the message will be received. There is no indication to the program that it is running in evaluation mode.

HKLM\SOFTWARE\Microsoft\Communicator\1.0\Registration\ProductID

There are 3 options to resolve this issue:

Option 1: Repair the MST (transform) by removing the ProductID property. Then delete the ProductID value in the registry and let the MSI self-heal.

Option 2: Re-push Communicator with the corrected transform & product key. This should run a repair and will replace the bad ProductID in the registry.

Option 3: Push an uninstall package; then the corrected installation package for Communicator