Solved: H.245 issue VCS-C / VCS-E

Stefan Walter · ‎06-04-2012

Hello all,

we've problems with our vcsc and vcse, when we make a call to our neighborzone (CUVCM - 3515/3545).

The H.225 (RAS and Q.931) works fine, but the H.245 process fails.

Immediately, the Call disconnect with cause: Normal Call clearing.

Here a diagnostic logfile in debug mode:

tanvcsx01 tvcs: UTCTime="2012-06-04 09:27:28,769" Module="network.h323" Level="INFO": Dst-ip="10.133.246.20" Dst-port="1719"

Detail="Sending RAS LRQ SeqNum=46766 Retransmit=True"

Jun 4 11:27:32 tanvcsx01 tvcs: UTCTime="2012-06-04 09:27:32,169" Module="network.tcp" Level="ERROR": Src-ip="10.150.246.51" Src-port="15457" Dst-ip="10.49.4.201" Dst-port="11247" Detail="TCP Connection Failed"

Jun 4 11:27:32 tanvcsx01 tvcs: UTCTime="2012-06-04 09:27:32,169" Module="network.h323" Level="ERROR": Dst-ip="10.49.4.201" Dst-port="11247"

Detail="Failed to connect outbound H.245 TCP connection. Rejecting inbound H.245 TCP connection."

Jun 4 11:27:32 tanvcsx01 tvcs: UTCTime="2012-06-04 09:27:32,169" Module="network.tcp" Level="DEBUG": Src-ip="10.151.1.51" Src-port="17588" Dst-ip="10.150.246.51" Dst-port="2776" Detail="TCP Connection Closed"

Jun 4 11:27:32 tanvcsx01 tvcs: UTCTime="2012-06-04 09:27:32,201" Module="network.h323" Level="INFO": Src-ip="10.151.1.51" Src-port="17623"

Detail="Received H.225 ReleaseComplete Q.931 Cause:Normal call clearing, H.225 Cause:Unknown reason, Additional Info:None"

Jun 4 11:27:32 tanvcsx01 tvcs: UTCTime="2012-06-04 09:27:32,201" Module="network.h323" Level="DEBUG": Src-ip="10.151.1.51" Src-port="17623"

thanks for help,

awinter2 · ‎06-05-2012

Stefan,

there seems to be something in the network blocking the TCP connection attempt from VCS-E to the endpoint (The connection attempt from 10.150.246.51 port 15457 to 10.49.4.201 port 11247).

Do you have any idea why this is happening? Are there any firewalls/switch ACL's which might be responsible for blocking this?

View solution in original post

awinter2 · ‎06-04-2012

Hi Stefan,

there's not a whole lot of information to work with here.

Can you clarify the following:

- What are the devices 10.49.4.201 and 10.150.246.51?

- What is the call scenario? Which devices are involved from one end to the other?

- Andreas

Stefan Walter · ‎06-04-2012

VCS-C 10.151.1.51 (X6.1)

VCS-E 10.150.246.51 (X7.1)

CUVCM 10.254.6.84

Endpoint A (EX90) is registered on the vcs-controll. Just we make a call to your neighborzone via H.323

(CUVCM)

the call gets a connect, but immediately after connecting the call disconnects with the message "normal call clearing".

So i've done a trace in debug mode.

awinter2 · ‎06-04-2012

What device is 10.49.4.201?

Stefan Walter · ‎06-04-2012

Hi,

this is the IP-Adress of the Endpoint (c-series), which is called. The EP is registered on the cuvcm with the ip adress 10.49.4.201. The neighborzone to the cuvcm ist configured on the expressway.

The call scenario look like this:

i call the alias 7795****, from our EX90 - the call gets an connect -

immediately after connecting, the call is terminated.

When i placed a call from the cuvcm to the EX90 the call is established.

awinter2 · ‎06-05-2012

Stefan,

there seems to be something in the network blocking the TCP connection attempt from VCS-E to the endpoint (The connection attempt from 10.150.246.51 port 15457 to 10.49.4.201 port 11247).

Do you have any idea why this is happening? Are there any firewalls/switch ACL's which might be responsible for blocking this?