Find answers to your technical questions and learn how to use our products
Search suggestions:
Find answers to your technical questions and learn how to use our products
Search suggestions:
Configures within-region and between-region connectivity settings for all VoIP resources and endpoints within a given IP region. The first page is used to modify the audio and QoS settings. The Codec Set field on this page reflects the CODEC set that must be used for connections between telephones within this region or between telephones and MedPro/Prowler boards and gateways within this region. The ability to do NAT shuffling for direct IP-to-IP audio connections is also supported.
Example command: change ip-network-region n, where n is the network region number.
Use this field to assign a network region group to the network region. You can enter a value from:
1 to 2000 for large systems.
1 to 250 for small systems.
Do not leave the field blank.
You can assign multiple network regions to the same network region group. During translations upgrade, the system assigns a network region group to each network region. For example, network region 45 will be assigned to network region group 45. The network region group names will also be assigned. If the network region has a name, the name is used for the associated network region group name. If the network region name is blank, a unique network region group name is created by appending the network region group number to the characters NRG. For example, NRG 16.
The domain for which this network region is responsible. The system displays the Authoritative Domain in the From header of any SIP messages. Accepts a name or IP address consisting of up to 20 characters.
If the Multinational Locations feature is enabled, and IP telephones derive their network region from the IP Network Map, administer this field with a valid value (1 to 2000). With this, the IP endpoints can use the right VoIP resources.
Valid Entry |
Usage |
|---|---|
1 to 250 or 1 to 2000 Depending on the server configuration. For more information, see Avaya Aura® Communication Manager System Capacities Table. |
Assigns the location number to the IP network region. Correct date and time information, and trunk routing based on IP network region can be configured. The IP endpoint uses this as its location number. See the Location sections in Avaya Aura® Communication Manager Feature Description and Implementation, for the other ways to assign a location, and for a list of features that use location. |
blank |
Obtains the location from the gateway where the endpoint is registered. By default, the value is blank. |
A description of the region. Accepts up to 20 characters.
The number of the network region being administered.
Using this field, you can create a core network region or a stub network region.
Valid entry |
Usage |
|---|---|
y |
Creates a stub network region. In the dst rgn field, you must enter the number of the destination network region that directly connects with this stub network region.
Note:
If you are converting a core network region to a stub network region, you must ensure that the core network region is directly connected with only one core network region. A stub network must have only one direct connection with a core network region. |
n |
Creates a core network region. For network regions 1 to 250, the default value of this field is n. For network regions 251 to 2000, this field is noneditable and displays a default of y. |
Valid Entry |
Usage |
|---|---|
1 to 7 |
The number for the codec set for the region. |
Allows direct audio connections between IP endpoints within a network region.
Valid Entry |
Usage |
|---|---|
y |
Saves on bandwidth resources and improves sound quality of voice over IP transmissions. |
n |
Might be used if, for example, the IP telephones within the region are behind two or more firewalls. |
native(NAT) |
The IP address from which audio is to be received for direct IP-to-IP connections within the region is that of the telephone/ softphone itself (without being translated by NAT). IP telephones must be configured behind a NAT device before this entry is enabled. |
translated(NAT) |
The IP address from which audio is to be received for direct IP-to-IP connections within the region is to be the one with which a NAT device replaces the native address. IP telephones must be configured behind a NAT device before this entry is enabled. |
Allows direct audio connections between IP endpoints in different regions
Valid Entry |
Usage |
|---|---|
y |
Saves on bandwidth resources and improves sound quality of voice over IP transmissions. |
n |
Might be used if, for example, the IP telephones within the region are behind two or more firewalls. |
native(NAT) |
The IP address from which audio is to be received for direct IP-to-IP connections between regions is that of the telephone itself (without being translated by NAT). IP telephones must be configured behind a NAT device before this entry is enabled. |
translated(NAT) |
The IP address from which audio is to be received for direct IP-to-IP connections between regions is to be the one with which a NAT device replaces the native address. IP telephones must be configured behind a NAT device before this entry is enabled. |
Valid Entry |
Usage |
|---|---|
1024 to 65534 |
The minimum range of the UDP port number used for audio transport. Defaults to 2048 to 3028. |
Valid Entry |
Usage |
|---|---|
1025 to 65535 |
The maximum range of the UDP port number used for audio transport. Defaults to 2048 to 3028. |
Provides scalable service discrimination in the Internet without per-flow state and signaling at every hop.
Valid Entry |
Usage |
|---|---|
0 to 63 |
The decimal equivalent of the DiffServ Audio PHB value. Default is 46. |
Provides scalable service discrimination in the Internet without per-flow state and signaling at every hop.
Valid Entry |
Usage |
|---|---|
0 to 63 |
The decimal equivalent of the Call Control PHB value. Default is 34. |
Valid Entry |
Usage |
|---|---|
0 to 63 |
The decimal equivalent of the DiffServ Video PHB value. Default is 26. |
Valid Entry |
Usage |
|---|---|
0 to 7 |
Provides Layer 2 priority for Layer 2 switches. Changes take effect after telephone reboot, or system reset. |
Valid Entry |
Usage |
|---|---|
0 to 7 |
Provides Layer 2 priority for Layer 2 switches. Changes take effect after telephone reboot, or system reset. |
Valid Entry |
Usage |
|---|---|
0 to 7 |
The Video 802.1p priority value. Changes take effect after telephone reboot, or system reset. |
Enables or disables retries when RSVP fails.
Available only if RSVP is enabled.
Enables or disables RSVP.
Available only if RSVP is enabled.
Set this field to what you have configured on your network.
Valid Entry |
Usage |
|---|---|
guaranteed-service |
Limits end-to-end queuing delay from sender to receiver. This setting is best for VoIP applications. |
controlled-load |
This subset of guaranteed-service provides for a traffic specifier, but not end-to-end queuing delay. |
Available only if RSVP is enabled.
The system displays this field only if the RSVP Enabled field is set to y.
Valid Entry |
Usage |
|---|---|
1 to 99 |
The RSVP refresh rate in seconds. |
Valid Entry |
Usage |
|---|---|
0 to 63 |
The BBE codepoint is used whenever an RSVP reservation is being obtained (pending), or has failed in some way, to provide efficient service to the voice stream. |
Enables or disables the H.323 Link Bounce Recovery feature for this network region. The default is enabled.
Valid Entry |
Usage |
|---|---|
5 to 7200 |
The maximum traffic idle time in seconds after which a TCP Keep-Alive (KA) signal is sent from the endpoint. Default is 20. |
Valid Entry |
Usage |
|---|---|
1 to 120 |
Sets the interval between TCP Keep-Alive re-transmissions. When no ACK is received for all retry attempts, the local TCP stack ends the TCP session and the associated socket is closed. Default is 5. |
Valid Entry |
Usage |
|---|---|
1 to 20 |
Sets the number of times the Keep-Alive message is transmitted if no ACK is received from the peer. Default is 5. |
To control the call processing behavior to send Alternative Network Address Types (ANAT) offer for the IP network region.
Use this field to control the call processing behavior of the Alternative Network Address Types (ANAT) for the IP network region.
Valid entry |
Usage |
|---|---|
y |
Communication Manager sends ANAT offer to SIP elements in the IP network region when you set this field to y as well as system-wide ANAT Enabled field to y. |
n |
Communication Manager does sends ANAT offer to SIP elements in the IP network region. |
If enabled, sends RTCP Reports to a special server, such as for the VMON tool.
Regardless of how this field is administered, RTCP packets are always sent peer-to-peer.
Available only if RTCP Reporting is enabled and if Default Server Parameters are disabled.
Valid Entry |
Usage |
|---|---|
1 to 65535 |
The port for the RTCP Monitor server. Default is 5005. |
Available only if RTCP Reporting is enabled and if Default Server Parameters are disabled.
Valid Entry |
Usage |
|---|---|
1 to 65535 |
The port for the RTCP Monitor server. Default is 5005. |
Available only if RTCP Reporting is enabled and if Default Server Parameters are disabled.
Valid Entry |
Usage |
|---|---|
5 to 30 |
The report period for the RTCP Monitor server in seconds. |
The IPv4 address for the RTCP Monitor server.
Available only if RTCP Reporting is enabled and if Default Server Parameters are disabled.
The IPv6 address for the RTCP Monitor server.
Available only if RTCP Reporting is enabled and if Default Server Parameters are disabled.
If enabled, uses the system-wide default RTCP Monitor server parameters. Available only if RTCP Reporting is enabled.
This page covers the information for Inter-Gatewày Alternate Routing (IGAR), backup server names in priority order, and security procedures.
If Inter-Gateway Alternate Routing (IGAR) is enabled for any row on subsequent pages, the following fields for each network region must be administered to route the bearer portion of an IGAR call.
Valid Entry |
Usage |
|---|---|
0 to 7 |
The digits to delete |
Valid Entry |
Usage |
|---|---|
0 to 16 blank |
The number of digits to insert. International numbers should begin with plus (+). The Inter-Gateway Alternate Routing (IGAR) and Dial Plan Transparency (DPT) features convert the plus (+) digit to appropriate international access code when starting the trunk call.
Note:
The optional plus (+) at the beginning of the inserted digits is an international convention indicating that the local international access code must be dialed before the number. |
Valid Entry |
Usage |
|---|---|
y |
Enables the Dial Plan Transparency feature when a gateway registers with a Survivable Remote Server (Local survivable processor). |
n |
Default is n. |
An extension used to assign an unused Listed Directory Number for incoming IGAR calls.
It is necessary to impose a limit on the trunk usage in a particular port network in a network region when Inter-Gateway Alternate Routing (IGAR) is active. The limit is required because if there is a major IP WAN network failure, it is possible to use all trunks in the network region(s) for IGAR calls.
Valid Entry |
Usage |
|---|---|
1 to 999, or blank |
The maximum number of trunks to be used for Inter-gateway alternate routing (IGAR). |
Lists the backup server names in priority order. Backup server names should include Survivable Remote Server names and Survivable Core Server names. If you are using the Processor Ethernet, the backup servers list must include the survivable core PE address else the phones will not register to the survivable core during a failure. Any valid node name is a valid entry. Valid node names can include names of Customer LANs, ICCs, Survivable Core Servers, and Survivable Remote Servers.
Permitted security profiles for endpoint registration in the network region. You must enter at least one security profile. Otherwise, no endpoint will be permitted to register from the region.
Valid Entry |
Usage |
|---|---|
challenge |
Includes the various methods of PIN-based challenge and response schemes in current use. This is a relatively weak security profile. |
pin-eke |
The H.235 Annex H SP1. |
strong |
Permits the use of any strong security profile. The H323TLS profile is the strongest security profile in Communication Manager. |
any-auth |
Includes any of the security profiles. |
H323TLS |
Communication Manager apples this security profile when the network region of an H.323 phone is administered with H323TLS or Strong security profiles. Also, Communication Manager and the endpoint negotiate by using the H323 TLS profile. H323TLS profile sends H.323 signaling messages through a TLS-encrypted channel. |
Administers whether or not a SIP URI should be permitted to change. Degrading the URI from sips//: to sip//: might result in a less secure call. This is required when SIP SRTP endpoints are allowed to make and receive calls from endpoints that do not support SRTP.
Valid Entry |
Usage |
|---|---|
y |
Allows conversion of SIP URIs. Default is y. |
n |
No URI conversion. Calls from SIP endpoints that support SRTP made to other SIP endpoints that do not support SRTP will fail. However, if you enter y for the Enforce SIPS URI for SRTP field on the signaling group screen, URI conversion takes place independent of the value set for the Allow SIP URI conversion field on the IP Network Region screen. |
Indicates whether Communication Manager (the near end) can establish the TCP socket for H.323 IP endpoints in this network region.
Valid Entry |
Usage |
|---|---|
y |
Communication Manager determines when to establish the TCP socket with the IP endpoints, assuming the endpoints support this capability. This is the default. |
n |
The IP endpoints always attempt to set up the TCP socket immediately after registration. This field should be disabled only in network regions where a non-standard H.323 proxy device or a non-supported network address translation (NAT) device would prevent the server from establishing TCP sockets with H.323 IP endpoints. |
Valid Entry |
Usage |
|---|---|
1024 to 65531 |
The minimum port value used by the processor Ethernet when establishing the TCP signaling socket to the H.323 IP endpoint. The range of port number must be at least 5 (Max-Min+1). Default is 61440. |
Valid Entry |
Usage |
|---|---|
1028 to 65535 |
The maximum port value to be used by the processor Ethernet when establishing the TCP signaling socket to the H.323 IP endpoint. The range of port number must be at least 5 (Max-Min+1). Default is 61444. |
Each subsequent page shows the inter-region connectivity for 15 region pairs.
The maximum number of destination region IP interfaces included in alternate gatekeeper lists (AGL).
Valid Entry |
Usage |
|---|---|
0 to 16 |
Communication Manager uses the numeric value of gatekeeper addresses. |
all |
Communication Manager includes all possible gatekeeper addresses in the endpoint's own network region and in any regions to which the endpoint's region is directly connected. |
blank |
The administration field is ignored. |
Valid Entry |
Usage |
|---|---|
1 to 7 pstn blank |
The codec set used between the two regions. This field cannot be blank if this route through two regions is being used by some non-adjacent pair of regions. If the two regions are disconnected at all, this field should be blank. |
Indicates whether the two regions (source and destination) are directly connected by a WAN link. The default value is enabled if a codec-set is administered.
Valid Entry |
Usage |
|---|---|
1 to 250 |
The destination region for this inter-network connection. |
Use this field to configure a gateway for Call Admission Control (CAC). The system displays this field only if the WAN-BW-limits (Units) field is set to Dynamic.
Valid Entry |
Usage |
|---|---|
1 to 250 blank |
The gateway that reports the bandwidth-limit for this link. Default is blank. |
If you set the BW Management Option field to shared-SM, you cannot view this field.
Allows pair-wise configuration of Inter-Gateway Alternate Routing (IGAR) between network regions.
Valid Entry |
Usage |
|---|---|
y |
Enables IGAR capability between this network region pair. Default for a pstn codec set. |
n |
Disable IGAR capability between this network region pair. Default, except for a pstn codec set. |
f |
Forced. Moves all traffic onto the PSTN. This option can be used during initial installation to verify the alternative PSTN facility selected for a network region pair. This option can also be used to temporarily move traffic off of the IP WAN if an edge router is having problems or an edge router needs to be replaced between a network region pair. |
Allows entry of intervening region numbers between the two indirectly-connected regions.
Valid Entry |
Usage |
|---|---|
1 to 250 |
Up to four intervening region numbers between the two indirectly-connected regions.
Note:
Indirect region paths cannot be entered until all direct region paths have been entered. In addition, the order of the path through the regions must be specified starting from the source region to the destination region. |
Valid Entry |
Usage |
|---|---|
t |
This is a test-only option. Inter-region connectivity testing is performed for the network region pair by using a simple PING sent between entities in each network region. If a test fails, only an error is added to the system error log. IP media connections between the region pair are never blocked. The testing is done at the rate of not more than once per 5 minutes. |
m |
This is a measurement based option. Inter-region connectivity testing is performed by a continuous set of PINGs sent between entities in each network region. The Ping Test Interval (sec) and Number of Pings Per Measurement Interval fields control the rate of testing. The Roundtrip Propagation Delay (ms) and Packet Loss (%) thresholds control success or failure. If the, test measurements exceed the administered thresholds; future IP media connections between the network region pair will be blocked. |
d |
No testing is performed for the network region pair. |
Valid Entry |
Usage |
|---|---|
1 to 250 |
The source region for this inter-network connection. |
The system displays Sync when the Synchronization over IP field is enabled.
Valid Entry |
Usage |
|---|---|
y |
Timing IGC streams are allowed between the region pair that is being administered. The default value is y. |
n |
Do not allow timing IGC streams between the region pair that is being administered. |
Use this field to specify the amount of bandwidth to allocate for the normal video pool to each IP network region. You can enter:
0 to 9999 for Kbits.
0 to 65 for Mbits.
blank for NoLimit.
If you set the BW Management Option field to shared-SM, you cannot view this field.
Use this field to specify the amount of bandwidth to allocate for the priority video pool to each IP network region. You can enter:
0 to 9999 for Kbits.
0 to 65 for Mbits.
blank for NoLimit.
If you set the BW Management Option field to shared-SM, you cannot view this field.
Use this field to specify whether the normal video pool can be shared for each link between IP network regions.
If you set the BW Management Option field to shared-SM, you cannot view this field.
Use this field to specify the bandwidth limit for direct WAN links. You can enter:
0 to 9999 for Kbits
0 to 65 for Mbits
blank for NoLimit
If you set the BW Management Option field to shared-SM, you cannot view this field.
Use this field to specify the unit of measurement corresponding to the value entered for bandwidth limitation.
Calls
Dynamic
Kbits
Mbits
NoLimit
If you set the BW Management Option field to shared-SM, you cannot view this field.