Inalp Networks SmartWare Release 2.10, Software Configuration Manual, Page: 262 / 357

262 Session Router Configuration
• Route mobile calls to carrier “Apple”
• Calls from “local_ba”, “node_b” and “node_c” are forwarded directly to “pbx_a”
The remainder of this example will focus on the configuration for Node A. The configuration for
Node B can be built accordingly. Node C has an even simple configuration.
It is a good idea to specify the required Session Router elements and names before starting the
configuration. A sketch may be helpful:
• Bearer Capability table named "ISDNservice", needed for requirement 1.
• Called Party Number table named "dest_a", needed for requirement 2, 3, 6 and 7
• CAC insertion for Apple "CACapple", needed to add Carrier Access Code for "Apple"
•
CAC insertion for Orange "CACorange", needed to add Carrier Access Code for "Orange"
•
CLI replacement for Melon "CLImelon", needed to add Carrier Access Code for "Melon"
• PSTN interfaces "pbx_a" and "local_ba", needed for requirement 4, 5 and 8.
• H.323 interface "node_b", needed for requirement 2.
• ISoIP interface "node_c", needed for requirement 3.
Figure 26-3 shows the corresponding CS Context and Session Router elements in Node A:
Figure 26-3: CS Context and Session Router elements
We assume that the CS interfaces have already been created and configured. So we can start directly
with the Session Router elements.
Since the command sequence is quite long it is useful to create the configuration offline and
download it using TFTP. Note in the following lines the prompt is omitted as in a configuration file
and for better readability.
#-------------------------------------------------------------
Software Configuration Guide Release 2.10, Revision 1.00