Avaya 4.0 is now Certified for SIP direct.

Avaya 4.0 is now Certified for SIP direct.

You could use direct SIP connection for a POC and then rip and replace :)

Get more information here

IP-PBX Vendor
Tested Product
Supported Configuration
Software Versions Tested
2007 R2
2007

Avaya
Communications Manager SIP Enablement Services
Direct SIP
4.0

Known Limitations:

• Configuration requires setting "Alternate Route Timer(sec)" value from default of 10 sec to 30 sec. The configuration should show "Alternate Route Timer(sec): 30" in the corresponding SIP signaling group.
• When an call is ringing to the Office Communicator user, the caller (either on an Avaya station or a PSTN line routed through the PBX) will not get ring back tone. This issue has been resolved by Avaya with the 5.x software releases.
• Quality of Experience reports will not contain information regarding jitter and packet loss.
• Comfort noise generation is not supported. As a result, comfort noise is not played on Office Communicator.
• ISDN Failover is not supported from an OCS perspective. If the Avaya PBX is being used for PSTN connectivity and multiple T1's are being utilized, an OC client will not retry a call based on a T1 being unavailable. It may be possible to configure the Avaya to not assign outbound calls from OCS to an unavailable T1, but this configuration was not tested.

AudioCodes livemeeting on roadmap for OCS W14

I was attending a Livemeeting today with Audiocodes.

On the agenda was Audiocodes roadmap for OCS W14.

There is some great and interesting news, and if you like to know what Audiocodes will do in OCS w14 timeframe go to this like for the recordings.

And also look at Msgoodies blog on this subject!

Microsoft Office Communications Server 2007 R2 Planning workbook (released)

Microsoft Office Communications Server 2007 R2 Planning Workbook can you now get here: http://communicationsserverteam.com/files/9/ocs_2007_r2_planning_workbook/entry346.aspx

This Planning Workbook is intended to document the recommended roll-out of Microsoft® Office Communications Server 2007 R2 in an enterprise-level lab or production environment. This document’s purpose is to provide enterprise customers and deployment partners a method to begin planning for their Office Communications Server 2007 R2 deployment. This document does not replace communications with Microsoft Consulting Services or a Microsoft UC deployment partner. This is a living document that will be continually updated throughout the product lifecycle.

Direct SIP to Cisco Unified Communications Manager 7.0(1) Simultaneous Ring Feature

Microsoft Office Communications Server 2007
Enterprise Edition using Direct SIP to Cisco Unified
Communications Manager 7.0(1) Simultaneous Ring
Feature.

Here is the guideline how to: http://www.cisco.com/en/US/solutions/collateral/ns340/ns414/ns728/ns784/716742.pdf

I don't think that Dual forking (Simultaneous ring) is a good solution, because you don't get "in a call" status in Communicator when using the phone, only when using the Communicator as endpoint you change status to "in a call".

If you use Dual forking and Remote Call Control you will have "in a call" status even when you are using the phone. it's only Nortel that supports Dual forking and Remote Call Control right now.

If you need to understand all the different way to connect to your phone system, please look at Jochen Kunert's blog: http://blogs.technet.com/jkunert/archive/2008/07/30/voice-scenarios-with-ocs-2007.aspx

Here is the Supported IP-PBXs for Microsoft Office Communications Server 2007 link :http://technet.microsoft.com/en-us/office/bb735838.aspx#ippbx2