If this is not a risk you are willing to tolerate, you
must use one of the third-party gateways listed on the Microsoft Web site. If that is the
route you choose, you will need to provision a PRI port or FXO port on your Cisco
voice gateway and connect it to the AudioCodes, Dialogic, or Quintum gateway. Although
this is a somewhat more expensive and convoluted scenario, it is supported by both Cisco
and Microsoft.
Understanding Partitions and Calling Search Spaces
You will fi nd entire books dedicated to creating and implementing dial plans in Cisco
CallManager. I won??™t attempt to squeeze hundreds of pages of knowledge into a single subsection,
but it is important to understand the basics of how CallManager routes calls. Partitions and
calling search spaces make up the two basic components of a dial plan in CallManager.
When you create a phone number in CallManager, you need to assign it to a partition.
In a sense, partitions are almost like phone books??”containers that have phone numbers listed
in them. So, for example, you could create phone numbers 1000??“2000 and put them in a
partition called Chicago Extensions. Then you could create phone numbers 3000??“4000 and
put them in a partition called Springfi eld Extensions. Partitions are a logical way to organize
phone numbers.
If one of my users wanted to be able to call anyone in Chicago, I would assign him rights,
or a calling search space that included the Chicago Extensions partition. If that were the only
partition in his calling search space, he would only be able to dial numbers 1000??“2000.
Pages:
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313