Archiving and CDR Agent and MSMQ

Microsoft Office Communications Server 2007 and Microsoft Office Communications Server 2007 R2 will reach end of support on January 9, 2018. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.

The archiving and CDR agent uses MSMQ to receive notifications from the Archiving and CDR Server destination queue. (Message Queuing also serves as a local temporary transmission queue if the Archiving and CDR Server is unavailable.) Message Queuing must be installed on all computers that participate in archiving, such as the following:

  • An Office Communications Server with an archiving and CDR agent that connects to the Archiving and CDR Server.

  • The Office Communications Server that is running the Archiving and CDR Server.

  • You must install Message Queuing on each server that you want to associate with the Archiving and CDR Server. If you want to archive an Enterprise pool, you must install Message Queuing on each server in the pool.

  • The computer that is running Message Queuing must be a member of a Microsoft Windows Authorization Access group to authenticate users in a Microsoft Windows Server¬†2003 domain.

  • Because Message Queuing relies on the Active Directory Domain Services for encryption to the destination queue, Message Queuing must be installed with the Active Directory integration component, which is the default configuration during Message Queuing installation.

    Note

    In a two-tier topology where the Archiving and CDR service component and the message queue are on a separate computer from the archiving database, automatic setup of encryption is not supported for the messages that are sent by the Archiving and CDR service component to the archiving database. Instead, encryption of the link between the Archiving and CDR service component and the archiving database must be configured manually by using SQL Server SSL encryption. For more information about configuring SQL Server SSL encryption, see the Microsoft Knowledge Base article 276553 at https://r.office.microsoft.com/r/rlidOCS?p1=kb276553. For information about configuring the registry to establish and help enforce SQL encryption, see the Microsoft Knowledge Base article 841695 at https://r.office.microsoft.com/r/rlidOCS?p1=kb841695.

  • Do not set the destination queue (the private queue) privacy level to None on the server that is running the Archiving and CDR Server. The privacy level must be set to either Body or Optional. The default setting is Optional.

  • Do not set the privacy level to Body when the Archiving and CDR Server and the Front End Server are installed on the same computer. When the Archiving and CDR Server and the Front End Server are installed on the same computer and the privacy level on the destination queue is set to Body, messages are not archived and the server stops running if archiving is running as a critical service.

The Enterprise pool, Standard Edition server or the Proxy Server, if configured for archiving, activates the archiving agent. The archiving agent then checks all outgoing SIP messages on the Office Communications Server to determine whether it should be archived and in what form. This requires the archiving agent to look up the archiving settings for the sender and receiver of the message (set per user). Based on these archiving settings, the archiving agent takes one of the following actions:

  • Do not archive.

  • Send message for archiving.

When messages are sent for archiving, the archiving agent queues the message to the configured MSMQ. The Archiving and CDR service is listening to the destination message of the MSMQ and on receiving this message, it writes it to the designated SQL Server.