OCS & CCM

Last week, I was in a multinational   IT company to deploy OCS 2007 R2 server (Office Communication Server 2007 R2). This company wanted to use OCS service to decrease cost and to use OCS features which will help company’s needs and employee’s connections.

They decided to implement OCS 2007 R2 Standard Edition because they will test OCS features in a narrow scope or with a few number of company’s Employees and they wanted to implement the mediation server. But the company depends on Cisco Call Manager server as an IP telephone system and they wanted to make a migration between OCS & CCM to enable users to send & receive calls using their phones devices without needing OCS handsets.

So, as OCS implementers, I was in need to migrate OCS with CCM. I was in need to SIP trunk (Session Initiation Protocol) to enabling this migration process.

Now, I can say with a lot of confidence that the most critical step in this OCS implementation case was the migration process between OCS & CCM via this SIP trunk because we must be in sure that this trunk  really initiated correctly and we must keep in mind that if the migration process is failed, we will be in () case. Why?

We will think in two ways, the first that is the failure belongs to mediation server configuration? The second is the failure belongs to SIP trunk configuration in CCM Server?  So, we should keep in minds that we have to take care in initiation SIP trunk.

For more details, Kindly find below our documentation for creating SIP trunk in CCM Console.SIP Trunk01

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: