get it here
The Group Chat feature lets organizations set up searchable, topic-based chat rooms that persist over time, allowing geographically distributed teams to better collaborate with one another while preserving organizational knowledge.
The Microsoft Office Communications Server 2007 R2 Software Development Kit (SDK) includes documentation and sample applications developed with the Office Communications Server 2007 R2 platform.
Get it here
972951 (http://support.microsoft.com/kb/972951/ ) A compliance server reports incomplete or inaccurate information about user JOIN and PART events in Microsoft Office Communications Server 2007 R2 Group Chat Server
972944 (http://support.microsoft.com/kb/972944/ ) You may experience performance issues in a channel server in Communications Server 2007 R2 Group Chat Channel Server
973384 (http://support.microsoft.com/kb/973384/ ) The Group Chat service does not work after you restart a computer that is running Office Communications Server 2007 R2 Group Chat Server
973385 (http://support.microsoft.com/kb/973385/ ) Users in a secured organizational unit (OU) named "Blocking Inheritance" cannot use the Group Chat Admin Tool
973386 (http://support.microsoft.com/kb/973386/ ) A compliance XML output file is not generated by a compliance server in Microsoft Office Communications Server 2007 R2 Group Chat Server
I my blog on Exchange Connectivity test tool I mentioned that it would be smart for such a tool for OCS.
So here it is: https://www.testocsconnectivity.com/
My recommendation is to not use your normal account, but perhaps make a test account that you can use to test on this site.
The site is still in Beta !
The Exchange connectivity test tool link is here
File Name:
OCS 2007 R2 Technical Reference for Clients.doc
Version:
1.0
Date Published:
7/30/2009
Language:
English
Download Size:
1.1 MB
get it here
get it here
the desciption should be on this link but its not working ?
http://support.microsoft.com/kb/970275 some kind of bad/wrong link on this page, when clicking the “972402”
972402 (http://support.microsoft.com/kb/972402/ ) Office Communicator 2007 R2 runs concurrently with Office Communications Server 2007 R2 Attendant
Udate/new Capacity Planning Tool
Get it here
File Name:
communicator.msp
Version:
2.0.6362.137
Knowledge Base (KB) Articles:
KB969694
Date Published:
7/28/2009
Language:
English
Download Size:
5.8 MB
967832 (http://support.microsoft.com/kb/967832/ ) Description of the update package for Communications Server 2007 R2 Application Host: April 2009
971296 (http://support.microsoft.com/kb/971296/ ) Description of the update package for Office Communications Server 2007 R2, Application Sharing Server: July 2009
971289 (http://support.microsoft.com/kb/971289/ ) Description of the update package for Office Communications Server 2007 R2, Administration Tools: July 2009
971793 (http://support.microsoft.com/kb/971793/ ) Description of the update package for Office Communications Server 2007 R2, Audio/Video Conferencing Server: July 2009
971299 (http://support.microsoft.com/kb/971299/ ) Description of the update package for Office Communications Server 2007 R2, Core Components: July 2009
969824 (http://support.microsoft.com/kb/969824/ ) Description of the update package for Office Communications Server 2007 R2, Communicator Web Access: July 2009
968922 (http://support.microsoft.com/kb/968922/ ) Description of the update package for Office Communications Server 2007 R2, Conferencing Attendant: July 2009
969823 (http://support.microsoft.com/kb/969823/ ) Description of the update package for Office Communications Server 2007 R2, Conferencing Announcement Service: July 2009
971298 (http://support.microsoft.com/kb/971298/ ) Description of the update package for Office Communications Server 2007 R2, Monitoring Server: July 2009
969835 (http://support.microsoft.com/kb/969835/ ) Description of the update package for Office Communications Server 2007 R2, Mediation Server: July 2009
967835 (http://support.microsoft.com/kb/967835/ ) Description of the update package for Communications Server 2007 R2, Outside Voice Control: April 2009
967829 (http://support.microsoft.com/kb/967829/ ) Description of the update package for Communications Server 2007 R2, Response Group Service: April 2009
969821 (http://support.microsoft.com/kb/969821/ ) Description of the update package for Office Communications Server 2007 R2: July, 2009
969834 (http://support.microsoft.com/kb/969834/ ) Description of the update package for Office Communications Server 2007 R2 database: July, 2009
970679 (http://support.microsoft.com/kb/970679/ ) Description of the update package for Office Communications Server 2007 R2, Unified Communications Managed API 2.0 Core Redist 64-bit: July 2009
971297 (http://support.microsoft.com/kb/971297/ ) Description of the update package for Office Communications Server 2007 R2, Web Conferencing Server: July 2009
967830 (http://support.microsoft.com/kb/967830/ ) Description of the update package for Communications Server 2007 R2, Web Components: April 2009
File Name:
communicator.msp
Version:
6907.37
Knowledge Base (KB) Articles:
KB969695
Date Published:
7/28/2009
Language:
English
Download Size:
9.9 MB
971843 (http://support.microsoft.com/kb/971843/ ) Enterprise administrators cannot both set and enforce the Personal Information Manager settings for Outlook Integration to be able to turn off Outlook Integration for Microsoft Office Communicator 2007 R2
972085 (http://support.microsoft.com/kb/972085/ ) Error message when you start Microsoft Office Communicator 2007 R2: "Either there is no default mail client or the current mail client cannot fulfill the message request. Please run Microsoft Office Outlook and set it as the default mail client."
972087 (http://support.microsoft.com/kb/972087/ ) In Communicator 2007 R2 when you use Tanjay to call a user, you hear both the ringing and the audio from the user side
972090 (http://support.microsoft.com/kb/972090/ ) Your voice is discontinuous when you use Microsoft Office Communicator 2007 R2 to make a call on a Windows 7 or a Windows Server 2008 R2-based remote desktop
972091 (http://support.microsoft.com/kb/972091/ ) Error message in Communicator 2007 R2 when you try to join a conference call from Outlook: "Can't open the program because Office Communicator or Office Communications Server Attendant is already running on your windows user account"
971845 (http://support.microsoft.com/kb/971845/ ) The delegate permissions feature in Office Communicator 2007 R2 is unavailable to non-unified communications users
971846 (http://support.microsoft.com/kb/971846/ ) Video frames are not displayed in Office Communicator 2007 R2 on a Windows XP-based computer
972093 (http://support.microsoft.com/kb/972093/ ) Error message when you try to adjust the volume during a call in a Communicator 2007 R2 conversation window on a computer that is running Windows XP: "Cannot adjust the speaker volume"
972097 (http://support.microsoft.com/kb/972097/ ) Error message when distribution group expansion fails in Office Communicator 2007 R2: "Cannot save a local copy of your distribution groups."
972099 (http://support.microsoft.com/kb/972099/ ) A "Meet Now - Invite by Email" HTML e-mail message that is generated by Microsoft Office Communicator 2007 R2 has unreadable text in the message body
972403 (http://support.microsoft.com/kb/972403/ ) Communicator 2007 R2 users may experience network performance issues that are caused by Global address list (GAL) full file download or GAL delta file download
971628 (http://support.microsoft.com/kb/971628/ ) When a delegate on behalf of a manager tries to use the Conferencing Add-in for Outlook to schedule a live meeting or to schedule a conference, the delegate's information instead of manager's information displays in the conferencing request unexpectedly
Note To resolve this issue, you have to apply update 969695, update 969696, and update 969821.
For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
969696 (http://support.microsoft.com/kb/969696/ ) Description of the update for Live Meeting Conferencing Add-in for Outlook: July 2009
969821 (http://support.microsoft.com/kb/969821/ ) Description of the update package for Office Communications Server 2007 R2: July, 2009
971078 (http://support.microsoft.com/kb/971078/ ) An Automatic Update download is not initiated on a computer that is running Office Communicator 2007 R2 build 3.5.6907.9
968504 (http://support.microsoft.com/kb/968504/ ) Description of the Communicator 2007 R2 update for Microsoft Online Services
968623 (http://support.microsoft.com/kb/968623/ ) You experience one-way audio when LG-Nortel IP8540 or Polycom CX700 phones are used in an Audio Video call on Windows XP
968624 (http://support.microsoft.com/kb/968624/ ) Error events occur when you disconnect a computer that is running Communicator 2007 R2 from the network: "Event ID: 3" or "Event ID: 7"
968625 (http://support.microsoft.com/kb/968625/ ) Description of a hotfix that applies the initial changes for the integration of Office Communicator 2007 R2 and the next version of Office after the Office 2007 release
968628 (http://support.microsoft.com/kb/968628/ ) Communicator 2007 R2 stores the Actual Remote Number (The number that is dialed) for outgoing calls to a remote party
968631 (http://support.microsoft.com/kb/968631/ ) The font in the Conversation window is very small when you run Office Communicator 2007 R2 on a Windows Vista-based computer that has high DPI (120 DPI) with Internet Explorer 8 installed
968632 (http://support.microsoft.com/kb/968632/ ) You cannot click the password field and enter a password when you sign in to Office Communicator 2007 R2
968634 (http://support.microsoft.com/kb/968634/ ) Description of Office Communicator 2007 R2 update to support Polycom roundtable devices
968690 (http://support.microsoft.com/kb/968690/ ) In Office Communicator 2007 R2, User A gets a failure-to-deliver message after sending an IM to User B even though User B receives the message
Problem/issue regarding “caller number” when using simultan ringing and Calling Line Identification Presentation Special Arrangement (CLIP SA).
When you have that service (CLIPSA) from your Telco provider, you have the possibility to see the Originate Caller number displayed on your Mobile phone.
But in OCS R2 it depend on if you are logged in to CoMo or not.
Problem:
Originate Caller number not sent to the mobile when logged in on CoMo, then it’s my company number (DID) as the caller number.
But the Originate Caller number is sent when not logged in on CoMo.
It’s not a problem if you see the “popup/toast” on your mobile, here you can see who the caller is, but if you like to use your call history on you mobile you will only see your own DID as caller ID. Okay then you can use the “last contact” in CoMo, but you haven’t any call detail (date-time) so this “last contact” list isn’t that useful.
Read more about CLIP SA here:
http://www.cept.dk/F580A011-3400-4C40-AB6E-40CAFE055F57?frames=no&
http://www.erodocdb.dk/Docs/doc98/Official/Pdf/ECCRec0301.pdf
http://www.niccstandards.org.uk/files/current/nd1202_2000_01.pdf?type=pdf
| Communications_Server_2007_R2_Documentation.chm |
| Communications_Server_2007_R2_Documentation.zip |
| OCS 2007 R2 Administering CWA.doc |
| OCS 2007 R2 Administering Group Chat.doc |
| OCS 2007 R2 Administering OCS.doc |
| OCS 2007 R2 Backup and Restoration.doc |
| OCS 2007 R2 Command Line Reference.doc |
| OCS 2007 R2 Deploy Monitoring Server.doc |
| OCS 2007 R2 Deploying Archiving Server.doc |
| OCS 2007 R2 Deploying Communicator.doc |
| OCS 2007 R2 Deploying CWA.doc |
| OCS 2007 R2 Deploying Dial-In Conferencing.doc |
| OCS 2007 R2 Deploying Edge Servers.doc |
| OCS 2007 R2 Deploying Enterprise Edition.doc |
| OCS 2007 R2 Deploying Enterprise Voice.doc |
| OCS 2007 R2 Deploying Group Chat Server.doc |
| OCS 2007 R2 Deploying in a Multiforest Topology.doc |
| OCS 2007 R2 Deploying Monitoring Server.doc |
| OCS 2007 R2 Deploying Response Group Service.doc |
| OCS 2007 R2 Deploying Standard Edition.doc |
| OCS 2007 R2 Getting Started - Documentation Roadmap.doc |
| OCS 2007 R2 Getting Started - New Client Features.doc |
| OCS 2007 R2 Getting Started - New Server Features.doc |
| OCS 2007 R2 Getting Started - Technical Overview.doc |
| OCS 2007 R2 Getting Started - Unified Communications Glossary.doc |
| OCS 2007 R2 Migration from 2005.doc |
| OCS 2007 R2 Migration from 2007.doc |
| OCS 2007 R2 Planning.doc |
| OCS 2007 R2 Preparing Active Directory Domain Services.doc |
| OCS 2007 R2 Security.doc |
| OCS 2007 R2 Supportability.doc |
| OCS 2007 R2 Technical Reference for Clients.doc |
| OCS 2007 R2 Technical Reference.doc |
| OCS 2007 R2 Troubleshooting.doc |
| OCS 2007 R2 Upgrading the Evaluation to Full Released Version.doc |
| OCS 2007 R2 Walkthrough - Mediation Server Replacement.doc |
| OCS 2007 R2 Walkthrough - Scale to Load Balanced Edge Server.doc |
| OCS 2007 R2 Walkthrough - Scale to Load Balanced EE Pool.doc |
| OCS 2007 R2 Walkthrough – Small- to-Medium Business Deployment.doc |
| OCS 2007 R2 Walkthrough - Voice Deployment.doc |
Get it them one by one here or get them all by downloading this ZIP file Communications_Server_2007_R2_Documentation.zip
I often get this questions why isn’t it the same phone numbers that I see on my Company contact on my Mobil Communicator and my Communicator.
Or questions like this: on my Mobile Communicator I can’t see any phone number at all on company contact, but in my Communicator I can see Work-Mobile-Privat.
My quick answer is: The Mobile Communicator doesn’t have a Global adresse list locally. and the “publish this phone number” in Communicator isn’t set.
Conclusion: If you like other users to see your phone number, you must use the “Publish this phone number” and the “level of access” to choose what number they can see in Mobile Communicator, regardless of they are users from your AD/organization/OCS system.
This is not like the way “PC” Communicator normaly interact!
The way that the Mobile Communicator get phone number is when it’s gets the contactcard in the Presence XML document on its contacts, at logon or update.
This table show what you see and don’t see when numbers are publish in Active Directory, and have set the “publish this phone number” in communicator, in combination with access level.
This behavior is like when one of you contact is a Federated contact and you like them to be able to see your phone numbers.
In the presence XML Document that users publish to the front-end server is all the information on what the Mobile Communicator can see and can’t see.
Use Snooper to trace:
SIP Snooper trace of a posted presence XML document from client where no numbers have set the “publish this phone number” (notes the <publish>FALSE</publish> )
<userInformation xmlns="http://schemas.microsoft.com/2006/09/sip/options/userInformation"><phones>
<phonetype="work"><publish>false</publish><readOnly>true</readOnly><displayString>+4589490123</displayString><uri>tel:+4589490123</uri></phone>
<phonetype="mobile"><publish>false</publish><readOnly>true</readOnly><displayString>+4747474747</displayString><uri>tel:+4747474747</uri></phone>
<phonetype="home"><publish>false</publish><readOnly>true</readOnly><displayString>+4646464646</displayString><uri>tel:+4646464646</uri></phone>
<phonetype="other"><publish>false</publish></phone></phones><callHandlingList><lastPhone><displayString>90138</displayString><uri>tel:+4589490138;ext=90138</uri></lastPhone></callHandlingList></userInformation>
******************************************************************************
Snooper trace: this XML post is when work number is set to “publish this phone number” (notes the missing <publish>FALSE</publish> on work number)
<userInformation
xmlns="http://schemas.microsoft.com/2006/09/sip/options/userInformation">
<phones><phonetype="work"><readOnly>true</readOnly><displayString>+4589490123</displayString><uri>tel:+4589490123</uri></phone>
<phonetype="mobile"><publish>false</publish><readOnly>true</readOnly><displayString>+4747474747</displayString><uri>tel:+4747474747</uri></phone>
<phonetype="home"><publish>false</publish><readOnly>true</readOnly><displayString>+4646464646</displayString><uri>tel:+4646464646</uri></phone>
<phonetype="other"><publish>false</publish></phone></phones><callHandlingList><lastPhone><displayString>90138</displayString><uri>tel:+4589490138;ext=90138</uri></lastPhone></callHandlingList></userInformation>
</category>
Snooper trace: This part of the contactcard is what mobile Communicator get from the front-end server (notes the work number is in this)
</contactCard>
</category>
<category name="contactCard" instance="3" publishTime="2009-07-24T14:22:00.127">
<contactCard xmlns="http://schemas.microsoft.com/2006/09/sip/contactcard">
<phone type="work">
<uri>tel:+4589490123</uri>
</phone>
</contactCard>
Here you can read a bit more on setting phone option.
In the text below from this link, it says that you can’t unpublish this number when its provided from Activ directory, thats not the case when you are using Mobil communicator, only when using “PC”Communicator, On Mobile Communicator you can’t see any numbers on your contacts if they haven’t set this “publish”
Text from link *********
About Active Directory and why some phone numbers cannot be modified or unpublished
Phone numbers that are provided to Communicator from Active Directory will appear in the Phones tab as inactive fields and cannot be edited. Additionally, these numbers cannot be unpublished. Clearing the Publish check box for numbers provided from Active Directory will not unpublish the number.
Setting access level
Snooper trace where a user set's access level for jan@ocsblogs.eu to Personal
Message-Body: <setContainerMembers xmlns="http://schemas.microsoft.com/2006/09/sip/container-management"><container id="400" version="8"><member action="add" type="user" value="jan@ocsblogs.eu"/></container></setContainerMembers>
$$end_record
Container ID Description
100 Presence is accessible by all federated users.
200 Users from the same company can access the presence data of the publisher.
300 The team members of the publisher can access the presence data of the publisher.
400 Specified subscribers have unrestricted access to the presence data, including sending a potentially interruptive IM invitation when the publisher's status is displayed as Do Not Disturb.
32000 The specified members are blocked to view the presence data. The category instances should be empty category elements.
When Troubleshooting Exchange UM and RNL (reverse number lookup) Jens has a blog on how Exchange behave and Glen has a blog regarding diagnostic logging.
Then key takeaways in Jens blog on Exchange and RNL, is that Exchange UM use the Active Directory attribute msRTCSIP-Line and personal contacts for RNL.
When you need to troubleshoot Exchange UM you set the Loglevel on Exchange UM with Glen’s Powershell script and then you will get all the “debug like” information in the eventlog on Exchange
Event log Category: get info here
Jens blog on Exchang UM here
Glen’s blog about diagnostic logging here and the script to set loglevel is here
Today is an important day for Nortel Enterprise Solutions. Following our announcement on June 19th that Nortel is advancing in its discussions to sell its businesses, Nortel announced it has entered into a “stalking horse” asset and share sale agreement with Avaya Inc. for its North American, Caribbean, Latin American and Asia Enterprise Solutions business, and an asset sale agreement with Avaya for the Europe, Middle East and Africa portion of its Enterprise Solutions business, for US$475 million. These agreements include the planned sale of substantially all of the assets of the Enterprise Solutions business globally as well as the shares of Nortel Government Solutions Inc. and DiamondWare, Ltd.
get more info here
