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 Michael,
in recent Exchange 2010 UM evaluation testings, I I found an issue in Exchange 2010 with SIP MWI (un-solicited NOTIFY), causing Interop issue with certain IP-PBX’s.
Exchange 2010 seems to use a mal-formed (invalid or none-rfc3261 compliant) SIP URI in the FROM: Header.
when Exchange 2010 sends the unsolicited NOTIFY for MWI, it puts it’s own FQDN in the FROM Header.
that's ok so far but Exchange 2010 does NOT divides the FQDN into the User-Portion and Host-portion (user@host) as per RFC3261
as example : Exchange 2010 UM puts something like this in FROM Header : FROM:exch2010um.contoso.com
however, a correct URI would look like exch2010um@contonso.com, exch2010um@192.1.1.1 (IP-Addr) or something like mwi@exch2010um.contoso.com
that's at least true 'til 14.00.0532.009 (R4/public beta)
this is causing issues on some IP-PBX's who validate the FROM Header in incomming packets as well. packets are being discarded due to invalide SIP Header (SIP URI)
will this be fixed in RC or RTM ?
in recent Exchange 2010 UM evaluation testings, I I found an issue in Exchange 2010 with SIP MWI (un-solicited NOTIFY), causing Interop issue with certain IP-PBX’s.
Exchange 2010 seems to use a mal-formed (invalid or none-rfc3261 compliant) SIP URI in the FROM: Header.
when Exchange 2010 sends the unsolicited NOTIFY for MWI, it puts it’s own FQDN in the FROM Header.
that's ok so far but Exchange 2010 does NOT divides the FQDN into the User-Portion and Host-portion (user@host) as per RFC3261
as example : Exchange 2010 UM puts something like this in FROM Header : FROM:exch2010um.contoso.com
however, a correct URI would look like exch2010um@contonso.com, exch2010um@192.1.1.1 (IP-Addr) or something like mwi@exch2010um.contoso.com
that's at least true 'til 14.00.0532.009 (R4/public beta)
this is causing issues on some IP-PBX's who validate the FROM Header in incomming packets as well. packets are being discarded due to invalide SIP Header (SIP URI)
will this be fixed in RC or RTM ?