![]() ![]() This ultimately meant that instead of Lync/ExchangeUM using the default receive connectors (which have the required “Exchange Server Authentication” enabled), they instead were using the custom application relay connector (which did not have Exchange Server Authentication enabled). Specifically, a custom connector used for application relay was modified so instead of only the individual IP addresses needed for relay (EX: Printers/Copiers/Scanners/3 rd Party Applications requiring relay), the entire IP subnet was included in the Remote IP Ranges scoping. This issue was caused by incorrectly modifying a receive connector on Exchange. I also wanted to spend more time discussing why this issue happened and why it’s important to understand receive connector scoping. This issue is not necessarily new ( Reference1 Reference2), but it didn’t immediately come up in search results. The voicemail folder on Exchange (C:\Program Files\Microsoft\Exchange Server\V15\UnifiedMessaging\voicemail) was filling up with hundreds of. In a Lync and Exchange UM environment (version doesn’t particularly matter in this case), voicemail messages were not being delivered.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |