How to configure autoconfig for Communicator
Steven
can't seem to get it to work. I have setup the following DNS records:
_sipinternal._tcp.domain.com
priority=0
weight=0
port=5060
svr hostname = A record of LCS 2005 stnd server
_sipinternaltls._tcp.domain.com
priority=0
weight=0
port=5061
svr hostname = A record of LCS 2005 stnd server
_sip._tcp.domain.com
priority=0
weight=0
port=5060
svr hostname = A record of LCS 2005 stnd server
_sip._tls.domain.com
priority=0
weight=0
port=5061
svr hostname = A record of LCS 2005 stnd server
Manually setting up the configuration works fine but I can't for the life of
my get the autoconfiguration to work. I have run some network captures of
the logon process of Office Communicator and the name resolution is working.
Any suggestions on what I am missing to allow for autoconfiguration?
Best regards,
Steven
Jeremy Buch
details. If your domain.com SRV record points to a server that isn't of the
form <host>.domain.com - if it isn't, then the client won't connect to it.
--
Jeremy Buch (Microsoft)
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email to this address, post a reply to this newsgroup.
"Steven" <spre...@qualcomm.com> wrote in message
news:euIjV$O1FHA...@TK2MSFTNGP10.phx.gbl...
Steven
(in this case nalcs01.im.company.com).
"Jeremy Buch" <jb...@online.microsoft.com> wrote in message
news:%23wFs7LQ...@TK2MSFTNGP09.phx.gbl...
Jeremy Buch
needs to be nalcs01.company.com NOT nalcs01.im.company.com - or the SRV
record (and SIP URIs) need to be of the form im.company.com.
Hopefully this helps clarify the problem. Your URIs, SRV domains and
hostnames all need to match up with exact matches:
URI: jb...@microsoft.com
SRV: _sip._tls.microsoft.com, _sipinternaltls.microsoft.com and
_sipinternal._tcp.microsoft.com
valid hostnames: server1.microsoft.com, server6.microsoft.com,
sip.microsoft.com
invalid hostnames: server1.im.microsoft.com, sip.eng.uk.microsoft.com,
sip.other.com
I would suggest that you determine whether it is easier to change the user
URIs to @im.company.com, or whether it is easier to publish DNS hostnames
for the company.com space.
--
Jeremy Buch (Microsoft)
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email to this address, post a reply to this newsgroup.
"Steven" <spre...@qualcomm.com> wrote in message
news:O4aUVbQ1...@TK2MSFTNGP14.phx.gbl...
Steven
then the following would work:
SRV records:
_sip._tls.qtalk.company.com
_sipinternaltls._tcp.qtalk.company.com
_sip._tcp.qtalk.company.com
_sipinternal._tcp.qtalk.company.com
That point to:
servername.qtalk.company.com
?
"Jeremy Buch" <jb...@online.microsoft.com> wrote in message
news:%23V%23dXsQ1...@TK2MSFTNGP12.phx.gbl...
Jeremy Buch
The domain portion of the URI must map directly across SRV and the hostname
as the full 'domain/subdomain-portion' of the hostname.
[Read only only if it won't be confusing - I'm going to talk about more
complex autoconfig scenarios here for outside/inside users and TCP/TLS
differences]
Keep in mind that if you are using TCP, this is where it ends - so the
actual FQDN of the LCS box could be something different. For TLS, however,
the certificate needs to match the perceived hostname during autoconfig, so
if the host is in a domain that prevents its name from matching, you just
need to use TCP or publish a different client port via SRV (like 443) that
you can put a client-only certificate on (for internal servers). For APs,
the 'domain' of the server doesn't matter as the AP will take its name from
the certificate installed (since it isn't tied to the FQDN stored in the AD
like internal servers are).
--
Jeremy Buch (Microsoft)
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email to this address, post a reply to this newsgroup.
"Steven" <spre...@qualcomm.com> wrote in message
news:OAbn%234Q1F...@tk2msftngp13.phx.gbl...