{"id":645,"date":"2016-02-12T17:45:43","date_gmt":"2016-02-12T16:45:43","guid":{"rendered":"http:\/\/www.vatland.no\/?p=645"},"modified":"2016-02-12T17:45:43","modified_gmt":"2016-02-12T16:45:43","slug":"exchange-um-event-id-1400","status":"publish","type":"post","link":"https:\/\/www.vatland.no\/index.php\/exchange-um-event-id-1400\/","title":{"rendered":"Exchange UM event ID 1400"},"content":{"rendered":"

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 is, in this senario, the Lync server.\"exevent1400\"<\/a><\/p>\n

I thought I knew this PKI stuff and I was sure that all my certificates where correct. Also when telneting for the exchange server to the Lync server on port 5061 there was most defiantly an answer – No timeout”. After a while a decided to do all my certificates all over. Replacing the Lync , \u00a0of course made no difference. When replacing the exchange certificate I change the SN to be the FQDN of the server, This did the trick. The error message disappeared. So now I remember that on Exchange UM server keep FQDN as Subject name and place all other names as SAN’s<\/p>\n","protected":false},"excerpt":{"rendered":"

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 is, in this senario, the … Continue reading Exchange UM event ID 1400<\/span> →<\/span><\/a><\/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":"#Exchange UM event ID 1400","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":[],"class_list":["post-645","post","type-post","status-publish","format-standard","hentry","category-exchange","category-lync"],"aioseo_notices":[],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_likes_enabled":false,"jetpack-related-posts":[{"id":403,"url":"https:\/\/www.vatland.no\/index.php\/lync-voice-messages-does-not-arrive-in-the-mailbox\/","url_meta":{"origin":645,"position":0},"title":"Lync voice messages does not arrive in the mailbox.","author":"Atle","date":"January 9, 2015","format":false,"excerpt":"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. This indicated that there is something wrong with the SMTP\u2026","rel":"","context":"In "Exchange"","block_context":{"text":"Exchange","link":"https:\/\/www.vatland.no\/index.php\/category\/exchange\/"},"img":{"alt_text":"exchange","src":"https:\/\/i0.wp.com\/www.vatland.no\/wp-content\/uploads\/2014\/09\/exchange.jpg?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":241,"url":"https:\/\/www.vatland.no\/index.php\/lync-federation-failes-for-some-partners\/","url_meta":{"origin":645,"position":1},"title":"Lync federation failes for some partners.","author":"Atle","date":"August 12, 2014","format":false,"excerpt":"You have installed Lync edge server and have\u00a0issues federating with some or all of your partners. If you check the eventlog you might see multiple errors\u00a0like \u00a0event Source\u00a0:\u00a0\"LS Protocol Stack\" and Event ID 14428. Event description might mislead you to think that there is something wrong with\u00a0your partners certificate.\u00a0 The\u2026","rel":"","context":"In "Lync"","block_context":{"text":"Lync","link":"https:\/\/www.vatland.no\/index.php\/category\/lync\/"},"img":{"alt_text":"Lync2013","src":"https:\/\/i0.wp.com\/www.vatland.no\/wp-content\/uploads\/2014\/05\/Lync2013.gif?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":37,"url":"https:\/\/www.vatland.no\/index.php\/missed-call-notification-from-lync-missing-in-users-mailbox\/","url_meta":{"origin":645,"position":2},"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":57,"url":"https:\/\/www.vatland.no\/index.php\/lync-phone-unable-to-sign-in-after-windows-update-on-lync-server\/","url_meta":{"origin":645,"position":3},"title":"Lync phone unable to sign in after windows update on Lync Server.","author":"Atle","date":"January 2, 2013","format":false,"excerpt":"After update to Root Sertificates ( KB931125) http:\/\/support.microsoft.com\/kb\/931125\u00a0You are constantly getting Warning in the eventlog. Also Lync Phones will be unable to sign in. The error message on the phone is that the \"Registrar FQDN could not be resolved\". UPDATED: On new Phones you will only get a message that\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":14,"url":"https:\/\/www.vatland.no\/index.php\/lync-unified-contact-store-ucs\/","url_meta":{"origin":645,"position":4},"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":408,"url":"https:\/\/www.vatland.no\/index.php\/keep-your-lync-public-certificates-up-to-date\/","url_meta":{"origin":645,"position":5},"title":"Keep Your Lync Public certificates up to date.","author":"Atle","date":"January 15, 2015","format":false,"excerpt":"Here is one reason why you should cleanup SAN's in your certificates.\u00a0Experienced\u00a0one scenario where a customer moved from one hosting provider to another and was unable to federate after the\u00a0move.\u00a0 This is not\u00a0about defining these hosting providers in the \"hosting provider\" configuration in Lync. The reason to do that\u00a0is if\u2026","rel":"","context":"In "Lync"","block_context":{"text":"Lync","link":"https:\/\/www.vatland.no\/index.php\/category\/lync\/"},"img":{"alt_text":"ssl-certificate","src":"https:\/\/i0.wp.com\/www.vatland.no\/wp-content\/uploads\/2015\/01\/ssl-certificate-300x300.jpg?resize=350%2C200","width":350,"height":200},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/posts\/645","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=645"}],"version-history":[{"count":1,"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/posts\/645\/revisions"}],"predecessor-version":[{"id":647,"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/posts\/645\/revisions\/647"}],"wp:attachment":[{"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/media?parent=645"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/categories?post=645"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/tags?post=645"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}