Configure A H.323 Voip Connection; Activate Cs Context Configuration - Patton electronics SmartNode Series Software Configuration Manual

23 • CS context overview
The call signaling method specifies the call setups to the destination SmartNode. In ISoIP there is one configu-
ration methods, 'direct call signaling'. This means that every ISoIP call needs the IP address of the destination
SmartNode. Therefore in every ISoIP interface a remote IP address is specified. For examples and information
on how to configure direct call signaling for ISoIP voice connections, refer to chapter 20,
tion" on page 235.
Configure a H.323 VoIP Connection
To configure a H.323 connection you have to specify the voice codec selection, the call signaling method and
Q.931 tunneling.
Configuring the voice codec for an H.323 connection differs from the procedure used for ISoIP. In the H.323
gateway a list of all possible codecs which we want to use we have to specified, and in the H.323 interface one
of these listed codecs we have to specified. If no codec is specified in the H.323 interface, during a call setup
the first codec listed in the H.323 gateway which matches with the remote SmartNode is taken. For informa-
tion how to configure the codecs for a H.323 connection refer to chapter 20,
235.
In H.323 there are two call signaling methods, 'direct call signaling' and 'gatekeeper routed call signaling'.
Direct call signaling works in the same way as ISoIP. Gatekeeper routed call signaling uses a gatekeeper to find
the destination address. For examples and information on how to configure direct call signaling on H.323
voice connections, refer to chapter 20,
call signaling on H.323 voice connections refer to chapter 20,
Q.931 tunneling is able to support ISDN services and Q.SIG over an IP network. In ISoIP Q.931 tunneling is
always enabled. To configure Q.931 tunneling on a H.323 connection, refer to chapter 20,
tion" on page 235.
Activate CS Context Configuration
After configuring the CS context and all its components the configuration must be activated. This includes
binding the PSTN interfaces to the ISDN ports and enabling the gateways, ISDN ports and the CS context.
In order to become functional, each PSTN interface must be bound to one or more ISDN ports from which it
receives incoming calls and to which it forwards outgoing calls. Note that there is a difference between IP inter-
faces and Ethernet ports. In the IP context the Ethernet port is bound to the IP interface, in the CS context
the PSTN interface is bound to the ISDN port! After binding to become active the ISDN port must be
enabled.
To bind the PSTN interfaces to ISDN ports refer to chapter 20,
enable the ISDN ports refer to chapter 27,
H.323 gateway must be enabled. Additionally the H.323 gateway must be bound to a specific IP interface. For
more information refer to chapter 27,
In order to become active the CS context must be enabled. When recovering from the shutdown status, the CS
context and Session Router configuration is checked and possible errors are indicated. The Session Router
debug monitor can be enabled to show the loading of the CS context and Session Router configuration. Smart-
Ware offers a number of possibilities to monitor and debug the CS context and session router configurations.
For example the Session Router debug monitor enables you follow the sequence of tables and functions exam-
ined by the Session Router for each call setup. Refer to chapter 27,
an introduction to the configuration debugging possibilities in SmartWare.
284
"DHCP configuration"
"ISDN port configuration"
"ISDN port configuration"
SmartWare Software Configuration Guide
"DHCP configuration"
on page 235. To configure gatekeeper routed
"DHCP configuration"
"DHCP configuration"
on page 341. Likewise the ISoIP or
on page 341.
"ISDN port configuration"
CS context configuration task list
"DHCP configura-
on page
on page 235.
"DHCP configura-
on page 235 and to
on page 341 for