#240 v0.4p2 not sending "CONNECT"

[Anonymous]

Problem: Using a Codian 4501 bridge or Xmeeting 0.3.4.a or a Tandberg Edge 95 the latest Xmeeeting client (v0.4p2) does not properly handshake when answering an incoming H.323 call. I believe it is does not send a Q.931 "CONNECT" packet back to the calling endpoint. It appears like it may be sending the "ALERT" in place of the "CONNECT".

We can successfully call all these devices directly BUT, v0.4p2 can NOT successfully answer a call.

v0.4p2 did work in some cases, sometimes when answering a call. We upgraded our bridge and it is more strict now in its adherence to protocol. Please see log info below for Xmeeting v0.4.p.2 NOT answering a call and then v0.3.4a successfully answering a call:

Here's the debug info:

40970 13:45:45.006 80220001 128.111.207.205:64961 128.111.186.74:1720 Q.931 TX Setup
40971 13:45:45.011 80220001 128.111.186.74:1720 128.111.207.205:64961 Q.931 RX CallProceeding
40972 13:45:45.013 80220001 128.111.186.74:1720 128.111.207.205:64961 Q.931 RX Alerting
40973 13:45:45.017 80220001 128.111.186.74:1720 128.111.207.205:64961 Q.931 RX Alerting

Here's what we should see:
40815 13:31:52.572 803F0000 128.111.207.205:64976 128.111.186.74:1720 Q.931 TX Setup
40816 13:31:52.575 803F0000 128.111.186.74:1720 128.111.207.205:64976 Q.931 RX CallProceeding
40817 13:31:52.576 803F0000 128.111.186.74:1720 128.111.207.205:64976 Q.931 RX Alerting
40818 13:31:52.770 00030001 128.111.207.205:2222 [127.0.0.1]:1719 RAS TX ARQ
40819 13:31:52.771 FFFFFFFF [127.0.0.1]:2222 128.111.207.205:1719 GK RX ARQ
40820 13:31:52.774 FFFFFFFF 128.111.207.205:1719 [127.0.0.1]:2222 GK TX ACF
40821 13:31:52.775 00030001 [127.0.0.1]:1719 128.111.207.205:2222 RAS RX ACF
40822 13:31:54.768 803F0000 128.111.186.74:1720 128.111.207.205:64976 Q.931 RX Connect