[cisco-voip] CUBE - Dial-peer multiple destination-pattern matching
Pawlowski, Adam
ajp26 at buffalo.edu
Mon Oct 26 13:31:22 EDT 2015
I have used the DNIS map, just as it was basically "static SAF" in a way without screwing around with extra unneeded settings. SAF is quickly obnoxious to use in a case like this where you're not advertising a pattern, but instead a large number of individual DIDs. The flat file is easy to maintain, but needs to be loaded again when you change it, so if you're transitioning phones between clusters it is not completely transparent.
With things arranged in the UCM so that it's matching against DNs and not generic patterns, "intercepts", etc, you could just put it at both with two peers and have it 404 out and fall to the second one. It will generate a bunch of noise in your call records if you're using PCA or some sort of thing but it works.
Someone here had also suggested arranging routes in a fall through manner between the clusters, which works as well with a similar effort - DNs match immediate, less specific pattern for the exchange or extension range falls to other UCM. You could then point a generic dial peer at each cluster without preference for round-robin and let it just go wherever it goes - this is obviously not necessarily ideal depending on your network topology.
Lots of ways to do it that work, but it is worth thinking about how you want to go about it so that you can expand/change later without overhauling everything.
Adam Pawlowski
SUNY Buffalo
More information about the cisco-voip
mailing list