That is really up to you, I normally recommend to have one partition for each site, or for each department and then create the CSS for each site/department and assign the partition of the phones that you wish to reach.
This is the basics of CCM, you need to understand exactly how this works otherwise you will have a lot of problems in the future.
ok, but what if I leave them in the None Partition (in other words no need to create DN's partitions per site/Dept/...) so all phones are able to reach each others internally and this is what I need in my deployment, in such case, is it a best practice to leave all phone's DNs in None Partition?
My preference is to put all internal DNs across all sites in a partition called "internal" or something similar. There are, of course, reasons for using different partitions for internal numbers such as hiding caller ID info among others, but if you do not have these requirements, it simplifies things to have them all in the same partition. It is acceptable to leave these in the partition, but this leaves things to chance in my opinion.
again, if I leave them in the None Partition so all phones are able to reach each others internally and this is basically what I need in my deployment, in such case, is it a best practice to leave all phone's DNs in None Partition?
what do u mean Brandon by (this leaves things to chance)?
and what are other reasons for using different partitions for internal numbers
By leaving things to chance, I mean that you are not configuring the system to work this way. It simply happens to work. I understand that this accomplishes your current goal of all phones being capable of calling all other phones internally. I would still recommend using a defined partition as your requirements may change in the future. Using a definined partition now cannot do harm in the future. Using the None partition now could require reconfiguring DNs in the future.
Putting DNs in seperate partitions gives you the control you will need to deploy security across your IP telephony deployment. This includes on-net as well as off-net access. It is very difficult to block access to a DN that is in the partition. For example, if you don't want people forwarding their line to the building access FXS port, you have to make sure that is in a seperate partition.
Somethings to consider:
- What dialplan strategy are you going to use? I'm not familiar with 5.x yet, but in 4.x you had the concept of the device and line calling search space.
- In 4.x calling search spaces had a max of 512+512 characters. Make sure you use short names where possible.
- Plan for expansion, even if no expansion is on the horizon.
- Don't over-partition when you don't need to.
- Be prepared to redesign your dial plan at least once. ;)
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...