Page History
| Panel | ||||
|---|---|---|---|---|
In this section:
|
This article describes the steps necessary to configure the
| Spacevars | ||
|---|---|---|
|
Use Case Scenario
A typical use case scenario for the Multiple IP Interface support is:
...
| Deck of Cards | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||
|
| Pagebreak |
|---|
Transformation Table
There are 4 different transformations used in this exerciseCreate four different transformation tables (for details, refer to Managing Transformation Tables):
- Translation table for OCS (1xxx) extensions
| Panel | |||||||
|---|---|---|---|---|---|---|---|
| |||||||
|
- Translation table for LAN-1 (2xxx) extensions
...
| borderStyle | none |
|---|
...
| 0 | Figure |
|---|---|
| 1 | 2xxx Transformation |
...
- Translation table for LAN-2 (5xxx) extensions
...
| borderStyle | none |
|---|
...
| 0 | Figure |
|---|---|
| 1 | 5xxx Transformation |
...
- Translation table for PSTN (3xxx) extensions
...
| borderStyle | none |
|---|
...
...
| 0 | Figure |
|---|---|
| 1 | 3xxx Transformation |
...
| Pagebreak |
|---|
Call Routing Tables
There are 3 Create three different Call Routing Table entries used in this exercise(for details, refer to Managing Call Routing Tables):
...
- Routing Calls from OCS Endpoints
...
| borderStyle | none |
|---|
- Routing Calls
...
...
- from Multiple IP Endpoints (LAN-1 and LAN-2 endpoints)
...
...
- Routing Calls
...
...
- from
...
| borderStyle | none |
|---|
...
- PSTN Endpoints
...
| Pagebreak |
|---|
Signaling Groups
Create four different Signaling Groups
...
| borderStyle | none |
|---|
(for details, refer to Managing Signaling Groups):
...
- Signaling Groups for OCS
...
...
- Signaling Groups for LAN-1 endpoints
...
| borderStyle | none |
|---|
...
- Signaling Groups for LAN-
...
- 2 endpoints
Signaling Group for PSTN endpoints
The LAN-2 Signaling Group
| Pagebreak |
|---|
Signaling Groups for LAN-2 endpoints
This signaling group refers to the IP subnet used between SBC and the SIP trunking provider. There are two subcases here.
...
If there is no NAT device between SBC and the SIP-trunking peer, then NAT Traversal must be set to NONE as shown below:
| Panel | |||||||
|---|---|---|---|---|---|---|---|
| |||||||
|
| Pagebreak |
|---|
Signaling Group for PSTN endpoints
| Panel | |||||||
|---|---|---|---|---|---|---|---|
| |||||||
|
| Pagebreak |
|---|
.
Additional Configuration step for
| Spacevars | ||
|---|---|---|
|
...
The previous steps complete the necessary configuration requirements for implementing the Multiple IP feature on the
| Spacevars | ||
|---|---|---|
|
| Spacevars | ||
|---|---|---|
|
| Spacevars | ||
|---|---|---|
|
...
| icon | false |
|---|---|
| title | Note |
For details, refer to Managing Static IP Route Tables.
All end-points located in a private or public network must be reachable through a next-hop gateway, as driven by the network environment.
...
| 0 | Figure |
|---|---|
| 1 | Modifying Ethernet IP |
| 3 | Modifying Ethernet IP |
...
| Pagebreak |
|---|
Overview
Content Tools