Voice Mail Preview will literally transform the way that you look at voice messages in Exchange.
Exchange Unified Messaging (UM) makes it easy to manage your voice messages by delivering them in...
Updated Jul 01, 2019
Version 2.0
Blog Post
Hi Mike
in recent Exchange 2010 UM evaluation testings, I figured out Exchange 2010 UM accept the current SIP ‘history-info’ header standard to recognize diverted number if someone is trying to leave a message.
that's a great achievement from ExCh07 UM which only supported the old/superseded Diversion-Header only) to recognize diverted number
But ... Exchange 2010 UM does not seem to support/accept ‘P-Asserted-Identity’ to identify the subscriber when a user is trying to dial into its own UM Box to listen/retrieve messages.
From my testing’s, Exch2010 only identifies the subscriber properly if subscriber number (calling-party) is sent in (old/supersede) ‘Remote-Party-ID’.
This causes an issue for subscriber access if ‘Remote-Party-ID’ is not present/missing but ‘History-info’ is used and in most newer IP-Telephony Products.
In that case, Exch2010 looks at the History-Info Header which obviously does NOT show the subscriber number (since it’s direct call, not diverted) but the UM Pilot Access Number.
(as per rfc3325, the 1st listed entry in history-info is the initial called party number (Targeted-to-URI) which is in that case the subscriber access number (pilot number)
With this, Exch2010 answers with the standard announcement ‘sorry, the person you are trying to reach does not have a valid voicemailbox in our system …).
Questions :
Since ‘Remote-Party-ID’ (draft-ietf-sip-privacy) has been supersede/replaced by the P-A-I (RFC3325), is there any intension from MSFT to support P-A-I instead ? (or better both, for backward compatibility)
in recent Exchange 2010 UM evaluation testings, I figured out Exchange 2010 UM accept the current SIP ‘history-info’ header standard to recognize diverted number if someone is trying to leave a message.
that's a great achievement from ExCh07 UM which only supported the old/superseded Diversion-Header only) to recognize diverted number
But ... Exchange 2010 UM does not seem to support/accept ‘P-Asserted-Identity’ to identify the subscriber when a user is trying to dial into its own UM Box to listen/retrieve messages.
From my testing’s, Exch2010 only identifies the subscriber properly if subscriber number (calling-party) is sent in (old/supersede) ‘Remote-Party-ID’.
This causes an issue for subscriber access if ‘Remote-Party-ID’ is not present/missing but ‘History-info’ is used and in most newer IP-Telephony Products.
In that case, Exch2010 looks at the History-Info Header which obviously does NOT show the subscriber number (since it’s direct call, not diverted) but the UM Pilot Access Number.
(as per rfc3325, the 1st listed entry in history-info is the initial called party number (Targeted-to-URI) which is in that case the subscriber access number (pilot number)
With this, Exch2010 answers with the standard announcement ‘sorry, the person you are trying to reach does not have a valid voicemailbox in our system …).
Questions :
Since ‘Remote-Party-ID’ (draft-ietf-sip-privacy) has been supersede/replaced by the P-A-I (RFC3325), is there any intension from MSFT to support P-A-I instead ? (or better both, for backward compatibility)