Michael J. Tubby G8TIC
2007-Feb-06 17:16 UTC
[asterisk-users] ooh323 drops registration with Cisco IOS GateKeeper - bug or config issue?
All, I'm running (attempting to) ooh323 with Asterisk and a Cisco 2621XM router operating as a H.323 GateKeeper, however when I bring the Asterisk box up it registers successfully with the GateKeeper (exchanges GRQ/GCF, then RRQ/RCF) it notes the GateKeeper supports keepalive at 300 seconds, when it gets to time to re-register its sends an RRQ again and gets rejected with RRJ (unspecified reason) and so closes the session. At this point the H.323 session is lost and never retried. The set up is as follows: Asterisk Box: RedHat/Fedora Core 3, Asterisk 1.2.14 (built from source), ooh323 rev 0.8.2 from Asterisk-Addons-1.2.5 Cisco GateKeeper: 2621XM router with c2600-jsx-mz.123-22.bin Config on Asterisk box: ; Objective System's H323 Configuration example for Asterisk ; ooh323c driver configuration ; ; [general] section defines global parameters ; ; This is followed by profiles which can be of three types - user/peer/friend ; Name of the user profile should match with the h323id of the user device. ; For peer/friend profiles, host ip address must be provided as "dynamic" is ; not supported as of now. ; ; Syntax for specifying a H323 device in extensions.conf is ; For Registered peers/friends profiles: ; OOH323/name where name is the name of the peer/friend profile. ; ; For unregistered H.323 phones: ; OOH323/ip[:port] OR if gk is used OOH323/alias where alias can be any H323 ; alias ; ; For dialing into another asterisk peer at a specific exten ; OOH323/exten/peer OR OOH323/exten@ip ; ; Domain name resolution is not yet supported. ; ; When a H.323 user calls into asterisk, his H323ID is matched with the profile ; name and context is determined to route the call ; ; The channel driver will register all global aliases and aliases defined in ; peer profiles with the gatekeeper, if one exists. So, that when someone ; outside our pbx (non-user) calls an extension, gatekeeper will route that ; call to our asterisk box, from where it will be routed as per dial plan. [general] ;Define the asetrisk server h323 endpoint ;The port asterisk should listen for incoming H323 connections. ;Default - 1720 ;port=1720 ;The dotted IP address asterisk should listen on for incoming H323 ;connections ;Default - tries to find out local ip address on it's own bindaddr=0.0.0.0 ;This parameter indicates whether channel driver should register with ;gatekeeper as a gateway or an endpoint. ;Default - no gateway=yes ;Whether asterisk should use fast-start and tunneling for H323 connections. ;Default - yes ;faststart=no ;h245tunneling=no ;H323-ID to be used for asterisk server ;Default - Asterisk PBX ;h323id=ObjSysAsterisk h323id=ASTERISK e164=100 ;CallerID to use for calls ;Default - Same as h323id callerid=ASTERISK ;Whether this asterisk server will use gatekeeper. ;Default - DISABLE ;gatekeeper = DISCOVER gatekeeper = 192.168.1.6 ;gatekeeper = DISABLE ;Location for H323 log file ;Default - /var/log/asterisk/h323_log ;logfile=/var/log/asterisk/h323_log ;Following values apply to all users/peers/friends defined below, unless ;overridden within their client definition ;Sets default context all clients will be placed in. ;Default - default context=default ;Sets rtptimeout for all clients, unless overridden ;Default - 60 seconds ;rtptimeout=60 ; Terminate call if 60 seconds of no RTP activity ; when we're not on hold ;Type of Service ;Default - none (lowdelay, thoughput, reliability, mincost, none) ;tos=lowdelay ;amaflags = default ;The account code used by default for all clients. ;accountcode=h3230101 ;The codecs to be used for all clients.Only ulaw and gsm supported as of now. disallow=all ;Note order of disallow/allow is important. allow=alaw allow=ulaw allow=gsm ; dtmf mode to be used by default for all clients. Supports rfc2833, q931keypad ; h245alphanumeric, h245signal. ;Default - rfc 2833 dtmfmode=rfc2833 [cisco-gk] type=peer ip=192.168.1.6 port=1720 context=from-h323 disallow=all allow=alaw allow=ulaw allow=gsm rtptimeout=60 dtmfmode=rfc2833 h323id=PABX trace of it disconnecting: [root@pabx asterisk]# cat h323_log ---------Date 02/06/07--------- 09:53:08:742 Signalling IP address is set to 0.0.0.0 09:53:08:742 Listen port number is set to 1720 09:53:08:742 Using local RAS Ip address 192.168.1.5 09:53:08:742 Gatekeeper Mode - RasUseSpecificGatekeeper 09:53:08:742 Gatekeeper IP:port set to - 192.168.1.6:1719 09:53:08:742 Enabled RFC2833 DTMF capability for end-point 09:53:08:742 H323 listener creation - successful 09:53:08:742 Creating CMD listener at 0.0.0.0:7575 09:53:08:742 CMD listener creation - successful 09:53:08:742 H.323 Endpoint Configuration is as follows: 09:53:08:742 Trace File: /var/log/asterisk/h323_log 09:53:08:742 FastStart - enabled 09:53:08:742 H245 Tunneling - enabled 09:53:08:742 MediaWaitForConnect - disabled 09:53:08:742 AutoAnswer - disabled 09:53:08:742 Terminal Type - 50 09:53:08:742 T35 CountryCode - 1 09:53:08:742 T35 Extension - 0 09:53:08:742 Manufacturer Code - 71 09:53:08:742 ProductID - objsys 09:53:08:742 VersionID - v0.8.2 09:53:08:742 Local signalling IP address - 0.0.0.0 09:53:08:742 H225 ListenPort - 1720 09:53:08:743 CallerID - ASTERISK 09:53:08:743 Call Establishment Timeout - 60 seconds 09:53:08:743 MasterSlaveDetermination Timeout - 30 seconds 09:53:08:743 TerminalCapabilityExchange Timeout - 30 seconds 09:53:08:743 LogicalChannel Timeout - 30 seconds 09:53:08:743 Session Timeout - 15 seconds 09:53:08:743 Gatekeeper Client Configuration: 09:53:08:743 Gatekeeper mode - UseSpecificGatekeeper 09:53:08:743 Gatekeeper To Use - 192.168.1.6:1719 09:53:08:743 H323 RAS channel creation - successful 09:53:08:743 Sent GRQ message 09:53:08:750 Gatekeeper Confirmed (GCF) message received. 09:53:08:750 Gatekeeper Confirmed 09:53:08:750 Sent RRQ message 09:53:08:760 Registration Confirm (RCF) message received 09:53:08:760 Gatekeeper supports KeepAlive, Registration TTL is 300 09:57:48:761 Sent RRQ message 09:57:48:766 Registration Reject (RRJ) message received. 09:57:48:766 RRQ Rejected - Undefined Reason 09:57:48:766 Error: Gatekeeper error. Either Gk not responding or Gk sending in valid messages 09:57:48:766 Error: Gatekeeper error detected. Closing GkClient as Gk mode is UseSpecifcGatekeeper 09:57:48:766 Destroying Gatekeeper Client 09:57:48:766 Closed RAS channel [root@pabx asterisk]# Any ideas whether this is a bug or a configuration issue? Regards Mike -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070206/b721c9c7/attachment.htm
Reasonably Related Threads
- Asterisk and Tandberg Gatekeeper
- -- Called 12127773456@OOH323 Segmentation fault (core dumped)
- Help sought: Asterisk H.323, Cisco IOS Gatekeeper(s) intra-zone call routing and TETRA
- Using ooh323 with Gatekeeper controlled dialling
- Configuring Asterisk as Gateway SIP-H.323 via ooh323