Article ID: 952787 - Last Review: August 15, 2008 - Revision: 1.0 A digest in a Session Initiation Protocol (SIP) Referred-By header uses a non-standard base64 encoding in Communications Server 2007SYMPTOMSIn Microsoft Office Communications Server 2007, the Session
Initiation Protocol (SIP) Referred-By header includes a signed digest. This
digest guarantees that no intermediate party has altered the basic details of the
referral. The encoding scheme that is used to communicate the signed digest in the Referred-By header is incorrect. Standard base64 encoding should be used, according to the "Request for Comments: 4648" (RFC) document. However, a modified encoding is used that does not communicate the exact length of the data that was encoded. Therefore, a binary-signed binary large object (BLOB) is obtained after the digest in a Referred-By header is decoded. This binary large object may have trailing zero bytes that are appended to it, and these bytes should not be part of the binary large object. RESOLUTION To resolve this issue, install the update package for
Communications Server 2007 that is dated August 2008.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
952783
(http://support.microsoft.com/kb/952783/
)
Description of the update package for Communications Server 2007: August 2008
STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section. MORE INFORMATIONThe Base16, Base32, and Base64 Data Encodings
document http://www.ietf.org/rfc/rfc4648.txt
(http://www.ietf.org/rfc/rfc4648.txt)
Microsoft
provides third-party contact information to help you find technical support.
This contact information may change without notice. Microsoft does not
guarantee the accuracy of this third-party contact information.
| Article Translations
|
Back to the top
