Re: 102 timer expiry and hooked calls.

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

 



> Make sure you're running signaling routed mode.
> 102 errors are often cause because of interop problems
> between H323v4 and earlier implementations.
> But in this case, the gatekeeper should have a log
> for the call anyway succeeded or failed.

> Also, tcp keepalive not working may suggest that
> you're in direct signaling mode.

this is my config. It seems ok to me.

GkRouted=1
H245Routed=1

[Proxy]
Enable=0

The thing is that when I close GnuGK, the hooked calls appear as 41
(network error) so there is a check that is made during shutdown but that
is not made during the call.


-------------------------
E-Mail powered by MadNet.
http://www.madnet.ro/



-------------------------------------------------------
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_ide95&alloc_id396&opÌk

_______________________________________________________

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


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

  Powered by Linux