|
I've committed a fix for this issue to the cvs
head. Please test it and report
whether it works (and does not break
something).
----- Original Message -----
Sent: Friday, September 19, 2008 3:01
AM
Subject: Re: Tandberg
Edge 95 unable to completenegotiation with gnugk227
Hi,
Thank you Jan
Willamowius and Zygmuntowicz Michal for their suggestions.
I have now done a wireshark trace, this
is the captured packet from the Tandberg Edge 95 as received by the
gatekeeper:
/*************/
Frame 59 (1179 bytes on wire, 1179 bytes
captured)
Ethernet II, Src: Cisco_df:
(), Dst: Ibm_71: ()
Internet Protocol,
Src: srcip (srcip), Dst: dstip (dstip)
Transmission Control Protocol, Src Port: 5561 (5561), Dst Port: 14558
(14558), Seq: 3, Ack: 648, Len: 1113
Reassembled TCP Segments (1108 bytes): #57(2), #59(2), #59(1104)
TPKT, Version: 3, Length: 1108
H.245
TPKT, Version: 3, Length: 7
H.245
/*************/
Is it normal to have 2 TPKT
wrappers?
Thanks,
Paul
| From:
| openh323gk-users-request@xxxxxxxxxxxxxxxxxxxxx
|
| To:
| openh323gk-users@xxxxxxxxxxxxxxxxxxxxx
|
| Date:
| 05/09/2008 12:38 PM
|
| Subject:
| Openh323gk-users Digest, Vol 28, Issue
3 |
------------------------------
Message:
3
Date: Fri, 05 Sep 2008 12:37:31 +1000
From: Paul Hii
<Paul.Hii@xxxxxxxxxxxxxxxxx>
Subject: Tandberg
Edge 95 unable to complete
negotiation
with gnugk227
To:
openh323gk-users@xxxxxxxxxxxxxxxxxxxxx
Message-ID:
<OFB06FB4CD.ADAACD3C-ONCA2574BB.000E4ACF-CA2574BB.000E63E7@xxxxxxxxxxxxx>
Content-Type: text/plain;
charset="us-ascii"
Hi,
we have been having an issue with a
Tandberg Edge 95 MXP that is failing
to establish calls via our gnugk
2.2.7.
Tandberg Edge 95 MXP (Malaysia) --- gnugk227 (Australia) ---
Tandberg 150
(Australia)
The gnugk227 is in routed mode and proxies
all calls. Both the Edge 95 and
T150 are registered to the
gnugk227.
The T150 initiated the call via the gnugk227 to Edge 95. The
usual arq,
acf, q931 (setup, alert, connect) happens until the call
connection failed
in the exchange of h245
terminalCapabilitySet.
Please see the gnugk log
below:
2008/08/28 14:27:31.333 3
ProxyChannel.cxx(3719) H245 Connected
from T150:5559 on
gnugk227:11473
2008/08/28 14:27:31.436 3
ProxyChannel.cxx(3751) H245 Connect to
edge95:11016
from gnugk227:0 successful
2008/08/28 14:27:31.436 5
ProxyChannel.cxx(5088) ProxyH(5) total
sockets 4
2008/08/28
14:27:31.437 5
job.cxx(426) JOB Job
H245Connector
deleted
2008/08/28 14:27:31.437 5
job.cxx(415) JOB Worker
threads: 21
total - 19 busy, 2 idle
2008/08/28 14:27:31.511 5
yasocket.cxx(783) ProxyH(5) 1
sockets selected from 4, total 4/0
2008/08/28 14:27:31.511 5
ProxyChannel.cxx(623) H245s Reading
from
T150:5559
2008/08/28 14:27:31.512 4
ProxyChannel.cxx(1093) H245 Received:
request
terminalCapabilitySet {
.................
2008/08/28 14:27:31.513 4
ProxyChannel.cxx(4487) H245 Request:
terminalCapabilitySet
2008/08/28 14:27:31.581 5
yasocket.cxx(783) ProxyH(5) 1
sockets selected from 4, total 4/0
2008/08/28 14:27:31.581 5
ProxyChannel.cxx(623) H245d Reading
from
edge95:11016
2008/08/28 14:27:31.681 4
yasocket.cxx(656) H245d edge95:11016
Error(0):
Timeout
2008/08/28 14:27:31.693 5
yasocket.cxx(783) ProxyH(5) 1
sockets selected
from 4, total 4/0
2008/08/28 14:27:31.693 5
ProxyChannel.cxx(623) H245d Reading
from
edge95:11016
2008/08/28 14:27:31.693 2
ProxyChannel.cxx(631) Proxy edge95:11016
NOT TPKT
PACKET!
2008/08/28 14:27:31.693 5
yasocket.cxx(783) ProxyH(5) 1
sockets selected
from 4, total 4/0
2008/08/28 14:27:31.693 5
ProxyChannel.cxx(623) H245d Reading
from
edge95:11016
2008/08/28 14:27:31.693 2
ProxyChannel.cxx(631) Proxy edge95:11016
NOT TPKT
PACKET!
Syslog on the edge95 showed that the edge95 did receive and
respond to the
request for terminalCapabilitySet from the
gnugk227.
We have had many calls by Tandberg endpoints via the gnugk227
without
problem except for this particular model, Edge 95 MXP.
Any
idea what could be cause of the Timeout and NOT TPKT PACKET?
Thanks in
advance for all
help.
Cheers,
Paul
|
