Connecting Via proxy ".. becos the service is temporarily un
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
Connecting Via proxy ".. becos the service is temporarily un

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





Posted: Wed Dec 22, 2004 8:37 pm    Post subject: Connecting Via proxy ".. becos the service is temporarily un Reply with quote

Hai,
I couldnt connect to LCS machine via proxy in Windows messenger. This is my
error log.

*******************
19:27:49.305 804:840 INFO :: Sending Packet - 10.1.8.7:80 (From Local
Address: 10.1.8.124:2161):
19:27:49.305 804:840 INFO :: REGISTER sip:sip.triad-india.net SIP/2.0Via:
SIP/2.0/TLS 10.1.8.124:2161Max-Forwards: 70From:
<sip:ajayc@sip.triad-india.net>;tag=4100cf0b50a84547806ca35b35dc22ad;epid=972bfd0b1dTo:
<sip:ajayc@sip.triad-india.net>Call-ID:
875a900b9a434680b4c154bb25459f88@10.1.8.124CSeq: 1 REGISTERContact:
<sip:10.1.8.124:2161;transport=tls>;methods="INVITE, MESSAGE, INFO,
SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK, REFER";proxy=replaceUser-Agent:
RTC/1.2.4949 (Messenger 5.0.0482)Supported:
com.microsoft.msrtc.presenceEvent: registrationAllow-Events:
presenceContent-Length: 0
19:27:49.305 804:840 INFO :: End of Sending Packet - 10.1.8.7:80 (From
Local Address: 10.1.8.124:2161)
19:27:49.305 804:840 TRACE :: - encrypted buffer length: 615 bytes. First 8
bytes:
19:27:49.305 804:840 TRACE :: 17 03 01 02 62 43 17 6B :....bC.k
19:27:49.515 804:840 TRACE :: SECURE_SOCKET: decrypting buffer size: 170
(first 8):
19:27:49.515 804:840 TRACE :: 17 03 01 00 A5 3E CE 7D :....Â¥>ÃŽ}
19:27:49.515 804:840 WARN :: Failed to parse SIP message StartOfMsg: 0
BytesReceived: 149 BytesParsed: 0 hr: 0x80004005
19:27:49.515 804:840 TRACE :: 48 54 54 50 2F 31 2E 31 20 34 30 30 20 42 61
64 :HTTP/1.1 400 Bad
19:27:49.515 804:840 TRACE :: 20 52 65 71 75 65 73 74 0D 0A 43 6F 6E 74 65
6E : Request..Conten
19:27:49.515 804:840 TRACE :: 74 2D 54 79 70 65 3A 20 74 65 78 74 2F 68 74
6D :t-Type: text/htm
19:27:49.515 804:840 TRACE :: 6C 0D 0A 44 61 74 65 3A 20 57 65 64 2C 20 32
32 :l..Date: Wed, 22
19:27:49.515 804:840 TRACE :: 20 44 65 63 20 32 30 30 34 20 31 33 3A 35 36
3A : Dec 2004 13:56:
19:27:49.515 804:840 TRACE :: 33 30 20 47 4D 54 0D 0A 43 6F 6E 6E 65 63 74
69 :30 GMT..Connecti
19:27:49.515 804:840 TRACE :: 6F 6E 3A 20 63 6C 6F 73 65 0D 0A 43 6F 6E 74
65 :on: close..Conte
19:27:49.515 804:840 TRACE :: 6E 74 2D 4C 65 6E 67 74 68 3A 20 32 30 0D 0A
0D :nt-Length: 20...
19:27:49.515 804:840 TRACE :: 0A 3C 68 31 3E 42 61 64 20 52 65 71 75 65 73
74 :.<h1>Bad Request
19:27:49.515 804:840 TRACE :: 3C 2F 68 31 3E :</h1>
19:27:49.515 804:840 INFO :: CRTCProfile::SetState - [011957E0]
enState:1->5, statusCode=80072746, text=(null)
19:27:49.515 804:840 INFO :: RegistrationStateChangeEvent-
profile=011957E0, state=5, statusCode=80072746, text=(null)
19:27:49.515 804:840 INFO :: CRTCProfile::SetState - register error, clear
postponed watchers
19:27:49.525 804:840 INFO :: CRTCClient::InternalEnableProfileEx -
pProfile=011957E0, regFlag=0x0, roamingFlag=0x0, realm=<(null)>
19:27:49.525 804:840 INFO :: RoamingSession::SetDeltaNum[01195890],0->0
19:27:49.525 804:840 INFO :: RoamingSession::SetDeltaNum[011958D4],0->0
19:27:49.525 804:840 INFO :: RoamingSession::SetDeltaNum[01195930],0->0
19:27:49.525 804:840 INFO :: RoamingSession::SetDeltaNum[01195948],0->0
19:27:49.525 804:840 INFO :: RoamingSession::SetDeltaNum[01195918],0->0
19:27:49.525 804:840 INFO :: SetRoamingStatus - roamingFlag:old(0)|=flag(0)
--> new(0), statusCode=0
19:27:49.525 804:840 INFO :: RoamingSession::SetDeltaNum[01195948],0->0



*******************

regards
R.Raja
Back to top
TomL LCS Kid
Guest





Posted: Tue Dec 28, 2004 3:57 am    Post subject: RE: Connecting Via proxy ".. becos the service is temporaril Reply with quote

Raja,

Can you provide more details for the configuration?
Does this work if the alias does not contain a hyphen in the alias
try
ajay@sip.triagindia.net instead of ajay@sip.triag-india.net. You need to
make sure you change the user's sip alias and also the server's domain list.

Can you test this with Windows Messenger 5.1?

Tom

"Raja" wrote:

Quote:
Hai,
I couldnt connect to LCS machine via proxy in Windows messenger. This is my
error log.

*******************
19:27:49.305 804:840 INFO :: Sending Packet - 10.1.8.7:80 (From Local
Address: 10.1.8.124:2161):
19:27:49.305 804:840 INFO :: REGISTER sip:sip.triad-india.net SIP/2.0Via:
SIP/2.0/TLS 10.1.8.124:2161Max-Forwards: 70From:
sip:ajayc@sip.triad-india.net>;tag=4100cf0b50a84547806ca35b35dc22ad;epid=972bfd0b1dTo:
sip:ajayc@sip.triad-india.net>Call-ID:
875a900b9a434680b4c154bb25459f88@10.1.8.124CSeq: 1 REGISTERContact:
sip:10.1.8.124:2161;transport=tls>;methods="INVITE, MESSAGE, INFO,
SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK, REFER";proxy=replaceUser-Agent:
RTC/1.2.4949 (Messenger 5.0.0482)Supported:
com.microsoft.msrtc.presenceEvent: registrationAllow-Events:
presenceContent-Length: 0
19:27:49.305 804:840 INFO :: End of Sending Packet - 10.1.8.7:80 (From
Local Address: 10.1.8.124:2161)
19:27:49.305 804:840 TRACE :: - encrypted buffer length: 615 bytes. First 8
bytes:
19:27:49.305 804:840 TRACE :: 17 03 01 02 62 43 17 6B :....bC.k
19:27:49.515 804:840 TRACE :: SECURE_SOCKET: decrypting buffer size: 170
(first 8):
19:27:49.515 804:840 TRACE :: 17 03 01 00 A5 3E CE 7D :....Â¥>ÃŽ}
19:27:49.515 804:840 WARN :: Failed to parse SIP message StartOfMsg: 0
BytesReceived: 149 BytesParsed: 0 hr: 0x80004005
19:27:49.515 804:840 TRACE :: 48 54 54 50 2F 31 2E 31 20 34 30 30 20 42 61
64 :HTTP/1.1 400 Bad
19:27:49.515 804:840 TRACE :: 20 52 65 71 75 65 73 74 0D 0A 43 6F 6E 74 65
6E : Request..Conten
19:27:49.515 804:840 TRACE :: 74 2D 54 79 70 65 3A 20 74 65 78 74 2F 68 74
6D :t-Type: text/htm
19:27:49.515 804:840 TRACE :: 6C 0D 0A 44 61 74 65 3A 20 57 65 64 2C 20 32
32 :l..Date: Wed, 22
19:27:49.515 804:840 TRACE :: 20 44 65 63 20 32 30 30 34 20 31 33 3A 35 36
3A : Dec 2004 13:56:
19:27:49.515 804:840 TRACE :: 33 30 20 47 4D 54 0D 0A 43 6F 6E 6E 65 63 74
69 :30 GMT..Connecti
19:27:49.515 804:840 TRACE :: 6F 6E 3A 20 63 6C 6F 73 65 0D 0A 43 6F 6E 74
65 :on: close..Conte
19:27:49.515 804:840 TRACE :: 6E 74 2D 4C 65 6E 67 74 68 3A 20 32 30 0D 0A
0D :nt-Length: 20...
19:27:49.515 804:840 TRACE :: 0A 3C 68 31 3E 42 61 64 20 52 65 71 75 65 73
74 :.<h1>Bad Request
19:27:49.515 804:840 TRACE :: 3C 2F 68 31 3E :</h1
19:27:49.515 804:840 INFO :: CRTCProfile::SetState - [011957E0]
enState:1->5, statusCode=80072746, text=(null)
19:27:49.515 804:840 INFO :: RegistrationStateChangeEvent-
profile=011957E0, state=5, statusCode=80072746, text=(null)
19:27:49.515 804:840 INFO :: CRTCProfile::SetState - register error, clear
postponed watchers
19:27:49.525 804:840 INFO :: CRTCClient::InternalEnableProfileEx -
pProfile=011957E0, regFlag=0x0, roamingFlag=0x0, realm=<(null)
19:27:49.525 804:840 INFO :: RoamingSession::SetDeltaNum[01195890],0->0
19:27:49.525 804:840 INFO :: RoamingSession::SetDeltaNum[011958D4],0->0
19:27:49.525 804:840 INFO :: RoamingSession::SetDeltaNum[01195930],0->0
19:27:49.525 804:840 INFO :: RoamingSession::SetDeltaNum[01195948],0->0
19:27:49.525 804:840 INFO :: RoamingSession::SetDeltaNum[01195918],0->0
19:27:49.525 804:840 INFO :: SetRoamingStatus - roamingFlag:old(0)|=flag(0)
--> new(0), statusCode=0
19:27:49.525 804:840 INFO :: RoamingSession::SetDeltaNum[01195948],0->0



*******************

regards
R.Raja


Back to top
Raja
Guest





Posted: Wed Dec 29, 2004 4:59 pm    Post subject: RE: Connecting Via proxy ".. becos the service is temporaril Reply with quote

Tom,
The alias name should match FQDN isnt it ? I have a Fully qualified domain
name [triag-india.net]. If i need to change it to triagindia.net then i need
to get a domain isnt it.

This is how i made my configuration
Server :
1. Has a FQDN.
2. Has a certificate authority
3. LCS and Active Directory installed and configured to use TLS [Single
forest and only one domain].

Client :
Two types of client. All are outside clients
1. Client that connect to the internet directly
Note : I dont have any problem with this client. Iam able to
connect to LCS server through Windows Messenger.

2. Client that connect to the internet via Winproxy software
Note : Only here i have a problem. I have a Server which is
directly connected to Internet . I have winproxy software in this software.
From my client node, i said for proxy configuration "HttpProxy" and gave the
Proxy server IP ( proxy means Winproxy machine). Iam able to see from the
Winproxy Log that the client is connecting to https://sip.mydomain.com:443.
After some time i got the above error message in the client. I have also
tried the configuration ( Socks 4 ,5 ). But Iam able to log on to .net
messenger service with the same configuration. Iam able to access https site
hosted in this server.

Iam using Windows Messenger 5.1

regards
R.Raja



"TomL LCS Kid" wrote:

Quote:
Raja,

Can you provide more details for the configuration?
Does this work if the alias does not contain a hyphen in the alias
try
ajay@sip.triagindia.net instead of ajay@sip.triag-india.net. You need to
make sure you change the user's sip alias and also the server's domain list.

Can you test this with Windows Messenger 5.1?

Tom

"Raja" wrote:

Hai,
I couldnt connect to LCS machine via proxy in Windows messenger. This is my
error log.

*******************
19:27:49.305 804:840 INFO :: Sending Packet - 10.1.8.7:80 (From Local
Address: 10.1.8.124:2161):
19:27:49.305 804:840 INFO :: REGISTER sip:sip.triad-india.net SIP/2.0Via:
SIP/2.0/TLS 10.1.8.124:2161Max-Forwards: 70From:
sip:ajayc@sip.triad-india.net>;tag=4100cf0b50a84547806ca35b35dc22ad;epid=972bfd0b1dTo:
sip:ajayc@sip.triad-india.net>Call-ID:
875a900b9a434680b4c154bb25459f88@10.1.8.124CSeq: 1 REGISTERContact:
sip:10.1.8.124:2161;transport=tls>;methods="INVITE, MESSAGE, INFO,
SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK, REFER";proxy=replaceUser-Agent:
RTC/1.2.4949 (Messenger 5.0.0482)Supported:
com.microsoft.msrtc.presenceEvent: registrationAllow-Events:
presenceContent-Length: 0
19:27:49.305 804:840 INFO :: End of Sending Packet - 10.1.8.7:80 (From
Local Address: 10.1.8.124:2161)
19:27:49.305 804:840 TRACE :: - encrypted buffer length: 615 bytes. First 8
bytes:
19:27:49.305 804:840 TRACE :: 17 03 01 02 62 43 17 6B :....bC.k
19:27:49.515 804:840 TRACE :: SECURE_SOCKET: decrypting buffer size: 170
(first 8):
19:27:49.515 804:840 TRACE :: 17 03 01 00 A5 3E CE 7D :....Â¥>ÃŽ}
19:27:49.515 804:840 WARN :: Failed to parse SIP message StartOfMsg: 0
BytesReceived: 149 BytesParsed: 0 hr: 0x80004005
19:27:49.515 804:840 TRACE :: 48 54 54 50 2F 31 2E 31 20 34 30 30 20 42 61
64 :HTTP/1.1 400 Bad
19:27:49.515 804:840 TRACE :: 20 52 65 71 75 65 73 74 0D 0A 43 6F 6E 74 65
6E : Request..Conten
19:27:49.515 804:840 TRACE :: 74 2D 54 79 70 65 3A 20 74 65 78 74 2F 68 74
6D :t-Type: text/htm
19:27:49.515 804:840 TRACE :: 6C 0D 0A 44 61 74 65 3A 20 57 65 64 2C 20 32
32 :l..Date: Wed, 22
19:27:49.515 804:840 TRACE :: 20 44 65 63 20 32 30 30 34 20 31 33 3A 35 36
3A : Dec 2004 13:56:
19:27:49.515 804:840 TRACE :: 33 30 20 47 4D 54 0D 0A 43 6F 6E 6E 65 63 74
69 :30 GMT..Connecti
19:27:49.515 804:840 TRACE :: 6F 6E 3A 20 63 6C 6F 73 65 0D 0A 43 6F 6E 74
65 :on: close..Conte
19:27:49.515 804:840 TRACE :: 6E 74 2D 4C 65 6E 67 74 68 3A 20 32 30 0D 0A
0D :nt-Length: 20...
19:27:49.515 804:840 TRACE :: 0A 3C 68 31 3E 42 61 64 20 52 65 71 75 65 73
74 :.<h1>Bad Request
19:27:49.515 804:840 TRACE :: 3C 2F 68 31 3E :</h1
19:27:49.515 804:840 INFO :: CRTCProfile::SetState - [011957E0]
enState:1->5, statusCode=80072746, text=(null)
19:27:49.515 804:840 INFO :: RegistrationStateChangeEvent-
profile=011957E0, state=5, statusCode=80072746, text=(null)
19:27:49.515 804:840 INFO :: CRTCProfile::SetState - register error, clear
postponed watchers
19:27:49.525 804:840 INFO :: CRTCClient::InternalEnableProfileEx -
pProfile=011957E0, regFlag=0x0, roamingFlag=0x0, realm=<(null)
19:27:49.525 804:840 INFO :: RoamingSession::SetDeltaNum[01195890],0->0
19:27:49.525 804:840 INFO :: RoamingSession::SetDeltaNum[011958D4],0->0
19:27:49.525 804:840 INFO :: RoamingSession::SetDeltaNum[01195930],0->0
19:27:49.525 804:840 INFO :: RoamingSession::SetDeltaNum[01195948],0->0
19:27:49.525 804:840 INFO :: RoamingSession::SetDeltaNum[01195918],0->0
19:27:49.525 804:840 INFO :: SetRoamingStatus - roamingFlag:old(0)|=flag(0)
--> new(0), statusCode=0
19:27:49.525 804:840 INFO :: RoamingSession::SetDeltaNum[01195948],0->0



*******************

regards
R.Raja


Back to top
Tom Laciano
Guest





Posted: Wed Dec 29, 2004 8:26 pm    Post subject: Re: Connecting Via proxy ".. becos the service is temporaril Reply with quote

Raja,

The sip-uri does not need to match your dns or domain naming environment
(there is an impact for Autoconfiguration but it can be done). I can test
dashes in names on my system so I won't ask you to change that unless I find
something. Also you say it works in one configuration so the dash would not
seem relevant.

The HTTPProxy behavior - it is my understanding that the proxy settings in
the Windows Messenger client is only used for the .NET client connection. As
to Windows Messenger behind a proxy, I have not tested that. It will take a
while for me to build a setup.

Is it possible that you could send an RTCDLL log file from the working and
nonworking clients? I would appreciate actual log files versus pasted text.
(I can give email account if needed)

TomL LCS Kid


"Raja" <Raja@discussions.microsoft.com> wrote in message
news:813FAC56-7B85-491D-AA9C-69D5350D6BD7@microsoft.com...
Quote:
Tom,
The alias name should match FQDN isnt it ? I have a Fully qualified domain
name [triag-india.net]. If i need to change it to triagindia.net then i
need
to get a domain isnt it.

This is how i made my configuration
Server :
1. Has a FQDN.
2. Has a certificate authority
3. LCS and Active Directory installed and configured to use TLS [Single
forest and only one domain].

Client :
Two types of client. All are outside clients
1. Client that connect to the internet directly
Note : I dont have any problem with this client. Iam able to
connect to LCS server through Windows Messenger.

2. Client that connect to the internet via Winproxy software
Note : Only here i have a problem. I have a Server which is
directly connected to Internet . I have winproxy software in this
software.
From my client node, i said for proxy configuration "HttpProxy" and gave
the
Proxy server IP ( proxy means Winproxy machine). Iam able to see from the
Winproxy Log that the client is connecting to
https://sip.mydomain.com:443.
After some time i got the above error message in the client. I have also
tried the configuration ( Socks 4 ,5 ). But Iam able to log on to .net
messenger service with the same configuration. Iam able to access https
site
hosted in this server.

Iam using Windows Messenger 5.1

regards
R.Raja



"TomL LCS Kid" wrote:

Raja,

Can you provide more details for the configuration?
Does this work if the alias does not contain a hyphen in the alias
try
ajay@sip.triagindia.net instead of ajay@sip.triag-india.net. You need to
make sure you change the user's sip alias and also the server's domain
list.

Can you test this with Windows Messenger 5.1?

Tom

"Raja" wrote:

Hai,
I couldnt connect to LCS machine via proxy in Windows messenger. This
is my
error log.

*******************
19:27:49.305 804:840 INFO :: Sending Packet - 10.1.8.7:80 (From Local
Address: 10.1.8.124:2161):
19:27:49.305 804:840 INFO :: REGISTER sip:sip.triad-india.net
SIP/2.0Via:
SIP/2.0/TLS 10.1.8.124:2161Max-Forwards: 70From:
sip:ajayc@sip.triad-india.net>;tag=4100cf0b50a84547806ca35b35dc22ad;epid=972bfd0b1dTo:
sip:ajayc@sip.triad-india.net>Call-ID:
875a900b9a434680b4c154bb25459f88@10.1.8.124CSeq: 1 REGISTERContact:
sip:10.1.8.124:2161;transport=tls>;methods="INVITE, MESSAGE, INFO,
SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK,
REFER";proxy=replaceUser-Agent:
RTC/1.2.4949 (Messenger 5.0.0482)Supported:
com.microsoft.msrtc.presenceEvent: registrationAllow-Events:
presenceContent-Length: 0
19:27:49.305 804:840 INFO :: End of Sending Packet - 10.1.8.7:80 (From
Local Address: 10.1.8.124:2161)
19:27:49.305 804:840 TRACE :: - encrypted buffer length: 615 bytes.
First 8
bytes:
19:27:49.305 804:840 TRACE :: 17 03 01 02 62 43 17 6B :....bC.k
19:27:49.515 804:840 TRACE :: SECURE_SOCKET: decrypting buffer size:
170
(first 8):
19:27:49.515 804:840 TRACE :: 17 03 01 00 A5 3E CE 7D :....¥>Î}
19:27:49.515 804:840 WARN :: Failed to parse SIP message StartOfMsg: 0
BytesReceived: 149 BytesParsed: 0 hr: 0x80004005
19:27:49.515 804:840 TRACE :: 48 54 54 50 2F 31 2E 31 20 34 30 30 20 42
61
64 :HTTP/1.1 400 Bad
19:27:49.515 804:840 TRACE :: 20 52 65 71 75 65 73 74 0D 0A 43 6F 6E 74
65
6E : Request..Conten
19:27:49.515 804:840 TRACE :: 74 2D 54 79 70 65 3A 20 74 65 78 74 2F 68
74
6D :t-Type: text/htm
19:27:49.515 804:840 TRACE :: 6C 0D 0A 44 61 74 65 3A 20 57 65 64 2C 20
32
32 :l..Date: Wed, 22
19:27:49.515 804:840 TRACE :: 20 44 65 63 20 32 30 30 34 20 31 33 3A 35
36
3A : Dec 2004 13:56:
19:27:49.515 804:840 TRACE :: 33 30 20 47 4D 54 0D 0A 43 6F 6E 6E 65 63
74
69 :30 GMT..Connecti
19:27:49.515 804:840 TRACE :: 6F 6E 3A 20 63 6C 6F 73 65 0D 0A 43 6F 6E
74
65 :on: close..Conte
19:27:49.515 804:840 TRACE :: 6E 74 2D 4C 65 6E 67 74 68 3A 20 32 30 0D
0A
0D :nt-Length: 20...
19:27:49.515 804:840 TRACE :: 0A 3C 68 31 3E 42 61 64 20 52 65 71 75 65
73
74 :.<h1>Bad Request
19:27:49.515 804:840 TRACE :: 3C 2F 68 31 3E :</h1
19:27:49.515 804:840 INFO :: CRTCProfile::SetState - [011957E0]
enState:1->5, statusCode=80072746, text=(null)
19:27:49.515 804:840 INFO :: RegistrationStateChangeEvent-
profile=011957E0, state=5, statusCode=80072746, text=(null)
19:27:49.515 804:840 INFO :: CRTCProfile::SetState - register error,
clear
postponed watchers
19:27:49.525 804:840 INFO :: CRTCClient::InternalEnableProfileEx -
pProfile=011957E0, regFlag=0x0, roamingFlag=0x0, realm=<(null)
19:27:49.525 804:840 INFO ::
RoamingSession::SetDeltaNum[01195890],0->0
19:27:49.525 804:840 INFO ::
RoamingSession::SetDeltaNum[011958D4],0->0
19:27:49.525 804:840 INFO ::
RoamingSession::SetDeltaNum[01195930],0->0
19:27:49.525 804:840 INFO ::
RoamingSession::SetDeltaNum[01195948],0->0
19:27:49.525 804:840 INFO ::
RoamingSession::SetDeltaNum[01195918],0->0
19:27:49.525 804:840 INFO :: SetRoamingStatus -
roamingFlag:old(0)|=flag(0)
--> new(0), statusCode=0
19:27:49.525 804:840 INFO ::
RoamingSession::SetDeltaNum[01195948],0->0



*******************

regards
R.Raja


Back to top
Raja
Guest





Posted: Tue Jan 04, 2005 7:27 pm    Post subject: Re: Connecting Via proxy ".. becos the service is temporaril Reply with quote

Hai,
Happy New Year . I was in away for few days. Can you give me your email id
so that i can send you the actual log files.

regards
R.Raja

"Tom Laciano <MSFT>" wrote:

Quote:
Raja,

The sip-uri does not need to match your dns or domain naming environment
(there is an impact for Autoconfiguration but it can be done). I can test
dashes in names on my system so I won't ask you to change that unless I find
something. Also you say it works in one configuration so the dash would not
seem relevant.

The HTTPProxy behavior - it is my understanding that the proxy settings in
the Windows Messenger client is only used for the .NET client connection. As
to Windows Messenger behind a proxy, I have not tested that. It will take a
while for me to build a setup.

Is it possible that you could send an RTCDLL log file from the working and
nonworking clients? I would appreciate actual log files versus pasted text.
(I can give email account if needed)

TomL LCS Kid


"Raja" <Raja@discussions.microsoft.com> wrote in message
news:813FAC56-7B85-491D-AA9C-69D5350D6BD7@microsoft.com...
Tom,
The alias name should match FQDN isnt it ? I have a Fully qualified domain
name [triag-india.net]. If i need to change it to triagindia.net then i
need
to get a domain isnt it.

This is how i made my configuration
Server :
1. Has a FQDN.
2. Has a certificate authority
3. LCS and Active Directory installed and configured to use TLS [Single
forest and only one domain].

Client :
Two types of client. All are outside clients
1. Client that connect to the internet directly
Note : I dont have any problem with this client. Iam able to
connect to LCS server through Windows Messenger.

2. Client that connect to the internet via Winproxy software
Note : Only here i have a problem. I have a Server which is
directly connected to Internet . I have winproxy software in this
software.
From my client node, i said for proxy configuration "HttpProxy" and gave
the
Proxy server IP ( proxy means Winproxy machine). Iam able to see from the
Winproxy Log that the client is connecting to
https://sip.mydomain.com:443.
After some time i got the above error message in the client. I have also
tried the configuration ( Socks 4 ,5 ). But Iam able to log on to .net
messenger service with the same configuration. Iam able to access https
site
hosted in this server.

Iam using Windows Messenger 5.1

regards
R.Raja



"TomL LCS Kid" wrote:

Raja,

Can you provide more details for the configuration?
Does this work if the alias does not contain a hyphen in the alias
try
ajay@sip.triagindia.net instead of ajay@sip.triag-india.net. You need to
make sure you change the user's sip alias and also the server's domain
list.

Can you test this with Windows Messenger 5.1?

Tom

"Raja" wrote:

Hai,
I couldnt connect to LCS machine via proxy in Windows messenger. This
is my
error log.

*******************
19:27:49.305 804:840 INFO :: Sending Packet - 10.1.8.7:80 (From Local
Address: 10.1.8.124:2161):
19:27:49.305 804:840 INFO :: REGISTER sip:sip.triad-india.net
SIP/2.0Via:
SIP/2.0/TLS 10.1.8.124:2161Max-Forwards: 70From:
sip:ajayc@sip.triad-india.net>;tag=4100cf0b50a84547806ca35b35dc22ad;epid=972bfd0b1dTo:
sip:ajayc@sip.triad-india.net>Call-ID:
875a900b9a434680b4c154bb25459f88@10.1.8.124CSeq: 1 REGISTERContact:
sip:10.1.8.124:2161;transport=tls>;methods="INVITE, MESSAGE, INFO,
SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK,
REFER";proxy=replaceUser-Agent:
RTC/1.2.4949 (Messenger 5.0.0482)Supported:
com.microsoft.msrtc.presenceEvent: registrationAllow-Events:
presenceContent-Length: 0
19:27:49.305 804:840 INFO :: End of Sending Packet - 10.1.8.7:80 (From
Local Address: 10.1.8.124:2161)
19:27:49.305 804:840 TRACE :: - encrypted buffer length: 615 bytes.
First 8
bytes:
19:27:49.305 804:840 TRACE :: 17 03 01 02 62 43 17 6B :....bC.k
19:27:49.515 804:840 TRACE :: SECURE_SOCKET: decrypting buffer size:
170
(first 8):
19:27:49.515 804:840 TRACE :: 17 03 01 00 A5 3E CE 7D :....Â¥>ÃŽ}
19:27:49.515 804:840 WARN :: Failed to parse SIP message StartOfMsg: 0
BytesReceived: 149 BytesParsed: 0 hr: 0x80004005
19:27:49.515 804:840 TRACE :: 48 54 54 50 2F 31 2E 31 20 34 30 30 20 42
61
64 :HTTP/1.1 400 Bad
19:27:49.515 804:840 TRACE :: 20 52 65 71 75 65 73 74 0D 0A 43 6F 6E 74
65
6E : Request..Conten
19:27:49.515 804:840 TRACE :: 74 2D 54 79 70 65 3A 20 74 65 78 74 2F 68
74
6D :t-Type: text/htm
19:27:49.515 804:840 TRACE :: 6C 0D 0A 44 61 74 65 3A 20 57 65 64 2C 20
32
32 :l..Date: Wed, 22
19:27:49.515 804:840 TRACE :: 20 44 65 63 20 32 30 30 34 20 31 33 3A 35
36
3A : Dec 2004 13:56:
19:27:49.515 804:840 TRACE :: 33 30 20 47 4D 54 0D 0A 43 6F 6E 6E 65 63
74
69 :30 GMT..Connecti
19:27:49.515 804:840 TRACE :: 6F 6E 3A 20 63 6C 6F 73 65 0D 0A 43 6F 6E
74
65 :on: close..Conte
19:27:49.515 804:840 TRACE :: 6E 74 2D 4C 65 6E 67 74 68 3A 20 32 30 0D
0A
0D :nt-Length: 20...
19:27:49.515 804:840 TRACE :: 0A 3C 68 31 3E 42 61 64 20 52 65 71 75 65
73
74 :.<h1>Bad Request
19:27:49.515 804:840 TRACE :: 3C 2F 68 31 3E :</h1
19:27:49.515 804:840 INFO :: CRTCProfile::SetState - [011957E0]
enState:1->5, statusCode=80072746, text=(null)
19:27:49.515 804:840 INFO :: RegistrationStateChangeEvent-
profile=011957E0, state=5, statusCode=80072746, text=(null)
19:27:49.515 804:840 INFO :: CRTCProfile::SetState - register error,
clear
postponed watchers
19:27:49.525 804:840 INFO :: CRTCClient::InternalEnableProfileEx -
pProfile=011957E0, regFlag=0x0, roamingFlag=0x0, realm=<(null)
19:27:49.525 804:840 INFO ::
RoamingSession::SetDeltaNum[01195890],0->0
19:27:49.525 804:840 INFO ::
RoamingSession::SetDeltaNum[011958D4],0->0
19:27:49.525 804:840 INFO ::
RoamingSession::SetDeltaNum[01195930],0->0
19:27:49.525 804:840 INFO ::
RoamingSession::SetDeltaNum[01195948],0->0
19:27:49.525 804:840 INFO ::
RoamingSession::SetDeltaNum[01195918],0->0
19:27:49.525 804:840 INFO :: SetRoamingStatus -
roamingFlag:old(0)|=flag(0)
--> new(0), statusCode=0
19:27:49.525 804:840 INFO ::
RoamingSession::SetDeltaNum[01195948],0->0



*******************

regards
R.Raja





Back to top
toml@online.microsoft.com
Guest





Posted: Wed Jan 05, 2005 10:13 pm    Post subject: Re: Connecting Via proxy ".. becos the service is temporaril Reply with quote

Raja,

remove online from my alias

TomL
Back to top
Raja
Guest





Posted: Thu Jan 06, 2005 3:01 pm    Post subject: Re: Connecting Via proxy ".. becos the service is temporaril Reply with quote

Tom,

I have solved the issue. It is a simple configuration issue. Thanks for all
your support.

regards
R.Raja

""Tom Laciano <MSFT>"" wrote:

Quote:
Raja,

remove online from my alias

TomL
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