1 / 10

Preparing CallManager for Device Registration

Preparing CallManager for Device Registration. Credits. The material provided in this presentation has been referenced from the following textbook: Configuring CallManager and Unity: A Step-by-Step Guide by David Bateman. Preparing CallManager for Deployment. Creating CallManger Groups

hilda-brooks
Download Presentation

Preparing CallManager for Device Registration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Preparing CallManager for Device Registration

  2. Credits • The material provided in this presentation has been referenced from the following textbook: Configuring CallManager and Unity: A Step-by-Step Guide by David Bateman

  3. Preparing CallManager for Deployment • Creating CallManger Groups • Defining Date and Time Groups • Configuring Regions • Building Device Pools

  4. Creating CallManger Groups • A CallManager group defines which CallMangers a given device points to as its primary, Secondary, and tertiary CallManger. • The order in which CMs appear determine their function • A CM may be in more than one group and its function might be different in each group • CallManger groups are created to achieve the goals of redundancy and load balancing

  5. Defining Date and Time Groups • Just as we need to be aware of time zones in our daily lives, we need to make sure that CallManger knows the time zone of its registered device. This is accomplished by configuring a date/time group for each time zone that devices will be in. • The default date/time group, called CMLocal, is created when CM is installed, and it is set to the zone selected during the installation

  6. Configuring Regions • When calls traverse lower bandwidth IP links, such as a WAN link between offices, it may be necessary to compress the audio stream so that the link is used efficiently, the compression is accomplished by using a codec that has a lower bandwidth requirement, such as G.729, for the call. • When using a Codec that requires lower bandwidth, the quality of the call is affected. For this reason, it is recommended that these codecs are used only when bandwidth is at premium. • The Codecs used should depend on the destination, rather than what device is using he call. Regions allow for this. • The two most often used codecs in a Cisco VoIP environment are G.711 and G.729. G.711 require approximately 80 kps when overhead is included . G.729 requires only 24 kps including overhead. • By creating and assigning regions, you define which codec is used between regions.

  7. Building Device Pools • Now that the Device Pool’s required components have been configured, you can create the device pools. The first thing you have to determine is how many device pools are needed. This is determined by looking at the number of device pool components you have created and how they tie together.

  8. Two CallManagers CMA CMB Two CallManager Groups: CMAB CMBA Regions: Detroit Chicago Date/Time Groups Eastern Central Right away you can tell that because you have three regions, there will have to be at least two device pools. However, because we want half the phones in each region to use CallManger group CMAB and the other half to use CMBA then we would need 4 Device Pools Example

  9. Example-Continued

  10. Labs • Manual Device Registration Lab • Device Registration Using Bulk Administration Tool (BAT)

More Related