SIP Service is temporaly unavailable
Windows Server Forum Index Windows Server
Server discussion on Windows platform.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web winserverhelp.com
SIP Service is temporaly unavailable

 
Post new topic   Reply to topic    Windows Server Forum Index -> Live Communications Server
Author Message
BJ Schubert
Guest





Posted: Sun Dec 19, 2004 11:07 pm    Post subject: SIP Service is temporaly unavailable Reply with quote

I have set up and installed LCS 2005, no matter what I do you cannot log in
with 5.0 or 5.1. the service is up and running, i followed the LCS2005 EE
instructions I have only 1 LCS server in the forest, the SQL is running as a
local machine instance on the LCS server. There are no errors in the log
files or event viewer. Everything shows that the Server is up and running.
All users are enabled, through the service account. I hve tried every way i
can think of on the Client with the FQDN, username and all log on options.
Any Ideas? This is a fresh install on this server.
Back to top
Bob Christian
Guest





Posted: Mon Dec 20, 2004 2:36 am    Post subject: Re: SIP Service is temporaly unavailable Reply with quote

BJ:

I have cut out parts of threads that I had posted for someone else. Please
see if it can help you. I should formulate it into a troubleshooting guide
when the time becomes available. Spare time is a rarity except when I am on
the plane...and that is usually spent catching up on sleep, if such a thing
is truly possible... =^)

Provided everything is working (you already noted this) the primary things
to ensure are:
1) Your forest supports the SIP domain that you are using
If your SMTP namespace and your domain namespace differ (ex. AD=
CompanyDomain.Forest.local SMTP=CompanyDomain.com)
2) The user is SIP-enabled in Active Directory Users & Computers
3) DNS is configured (at a minumum the server name and IP, the pool name
and IP)
4) The IM client is configured properly
As an aside: I have found that configuring certificates and running over
TLS seems to make things run a bit smoother. That, again, is after you get
things working first.

Thread below:
==============================================
CLIENT CONFIG:

I am assuming that you are inside your network and testing this first.
If you are outside, then you need to setup certificates and TLS...and that
is a whole other ballgame.

When you open Windows Messenger:
Select Tools...Options
Accounts Tab
Check My contacts include users of a SIP....
Sign-in name (SIP address)
Ex. Bob.Christian@company.com
Advanced...
Configure Settings
(even if you have your _SIP._TLS record set for your domain,
let's test this first)
(Server or IP address)
Ex LCSPool1.company.com or
LCSServer.company.com or
10.10.10.10 (Server IP)
Connect using:
TCP

When you try to sign in it should prompt you for your SIP Address
(sign-in name), Username and Password.
Your username is domain\username or usernam@domainname
(ex. Domain\Bob or bob@domain.local)
The domain should be your NetBIOS domain name or your
fully-qualified Active Directory Domain name. It may not necessarily
match your SMTP or SIP namespace.

==============================================
SIP DOMAIN FOREST CONFIG:
In LCS 2005, right-click on the forest name and select Properties.
Click on Add and add the emaildomain.com for your SMTP namespace if it is
not in there. You will probably see ADFQDN.local or whatever in there...but
the sip users are EmailAddress@company.com versus Username@company.local




"BJ Schubert" <BJ Schubert@discussions.microsoft.com> wrote in message
news:92634F30-3426-4333-8DC3-4E866AC9FF41@microsoft.com...
Quote:
I have set up and installed LCS 2005, no matter what I do you cannot log
in
with 5.0 or 5.1. the service is up and running, i followed the LCS2005 EE
instructions I have only 1 LCS server in the forest, the SQL is running as
a
local machine instance on the LCS server. There are no errors in the log
files or event viewer. Everything shows that the Server is up and running.
All users are enabled, through the service account. I hve tried every way
i
can think of on the Client with the FQDN, username and all log on options.
Any Ideas? This is a fresh install on this server.
Back to top
BJ Schubert
Guest





Posted: Mon Dec 20, 2004 3:19 am    Post subject: Re: SIP Service is temporaly unavailable Reply with quote

Thanks Bob! Adding the SMTP=companyname did it. I can now log on! But when
sending A message it comes back that it couldnt be delivered. Any thoughts
there?

"Bob Christian" wrote:

Quote:
BJ:

I have cut out parts of threads that I had posted for someone else. Please
see if it can help you. I should formulate it into a troubleshooting guide
when the time becomes available. Spare time is a rarity except when I am on
the plane...and that is usually spent catching up on sleep, if such a thing
is truly possible... =^)

Provided everything is working (you already noted this) the primary things
to ensure are:
1) Your forest supports the SIP domain that you are using
If your SMTP namespace and your domain namespace differ (ex. AD=
CompanyDomain.Forest.local SMTP=CompanyDomain.com)
2) The user is SIP-enabled in Active Directory Users & Computers
3) DNS is configured (at a minumum the server name and IP, the pool name
and IP)
4) The IM client is configured properly
As an aside: I have found that configuring certificates and running over
TLS seems to make things run a bit smoother. That, again, is after you get
things working first.

Thread below:
==============================================
CLIENT CONFIG:

I am assuming that you are inside your network and testing this first.
If you are outside, then you need to setup certificates and TLS...and that
is a whole other ballgame.

When you open Windows Messenger:
Select Tools...Options
Accounts Tab
Check My contacts include users of a SIP....
Sign-in name (SIP address)
Ex. Bob.Christian@company.com
Advanced...
Configure Settings
(even if you have your _SIP._TLS record set for your domain,
let's test this first)
(Server or IP address)
Ex LCSPool1.company.com or
LCSServer.company.com or
10.10.10.10 (Server IP)
Connect using:
TCP

When you try to sign in it should prompt you for your SIP Address
(sign-in name), Username and Password.
Your username is domain\username or usernam@domainname
(ex. Domain\Bob or bob@domain.local)
The domain should be your NetBIOS domain name or your
fully-qualified Active Directory Domain name. It may not necessarily
match your SMTP or SIP namespace.

==============================================
SIP DOMAIN FOREST CONFIG:
In LCS 2005, right-click on the forest name and select Properties.
Click on Add and add the emaildomain.com for your SMTP namespace if it is
not in there. You will probably see ADFQDN.local or whatever in there...but
the sip users are EmailAddress@company.com versus Username@company.local




"BJ Schubert" <BJ Schubert@discussions.microsoft.com> wrote in message
news:92634F30-3426-4333-8DC3-4E866AC9FF41@microsoft.com...
I have set up and installed LCS 2005, no matter what I do you cannot log
in
with 5.0 or 5.1. the service is up and running, i followed the LCS2005 EE
instructions I have only 1 LCS server in the forest, the SQL is running as
a
local machine instance on the LCS server. There are no errors in the log
files or event viewer. Everything shows that the Server is up and running.
All users are enabled, through the service account. I hve tried every way
i
can think of on the Client with the FQDN, username and all log on options.
Any Ideas? This is a fresh install on this server.


Back to top
Bob Christian
Guest





Posted: Mon Dec 20, 2004 9:09 am    Post subject: Re: SIP Service is temporaly unavailable Reply with quote

Tell me about your settings on the client. Are you running the client with
TLS or TCP? Are you connecting to the pool name or the server (DNS entry or
IP)?

What I would do is setup the pool name and IPs and make sure the clients are
pointing to the pool. If you have TLS configured, definitely use it. If
not, set the clients to TCP. Point them to the pool name rather than the
server name. Note: You want to check, if you have DNS scavenging enabled,
that you don't scavenge the Pool name out of DNS.
DNS Example:
Pool 10.10.100.50
Server1 10.10.100.50

Out of sheer curiosity...why go through the licensing expense of running a
single-node EE rather than the LCS 2005 Standard Edition. (Granted, you may
need SQL from IM Archiving...and plan on standing up another EE server for
load-balancing purposes). You won't need load balancing for a single server
and a single IP attached to the pool.

Bob

"BJ Schubert" <BJSchubert@discussions.microsoft.com> wrote in message
news:76CFB5C9-5EC3-4452-95A2-C828DF14B6D9@microsoft.com...
Quote:
Thanks Bob! Adding the SMTP=companyname did it. I can now log on! But when
sending A message it comes back that it couldnt be delivered. Any thoughts
there?

"Bob Christian" wrote:

BJ:

I have cut out parts of threads that I had posted for someone else.
Please
see if it can help you. I should formulate it into a troubleshooting
guide
when the time becomes available. Spare time is a rarity except when I
am on
the plane...and that is usually spent catching up on sleep, if such a
thing
is truly possible... =^)

Provided everything is working (you already noted this) the primary
things
to ensure are:
1) Your forest supports the SIP domain that you are using
If your SMTP namespace and your domain namespace differ (ex. AD=
CompanyDomain.Forest.local SMTP=CompanyDomain.com)
2) The user is SIP-enabled in Active Directory Users & Computers
3) DNS is configured (at a minumum the server name and IP, the pool
name
and IP)
4) The IM client is configured properly
As an aside: I have found that configuring certificates and running
over
TLS seems to make things run a bit smoother. That, again, is after you
get
things working first.

Thread below:
==============================================
CLIENT CONFIG:

I am assuming that you are inside your network and testing this first.
If you are outside, then you need to setup certificates and TLS...and
that
is a whole other ballgame.

When you open Windows Messenger:
Select Tools...Options
Accounts Tab
Check My contacts include users of a SIP....
Sign-in name (SIP address)
Ex. Bob.Christian@company.com
Advanced...
Configure Settings
(even if you have your _SIP._TLS record set for your domain,
let's test this first)
(Server or IP address)
Ex LCSPool1.company.com or
LCSServer.company.com or
10.10.10.10 (Server IP)
Connect using:
TCP

When you try to sign in it should prompt you for your SIP Address
(sign-in name), Username and Password.
Your username is domain\username or usernam@domainname
(ex. Domain\Bob or bob@domain.local)
The domain should be your NetBIOS domain name or your
fully-qualified Active Directory Domain name. It may not necessarily
match your SMTP or SIP namespace.

==============================================
SIP DOMAIN FOREST CONFIG:
In LCS 2005, right-click on the forest name and select Properties.
Click on Add and add the emaildomain.com for your SMTP namespace if it
is
not in there. You will probably see ADFQDN.local or whatever in
there...but
the sip users are EmailAddress@company.com versus Username@company.local




"BJ Schubert" <BJ Schubert@discussions.microsoft.com> wrote in message
news:92634F30-3426-4333-8DC3-4E866AC9FF41@microsoft.com...
I have set up and installed LCS 2005, no matter what I do you cannot
log
in
with 5.0 or 5.1. the service is up and running, i followed the LCS2005
EE
instructions I have only 1 LCS server in the forest, the SQL is
running as
a
local machine instance on the LCS server. There are no errors in the
log
files or event viewer. Everything shows that the Server is up and
running.
All users are enabled, through the service account. I hve tried every
way
i
can think of on the Client with the FQDN, username and all log on
options.
Any Ideas? This is a fresh install on this server.


Back to top
 
Post new topic   Reply to topic    Windows Server Forum Index -> Live Communications Server All times are GMT
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




New Topics Powered by phpBB