Patton electronics SmartNode Series Software Configuration Manual page 329

SmartWare Software Configuration Guide
• Carriers Apple, Orange and Melon do not support ISDN data calls (PC with ISDN Terminal Adapter
behind PBX A)
• When calling through carrier "Melon" the CLI must not use the public number blocks of Site A and B
• Carrier "Orange" is to be used for national calls
• Carrier "Apple" is to be used for calls to mobile
The requirements for the Session Router can be summarized as:
• Route ISDN data calls to the local breakout
• Route inter-site calls to the opposite SmartNode (Node A to Node B and vice versa)
• Route international calls to Carrier "Melon"
• Provide a fallback for all VoIP calls on the local breakout
• Route local calls to the local breakout
• Route national calls to carrier "Orange"
• 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 63 shows the corresponding CS Context and Session Router elements in Node A:
Example
25 • Session router configuration
327