I'm hoping for a few more ideas.
Since the above I've worked with comcast to update the DB (ali/ani?) whereby we assign each address/zone an identifier for both area codes. So: "123 example street" has both 777-222-3333 and 888-444-5555 numbers. This has been tested with almost every PSAP and operates properly.
The issue is resiliency on the 3300 and how it continues to send the CESID from the primary over an IP Trunk to the secondary. I've moved away from hard-coding cesid's on the base devices configured zones. Again, this has worked just fine except resiliency. It was also very handy during testing as I didn't need to reboot or logout of the phone.
One attempt was to disable SDS on the zone form so each 3300 would have unique numbers. Technically that worked to separate the forms, however, it failed in practice as I guess the primary 3300 is responsible for assigning the cesid/cpn before routing over.
Is there a way to force the PBX that ultimately sends the call out a PRI (or SIP) to the pstn/real world to do the assignment or some kind of translation?
During a major failover (pri dies, 3300 dies) I could simply update the zone form, but cannot account for call re-routing over the IP trunk due to all channels being occupied.
Location-based routing doesn't seem to help in this situation either. Sure, I can add the LBR prefix and push calls to different 3300/PRI's as needed, but resiliency continues to be the sticking point.
And if you've read this far down, I appreciate that. I'm starting to think that I'm putting in too much time on this issue since 100% of our 911 calls have gone out the primary. The not so funny part is that it's due to an error in ARS by Mitel installers. They setup a digit modification plan on the emergency IP trunk route to remove 1 digit from the front. So then the secondary 3300 removes another digit, as it should, and bingo the call doesn't go through.
Thank You,
Show Posts
