Hi Teodor,
Here's that part of the log where I see the timer expiry. What surprises
me, though, is while the gateway has ISDN cards, I was actually making the
call thru the non-ISDN port.
2004/10/20 12:09:20.251 6 yasocket.cxx(610) 192.168.3.229:65318
32 bytes sent
2004/10/20 12:09:20.267 5 yasocket.cxx(699) ProxyRTP(0) 1
sockets selected from 2, total 2/0
2004/10/20 12:09:20.267 6 ProxyChannel.cxx(2481) RTP Forward
192.168.9.10:16874 to 192.168.3.229:65318
2004/10/20 12:09:20.268 6 yasocket.cxx(610) 192.168.3.229:65318
32 bytes sent
2004/10/20 12:09:20.271 5 yasocket.cxx(699) ProxyRTP(0) 1
sockets selected from 2, total 2/0
2004/10/20 12:09:20.271 6 ProxyChannel.cxx(2467) RTP forward
192.168.3.229:65318 to 192.168.9.10:16874
2004/10/20 12:09:20.271 6 yasocket.cxx(610) 192.168.3.229:65318
32 bytes sent
2004/10/20 12:09:20.287 5 yasocket.cxx(699) ProxyRTP(0) 1
sockets selected from 2, total 2/0
2004/10/20 12:09:20.287 6 ProxyChannel.cxx(2481) RTP Forward
192.168.9.10:16874 to 192.168.3.229:65318
2004/10/20 12:09:20.288 6 yasocket.cxx(610) 192.168.3.229:65318
32 bytes sent
2004/10/20 12:09:20.291 5 yasocket.cxx(699) ProxyH(0) 1 sockets
selected from 4, total 4/0
2004/10/20 12:09:20.291 5 ProxyChannel.cxx(472) H245s Reading from
192.168.9.10:11753
2004/10/20 12:09:20.291 4 ProxyChannel.cxx(2018) H245 Received:
indication terminalCapabilitySetRelease {
}
2004/10/20 12:09:20.292 4 ProxyChannel.cxx(2079) H245 Indication:
terminalCapabilitySetRelease
2004/10/20 12:09:20.292 6 yasocket.cxx(610) 192.168.3.229:63275
6 bytes sent
2004/10/20 12:09:20.292 5 yasocket.cxx(699) ProxyRTP(0) 1
sockets selected from 2, total 2/0
2004/10/20 12:09:20.292 6 ProxyChannel.cxx(2467) RTP forward
192.168.3.229:65318 to 192.168.9.10:16874
2004/10/20 12:09:20.292 6 yasocket.cxx(610) 192.168.3.229:65318
32 bytes sent
2004/10/20 12:09:20.292 5 yasocket.cxx(699) ProxyH(0) 1 sockets
selected from 4, total 4/0
2004/10/20 12:09:20.292 5 ProxyChannel.cxx(472) Q931d Reading from
192.168.9.10:1720
2004/10/20 12:09:20.292 3 ProxyChannel.cxx(687) Q931d Received:
ReleaseComplete CRV=12350 from 192.168.9.10:1720
2004/10/20 12:09:20.293 4 ProxyChannel.cxx(634) Q931 Received: {
q931pdu = {
protocolDiscriminator = 8
callReference = 12350
from = destination
messageType = ReleaseComplete
IE: Cause - Recovery from timer expiry = {
81 e6 ..
}
IE: User-User = {
25 80 06 00 08 91 4a 00 04 11 00 11 00 02 b2 1d %.....J.........
d2 5a 85 16 3a 56 34 34 34 34 ef 00 00 10 80 01 .Z..:V4444......
00 .
}
}
h225pdu = {
h323_uu_pdu = {
h323_message_body = releaseComplete {
protocolIdentifier = 0.0.8.2250.0.4
callIdentifier = {
guid = 16 octets {
02 b2 1d d2 5a 85 16 3a 56 34 34 34 34 ef 00 00
....Z..:V4444...
}
}
}
h245Tunneling = FALSE
}
}
}
2004/10/20 12:09:20.293 6 RasTbl.cxx(1861) GK Removing
callptr: 02 b2 1d d2 5a 85 16 3a 56 34 34 34 34 ef 00 00
2004/10/20 12:09:20.293 6 yasocket.cxx(610) 192.168.1.252:1334
257 bytes sent
2004/10/20 12:09:20.294 1 RasTbl.cxx(1900) CDR|1|02 b2 1d d2 5a
85 16 3a 56 34 34 34 34 ef 00 00|11|Wed, 20 Oct 2004 12:09:09 +0800|Wed, 20
Oct 2004 12:09:20 +0800|192.168.3.229:63274|8650_epmax
r|192.9.90.2:1720|8649_epmaxr|19017514800:dialedDigits|00026b010865:h323_ID=
63141002:dialedDigits|ePmax;
2004/10/20 12:09:20.294 2 gkacct.cxx(936) GKACCT Successfully
logged event 2 for call no. 1
2004/10/20 12:09:20.294 6 yasocket.cxx(610) 192.168.3.229:63274
50 bytes sent
2004/10/20 12:09:20.294 5 yasocket.cxx(699) RasServer 1 sockets
selected from 2, total 2/0
2004/10/20 12:09:20.294 4 RasSrv.cxx(183) RAS Receiving on
192.168.1.100:1719(U)
2004/10/20 12:09:20.295 2 RasSrv.cxx(152) RAS Read from
192.168.9.10:49727
-----Original Message-----
From: openh323gk-users-admin@xxxxxxxxxxxxxxxxxxxxx
[mailto:openh323gk-users-admin@xxxxxxxxxxxxxxxxxxxxx] On Behalf Of Teodor
Georgiev
Sent: Wednesday, October 20, 2004 8:32 PM
To: openh323gk-users@xxxxxxxxxxxxxxxxxxxxx
Subject: Re: Disconnection due to timer expiry
Where do you see that message ?
This is given if the ISDN T310 times expires. It is very
common to the T303 timer.
After the calling endpoints sends a SETUP message, T303
timer is started. Until the T303 timex expires (by default 4sec),
the calling party must receive either ALERTING, CALL PROCEEDING
or CONNECT message.
You have to either increse the timer value or troubleshoot and see
why the calling endpoint is not getting a message.
On Wednesday 20 October 2004 15:04, Abano, Fernando wrote:
> Cause - Recovery from timer expiry
---
Best regards,
Teodor Georgiev
Information Services Plc.
Tel : +359 2 9656208
Mobile: +359 887 508989
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________________
List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx
Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549
Homepage: http://www.gnugk.org/
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________________
List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx
Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549
Homepage: http://www.gnugk.org/
