Avaya Administering Aura Session Manager Release 6.1 Instrukcja Użytkownika Pobierz pdf (Strona 251)

Provisioning Session Manager and Communication Manager CAC together

For simultaneous use of Session Manager and Communication Manager CAC, following

configurations should be done:

1. Create 1-to-1 mapping of Session Manager Locations to Communication Manager

Network Regions, because Communication Manager uses Network Regions for

CAC. This is limited by the fact that Communication Manager supports no more

than 250 Network Regions, while Session Manager supports thousands of

Locations.

2. As Session Manager maps IP addresses to Locations, Communication Manager

maps IP addresses to Network Regions. These mappings must be synchronized

manually.

3. As part of Communication Manager administration, the SIP trunk to Communication

Manager must be placed within a dummy Network Region for which no CAC limits

are set.

This enables the following changes:

• Calls terminated to non-SIP destinations (H.323 phones, non-SIP trunks) are counted by

Communication Manager CAC for the appropriate Network Regions.

• All calls terminated to SIP destinations (SIP phones, SIP trunks on Session Manager) are

counted by Session Manager CAC for the appropriate Locations.

• SIP trunks on Communication Manager that do not route to Session Manager (not a

recommended configuration) are counted by Communication Manager.

Note:

Communication Manager performs CAC in terms of bandwidth limits between two specific

Network Regions, while Session Manager performs CAC as per limits covering all traffic into

or out of a Location, regardless of the far-end location.

Recommended modifications for the earlier versions of Session Manager

1. For CAC in Session Manager 6.0 used for counting calls

CAC may have been provisioned in Session Manager 6.0 by setting the "Average Bandwidth

per Call" limit to 1 kbps which provides a simple call count limit of X simultaneous calls in the

location. In such case, clearing Ignore SDP for Call Admission Control option (“Use SDP”

CAC mode) drastically reduces the number of calls allowed in the location since the common

codec G.711-Mu uses 83 kbps which limits the number of calls allowed to change from X to

X/83.

For Session Manager 6.1, CAC does not enforce a limit on the number of calls per location

but applies a limit on the bandwidth usage. The limits for each location should be multiplied by

the determined average bandwidth per call Y (in kbps). If there are no multimedia users in the

Locations

Administering Avaya Aura

Session Manager November 2010 251

1 2 ... 246 247 248 249 250 251 252 253 254 255 256 ... 531 532

Brak uwag

Avaya Administering Aura Session Manager Release 6.1 Instrukcja Użytkownika Strona 251