SupportResource CenterH3C XE 200 2000 IP PBXConfiguration
Chapters Download(618 KB)
Chapter 1 Location Server Configuration
1.2 Functionality and Features
1.3.2 Configuring Interface and Port Number
1.3.4 Enabling/Disabling an LS
1.3.5 Configuring Call-matching Criterion
1.3.6 Configuring Whether to Accept Requests from an Unknown Device
1.3.7 Configuring a PS Registered with an LS
1.3.8 Configuring a MS Registered with an LS
1.3.9 Configuring a Gateway Registered with an LS
1.3.10 Configuring an Office on an LS
1.4.1 Enabling/Disabling Random Selection
1.4.2 Configuring a PS Registered with an LS
1.4.3 Configuring the Information about the Gateway Registered with an LS
1.4.4 Configuring an Office Group on an LS
1.4.5 Configuring the Allowed Time Difference between LS and PS/MS
1.4.6 Configuring Number Substitution
1.5 Displaying and Debugging LS
Chapter 2 NAT/FW Tunnel Traversal
2.1.2 Introduction to Firewall
2.1.3 NAT/FW Tunnel Traversal Function Provided by XE IP PBXs
2.2 Basic NAT/FW Tunnel Traversal Configuration
Chapter 3 Configuration Examples
3.1 Integrated Implementation of LS and H.323 Gatekeeper
3.2 Separate Implementation of LS and H.323 Gatekeeper
3.3 Basic H.323 Routed Call Mode
3.4 Office Device Configuration
3.5 Integrated Implementation of LS and SIP Redirect Server
3.6 Integrated Implementation of LS and SIP Proxy Server
3.7 Separate Implementation of LS and SIP Proxy Server
3.8 H.323 Terminal Communicating with SIP Terminal in Common Call Mode
3.9 H.323 Terminal Communicating with SIP Terminal in Faststart Call Mode
3.10 Multiple Called Parties Simultaneously Ringing in a Hybrid Network
3.11 Multiple Called Parties Orderly Ringing
3.12 NAT/FW Tunnel Traversal Between Private and Public Networks
3.13 NAT/FW Tunnel Traversal Between Two Private Networks
Chapter 4 XE IP PBX Troubleshooting
4.1 Troubleshooting H.323 Gatekeeper
4.2 Troubleshooting SIP Servers
4.2.1 Troubleshooting SIP Proxy Server
4.2.2 Troubleshooting SIP Registration Server
4.2.3 Troubleshooting SIP Redirect Server
A location server (LS) stores device and number information, answers queries about the information from a process server (PS), and manages the media server (MS).
Figure 1-1 shows the architecture of the XE IP PBXs.
Figure 1-1 Architecture of the XE IP PBXs
A PS, LS and MS communicate with each other via call application interface (CAI) proprietary protocol interface. After receiving a register request from a gateway (the gateway in this manual refers to H.323 gateway and SIP user agent client, unless otherwise noted), the PS exchanges such messages as query, response, notification, and indication with the LS. And after receiving a call request from a gateway, the PS queries the LS for number information through CAI message.
The device information on an LS is configured by an administrator, while the number information on the LS is configured by an administrator or reported by gateways through PS.
l Uniformly assigning number resources
Number resource is traditionally assigned at the gateway side, and this method is not efficient. The feature of assigning number resource uniformly is designed to resolve this problem. By design, each gateway has a factory-set port number. Bund with the gateway’s ID, the port number is mapped to a number during configuration. By this means, the LS can implement number assignment, making it easy for maintenance.
This feature supports only POTS (plain old telephone service) users.
l Querying device information and sending a response
SIP Registrar or H.323 gatekeeper needs to gain the IP PBX’s device information from LS when authenticating register requests from the IP PBX. It sends requests of querying device information to LS, and the request carries gateway ID or address. Then the LS returns device information to the SIP Registrar or H.323 gatekeeper by sending a query response after the device information is retrieved.
l Querying a number and sending a response
Before sending a session request to a called number, a SIP proxy server or H.323 gatekeeper needs the called information corresponding to the number. It sends number query request to an LS, then the LS returns information corresponding to the number to the SIP proxy server or H.323 gatekeeper by sending a query response after the information is retrieved.
l Configuring PS information
You must configure the following PS information on the LS: PS ID (SIP Server or H.323 gatekeeper), the number of the port where the PS receives RAS packets, the number of the port where the PS receives SIP packets, the ID of the group to which the PS belongs, heartbeat password, whether multiplexing is enabled, whether tunneling is enabled, the relative capability value of the PS group, and the domain that the device belongs to.
l Querying PS information
By specifying a PS ID, you can query the information about the PS or list the information about all PSs, including: IP address and port number, ID and the ID of the group to which the PS belongs, heartbeat password, transmission mode for SIP packets, and register status.
l Configuring MS information
You need to configure MS information on the LS, including the MS ID, heartbeat password and language type that the MS supports.
l Configuring gateway information
You can configure the information of a gateway (SIP User Agent or H.323 gateway) registered with an LS, which includes the following information: gateway identifier, gateway type, whether a dynamic IP address is used, IP address and port number of the gateway, IP address and port number of H.323 gateway call signaling, device status, transport layer protocol of SIP UA, default route priority, static route number and priority, whether authentication is enabled, authentication password, manufacturer information, whether multiplexing is enabled, registering cycle, and so on.
& Note:
If calling number hiding is configured on a gateway acting as a SIP user agent, services related with the calling number may not work.
l Query gateway information
To query the gateway information, you can provide the identifier of the gateway; also you can list information about the gateway by device type.
l Configuring office device information
You need to configure the information of an office device configured on an LS, which includes: office device identifier, device type, device status, IP address and port number, static route number, default route priority, and whether multiplexing is enabled.
l Querying information about office device
To query the office device information, you can provide the identifier of the office device; also you can list information about the office device by device type.
l Configuring office group information
You need to configure the information of an office group on an LS, including office group identifier, area code, domain to which the office group belongs, static route, number substitution table, and so on.
l Querying information about office group
You can query the information of an office group by the office group identifier.
l Querying devices corresponding to a number
You can query the devices that support a specific number.
l Enabling/disabling LS functions
You can enable/disable an LS to meet different network requirements of PS and LS. If the PS function and LS function are enabled on the same XE IP PBX, you must enable the LS function. If the PS function and the LS function are enabled on different XE IP PBXs, you must disable LS function on the XE IP PBX serving as PS. If LS function was enabled on the PS IP PBX and now you have disabled it, all the dynamic information record will be lost on the LS, and new registrations and calls will fail, but the calls that have already been set up will not be affected, and the LS function should be enabled on the XE IP PBX serving as the LS.
l Specifying call processing method
You can specify the call mode (redirect call mode or routed call mode) for SIP calling or H.323 calling on the LS. In the redirect call mode, the PS registered with the LS works in redirect mode; and in the routed call mode, the PS works in proxy mode.
& Note:
When the SIP call mode is adopted, if CLIR (calling line identification restriction) is enabled on the gateway, services that related with calling line may work improperly.
l Querying statistics information about an LS
You can query the statistics information about an LS, including the statistics about the messages received/transmitted by internal and external modules, and error count.
The LS supports:
l Networking with H3C’s SIP Server and H.323 gatekeeper
l Networking with the H.323 gatekeeper from other vendors
l Management on SIP Server or H.323 gatekeeper
l Networking with H3C’s SIP devices and H.323 devices
l Dynamic IP gateways
l Management on gateways (including SIP user agent and H.323 gateway)
l CAI proprietary protocol
l When the XE 200 IP PBX functions as an LS, up to 1600 gateways, 3200 subscriber numbers and 3200 routes can be configured on the XE 200; at most eight PSs can be cascaded.
l When the XE 2000 IP PBX functions as an LS, up to 16000 gateways, 32,000 subscriber numbers and 32,000 routes can be configured on the XE 2000; at most eight PSs can be cascaded.
The following sections describe the basic configuration tasks:
l Configuring Interface and Port Number
l Configuring Call-matching Criterion
l Configuring Whether to Accept Requests from an Unknown Device
l Configuring a PS Registered with an LS
l Configuring a MS Registered with an LS
l Configuring a Gateway Registered with an LS
l Configuring an Office on an LS
Before configuring the LS, you need to enter LS view first.
Perform the following configuration in system view.
|
Operation |
Command |
|
Enter LS view |
location-server |
When XE IP PBX is configured as an LS, you must configure the IP address of the LS to that of the Ethernet interface of the XE IP PBX and specify an Ethernet interface that will be used. By default, the Ethernet interface for XE200 is “ethernet 0/0” (for XE2000 it is “GigabitEthernet 0/0”).
Caution:
If you configure an LS on a PS to work in remote mode, the IP address and the port number of the remote LS must be identical to the local ones.
Perform the following configuration in LS view.
Table 1-2 Configure the interface and port number used by the LS
|
Operation |
Command |
|
Configure the interface and port number used by the LS |
ls-config interface interface-type slot-number [ port port ] |
|
Restore the default configuration |
undo ls-config |
Call mode refers to the way PS works under the administration of an LS, including routed mode and redirect mode. The default call mode of a SIP Server or a gatekeeper is routed mode. You can configure the call mode of the gatekeeper and the SIP Server respectively. The PS transmits information between the calling party and the called party, and the call is placed under the control of the PS and the LS. In redirect mode, the PS directly responds with the IP address of the called party to the calling party (if the IP address of the called party is stored in the LS), and then the calling party calls the called party.
& Note:
For networks containing both H.323 and SIP devices, you need to set call mode of both SIP Server and gatekeeper as “routed” to achieve interworking between SIP and H.323 terminals.
Perform the following configuration in LS view.
|
Operation |
Command |
|
Configure call mode |
call-mode { h323 | sip } { redirect | routed } |
|
Restore the default call mode |
undo call-mode { h323 | sip } |
An LS is disabled by default. You need to enable an LS to implement the functions it provides.
Perform the following configuration in LS view.
Table 1-4 Enable/disable an LS
|
Operation |
Command |
|
Enable an LS |
start |
|
Disable an LS |
stop |
This command is used to configure call-matching criterion for called numbers.
Perform the following configuration in LS view.
Table 1-5 Configure call-matching criterion
|
Operation |
Command |
|
Configure the longest number at higher priority |
policy select-rule number-first |
|
Configure the priority number at higher priority |
policy select-rule priority-first |
The command is used to configure whether to accept requests from an unknown device.
Perform the following configuration in LS view.
Table 1-6 Configure whether to accept requests from an unknown device
|
Operation |
Command |
|
Configure to enable accepting requests from an unknown device |
policy unknown-device-admission enable |
|
Configure to disable accepting requests from an unknown device |
policy unknown-device-admission disable |
When acting as an LS, an XE IP PBX can manage multiple PSs. You must configure an IP address and a heartbeat password for each managed PS on the LS.
To configure managed PSs, you must enter LS-PS view first, where IP addresses and heartbeat passwords are configured.
If a specific LS-PS view already exists, you can enter it directly; if not, you must create a new PS first, and then enter the corresponding LS-PS view.
Perform the following configuration in LS view.
Table 1-7 Add/delete a PS or enter a PS view
|
Operation |
Command |
|
Add a PS or enter a PS view |
process-server device-id |
|
Delete a specified PS or all PSs |
undo process-server { device-id | all } |
& Note:
In the actual network configuration, the IDs for all gateway(s), PS(s) and office device(s) should be different.
The LS listens to the keepalive status message periodically sent by the PS to learn the PS’s keepalive status. To ensure a proper connection between the LS and the PS, the heartbeat password of the LS must be identical to that of the PS.
Perform the following configuration in LS-PS view.
Table 1-8 Configure the heartbeat password
|
Operation |
Command |
|
Configure the heartbeat password |
heartbeat password password |
|
Restore the default heartbeat password |
undo heartbeat password |
For configuration details, refer to the “Configuring MS Device Information in LS View” part of module “Media Server Operation”.
H.323 Gateway and SIP User Agent are both gateways, which connect to user phones or PBXs and are responsible for the conversion between different signaling protocols and media formats. The LS records information about these gateways for the PSs.
To configure gateways, you must create an LS-GW view first. You can perform the following:
l Adding a gateway or entering a gateway view
l Configuring the type of a gateway
l Specifying whether a gateway uses a dynamic IP
l Configuring the IP address of a gateway
l Configuring the port number of a gateway
l Configuring the IPv4 address of the call signaling for a gateway
l Configuring the call signaling port of a gateway
l Configuring the status of a gateway
l Configuring the transport layer protocol used by SIP UA
l Configuring the default route number priority of a gateway
l Configuring the static route number of a gateway
l Specifying whether a gateway needs to perform authentication
l Configuring the authentication password of a gateway
l Configuring the bearer capability type for a gateway
If a specific gateway view already exists, you can enter it directly; if not, you must create a new one first, and then enter it.
Perform the following configuration in LS view.
Table 1-9 Add a gateway or enter a gateway view
|
Operation |
Command |
|
Add a gateway or enter a gateway view |
gateway device-id |
|
Delete one or all gateways |
undo gateway { device-id | all } |
& Note:
In the actual network configuration, the IDs for all gateway(s), PS(s) and office device(s) should be different.
There are two gateway types: H.323 and SIP. The voice-processing method varies with the device type.
Perform the following configuration in LS-GW view.
Table 1-10 Configure the type of a gateway
|
Operation |
Command |
|
Configure the type of a gateway |
device-type { h323 | sip } |
|
Restore the default type |
undo device-type |
If you specify a gateway as a dynamic IP device, the LS updates the IP address dynamically with the latest one reported by the gateway when it registers with the LS, otherwise the LS cannot update the IP address of the gateway dynamically.
Perform the following configuration in LS-GW view.
& Note:
l If you use the manufacturer command to set the manufacturer of the gateway to other, the system will disable the dynamic update of the gateway’s IP address.
l After enabling the dynamic update of the gateway’s IP address with the dynamic-ip command, you cannot use the manufacturer command to change the manufacturer setting of the gateway; in addition, the ip-address, port, call-signal ip-address, and call-signal port commands become invalid.
Table 1-11 Specify whether a gateway uses a dynamic IP
|
Operation |
Command |
|
Specify whether a gateway uses a dynamic IP address |
dynamic-ip { disable | enable} |
|
Restore the default setting |
undo dynamic-ip |
The IP address of a gateway here is the one recorded on the LS. To ensure a proper connection, you must set the IP address of the gateway identical to the actual one on the gateway.
Perform the following configuration in LS-GW view.
Table 1-12 Configure the IP address of a gateway
|
Operation |
Command |
|
Configure the IP address of a gateway |
ip-address ip-address |
|
Delete the IP address of the gateway |
undo ip-address |
The port number of a gateway here is the one recorded on the LS. The LS communicates with the gateway through this port, and thus the port number configured on the LS for this gateway must be identical to the one configured on the gateway. For SIP, the port number is 5060 (default); and for H.323, it is 1719 (default).
& Note:
By default, the port number is 5060. When the dynamic-ip disable command is used and the type of the gateway is SIP, you can keep this number unchanged; while if the type is h323, you must use the port command to set the port number to 1719 (default).
Perform the following configuration in LS-GW view.
Table 1-13 Configure the port number of a gateway
|
Operation |
Command |
|
Configure the port number of a gateway |
port port |
|
Restore the default port number |
undo port |
By default, the gateway reports information to the LS dynamically. When you configure the gateway to register with the XE IP PBX in static mode, the gateway device type is H.323, and the gateway status is set to normal or forever-up, you must configure the IP address of the call signaling.
Perform the following configuration in LS-GW view.
Table 1-14 Configure the IPv4 address of the call signaling for a gateway
|
Operation |
Command |
|
Configure the IPv4 address of the call signaling for a gateway |
call-signal ip-address ip-address |
|
Delete the IPv4 address of the call signaling for a gateway |
undo call-signal ip-address |
& Note:
Different gateways can share the same IP address of call signaling, being identified by different port numbers. Refer to Configuring the port number of an office device for details.
By default, the gateway reports information to the LS dynamically. When you configure the gateway to register with the XE IP PBX in static mode, and the gateway status is set to normal or forever-up, you must configure the port number of the call signaling.
Perform the following configuration in LS-GW view.
Table 1-15 Configure the call signaling port of a gateway
|
Operation |
Command |
|
Configure the call signaling port of a gateway |
call-signal port port |
|
Restore the default setting |
undo call-signal port |
The status of gateway is the primary parameter of PS and LS gateways recorded by an LS. There are three states all together: normal, suspend, and forever-up.
In normal state, a gateway must successfully register to be able to interact with the PS registered with an LS. Besides, it needs to register regularly according to the timeout interval configured on the LS.
In suspend state, a gateway can neither register successfully, nor interact with any PS registered with an LS. PS will provide no service to this type of gateway.
In forever-up state, a gateway can utilize services provided by PSs and LSs without registration.
& Note:
To configure a gateway to forever-up state, you need to configure:
The PS which the gateway belongs to. For configuration of the PS, refer to the “Process Server Configuration Operation” module of this manual.
l IPv4 address and port of the call signaling for the gateway. Refer to Configuring the IPv4 address of the call signaling for a gateway and Configuring the call signaling port of a gateway.
Perform the following configuration in LS-GW view.
Table 1-16 Configure the status of a gateway
|
Operation |
Command |
|
Configure the status of a gateway |
device-status { forever-up attachedps ps-id | normal | suspend } |
|
Restore the default state |
undo device-status |
By default, the state of a gateway is normal.
& Note:
This configuration is unavailable to H.323 gateways.
A SIP gateway communicates a PS using a certain transport mode. XE IP PBX supports TCP and UDP transport modes. Three parameters are available: auto, tcp, and udp. In auto mode, TCP protocol is be used first; if it fails, UDP protocol will be used. As for tcp and udp modes, you must set a transport mode identical to the actual one. If you have no idea how data are transported, you can set the mode to auto.
Perform the following configuration in LS-GW view.
Table 1-17 Configure the transport layer protocol used by the gateway
|
Operation |
Command |
|
Configure the transport layer protocol to be used by a gateway |
transport {auto | tcp | udp } |
|
Restore the default transport layer protocol |
undo transport |
By default, UDP protocol is used when the gateway functions as the SIP user agent.
& Note:
When configuring simultaneous ringing for multiple called parties, you must configure the transport mode to tcp or udp using the transport command.
If you have not configured route priorities for the number resource of the gateway, you can use the default priority of the current gateway as the priority of number resource.
Perform the following configuration in LS-GW view.
Table 1-18 Configure the default route priority of a gateway
|
Operation |
Command |
|
Configure the default route priority of a gateway |
priority level |
|
Restore the default priority |
undo priority |
The default value of the route priority is 10. The larger the value is, the higher the priority will be.
When a user calls a number and you have set a static route number for a gateway or an office device configured on an LS, the request will be forwarded to the gateway or office device for query. When multiple numbers that comply with a certain rule are to be routed to the same device, you can configure a regular expression to match these static numbers to decrease the length of the LS’s routing table, improve the LS’ executing efficiency, and shorten the LS’ responding time.
& Note:
When using the regular expression to match the dialed number, the system automatically begins the match from the beginning of the regular expression. If the first judgment is true, the match goes on; otherwise, the match fails. You do not need to add a caret (^) at the beginning of the expression, because the system has added it by default. For details about the regular expression, refer to the Basic Configuration part of the H3C XE 200/2000 IP PBX Operation Manual.
Perform the following configuration in LS-GW view.
Table 1-19 Configure the static route number of a gateway
|
Operation |
Command |
|
Configure the static route number of a gateway |
prefix number |
|
Delete one or all static route numbers |
undo prefix { number | all } |
& Note:
When configuring the static route number, make sure that it does not conflict with the ONLY number, the automatic operator number and the group notification number. For detailed information, refer to the “Call Services Operation” module of this manual.
The LS can determine whether to authenticate register and call requests sent from the UA. If authentication is disabled, the UA can register with the registrar and place voice calls without authentication; if authentication is enabled, the UA must pass the authentication first.
& Note:
Authentication is currently available to SIP-supported devices. As for H.323 devices, it is a reserved parameter.
Perform the following configuration in LS-GW view.
Table 1-20 Specify whether a gateway needs to perform authentication
|
Operation |
Command |
|
Specify whether a gateway needs to perform authentication |
authentication { disable | enable } |
|
Restore the default setting |
undo authentication |
After you have configured authentication passwords on an LS and a gateway respectively, the PS will check whether the authentication password of the gateway is identical to that recorded on the LS when the gateway performs registration and initiates a call, so as to ensure the validity of the gateway identification.
& Note:
Authentication is currently available to SIP-supported devices only. As for H.323 devices, it is a reserved parameter. An authentication password is valid only when authentication is enabled, although it is configurable when authentication is disabled.
Perform the following configuration in LS-GW view.
Table 1-21 Configure the authentication password of a gateway
|
Operation |
Command |
|
Configure the authentication password of a gateway |
password password |
|
Restore the default authentication password |
undo password |
The bearer capability type of a gateway indicates the service type (bearer capability type) supported in the Q.931 header of setup messages sent to the terminating side when the gateway communicates with the trunking gateway.
Perform the following configuration in LS-GW view.
Table 1-22 Configure the bearer capability type for a gateway
|
Operation |
Command |
|
Configure the bearer capability type for the gateway |
bearer-capability { audio | video } |
|
Restore the default bearer capability type |
undo bearer-capability |
For an LS domain, office devices are devices that do not report device information but have reachable routes to the LS of this domain. The office device contains the number information needed by the LS, but the office device does not belong to the LS domain. The office device can be an H.323 gateway, gatekeeper, a SIP server, or a SIP user agent. Office devices outside an LS domain form one or several office groups, each containing multiple office devices. An office device must belong to some office group.
To configure an office on the LS, you must create an office group and enter LS-OFFICEGROUP view first. In this view, you can configure the office information including:
l Configuring the domain to which an office group belongs
l Configuring the static route number of an office group
l Adding an office device or enter an office view
In LS-OFFICEGROUP-OFFICE view, you can configure the following:
l Configuring the device type of an officeConfiguring the device type of an officeConfiguring the device type of an officeConfiguring the device type of an officeConfiguring the device type of an office
l Configuring the IP address of an office device
l Configuring the port number of an office device
l Configuring the transport layer protocol used by an office device
l Configuring default route number priority of the office device
l Configuring the status of an office device
l Configuring the bearer capability type for an office device
With the office-group command, you can enter office group view of the specified office group, or create the specified office group if it does not exist and then enter its office group view.
Perform the following configuration in LS view.
Table 1-23 Add an office group or enter an office group view
|
Operation |
Command |
|
Add an office group or enter an office group view |
office-group office-group-id |
|
Delete one or all office groups |
undo office-group { office-group-id | all } |
Refer to Creating a domain for the information about domain.
Perform the following configuration in LS-OFFICEGROUP view.
Table 1-24 Configure the domain to which the office group belongs
|
Operation |
Command |
|
Configure the domain to which the office group belongs |
belongto domain-id |
|
Specify that the office group belongs to the default-domain domain |
undo belongto |
By default, an office group belongs to the default-domain domain.
A static route number is a regular expression. When a user calls a number and you have set a static route number for a gateway or an office device configured on an LS, the request will be forwarded to the gateway or office device for query. When multiple numbers that comply with a certain rule are to be routed to the same device, you can configure a regular expression to match these static numbers to decrease the size of the LS’s routing table, improve the LS’ executing efficiency, and shorten the LS’ responding time.
Each static route number has a priority value, ranging from 0 to 1000 and defaulting to that of the office device. The greater value enjoys the higher the priority. You can configure an identical static route number for several different office devices (multiple called parties). If the priorities of the called numbers are the same, the corresponding telephones will ring simultaneously when the number is called. If the priorities are not the same, the telephones will ring orderly.
Perform the following configuration in LS-OFFICEGROUP view.
Table 1-25 Configure the static route number of an office group
|
Operation |
Command |
|
Configure the static route number of an office group |
prefix number |
|
Delete one or all static route numbers of an office group |
undo prefix { number | all } |
& Note:
When configuring the static route number, make sure that it does not conflict with the ONLY number, the automatic operator number and the group notification number. For detailed information, refer to the “Call Services Operation” module of this manual.
Caution:
The XE IP PBX does not support cyclic route check.
For example:
l On the LS A, map the static route number 8801 to the office PS B.
l On the LS in the LS domain where the PS B resides, map the static route number 8801 to PS C.
l On the LS in the LS domain where the PS C resides, map the static route number 8801 to PS D.
l …
l On the LS in the LS domain where the PS N-1 reside, map the static route number 8801 to PS N.
l On the LS in the LS domain where the PS N resides, map the static route number 8801 to a certain PS in the LS A domain.
After the above configurations are completed, cyclic route will occur, thereby reducing the network performance. Therefore, it is recommended not to perform such configurations.
If a specific LS-OFFICE view already exists, you can enter it directly; if not, you must create a new one first, and then enter it.
With the office command, you can enter office view of the specified office device, or create the specified office if it does not exist and then enter its LS-OFFICEGROUP-OFFICE view.
Perform the following configuration in LS-OFFICEGROUP view.
Table 1-26 Add an office device or enter an office view
|
Operation |
Command |
|
Add an office device or enter an office view |
office device-id |
|
Delete one or all office devices |
undo office { device-id | all } |
& Note:
In the actual network configuration, the IDs for all gateway(s), PS(s) and office device(s) should be different.
Currently used office devices fall into three categories: H.323 gatekeeper, H.323 gateway, and SIP device (including SIP server and SIP UA). The processing method used by an XE IP PBX depends on the device type.
Perform the following configuration in LS-OFFICEGROUP-OFFICE view.
Table 1-27 Configure the device type of an office
|
Operation |
Command |
|
Configure the device type of an office |
device-type { h323-gk | h323-gw | sip } |
|
Restore the default device type |
undo device-type |
By default, the type of an office device is SIP-grade device.
The IP address configured on the LS for this device must be identical to the actual one on the office device.
Perform the following configuration in LS-OFFICEGROUP-OFFICE view.
Table 1-28 Configure the IP address of an office device
|
Operation |
Command |
|
Configure the IP address of an office device |
ip-address ip-address |
|
Delete the IP address |
undo ip-address |
Here, the port number of an office is a piece of information about the office recorded on the LS. The LS sends voice call information through the port to the office device. You must ensure that the port number configured on the LS for an office device must be identical to the one configured on the office device.
Perform the following configuration in LS-OFFICEGROUP-OFFICE view.
Table 1-29 Configure the port number of an office device
|
Operation |
Command |
|
Configure the port number of an office device |
port port |
|
Restore the default port number |
undo port |
By default, the port number of the office device is 5060.
& Note:
If the type of the office device is SIP, you can keep this number unchanged; if the type is h323-gk, you must use the port command to set the port number to 1719; if the type is h323-gw, you must use the port command to set the port number to 1720.
& Note:
This configuration does not apply to H.323 office devices.
The office device communicates with the PS using a certain transport mode. XE IP PBX supports UDP and TCP transport modes. Three parameters are available: auto, tcp, and udp. In auto mode, TCP protocol is used first; if it fails, UDP protocol will be used. As for tcp and udp modes, you must set a transport mode identical to the actual one. If you have no idea how data are transported, you can set the mode to auto.
Perform the following configuration in LS-OFFICEGROUP-OFFICE view.
Table 1-30 Configure the transport layer protocol used by an office device
|
Operation |
Command |
|
Configure the transport layer protocol used by an office device |
transport { auto | tcp | udp } |
|
Restore the default transport mode |
undo transport |
The parameter defaults to udp.
& Note:
When configuring simultaneous ringing for multiple called parties, you must configure the transport mode to tcp or udp using the transport command.
If you have not configured route priorities for the number resource of the office device, you can use the default priority of the current office device as the priority of number resource.
Perform the following configuration in LS-OFFICEGROUP-OFFICE view.
Table 1-31 Configure default routing priority of the office device
|
Operation |
Command |
|
Configure default routing priority of the office device |
priority priority-level |
|
Restore the default priority |
undo priority |
The default value of the routing priority of an office device is 10. The larger the value, the higher the priority.
The state of an office device can be forever or normal. In forever state, no heartbeat message is exchanged between the PS and office device; while in normal state, heartbeat messages (register messages based on SIP) are exchanged between them.
Perform the following configuration in LS-OFFICEGROUP-OFFICE view.
Table 1-32 Configure the status of an office device
|
Operation |
Command |
|
Configure the status of an office device |
device-status { forever | normal } |
& Note:
The office device state can be configured as normal only when the peer device is also an XE IP PBX.
The bearer capability type of an office device indicates the service type (bearer capability type) supported in the Q.931 header of setup messages sent to the terminating side when the office device communicates with the trunking gateway.
Perform the following configuration in LS-OFFICEGROUP-OFFICE view.
Table 1-33 Configure the bearer capability type for an office device
|
Operation |
Command |
|
Configure the bearer capability type for the office device |
bearer-capability { audio | video } |
|
Restore the default bearer capability type |
undo bearer-capability |
As for multiple terminals with the same number and priority, if the random selection is disabled, multiple terminals respond to the call simultaneously; if enabled, the system selects a terminal randomly in the redirect call mode, while the system randomly arranges the order of the terminals to have them ring in turn in the routed call mode.
Perform the following configuration in LS view.
Table 1-34 Enable/Disable random selection
|
Operation |
Command |
|
Enable random selection |
policy random-selection enable |
|
Disable random selection |
policy random-selection disable |
|
Restore the default for the random selection |
undo policy random-selection |
By default, random selection is enabled.
Use the multiplex command to specify the multiplexing mode of a PS registered with an LS.
Perform the following configuration in LS-PS view.
Table 1-35 Specify whether to enable multiplexing
|
Operation |
Command |
|
Specify whether to enable multiplexing |
multiplex { disable | enable } |
|
Restore the default multiplexing setting |
undo multiplex |
Use the psgroup-id command to set the identifier of the group that to which a PS belongs.
Perform the following configuration in LS-PS view.
Table 1-36 Configure the identifier of the group to which the current PS belongs
|
Operation |
Command |
|
Configure the identifier of the group to which the current PS belongs |
psgroup-id group-id |
|
Delete the identifier of the group |
undo psgroup-id |
The user agent supports dynamic IP registration by when the information about the gateway manufacturer is H3C.
Perform the following configuration in LS-GW view.
Table 1-37 Configure the information about the gateway manufacturer
|
Operation |
Command |
|
Configure the information about the gateway manufacturer |
manufacturer { other | h3c } |
|
Restore the default manufacturer |
undo manufacturer |
The default manufacturer is h3c.
Use the multiplex command to specify the multiplexing mode of a gateway registered with an LS.
Perform the following configuration in LS-GW view.
Table 1-38 Specify whether to enable multiplexing
|
Operation |
Command |
|
Specify whether to enable multiplexing |
multiplex { disable | enable } |
|
Restore the default multiplexing setting |
undo multiplex |
A number entry for a subscriber line contains one short number and one long number. A short number starts with a pound sign (#) and is two to three characters in length. It corresponds to an interface of a gateway, whichever interface it corresponds to depends on the configuration on the gateway.
Using the subscriber command you can create such an entry on the LS to associate a short number with a calling/called number (long number). In such a way, you can configure terminals (such as telephone sets) of a gateway directly on the LS and make the LS uniformly manage the number resources so as to ease the management burden of the gateway.
Specifically, when a user makes a call and the called number matches such an entry, the system directs the call to the called gateway and the corresponding port, and the called gateway receives the call and directs the call to the corresponding subscriber line interface. If the called number matches only a route number, the system direct the call only to the called gateway, which matches the called long number with its number resource to determine the subscriber line interface corresponding to the called number.
To configure a subscriber line number of a gateway and enter the corresponding subscriber view, perform the following configuration in LS-GW view.
Table 1-39 Configure a subscriber line number of a gateway and enter the corresponding subscriber view
|
Operation |
Command |
|
Create a number entry for a subscriber line of a gateway and enter the corresponding subscriber view |
subscriber short-number long-number |
|
Delete one or all of the entries of a gateway |
undo subscriber { short-number long-number | all } |
& Note:
l The XE IP PBX supports multiple called parties, which allows number entries configured (on one or multiple gateways) with the same long number but respective short numbers.
l When configuring the subscriber line number, make sure that it does not conflict with the ONLY number, the automatic operator number and the group notification number. For detailed information, refer to the “Call Services Operation” module of this manual.
Perform the following configuration in subscriber view.
Table 1-40 Configure the priority of a subscriber line number of a gateway
|
Operation |
Command |
|
Configure the priority of a subscriber line number of a gateway |
priority priority-level |
|
Configure the default priority |
undo priority |
By default, the subscriber line number uses the priority of a gateway. Refer to Configuring the default route number priority of a gateway.
The time-to-live value refers to the length of time interval within which the registration information of a gateway is valid. A PS accepts a call from a gateway during a specified time-to-live interval.
& Note:
The time-to-live value of registration does not affect established calls.
Perform the following configuration in LS-GW view.
Table 1-41 Configure the time-to-live value of registration
|
Operation |
Command |
|
Configure the time-to-live value of registration |
ttl time-length |
|
Restore the default time-to-live value |
undo ttl |
By default, the time-to-live value of the gateway is 180 seconds.
Each route number has a priority value ranging from 0 to 1000. The greater the value, the higher the priority. If this value is not specified, the default priority is used. You can configure an identical route number for several different gateways (multiple called parties). If the priorities of the called numbers are the same, the telephones will ring simultaneously. If the priorities are not the same, the telephones will ring orderly.
Perform the following configuration in LS-GW-Prefix view.
Table 1-42 Configuring the priority of a static route number of a gateway
|
Operation |
Command |
|
Configure the priority of a static route number of a gateway |
priority priority-level |
|
Restore the default priority |
undo priority |
The attributes of a static route number are: user number and relay number. You can configure the same static route number of different gateways. If the static route number is a user number, you can make multiple called parties of different gateways ring simultaneously or in turn based on different priorities. With the same priority, the called parties ring simultaneously while with different priorities, the called parties ring in turn. If the static route number is a relay number, only one called party is chosen to ring among different gateways. Choosing which one is decided by the priority of the called number and that whether the random selection is enabled or not:
l If the called number priorities are different on the gateways, the terminal on the gateway with the highest priority will be selected.
l If the called number priorities are the same, and the random selection is enabled, a terminal corresponding to the number will be selected randomly from these gateways. Each time the number is called, a different terminal is selected.
l If the called number priorities are the same, and the random selection is not enabled, a specific terminal corresponding to the number will be selected from these gateways. Each time the number is called, the same terminal is selected.
Perform the following configuration in LS-GW-Prefix view.
Table 1-43 Configure attribute of a static route number of a gateway
|
Operation |
Command |
|
Configure attribute of a static route number of a gateway |
otapc { fxs | relay } |
|
Restore the default attribute |
undo otapc |
By default, the static route number is the user number.
When the gatekeeper initiates capability negotiation to a called/calling gateway in the routed call mode, the audio/video/data codec type of the called/calling gateway is required. The gatekeeper fails the capability negotiation if it has not obtained the codec type that the gateway supports. Therefore, you need to configure the audio/video/data codec type of the called/calling gateway.
The gatekeeper uses the codec type configured for the called/calling number for capability negotiation. If the number is not configured with a codec type, the codec type configured for the gateway will be used instead.
& Note:
Before the configuration, you need to know the audio/video/data codec type of the called/calling gateway. In the configuration, note to configure the same codec type with both the calling and called gateways to make sure successful calls can be made.
Perform the following configuration in LS-GW view.
Table 1-44 Configure the codec type
|
Operation |
Command |
|
Configure the codec type used when the gatekeeper initiates capability negotiation to a gateway device |
codec { audio { g7231 | g729 | pcma | pcmu } [ packet-length packet-length ] } | { video { h261 | h263 } } | { data t38fax } |
|
Restore the default codec type |
undo codec { audio | video | data } |
By default, G.729 is adopted for audio codec, the packetization time length is 30 ms, and video codec and data faxing is not supported.
The gatekeeper uses the codec type configured for the called/calling number for capability negotiation. If the number is not configured with a codec type, the codec type configured for the gateway will be used instead.
Perform the following configuration in LS-GW-PREFIX or LS-GW-SUBSCRIBER view.
Table 1-45 Configure the codec type of the subscriber
|
Operation |
Command |
|
Configure the codec type of the subscriber when the gatekeeper initiates capability negotiation to a gateway device |
codec { audio { g7231 | g729 | pcma | pcmu } [ packet-length packet-length ] } | { video { h261 | h263 } } | { data t38fax } |
|
Restore the default codec type |
undo codec { audio | video | data } |
By default, the codec type configured on the gateway is adopted.
Each route number has a priority value ranging from 0 to 1000. The greater the value, the higher the priority. If this value is not specified, the default priority is used. You can configure an identical route number for several different office groups (multiple called parties). If the priorities of the called numbers are the same, the corresponding telephones will ring simultaneously when the number is called. If the priorities are not the same, the telephones will ring orderly.
Perform the following configuration in LS-OFFICEGROUP-PREFIX view:
Table 1-46 Configuring the priority of a static route number of an office group
|
Operation |
Command |
|
Configure the priority of a static route number of an office group |
priority priority-level |
|
Restore the default priority |
undo priority |
Use the multiplex command to specify the multiplexing mode of an office device configured on an LS.
Perform the following configuration in LS-OFFICEGROUP-OFFICE view.
Table 1-47 Specify whether to enable multiplexing
|
Operation |
Command |
|
Specify whether to enable multiplexing |
multiplex { disable | enable } |
|
Restore the default setting |
undo multiplex |
By default, multiplexing is disabled.
For the attributes of a static route number, refer to Configuring attribute of a static route number of a gateway.
Perform the following configuration in LS-LS-OFFICEGROUP-PREFIX view.
Table 1-48 Configure attribute of a static route number of an office group
|
Operation |
Command |
|
Configure attribute of a static route number of an office group |
otapc { fxs | relay } |
|
Restore the default attribute |
undo otapc |
By default, the static route number is the user number.
When the gatekeeper initiates capability negotiation to a called/calling office device in the routed call mode, the audio/video/data codec type of the called/calling office device is required. The gatekeeper fails the capability negotiation if it has not obtained the codec type that the office device supports. Therefore, you need to configure the audio/video/data codec type of the called/calling office device.
& Note:
Before the configuration, you need to know the audio/video/data codec type of the called/calling office device. In the configuration, note to configure the same codec type with both the calling and called devices to make sure successful calls can be made.
Perform the following configuration in LS-OFFICEGROUP-OFFICE view.
Table 1-49 Configure the codec type
|
Operation |
Command |
|
Configure the codec type used when the gatekeeper initiates capability negotiation to an office device |
codec { audio { g7231 | g729 | pcma | pcmu } [ packet-length packet-length ] } | { video { h261 | h263 } } | { data t38fax } |
|
Restore the default codec type |
undo codec { audio | video | data } |
By default, G.729 is adopted for audio codec, the packetization time length is 30 ms, and video codec and data faxing is not supported.
For an office device that is not configured with a codec type, the gatekeeper uses the codec type configured on the office device for capability negotiation.
Perform the following configuration in LS-OFFICEGROUP-PREFIX view.
Table 1-50 Configure the default codec type of an office group
|
Operation |
Command |
|
Configure the default codec type of an office group |
codec { audio { g7231 | g729 | pcma | pcmu } [ packet-length packet-length ] } | { video { h261 | h263 } } | { data t38fax } |
|
Restore the default codec type |
undo codec { audio | video | data } |
By default, the default codec type configured on the office device is adopted.
Perform the following configuration in LS view.
Table 1-51 Configure the allowed time difference between LS and PS/MS
|
Operation |
Command |
|
Configure the allowed time difference between LS and PS/MS |
heartbeat-time-range time |
|
Restore the default value |
undo heartbeat-time-range |
By default, this value is 0, indicating the time difference is not limited.
Refer to the “Feature Operation” module of this manual.
On the LS, you can view the information about the PSs, GKs, gateways and office devices configured on the LS, and the CAI message statistics of the LS. Refer to the Location Server Configuration Command part of H3C XE 200/2000 IP PBX Command Manual.
Perform the following configuration in any view.
Table 1-52 Display the information about PSs registered with an LS
|
Operation |
Command |
|
Display the information about PSs registered with an LS |
display location-server process-server { device-id | all | list } |
Perform the following configuration in any view.
Table 1-53 Display the information about gateways registered with an LS
|
Operation |
Command |
|
Display the information about gateways registered with an LS |
display location-server gateway { device-id | all | h323 | sip | list } |
Perform the following configuration in any view.
Table 1-54 Display the information about office groups configured on an LS
|
Operation |
Command |
|
Display the information about office groups configured on an LS |
display location-server office-group { all | officegroup-id | list } |
Run the location-server statistics command in any view, and run the reset location-server statistics command in user view.
Table 1-55 Display the statistics about the LS
|
Operation |
Command |
|
Display the statistics about the LS |
display location-server statistics |
|
Delete the statistics about the LS |
reset location-server statistics |
Perform the following configuration in user view.
Table 1-56 Configure the debugging level of an LS
|
Operation |
Command |
|
Configure the debugging level of an LS |
debugging location-server { call | heartbeat | register } level level |
|
Restore the default debugging level |
undo debugging location-server { call | heartbeat | register } |
By default, the debugging level of the LS is 3.
Perform the following configuration in any view.
Table 1-57 Display the debugging level of the LS
|
Operation |
Command |
|
Display the debugging level of the LS |
display debugging location-server |
Network address translation (NAT) is a technology that translates private network addresses into valid public network addresses transparently according to specific rules. The internal addresses used in a private network are invisible to network devices outside the network and they must be translated into valid public network addresses by NAT for hosts using these private network addresses to communicate with hosts in public networks. This sort of address translation is implemented through the address mapping table maintained by the NAT device. NAT helps to save the IP address resources. It also isolates private networks from public networks so that the private network topologies are concealed from outside and the private networks are secured in certain degree.
l The following describes the principle of address translation for NAT traversal from private network to public network:
Figure 2-1 Diagram for address translation for NAT traversal from private network to public network
When the NAT device receives an IP packet from the private network, it translates and changes the source IP address of the packet (a private network address) to a public network IP address it owns, updates the address mapping table on itself to reflect the mapping relationship between the two IP addresses in an entry for the use of the reverse translation from the public address to the private address, and then sends the packet to the destination public network. In this procedure, if the NAT device fails to translate the source address, it discards the packet.
l The following describes the principle of address translation for NAT traversal from public network to private network:
Figure 2-2 Diagram for address translation for NAT traversal from public network to private network
On receiving an IP packet sourced from the public network, the NAT device searches the address mapping table for a matched mapping entry and changes the public network destination address carried by the packet to the private network address in the matched entry, and then sends the packet to the destination host in the private network. The NAT device discards a received packet if it does not find a matched entry in the address mapping table.
l Firewall
A firewall (FW) refers to a group of components between different networks (e.g., between a trustworthy intranet and untrustworthy public networks) or different security domains in a network. It is the only gate for the information exchange between these networks or network security domains and is able to control (that is, permit, deny, or monitor) the traffic flow from/to these networks or domains depending on your security policies. FWs have relatively strong anti-attack capability and are basic network elements for implementing network and information security.
Logically, an FW acts as a separator, a limiter, and an analyzer. It monitors all of the operations between the internal network and the Internet to ensure the security of the internal network.
l Categories of FWs
Although FWs are divided into multiple types according to the ways they use to protect networks or the aspects they focus on, they fall into two categories: packet filtering and application proxy.
Packet filtering: An FW of this category operates at the network layer and the transport layer. It permits/denies a packet by checking the information carried in the packet header, such as the source IP address, destination IP address, port numbers, and protocol type.
Application proxy: An FW of this category is also known as an application gateway. It operates at the application layer. Different from packet filtering FWs, an application proxy FW intercepts network traffic completely. It monitors traffic at application layer by using the proxy programs specifically designed for different kind of application services. Application proxy FWs are usually implemented using dedicated workstations.
A tunnel here refers to a TCP or UDP channel traversing the NAT/FW between a private network and a public network. NAT/FW tunnel traversal refers to the communication across NAT/FW through tunnels.
The NAT/FW tunnel traversal function provided by XE IP PBXs enables voice communication between a private network and a public network across a NAT/FW or between two private networks across NAT/FWs. The NAT/FW tunnel traversal function is also available in networks containing both H.323 and SIP devices.
& Note:
l You need to set the call mode of the XE IP PBX as routed mode to enable NAT/FW tunnel traversal for it.
l Currently, the tunnel traversal function implemented on XE IP PBXs only supports common call services, instead of voice services.
Before the NAT/FW traversal function can take effect between the private and public networks deployed with XE IP PBXs, the following three types of tunnels must be established:
l A TCP tunnel between the PS in the private network and the LS in the public network
l A TCP tunnel between the PS in the private network and the PS in the public network
l An UDP tunnel between the PS in the private network and the PS in the public network, which is used to transmit voice media stream
Before these types of tunnels can be established, the corresponding ports must be enabled by the administrator on the FW.
The procedure to establish these tunnels is as follows:
1) The PS in the private network initiates a TCP connection request to the LS in the public network through the NAT/FW to establish a TCP tunnel between two of them.
2) The LS issues the tunnel configuration information to the PS in the public network and the PS in the private network.
3) The PS in the private network establishes a TCP tunnel and a UDP tunnel between itself and the PS in the public network using the tunnel configuration information.
As shown in Figure 2-3, the PS on XE IP PBX 1 and the voice gateway H.323 Gateway 1 reside in a private network. The PS on XE IP PBX 2, the voice gateway H.323 Gateway 2, and the LS on XE IP PBX 3 reside in a public network. A NAT/FW is deployed between the private network and the public network.
Figure 2-3 Diagram for tunnel traversal between public and private networks using XE IP PBXs
Tunnel traversal between the private network and the public network using XE IP PBXs is implemented as follows.
The LS on XE IP PBX 3 opens a TCP port for listening and receiving TCP connection request when the LS starts.
2) The PS on XE IP PBX 1 establishes a tunnel (Tunnel 1) between itself and the LS on XE IP PBX 3 when the PS starts. This tunnel traverses the NAT/FW and is used for the signaling exchange between the PS and the LS.
3) The LS on XE IP PBX 3 issues the configuration information about the tunnels to be established between the PSs in the private network and the public network to the PS on XE IP PBX 1 and the PS on XE IP PBX 2.
4) The PS on XE IP PBX 1 establishes a TCP tunnel (Tunnel 2) and an UDP tunnel (Tunnel 3) between itself and the PS on XE IP PBX2. Both the tunnels traverse the NAT/FW.
5) When establishing a call connection, H.323 Gateway 1 exchanges H.323 call control signaling, H.323 media channel control signaling, or SIP signaling with H.323 Gateway 2 through the TCP tunnel (Tunnel 2) established between the PS on XE IP PBX 1 and the PS on XE IP PBX 2.
6) When the call is being carried out, H.323 Gateway 1 and H.323 Gateway 2 exchange voice media stream through the UDP tunnel (Tunnel 3) established between the PS on XE IP PBX 1 and the PS on XE IP PBX 2.
As shown in Figure 2-4, Process Server 1 and H.323 Gateway 1 reside in Private Network 1. Process Server 3 and H.323 Gateway 2 reside in Private Network 2. Process Server 2 and the LS reside in the public network. NAT/FW 1 and NAT/FW 2 are deployed respectively between the two private networks and the public network.
Figure 2-4 Diagram for tunnel traversal between different private networks using XE IP PBXs
The tunnel traversal of the XE IP PBXs between the two private networks is implemented as follows.
1) The LS opens a TCP port for listening and receiving TCP connection request when the LS starts.
2) Process Server 1 establishes a tunnel (Tunnel 1) between itself and the LS when it starts. This tunnel traverses NAT/FW 1 and is used for the signaling exchange between Process Server 1 and LS.
3) The LS issues the configuration information about the tunnels to be established between the PSs in Private Network 1 and the public network to Process Server 1 and Process Server 2.
4) Process Server 1 establishes a TCP tunnel (Tunnel 2) and an UDP tunnel (Tunnel 3) between itself and Process Server 2. Both the tunnels traverse NAT/FW 1.
5) In the same way, Tunnel 4, Tunnel 5 and Tunnel 6 are established when Process Server 3 starts.
6) When establishing a call connection, H.323 Gateway 1 exchanges H.323 call control signaling, H.323 media channel control signaling, or SIP signaling with H.323 Gateway 2 through Tunnel 2 and Tunnel 5.
7) When the call is being carried out, H.323 Gateway 1 and H.323 Gateway 2 transmit/receive voice media stream through Tunnel 3 and Tunnel 6 (the UDP tunnels).
Process Server 2, which connects Tunnel 2 and Tunnel 5, Tunnel 3 and Tunnel 6, forwards signaling and media stream between Process Server 1 and Process Server 3.
You can divide the entire network (including public networks and private networks) into multiple parts called domains. Each domain has an attribute, which you can configure to indicate that the domain belongs to a public network or a private network. A domain can contain multiple PSs, whereas a PS can only belong to one domain.
& Note:
A domain is different from an LS domain. For LS domain, refer to section 1.4.7 “Rule-Based Number Substitution Policy” in the “Feature Operation” module of this manual.
Perform the following configuration in LS view.
Table 2-1 Create a domain and enter the domain view
|
Operation |
Command |
|
Create a domain and enter the domain view |
domain domain-id |
|
Remove one domain or all domains |
undo domain { domain-id | all } |
You can use the attribute command to configure the attribute of a domain to specify the type (public network or private network) of the domain.
Perform the following configuration in LS-domain view.
Table 2-2 Configure the attribute of a domain
|
Operation |
Command |
|
Configure the attribute of a domain |
attribute { private | public} |
|
Remove the attribute configuration of the domain |
undo attribute |
You can use the belongto command to specify the domain to which a PS belongs.
Perform the following configuration in LS-PS view.
Table 2-3 Configure the domain to which a PS belongs
|
Operation |
Command |
|
Configure the domain to which a PS belongs |
belongto domain-id |
|
Specify that the PS belongs to the default-domain domain |
undo belongto |
By default, the PS belongs to the default-domain domain.
To perform NAT/FW tunnel traversal related configuration, you need to enter NAT&FW view first.
Perform the following configuration in LS view.
Table 2-4 Enter NAT&FW view
|
Operation |
Command |
|
Enter NAT&FW view |
nat&fw |
You can use the tunnel command to enable tunnel traversal after configuring a tunnel end pair. You can also use this command to disable tunnel traversal.
Perform the following configuration in LS-PS view.
Table 2-5 Enable/disable tunnel traversal
|
Operation |
Command |
|
Enable/Disable tunnel traversal |
tunnel { enable | disable } |
|
Restore the defaults for the tunnel traversal |
undo tunnel |
Tunnel traversal is disabled by default.
Before the NAT/FW tunnel traversal function can take effect, you need to use the tunnelpeer command to configure basic information for tunnels between the PSs in the public network and private network respectively.
Perform the following configuration in LS-NAT&FW view.
Table 2-6 Configure a tunnel end pair
|
Operation |
Command |
|
Configure a tunnel end pair |
tunnelpeer tunnelpeer-id private private-ps-id private-to-public-add port private-to-public-port public public-ps-id public-to-private-add port public-to-private-port |
|
Remove a tunnel end pair or all tunnel end pairs |
undo tunnelpeer { tunnelpeer-id | all } |
& Note:
l Correctly configure the domain to which the tunnel end pair belongs before configure the pair successfully.
l When the public process server needs to create multiple tunnel end pairs with the private process server, it must use different ports in doing so.
An XE IP PBX serves as both H.323 gatekeeper and LS for H.323 calls.
Figure 3-1 Network diagram for integrated networking with LS and H.323 gatekeeper
& Note:
This example assumes that the H.323 gateway 1, H.323 gateway 2 and XE IP PBX are all reachable to each other and omits the related route configuration, which you can do as required before performing the following configuration.
1) Configure H.323 gateway 1
# Configure the Ethernet interface.
[VG1] interface ethernet 0
[VG1-Ethernet0] ip address 192.168.10.1 255.255.255.0
[VG1-Ethernet0] quit
# Configure voice entities.
[VG1] voice-setup
[VG1-voice] dial-program
[VG1-voice-dial] entity 8888 voip
[VG1-voice-dial-entity8888] address ras
[VG1-voice-dial-entity8888] match-template ....
[VG1-voice-dial-entity8888] quit
[VG1-voice-dial] entity 9901 pots
[VG1-voice-dial-entity9901] line 0
[VG1-voice-dial-entity9901] match-template 9901
[VG1-voice-dial-entity9901] return
# Configure GK-Client.
[VG1] voice-setup
[VG1-voice] gk-client
[VG1-voice-gk] gw-id gw01
[VG1-voice-gk] gw-address ip 192.168.10.1
[VG1-voice-gk] gk-id gkserver gk-addr 192.168.30.10 1719
[VG1-voice-gk] ras-on
2) Configure H.323 Gateway 2
# Configure the Ethernet interface.
[VG2] interface ethernet 0
[VG2-Ethernet0] ip address 192.168.20.1 255.255.255.0
[VG2-Ethernet0] quit
# Configure voice entities.
[VG2] voice-setup
[VG2-voice] dial-program
[VG2-voice-dial] entity 8888 voip
[VG2-voice-dial-entity8888] address ras
[VG2-voice-dial-entity8888] match-template ....
[VG2-voice-dial-entity8888] quit
[VG2-voice-dial] entity 8801 pots
[VG2-voice-dial-entity8801] line 0
[VG2-voice-dial-entity8801] match-template 8801
[VG2-voice-dial-entity8801] return
# Configure GK-Client.
[VG2] voice-setup
[VG2-voice] gk-client
[VG2-voice-gk] gw-id gw02
[VG2-voice-gk] gw-address ip 192.168.20.1
[VG2-voice-gk] gk-id gkserver gk-addr 192.168.30.10
[VG2-voice-gk] ras-on
3) Configure the H.323 gatekeeper
# Configure the Ethernet interface.
[XE] interface ethernet 0/0
[XE-Ethernet0/0] ip address 192.168.30.10 255.255.255.0
[XE-Ethernet0/0] quit
# Configure the gatekeeper.
[XE] process-server
[XE-ps] ps-config gkserver interface Ethernet 0/0
[XE-ps] heartbeat password xe200
[XE-ps] ls-mode 0 local
[XE-ps] start
[XE-ps] gatekeeper
[XE-ps-gk] start
4) Configure the LS
# Configure the LS.
[XE] location-server
[XE-ls] ls-config interface Ethernet 0/0
[XE-ls] call-mode h323 redirect
[XE-ls] start
[XE-ls] process-server gkserver
[XE-ls-ps-gkserver] heartbeat password xe200
[XE-ls-ps-gkserver] quit
[XE-ls] gateway gw01
[XE-ls-gw-gw01] device-type h323
[XE-ls-gw-gw01] dynamic-ip enable
[XE-ls-gw-gw01] quit
[XE-ls] gateway gw02
[XE-ls-gw-gw02] device-type h323
[XE-ls-gw-gw02] dynamic-ip enable
The LS and the H.323 gatekeeper are implemented on different XE 200. Two H.323 voice gateways (VGs) are connected to the LS by the H.323 gatekeeper for H.323 call.
Figure 3-2 Network diagram for distributed networking with LS and H.323 gatekeeper
& Note:
This example assumes that the H.323 gateway 1, H.323 gateway 2, XE IP PBX 1 (gatekeeper) and XE IP PBX 2 (LS) are all reachable to each other and omits the related route configuration, which you can do as required before performing the following configuration..
1) Configure H.323 Gateway 1
# Configure the Ethernet interface.
[VG1] interface ethernet 0
[VG1-Ethernet0] ip address 192.168.10.2 255.255.255.0
[VG1-Ethernet0] quit
# Configure voice entities.
[VG1] voice-setup
[VG1-voice] dial-program
[VG1-voice-dial] entity 8888 voip
[VG1-voice-dial-entity8888] address ras
[VG1-voice-dial-entity8888] match-template ....
[VG1-voice-dial-entity8888] quit
[VG1-voice-dial] entity 9901 pots
[VG1-voice-dial-entity9901] line 0
[VG1-voice-dial-entity9901] match-template 9901
[VG1-voice-dial-entity9901] return
# Configure GK-Client.
[VG1] voice-setup
[VG1-voice] gk-client
[VG1-voice-gk] gw-id gw01
[VG1-voice-gk] gw-address ip 192.168.10.2
[VG1-voice-gk] gk-id gkserver gk-addr 192.168.30.10 1719
[VG1-voice-gk] ras-on
2) Configure H.323 Gateway 2
# Configure the Ethernet interface.
[VG2] interface ethernet 0
[VG2-Ethernet0] ip address 192.168.40.2 255.255.255.0
[VG2-Ethernet0]quit
# Configure voice entities.
[VG2] voice
[VG2-voice] dial-program
[VG2-voice-dial] entity 8888 voip
[VG2-voice-dial-entity8888] address ras
[VG2-voice-dial-entity8888] match-template ....
[VG2-voice-dial-entity8888] quit
[VG2-voice-dial] entity 8801 pots
[VG2-voice-dial-entity8801] line 0
[VG2-voice-dial-entity8801] match-template 8801
[VG2-voice-dial-entity8801] return
# Configure GK-Client.
[VG2] voice-setup
[VG2-voice] gk-client
[VG2-voice-gk] gw-id gw02
[VG2-voice-gk] gw-address ip 169.254.20.1
[VG2-voice-gk] gk-id gkserver gk-addr 169.254.10.10
[VG2-voice-gk] ras-on
3) Configure the H.323 gatekeeper
# Configure the Ethernet interface.
[XE1] interface ethernet 0/0
[XE1-Ethernet0/0] ip address 192.168.30.10 255.255.255.0
[XE1-Ethernet0/0] quit
# Configure the gatekeeper.
[XE1] process-server
[XE1-ps] ps-config gkserver interface Ethernet 0/0
[XE1-ps] heartbeat password xe200
[XE1-ps] ls-mode 0 remote ip-address 192.168.20.20
[XE1-ps] start
[XE1-ps] gatekeeper
[XE1-ps-gk] start
4) Configure the LS
# Configure the Ethernet interface.
[XE2] interface ethernet 0/0
[XE2-Ethernet0/0] ip address 192.168.20.20 255.255.255.0
[XE2-Ethernet0/0] quit
# Configure the LS.
[XE2] location-server
[XE2-ls] ls-config interface Ethernet 0/0
[XE2-ls] call-mode h323 redirect
[XE2-ls] start
[XE2-ls] process-server gkserver
[XE2-ls-ps-gkserver] heartbeat password xe200
[XE2-ls-ps-gkserver] quit
[XE2-ls] gateway gw01
[XE2-ls-gw-gw01] device-type h323
[XE2-ls-gw-gw01] dynamic-ip enable
[XE2-ls-gw-gw01] quit
[XE2-ls] gateway gw02
[XE2-ls-gw-gw02] device-type h323
[XE2-ls-gw-gw02] dynamic-ip enable
An XE IP PBX serves as both LS and H.323 gatekeeper to process H.323 routed calls.
Figure 3-3 Network diagram for processing basic H.323 routed calls
& Note:
This example assumes that H.323 gateway 1, H.323 gateway 2, and XE IP PBX are all reachable to each other and omits the related route configuration, which you can do as required before performing the following configuration.
1) Configure H.323 gateway 1
# Configure the Ethernet port.
[VG1] interface ethernet 0
[VG1-Ethernet0] ip address 192.168.10.2 255.255.255.0
[VG1-Ethernet0] quit
# Configure voice entities.
[VG1] voice-setup
[VG1-voice] dial-program
[VG1-voice-dial] entity 8888 voip
[VG1-voice-dial-entity8888] address ras
[VG1-voice-dial-entity8888] match-template ....
[VG1-voice-dial-entity8888] quit
[VG1-voice-dial] entity 8801 pots
[VG1-voice-dial-entity8801] line 0
[VG1-voice-dial-entity8801] match-template 8801
[VG1-voice-dial-entity8801] return
# Configure gatekeeper client.
[VG1] voice-setup
[VG1-voice] gk-client
[VG1-voice-gk] gw-id h323gateway1
[VG1-voice-gk] gw-address ip 192.168.10.2
[VG1-voice-gk] gk-id xeippbx gk-addr 192.168.20.10 1719
[VG1-voice-gk] ras-on
2) Configure H.323 gateway 2
# Configure the Ethernet interface.
[VG2] interface ethernet 0
[VG2-Ethernet0] ip address 192.168.30.2 255.255.255.0
[VG2-Ethernet0] quit
# Configure voice entities.
[VG2] voice-setup
[VG2-voice] dial-program
[VG2-voice-dial] entity 8888 voip
[VG2-voice-dial-entity8888] address ras
[VG2-voice-dial-entity8888] match-template ....
[VG2-voice-dial] entity 8802 pots
[VG2-voice-dial-entity8802] line 0
[VG2-voice-dial-entity8802] match-template 8802
[VG2-voice-dial-entity8802] return
# Configure gatekeeper client.
[VG2] voice-setup
[VG2-voice] gk-client
[VG2-voice-gk] gw-id h323gateway2
[VG2-voice-gk] gw-address ip 192.168.30.2
[VG2-voice-gk] gk-id xeippbx gk-addr 192.168.20.10 1719
[VG2-voice-gk] ras-on
3) Configure the H.323 gatekeeper
# Configure the Ethernet interface.
[XE] interface ethernet 0/0
[XE-Ethernet0/0] ip address 192.168.20.10 255.255.255.0
# Configure the gatekeeper.
[XE] process-server
[XE-ps] ps-config xeippbx interface Ethernet 0/0
[XE-ps] heartbeat password xe200
[XE-ps] ls-mode 0 local
[XE-ps] start
[XE-ps] gatekeeper
[XE-ps-gk] start
4) Configure the LS
# Configure the LS.
[XE]location-server
[XE-ls] ls-config interface Ethernet 0/0
[XE-ls] call-mode h323 routed
[XE-ls] start
[XE-ls] process-server xeippbx
[XE-ls-ps-xeippbx] heartbeat password xe200
[XE-ls] gateway h323gateway1
[XE-ls-gw-h323gateway1] device-type h323
[XE-ls-gw-h323gateway1] dynamic-ip enable
[XE-ls-gw-h323gateway1] quit
[XE-ls] gateway h323gateway2
[XE-ls-gw-h323gateway2] device-type h323
[XE-ls-gw-h323gateway2] dynamic-ip enable
Both XE 200 IP PBXs in LS areas 1 and 2 are in integrated networking mode. The XE IP PBX XE 1 in LS domain 1 is configured with two office devices each corresponding to one VG in LS domain 2 for H.323 calls.
Figure 3-4 Network diagram for office devices
& Note:
This example assumes that the H.323 gateway 1, H.323 gateway 2, office gateway 1, office gateway 2, XE IP PBX 1 and XE IP PBX 2 are all reachable to each other and omits the related route configuration, which you can do as required before performing the following configuration.
1) Configure H.323 gateway 1
# Configure the Ethernet interface.
[VG1] interface ethernet 0
[VG1-Ethernet0] ip address 192.168.10.2 255.255.255.0[VG1-Ethernet0] quit
# Configure voice entities.
[VG1] voice-setup
[VG1-voice] dial-program
[VG1-voice-dial] entity 8888 voip
[VG1-voice-dial-entity8888] address ras
[VG1-voice-dial-entity8888] match-template 88..
[VG1-voice-dial-entity8888] quit
[VG1-voice-dial] entity 9999 voip
[VG1-voice-dial-entity9999] address ras
[VG1-voice-dial-entity9999] match-template 99..
[VG1-voice-dial-entity9999] quit
[VG1-voice-dial] entity 8801 pots
[VG1-voice-dial-entity8801] line 0
[VG1-voice-dial-entity8801] match-template 8801
[VG1-voice-dial-entity8801] return
# Configure the gatekeeper client.
[VG1] voice-setup
[VG1-voice] gk-client
[VG1-voice-gk] gw-id gw01
[VG1-voice-gk] gw-address ip 192.168.10.2
[VG1-voice-gk] gk-id gkserver gk-addr 192.168.30.10
[VG1-voice-gk] ras-on
2) Configure H.323 gateway 2
# Configure the Ethernet interface.
[VG2] interface ethernet 0
[VG2-Ethernet0] ip address 192.168.20.2 255.255.255.0
[VG2-Ethernet0] quit
# Configure the voice entities.
[VG2] voice-setup
[VG2-voice] dial-program
[VG2-voice-dial] entity 88 voip
[VG2-voice-dial-entity88] address ras
[VG2-voice-dial-entity88] match-template 88..
[VG2-voice-dial-entity88] quit
[VG2-voice-dial] entity 99 voip
[VG2-voice-dial-entity99] address ras
[VG2-voice-dial-entity99] match-template 99..
[VG2-voice-dial-entity99] quit
[VG2-voice-dial] entity 8802 pots
[VG2-voice-dial-entity8802] line 0
[VG2-voice-dial-entity8802] match-template 8802
[VG2-voice-dial-entity8802] return
# Configure the gatekeeper client.
[VG2] voice-setup
[VG2-voice] gk-client
[VG2-voice-gk] gw-id gw02
[VG2-voice-gk] gw-address ip 192.168.20.2
[VG2-voice-gk] gk-id gkserver gk-addr 192.168.30.10
[VG2-voice-gk] ras-on
3) Configure office gateway 1
# Configure the Ethernet interface.
[VG3] interface ethernet 0
[VG3-Ethernet0] ip address 192.168.60.2 255.255.255.0
[VG3-Ethernet0] quit
# Configure voice entities.
[VG3] voice-setup
[VG3-voice] dial-program
[VG3-voice-dial] entity 88 voip
[VG3-voice-dial-entity88] address ras
[VG3-voice-dial-entity88] match-template 88..
[VG3-voice-dial-entity88] quit
[VG3-voice-dial] entity 99 voip
[VG3-voice-dial-entity99] address ras
[VG3-voice-dial-entity99] match-template 99..
[VG3-voice-dial-entity99] quit
[VG3-voice-dial] entity 9901 pots
[VG3-voice-dial-entity9901] line 0
[VG3-voice-dial-entity9901] match-template 9901
[VG3-voice-dial-entity9901] return
# Configure the gatekeeper client.
[VG3] voice-setup
[VG3-voice] gk-client
[VG3-voice-gk] gw-id gw03
[VG3-voice-gk] gw-address ip 192.168.60.2
[VG3-voice-gk] gk-id gkserver1 gk-addr 192.168.40.10
[VG3-voice-gk] ras-on
4) Configure office gateway 2
# Configure the Ethernet interface.
[VG4] interface ethernet 0
[VG4-Ethernet0] ip address 192.168.50.2 255.255.255.0
[VG4-Ethernet0] quit
# Configure voice entities.
[VG4] voice-setup
[VG4-voice] dial-program
[VG4-voice-dial] entity 88 voip
[VG4-voice-dial-entity88] address ras
[VG4-voice-dial-entity88] match-template 88..
[VG4-voice-dial-entity88] quit
[VG4-voice-dial] entity 99 voip
[VG4-voice-dial-entity99] address ras
[VG4-voice-dial-entity99] match-template 99..
[VG4-voice-dial-entity99] quit
[VG4-voice-dial] entity 9902 pots
[VG4-voice-dial-entity9902] line 0
[VG4-voice-dial-entity9902] match-template 9902
[VG4-voice-dial-entity9902] return
# Configure the gatekeeper client.
[VG4] voice-setup
[VG4-voice] gk-client
[VG4-voice-gk] gw-id gw04
[VG4-voice-gk] gw-address ip 192.168.50.2
[VG4-voice-gk] gk-id gkserver1 gk-addr 192.168.40.10
[VG4-voice-gk] ras-on
5) Configure the H.323 gatekeeper in the LS Domain1
# Configure the Ethernet interface.
[XE1] interface ethernet 0/0
[XE1-Ethernet0/0] ip address 192.168.30.10 255.255.255.0
[XE1-Ethernet0/0] quit
# Configure the gatekeeper.
[XE1] process-server
[XE1-ps] ps-config gkserver interface Ethernet 0/0
[XE1-ps] heartbeat password xe200
[XE1-ps] ls-mode 0 local
[XE1-ps] start
[XE1-ps] gatekeeper
[XE1-ps-gk] start
6) Configure the LS
# Configure the LS.
[XE1] location-server
[XE1-ls] ls-config interface Ethernet 0/0
[XE1-ls] call-mode h323 redirect
[XE1-ls] start
[XE1-ls] process-server gkserver
[XE1-ls-ps-gkserver] heartbeat password xe200
[XE1-ls-ps-gkserver] quit
[XE1-ls] gateway gw01
[XE1-ls-gw-gw01] device-type h323
[XE1-ls-gw-gw01] dynamic-ip enable
[XE1-ls-gw-gw01] quit
[XE1-ls] gateway gw02
[XE1-ls-gw-gw02] device-type h323
[XE1-ls-gw-gw02] dynamic-ip enable
[XE1-ls-gw-gw02] quit
[XE1-ls] office-group og01
[XE1-ls-og-og01] prefix 9901
[XE1-ls-og-og01 9901] quit
[XE1-ls-og-og01] office of01
[XE1-ls-og-og01 of01] device-type h323-gw
[XE1-ls-og-og01 of01] ip-address 192.168.60.2
[XE1-ls-og-og01 of01] port 1720
[XE1-ls-og-og01 of01] quit
[XE1-ls-og-og01] quit
[XE1-ls] office-group og02
[XE1-ls-og-og02] prefix 9902
[XE1-ls-og-og01 9902] quit
[XE1-ls-og-og02] office of02
[XE1-ls-og-og02 of02] device-type h323-gw
[XE1-ls-og-og02 of02] ip-address 192.168.50.2
[XE1-ls-og-og02 of02] port 1720
[XE1-ls-og-og02 of02] quit
[XE1-ls-og-og02] quit
7) Configure the H.323 gatekeeper in LS domain 2
# Configure the Ethernet interface.
[XE2] interface ethernet 0/0
[XE2-Ethernet0/0] ip address 192.168.40.10 255.255.255.0
[XE2-Ethernet0/0] quit
# Configure the gatekeeper.
[XE2] process-server
[XE2-ps] ps-config gkserver1 interface Ethernet 0/0
[XE2-ps] heartbeat password xe200
[XE2-ps] ls-mode 0 local
[XE2-ps] start
[XE2-ps] gatekeeper
[XE2-ps-gk] start
8) Configure the LS
# Configure the LS.
[XE2] location-server
[XE2-ls] ls-config interface Ethernet 0/0
[XE2-ls] call-mode h323 redirect
[XE2-ls] start
[XE2-ls] process-server gkserver1
[XE2-ls-ps-gkserver1] heartbeat password xe200
[XE2-ls-ps-gkserver1] quit
[XE2-ls] gateway gw03
[XE2-ls-gw-gw03] device-type h323
[XE2-ls-gw-gw03] dynamic-ip enable
[XE2-ls-gw-gw03] quit
[XE2-ls] gateway gw04
[XE2-ls-gw-gw04] device-type h323
[XE2-ls-gw-gw04] dynamic-ip enable
[XE2-ls-gw-gw04] quit
[XE2-ls] office-group og1
[XE2-ls-og-og1] prefix 8801
[XE2-ls-og-og1 8801] quit
[XE2-ls-og-og1] office of1
[XE2-ls-og-og1 of1] device-type h323-gw
[XE2-ls-og-og1 of1] ip-address 192.168.10.2
[XE2-ls-og-og1 of1] port 1720
[XE2-ls-og-og1 of1] quit
[XE2-ls-og-og1] quit
[XE2-ls] office-group og2
[XE2-ls-og-og2] prefix 8802
[XE2-ls-og-og2 8802] quit
[XE2-ls-og-og2] office of2
[XE2-ls-og-og2 of2] device-type h323-gw
[XE2-ls-og-og2 of2] ip-address 192.168.20.2
[XE2-ls-og-og2 of2] port 1720
[XE2-ls-og-og2 of2] return
<XE>
An XE 200 IP PBX serves as a SIP redirect server. This enables two voice gateways to function as user agents (UAs) for SIP calls.
Figure 3-5 Network diagram for call redirection by a SIP redirect server
& Note:
This example assumes that the SIP user agent 1, SIP user agent 2, and XE IP PBX are all reachable to each other and omits the related route configuration, which you can do as required before performing the following configuration.
1) Configure SIP user agent 1
# Configure the Ethernet interface.
[VG1] interface ethernet 0
[VG1-Ethernet0] ip address 192.168.1.2 255.255.255.0
[VG1-Ethernet0] quit
# Configure voice entities.
[VG1] voice-setup
[VG1-voice] dial-program
[VG1-voice-dial] entity 2222 voip
[VG1-voice-dial-entity2222] address sip proxy
[VG1-voice-dial-entity2222] match-template ....
[VG1-voice-dial] entity 1111 pots
[VG1-voice-dial-entity1111] line 0
[VG1-voice-dial-entity1111] match-template 8801
[VG1-voice-dial-entity1111] return
# Configure the SIP user agent.
[VG1-voice] sip
[VG1-voice-sip] sip-server master 192.168.10.10
[VG1-voice-sip] sip-id vg1
[VG1-voice-sip] register-enable on
2) Configure SIP user agent 2
# Configure the Ethernet interface.
[VG2] interface ethernet 0
VG2-Ethernet0] ip address 192.168.2.2 255.255.255.0
[VG2-Ethernet0] quit
# Configure voice entities.
[VG2] voice-setup
[VG2-voice] dial-program
[VG2-voice-dial] entity 1111 voip
[VG2-voice-dial-entity1111] address sip proxy
[VG2-voice-dial-entity1111] match-template ....
[VG2-voice-dial-entity1111] quit
[VG2-voice-dial] entity 2222 pots
[VG2-voice-dial-entity2222] line 0
[VG2-voice-dial-entity2222] match-template 8802
[VG2-voice-dial-entity2222] return
# Configure the SIP user agent.
[VG2-voice] sip
[VG2-voice-sip] sip-server master 192.168.10.10
[VG2-voice-sip] sip-id vg2
[VG2-voice-sip] register-enable on
3) Configure SIP Server (including a proxy server and an LS)
# Configure the Ethernet interface.
[XE] interface ethernet 0/0
[XE-Ethernet0/0] ip address 192.168.10.10 255.255.255.0
[XE-Ethernet0/0] quit
# Configure the proxy server.
[XE] process-server
[XE-ps] ps-config xe200 interface Ethernet 0/0
[XE-ps] heartbeat password xe200
[XE-ps] ls-mode 0 local
[XE-ps] start
[XE-ps] sip
[XE-ps-sip] start
# Configure the LS.
[XE] location-server
[XE-ls] ls-config interface Ethernet 0/0
[XE-ls] call-mode sip redirect
[XE-ls] start
[XE-ls] process-server xe200
[XE-ls-ps-xe200] heartbeat password xe200
# Register the gateway information with the LS.
[XE-ls] gateway vg1
[XE-ls-gw-vg1] device-type sip
[XE-ls-gw-vg1] dynamic-ip enable
[XE-ls] gateway vg2
[XE-ls-gw-vg2] device-type sip
[XE-ls-gw-vg2] dynamic-ip enable
A SIP proxy server and an LS are integrated into the XE 200 IP PBX. It enables two voice gateways to function as SIP UAs for SIP calls.
Figure 3-6 Network diagram for SIP user agents to make calls by a SIP Server
& Note:
This example assumes that the SIP user agent 1, SIP user agent 2, and SIP server are all reachable to each other and omits the related route configuration, which you can do as required before performing the following configuration.
1) Configure SIP user agent 1
# Configure the Ethernet interface.
[VG1] interface ethernet 0
[VG1-Ethernet0] ip address 192.168.1.2 255.255.255.0
[VG1-Ethernet0] quit
# Configure voice entities.
[VG1] voice-setup
[VG1-voice] dial-program
[VG1-voice-dial] entity 2222 voip
[VG1-voice-dial-entity2222] address sip proxy
[VG1-voice-dial-entity2222] match-template ....
[VG1-voice-dial-entity2222] quit
[VG1-voice-dial] entity 1111 pots
[VG1-voice-dial-entity1111] line 0
[VG1-voice-dial-entity1111] match-template 8801
[VG1-voice-dial-entity1111] return
# Configure the SIP user agent.
[VG1] voice-setup
[VG1-voice] sip
[VG1-voice-sip] sip-server master 192.168.10.10
[VG1-voice-sip] sip-id router1
[VG1-voice-sip] register-enable on
2) Configure SIP user agent 2
# Configure the Ethernet interface.
[VG2] interface ethernet 0
[VG2-Ethernet0] ip address 192.168.2.2 255.255.255.0
[VG2-Ethernet0] quit
# Configure voice entities.
[VG2] voice-setup
[VG1-voice] dial-program
[VG2-voice-dial] entity 1111 voip
[VG2-voice-dial-entity1111] address sip proxy
[VG2-voice-dial-entity1111] match-template ....
[VG2-voice-dial-entity1111] quit
[VG2-voice-dial] entity 2222 pots
[VG2-voice-dial-entity2222] line 0
[VG2-voice-dial-entity2222] match-template 8802
[VG2-voice-dial-entity2222] return
# Configure the SIP user agent.
[VG2] voice-setup
[VG2-voice] sip
[VG2-voice-sip] sip-server master 192.168.10.10
[VG2-voice-sip] sip-id router2
[VG2-voice-sip] register-enable on
3) Configure the SIP server (including a SIP proxy server and an LS)
# Configure the Ethernet interface.
[XE] interface ethernet 0/0
[XE-Ethernet0/0] ip address 192.168.10.10 255.255.255.0
[XE-Ethernet0/0] quit
# Configure the SIP proxy server.
[XE] process-server
[XE-ps] ps-config xe200 interface Ethernet 0/0
[XE-ps] heartbeat password xe200
[XE-ps] ls-mode 0 local
[XE-ps] start
[XE-ps] sip
[XE-ps-sip] start
# Configure the LS.
[XE] location-server
[XE-ls] ls-config interface Ethernet 0/0 port 13579
[XE-ls] call-mode sip routed
[XE-ls] start
[XE-ls] process-server xe2000
[XE-ls-ps-xe2000] heartbeat password xe200
[XE-ls] gateway router1
[XE-ls-gw-router1] device-type sip
[XE-ls-gw-router1] dynamic-ip enable
[XE-ls-gw-router1] quit
[XE-ls] gateway router2
[XE-ls-gw-router2] device-type sip
[XE-ls-gw-router2] dynamic-ip enable
The LS and SIP proxy server are implemented on two XE IP PBXs respectively. Two voice gateways function as SIP UAs for SIP calls by the SIP proxy server and the proxy server acquires information about the called party through the LS.
Figure 3-7 Network diagram for SIP user agents to make calls by proxy server and LS
& Note:
This example assumes that the SIP user agent 1, SIP user agent 2, SIP proxy server, and LS are all reachable to each other and omits the related route configuration, which you can do as required before performing the following configuration.
1) Configure SIP user agent 1
# Configure the Ethernet interface.
[VG1] interface ethernet 0/0
[VG1-Ethernet0/0] ip address 192.168.1.2 255.255.255.0
[VG1-Ethernet0/0] quit
# Configure voice entities.
[VG1] voice-setup
[VG1-voice] dial-program
[VG1-voice-dial] entity 2222 voip
[VG1-voice-dial-entity2222] address sip proxy
[VG1-voice-dial-entity2222] match-template ....
[VG1-voice-dial-entity2222] quit
[VG1-voice-dial] entity 1111 pots
[VG1-voice-dial-entity1111] line 0
[VG1-voice-dial-entity1111] match-template 9901
[VG1-voice-dial-entity1111] return
# Configure the SIP user agent.
[VG1] voice-setup
[VG1-voice] sip
[VG1-voice-sip] sip-server master 192.168.10.10
[VG1-voice-sip] sip-id router1
[VG1-voice-sip] register-enable on
2) Configure SIP user agent 2
# Configure the Ethernet interface.
[VG2] interface ethernet 0/0
[VG2-Ethernet0/0] ip address 192.168.2.2 255.255.255.0
[VG2-Ethernet0/0] quit
# Configure voice entities.
[VG2] voice-setup
[VG2-voice] dial-program
[VG1-voice-dial] entity 1111 voip
[VG2-voice-dial-entity1111] address sip proxy
[VG2-voice-dial-entity1111] match-template ....
[VG2-voice-dial-entity1111] quit
[VG2-voice-dial] entity 2222 pots
[VG2-voice-dial-entity2222] line 0
[VG2-voice-dial-entity2222] match-template 8801
[VG2-voice-dial-entity2222] return
# Configure the SIP user agent.
[VG2] voice-setup
[VG2-voice] sip
[VG2-voice-sip] sip-server master 192.168.10.10
[VG2-voice-sip] sip-id router2
[VG2-voice-sip] register-enable on
3) Configure the SIP proxy server
# Configure the Ethernet interface.
[XE1] interface ethernet 0/0
[XE1-Ethernet0/0] ip address 192.168.10.10 255.255.255.0
[XE1-Ethernet0/0] quit
# Configure the proxy server.
[XE1] process-server
[XE1-ps] ps-config xe200 interface Ethernet 0/0
[XE1-ps] heartbeat password xe200
[XE1-ps] ls-mode 0 remote ip-address 192.168.20.20
[XE1-ps] start
[XE-ps] sip
[XE-ps-sip] start
4) Configure the LS
# Configure the Ethernet interface.
[XE2] interface ethernet 0/0
[XE2-Ethernet0/0] ip address 192.168.20.20 255.255.255.0
[XE2-Ethernet0/0] quit
# Configure the LS.
[XE2] location-server
[XE2-ls] ls-config interface Ethernet 0/0
[XE2-ls] call-mode sip routed
[XE2-ls] start
[XE2-ls] process-server xe200
[XE2-ls-ps-xe200] heartbeat password xe200
[XE2-ls] gateway router1
[XE2-ls-gw-router1] device-type sip
[XE2-ls-gw-router1] dynamic-ip enable
[XE2-ls-gw-router1] quit
[XE2-ls] gateway router2
[XE2-ls-gw-router2] device-type sip
[XE2-ls-gw-router2] dynamic-ip enable
An XE 200 IP PBX is deployed in integrated networking mode so that it serves as both LS and PS. Both H.323 gatekeeper and SIP server are enabled on the XE 200 IP PBX and are configured to adopt the routed call mode. H.323 gateway 1 and SIP user agent 1 are two gateway devices under the administration of the LS. Through the two gateway devices, the H.323 terminal communicates with the SIP terminal.
& Note:
For common call and faststart call modes, see section 2.1.1.VI “H.323 call setup modes” in the “PS Configuration Operation” module of this manual.
Figure 3-8 Network diagram for H.323 terminal communicating with SIP terminal in common call mode
& Note:
This example assumes that H.323 gateway 1, SIP user agent 1 and XE IP PBX shown in Figure 3-8 are all routing reachable to each other and omits the related route configuration, which you can do as required before performing the following configuration.
1) Configure H.323 gateway 1
# Configure the Ethernet interface.
[VG1] interface ethernet 0
[VG1-Ethernet0] ip address 192.168.30.2 255.255.255.0
[VG1-Ethernet0] quit
# Configure voice entities.
[VG1] voice-setup
[VG1-voice] dial-program
[VG1-voice-dial] entity 8888 voip
[VG1-voice-dial-entity8888] address ras
[VG1-voice-dial-entity8888] match-template ....
[VG1-voice-dial-entity8888] quit
[VG1-voice-dial] entity 8801 pots
[VG1-voice-dial-entity8801] line 0
[VG1-voice-dial-entity8801] match-template 8801
[VG1-voice-dial-entity8801] return
#Configure the gatekeeper client.
[VG1] voice-setup
[VG1-voice] gk-client
[VG1-voice-gk] gw-id h323gateway1
[VG1-voice-gk] gw-address ip 192.168.30.2
[VG1-voice-gk] gk-id xeippbx gk-addr 192.168.10.10 1719
[VG1-voice-gk] ras-on
2) Configure SIP user agent 1
# Configure the Ethernet interface.
[UA] interface ethernet 0
[UA-Ethernet0] ip address 192.168.20.2 255.255.255.0
[UA-Ethernet0] quit
# Configure voice entities.
[UA] voice-setup
[UA-voice] dial-program
[UA-voice-dial] entity 8888 voip
[UA-voice-dial-entity8888] address sip proxy
[UA-voice-dial-entity8888] match-template ....
[UA-voice-dial] entity 8802 pots
[UA-voice-dial-entity8802] line 0
[UA-voice-dial-entity8802] match-template 8802
[UA-voice-dial-entity8802] return
# Configure the SIP gateway (user agent).
[UA] voice-setup
[UA-voice] sip
[UA-voice-sip] sip-id sipuseragent1
[UA-voice-sip] sip-server master ip 192.168.10.10 port default all
[UA-voice-sip] register-enable on
3) Configure the XE IP PBX
# Configure the Ethernet interface.
[XE] interface ethernet 0/0
[XE-Ethernet0/0] ip address 192.168.10.10 255.255.255.0
# Configure the gatekeeper and the SIP proxy server.
[XE] process-server
[XE-ps] ps-config xeippbx interface Ethernet 0/0
[XE-ps] heartbeat password xe200
[XE-ps] ls-mode 0 local
[XE-ps] start
[XE-ps] gatekeeper
[XE-ps-gk] start
[XE-ps-gk] quit
[XE-ps] sip
[XE-ps-sip] start
4) Configure the LS
# Configure the LS.
[XE] location-server
[XE-ls] ls-config interface Ethernet 0/0
[XE-ls] call-mode h323 routed
[XE-ls] call-mode sip routed
[XE-ls] process-server xeippbx
[XE-ls-ps-xeippbx] heartbeat password xe200
[XE-ls-ps-xeippbx] quit
[XE-ls] gateway h323gateway1
[XE-ls-gw-h323gateway1] device-type h323
[XE-ls-gw-h323gateway1] dynamic-ip enable
[XE-ls-gw-h323gateway1] quit
[XE-ls] gateway sipuseragent1
[XE-ls-gw-sipuseragent1] device-type sip
[XE-ls-gw-sipuseragent1] dynamic-ip enable
[XE-ls-gw-sipuseragent1] quit
[XE-ls] start
An XE 200 IP PBX is deployed in integrated mode so that it serves as both LS and PS. Both H.323 gatekeeper and SIP server are enabled on the XE 200 IP PBX and are configured to adopt the routed call mode. H.323 gateway 1 and SIP user agent 1 are two gateway devices under the administration of the LS. Through the two gateway devices, the H.323 terminal communicates with the SIP terminal.
Figure 3-9 Network diagram for H.323 terminal communicating with SIP terminal in faststart mode
1) Configure H.323 gateway 1
# Configure the Ethernet interface.
[VG1] interface ethernet 0
[VG1-Ethernet0] ip address 192.168.30.2 255.255.255.0
[VG1-Ethernet0] quit
# Configure voice entities.
[VG1] voice-setup
[VG1-voice] dial-program
[VG1-voice-dial] entity 8888 voip
[VG1-voice-dial-entity8888] address ras
[VG1-voice-dial-entity8888] match-template ....
[VG1-voice-dial-entity8888] fast-connect
[VG1-voice-dial-entity8888] quit
[VG1-voice-dial] entity 8801 pots
[VG1-voice-dial-entity8801] line 0
[VG1-voice-dial-entity8801] match-template 8801
[VG1-voice-dial-entity8801] return
# Configure the gatekeeper client.
[VG1] voice-setup
[VG1-voice] gk-client
[VG1-voice-gk] gw-id h323gateway1
[VG1-voice-gk] gw-address ip 192.168.30.2
[VG1-voice-gk] gk-id xeippbx gk-addr 192.168.10.10 1719
[VG1-voice-gk] ras-on
2) Configure SIP user agent 1
# Configure the Ethernet interface.
[UA] interface ethernet 0
[UA-Ethernet0] ip address 192.168.20.2 255.255.255.0
[UA-Ethernet0] quit
# Configure voice entities.
[UA] voice-setup
[UA-voice] dial-program
[UA-voice-dial] entity 8888 voip
[UA-voice-dial-entity8888] address sip proxy
[UA-voice-dial-entity8888] match-template ....
[UA-voice-dial] entity 8802 pots
[UA-voice-dial-entity8802] line 0
[UA-voice-dial-entity8802] match-template 8802
[UA-voice-dial-entity8802] return
# Configure the SIP gateway (user agent).
[UA] voice-setup
[UA-voice] sip
[UA-voice-sip] sip-id sipuseragent1
[UA-voice-sip] sip-server master ip 192.168.10.10 port default all
[UA-voice-sip] register-enable on
3) Configure the XE IP PBX
# Configure the Ethernet interface.
[XE] interface ethernet 0/0
[XE-Ethernet0/0] ip address 192.168.10.10 255.255.255.0
# Configure the gatekeeper and the SIP proxy server.
[XE] process-server
[XE-ps] ps-config xeippbx interface Ethernet 0/0
[XE-ps] heartbeat password xe200
[XE-ps] ls-mode 0 local
[XE-ps] start
[XE-ps] gatekeeper
[XE-ps-gk] start
[XE-ps-gk] quit
[XE-ps] sip
[XE-ps-sip] start
4) Configure the LS.
# Configure the LS.
[XE] location-server
[XE-ls] ls-config interface Ethernet 0/0
[XE-ls] call-mode h323 routed
[XE-ls] call-mode sip routed
[XE-ls] process-server xeippbx
[XE-ls-ps-xeippbx] heartbeat password xe200
[XE-ls-ps-xeippbx] quit
[XE-ls] gateway h323gateway1
[XE-ls-gw-h323gateway1] device-type h323
[XE-ls-gw-h323gateway1] dynamic-ip enable
[XE-ls-gw-h323gateway1] quit
[XE-ls] gateway sipuseragent1
[XE-ls-gw-sipuseragent1] device-type sip
[XE-ls-gw-sipuseragent1] dynamic-ip enable
[XE-ls-gw-sipuseragent1] quit
[XE-ls] start
An XE 200 IP PBX is deployed in integrated networking mode so that it serves as both LS and PS. Two H.323 gateways (H.323 gateway 1 and H.323 gateway 2) and one SIP gateway (SIP user agent 1) are three gateway devices under the administration of the local LS. In this hybrid network, one H.323 gateway operates as the calling party gateway, both the other H.323 gateway and the SIP gateway operate as the called party gateways and the two attached phones are simultaneously-ringing phones.
Figure 3-10 Network diagram for multiple called party simultaneously ringing in a hybrid network
& Note:
This example assumes that the H.323 gateway 1, H.323 gateway 2, SIP user agent 1, and XE IP PBX are all reachable to each other and omits the related route configuration, which you can do as required before performing the following configuration.
1) Configure H.323 gateway 1
# Configure the Ethernet interface.
[VG1] interface ethernet 0
[VG1-Ethernet0] ip address 192.168.30.2 255.255.255.0
[VG1-Ethernet0] quit
# Configure voice entities.
[VG1] voice-setup
[VG1-voice] dial-program
[VG1-voice-dial] entity 8888 voip
[VG1-voice-dial-entity8888] address ras
[VG1-voice-dial-entity8888] match-template ....
[VG1-voice-dial-entity8888] fast-connect
[VG1-voice-dial-entity8888] quit
[VG1-voice-dial] entity 8801 pots
[VG1-voice-dial-entity8801] line 0
[VG1-voice-dial-entity8801] match-template 8801
[VG1-voice-dial-entity8801] return
# Configure the gatekeeper client.
[VG1] voice-setup
[VG1-voice] gk-client
[VG1-voice-gk] gw-id h323gateway1
[VG1-voice-gk] gw-address ip 192.168.30.2
[VG1-voice-gk] gk-id xeippbx gk-addr 192.168.10.10 1719
[VG1-voice-gk] ras-on
2) Configure H.323 gateway 2
# Configure the Ethernet interface.
[VG2] interface ethernet 0
[VG2-Ethernet0] ip address 192.168.40.3 255.255.255.0
[VG2-Ethernet0] quit
# Configure voice entities.
[VG2] voice-setup
[VG2-voice] dial-program
[VG2-voice-dial] entity 8888 voip
[VG2-voice-dial-entity8888] address ras
[VG2-voice-dial-entity8888] match-template ....
[VG2-voice-dial-entity8888] quit
[VG2-voice-dial] entity 8802 pots
[VG2-voice-dial-entity8802] line 0
[VG2-voice-dial-entity8802] match-template 8802
[VG2-voice-dial-entity8802] return
# Configure the gatekeeper client.
[VG2] voice-setup
[VG2-voice] gk-client
[VG2-voice-gk] gw-id h323gateway2
[VG2-voice-gk] gw-address ip 192.168.40.3
[VG2-voice-gk] gk-id xeippbx gk-addr 192.168.10.10 1719
[VG2-voice-gk] ras-on
3) Configure SIP user agent 1
# Configure the Ethernet interface.
[UA] interface ethernet 0
[UA-Ethernet0] ip address 192.168.20.2 255.255.255.0
[UA-Ethernet0] quit
# Configure voice entities.
[UA] voice-setup
[UA-voice] dial-program
[UA-voice-dial] entity 8888 voip
[UA-voice-dial-entity8888] address sip proxy
[UA-voice-dial-entity8888] match-template ....
[UA-voice-dial] entity 8802 pots
[UA-voice-dial-entity8802] line 0
[UA-voice-dial-entity8802] match-template 8802
[UA-voice-dial-entity8802] return
# Configure the SIP gateway (user agent).
[UA] voice-setup
[UA-voice] sip
[UA-voice-sip] sip-id sipuseragent1
[UA-voice-sip] sip-server master ip 192.168.10.10 port default all
[UA-voice-sip] register-enable on
4) Configure the XE IP PBX
# Configure the Ethernet interface.
[XE] interface ethernet 0/0
[XE-Ethernet0/0] ip address 192.168.10.10 255.255.255.0
# Configure the gatekeeper and the SIP proxy server.
[XE] process-server
[XE-ps] ps-config xeippbx interface Ethernet 0/0
[XE-ps] heartbeat password xe200
[XE-ps] ls-mode 0 local
[XE-ps] start
[XE-ps] gatekeeper
[XE-ps-gk] start
[XE-ps-gk] quit
[XE-ps] sip
[XE-ps-sip] start
5) Configure the LS
# Configure the LS.
[XE] location-server
[XE-ls] ls-config interface Ethernet 0/0
[XE-ls] call-mode h323 routed
[XE-ls] call-mode sip routed
[XE-ls] policy random-selection disable
[XE-ls] process-server xeippbx
[XE-ls-ps-xeippbx] heartbeat password xe200
[XE-ls-ps-xeippbx] quit
[XE-ls] gateway h323gateway1
[XE-ls-gw-h323gateway1] device-type h323
[XE-ls-gw-h323gateway1] dynamic-ip enable
[XE-ls-gw-h323gateway1] quit
[XE-ls] gateway h323gateway2
[XE-ls-gw-h323gateway2] device-type h323
[XE-ls-gw-h323gateway2] dynamic-ip enable
[XE-ls-gw-h323gateway2] prefix 8802
[XE-ls-gw-h323gateway2 8802] priority 12
[XE-ls-gw-h323gateway2 8802] quit
[XE-ls-gw-h323gateway2] quit
[XE-ls] gateway sipuseragent1
[XE-ls-gw-sipuseragent1] device-type sip
[XE-ls-gw-sipuseragent1] dynamic-ip enable
[XE-ls-gw-sipuseragent1] prefix 8802
[XE-ls-gw-sipuseragent1 8802] priority 12
[XE-ls-gw-sipuseragent1 8802] quit
[XE-ls-gw-sipuseragent1] quit
[XE-ls] start
Three VGs function as SIP UAs. They place SIP calls and implement multiple called parties orderly ringing through an XE IP PBX.
PS and LS are co-located on the XE IP PBX.
Figure 3-11 Network diagram for multiple called parties orderly ringing
& Note:
This example assumes that the SIP user agent 1, SIP user agent 2, SIP user agent 3, and XE IP PBX are all reachable to each other and omits the related route configuration, which you can do as required before performing the following configuration.
1) Configure SIP server
# Configure the Ethernet interface.
[XE] interface ethernet 0/0
[XE-Ethernet0/0] ip address 192.168.10.10 255.255.255.0
[XE-Ethernet0/0] quit
# Configure proxy server.
[XE] process-server
[XE-ps] ps-config xe200 interface Ethernet 0/0
[XE-ps] heartbeat password xe200
[XE-ps] ls-mode 0 local
[XE-ps] start
[XE-ps] sip
[XE-ps-sip] start
# Configure LS.
[XE] location-server
[XE-ls] ls-config interface Ethernet 0/0
[XE-ls] call-mode sip routed
[XE-ls] start
[XE-ls] process-server xe200
[XE-ls-ps-xe200] heartbeat password xe200
[XE-ls-ps-xe200] quit
[XE-ls]gateway ua001
[XE-ls-gw-ua001] device-type sip
[XE-ls-gw-ua001] dynamic-ip enable
[XE-ls-gw-ua001] prefix 8801
[XE-ls-gw-ua0018801] priority 12
[XE-ls-gw-ua0018801] quit
[XE-ls-gw-ua001] quit
[XE-ls] gateway ua002
[XE-ls-gw-ua002] device-type sip
[XE-ls-gw-ua002] dynamic-ip enable
[XE-ls-gw-ua002] prefix 8802
[XE-ls-gw-ua0028802] priority 12
[XE-ls-gw-ua0028802] quit
[XE-ls-gw-ua002] quit
[XE-ls] gateway ua003
[XE-ls-gw-ua003] device-type sip
[XE-ls-gw-ua003] dynamic-ip enable
[XE-ls-gw-ua003] prefix 8802
[XE-ls-gw-ua0038802] priority 11
[XE-ls-gw-ua0038802] quit
[XE-ls-gw-ua003] quit
2) Configure SIP user agent 1
# Configure the Ethernet interface.
[UA001] interface ethernet 0/0
[UA001-Ethernet0/0] ip address 192.168.30.2 255.255.255.0
[UA001-Ethernet0/0] quit
# Configure voice entities.
[UA001] voice-setup
[UA001-voice] dial-program
[UA001-voice-dial] select-rule type-first 2 1 3
[UA001-voice-dial] entity 1111 voip
[UA001-voice-dial-entity1111] address sip proxy
[UA001-voice-dial-entity1111] match-template ....
[UA001-voice-dial-entity1111] quit
[UA001-voice-dial] entity 8801 pots
[UA001-voice-dial-entity8801] line 0
[UA001-voice-dial-entity8801] match-template 8801
[UA001-voice-dial-entity8801] return
# Configure SIP user agent.
[UA001] voice-setup
[UA001-voice] sip
[UA001-voice-sip] sip-server master 192.168.10.10
[UA001-voice-sip] sip-id ua001
[UA001-voice-sip] register-enable on
3) Configure SIP user agent 2
# Configure the Ethernet interface.
[UA002] interface ethernet 0/0
[UA002-Ethernet0/0] ip address 192.168.40.3 255.255.255.0
[UA002-Ethernet0/0] quit
# Configure voice entities.
[UA002] voice-setup
[UA002-voice] dial-program
[UA002-voice-dial] select-rule type-first 2 1 3
[UA002-voice-dial] entity 1111 voip
[UA002-voice-dial-entity1111] address sip proxy
[UA002-voice-dial-entity1111] match-template ....
[UA002-voice-dial-entity1111] quit
[UA002-voice-dial] entity 8802 pots
[UA002-voice-dial-entity8802] line 0
[UA002-voice-dial-entity8802] match-template 8802
[UA002-voice-dial-entity8802] return
# Configure SIP user agent.
[UA002] voice-setup
[UA002-voice] sip
[UA002-voice-sip] sip-server master 192.168.10.10
[UA002-voice-sip] sip-id ua002
[UA002-voice-sip] register-enable on
4) Configure SIP user agent 3
# Configure the Ethernet interface.
[UA003] interface ethernet 0/0
[UA003-Ethernet0/0] ip address 192.168.20.4 255.255.255.0
[UA003-Ethernet0/0] quit
# Configure voice entities.
[UA003] voice-setup
[UA003-voice] dial-program
[UA003-voice-dial] select-rule type-first 2 1 3
[UA003-voice-dial] entity 1111 voip
[UA003-voice-dial-entity1111] address sip proxy
[UA003-voice-dial-entity1111] match-template ....
[UA003-voice-dial-entity1111] quit
[UA003-voice-dial] entity 8802 pots
[UA003-voice-dial-entity8802] line 0
[UA003-voice-dial-entity8802] match-template 8802
[UA003-voice-dial-entity8802] return
# Configure SIP user agent.
[UA003] voice-setup
[UA003-voice] sip
[UA003-voice-sip] sip-server master 192.168.10.10
[UA003-voice-sip] sip-id ua003
[UA003-voice-sip] register-enable on
An NAT/FW separates a private network from a public network. The public network contains one voice gateway (H.323 gateway 2) and two XE IP PBXs. One XE IP PBX operates as an LS (location server), and the other operates as a PS (process server 2). The private network contains one voice gateway (H.323 gateway 1) and one XE IP PBX. This XE IP PBX operates as a PS (process server 1).
Figure 3-12 Network diagram for NAT/FW tunnel traversal between private and public networks
& Note:
This example assumes that the private network interfaces of H.323 gateway 1, XE IP PBX 1 and NAT/FW are reachable to each other, and the public network interfaces of H.323 gateway 2, XE IP PBX 2, XE IP PBX 3 and NAT/FW are reachable to each other. So this example omits the related route configuration, which you can do as required before performing the following configuration.
1) Configure H.323 gateway 1
# Configure the Ethernet interface.
[VG1] interface ethernet 0
[VG1-Ethernet0] ip address 192.168.2.11 255.255.255.0
[VG1-Ethernet0] quit
# Configure voice entities.
[VG1] voice-setup
[VG1-voice] dial-program
[VG1-voice-dial] entity 8888 voip
[VG1-voice-dial-entity8888] address ras
[VG1-voice-dial-entity8888] match-template ....
[VG1-voice-dial-entity8888] quit
[VG1-voice-dial] entity 8801 pots
[VG1-voice-dial-entity8801] line 0
[VG1-voice-dial-entity8801] match-template 8801
[VG1-voice-dial-entity8801] return
# Configure the gatekeeper client.
[VG1] voice-setup
[VG1-voice] gk-client
[VG1-voice-gk] gw-id h323gateway1
[VG1-voice-gk] gw-address ip 192.168.2.11
[VG1-voice-gk] gk-id xeippbx1 gk-addr 192.168.1.10 1719
[VG1-voice-gk] ras-on
2) Configure H.323 gateway 2
# Configure the Ethernet interface.
[VG2] interface ethernet 0
[VG2-Ethernet0] ip address 1.1.3.12 255.255.255.0
[VG2-Ethernet0] quit
# Configure voice entities.
[VG2] voice-setup
[VG2-voice] dial-program
[VG2-voice-dial] entity 8888 voip
[VG2-voice-dial-entity8888] address ras
[VG2-voice-dial-entity8888] match-template ....
[VG2-voice-dial] entity 8802 pots
[VG2-voice-dial-entity8802] line 0
[VG2-voice-dial-entity8802] match-template 8802
[VG2-voice-dial-entity8802] return
# Configure the gatekeeper client
[VG2] voice-setup
[VG2-voice] gk-client
[VG2-voice-gk] gw-id h323gateway2
[VG2-voice-gk] gw-address ip 1.1.3.12
[VG2-voice-gk] gk-id xeippbx2 gk-addr 1.1.1.11 1719
[VG2-voice-gk] ras-on
3) Configure process server 1
# Configure the Ethernet interface.
[XE1] interface ethernet 0/0
[XE1-Ethernet0/0] ip address 192.168.1.10 255.255.255.0
[XE1-Ethernet0/0] quit
[XE1] ip route-static 0.0.0.0 0.0.0.0 192.168.3.2
# Configure the gatekeeper.
[XE1] process-server
[XE1-ps] ps-config xeippbx1 interface Ethernet 0/0
[XE1-ps] heartbeat password xe200
[XE1-ps] ls-mode 0 remote ip-address 1.1.1.10
[XE1-ps] start
[XE1-ps] gatekeeper
[XE1-ps-gk] start
4) Configure process server 2
# Configure the Ethernet interface.
[XE2] interface ethernet 0/0
[XE2-Ethernet0/0] ip address 1.1.2.11 255.255.255.0
[XE2-Ethernet0/0] quit
# Configure the gatekeeper.
[XE2] process-server
[XE2-ps] ps-config xeippbx2 interface Ethernet 0/0
[XE2-ps] heartbeat password xe200
[XE2-ps] ls-mode 0 remote ip-address 1.1.1.10
[XE2-ps] start
[XE2-ps] gatekeeper
[XE2-ps-gk] start
5) Configure the LS
# Configure the Ethernet interface.
[XE3] interface ethernet 0/0
[XE3-Ethernet0/0] ip address 1.1.1.10 255.255.255.0
[XE3-Ethernet0/0] quit
# Configure the LS.
[XE3] location-server
[XE3-ls] ls-config interface Ethernet 0/0
[XE3-ls] call-mode h323 routed
[XE3-ls] start
[XE3-ls] domain PriDomain
[XE3-ls-domain-PriDomain] attribute private
[XE3-ls-domain-PriDomain] quit
[XE3-ls] domain PubDomain
[XE3-ls-domain-PubDomain] attribute public
[XE3-ls-domain-PubDomain] quit
[XE3-ls] process-server xeippbx1
[XE3-ls-ps-xeippbx1] heartbeat password xe200
[XE3-ls-ps-xeippbx1] belongto PriDomain
[XE3-ls-ps-xeippbx1] quit
[XE3-ls] process-server xeippbx2
[XE3-ls-ps-xeippbx2] heartbeat password xe200
[XE3-ls-ps-xeippbx2] belongto PubDomain
[XE3-ls-ps-xeippbx2] quit
[XE3-ls] nat&fw
[XE3-ls-nat&fw] tunnelpeer tunnelpeer01 private xeippbx1 1.1.2.11 port 9600 public xeippbx2 1.1.4.2 port 9700
[XE3-ls-nat&fw] quit
[XE3-ls] process-server xeippbx1
[XE3-ls-ps-xeippbx1] tunnel enable
[XE3-ls-ps-xeippbx1] quit
[XE3-ls] process-server xeippbx2
[XE3-ls-ps-xeippbx2] tunnel enable
[XE3-ls-ps-xeippbx2] quit
[XE3-ls] gateway h323gateway1
[XE3-ls-gw-h323gateway1] device-type h323
[XE3-ls-gw-h323gateway1] dynamic-ip enable
[XE3-ls-gw-h323gateway1] quit
[XE3-ls] gateway h323gateway2
[XE3-ls-gw-h323gateway2] device-type h323
[XE3-ls-gw-h323gateway2] dynamic-ip enable
6) Configure the NAT/FW.
& Note:
This example uses SecPath 1000 of H3C as the NAT/FW device. Configurations may differ with the NAT/FW device that you use for networking.
# Configure Ethernet interfaces.
<SECPATH> system-view
[SECPATH] interface GigabitEthernet 0/0
[SECPATH-GigabitEthernet0/0] ip address 1.1.4.2 255.255.255.0
[SECPATH-GigabitEthernet0/0] quit
[SECPATH] interface GigabitEthernet 0/1
[SECPATH-GigabitEthernet0/1] ip address 192.168.3.2 255.255.255.0
[SECPATH-GigabitEthernet0/1] quit
# Configure an ACL (access control list).
[SECPATH] acl number 2001
[SECPATH-acl-basic-2001] rule permit source 192.168.1.0 0.0.0.255
[SECPATH-acl-basic-2001] quit
[SECPATH] interface GigabitEthernet 0/0
[SECPATH-GigabitEthernet0/0] nat outbound 2001
[SECPATH-GigabitEthernet0/0] nat server protocol udp global 1.1.4.2 9700 inside 192.168.1.10 9700
Two NAT/FW devices separate two private networks (private network 1 and private network 2) from the public network. The public network contains a XE IP PBX, which operates as both LS and PS. Both private network 1 and private network 2 contain a voice gateway and an XE IP PBX serving as a PS.
Figure 3-13 Network diagram for NAT/FW tunnel traversal between two private networks across one public network
& Note:
This example assumes that the private network interfaces of H.323 gateway 1, XE IP PBX 1 and NAT/FW 1 are all reachable to each other, the private network interfaces of H.323 gateway 2, XE IP PBX 3 and NAT/FW 2 are reachable to each other, and the public interface of NAT/FW 1, the public interface of NAT/FW 2 and XE IP PBX are also reachable to each other. So this example omits the related route configuration, which you can do as required before performing the following configuration.
1) Configure H.323 gateway 1
# Configure the Ethernet interface.
[VG1] interface ethernet 0
[VG1-Ethernet0] ip address 192.168.3.11 255.255.255.0
[VG1-Ethernet0] quit
# Configure voice entities.
[VG1] voice-setup
[VG1-voice] dial-program
[VG1-voice-dial] entity 8888 voip
[VG1-voice-dial-entity8888] address ras
[VG1-voice-dial-entity8888] match-template ....
[VG1-voice-dial-entity8888] quit
[VG1-voice-dial] entity 8801 pots
[VG1-voice-dial-entity8801] line 0
[VG1-voice-dial-entity8801] match-template 8801
[VG1-voice-dial-entity8801] return
# Configure the gatekeeper client.
[VG1] voice-setup
[VG1-voice] gk-client
[VG1-voice-gk] gw-id h323gateway1
[VG1-voice-gk] gw-address ip 192.168.3.11
[VG1-voice-gk] gk-id xeippbx1 gk-addr 192.168.1.10 1719
[VG1-voice-gk] ras-on
2) Configure H.323 gateway 2
# Configure the Ethernet interface.
[VG2] interface ethernet 0
[VG2-Ethernet0] ip address 10.10.30.12 255.255.255.0
[VG2-Ethernet0] quit
# Configure voice entities.
[VG2] voice-setup
[VG2-voice] dial-program
[VG2-voice-dial] entity 8888 voip
[VG2-voice-dial-entity8888] address ras
[VG2-voice-dial-entity8888] match-template ....
[VG2-voice-dial] entity 8802 pots
[VG2-voice-dial-entity8802] line 0
[VG2-voice-dial-entity8802] match-template 8802
[VG2-voice-dial-entity8802] return
# Configure the gatekeeper client.
[VG2] voice-setup
[VG2-voice] gk-client
[VG2-voice-gk] gw-id h323gateway2
[VG2-voice-gk] gw-address ip 10.10.30.12
[VG2-voice-gk] gk-id xeippbx3 gk-addr 10.10.10.10 1719
[VG2-voice-gk] ras-on
3) Configure process server 1
# Configure the Ethernet interface.
[XE1] interface ethernet 0/0
[XE1-Ethernet0/0] ip address 192.168.1.10 255.255.255.0
[XE1-Ethernet0/0] quit
[XE1] ip route-static 0.0.0.0 0.0.0.0 192.168.2.2
# Configure the gatekeeper.
[XE1] process-server
[XE1-ps] ps-config xeippbx1 interface Ethernet 0/0
[XE1-ps] heartbeat password xe200
[XE1-ps] ls-mode 0 remote ip-address 1.1.1.10
[XE1-ps] start
[XE1-ps] gatekeeper
[XE1-ps-gk] start
4) Configure process server 2
# Configure the Ethernet interface.
[XE2] interface ethernet 0/0
[XE2-Ethernet0/0] ip address 1.1.1.10 255.255.255.0
[XE2-Ethernet0/0] quit
# Configure the gatekeeper.
[XE2] process-server
[XE2-ps] ps-config xeippbx2 interface Ethernet 0/0
[XE2-ps] heartbeat password xe200
[XE2-ps] ls-mode 0 local
[XE2-ps] start
[XE2-ps] gatekeeper
[XE2-ps-gk] start
5) Configure process server 3
# Configure the Ethernet interface.
[XE3] interface ethernet 0/0
[XE3-Ethernet0/0] ip address 10.10.10.10 255.255.255.0
[XE3-Ethernet0/0] quit
[XE3] ip route-static 0.0.0.0 0.0.0.0 10.10.20.2
# Configure the gatekeeper.
[XE3] process-server
[XE3-ps] ps-config xeippbx3 interface Ethernet 0/0
[XE3-ps] heartbeat password xe200
[XE3-ps] ls-mode 0 remote ip-address 1.1.1.10
[XE3-ps] start
[XE3-ps] gatekeeper
[XE3-ps-gk] start
6) Configure the LS
# Configure the LS.
[XE2] location-server
[XE2-ls] ls-config interface Ethernet 0/0
[XE2-ls] call-mode h323 routed
[XE2-ls] start
[XE2-ls] domain PriDomain01
[XE2-ls-domain-PriDomain01] attribute private
[XE2-ls-domain-PriDomain01] quit
[XE2-ls] domain PriDomain02
[XE2-ls-domain-PriDomain02] attribute private
[XE2-ls-domain-PriDomain02] quit
[XE2-ls] domain PubDomain
[XE2-ls-domain-PubDomain] attribute public
[XE2-ls-domain-PubDomain] quit
[XE2-ls] process-server xeippbx1
[XE2-ls-ps-xeippbx1] heartbeat password xe200
[XE2-ls-ps-xeippbx1] belongto PriDomain01
[XE2-ls-ps-xeippbx1] quit
[XE2-ls] process-server xeippbx2
[XE2-ls-ps-xeippbx2] heartbeat password xe200
[XE2-ls-ps-xeippbx2] belongto PubDomain
[XE2-ls-ps-xeippbx2] quit
[XE2-ls] process-server xeippbx3
[XE2-ls-ps-xeippbx3] heartbeat password xe200
[XE2-ls-ps-xeippbx3] belongto PriDomain02
[XE2-ls-ps-xeippbx3] quit
[XE2-ls] nat&fw
[XE2-ls-nat&fw] tunnelpeer tunnelpeer01 private xeippbx1 1.1.1.10 port 9600 public xeippbx2 1.1.2.3 port 9700
[XE2-ls-nat&fw] tunnelpeer tunnelpeer02 private xeippbx3 1.1.1.10 port 9601 public xeippbx2 1.1.3.2 port 9701
[XE2-ls-nat&fw] quit
[XE2-ls] process-server xeippbx1
[XE2-ls-ps-xeippbx1] tunnel enable
[XE2-ls-ps-xeippbx1] quit
[XE2-ls] process-server xeippbx2
[XE2-ls-ps-xeippbx2] tunnel enable
[XE2-ls-ps-xeippbx2] quit
[XE2-ls] process-server xeippbx3
[XE2-ls-ps-xeippbx3] tunnel enable
[XE2-ls-ps-xeippbx3] quit
[XE2-ls] gateway h323gateway1
[XE2-ls-gw-h323gateway1] device-type h323
[XE2-ls-gw-h323gateway1] dynamic-ip enable
[XE2-ls-gw-h323gateway1] quit
[XE2-ls] gateway h323gateway2
[XE2-ls-gw-h323gateway2] device-type h323
[XE2-ls-gw-h323gateway2] dynamic-ip enable
7) Configure NAT/FW 1.
& Note:
This example uses SecPath 1000 of H3C as the NAT/FW device. Configurations may differ with the NAT/FW device that you use for networking.
# Configure Ethernet interfaces.
<SECPATH1> system-view
[SECPATH1] interface GigabitEthernet 0/0
[SECPATH1-GigabitEthernet0/0] ip address 1.1.2.3 255.255.255.0
[SECPATH1-GigabitEthernet0/0] quit
[SECPATH1] interface GigabitEthernet 0/1
[SECPATH1-GigabitEthernet0/1] ip address 192.168.2.2 255.255.255.0
[SECPATH1-GigabitEthernet0/1] quit
# Configure an ACL.
[SECPATH1] acl number 2001
[SECPATH1-acl-basic-2001] rule permit source 192.168.1.0 0.0.0.255
[SECPATH1-acl-basic-2001] quit
[SECPATH1] interface GigabitEthernet 0/0
[SECPATH1-GigabitEthernet0/0] nat outbound 2001
[SECPATH1-GigabitEthernet0/0] nat server protocol udp global 1.1.2.3 9700 inside 192.168.1.10 9700
8) Configure NAT/FW 2.
# Configure Ethernet interfaces.
<SECPATH2> system-view
[SECPATH2] interface GigabitEthernet 0/0
[SECPATH2-GigabitEthernet0/0] ip address 1.1.3.2 255.255.255.0
[SECPATH2-GigabitEthernet0/0] quit
[SECPATH2] interface GigabitEthernet 0/1
[SECPATH2-GigabitEthernet0/1] ip address 10.10.20.2 255.255.255.0
[SECPATH2-GigabitEthernet0/1] quit
# Configure an ACL.
[SECPATH2] acl number 2001
[SECPATH2-acl-basic-2001] rule permit source 10.10.10.0 0.0.0.255
[SECPATH2-acl-basic-2001] quit
[SECPATH2] interface GigabitEthernet 0/0
[SECPATH2-GigabitEthernet0/0] nat outbound 2001
[SECPATH2-GigabitEthernet0/0] nat server protocol udp global 1.1.3.2 9701 inside 10.10.10.10 9701
On an H.323 gatekeeper, a symptom may result from different causes. Follow the description to diagnose and correct the problems you encounter.
Cause: The IP address of the involved interface is not configured on the gatekeeper.
Diagnosis: Use the display current-configuration interface command to check if the involved interface on the gatekeeper is configured with an IP address.
Solution: Configure the involved interface on the gatekeeper with an IP address.
1) Cause 1: The gatekeeper is not started.
Diagnosis: On the gatekeeper use the display current-configuration command to check if the PS is started in PS view and if the gatekeeper is started in GK view.
Solution: On the gatekeeper run the start command in PS view and then the start command in GK view.
2) Cause 2: The LS is not started.
Diagnosis: Use the display current-configuration command to check if the LS is started in LS view.
Solution: Run the start command in LS view.
3) Cause 3: The gateway is not activated.
Diagnosis: Check the configuration on the gateway if the gateway is permitted to initiate a request to the gatekeeper for registration.
Solution: Take the VG series voice gateways for example, use the ras-on command to activate the H.323 gateway in GK-Client view.
4) Cause 4: H.323 gateway fails to register with the LS.
Diagnosis: Use the display location-server gateway h323 command to check if the corresponding H.323 gateway exists in LS view on the LS (the two correspond to each other by the gateway device identifiers). Meanwhile, check the registration status of the gateway (the offline state indicates that the gateway failed to register).
Solution 1: In LS view, add the corresponding H.323 gateway and assign the related static route number.
Solution 2: On the gateway, use the gw-id command in GK-Client view to configure the device identifier consistent with that on the LS.
Solution 3: On the gateway use the undo ras-on command in GK-Client view to disable the H.323 gateway, and then use the ras-on command to reactivate it.
5) Cause 5: The state of the involved H.323 gateway on the LS is disabled.
Diagnosis: Use the display current-configuration command to check if the device status in LS-GW view is disabled (the two correspond to each other by the gateway device identifiers).
Solution: In LS-GW view, use the device-status command to set the device status to forever-up or normal.
6) Cause 6: The corresponding gateway on the LS has no corresponding call numbers (the calling number or the called number).
Diagnosis: On the LS, use the display current-configuration command to check for the corresponding call numbers in LS-GW view: whether the calling number and called number are configured on the calling and called H.323 gateways respectively.
Solution: In LS-GW view, configure the calling number and called number on the corresponding gateways.
1) Cause 1: No corresponding gatekeeper (corresponded by PS identifier) is configured on the LS.
Diagnosis: On the LS use the display current-configuration command to check for the corresponding gatekeeper (corresponded by PS identifier) in LS view.
Solution: On the LS add the corresponding gatekeeper in LS view and assign its PS identifier.
2) Cause 2: The configuration of the PS on the LS is not consistent with that on the PS.
Diagnosis: Use the display current-configuration command to view the configuration of the gatekeeper in LS view on the LS and in PS view on the PS respectively, and check for the consistency of heartbeat passwords.
Solution 1: On the LS, configure the heartbeat password in LS-PS view for the PS, consistent with those configured on the gatekeeper.
Solution 2: On the PS, configure the heartbeat password, consistent with those configured in LS-PS view of the LS.
3) Cause 3: A remote LS is configured on the gatekeeper, but its IP address or port number may be incorrect.
Diagnosis: Use the display current-configuration command to view the IP address and port number of the remote LS in PS view on the gatekeeper and in LS view on the LS and check for their consistency.
Solution: On the gatekeeper, configure the IP address and port number of the remote LS in PS view of the gatekeeper, consistent with the configuration on the LS.
On a SIP Server, a symptom may result from different causes. Follow the description to diagnose and correct the problems you encounter.
Cause: The IP address of the involved interface is not configured on the proxy server.
Diagnosis: Use the display current-configuration interface command to view if the involved interface on the proxy server is configured with an IP address.
Solution: Configure the involved interface on the proxy server with an IP address.
1) Cause 1: The IP addresses or port numbers configured on the proxy server and the UA do not match.
Diagnosis: On the LS use the display current-configuration command to see if the IP address and port number in LS-GW view match those for the gateway configured on the UA.
Solution: On the UA, configure the IP address and port number of the proxy server, which match those configured on the proxy server.
2) Cause 2: The transport protocols configured on the proxy server and the UA do not match.
Diagnosis: On the LS use the display current-configuration command to see if the transport protocol in LS-GW view matches that configured on the UA.
Solution 1: On the PS use the transport command in LS-GW view to configure the transport protocol, matching that configured on the UA.
Solution 2: On the UA use the transport command to configure the transport protocol, matching that configured on the PS.
1) Cause 1: The proxy server is not started.
Diagnosis: On the proxy server use the display current-configuration command to check if the PS is started in PS view and if the SIP Server is started in SIP view.
Solution: On the PS run the start command in PS view and then the start command in SIP view.
2) Cause 2: The LS is not started.
Diagnosis: On the LS use the display current-configuration command to check if the LS is started in LS view.
Solution: On the LS, run the start command in LS view.
3) Cause 3: No corresponding UA is configured on the LS.
Diagnosis: On the LS use the display current-configuration command to check if the corresponding UA exists in LS view (the two correspond to each other by the gateway device identifiers).
Solution: In LS view, add the corresponding UA, and configure the corresponding call numbers.
4) Cause 4: The device status of the UA on the LS is disabled.
Diagnosis: On the LS use the display current-configuration command to check if the device status in LS-GW view is disabled (the two correspond to each other by the gateway device identifiers).
Solution: In LS-GW view use the device-status command to set the device status to forever-up or normal.
5) Cause 5: The device status of the corresponding UA on the LS is normal, but the registration status is offline.
Diagnosis: On the LS use the display location-server gateway all command to check if the registration status of the corresponding gateway (specified by the device identifier) is offline.
Solution: Configure correctly on the UA to start the dynamic registration of the gateway, making the registration status of the corresponding gateway online.
6) Cause 6: The corresponding UA on the LS has no corresponding call numbers (calling number and called number).
Diagnosis: On the LS, use the display current-configuration command to check for the corresponding call numbers in LS-GW view: whether the corresponding calling number and called number are configured on the calling and called UAs, respectively.
Solution: In LS-GW view, configure the corresponding calling number and called number.
1) Cause 1: No corresponding proxy server is configured on the LS (corresponded by device identifiers).
Diagnosis: On the LS, use the display current-configuration command to check for the corresponding proxy server in LS view (the two correspond to each other by device identifiers).
Solution: On the LS, add the corresponding proxy server in LS view, and assign its device identifier. Set a heartbeat password if authentication is required.
2) Cause 2: The configuration of the corresponding proxy server on the LS does no match that configured on the proxy server.
Diagnosis: Use the display current-configuration command to view the configuration of the corresponding proxy server in LS view on the LS and in PS view on the proxy server respectively, and check for the consistency of the device identifiers and heartbeat passwords (if authentication is needed).
Solution 1: On the LS, in LS-PS view configure the device identifier and the heartbeat password (if authentication is needed) for the proxy server, making them consistent with those configured on the proxy server.
Solution 2: On the proxy server, configure the device identifier and the heartbeat password (if authentication is needed), making them consistent with those configured for the proxy server in LS-PS view on the LS.
3) Cause 3: A remote LS is configured on the proxy server, but its IP address and port are not consistent with those configured on the LS.
Diagnosis: Use the display current-configuration command to view the IP address and port number of the remote LS in PS view on the proxy server and in LS view on the LS respectively, and check for their consistency.
Solution 1: On the proxy server, configure the IP address and port number for the remote LS in PS view, making them consistent with those configured on the LS.
Solution 2: On the LS, configure the IP address and port number in LS view, making them consistent with those configured on the proxy server.
Cause: The heartbeat passwords of the proxy server and the LS are not consistent.
Diagnosis: Use the display location-server process-server all command to check if the heartbeat password of the PS is consistent with that on the LS.
Solution 1: On the LS, configure the heartbeat password in PS view, making it consistent with that configured on the LS.
Solution 2: On the LS, configure the heartbeat password in LS-PS view, making it consistent with that configured on the proxy server.
1) Cause 1: Multiple UAs are not configured with the same called number.
Diagnosis: Use the display current-configuration command to check if the same called number is configured in LS-GW view.
Solution: In LS-GW view, use the prefix or subscriber command to configure the same called numbers, and prioritize them in descending order.
2) Cause 2: Multiple UAs have the same numbers configured with the same priority.
Diagnosis: Use the display current-configuration command to check if the same called numbers are configured with the same priority in each LS-GW view.
Solution: In each LS-GW view, use the prefix or subscriber command to configure the same called numbers, and prioritize them in descending order.
1) Cause 1: Multiple UAs are not configured with the same called number.
Diagnosis: On the LS, use the display current-configuration command to check if the same called number is configured in each LS-GW view.
Solution: In LS-GW view, use the prefix or subscriber command to configure the same called numbers, and prioritize them in the same order.
2) Cause 2: Multiple UAs have the same number configured with different priorities.
Diagnosis: On the LS, use the display current-configuration command to check if the same called number is configured with the same priority in LS-GW view.
Solution: In each LS-GW view, use the prefix or subscriber command prioritize the same called numbers in the same order.
3) Cause 3: The random selection function is enabled.
Diagnosis: Use the display current-configuration command on the LS to check if the random selection function is disabled.
Solution: In LS view, use the policy random-selection disable command to disable the function.
Cause: The dynamic IP registration of the UA is disabled.
Diagnosis: On the LS use the display location-server gateway command to check the dynamic information. If the registration status is online, but the IP address is not consistent with that of the actual UA, the dynamic IP registration fails. Check to see if dynamic registration is enabled in LS-GW view by the display current-configuration command.
Solution: In LS-GW view, use the dynamic-ip command to enable the dynamic IP registration.
Cause: The dynamic IP registration on the UA is disabled.
Diagnosis: On the LS, use the display current-configuration command to check in LS-GW view if the manufacturer is h3c.
Solution: In LS-GW view, use the manufacturer command to set the manufacturer to h3c.
1) Cause 1: The IP address and port number for the UA configured on the LS do not match those configured on the UA.
Diagnosis: Use the display location-server gateway xxx command to check the dynamic information on the LS (xxx corresponds to the device identifier of the UA). If the registration status is offline, the registration fails. Use the display current-configuration command to check in LS-GW view if the IP address and port number are consistent with those configured on the UA.
Solution: On the LS, configure the IP address and port number for the UA in LS-GW view, making them consistent with those configured on the UA.
2) Cause 2: If the authentication of the UA registration is enabled on the LS, the authentication password or default password in LS-GW view is inconsistent with that configured on the UA.
Diagnosis: Use the authentication enable command to check if the authentication is enabled in LS-GW view. If yes, check if the configured password is consistent with that configured on the UA.
Solution 1: In LS-GW view, use the password command to configure the password, making it consistent with that configured on the UA.
Solution 2: In LS-GW view, use the authentication disable command disable the authentication.
Cause: Similar to 4.2.1 I. “The proxy server is unreachable from the SIP UA ”.
Diagnosis: Similar to 4.2.1 I. “The proxy server is unreachable from the SIP UA ”.
Solution: Similar to 4.2.1 I. “The proxy server is unreachable from the SIP UA ”.
Cause: Similar to The proxy server is reachable from the SIP UA, but calls cannot be set up.
Diagnosis: Similar to The proxy server is reachable from the SIP UA, but calls cannot be set up.
Solution: Similar to The proxy server is reachable from the SIP UA, but calls cannot be set up.
Cause: The IP address of the gateway to be configured is in collision with that of a configured gateway.
Diagnosis: On the LS, use the display current-configuration command to check in LS-GW view to check if the IP address for configuration is already used.
Solution: In LS-GW view, use the ip-address command to configure an IP address not conflicting with any other for the gateway.
Cause: The IP address of the office device to be configured is in collision with that of a configured office device.
Diagnosis: On the LS, use the display current-configuration command to check in OFFICEGROUP-OFFICE view if the IP address intended for configuration is already used.
Solution: In LS-OFFICEGROUP-OFFICE view, use the ip-address command to configure an IP address not in conflict with any other for the office device.
Cause: When the LS is in the remote mode and the system time of the PS is ahead of the LS’s, the PS is in the idle state.
Diagnosis: Use the display clock command to view the system time.
Solution: Use the same system time on the two devices or make the system time of the LS ahead of the PS’s. Use the heartbeat-time-range command to adjust the threshold values of the heartbeat, enabling the PS to pass authentication.
Cause: When the SIP terminal registers, the wrong IP or 0.0.0.0 displays.
Diagnosis: Check if the IP address in the registration message is valid through the debugging information of the XE IP PBX.
Solution: Configure the correct IP address for the SIP terminal.
