Windows Server

Guest

Hi,

I have a IM message application that communicates with about 40
clients.

The application maintains a sip session with each of its clients.

After a client session has be operational for some number
of hours LCS inexplicably 'disconnects' the session.

I set the logging level to 4 on the LCS and captured the 'cause'
of the disconnect below. LCS appears to think that the route
header in the message from the application is invalid. I have no idea
why this
might be since the application has been happily sending IM messages to
the client for many hours. Any help would be much appreciated.

Beneath the failed message log extract I've included
a previous successfully message log extract.

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

$$begin_record
LogType: security
Date: 20051110 204128
Text: Route headers specified are invalid
Result-Code: 0xc3e92046
Peer: 192.168.1.213:2248
SIP-Start-Line: MESSAGE
sip:nylcs.sandellmgmt.com;transport=tcp;lr;ms-route-sig=ga7y1TxBCOa2kNhu_b5DBkD0j8AmC_
SIP/2.0
SIP-Call-ID: 3781fe8857f44954b906a04253e47156
SIP-CSeq: 1493 MESSAGE
$$end_record

$$begin_record
LogType: security
Date: 20051110 204128
Text: Parsing failed
Result-Code: 0xc3ed182b
Peer: 192.168.1.213:2248
SIP-Start-Line: MESSAGE
sip:nylcs.sandellmgmt.com;transport=tcp;lr;ms-route-sig=ga7y1TxBCOa2kNhu_b5DBkD0j8AmC_
SIP/2.0
SIP-Call-ID: 3781fe8857f44954b906a04253e47156
SIP-CSeq: 1493 MESSAGE
$$end_record

$$begin_record
LogType: protocol
Date: 20051110 204128
Direction: Incoming
Message-Type: Request
Start-Line: INVITE sip:gcragin@sandellmgmt.com SIP/2.0
To: <sip:gcragin@sandellmgmt.com>;epid=fb0ea4763f
From: "SOB BOT"
<sip:sob_bot@sandellmgmt.com>;tag=f7342fb7e25c4311864a31cbb96a1c49;epid=7c52bc9fb3
Call-ID: e68e785c378049d79b7f510e209662db
CSeq: 1 INVITE
Contact:
<sip:sob_bot@sandellmgmt.com:9023;maddr=192.168.1.213;transport=tcp>;proxy=replace
Via: SIP/2.0/TCP 192.168.1.213:9023
Max-Forwards: 70
Content-Length: 125
Content-Type: application/sdp
Message-Body: v=0\no=- 0 0 IN IP4 192.168.1.213\ns=session\nc=IN IP4
192.168.1.213\nt=0 0\nm=message 5060 sip sip:sob_bot@sandellmgmt.com
$$end_record

$$begin_record
LogType: protocol
Date: 20051110 204128
Direction: Outgoing
Origin: Local
Message-Type: Response
Start-Line: SIP/2.0 100 Trying
To: <sip:gcragin@sandellmgmt.com>;epid=fb0ea4763f
From: "SOB BOT"
<sip:sob_bot@sandellmgmt.com>;tag=f7342fb7e25c4311864a31cbb96a1c49;epid=7c52bc9fb3
Call-ID: e68e785c378049d79b7f510e209662db
CSeq: 1 INVITE
Via: SIP/2.0/TCP
192.168.1.213:9023;ms-received-port=2248;ms-received-cid=1a0a00
Content-Length: 0
$$end_record

$$begin_record
LogType: protocol
Date: 20051110 204128
Direction: Outgoing
Message-Type: Request
Start-Line: INVITE
sip:192.168.1.104:1477;transport=tcp;ms-received-cid=20D500 SIP/2.0
To: <sip:gcragin@sandellmgmt.com>;epid=fb0ea4763f
From: "SOB BOT"
<sip:sob_bot@sandellmgmt.com>;tag=f7342fb7e25c4311864a31cbb96a1c49;epid=7c52bc9fb3
Call-ID: e68e785c378049d79b7f510e209662db
CSeq: 1 INVITE
Contact:
<sip:sob_bot@sandellmgmt.com:2248;maddr=192.168.1.213;transport=tcp;ms-received-cid=1A0A00>
Via: SIP/2.0/TCP
192.168.1.213;branch=z9hG4bKCB988195.EBCAFB61;branched=FALSE;ms-internal-info="daxUlZR22df3q5cyoNh3WchCxOFQ58"
Via: SIP/2.0/TCP
192.168.1.213:9023;ms-received-port=2248;ms-received-cid=1a0a00
Max-Forwards: 69
Content-Length: 125
Content-Type: application/sdp
Message-Body: v=0\no=- 0 0 IN IP4 192.168.1.213\ns=session\nc=IN IP4
192.168.1.213\nt=0 0\nm=message 5060 sip sip:sob_bot@sandellmgmt.com
$$end_record

$$begin_record
LogType: protocol
Date: 20051110 204128
Direction: Incoming
Message-Type: Response
Start-Line: SIP/2.0 100 Trying
To:
<sip:gcragin@sandellmgmt.com>;epid=fb0ea4763f;tag=e12d20a54e754a05b23bd177978e7eb8
From: "SOB BOT"
<sip:sob_bot@sandellmgmt.com>;tag=f7342fb7e25c4311864a31cbb96a1c49;epid=7c52bc9fb3
Call-ID: e68e785c378049d79b7f510e209662db
CSeq: 1 INVITE
Via: SIP/2.0/TCP
192.168.1.213;branch=z9hG4bKCB988195.EBCAFB61;branched=FALSE;ms-internal-info="daxUlZR22df3q5cyoNh3WchCxOFQ58"
Via: SIP/2.0/TCP
192.168.1.213:9023;ms-received-port=2248;ms-received-cid=1a0a00
Content-Length: 0
$$end_record

$$begin_record
LogType: protocol
Date: 20051110 204128
Direction: Incoming
Message-Type: Response
Start-Line: SIP/2.0 200 OK
To:
<sip:gcragin@sandellmgmt.com>;epid=fb0ea4763f;tag=e12d20a54e754a05b23bd177978e7eb8
From: "SOB BOT"
<sip:sob_bot@sandellmgmt.com>;tag=f7342fb7e25c4311864a31cbb96a1c49;epid=7c52bc9fb3
Call-ID: e68e785c378049d79b7f510e209662db
CSeq: 1 INVITE
Contact:
<sip:gcragin@sandellmgmt.com:8987;maddr=192.168.1.104;transport=tcp>;proxy=replace
Via: SIP/2.0/TCP
192.168.1.213;branch=z9hG4bKCB988195.EBCAFB61;branched=FALSE;ms-internal-info="daxUlZR22df3q5cyoNh3WchCxOFQ58"
Via: SIP/2.0/TCP
192.168.1.213:9023;ms-received-port=2248;ms-received-cid=1a0a00
Record-Route:
<sip:nylcs.sandellmgmt.com;transport=tcp;lr;ms-route-sig=ba4RIy70moK8jL63HMYODj5Ej8AmAo>;tag=825592B9B5381873741F0C596EC1D071
Content-Length: 125
Content-Type: application/sdp
Message-Body: v=0\no=- 0 0 IN IP4 192.168.1.104\ns=session\nc=IN IP4
192.168.1.104\nt=0 0\nm=message 5060 sip sip:gcragin@sandellmgmt.com
$$end_record

$$begin_record
LogType: protocol
Date: 20051110 204128
Direction: Outgoing
Message-Type: Response
Start-Line: SIP/2.0 200 OK
To:
<sip:gcragin@sandellmgmt.com>;epid=fb0ea4763f;tag=e12d20a54e754a05b23bd177978e7eb8
From: "SOB BOT"
<sip:sob_bot@sandellmgmt.com>;tag=f7342fb7e25c4311864a31cbb96a1c49;epid=7c52bc9fb3
Call-ID: e68e785c378049d79b7f510e209662db
CSeq: 1 INVITE
Contact:
<sip:gcragin@sandellmgmt.com:1477;maddr=192.168.1.104;transport=tcp;ms-received-cid=20D500>
Via: SIP/2.0/TCP
192.168.1.213:9023;ms-received-port=2248;ms-received-cid=1a0a00
Record-Route:
<sip:nylcs.sandellmgmt.com;transport=tcp;lr;ms-route-sig=ba4RIy70moK8jL63HMYODj5Ej8AmAo>;tag=825592B9B5381873741F0C596EC1D071
Content-Length: 125
Content-Type: application/sdp
Message-Body: v=0\no=- 0 0 IN IP4 192.168.1.104\ns=session\nc=IN IP4
192.168.1.104\nt=0 0\nm=message 5060 sip sip:gcragin@sandellmgmt.com
$$end_record

$$begin_record
LogType: protocol
Date: 20051110 204128
Direction: Incoming
Message-Type: Request
Start-Line: ACK
sip:nylcs.sandellmgmt.com;transport=tcp;lr;ms-route-sig=bagL9jWwYHH_ZcX4t03oIFXUj8AmD8
SIP/2.0
To:
<sip:gcragin@sandellmgmt.com>;epid=fb0ea4763f;tag=e12d20a54e754a05b23bd177978e7eb8
From: "SOB BOT"
<sip:sob_bot@sandellmgmt.com>;tag=f7342fb7e25c4311864a31cbb96a1c49;epid=7c52bc9fb3
Call-ID: e68e785c378049d79b7f510e209662db
CSeq: 1 ACK
Via: SIP/2.0/TCP 192.168.1.213:9023
Route:
<sip:gcragin@sandellmgmt.com:1477;maddr=192.168.1.104;transport=tcp;ms-received-cid=20D500>
Max-Forwards: 70
Content-Length: 0
$$end_record

$$begin_record
LogType: protocol
Date: 20051110 204128
Direction: Outgoing
Message-Type: Request
Start-Line: ACK
sip:nylcs.sandellmgmt.com;transport=tcp;lr;ms-route-sig=bagL9jWwYHH_ZcX4t03oIFXUj8AmD8
SIP/2.0
To:
<sip:gcragin@sandellmgmt.com>;epid=fb0ea4763f;tag=e12d20a54e754a05b23bd177978e7eb8
From: "SOB BOT"
<sip:sob_bot@sandellmgmt.com>;tag=f7342fb7e25c4311864a31cbb96a1c49;epid=7c52bc9fb3
Call-ID: e68e785c378049d79b7f510e209662db
CSeq: 1 ACK
Via: SIP/2.0/TCP
192.168.1.213;branch=z9hG4bKCB0A7BDB.2E30F24B;branched=FALSE
Via: SIP/2.0/TCP
192.168.1.213:9023;ms-received-port=2248;ms-received-cid=1a0a00
Max-Forwards: 70
Content-Length: 0
$$end_record

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

example of a previously sent successful message:

$$begin_record
LogType: protocol
Date: 20051111 121258
Direction: Incoming
Message-Type: Request
Start-Line: MESSAGE
sip:nylcs.sandellmgmt.com;transport=tcp;lr;ms-route-sig=caetZ6vOC3a9VruOObH7t8qEj8AmAM
SIP/2.0
To:
<sip:jdepablo@sandellmgmt.com>;epid=7230c15b22;tag=ee4f45f63513497e8a9fd0cbaad5600f
From: "SOB BOT"
<sip:sob_bot@sandellmgmt.com>;tag=aabc646839e64433894efd4556f3ec9b;epid=7c52bc9fb3
Call-ID: 59dbd046efab4d3a993d8a14705a24ee
CSeq: 1381 MESSAGE
Contact:
<sip:sob_bot@sandellmgmt.com:9023;maddr=192.168.1.213;transport=tcp>;proxy=replace
Via: SIP/2.0/TCP 192.168.1.213:9023
Route:
<sip:jdepablo@sandellmgmt.com:4286;maddr=192.168.1.163;transport=tcp;ms-received-cid=1FA800>
Max-Forwards: 70
Content-Length: 68
Content-Type: text/plain
Other-Headers: User-Agent: RTC/1.3
Other-Headers: Proxy-Authorization: Kerberos qop="auth", realm="SIP
Communications Service", opaque="23A325A1", crand="3d708c0d",
cnum="8495", targetname="sip/nylcs.sandellmgmt.com",
response="602306092a864886f71201020201011100fffffffff23b00ed88967a356e6461368442e875"
$$end_record

$$begin_record
LogType: diagnostic
Date: 20051111 121258
Severity: information
Text: Routed a request using signed route headers
SIP-Start-Line: MESSAGE
sip:nylcs.sandellmgmt.com;transport=tcp;lr;ms-route-sig=caetZ6vOC3a9VruOObH7t8qEj8AmAM
SIP/2.0
SIP-Call-ID: 59dbd046efab4d3a993d8a14705a24ee
SIP-CSeq: 1381 MESSAGE
Peer: 192.168.1.163:4286
$$end_record

$$begin_record
LogType: protocol
Date: 20051111 121258
Direction: Outgoing
Message-Type: Request
Start-Line: MESSAGE
sip:nylcs.sandellmgmt.com;transport=tcp;lr;ms-route-sig=caetZ6vOC3a9VruOObH7t8qEj8AmAM
SIP/2.0
To:
<sip:jdepablo@sandellmgmt.com>;epid=7230c15b22;tag=ee4f45f63513497e8a9fd0cbaad5600f
From: "SOB BOT"
<sip:sob_bot@sandellmgmt.com>;tag=aabc646839e64433894efd4556f3ec9b;epid=7c52bc9fb3
Call-ID: 59dbd046efab4d3a993d8a14705a24ee
CSeq: 1381 MESSAGE
Contact:
<sip:sob_bot@sandellmgmt.com:2248;maddr=192.168.1.213;transport=tcp;ms-received-cid=1A0A00>
Via: SIP/2.0/TCP
192.168.1.213;branch=z9hG4bKFFA453F7.54F3ACF4;branched=FALSE;ms-internal-info="caAQ37Zte_iJ5UxRi8oXYwBixOFQ4k"
Via: SIP/2.0/TCP
192.168.1.213:9023;ms-received-port=2248;ms-received-cid=1a0a00
Max-Forwards: 69
Content-Length: 68
Content-Type: text/plain
Other-Headers: Authentication-Info: Kerberos
rspauth="602306092A864886F71201020201011100FFFFFFFF99F2A3A61C3FF66AAA00C40EC7F19787",
srand="73D17C4C", snum="442", opaque="C4475B45", qop="auth",
targetname="sip/nylcs.sandellmgmt.com", realm="SIP Communications
Service"
Other-Headers: User-Agent: RTC/1.3
$$end_record

Guest

I started a support case with Microsoft on this issue.

Microsoft did the following:

- gave me an unpublished 'hot fix' to install on LCS
- enabled tracing on the client pc by setting
[HKEY_CURRENT_USER\Software\Microsoft\Tracing\RTCDLL]
"EnableFileTracing"=dword:00000001
- asked that I set the authentication on LCS from 'NTLM & Kerberos' to
just 'NTLM'

Not entirely sure the person I spoke at Microsoft understood the
problem
but I'll install the patch on Monday and see what happens. Our network
only uses NTLM
authentication (but all other server software is set to NTLM & Kerberos
which I believe is the default)

Last thing, I included the wrong bit of the log showing the 'route
headers are invalid' error. Sorry.
Here's what I meant to post:

$$begin_record
LogType: protocol
Date: 20051111 123033
Direction: Incoming
Message-Type: Request
Start-Line: MESSAGE
sip:nylcs.sandellmgmt.com;transport=tcp;lr;ms-route-sig=caetZ6vOC3a9VruOObH7t8qEj8AmAM
SIP/2.0
To:
<sip:jdepablo@sandellmgmt.com>;epid=7230c15b22;tag=ee4f45f63513497e8a9fd0cbaad5600f
From: "SOB BOT"
<sip:sob_bot@sandellmgmt.com>;tag=aabc646839e64433894efd4556f3ec9b;epid=7c52bc9fb3
Call-ID: 59dbd046efab4d3a993d8a14705a24ee
CSeq: 1416 MESSAGE
Contact:
<sip:sob_bot@sandellmgmt.com:9023;maddr=192.168.1.213;transport=tcp>;proxy=replace
Via: SIP/2.0/TCP 192.168.1.213:9023
Route:
<sip:jdepablo@sandellmgmt.com:4286;maddr=192.168.1.163;transport=tcp;ms-received-cid=1FA800>
Max-Forwards: 70
Content-Length: 68
Content-Type: text/plain
Other-Headers: User-Agent: RTC/1.3
Other-Headers: Proxy-Authorization: Kerberos qop="auth", realm="SIP
Communications Service", opaque="23A325A1", crand="4bc12524",
cnum="8985", targetname="sip/nylcs.sandellmgmt.com",
response="602306092a864886f71201020201011100ffffffff7a2720fe8d936ae96611004f680a9c54"
$$end_record

$$begin_record
LogType: security
Date: 20051111 123033
Text: Route headers specified are invalid
Result-Code: 0xc3e92046
Peer: 192.168.1.213:2248
SIP-Start-Line: MESSAGE
sip:nylcs.sandellmgmt.com;transport=tcp;lr;ms-route-sig=caetZ6vOC3a9VruOObH7t8qEj8AmAM
SIP/2.0
SIP-Call-ID: 59dbd046efab4d3a993d8a14705a24ee
SIP-CSeq: 1416 MESSAGE
$$end_record

$$begin_record
LogType: security
Date: 20051111 123033
Text: Parsing failed
Result-Code: 0xc3ed182b
Peer: 192.168.1.213:2248
SIP-Start-Line: MESSAGE
sip:nylcs.sandellmgmt.com;transport=tcp;lr;ms-route-sig=caetZ6vOC3a9VruOObH7t8qEj8AmAM
SIP/2.0
SIP-Call-ID: 59dbd046efab4d3a993d8a14705a24ee
SIP-CSeq: 1416 MESSAGE
$$end_record

$$begin_record
LogType: diagnostic
Date: 20051111 123033
Severity: information
Text: Response successfully routed
SIP-Start-Line: SIP/2.0 481 Call Leg Does Not Exist
SIP-Call-ID: 59dbd046efab4d3a993d8a14705a24ee
SIP-CSeq: 1416 MESSAGE
Peer: 192.168.1.213:2248
$$end_record

$$begin_record
LogType: protocol
Date: 20051111 123033
Direction: Outgoing
Origin: Local
Message-Type: Response
Start-Line: SIP/2.0 481 Call Leg Does Not Exist
To:
<sip:jdepablo@sandellmgmt.com>;epid=7230c15b22;tag=ee4f45f63513497e8a9fd0cbaad5600f
From: "SOB BOT"
<sip:sob_bot@sandellmgmt.com>;tag=aabc646839e64433894efd4556f3ec9b;epid=7c52bc9fb3
Call-ID: 59dbd046efab4d3a993d8a14705a24ee
CSeq: 1416 MESSAGE
Via: SIP/2.0/TCP
192.168.1.213:9023;ms-received-port=2248;ms-received-cid=1a0a00
Content-Length: 0
Other-Headers: Authentication-Info: Kerberos
rspauth="602306092A864886F71201020201011100FFFFFFFFA2AA2C3D256AF50CBA1869AE57979F3E",
srand="A1316E35", snum="8155", opaque="23A325A1", qop="auth",
targetname="sip/nylcs.sandellmgmt.com", realm="SIP Communications
Service"
Other-Headers: ms-diagnostic-info: 825592B9B5381873741F0C596EC1D071
$$end_record

$$begin_record
LogType: diagnostic
Date: 20051111 123033
Severity: information
Text: Error processing message
Result-Code: 0xc3e92046
SIP-Start-Line: MESSAGE
sip:nylcs.sandellmgmt.com;transport=tcp;lr;ms-route-sig=caetZ6vOC3a9VruOObH7t8qEj8AmAM
SIP/2.0
SIP-Call-ID: 59dbd046efab4d3a993d8a14705a24ee
SIP-CSeq: 1416 MESSAGE
Peer: 192.168.1.213:2248
$$end_record

Toryg33 · Guest

I've got this exact same problem. LCS 2005 w/SP1 installed on Windows
2003 w/ SP1. I can't figure out what the issue is. On the LCS server I
get the same error you have. On the client tracing I get a thing saying
that the socket can't be made and and that the host name can't be
found. However if you sign out wait a couple minutes and then sign back
in, you are good for a few hours. Also if you log out, flush the DNS
cache then it works too. I'm at a loss...

LCS 2005 "Route headers specified are invalid" error after s

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