14.5.4.1. Initial Situation 
Key parameters:
|
Endpoint/Description
|
DN name/Phone number
|
IP address
|
|
DNS - service provider
|
iandc.training.com (domain name)
|
2.3.3.123
|
|
SIP registrar / proxy
|
sip.iandc.training.com
|
2.3.3.124
|
|
STNO carrier connection / SBC-WAN-1
|
+49180130100
|
3.3.3.1
|
|
STNO carrier connection / HG 3500-2
|
+49180130200
|
3.3.3.2
|
|
HG 3500 -1 (LAN)
|
1.40.11.82
|
|
|
SBC -1 (LAN)
|
1.40.11.89
|
HG 3500 via session border controller to SIP carrier
In this example, the scenario has changed as only one session border
controller (SBC) is switched between the SIP trunk gateway (HG 3500)
and service provider on the OpenScape 4000 -1 system. The SIP trunk gateway
is now configured with an IP address from the customer LAN (1.40.11.82).
The session border controller has two IP addresses, 1.40.11.89 in the
customer LAN and 3.3.3.1 in the service provider LAN.
A session border controller is recommended when using OpenScape 4000
SoftGates, to increase security. It has Network Address Translation (NAT)
and firewall functionality.
In case of AMO configuration in the OpenScape 4000-1, only the HG
3500 changes. In the HG 3500 WBM, the session border controller is configured
as the interface to the service provider (Outbound-Proxy). Of course,
the session border controller must also be configured.
The OpenScape 4000-1 system can be called from the OpenScape 4000-2
system using the digit pattern 0049180130100-xxxx.