[ previous ] [ next ] [ threads ]
 To :  yate@v...
 From :  Koochy Black <koochy@a...>
 Subject :  Re: [yate] gatekeeper
 Date :  Fri, 17 Jul 2009 20:07:19 +0200
Hi,
have you tried a user without a password?
You can have look at the console,
- change Log level in h323chan.conf
h323chan.conf
debug=10

- then start yate like
sudo logsave H323debug.log yate -vvvvvvvvvvvvvvvvv



Mohammed El Maâroufi schrieb:
> I did configure the regfile.comf with the H323 user, but when I try with a H323 client I get this message:" 2020 con't log to GK"
>
> BR
> Mohammed
>
> -----Original Message-----
> From: Koochy Black [mailto:koochy@a...] 
> Sent: vendredi 17 juillet 2009 10:10
> To: yate@v...
> Subject: Re: [yate] gatekeeper
>
> Hi,
>
> there are almost all infiormations on the web and in the conf files, but
> I'll give you a little help
>
> regfile.conf:
> ; Here you can declare user/clients with password for your System.
> [user1]
> password=user1pw
>
> h323chan.conf:
> [general]
> ; This section sets global variables of the implementation
> .....
> ; vendor: string: Vendor name
> vendor=TESTSERVER
> .....
> ; Use an external RTP module instead of the native OpenH323 RTP stack,
> which is
> ;  very cpu intensive. If no external RTP can be found it will fallback
> to the
> ;  native stack. The only external RTP now is yrtp (see the yrtpchan
> module).
> ; external_rtp: bool: default: yes
> external_rtp=yes
>
> ; Attempt to use native (OpenH323) RTP if external fails to start. This is
> ;  usefull only if the failure is caused by the external RTP module not
> ;  being loaded.
> ; fallback_rtp: bool: default: yes
> fallback_rtp=yes
>
> ; Perform direct RTP forwarding between client endpoints.
> ; You should enable faststart=on in the [ep] section and make sure fast
> start
> ;  is also supported and enabled on all clients.
> ; forward_rtp: bool: default: no
> forward_rtp=no
>
> [codecs]
> ......(make your change)....
>
>
> [ep]
> ; Control the endpoint operation of the module
>
> ; ep: bool: True if you want to activate the h323 endpoint
> ep = false
>
> ; gw: bool: Set to true if you want this endpoint to declare itself as
> gateway
> gw = false
>
> ; addr: string: IP address to bind the endpoint to, defaults to all
> interfaces
> addr=10.10.10.10
>
> ; port: int: TCP port on which the endpoint will listen
> port=1720
> ......
> ; faststart: bool: Enable Fast Start mode (offer media channels early)
> faststart=true
>
> ; h245tunneling: bool: Enable H.245 tunneling mode
> h245tunneling=true
>
> ; h245insetup: bool: Enable H.245 establishment early in call setup message
> ; Note that this setting may conflict with faststart so don't enable both
> ;h245insetup=false
>
> ; dtmfinband: bool: Wheter to decode inband DTMF (CPU intensive)
> ;dtmfinband = false
>
> ; silencedetect: keyword: Silence detection algorithm: none, fixed, adaptive
> ;silencedetect = none
>
> ; gkclient: bool: If h323 module endpoint should register to a gatekeeper
> gkclient = false
> ......
>
> [gk]
> ; If server is true the gatekeeper of yate will start. You must
> understand that
> ; the H323EndPoint and H323GateKeeper share the calls. So you can make a
> call
> ; to a registered endpoint of this gatekeeper even if in the [ep] section
> ; you haven't register the local H323EndPoint to the local
> H323Gatekeeper. In
> ; fact is not recomanded to register the local EndPoint to the local
> GateKeeper.
> ; The local H323EndPoint is used as proxy for calls to local non h323
> ; destinations. If you wanna call let's say tone/dial from a registered
> ; endpoint to the local gatekeeper, you must make a route in regexroute (or
> ; whatever you use) and then just dial the number.
> ; If you wanna call a registered endpoint you must use now as a module
> register
> ; since is the only module who can record prefixes right now.
>
> ; server: bool: Enable running a gatekeeper on the main endpoint
> server = true
>
> ; You must define the binding interfaces. Right now the multi hosted
> boxes don't
> ; work very well because OpenH323 mechanism, but we will fix that if someone
> ; have any problem.
> interface1=10.10.101.10
>
> ; port: int: Port on which the gatekeeper listens for connections
> port = 1719
>
> ; name: string: Identifier of the gatekeeper
> name = testGatekepper
>
> ; ttl: int: Registrations time to live in seconds, 0 to disable
> ttl = 30
>
> ; heartbeatdrop: bool: Drop calls for which the heartbeat timed out
> heartbeatdrop=true
>
> ; registeredonly: bool: Allow calls only with registered endpoints
> registeredonly=false
> .........
>
>
> As you can see you start the Gatekepper in ther [gk ] section in the
> h323chan.conf. If you make SIP<>H323 Proxying  you should declare in
> h323chan.conf 
> ep=true and gw=true in the [ep] (Endpoint) section. Also make sure you
> have some right routs in regexroute.conf .
>
> regexroute.conf:
> .....
> [default]
> ^10001$=wave/play//etc/yate/sounds/OhGod.mulaw
> ......
>
>
> Mohammed El Maâroufi schrieb:
>   
>> Hi all ;
>>
>>  
>>
>> It’s my 4 time that i’m asking you to explain me how can I configure
>> YATE as a gatekeeper, I’m a beginner and I need your help, once there
>> is a poor documentation in the web,
>>
>>  
>>
>> I need to configure yate as a gatekeeper, and register a H323 client
>> in this server
>>
>>  
>>
>> Thank you in advance
>>
>>  
>>
>> Mohammed;
>>
>>  
>>
>>  
>>
>>
>>
>> __________ Information from ESET Smart Security, version of virus
>> signature database 4251 (20090716) __________
>>
>> The message was checked by ESET Smart Security.
>>
>> http://www.eset.com
>>     
>
>
> __________ Information from ESET Smart Security, version of virus signature database 4252 (20090717) __________
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>
>
>  
>
> __________ Information from ESET Smart Security, version of virus signature database 4254 (20090717) __________
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>  
>
>