|
Is this timer expiry happening in the
originating/terminating gateways or the GNUGK? In other words, does GNUGK create
a timer for setup, alert, connect or so and keep track of them for all
the calls itself or it just rely on the endpoints' timers?
If the GNUGK has its own timers, in which
trace level I can see the expiry in the logs. If it is relying on the
endpoints' timers then the release complete should have initiated from
either the originating or terminating endpoints; something like the following;
which based on the last log that I sent it seemed it was initiated by
GNUGK itself.
2005/11/22 09:50:50.586 4 ProxyChannel.cxx(2370) H245 Indication:
terminalCapabilitySetRelease
2005/11/22 09:50:50.588 5 yasocket.cxx(709) ProxyRTP(0) 1 sockets selected
from 4, total 4/0
2005/11/22 09:50:50.599 5 yasocket.cxx(709) ProxyH(0) 1 sockets selected
from 4, total 4/0
2005/11/22 09:50:50.600 5 ProxyChannel.cxx(501) Q931s Reading from
209.167.xxx.xxx:42102
2005/11/22 09:50:50.601 3 ProxyChannel.cxx(744) Q931s Received: ReleaseComplete CRV=720 from
209.167.xxx.xxx:42102
2005/11/22 09:50:50.609 4 ProxyChannel.cxx(686) Q931 Received: {
q931pdu = {
protocolDiscriminator = 8
callReference = 720
from = originator
messageType = ReleaseComplete
IE: Cause - Temporary failure =
{
One more thing to consider. I can see
dcc 41 rarely if I use version 2.2.1. It would occur much more if the version is
higher than 2.2.1. Maybe this shed some lights for
pinpointing.
I will try to get something out of the cv
command as well.
Bahram
----- Original Message -----
Sent: Wednesday, November 23, 2005 5:17
AM
Subject: Re: GNUGK
versions higher than 2.1.1 and dcc 41
The log tells, that the gatekeeper disconnects the call with
cause 41.
This may happend due to:
1) accounting failure,
2) timer
expiry (SetupTimeout, SignalTimeout, AlertingTimeout, call duration
limit).
Use telnet interface and the 'cv' command to
monitor timers and see which one
needs to be
increased.
----- Original Message -----
From: "Bahram S. Biria"
<bsbiria@xxxxxxxxxxxxx>
Sent:
Wednesday, November 23, 2005 6:07 AM
This is an example of those
call rejects with dcc 41 when the call is passed through the GNUGK.
The
version of the GNUGK on this example was 2.2.2 and it was working in full
proxy. All the required steps were included in the
log. Below is some part
of the log of a call which got disconnected by dcc 41 (I didn't include the
complete log because I knew,
most likely nobody would have enough time and
patient to go through all the log top to bottom).
I colored and
enlarged the parts that I thought would be more important to pay attention
first. What I could see (please correct me
if I am wrong) is that after
"progress" GNUGK was sending release complete to both Calling and Called
parties. What confuses me is
that the release complete is not coming from
one party and be passed to the other party by GNUGK . The way that I saw it
was that
the release complete was issued by GNUGK itself. If you also
agree, then I need an idea about why.
Does what I wrote above and what
you could see below make sense?
To explain the condition of the call,
there were only this call on the GNUGK at the time and the call to same
destination was
connected just fine without GNUGK in the middle of the
way. One more interesting part is that this problem (call rejects with dcc
41) is not always duplicable meaning maybe one call gets cause code 41 in
the first shot but get connected on the next try.
Does anyone have
anything to share on this?
Cheers,
Bahram.
2005/11/22
16:52:45.068 3 ProxyChannel.cxx(2823) RTP 209.167.xxx.xxx:56090 socket is
busy, 60 bytes queued
2005/11/22 16:52:45.069 3 ProxyChannel.cxx(3631)
Proxy 209.167.xxx.xxx:56090 forward blocked
2005/11/22 16:52:45.070 4
ProxyChannel.cxx(686) Q931 Send to 209.167.xxx.xxx:58310 {
q931pdu =
{
protocolDiscriminator = 8
callReference = 67
from =
destination
messageType = Progress
IE: Progress-Indicator =
{
.
.
.
.
}
2005/11/22 16:52:45.071 4 ProxyChannel.cxx(2859)
RTP 60 bytes flushed to 209.167.xxx.xxx:56090
2005/11/22 16:52:45.071 4
ProxyChannel.cxx(2859) RTP 60 bytes flushed to
209.167.xxx.xxx:56090
2005/11/22 16:52:45.072 4 ProxyChannel.cxx(2859) RTP
60 bytes flushed to 209.167.xxx.xxx:56090
2005/11/22 16:52:45.073 4
ProxyChannel.cxx(3721) Proxy 209.167.xxx.xxx:56090 flush ok
2005/11/22
16:52:57.474 4 RasTbl.cxx(1604) Sending ReleaseComplete to calling party
...
2005/11/22 16:52:57.483 4 ProxyChannel.cxx(686) Q931 Send to
209.167.xxx.xxx:58310 {
q931pdu = {
protocolDiscriminator =
8
callReference = 32835
from = destination
messageType =
ReleaseComplete
IE: Cause - Temporary failure =
{
.
.
.
}
2005/11/22 16:52:57.485 4 RasTbl.cxx(1609) Sending
ReleaseComplete to called party ...
2005/11/22 16:52:57.495 4
ProxyChannel.cxx(686) Q931 Send to 69.44.xxx.xxx:1720 {
q931pdu =
{
protocolDiscriminator = 8
callReference = 67
from =
originator
messageType = ReleaseComplete
IE: Cause - Temporary failure =
{
80 a9 ..
}
IE: User-User = {
.
.
.
}
2005/11/22
16:52:57.497 2 RasTbl.cxx(1597) Gk Disconnect Call No. 3
-----
Original Message -----
From: Jove Blazevski
To: openh323gk-users@xxxxxxxxxxxxxxxxxxxxx
Sent: Saturday, November 19, 2005 8:18 PM
Subject: Re:
GNUGK versions higher than 2.1.1 and dcc
41
I have a similar problem with versions higher then 2.2.1.
After 5 sec of conversation the call is dropped. I couldn't manage to
fix
the problem by altering the configuration file.
Regards,
Jove
----- Original Message -----
From: Bahram S. Biria
To: openh323gk-users@xxxxxxxxxxxxxxxxxxxxx
Sent: Saturday, November 19, 2005 6:36 PM
Subject:
GNUGK versions higher than 2.1.1 and dcc
41
Hi folks,
When I
use any version higher than 2.2.1 I can see many call rejects with cause code
41 which is not appear with version 2.1.1.
I checked almost all the
versions 2.2.1, 2.2.2, 2.2.3 and 2.2.4.
Why I dont
use the 2.2.1 then? Because the CLIRewrite feature has come into the scene
since version 2.2.2.
Has anyone experienced the same
problem? Does anyone have any heads up on this?
Cheers,
Bahram.
-------------------------------------------------------
This
SF.Net email is sponsored by the JBoss Inc. Get Certified
Today
Register for a JBoss Training Course. Free Certification
Exam
for All Training Attendees Through End of 2005. For more info
visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________________
Posting:
mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx
Archive:
http://sourceforge.net/mailarchive/forum.php?forum_id=8549
Unsubscribe:
http://lists.sourceforge.net/lists/listinfo/openh323gk-users
Homepage:
http://www.gnugk.org/
|
