Network Regions For Avaya MultiVantageSolutionsA Tutorial

ABSTRACT
This paper defines the concept and demonstrates practical applications of Network Regions in a data network carrying voice packets with Avaya MultiVantage powered servers. The varying characteristics of IP Endpoints can require the assignment of different settings to optimize the delivery of the expected voice quality for those endpoints. This paper describes the process of assigning IP endpoints to Network Regions in order to assign the appropriate VoIP resources according to the varying characteristics of the endpoints and the network.

Application Notes
August 2002

AMR LPH 08/19/02

2002 Avaya Inc. All Rights Reserved.

Network Regions for Avaya 1 MultiVantage Solutions

Network Regions For Avaya Multivantage SolutionsA Tutorial

Table of Contents
1. 2. Network Regions Defined.....................................................................................3 How to Assign Endpoints to Network Regions....................................................4 2.1. 2.2. 2.3. 3. 4. IP Stations ...................................................................................................4 Trunks .........................................................................................................5 Avaya G700 Media Gateways: ..................................................................6

When To Use Network Regions ...........................................................................7 Network Region Connectivity ............................................................................12 4.1. Allow shuffling between endpoints in different regions:........................13

4.2. Allow inter-region calls in a pure IP environment such as S8300/S8700........................................................................................................14 4.3. Force the use of a different codec set for inter-region calls than the one used for intra-region calls....................................................................................15 4.4. 4.5. 5. Media processor overflow strategy ..........................................................16 Provide alternate C-LANs from other regions ........................................16

Conclusion ...........................................................................................................17

AMR LPH 08/19/02

2002 Avaya Inc. All Rights Reserved.

Network Regions for Avaya MultiVantage Solutions

1.

Network Regions Defined

For Avaya Multivantage Solutions a network region is a way to group IP endpoints that share the same characteristics and the same VoIP and Signaling resources such as Media Processor boards and C-LANs. IP endpoint refers to IP stations, IP trunks and Avaya G700 Media Gateways. The characteristics that can be defined for these IP endpoints are: Audio Parameters Codec Set UDP port Range Enabling Direct IP-IP connections Enabling Hairpinning

Quality of Service Parameters: Diffserv settings 802.1p/Q settings RTCP settings RSVP settings

Other Parameters: Location

AMR LPH 08/19/02

2002 Avaya Inc. All Rights Reserved.

Network Regions for Avaya MultiVantage Solutions

2.

How to Assign Endpoints to Network Regions

Types of endpoints: IP stations IP trunks Avaya G700 Media Gateways

2.1. IP Stations An IP station will acquire its network region identity in two different ways. Using the ip-network-map form you can define the region of the endpoint by including its IP address in the range administered in this map. Note that this ip-network-map is available in Avaya MultiVantage Software.

Figure 1

The second way is by letting the endpoint inherit the network region of the C-LAN that it registers to. So for the softphone it will get the region of the C-LAN that is used in the login softphone settings. The IP telephone will get the network region for the C-LAN that it obtains from the DHCP server. This is how it works for systems prior to those powered by MultiVantage Software but is also an option that applies to MULTIVANTAGE solutions. The ip-network-form is not used in this case. The region of the C-LAN is administered in the ip-interfaces form.

AMR LPH 08/19/02

2002 Avaya Inc. All Rights Reserved.

Network Regions for Avaya MultiVantage Solutions

Figure 2

In the case above all the C-LANs are in region 6, so if an endpoint registers with any of these C-LANs and it does not have a region of its own it will be treated as belonging to region 6. Administering regions for the endpoints in the ip-network-map offers more control of what the endpoints will do independently of the C-LAN with which they register. 2.2. Trunks A trunk acquires a network region at the time of administration of its signaling group. In the signaling-group form they inherit the network region from the nearend node C-LAN administered in the signaling group form. Note that there is also a field where a far-end node network region can be defined. The system treats the far end of the trunk as if it were an endpoint in the region specified in this field. Therefore, calls across this trunk use the inter-region CODEC set specified for calls between these regions. If this far-end region is not defined, the system views both the near end and the far end as being in the same region. If the network at the far end cannot handle the characteristics of the near-end region then there could be a problem completing calls between the two sites. It would be wiser in this case to use a separate network region for the far-end. If both sides are compatible, the field can be left blank.

AMR LPH 08/19/02

2002 Avaya Inc. All Rights Reserved.

Network Regions for Avaya MultiVantage Solutions

Figure 3

The best way to look at this is to think of the trunks as two endpoints: one being the near-end and the other being the far-end. Each endpoint will belong to the same region or different regions depending upon the near-end C-LANs network region and the far-end network region. If the trunk traverses across networks with different characteristics it is useful to set the two sides of the trunk in separate regions. Otherwise the far-end region can be left blank. 2.3. Avaya G700 Media Gateways: Avaya G700 Media gateways will get their region defined in the media-gateway form - as simple as filling in the required field.

Figure 4

AMR LPH 08/19/02

2002 Avaya Inc. All Rights Reserved.

Network Regions for Avaya MultiVantage Solutions

3.

When To Use Network Regions

When there are separate groups of endpoints in a system or customer configuration that require that the characteristics listed in section 1 be different for each one of the groups then it make sense to separate these endpoints by Network Regions. For example: A customer configuration requires IP users in the main location in Denver. In this location every IP user is on 100MB LAN and all the subnets connect via a gigabit Ethernet backbone. This customer has also several employees who telecommute from home. They all use IP softphones to access the Multivantage server. They connect to the main location using cable modem/DSL connections.

Figure 5

So in this example there are two groups of IP endpoint users. Those in the main location in Denver, which do not have any bandwidth limitations, can use the codec with the best audio quality and highest bandwidth utilization G.711. The second group of endpoints is comprised of the remote softphone users. They use Avaya IP Softphone in Roadwarrior mode (full VoIP) and require a lower bandwidth connection. So they need to use Codec G.729. What this means is that to guarantee that these remote endpoints use the lower bandwidth connection and the main location users capitalize on the higher bandwidth connection, then these two groups of IP endpoints need to be separated into two network regions. Network regions are identified with numbers from 1 to 250 and they are created using the change ip-network-region <#> command.

AMR LPH 08/19/02

2002 Avaya Inc. All Rights Reserved.

Network Regions for Avaya MultiVantage Solutions

All of the characteristics that can be specified for a network region are listed in page 1 of the ip-network-region form.

Figure 6

Another reason why network regions are used to separate endpoints and VoIP resources is to give endpoints certain preference to use resources that belong to the same region as the endpoint. It is important to say that it is only a preference, not a mandatory rule. There are certain cases where it is preferential to allow endpoints to use VoIP resources from other regions, which will be explained later in section 4.2. Another level of complexity is added if another Avaya Multivantage System in New Jersey is added to the configuration. This system is connected to the Denver location via H.323 IP trunks. In a configuration like this the number of Media processor boards would be engineered based on the call traffic expected between the two locations. A common option would be to allocate a separate group of Media processor boards to serve the IP trunks separate from those serving the IP stations. In this case we have a situation where the Media processor boards for IP stations need to be located in the same region as the IP stations. The Media Processor boards for trunks need to be located in a different region for where the signaling groups for the trunks are located. This way the IP stations will have a preference to use their Media Processor resources and avoid using the ones allocated for the IP trunks and vice versa.

AMR LPH 08/19/02

2002 Avaya Inc. All Rights Reserved.

Network Regions for Avaya MultiVantage Solutions

Figure 7

In cases like this, where a good amount of call volume is expected between locations (Denver and New Jersey), but only a limited amount of bandwidth over the WAN is available, concerns that voice quality will degrade during peak hours will arise. A practical solution is to use codec G.729 for IP voice calls over the IP trunks and use Diffserv QoS mechanisms. To accomplish a design in this manner for the trunk network region, diffserv values and a codec set that contains G.729 as a first option must be used. A third reason to use network regions is to associate endpoints with another type of signaling resources (C-LANs). This would be done to load balance the registration of endpoints in a given network region across a specific group of C-LANs. Every time an endpoint registers with the system, Multivantage Software will direct the endpoint to the next C-LAN in the same region as the endpoint. It distributes the registrations among the C-LANs in the region in a cyclical fashion. This is to try to spread the registration load among several C-LANs in the region. So regions can be used to force groups of endpoints to register with a certain group of C-LANs according to any of the different reasons for grouping endpoints and resources together: Based on geographical location, subnets, media gateways or what ever makes most sense for the specific situation.

AMR LPH 08/19/02

2002 Avaya Inc. All Rights Reserved.

Network Regions for Avaya MultiVantage Solutions

Figure 8

For example, in this scenario there are two AvayaG600-Ip Connect Media Gateways in an Avaya S8700 ip-connect configuration. Each gateway is at a different geographical location. Each one of them will serve ip endpoints with their own media processors and C-LANs. It is desirable that endpoints have a preference to use the local resources instead of resources from the other location. To satisfy the alignment with local resources regions 1 and 2 are created. In this case endpoints in region 1 are programmed to register with a C-LAN in region 1 so that they spread among all active C-LANs in that region. Similarly endpoints in region 2 are programmed to register with a C-LAN in region 2 will be spread among C-LANs in that same region (2). There can be situations where endpoints are programmed to register with a C-LAN that belongs to a different region than the endpoint. In that case the algorithm for load spreading will still attempt to spread the registration among C-LANs in the region of the endpoint. However, when the endpoints are in a region where there are no C-LANs, these endpoints can still be programmed to register to C-LANs in other regions without problem. In this case the load spreading will occur among all C-LANs in the same region as the C-LAN to which the endpoint attempted to register. This situation is permitted and in some cases still makes sense given the low bandwidth requirements between the endpoint and the C-LAN. An example of this would be a scenario where there are plenty of C-LANS resources in gateway 1 and given the low number of endpoints hanging off gateway 1, the customer decides not to include C-LANs in gateway 2. So IP endpoints in region 2 will have no choice but to register with a C-LAN on region 1 and their load will be spread this time among C-LANs also in region 1.

AMR LPH 08/19/02

2002 Avaya Inc. All Rights Reserved.

Network Regions for Avaya MultiVantage Solutions

10

Another scenario could be to program the IP phones in region 1 to register with a C-LAN in region 1 and as a backup a second C-LAN in the list that comes from DHCP is assigned to region 2. So the IP phone will always have a preference to register with the first C-LAN in the list. Now, in the case where the primary CLAN is down for some reason and the phone fails to get a response from that CLAN, the phone could try sending the registrations to the back-up C-LAN in region 2. The load-spreading algorithm would assign that registration in a round-robin fashion among C-LANs in region 1 if there were other C-LANs active there. If no others were available, then the round-robin distribution would occur among CLANs in region 2. Those endpoints that registered with C-LANs in region 2 during the outage will remain registered there with those C-LANs until the next time they re-register. This could pose an interesting situation where depending on the nature and frequency of the outages the system may end-up with a whole set of endpoints registered with the backup C-LANs in region 2 instead of their primary C-LANs in region 1. The only way for endpoints to go back to the primary C-LANs in their original region is for them to unregister and re-register again.

AMR LPH 08/19/02

2002 Avaya Inc. All Rights Reserved.

Network Regions for Avaya MultiVantage Solutions

11

4.

Network Region Connectivity

Apparent in the second page of the ip-network-region form is a matrix named Inter-Network Region Connection Management. This matrix defines interconnectivity between the region that is being administered and any of the other 79 to 249 regions, depending on the platform.

Figure 9

The way this matrix works is as follows: The left column, the Region column, defines a range of regions that can be interconnected to the region being administered. There is a range of network regions for each row of the matrix. For example, the first range in the region column shows a range 1 - 32. This means that along that row one can find the position in the matrix corresponding to regions in that range. The sequence of numbers on top of the first row is there to help find the right position in the row. The first nine digits mark the positions from regions 1 to 9. The next ten digits show positions form 10 to 19 and so on until position 32. So in order to find region 27, the position below the third seven in the first row as shown in figure 9 needs to be selected. For the second row where the range goes from 33 to 64, the guide is still useful but not that easy to follow. The process is to subtract the number for the beginning of the range from the region in which a position is desired and then add one to it. So the position for region 56 is in the 33 to 64 range so 56-33+1 = 24. So the position is on the 2nd row below the third 4 in the guide. What is put in this position will indicate what codec set will be used in order to interconnect the two. So in the example above if the command ch ip-networkregion 1is entered and the position corresponding to region 27 is selected and a 4
AMR LPH 08/19/02 2002 Avaya Inc. All Rights Reserved. Network Regions for Avaya MultiVantage Solutions

12

is input, this means that regions 1 and 27 are interconnected and the codec set that will be used is 4. It is important to note that in many cases there is no need to administer any connectivity between regions. It is only necessary to administer this connectivity when there is going to be some sort of IP connection allowed directly between endpoints or resources in the different regions. Inter-region connectivity is necessary in the following cases. To allow Shuffling between endpoints in different regions To allow inter-region calls in a pure ip environment such as an Avaya S8700 ip-connect. To force the use of a different codec set for inter-region calls than the one used for intra-region calls For Media Processor overflow strategy To provide alternate C-LANs from other regions

4.1. Allow shuffling between endpoints in different regions: A scenario that allows shuffling between endpoints in different regions is illustrated in Figure 7. In the location in Denver where two regions are defined: Region 1 for the IP stations and Region 3 for IP trunks. For every region the necessary number of Media processors are allocated. So in the picture there is Telephone A and Media processor 1 in Region 1. The H.323 Signaling group and Media processor 2 are in region three. In the New Jersey location there is a similar configuration. So Telephone A is in Region 1 along with Media processor 1 and the signaling group for the H.323 trunk to Denver is in Region 3 along with Media processor 2. Note that the prime notation was used on purpose to show that Network region numbers can be repeated in the two locations but they are in reality separate regions, each one possibly having different characteristics defined in each one of the Multivantage servers. In this case, for shuffling to occur and an ip-direct call to be established between Endpoint A and Endpoint A, in the Denver Multivantage server, network region 1 and network region 3 need to be interconnected. Similarly in the NJ Multivantage server, Network region 1and Network Region 3 also need to be interconnected. Now assume that Region 1 in Denver uses codec set 1 for intra-region calls that contains only G.711. This is the codec set defined in the first page of the ipnetwork-region-form. This allows IP telephones to use G.711 when they call each other within region 1. The NJ is similarly administered.

AMR LPH 08/19/02

2002 Avaya Inc. All Rights Reserved.

Network Regions for Avaya MultiVantage Solutions

13

The trunks were specified codec set 3 in the first page of ip-network-region 3 and 3 that only contains g.729. This forces a compression codec to be used over the ip trunk where bandwidth needs to be conserved. In order for the call to shuffle, the network regions not only need to be interconnected as explained above, but it is also necessary to use the right codec set in the connectivity matrix. Since the bandwidth limitation exists on the trunk leg, the codec set specified in the second page of the ip-network form for the 1 to 3 position will be a codec set that contains g.729 only. Now when the call is made, IP phone A will use G.729 to interconnect to region 3, where the H.323 signaling group is, and similarly IP phone A will use G.729 to connect to region 3 where the H.323 signaling group is. Because each call is using G.729, the Multivantage servers will shuffle the call and allow the IP phones to communicate directly to each other without intervention of the media processor boards. 4.2. Allow inter-region calls in a pure IP environment such as S8300/S8700. Figure 10 illustrates the scenario in which inter-region calls in a pure IP environment such as S8300/S8700 are allowed:

Figure 10

In this case there are two media gateways registered and controlled by an external call controller (ECC). Media gateway 1 is in Region 1 and Media Gateway 2 in Region 2. Phone A is also put in region 1 and phone B is in region 2. In order for a call to complete between phones A and B there has to be some connectivity defined between region 1 and region 2. The inter-region codec set administered in the matrix will define what codec will be used for this call. In this case the codec used will be G.729 as determined by codec set 2.

AMR LPH 08/19/02

2002 Avaya Inc. All Rights Reserved.

Network Regions for Avaya MultiVantage Solutions

14

This rule applies to both shuffling and non-shuffling calls. In the non-shuffling scenario an endpoint is allowed to use resources from other regions. What happens in this call is that IP phone A will originate the call and use a VoIP resource from MG 1 to call IP phone B. The ECC will try to use resources in the most efficient way and IP phone B will also use a VoIP resource from the same MG 1. This utilization of VoIP resources eliminates unnecessary connection between the media gateways. If connectivity between Region 1 and Region 2 is not defined, the call will not complete! This is different in a legacy platform, where a similar situation could occur. In figure 11 traditional port networks take the place of the MG. Each port network has media processor resources. In this case connectivity between region 1 and 2 is not necessary to complete the call since port networks are connected via the TDM bus and the call can be completed using that route. Only in cases where it is desired to have the calls shuffle would it be necessary to set the connectivity between the two regions: thus allowing IP phones to connect directly to each other.

Figure 11

4.3. Force the use of a different codec set for inter-region calls than the one used for intra-region calls In the same example as the ECC configuration, the intra-region codec set defined in the fist page of the ip-network-region 1 contains only G.711. This means that all endpoints that call each other within the same region 1 will use G.711. However, when calls go across regions, the inter-region codec set defined in the matrix forces the endpoints to use G.729. Here it is demonstrated how network regions have a direct relationship with the IP network topology. Each region represents a separate LAN that connects to other LAN via a WAN link that has certain bandwidth limitations as it is shown in figure 10.

AMR LPH 08/19/02

2002 Avaya Inc. All Rights Reserved.

Network Regions for Avaya MultiVantage Solutions

15

4.4. Media processor overflow strategy To demonstrate an example of a Media Processor overflow strategy consider a traditional port network that has just one media processor board. This board is capable of handling 64 G.711 connections. This media processor is administered for network region 1, which does not allow shuffling. If region 1 has 200 IP phones administered, then the number of simultaneous G.711 calls that can be supported among these 200 endpoints is 32. If an additional simultaneous call were attempted, then there would not be enough resources in the same media processor board and the call would be denied. Now, if there were media processor boards in other network regions in the system, the 33rd call would be accepted and completed, only if the connectivity between the network regions was established. . There are many possible reasons for establishing the network regions in this scenario that would cause a call like this to be completed using the inter-region codec set. . It could be because the endpoints and resources in region 1 are separated from the resources in region 2 by a WAN. So in order for endpoints in region 1 to access a resource across the WAN it is necessary to make sure that a low bandwidth codec is used, and that is what is forced via the entries on the interconnectivity matrix. 4.5. Provide alternate C-LANs from other regions When IP endpoints lose connectivity to the C-LAN with which they register, they will try to re-register to other C-LANs in their alternate gatekeeper list. This list is partly composed by a list coming from the DHCP server, or for the softphone it can be programmed manually. The other part of the list will come from Multivantage Software when the phone registers. The Multivantage Software will send to the endpoint all the C-LANs in the network region of the endpoint and in the case where other regions are connected to the endpoints region, the list will include CLANs in those regions as well.

Figure 12

AMR LPH 08/19/02

2002 Avaya Inc. All Rights Reserved.

Network Regions for Avaya MultiVantage Solutions

16

So in the example shown in figure 12, there are two Avaya G600 Media Gateways in a S8700-ip connect configuration. Each gateway represents one region. So the endpoints in each location will register with C-LANs in their region and when they lose connectivity, they will try to re-register to other C-LANs in the same region. However, if the whole media gateway 1 went down and no C-LANs were available in that location anymore, then, since the two regions are interconnected, the endpoints in MG 1 will also have those C-LANs that are located in MG 2 in their alternate gatekeeper list. The phones, once they re-register, would continue to work off the other media gateway.

5.

Conclusion

IP endpoints can be easily assigned to Network Regions using the network management tools and matrixes in MultiVantage Software. Network Regions can be used to provide alternative VoIP resources in situations where CLAN resource shortages in a geographical area, short term gateway failures, or other non standard operational situations occur. The administration process for establishing network Regions are described in this document and could provide an enterprise with additional reliability and flexibility in their VoIP network.

2002 Avaya Inc. All Rights Reserved. All trademarks identified by the or TM are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners.

AMR LPH 08/19/02

2002 Avaya Inc. All Rights Reserved.

Network Regions for Avaya MultiVantage Solutions

17