[ previous ] [ next ] [ threads ]
 To :  yate@v...
 From :  Paul Chitescu <paulc@v...>
 Subject :  Re: [yate] H323 Gatekeeper and Prerouting
 Date :  Fri, 23 Oct 2009 17:23:25 +0300

When Yate acts as a gatekeeper 
YateGatekeeperServer::TranslateAliasAddressToSignalAddress will use a 
call.route message to find out if the call is to be handled internally by the 
gatekeeper, by the associated endpoint or rejected. The only available 
information is the alias of the called party so the prerouting is skipped 
entirely. Absolutely no information is available about the caller or other 
parameters of the call.

If this request is rejected or handled by the internal gatekeeper you won't 
see another trace of it.

The same code is called in a hierarchy of gatekeepers when receiving a LRQ 
(location request). In the end the call may not establish a call leg in Yate 
or there may not be a call at all.

If the call is handled by the endpoint (destination is known but not 
registered on H.323) a call leg will be created and you will get another 
call.preroute, call.route etc.



On Friday 23 October 2009 16:53:24 Koochy Black wrote:
> Hi,
> I've seen some strange behaviour of my Yate System. I'm running a test
> Yate Server Rev. 2760, there is a problem when using it as a H323
> Gatekeeper. When I disable the Gatekeeper, Yate always calls
> Call.Preroute, routing is done in mysql, as I told him, but when I
> enable the Gatekeeper and start a H323 Call, Yate is not making
> Call.Preroute anymore.
> I've tried the context option in h323chan.conf
>     context=default
> Do some have hint for me?
> Thanks in Advance, best regards
>        koochy