{"id":403,"date":"2015-01-09T11:02:10","date_gmt":"2015-01-09T09:02:10","guid":{"rendered":"http:\/\/www.vatland.no\/?p=403"},"modified":"2015-01-09T11:02:10","modified_gmt":"2015-01-09T09:02:10","slug":"lync-voice-messages-does-not-arrive-in-the-mailbox","status":"publish","type":"post","link":"https:\/\/www.vatland.no\/index.php\/lync-voice-messages-does-not-arrive-in-the-mailbox\/","title":{"rendered":"Lync voice messages does not arrive in the mailbox."},"content":{"rendered":"

\"exchange\"<\/a>It is time to remind me to always check Exchange for existence of\u00a0receive connectors and their scoping. In this case users where able to record voice messages, but they never arrived in recipients mailbox. Checked the Exchange server event Viewer.\"voicemailsmtp2\"<\/a><\/p>\n

This indicated that there is something wrong with the SMTP server. There I found a “Mailrelay” receive connector configured\u00a0to not use\u00a0 authentication or encryption also scoped\u00a0to hit\u00a0the IP subnet containing the server IP address. Created two new ranges, excluding the exchange server ip address.<\/p>\n

Here we go. This done the trick.<\/p>\n","protected":false},"excerpt":{"rendered":"

It is time to remind me to always check Exchange for existence of\u00a0receive connectors and their scoping. In this case users where able to record voice messages, but they never arrived in recipients mailbox. Checked the Exchange server event Viewer.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"#Lync voice messages does not arrive in the mailbox.","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[5,6],"tags":[35,25,29,28,27,26],"class_list":["post-403","post","type-post","status-publish","format-standard","hentry","category-exchange","category-lync","tag-exchange","tag-lync","tag-receiveconnector","tag-relayconnector","tag-smtp","tag-unified-messaging"],"aioseo_notices":[],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_likes_enabled":false,"jetpack-related-posts":[{"id":37,"url":"https:\/\/www.vatland.no\/index.php\/missed-call-notification-from-lync-missing-in-users-mailbox\/","url_meta":{"origin":403,"position":0},"title":"Missed Call notification from Lync missing in users mailbox.","author":"Atle","date":"June 13, 2013","format":false,"excerpt":"A new install of Lync and Exchange. Enabled enterprise voice and Unified Messaging. Useres never get missed call notifications in their mailbox. On the exchange server there where several entries in the eventviewer complaining about smtp and voice mail files. \u00a0 Solution to this is to verify that the receive\u2026","rel":"","context":"In "Exchange"","block_context":{"text":"Exchange","link":"https:\/\/www.vatland.no\/index.php\/category\/exchange\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":645,"url":"https:\/\/www.vatland.no\/index.php\/exchange-um-event-id-1400\/","url_meta":{"origin":403,"position":1},"title":"Exchange UM event ID 1400","author":"Atle","date":"February 12, 2016","format":false,"excerpt":"This is a rather confusing event. It occurs on the Exchange server 2010 that is holding the Unified Messaging role. \"The following UM IP gateways did not respond as expected to a SIP OPTIONS request\", and at the end \"This operation has timed out\". The server mentioned in the erro\u2026","rel":"","context":"In "Exchange"","block_context":{"text":"Exchange","link":"https:\/\/www.vatland.no\/index.php\/category\/exchange\/"},"img":{"alt_text":"exevent1400","src":"https:\/\/i0.wp.com\/www.vatland.no\/wp-content\/uploads\/2016\/02\/exevent1400.jpg?resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.vatland.no\/wp-content\/uploads\/2016\/02\/exevent1400.jpg?resize=350%2C200 1x, https:\/\/i0.wp.com\/www.vatland.no\/wp-content\/uploads\/2016\/02\/exevent1400.jpg?resize=525%2C300 1.5x"},"classes":[]},{"id":544,"url":"https:\/\/www.vatland.no\/index.php\/unable-to-join-lyncs4b-from-client-schedule-tab\/","url_meta":{"origin":403,"position":2},"title":"Unable to join Lync\\S4B from client schedule tab.","author":"Atle","date":"September 11, 2015","format":false,"excerpt":"Latest issue was kind of a puzzle. When one organization sent Skype meeting invitation to another organization it was impossible to click on the meeting in the schedule tab of Skype\/Lync. \"Join\" functionality\u00a0missing from sceduler tab in Skype or Lync. Right click on the meeting gave nothing. The links in\u2026","rel":"","context":"In "Exchange"","block_context":{"text":"Exchange","link":"https:\/\/www.vatland.no\/index.php\/category\/exchange\/"},"img":{"alt_text":"skype","src":"https:\/\/i0.wp.com\/www.vatland.no\/wp-content\/uploads\/2015\/09\/skype-150x150.jpg?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":14,"url":"https:\/\/www.vatland.no\/index.php\/lync-unified-contact-store-ucs\/","url_meta":{"origin":403,"position":3},"title":"Lync Unified Contact Store – UCS","author":"Atle","date":"March 7, 2014","format":false,"excerpt":"How do I check and enable Lync UCS? First of all you need Exchange 2013 , then\u00a0make sure you have enabled UCS in Lync server. By running get-csuserservicesPolicy and verify it has been set to UCSAllowed=TRUE Next check you client policy. Get-CsClientPolicy should show you \"EnableExchangeContactSync = true\" for the\u2026","rel":"","context":"Similar post","block_context":{"text":"Similar post","link":""},"img":{"alt_text":"USERSP","src":"https:\/\/i0.wp.com\/www.vatland.no\/wp-content\/uploads\/2014\/03\/USERSP-300x71.jpg?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":95,"url":"https:\/\/www.vatland.no\/index.php\/move-lync-database-to-new-sql-server\/","url_meta":{"origin":403,"position":4},"title":"Move Lync database to new sql server.","author":"Atle","date":"August 3, 2011","format":false,"excerpt":"This is how I've done it. First in lab then in production. This is moving\u00a0enterprise edition databases. For this to work you need one extra temporary sql server and one Lync server in a temporary Lync pool ,along with the new SQL production server. 1. Export Lync configuration just in\u2026","rel":"","context":"In "Lync"","block_context":{"text":"Lync","link":"https:\/\/www.vatland.no\/index.php\/category\/lync\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":559,"url":"https:\/\/www.vatland.no\/index.php\/lync-server-security-fix-kb3080353-causing-problems\/","url_meta":{"origin":403,"position":5},"title":"Lync server security fix KB3080353 causing problems.","author":"Atle","date":"September 22, 2015","format":false,"excerpt":"(UPDATED) After we installed the Latest Lync server 2013 security fix (Security Update for Lync Server 2013 Web Components Server KB3080353) we have had severeal issues where users where unable to sign in to\u00a0 Lync. This was the server complaining about the client certificate , normally it is the client\u2026","rel":"","context":"In "Lync"","block_context":{"text":"Lync","link":"https:\/\/www.vatland.no\/index.php\/category\/lync\/"},"img":{"alt_text":"LyncCertError","src":"https:\/\/i0.wp.com\/www.vatland.no\/wp-content\/uploads\/2015\/09\/LyncCertError.png?resize=350%2C200","width":350,"height":200},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/posts\/403","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/comments?post=403"}],"version-history":[{"count":1,"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/posts\/403\/revisions"}],"predecessor-version":[{"id":405,"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/posts\/403\/revisions\/405"}],"wp:attachment":[{"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/media?parent=403"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/categories?post=403"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/tags?post=403"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}