Re: weird 34 error..

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Note that if the calling/called party is registered with the gatekeeper
and is behind NAT, H245Route=0 will not take effect and H.245 will
be still routed through the gatekeeper.
Anyway, if both your gateways use H.245 tunneling, this option
is unrelevant.

----- Original Message ----- From: "Costin Manda" <siderite@xxxxxxxxx>
Sent: Wednesday, April 06, 2005 2:20 PM



  I changed the config to h245route=0 and now the calls no longer have
code 34, but end with error 16. The duration of the calls remains very
low, though, and I think it is a problem with the terminating gateway.

It was a fluke. After 10 calls, the dreaded 34 appeared again. H245Routed=0 had no effect.



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

_______________________________________________________

List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx
Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549
Homepage: http://www.gnugk.org/

[Index of Archives]     [SIP]     [Open H.323]     [Gnu Gatekeeper]     [Asterisk PBX]     [ISDN Cause Codes]     [Yosemite News]

  Powered by Linux