Inalp Networks SmartWare Release 2.10, Software Configuration Manual

Page: 220 / 357

220 CS Context Overview
Software Configuration Guide Release 2.10, Revision 1.00
• Furthermore we need two PSTN interfaces, each bound to an ISDN port. (This is described
in section 'Configure Call Routing')
24.2 CS Context Configuration Task List
The information that is needed for the CS entity configuration is distributed among several
configuration tasks, depending on its logical content.
For example, all related information that pertains to call routing is described in configuration task
'Configure Call Routing'. These configuration steps themselves can be described in one or more other
chapters. Thus, to configure call routing you have to refer to Chapter
25 , “ CS Interface
Configuration ” and Chapter 26 , “ Session Router Configuration ”.
This chapter shows you the correlation between the several CS configuration components. We
recommend that you perform the CS context configuration in the order that is described below.
Many of the parameters have default values which do not need to be changed. This means, that you
generally do not need perform all of the described configuration tasks. In such cases it is stated in the
text that you can skip the respective configuration task. If you are unaware of the default values
refer to Chapter 16, “Context CS Mode” in the SmartWare
Command Reference Guide .
• Plan the CS Configuration
• Configure General CS Settings
• Configure Call Routing
•
Configure Dial Tones (Advanced)
•
Configure Voice Over IP Settings (Advanced)
• Configure ISDN Ports
• Configure an ISoIP VoIP Connection
• Configure a H.323 VoIP Connection
• Activate CS Context Configuration
24.3 Plan the CS Configuration
There are many possible policies and factors that may influence the CS context configuration. It
depends on what your application is and how your network is configured. Several factors to
consider for planning your CS configuration are listed below:
•
Application / Network Scenario
• Peripheral devices, such as PBX or remote VoIP gateway.
• VoIP protocol (ISoIP or H.323); gatekeeper settings in the case of H.323
• Number and type of interface cards installed in your SmartNode(s)
•
Call routing
For an example see Figure 24-2, which depicts a remote office in an enterprise network. The example
concentrates on the SmartNode in the remote office. There is an ISDN phone, a personal computer, a
connection to the Public ISDN network and a connection to the IP backbone. The VoIP protocol used
is ISoIP with a codec G.711. A call is routed to the IP backbone as well as to the Public ISDN network
depending on its prefix and number length. This implies the following CS configuration:
• Because we are connected to the Public Switched Telephone Network, we get the clock-
source from the corresponding ISDN port and simultaneously synchronize the system time
of the SmartNode to the ISDN time. (Described in section 'Configure General CS Settings').
In general, please be careful from which location you get your clock source. If your clock for
packaging the ISDN voice frames is not synchronized with the remote ISDN clock, this may
result in bit errors. In case of fax applications not one page could be transmitted.
• We need two ISDN ports, the first one for the ISDN phone, the second one for the public
ISDN network. This is described in section 'Configure ISDN Ports'.