Router 1
Routes
10.1.1.0/24
10.1.2.0/24
10.1.3.0/24
Can be summarized to
10.1.0.0/16
(...)
This statement is wrong.
You need to take in account all routes:
e.g.
10.1.1.0/24 via a
10.1.2.0/24 via a
10.1.3.0/24 via a
0.0.0.0/0 via b
Now if you summarize as you said:
10.1.0.0/16 via a
then 10.1.4.0/24, instead of going via b will go via a and this will be wrong because it is no equivalent behavior.
Since the router can not guess what you expect to happen, such summary will not happen (and should not happen) unless you enforce it some way by adding a '10.1.0.0/16 via a' route somewhere and redistribute it.
Since the PBX is the only element which has this routing table size limitation, I would choose some static routing for the PBX (the "consolidated " RIP information) if the configuration would allow that, or even a dedicated router connection to a router running RIP, as a dispatcher for the PBX, with the PBX having just a single default route to that dispatcher, and leave the routing tasks to the router.
Actually my statement is not wrong at all, you gotta read carefully the original post so you'll understand why I said "can be summarized to 10.1.0.0/16" when of course, you can sumarize it to a lower prefix being more precise.
He stated that 10.X.Y.Z were the prefixes being advertised over, where X is the location's number, which means all the routes from that particular location will always have the form 10.X.Y.Z/16 - For instance:
Location 1:
10.1.0.0/16
Location 2:
10.2.0.0/16
You're not taking into account this fact and instead assuming something not related to the original request and specifications. What it means (unless the OP wants to do it a different way) is that all the addressing space from 10.1.0.0 will always belong to location 1. So there's no point on allowing the default route (0.0.0.0/0) to be taken into account for said routes when we know beforehand that they'll always point to the same place (Location's 1 routers).
It's a matter of how the addresses were schematized.
Whenever you have the possibility you should always be precise with the routes, and only use the default route as a last resource (hence the reason for it being called gateway of last resort) - Here am not letting the router guess I'm being precise with the behaviour I want.