Sounds like an interesting project you have there. Before considering SRST I would explore other avenues such as clustering over the WAN or deploying a dedicated cluster for this site - there are some features either roadmapped by Cisco or available through third parties that may make this possible.
If SRST is your only option then I would recommend deploying extensions in as larger blocks as possible to reduce the number of dial peers on the system.
The ideal would be five blocks of 1000 extensions so each SRST router could reach all other extensions on the site using just four VOIP dial peers. This would be straightforward in a green field site but would be difficult in an established site (PABX replacement).
This number of dial peers is pretty straightforward to configure and the SRST routers can be fully meshed. Any more and it can become really complex.
You also need to think about how hunt groups etc. will be handled whilst SRST is active. Each SRST router can have up to 50 alias commands but you can get through that number really quickly if you have lots of hunt group users.
I will be really interested to see what path you follow with this.
I agree with James. A deployment this size it is best to go down the route of Clustering over the WAN. Of course you will need to ensure 80ms RT between the servers. On a side not by adding multiple gateways to get your user base covered, you would have already bought a 7835 server.
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 ...