This trace message is generated when Q.931 Setup signalling message
is received from an enpoint without preceeding ARQ from this endpoint
(unregistered endpoint).
You can overcome this either:
*) by setting AcceptUnregisteredCalls=1
or
*) by setting AcceptNeigborsCalls=1 (this also means AcceptCallsFromParent=1)
Recently I found another issue:
EP1---GKC---GKP---EP2
GKC is a child gatekeeper, GKP is a parent gatekeeper. If I place a call from
EP1 to EP2 it works only for the first time. When I try to call the same EP for the second time,
GK is not sending ARQ to parent (it finds OZEP in the registration table and thinks
it is registered ep, so there is not need to send ARQ to the parent), just sends Setup
message directly. That results in call rejection from parent ("No CallRec found...").
This behaviour has been corrected in 2.2.
----- Original Message -----
From: "Ray Jackman" <ray@havenet.com>
Sent: Thursday, October 02, 2003 4:34 AM
> > The reason is that child GK is not sending ARQ to parent.
> > There are some issues with child/neighbor setup not working as expected
> > in gk 2.0.
> > You can try 2.2 - it has lots of improvements in this area.
> >
> thanks michael.
> well, i dont have either gatekeeper as a neighbor so there should be no lrq message issues. in
> this case im running 2.0.5 gk.
>
> i also have another gk using 2.0.6 but not tested this one.
>
> i also ask, then why would gw1 have problems to send calls to registered gw gw3 as it cant
> find its call rec either. can you recommend another config for me or do you still suggest that i
> change to 2.2. i was also only aware of 2.1 development so i will study this more.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
List: Openh323gk-users@lists.sourceforge.net
Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549
Homepage: http://www.gnugk.org/
