Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
911 call handling and disaster recovery
- Thread starter jdrive
- Start date
phoneguy55
Programmer
Send 911 calls to the police. As for DR. Have a good backup.
I might add that along with an offsite copy of the backups I also look to the local providers to route calls to a alternate site if necessary. Site a backups site b. If you don't have multiple sites then a hot site will be ok. These days when the PBX equipment is server based recovery is easy and faster that the old days.
Just my 2 cents
ED
1a2 to ip I seen it all
Just my 2 cents
ED
1a2 to ip I seen it all
ALWAYS send 911 calls to 911, don't redirect/block/etc, it's an invitation for law suits.
I've used crisis-alert for 911 calls in the past. It's great to put on security phones and reception areas. It will report the name and number that called 911, or the room number if you're using the hotelling feature.
It's great if you want to be able to direct authorities to the proper location within the building. It helps prevent surprise appearances by authorities at your door. It's also good if the caller can't communicate with the 911 operator. It helped us once when we had crank calls being made to 911, once the crisis-alert was in place we knew exactly who was making the calls.
- Stinney
Favorite all too common vendor response: "We've never seen this issue before.
I've used crisis-alert for 911 calls in the past. It's great to put on security phones and reception areas. It will report the name and number that called 911, or the room number if you're using the hotelling feature.
It's great if you want to be able to direct authorities to the proper location within the building. It helps prevent surprise appearances by authorities at your door. It's also good if the caller can't communicate with the 911 operator. It helped us once when we had crank calls being made to 911, once the crisis-alert was in place we knew exactly who was making the calls.
- Stinney
Favorite all too common vendor response: "We've never seen this issue before.
Toni269
MIS
- Apr 18, 2002
- 815
jdrive, list out your equipment version and adjunct's, (what are your resources? Do you have multiple sites?) No DR plans are alike, you need to maximize the use of what you have, look for holes and vulnerability and then work towards improving. My DR plan will NEVER be complete, it's a work in progress, always to be updated and improved upon.
For 911, program 911 and also 11, there are planty of history posts in this forum you can search to see how it's programmed.
For 911, program 911 and also 11, there are planty of history posts in this forum you can search to see how it's programmed.
- Thread starter
- #6
We have 2 S8700’s
G3xv11 software version R011
Communication manager 1
Intuity audix v4.4-7
Cms sunblade 150 r3v11ab.g
We do use the crisis alert feature and send calls to 911. I was just wondering what everyone else does out there.
At this time we only have 1 location. We backup our s8700 on an sd-card nightly as well as ftp that’s backed up on our network.
For audix and cms we have a 2 week rotation of daily tapes that we reuse. We haven’t been pulling any of these tapes for storage (should we?)
We backup our VAL board monthly to our network.
We do have a service contract with Avaya but I do not have a disaster recovery plan on paper. Can anyone share their plan?
Thanks
G3xv11 software version R011
Communication manager 1
Intuity audix v4.4-7
Cms sunblade 150 r3v11ab.g
We do use the crisis alert feature and send calls to 911. I was just wondering what everyone else does out there.
At this time we only have 1 location. We backup our s8700 on an sd-card nightly as well as ftp that’s backed up on our network.
For audix and cms we have a 2 week rotation of daily tapes that we reuse. We haven’t been pulling any of these tapes for storage (should we?)
We backup our VAL board monthly to our network.
We do have a service contract with Avaya but I do not have a disaster recovery plan on paper. Can anyone share their plan?
Thanks
just a boring comment but here in england we route 999 to police as well as 112 and because we dial 9 on systems in england to access the pstn ie. 9 for a line the pstn network is set up to route 99 through to police in case a caller dials 999 from a pbx thus only sending 99 to the network....boring i know!!
Toni269
MIS
- Apr 18, 2002
- 815
I would not be able to share any documentation with you but it would depend on what the disaster was and what service was affected.
We have two long distance carriers, redundant sites, redundant DS1 Boards and Signaling Channels, ability to re-route Toll Free numbers to different DNIS or POTS lines instantly, Bank of Centrex lines with 3rd long distance carrier. Ability to change our main long distance carrier to backup long distance carrier on our inbound toll free with SMS routing. 2 phones on the desktop, two IPSI boards per site, trunks coming in over both fiber and copper lines from the same network vendor, I could go on and on. Sounds like you are doing the normal maintenance stuff.
If something were to fail, I would juggle one of my solutions, in many cases I have more than one solution to fix a problem. You could document your sytem if "X" happens then do "X". A good way to start is by creating a network diagram listing all of your services, adjuncts and systems including network vendors with contact info, circuit ID's, account numbers, DID Ranges.
We have two long distance carriers, redundant sites, redundant DS1 Boards and Signaling Channels, ability to re-route Toll Free numbers to different DNIS or POTS lines instantly, Bank of Centrex lines with 3rd long distance carrier. Ability to change our main long distance carrier to backup long distance carrier on our inbound toll free with SMS routing. 2 phones on the desktop, two IPSI boards per site, trunks coming in over both fiber and copper lines from the same network vendor, I could go on and on. Sounds like you are doing the normal maintenance stuff.
If something were to fail, I would juggle one of my solutions, in many cases I have more than one solution to fix a problem. You could document your sytem if "X" happens then do "X". A good way to start is by creating a network diagram listing all of your services, adjuncts and systems including network vendors with contact info, circuit ID's, account numbers, DID Ranges.
- Status
Similar threads
