You will have a global view of Office Communications Server 2007 R2 traffic flow between component like : IM and Presence, Conferencing, Application Sharing, and Enterprise Voice.
You can see the different server roles, the needs in term of server certificate, and also the firewall and DNS configuration requirements.
Ref :
The Deployment Validation Tool allows you to perform automated testing of calls between agents that are Office Communications Server 2007 R2 clients. It is included with Office Communications Server 2007 R2 Resource Kit Tools, available as a free download at the Microsoft Download Center at :
http://go.microsoft.com/fwlink/?LinkId=145159
You can find the technet page here :
http://technet.microsoft.com/en-us/library/dd572350(office.13).aspx
And watch this video from the Microsoft Technet Chopstick :
iDialog is an OCS 2007 and OCS 2007 R2 compatible client for the Apple iPhone and iPod Touch.
Participate in IM message and Forward incoming OCS Voice Calls
iDialog supports the following features:
http://www.modalitysystems.com/idialog/
What you can do :
Download the BlackBerry Client for use with Microsoft Office Communications Server 2007
http://na.blackberry.com/eng/services/server/exchange/ocs2007.jsp
Java Based Phones (Nokia S40/S60 series and Motorola RAZR v3 Devices)
Microsoft makes a version of Office Communicator Mobile R2 available that is optimized for Java. There are different versions available depending on your phone (listed below). OCS 2007 R2 must be running on the backend.
a) Office Communicator Mobile 2007 R2 for Java (Nokia S60 320X240 resolution)
- Supported Phone Models: E51, E66, N95; Supported Telecom Network: Vodafone and Orange networks in Europe, Airtel and Vodafone networks in India.
b) Office Communicator Mobile 2007 R2 for Java (Nokia S60 240X320 resolution)
- Supported Phone Models: E51, E66, N95; Supported Telecom Network: Vodafone and Orange networks in Europe, Airtel and Vodafone networks in India.
c) Microsoft Office Communicator Mobile 2007 R2 for Java (Nokia S40)
- Supported Telecom Networks: Vodafone and Orange networks in Europe, Airtel and Vodafone networks in India; Â Â Supported Phone Models: Nokia S40 5th edition phones including: 3120 Classic, 3600 Slide, 5220 XpressMusic , 5310 XpressMusic , 5610 XpressMusic, 6212 Classic, 6300i, 6301, 6500 Classic, 6500 Slide, 6600 Fold, 6600 Slide, 7210 Super Nova, 7310 Super Nova, 7510 Super Nova, 7610 Super Nova, 7900 Prism and 8800 Arte
d) Microsoft Office Communicator Mobile 2007 R2 for Java (Motorola Razr V3 U.S.)
- Supported Telecom Network: AT&T (US); Supported Phone Models: Motorola RAZR V3xx
How to make OCS 2007 R2 non-RFC 3966-compliant ?
Office Communications Server 2007 Mediation Server uses a plus sign (+) to prefix E.164 numbers in the Request Uniform Resource Identifier (URI) for outgoing calls. Unfortunately, some IP-PBXs don’t comply with RFC 3966 and do not accept numbers that are prefixed with a plus sign (+).
In OCS 2007 R2 use a new WMI setting, RemovePlusFromRequestURI, which is described in this TechNet article called Enterprise Voice Server-Side Components.
According to the TechNet article, Office Communications Server 2007 R2 introduces two new Windows Management Instrumentation (WMI) settings for Mediation Server. The first new setting specifies how Mediation Server processes E.164 numbers in outbound calls. The second new setting enables Quality of Service (QoS) marking on Mediation Server.
Handling E.164 Numbers in Outbound Calls (OCS 2007 R2)
By default, E.164 numbers in the Request Uniform Resource Identifier (URI) for outgoing calls are prefixed with a plus sign (+). Most Private Branch eXchanges (PBXs) process such numbers without problem. Certain PBXs, however, do not accept numbers that are prefixed with a plus sign.
To ensure interoperability with these PBXs, Mediation Server has a new WMI Boolean setting called RemovePlusFromRequestURI, which has two values: TRUE and FALSE. If your PBX does not accept numbers prefixed with a plus sign, the value for the WMI setting should be set to TRUE, which causes Mediation Server to strip the plus sign from a Request URI for outbound calls. The default is FALSE, which causes Mediation Server to pass the outgoing INVITE’s Request URI, To URI, and From URI unchanged.
The TechNet article also discusses compatibility with PBXs that do not support the plus (+) sign.
By default, E.164 numbers in the Request URI of outgoing calls from Office Communications Server 2007 R2 are prefixed with a plus sign. Most PBXs process such numbers without problem. Some PBXs, however, do not accept numbers that are prefixed with a plus sign and do not route those calls correctly.
Additionally, the From headers of inbound calls from some PBXs does not conform to RFC 3966 because they are not prefixed with a plus sign. Microsoft Office Communicator cannot resolve these numbers to the correct user.
To assure interoperability with these PBXs, Office Communications Server 2007 R2 has a new Mediation Server setting for WMI called RemovePlusFromRequestURI. This setting can be set to YES or NO. The default value is NO.
- If a PBX downstream from the Office Communications Server 2007 R2 Mediation server does not accept numbers prefixed with a plus sign, set the value of RemovePlusFromRequestURI to YES. This causes Mediation Server to remove the plus signs from the Request URIs of outgoing calls. It also causes the plus signs to be removed from the To and From URIs.
- If the downstream PBX accepts numbers prefixed with plus signs, leave the value of RemovePlusFromRequestURI set to its default value of NO. This causes Office Communications Server 2007 Mediation Server to pass Request URIs, To URIs, and From URIs unchanged (that is, with plus signs).
Extract from : http://tmcnet.com
You have to choose between beeing secure or stop working with OCS according to Microsoft !:
Your evaluation period may be expired with this error in event viewver :
Event source: OCS Server
Event id: 12290
Event text: The evaluation period for Microsoft Office Communications Server 2007 R2 has expired. Please upgrade from the evaluation version to the full released version of the product.
So, you follow the “Upgrading Office Communications Server 2007 Evaluation to the Full Released Version” document :
BUT here’s the result :
OCS Setup log :
Failure
[0xC3EC78D8] Failed to read the Office Communications Server version information. This can happen if the computer clock is not set to correct date and time.
After some research I’ve found that the workaround was to remove the MS Crypto API security update KB974571. So I removed the update, rebooted the machine, and OCS 2007 R2 was up and running again, without any issues.
What is the position of MS regarding this issue :
http://support.microsoft.com/kb/974571/en-us
Microsoft recommends to postpone installing KB974571 on any LCS 2005 / OCS 2007 /OCS 2007 R2 servers.
Microsoft is investigating this issue, and will determine the most appropriate way to address it. Customers who are not running OCS or LCS server are not affected by this known issue, and can safely ignore this issue.
Customers who have deployed the OCS or LCS product on a server should assess the risk that is involved to decide whether to install the security update on that server. These customers should revisit this Knowledge Base article often, because this article will be updated as soon as more information and a resolution are available.
Nice one from MS !
You can download Exchange Server 2010 Release Candidate to the Microsoft Download Center!
This is the build number 14.00.0639.011 and you can download it from here : http://www.microsoft.com/downloads/details.aspx?FamilyID=c6d27da1-ba2c-4570-a491-c0d7b39ede8b
This build is compatible with both Windows 2008 SP2 and Windows 2008 R2 (from RC1 through to RTM). As we changed the store schema between the Exchange Beta and RC, there’s no in-place upgrade from the Beta release. However, we will support in-place upgrade from the Release Candidate through to the final RTM build.
Extract from “Paul Bowden – Release Manager – Exchange Server”
——————————————————————————————–
Here’s a quick start guide to get you up and running as quickly as possible with the new build:
Windows 2008
1. Install Windows Server 2008 x64 (Standard or Enterprise – but not Core or Web Server) and join the appropriate domain
2. Install Service Pack 2 from http://technet.microsoft.com/en-us/windows/dd262148.aspx
3. Install .NET Framework 3.5 Service Pack 1 from http://www.microsoft.com/downloads/details.aspx?FamilyID=ab99342f-5d1a-413d-8319-81da479ab0d7
4. Install the .NET Framework 3.5 SP1 Update from http://www.microsoft.com/downloads/details.aspx?FamilyID=98E83614-C30A-4B75-9E05-0A9C3FBDD20D
5. Install the combined PowerShell v2/Windows Remote Management package (Windows 6.0-KB968930.msu) from Connect (public link TBD)
6. Open a command prompt, and use the installation scripts from the \Scripts sub-folder on the installation media to enable operating system components:
a. For a typical installation of Client Access, Hub Transport, and the Mailbox role, run:
a. For a Client Access role only, enter:
b. For a Hub Transport role, enter:
c. For a Mailbox role, enter:
d. For a Unified Messaging role, enter:
e. For an Edge Transport role, enter:
7. For Hub Transport and/or Mailbox roles, install the Office Filter Pack from http://www.microsoft.com/downloads/details.aspx?FamilyId=60C92A37-719C-4077-B5C6-CAC34F4227CC
8. Run the Setup.exe program from the Exchange 2010 installation media
Windows 2008 R2
1. Install Windows Server 2008 R2 (Standard or Enterprise – but not Core, Web Server or Foundation Server) and join the appropriate domain
2. Open a Windows PowerShell console window from the Accessories menu
3. Enter “Import-Module ServerManager” and press return
4. Use the Add-WindowsFeature cmdlet to enable operating system components:
a) For a typical installation of Client Access, Hub Transport, and the Mailbox role, enter:
b) For a Client Access role only, enter:
c) For a Hub Transport role or Mailbox role, enter:
d) For a Unified Messaging role, enter:
e) For an Edge Transport role, enter:
5. For Hub Transport and/or Mailbox roles, install the Office Filter Pack from http://www.microsoft.com/downloads/details.aspx?FamilyId=60C92A37-719C-4077-B5C6-CAC34F4227CC
6. Restart the computer
7. Run the Setup.exe program from the Exchange 2010 installation media
Exchange 2010 and Upgrades from Windows 2008 R2 RC1 (build 7100) to RTM (build 7600)
You can upgrade the R2 operating system of a server that currently has Exchange 2010 installed. The steps are as follows:
i. Take an existing server running Windows 2008 R2 Release Candidate (build 7100) and Exchange 2010 pre-RTM
ii. Upgrade Exchange 2010 to R4 DF-Final
iii. Copy c:\windows\system32\inetsrv\config\schema\wsmanconfig_schema.xml to a safe place
iv. Insert the Windows 2008 R2 RTM (build 7600) installation media and choose ‘Upgrade’
v. After several restarts, the server should now be upgraded
vi. Copy your saved-off wsmanconfig_schema.xml file to c:\windows\system32\inetsrv\config\schema\
NOTE: In-place upgrades of Exchange 2010 servers running Windows 2008 SP2, to Windows 2008 R2 are not tested or supported.
Active Directory Configuration
a. The schema master must be running a minimum of Windows Server 2003 with Service Pack 1
b. The forest must be in Windows Server 2003 functionality mode (or later)
c. All Exchange 2010 servers must be able to communicate with a global catalog server which is running Windows Server 2003 with Service Pack 1 (or later)
d. Read-only domain controllers (RODC) are not supported with Exchange 2010
e. We generally recommend that you install Exchange 2010 on member servers versus domain controllers. This helps to secure your installation
Enjoy your test !
Goals of the demo :
Use asterisk like a UPD/TCP translator between OCS and a SIP trunking services in UDP mode.
I use Asterisk 1.6 which support TCP and UDP installed on CentOS 5 – Kernel 2.6.18
Installation steps :
OCS R2 —- Mediation —- Asterisk —— Firewall — SIPTrunk
MTLS —- TCP —- UDP —- NAT —– UDP
I use Hyper-V for the two OCS servers and VMware for the Asterisk server.
The first will be use for internal numbering and the second is a generic rule that redirect all call that do not correspond to a valid extension number in OCS to the default gateway.
Phone pattern : ^2(\d{2})$
Translation pattern : +2$1
Phone pattern : ^(.*)$
Translation pattern : $1
Assign the location profile to the front-end server (properties of the pool / properties of front-end / Voice Tab)
NB : Test your dial plan using the Enterprise Voice route helper
tcpenable = yes
bindport = 5060
nat=yes
externip=Valid_FQDN
localnet=Your_Localnet/Your_Subnet
Trunk Name : ocs
PEER Details :
host=ip-mediation-server
type=peer
qualify=yes
transport=tcp
insecure=very
port=5060
canreinvite=yes
fromdomain=yourdomain
context=from-ocs
Incoming Settings :
User context : (I put a OCS username here)
User details :
host=ip-mediation-server
type=peer
transport=tcp
insecure=very
port=5060
context=from-ocs
register string :
(leave blank)
Trunk Name : siptrunk
PEER Details :
type=friend
disallow=all
allow=ilbc&speex&gsm&alaw&ulaw
username=username
secret=password
host=yoursipregistrar
canreinvite=no
context=from-siptrunk
Incoming Settings :
Clear all
register string :
username:password@yoursipregistrar (/yournumber if needded)
Edit Extension_Custom.conf and add a the end of the file :
[from-ocs]
exten => _X.,1,Answer
exten => _X.,2,Dial(SIP/${EXTEN}@siptrunk,,tr)
#include extensions-away-status.conf
[from-siptrunk]
exten => _X.,1,Set(numDialled=+${EXTEN:Number_of_X_to_ignore})
exten => _X.,2,Set(__FROM_DID=${EXTEN})
exten => _X.,3,Answer
exten => _X.,4,Dial(SIP/${numDialled}@ocs,,tr)
exten => _X.,4,Dial(SIP/${numDialled}@ocs)
Assign line number from your sip trunk to Asterisk extension and redirect to phone extension in OCS by using a # after the number.
DID number from your SIP trunk provider —> Extension in Asterisk —> Follow-me to OCS extention (use # after the number to precise that it’s external to asterisk)
Have fun with that and leave me a message if encounter some problems!
It’s probably possible to do the same withother IP/PBX like : Freeswitch, OpenSer, SipxECS, …
Date : 04/08:2009 – Author : Yann Espanet – mail : yann@unifiedcommunications.eu
Exchange 2007 KB Communications Server KB KB Alert
