![]() ![]() Communicator tries a number of alternatives before failing which is why you can get away without SRV records but it is best to create them if you can. Autodiscovery will still work even without SRV records provided you have the relevant aliases (_ etc) setup as A records in DNS. Ideally you should also have DNS SRV records for the autodiscovery names ( these are _sipinternaltls._tcp.company, _sipinternal._, _sip._ and _sip._ ) that point to the Front End server so that the auto-discovery process will work properly. If Communicator is working at all then these are probably OK but worth checking. Your internal (and external if you want external access) DNS settings must have A records for all of the OCS services (SIP, web-conferencing, AV etc). I'd still recommend you take a good look at the Cert\DNS configuration in your environment as you really should be able to get users to simply install Communicator and have it "just work". Presence failures related to Outlook Integration can be resolved by this if the issues are simply a client side problem. You can find a brief outline of the steps you need to follow to get it all working here and there's some pretty OK simplified installation documentation at OCSPedia.Īs it stands it's also possible that your end users just need to apply the Communicator Roll-up Hotfix from KB969694. I've seen this sort of failure when not all of the SAN's were correctly set up on the certs and when the various DNS SRV records were incorrect. There are number of configuration areas where you will need to check that but pay particular attention to the certificate configuration. There's no reason why your users should not be able to log in using their e-mail account identity provided OCS has been configured correctly to use the SIP URI's and DNS is set up properly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |