We extract voicemails as emails from our PBX system. The Caller ID information displays as the Display Name in the message, but the email address in the From: header is blank. When I directly connect to the PBX using Outlook as an IMAPor POPclient, I can see the Caller ID. When I have the system send messages to Exchange via SMTP, the Display Name is truncated entirely, though it is contained in the message.PBX vendor says this is an Exchange issue, though if they just filled in ANY email address I know the problem would be resolved.However, that isn't an option.Is there any way to force Exchange to show the display name, even when the email address is blank?Here is an example message... the 18185551212 is only visible when viewing the message contents... it does not show anywhere via the standard Outlook client display.From: 18185551212 <>Subject: VOICE-Message (~00:00:51)To: me@you.comX-UID: 2147516280 X-MessageContext: VoiceMessage.4635 X-MessageDuration: 51000 X-MessageSenderID: 18185551212 X-ReplyAllowed: yes X-Sensitivity: public X-Forwardable: yes X-CallAble: yes X-MessageCodec: 1 MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="1240419290=:1" Return-Path: <> X-OriginalArrivalTime: 22 Apr 2009 19:55:04.0134 (UTC) FILETIME=[3A800E60:01C9C384] --1240419290=:1 Content-Type: AUDIO/x-wav; name="Attachment_0.wav" Content-Transfer-Encoding: BASE64 Content-Disposition: ATTACHMENT; filename="Attachment_0.wav"

Hello Nickle,Let me explain you why is this happening.The Outlook Properties will show the 5 tabs if the user is in the same Exchange organization. However, if the user is in a different Exchange organization, it will show only E-mail properties because the Exchange does not have the user's Active Directory information if he is not in the same Exchange organization.Arun Kumar | MCSE - 2K3 + Messaging | ITIL-F V3

Hi, I agree with Arun_Kumar. When Unified Messaging receives a call the SIP INVITE request has the phone number of the calling party. It will try to resolve the number to users in Active Directory or the personal contact folder for the called user. The sequence of operation is as follows: 1. Checks the calling party for null. If the calling party is null or empty it will return a null reference specifiying an unknown caller. 2. Gets the dial plan object associated with the called party. 3. Tries to find the caller in the active directory by using the called users dial plan and calling party number. The search is performed agaist eum type of address in the active directory. The search string is: Caller-id;phone-context=called-party-dialplan.domain.com 4. If the caller was not found in the active directory, then Unified Messaging will continue the search by pulling the list of contacts for the called user. It will try to match the business, home, or cell phone number of the contacts. The contacts phone number is trimmed out just like outbound dialing (see Module 3: Lesson 4 for more information) prior to matching. 5. If a match is found on any of the phone numbers mentioned above, it populates the caller ID with the information found. 6. If no match is found, returns a null reference indicating an unknown caller. Regards, Xiu