Provisioning Session Manager and Communication Manager CAC together

Last Updated : May 03, 2013 |

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 for small and medium platforms and 2000 Network Regions for large platforms, 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 from 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.