tcp communication error

[rvincent]

event viewer on the subscriber shows the following messages, which repeat every 6 seconds:

Warning: NodeId: 2, EventId: 14 EventClass: 4 EventInfo: TCP Communication Error: EnvProcssTcpPort Tcp Data Write Error 10038 socket 3012.

Warning: NodeId: 2, EventId: 14 EventClass: 4 EventInfo: TCP Communication Error: EnvProcssTcpPort Shutdown Error 10038 IPAddr 72024330.

Does anyone know what these messages are saying?

thanks

Rob

[dgoodwin]

What is the IP address 10.16.176.68? I think I decoded that correctly.

Is that an H.323 gateway by any chance?

[rvincent]

Dave:

The address 10.16.176.68 does not exist in my network.

I tried converting IP address 72024330 to binary and got 10.1.75.4 which is one of my H.323 gateways.

Rob

[dgoodwin]

Then that is a normal message that you will see when the CallManager side hangs up a call before the H.323 gateway releases the call.

[rvincent]

Dave:

Thanks. Does it seem right that I'd get this pair of messages every 6 seconds ? Are they being buffered?

Rob

[dgoodwin]

I'm not sure about that. You might want to take a detailed CCM trace and compare what's happening. Use the timestamp in Event Viewer to find the events in the CCM trace and see if you can figure out what is going on.

What I can tell you about the messages is that we are closing the socket after we hang up and send a Release Complete and we don't wait for them to respond. Which is not really a problem. I'm not sure why they seem to happen on such an exact timespan basis.

[rvincent]

Dave:

You are right. Messages only happen during business hours. I looked in the trace file and see the following:

16:24:22.965 Cisco CallManager|NodeId: 2, EventId: 14 EventClass: 4 EventInfo: TCP Communication Error: EnvProcssTcpPort Tcp Data Write Error 10038 socket 13648

16:24:22.965 Cisco CallManager|EnvProcessTcpPort - Socket operation on non-socket.

16:24:22.965 Cisco CallManager|An operation was attempted on something that is not a socket. Either the socket handle parameter did not reference a valid socket, or for select, a member of an fd_set was not valid.

16:24:22.965 Cisco CallManager|Locations: release: cdccPID=(2.14.14751) no entry.

16:24:22.965 Cisco CallManager|NodeId: 2, EventId: 14 EventClass: 4 EventInfo: TCP Communication Error: EnvProcssTcpPort Shutdown Error 10038 IPAddr 72024330

16:24:22.965 Cisco CallManager|EnvProcessTcpPort - Socket operation on non-socket.

16:24:22.965 Cisco CallManager|An operation was attempted on something that is not a socket. Either the socket handle parameter did not reference a valid socket, or for select, a member of an fd_set was not valid.

This happens right after a H225ReleaseCompleteMsg.

Rob

[8mliebscher]

Hi Rob,

can you explain, how you convert the ip address. My result is 2.37.128.133? Where is my fault?

Thanks

Martin

[rvincent]

Martin:

my address in the event viewer was : 72024330 which converted to : 100010010110000000100001010. working from right to left you get 10.1.75.4 as an ip address. this happens to be the address of one of my gateways.

check in the trace file at the time of your event viewer message and you should see the same message in the body of the event along with the associated gateway.

Rob

[8mliebscher]

Thank you for your reply.

I missed the last 0 during binary convertion. So my result is 4.75.1.10. This is the first time where i hear working from right to left!! Is this a microsoft specification. Can you say some words for explanation??

Thanks in advance!!

Martin