Windows Server

Venkat Goud · Guest

When my server forwards a request to LCS 2005 server, it responds with a 400
response.
The response has the following header
Via: SIP/2.0/TCP
135.8.69.104:5060;branch=z9hG4bK4343868383376363372e8d.0;ms-received-port=47780;ms-received-cid=100

I am assuming that ms-received-port means LCS expects the top most via
header to contain this port number(47780) instead of the listen port number
of the server(5060). If this is the case then it won't work with any TCP
based sip proxies.

Any one tried forwarding requests from their servers to LCS?

SUBSCRIBE sip:egilbert@presence.mydomain.com:5060;transport=tcp SIP/2.0
Accept: application/xpidf+xml,application/cpim-pidf+xml
Call-ID: 486442225-18582
CSeq: 1 SUBSCRIBE
Expires: 3600
From: sip:presenceserver@presence.mydomain.com;tag=hssUA_486442310-18582
To: sip:egilbert@presence.mydomain.com
Via: SIP/2.0/TCP
135.8.69.104:5060;branch=z9hG4bK4343868383376363372e8d.0,SIP/2.0/TLS
135.8.69.104:6061;psrrposn=1;branch=z9hG4bK486442282-18582
Content-Length: 0
Contact: <sips:egilbert@135.8.69.104:6061>
Max-Forwards: 69
Allow:
INVITE,BYE,CANCEL,ACK,INFO,PRACK,COMET,OPTIONS,SUBSCRIBE,NOTIFY,REGISTER,UPDATE
Event: presence
Record-Route: <sip:135.8.69.104:5060;lr;transport=tcp>

SIP/2.0 400 Missing correct Via header
Via: SIP/2.0/TCP
135.8.69.104:5060;branch=z9hG4bK4343868383376363372e8d.0;ms-received-port=47780;ms-received-cid=100
Via: SIP/2.0/TLS 135.8.69.104:6061;psrrposn=1;branch=z9hG4bK486442282-18582
From: sip:presenceserver@presence.mydomain.com;tag=hssUA_486442310-18582
To: sip:egilbert@presence.mydomain.com;tag=D9E72A54BD32CE53ED9E4D6682DCAC2C
Call-ID: 486442225-18582
CSeq: 1 SUBSCRIBE
Content-Length: 0

Thanks
Venkat

Expand AllCollapse All

Dhigha D Sekara · Guest

Venkat,
This response is usually sent when LCS doesnt trust the request coming in
from another server.

Trust between servers can be done by configuring MTLS between by the two
servers.
In your case I guess you have a proxy-server and you would want to do TCP
with the server. In this case you can add this server to the "Host
Authorization" table in the pool level settings in the LCS MMC console. For
more details on this please see documentation.

Thanks,
Dhigha

--
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

"Venkat Goud" <VenkatGoud@discussions.microsoft.com> wrote in message
news:356B2DCB-3788-4C9E-9BFC-2AEDC244631E@microsoft.com...

Venkat Goud · Guest

Thanks Dhigha.
After I made those changes, LCS responds with a 504 Server time-out.

I see this in the log "Data: Host name resolution failure". I am trying
to figure out what Host name it is trying to resolve?

$$begin_record
LogType: protocol
Date: 20050205 003054
Direction: Incoming
Message-Type: Request
Start-Line: SUBSCRIBE sip:venkat@presence.domain.com;transport=tcp SIP/2.0
To: sip:venkat@domain.com
From: sip:presenceserver@domain.com;tag=hssUA_3092551338-24094
Call-ID: 3092551245-24094
CSeq: 1 SUBSCRIBE
Contact: <sip:venkat@135.8.69.104:6060;transport=tcp>
Via: SIP/2.0/TCP
135.8.69.104:5060;branch=z9hG4bK3333860303379393372e49.0,SIP/2.0/TCP
135.8.69.104:6060;psrrposn=1;branch=z9hG4bK3092551307-24094
Route: <sip:135.8.121.39;transport=tcp;lr>
Record-Route: <sip:135.8.69.104:5060;lr;transport=tcp>
Max-Forwards: 69
Expires: 3600
Content-Length: 0
Other-Headers: Accept: application/xpidf+xml,application/cpim-pidf+xml
Other-Headers: Allow:
INVITE,BYE,CANCEL,ACK,INFO,PRACK,COMET,OPTIONS,SUBSCRIBE,NOTIFY,REGISTER,UPDATE
Other-Headers: Event: presence
Other-Headers: P-Asserted-Identity: <sip:presenceserver@domain.com>
$$end_record
$$begin_record
LogType: diagnostic
Date: 20050205 003054
Severity: warning
Text: Unable to route the request
SIP-Start-Line: SUBSCRIBE sip:venkat@presence.domain.com;transport=tcp SIP/2.0
SIP-Call-ID: 3092551245-24094
SIP-CSeq: 1 SUBSCRIBE
Data: Host name resolution failure
$$end_record
$$begin_record
LogType: diagnostic
Date: 20050205 003054
Severity: information
Text: Response successfully routed
SIP-Start-Line: SIP/2.0 504 Server time-out
SIP-Call-ID: 3092551245-24094
SIP-CSeq: 1 SUBSCRIBE
Peer: 135.8.69.104:37002
$$end_record
$$begin_record
LogType: protocol
Date: 20050205 003054
Direction: Outgoing
Origin: Local
Message-Type: Response
Start-Line: SIP/2.0 504 Server time-out
To: sip:venkat@domain.com;tag=769F8029C7138B1B8C48FD54FB5EFC61
From: sip:presenceserver@domain.com;tag=hssUA_3092551338-24094
Call-ID: 3092551245-24094
CSeq: 1 SUBSCRIBE
Via: SIP/2.0/TCP
135.8.69.104:5060;branch=z9hG4bK3333860303379393372e49.0;ms-received-port=37002;ms-received-cid=800
Via: SIP/2.0/TCP 135.8.69.104:6060;psrrposn=1;branch=z9hG4bK3092551307-24094
Content-Length: 0
$$end_record

"Dhigha D Sekaran<msft>" wrote:

Dhigha D Sekara · Guest

Have you added the sip domain you are using to the global supported sip
domain list...
see http://support.microsoft.com/?kbid=834470 for details....

--
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

"Venkat Goud" <VenkatGoud@discussions.microsoft.com> wrote in message
news:17EAFA33-AA71-4450-A37D-79041F7E4525@microsoft.com...

Venkat Goud · Guest

The sip domain is same on both my proxy and LCS.
I also added it and tried it again. It did not work.

-Venkat

"Dhigha D Sekaran<msft>" wrote:

	Windows Server Forum Index -> Live Communications Server	All times are GMT
Page 1 of 1