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 Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Crisis Alert Issue

Status
Not open for further replies.

SF0751

MIS
Apr 15, 2002
3,092
US
We have crisis alert set up on our PBX (CM3.1.2; S8700, ESS, and many S8300/G700 combos). On the crisis-alert sys para screen, we are using both the "Alert Station" and "Alert Pager" sections - although the telephone numbers listed are cell phones and not pagers. This has not been an issue in the past, as the call comes through with a unique phone number (through the pub-unk facility) and the receiving party at least knows that someone, somewhere, made a call to 911.

Recently, the "pager" alerting for 911 calls has stopped working. The only thing that I can think of that might have caused this are the changes that I've been doing for my route patterns. For some unknown reason, the Avaya technicans had previously set up Partition Routing Tables for our ARS routing. Over the past 3-4 weeks, I've been removing the partition routing and putting in straight ARS routing tables for each of my 30 locations.

Here are some facts:
- 911 calls route correctly.
- Calls marked as ALRT calls in all ARS analysis tables route correctly, and alert the stations with CRSS-ALRT buttons.
- None of my route patterns show any blocked or incomplete calls.
- Phantom users (the crisis alert extension) have a COR of 0; and COR 0 has an FRL level of 7.
- The route pattern for 911 calls has an FRL of 0.
- Just for grins, I set the FRL level to 0 for COR 0. No dice.
- I changed the 911 route pattern back to the orginal one (from my partition routing tables) but received the same results.
- Phantom extension cannot be traced with the "list trace stat" command.
- I changed the crisis alert extension to something new without success.

This is driving me nuts. And I'm tired of listening to the weather report for Kodiak, Alaska (my test ALRT number). Can anyone point me in the right direction for this?

Susan
"When the gods wish to punish us, they answer our prayers." - Oscar Wilde, An Ideal husband, 1893
 
Crud. I changed both settings (Alert Stations and Alert Pagers) to No, removed all CRSS-ALRT buttons, and did a SAVE TRANS. Then I re-added the information and tried it again - same (non-) results.

Crud again. Anything else?

Susan
"When the gods wish to punish us, they answer our prayers." - Oscar Wilde, An Ideal husband, 1893
 
Here is the solution, just in case anyone has this issue:

Phantom extensions, like the one used for Crisis Alerting, cannot be assigned to a location. Since they do not have a location, they do not have access to a specific ARS analysis table. I had to put the pager telephone numbers in the ARS ana "all" table (cha ars ana 0) with the correct route table number.

Susan
"When the gods wish to punish us, they answer our prayers." - Oscar Wilde, An Ideal husband, 1893
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top