[cisco-voip] 911 Sanity Check

[Tim Jackson]

Your provider in Dallas would have to have connectivity to all of the 911
tandems that you are wanting to put service into, unless they are using a
service such as Dash911 etc... Usually only VoIP providers bother using
Dash911 or any sort of location-based E911.. Most traditional telcos will
only be able to offer you 911/E911 service off of whatever the local switch
that your PRI connects to...

There is no motivation (nor should there be) for Verizon to connect to all
of the 911 areas that you wish to service... The DFIATXXADS0 switch that
servces that NPA-NXX (assuming this isn't ported to another carrier)
probably only has trunks into the local Dallas 911 tandem...

You could sign up for Dash911 (http://www.dash911.com/) and use that instead
of routing the calls to your PRI provider in Dallas. They are more oriented
towards service providers, but I am willing to bet that they would
accommodate you.

--
Tim


On 7/11/07, TechGuy <techguy at gmail.com> wrote:
>
> I am having the worst time dealing with our telco SP and 911, because of
> this I have to reach out to others and find out if I am simply asking for
> too much or if there is a major deficiency on the part of our telco
> provider.
>
> Here is the basic issue / scenario I am dealing with.
>
> Business with about 10 different offices spread out in 10 different
> locations / rate centers.
>
> Four PRI's all coming into one data center, and using CallManager to
> manage gateway and phones.  This isn't really a technical issue related to
> callmanager as much as its an issue with the PRI's and 911
>
> The PRI's have 600 DID's all in one range and tied to the telco rate
> center in which the data center is located.
>
> Obviously the data center and the offices are not the same and like I said
> in many different rate centers.
>
> So I have employees with a number that does not accurately represent the
> location they are in.  For arguments sake and in an effort to paint a
> clearer picture here, lets say the data center is in Dallas and the DID
> range is say 972-453-1000 thru 1599
>
> And say I have an employee at an office in Houston, but his number is one
> falling into the range above.
>
> Where this becomes an issue obviously is with 911.  I thought there would
> or should be a way through e911 or something to provide a list of numbers
> and the office they should be tied to.  Say I have setup a group of 100
> numbers from my above range to belong to my Houston office.  It would seem
> that there would or should be a way to have that group of numbers setup to
> reflect the correct address and route to the correct 911 center.
>
> Maybe I am sadly mistaken here and this is not something that can be done
> or can but not by all service providers or something?
>
> My other option obviously is to place a local gateway at each office and
> get a local pots line tied to it and setup callmanager to route 911 calls
> through this gateway for the phones in that particular office. I know I can
> do this, but it really takes away from the whole voip cost savings by
> increasing my need for new hardware.
>
> So, who can help me understand this?  Is this a limitation of the my telco
> service provider if they are saying they can't do this and that I have to
> have numbers on the PRI tied to each rate center?  Because thats where I am
> right now, telco is telling me I have to get numbers or DID's for each rate
> center and use those for each of my offices.  Which to me would just be a
> major admin nightmare.  I would have very inconsistent ext. ranges and such
> all over the place.
>
> Love to hear some thoughts.  Tell me I am crazy and expecting too much,
> missing some obvious point, I can take it.  :-)  I just need to know good or
> bad what the deal is.
>
> Appreciate all your time and thanks for any responses in advance.
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20070711/b986f81d/attachment-0001.html