Inalp Networks SmartWare Release 2.10, Software Configuration Manual

Page: 293 / 357

Gateway Configuration 293
SN(gw-h323)[h323]# gatekeeper-discovery auto
SN(gw-h323)[h323]# alias h323-id Berne1
SN(gw-h323)[h323]# alias e164 007
SN(gw-h323)[h323]# alias e164 *5
SN(gw-h323)[h323]# alias e164 19421
SN(gw-h323)[h323]# ras
30.5 H.323 RAS Gatekeeper Registration Type
H.323 gatekeepers usually allow configuring the registration type (terminal or gateway) of the
registrant (RAS). For administrative purposes it may be desirable to change the registration type on
the gatekeeper. The gateway however needs to register with the same registration type; registration
type mismatch may result in registration failure.
Procedure
Configure the registration type of the registration with the gatekeeper
Mode
Gateway H.323
Command Purpose
Step 1 node (gw-h323)[h323]#terminal-type
{terminal | gateway }
Set the registration type of the
gatekeeper registration. Default
registration type is gateway.
Example: Configuring RAS registration type
The following example shows how to configure the RAS registration type.
SN(cfg)#gateway h323 h323
SN(cfg)#terminal-type gateway
30.6 Enable Q.931 Tunneling for an H.323 connection
Q.931 tunneling is able to support ISDN supplementary services which use D-channel broadcast
messages, such as call back and call waiting services. In ISoIP Q.931 tunneling is always enabled, in
H.323 it must be enabled or disabled explicitly.
The three different tunneling options are provided in order to achieve best interoperability with
certain H.323 gateways. All three tunneling options work between two SmartNode. Depending on
the tunneling option used the set of services provided may differ. The tunneling option isoip-sp has
some restrictions when operated solely between two SmartNodes (due to the protocols asymmetry).
The default tunneling option is isoip-2. When the peers in the H.323 network are SmartNodes (no
third party gateways) using the tunneling option isoip-2 will afford the best results.
Note: Most gatekeepers do not support tunneled Q.931 messages. When using a gatekeeper without
Q.931 tunneling support make sure that RAS is disabled (no ras).
Note: Irrespective of the tunneling option (isoip-2, isoip-sp, isoip-ig) Q.931 tunneling is automatically
switched off if the H.323 peer (terminal, gateway) does not support tunneling (on a per call basis). In
such cases the call will be established with ‘plain’ H.323 (without the services afforded by tunneling).
Procedure
To enable Q.931 tunneling in H.323 and select the appropriate tunneling option.
Software Configuration Guide Release 2.10, Revision 1.00