[asterisk-users] 00h323 cant get gatekeeper to connect

[Michelle Dupuis]

I'm still awaiting detailed Avaya config info, but I have learned more.
Hopefully someone will have some useful input to help me out..

When we try to connect the Asterisk box directly to the Avaya (bypass the
Gatekeeper/CLAN), we get this error in the ooh323 log:
ERROR:Failed to connect to remote destination for transmit H2250 channel

When we try to connect the Asterisk box to the Avaya Gatekeeper/CLAN we get
this error:
ERROR:No Gatekeeper ID present in received GKConfirmed message

Our ooh323.config is:
[general]
port=1719
bindaddr=99.197.126.160
faststart=yes
h245tunneling=yes
gatekeeper=99.197.126.12 
h323id=ObjSysAsterisk
callerid=asterisk
gateway=yes
progress_setup = 8
progress_alert = 8
logfile=/logs/ooh323
 
[Avaya]
type=peer
context=entry
ip=99.197.126.19
disallow=all
allow=ulaw
canreinvite=no
dtmfmode=rfc2833
port=1720

Can anyone see an obvious flaw?
I know the Avaya setup as three boxes (CLAN, MedPro, and main box).  The
h323 gatekeeper IP should obviously be the CLAN, but to what IP should the
peer IP point?

Thanks
MD

________________________________

From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Magnus
Benngård
Sent: Wednesday, March 10, 2010 1:53 PM
To: Asterisk Users List
Subject: Re: [asterisk-users] 00h323 cant get gatekeeper to connect



hmmm... will be hard to help u without u having access... will do my best.
Here is my ooh323.conf anyway...


sip:/etc/asterisk# cat ooh323.conf
[general]
bindaddr=213.88.138.183
port=5088 <--- Port for "incoming call" defined in "signal-group"
context=inputinterior.se
dtmfmode=rfc2833
disallow=all
allow=alaw:40 <--- Skip :40 and just stay with ulaw
tracelevel=6

[Avaya]
type=friend
context=inputinterior.se
dtmfcodec=127 <--- I needed that for proper DTMF signaling
dtmfmode=rfc2833
ip=10.242.14.11 <--- IP to "my Avaya"
port=5088 <--- Port for "outgoing call" defined in "signal-group"

 

 

	I don't have access to the Avaya (client controlled) - but I will
ask for their config.  Does the Avaya allow dumping the config to a file?
(Or screen shots only?)
	Here's my ooh323.conf (IP's changed)
	 
	Thanks,
	MD
	 
	 
	[general]
	port=1720
	bindaddr=99.197.126.160
	faststart=yes
	h245tunneling=yes
	gatekeeper=99.197.126.12
	h323id=ObjSysAsterisk
	callerid=asterisk
	gateway=yes
	progress_setup = 8
	progress_alert = 8
	logfile=/logs/ooh323
	 
	[Avaya]
	type=peer
	context=entryBMW
	host=99.197.126.29
	disallow=all
	allow=ulaw
	canreinvite=no
	dtmfmode=rfc2833
	port=1720
	 
	
	 

________________________________

	From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Magnus
Benngård
	Sent: Wednesday, March 10, 2010 12:18 PM
	To: Asterisk Users List
	Subject: Re: [asterisk-users] 00h323 cant get gatekeeper to connect
	
	

	I am running Asterisk trunk with ooh323 towards an Avaya CM 3.1
without any problems. I need your ooh323.conf and all relevant CM config
(signal-group, trounk-group, ip-codec... ) before I can assist u. ;)

	On Wed, 10 Mar 2010 10:34:30 -0500, Michelle Dupuis wrote:

		I'm trying to connect an Asterisk 1.6 to an Avaya with
gatekeeper (CLAN).  When chan_ooh323 first loads it tries to establish a
connection with the gk but I it fails.  I have the following extract from
the ooh323 log.  Can anyone give some insight?
		 
		Thanks!  
		MD
		 
		23:02:59:045  Sent GRQ message
		23:02:59:045  GkClient Received RAS Message
		23:02:59:045  Received RAS Message = {
		23:02:59:045     gatekeeperReject = {
		23:02:59:045        requestSeqNum = {
		23:02:59:045           1
		23:02:59:046        }
		23:02:59:046        protocolIdentifier = {
		23:02:59:046           { 
		23:02:59:046  0 0 8 2250 0 5 }
		23:02:59:046        }
		23:02:59:047        rejectReason = {
		23:02:59:047           resourceUnavailable = {
		23:02:59:048              NULL
		23:02:59:048           }
		23:02:59:048        }
		23:02:59:048     }
		23:02:59:048  }
		23:02:59:048  Gatekeeper Reject (GRJ) message received
		23:02:59:048  Deleted GRQ Timer.
		23:02:59:048  Error: Gatekeeper Reject - Resource
Unavailable
		23:02:59:049  Error: Gatekeeper error. Either Gk not
responding or Gk sending invalid messages
		23:02:59:049  Error: Gatekeeper error detected. Closing
GkClient as Gk mode is UseSpecifcGatekeeper
		23:02:59:049  Destroying Gatekeep