1. Question:
Previously, the integration of Lync Server 2013 with Exchange Server 2013 was normal, but once the public network certificate was replaced.
The problem is that UM doesn't work.
Sa,aa used to be normal, now not normal, only once replaced the public network certificate, Exchange Server 2013 and Lync Server 2013 have been replaced!
Pre-test, the replacement of the SA,AA is normal, the results found not normal.
Problem
650) this.width=650; "height=" 484 "title=" clip_image001 "style=" border:0px; "alt=" clip_image001 "src=" http:/ S3.51cto.com/wyfs02/m00/58/bf/wkiom1s68x3qsnogaaciehlwxpw867.jpg "border=" 0 "/>
650) this.width=650; "height=" 434 "title=" clip_image002 "style=" border:0px; "alt=" clip_image002 "src=" http:/ S3.51cto.com/wyfs02/m01/58/bf/wkiom1s68x7chninaadjyao049g168.jpg "border=" 0 "/>
650) this.width=650; "height=" 484 "title=" clip_image003 "style=" border:0px; "alt=" clip_image003 "src=" http:/ S3.51cto.com/wyfs02/m02/58/bf/wkiom1s68x7d0jseaacj2m3ela4943.jpg "border=" 0 "/>
650) this.width=650; "height=" 434 "title=" clip_image004 "style=" border:0px; "alt=" clip_image004 "src=" http:/ S3.51cto.com/wyfs02/m00/58/bf/wkiom1s68x-jmcimaadjhqhknvw939.jpg "border=" 0 "/>
2. Troubleshooting:
2.1. Um aa,sa Normal
2.2. Replace the public network certificate for Exchange Server 2013, replaced by the Exchange administrator
2.3. Replace the public network certificate for Lync Server 2013, replaced by the Lync Administrator
2.4. The AA,SA function of UM is not checked after the replacement, because the use of fewer people, and then, change certificates, distribution services, should be no problem
2.5. This use, a pull on the above problems
2.6. Check the Lync logs to see the following issues:
650) this.width=650; "height=" 449 "title=" clip_image005 "style=" border:0px; "alt=" clip_image005 "src=" http:/ S3.51cto.com/wyfs02/m01/58/bf/wkiom1s68x_sie7_aaiseslfbc8531.jpg "border=" 0 "/>
Attempts to route to servers in an Exchange UM DialPlan failed
No server in the DialPlan [UMDialPlan.contoso.com] accepted the call with ID [99189d47-6bc5-4aac-8cd8-46deb0e0d439].
Cause:dialplan is not configured properly.
Resolution:
Check the configuration of the DialPlan on Exchange UM Servers.
2.7. May be a UM certificate issue
650) this.width=650; "height=" 311 "title=" clip_image007 "style=" border:0px; "alt=" clip_image007 "src=" http:/ S3.51cto.com/wyfs02/m02/58/bf/wkiom1s68ycinm1laac92w0csby532.jpg "border=" 0 "/>
650) this.width=650; "height=" 276 "title=" clip_image009 "style=" border:0px; "alt=" clip_image009 "src=" http:/ S3.51cto.com/wyfs02/m00/58/bf/wkiom1s68ydzzipaaacc9zbvucg070.jpg "border=" 0 "/>
650) this.width=650; "height=" 469 "title=" clip_image011 "style=" border:0px; "alt=" clip_image011 "src=" http:/ S3.51cto.com/wyfs02/m01/58/bf/wkiom1s68ygb7ucsaae747kbgwk383.jpg "border=" 0 "/>
2.8. Call SA
650) this.width=650; "height=" 434 "title=" clip_image012 "style=" border:0px; "alt=" clip_image012 "src=" http:/ S3.51cto.com/wyfs02/m02/58/bf/wkiom1s68yktp8ylaad3i404w5i234.jpg "border=" 0 "/>
Normal
2.9. Call AA
650) this.width=650; "height=" 434 "title=" clip_image013 "style=" border:0px; "alt=" clip_image013 "src=" http:/ S3.51cto.com/wyfs02/m01/58/bf/wkiom1s68yksue6qaad6jwthww4536.jpg "border=" 0 "/>
Normal
3. Summary:
3.1. Lync Server 2013 Frontend is a private network certificate.
3.2. Exchange Server 2013 for UM with private network certificates, and other public network certificates.
3.3. Um does not have a problem, if UM also uses a public network certificate, there is a problem, such as errors in the above troubleshooting process.
This article is from the "it-standardization" blog, make sure to keep this source http://dynamic.blog.51cto.com/711418/1605233
Lync Tips -47-Error -44009-caused-certificate-planning-lync with UM