search for: allowgkrouted

...t by root@boldsoft on a i686 running Linux I can make H323 call without any problem from X-Pro and from X-lite dead-air both end. My default h323.conf =============== [general] port = 1720 bindaddr = 0.0.0.0 disallow=all allow=g729 allow=g723 allow=alaw allow=ulaw allow=gsm gatekeeper = a.b.c.d AllowGKRouted = yes noFastStart = no noH245Tunneling = no noSilenceSuppression = no Modified h323.conf ============== [general] port = 1720 bindaddr = 0.0.0.0 disallow=all allow=g729 allow=g723 allow=alaw allow=ulaw allow=gsm gatekeeper = a.b.c.d AllowGKRouted = yes noFastStart = yes noH245Tunneling = yes no...

...do that with an IPNx. But get dead air. With chan_oh323 it's fine, all works. With chan_h323 => dead air. The configuration is GW to GW. This is my configuration from h323.conf: [general] port=1720 bindaddr=my.ipaddr dtmfmode=rfc2833 gatekeeper=DISABLE AllowGKRouted=no context=default [termination] type=peer host=some.ipaddr noFastStart=no noH245Tunneling=no noSilenceSuppression=yes progress_setup=3 progress_alert=8 progress_audio=yes disallow=all allow=ulaw Any Suggestion is welcome. Thanks! _____...

...245Tunnelling=no h245inSetup=no inBandDTMF=no silenceSuppression=no jitterMin=20 jitterMax=100 ipTos=none outboundMax=10 inboundMax=10 simultaneousMax=10 wrapLibTraceLevel=1 libTraceLevel=0 libTraceFile=stdout gatekeeper=200.69.192.252 gatekeeperPassword = secret name=xxxxxxxxxx secret=xxxxxxxxxx AllowGKRouted = yes gatekeeperTTL=100 userInputMode=TONE amaFlags=omit alias=50312049 allow=all prefcodec=G729A [50312049] type=friend context=50312049 gatekeeper=200.69.192.252 gatekeeperPassword = secret gwprefix=4 name=xxxxxxxx secret= xxxxxxxx alias=50312049 Please, may you help me?

.... Any ideas on what could be the problem ?? My asterisk configuration, debug and console output are as follow : SIP.CONF ====== [general] port = 5080 bindaddr = 10.10.1.170 context = to_GNUGK disallow=all allow=g729 H323.CONF ======= [general] port = 1720 allow = g729 gatekeeper = 64.80.103.12 allowgkrouted = yes context = to_SER EXTENSIONS.CONF ============ [general] static = yes writeprotect = yes [to_GNUGK]] exten => _.,1,Dial(h323/${EXTEN}@10.10.1.12:1720,60,C) [to_SER] exten => _.,1,Dial(SIP/${EXTEN}@10.10.1.170:5060,60) DEBUG File ========== Jul 15 16:14:10 DEBUG[65541]: Check for re...

...din H.323 Gatekeeper.... So Far, i got registerd the asterisk on the M$ Gatekeeper... here is the h.323 configuration: ; Open H.323 driver configuration ; [general] port = 1720 bindaddr = 0.0.0.0 allow=all ; turns on all installed codecs dtmfmode=rfc2833 gatekeeper = 62.225.189.250 AllowGKRouted = yes context=local ; [time] type=h323 e164=18102341212 context=local ; ;[det-gw] ;type=h323 ;prefix=1248,1313 ;context=detroit ; [202] type=user host=* context=incoming incominglimit=4 Here is the extensions.conf: debian:/etc/asterisk# cat extensions.conf [general] static=yes writeprotect=...

Hello folks. We are trying to interconnect an asterisk installation with a gnugk 2.0.5 installation to become able to use some H323 hardware that needs a gatekeeper (particulary an Ericsson WebSwitch 100). We have managed asterisk to dial H323 endpoints successfully (although calls are interrupted immediately after connection with "spawn extension exited non-zero"), but we could not

Hello every one, I have got a H323 gatekeeper for testing. The informations are something like this: account code: test01 gk ip address:192.168.10.12 I don't know how to set it in the h323.conf or oh323.conf, I have tried it for almost one day but I always got the error. Help me please. Regards. -------------- next part -------------- An HTML attachment was scrubbed... URL:

....conf that looks like this to be able to achieve this. ; The NuFone Network's ; Open H.323 driver configuration ; [general] port = 1720 bindaddr = 0.0.0.0 amaflags = default disallow=all allow=all ; turns on all installed codecs allow=g711 dtmfmode=rfc2833 gatekeeper = 200.84.48.85 AllowGKRouted = yes context=gateway [gw1] exten =>9999XXXXXXXXXXX,1,Dial(h323/${Exten:1}@217.199.177.152) [gw1] type=h323 prefix=9999 context=gateway So when I start asterisk with -vvvvvvgc the last part of the information looks like this [chan_h323.so] => (The NuFone Network's Open H.323 Channel...

...using X-Lite as SIP client, i have set up my h323.conf:<BR>[general]<BR>port = 1721<BR>bindaddr = 0.0.0.0<BR>tos = lowdelay<BR>dtmfmode = rfc2833<BR>context = Out<BR>noFastStart = yes<BR>noH245Tunneling = no<BR>gatekeeper = 01.23.45.67<BR>AllowGKRouted = no<BR>allow = all</P> <P>[NET1-BG]<BR>type=h323<BR>prefix=0<BR>context=Inc<BR><BR>and in my extensions.conf there's a line like this:<BR>exten =&gt; _0.,1,Dial(H323/0889811777,20)<BR>&nbsp;which i think should dial the phone...

Hello group, I am trying to register to a opengk h323 gatekeeper using chan_h323. The gatekeeper expects me to register a username like 31201234567@gatekeper.com with a password secret and an e164 of 31201234567. Thus I put the following in the config file: [general] gatekeeper=w.x.y.z. AllowGKRouted=yes [31201234567@gatekeer.com.com] type=h323 e164=31201234567 secret=geheim context=default However it looks like the gatekeeper doesn't like me and I expect the security to be the reason. Is there a way to specify how the password is communicated? or is plaintext the only supported way at...

Hi, I'm using asterisk with chan_h323 together with gnugk. chan_h323 and gnugk were recently compiled with pwlib-1.5.2 and openh323-1.12.2 as advised. When connecting asterisk directly by ohphone (without gatekeeper), everthing is fine. When using gnugk for usage control in routed mode, I find a funny situation in asterisk's H.323 debug: == New H.323 Connection created. --

...| | | H.323 SIP And I wanna configure a setup that the SIP terminal talk with the H323 terminal. For this I would like use the asterisk. My h323.conf file is like: [general] gatekeeper=10.11.2.80 AllowGKRouted=yes [H323Asterisk] type=h323 context=sip_provider prefix=113151,116462 [default] type=h323 context=default My sip.conf file is like: [default] context=default My extension file is like: exten=_1131517400,1,Dial(h323/1131517400@10.11.2.80,10) exten=_1131517401,1,Dial(h323/OPENH323GK@10.11.2.80,1...

...that an asterisk application (Astcc) answers H.323 calls from any terminal logged into the gatekeeper. I'm using asterisk's channels/h323 implementation, and I've configured the following in h323.conf: [general] port = 1720 bindaddr = AAA.BBB.CCC.DDD allow=all gatekeeper=XXX.YYY.ZZZ.AAA AllowGKRouted = yes context=default [prep] type=h323 e164=77 context=default noFastStart=yes Then, in extensions, I've added the following: in [default]: exten => prep,1,Answer exten => prep,2,DeadAGI(astcc.agi) exten => prep,3,Hangup Asterisk registers properly in the gatekeeper when it is start...

Hello, I'm trying to register with a gatekeeper using chan_h323, I have a Login, Password and a user (telephone) number, This is my h323.conf [general] port=1720 bindaddr=x.x.x.x (my fixed IP) gatekeeper=x.x.x.x (gk ip) allowgkrouted=yes allow=all [xx] (my login) type=h323 e164=111 (my assigned phone number) secret=1111 (my password) context=incoming I'm getting this error when trying to make a call (h.323 trace 1) 2:37.884 Transactor:814d8d0 h323trans.cxx(678) Trans admissionRequest rejected: callerNo...

...n opt cd /path/to/asterisk/channels/h323 make cd /path/to/asterisk make install This seemed to work fine, in /usr/lib/asterisk/modules/ I have a chan_h323.so and I created an /etc/asterisk/h323.conf file: [general] port = 1720 bindaddr = 0.0.0.0 disallow=all dtmfmode=rfc2833 gatekeeper = DISABLE AllowGKRouted = yes context=unauthenticated [test] type=friend host=209.237.227.185 context=termination incominglimit=10 accountcode=008 However, when I have the Asterisk at 209.237.227.185 push a call through via H323, the Asterisk on the receiving end of course does not bother to match the source IP, and dec...

...- The acutal IP address or hostname of your GK ;gatekeeper = DISABLE ; Tell Asterisk whether or not to accept Gatekeeper routed calls or not. Normally this should always be set to yes, unless you want to have finer control over wh ch users are allowed access to Asterisk. Default: YES ; AllowGKRouted = yes ; Default context gets used in siutations where you are using the GK routed model or no type=user was found. This gives you the ability to either play an invalid message or to simply not use user authentication at all. Thanks in advance. Pedro. -------------- next part -...

...ports. It seems to be running OK, but when i try to dial through h323, it segfaults I'm using X-Lite as SIP client, i have set up my h323.conf [general port = 1721 bindaddr = 0.0.0.0 tos = lowdelaydtmfmode = rfc2833 context = Out noFastStart = yes noH245Tunneling = no gatekeeper = 01.23.45.67 AllowGKRouted = no allow = all [NET1-BG] type=h323 prefix=0 context=Inc and in my extensions.conf there's a line like this: exten = _0.,1,Dial(H323/0889811777,20) which i think should dial the phone entered, no matter what number is dialed by the client (if it start with 0, of course). Anyone with sugge...

...decs ;disallow=g723.1 ; Hm... Proprietary, don't use it... allow=gsm ; Always allow GSM, it's cool :) ;allow=ulaw allow=alaw ;allow=g729 ; noFastStart=yes noH245Tunneling=yes noSilenceSuppression=yes ; jitter=20 ; dtmfmode=inband ; gatekeeper = 192.168.0.207 ; AllowGKRouted = yes ; context=outgoing ; [CAC-IP] ;our computer. type=h323 prefix=9,7,*,8 context=outgoing ; -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20031104/5d2ba009/attachment.htm

...- The acutal IP address or hostname of your GK ;gatekeeper = DISABLE ; ; ; Tell Asterisk whether or not to accept Gatekeeper ; routed calls or not. Normally this should always ; be set to yes, unless you want to have finer control ; over which users are allowed access to Asterisk. ; Default: YES ; ;AllowGKRouted = yes ; ; Optionally you can determine a user by Source IP versus its H.323 alias. ; Default behavour is to determine user by H.323 alias. ;UserByAlias=no ; ; Default context gets used in siutations where you are using ; the GK routed model or no type=user was found. This gives you ; the ability...

...as expecting. Here is my ooh323.conf, followed by the relevant portion of the h323_log: [general] port = 1720 bindaddr = 10.4.16.45 h323id = AsteriskVM e164 = 1200 callerid = Asterisk faststart = yes h245tunneling = yes gateway = no disallow=all allow=ulaw dtmfmode=rfc2833 gatekeeper = 10.4.48.15 AllowGKRouted = yes AcceptAnonymous = yes progress_setup = 3 progress_alert = 8 tunneling=none 11:27:28:163 Trace File: /var/log/asterisk/h323_log 11:27:28:163 FastStart - enabled 11:27:28:163 H245 Tunneling - enabled 11:27:28:163 MediaWaitForConnect - disabled 11:27:28:163 AutoAnswer - disabled...