Asterisk LAN-only University Emergency System — Decision Questionnaire¶
Purpose¶
This document lists every naming decision, operational decision, technical decision, permission decision, and policy decision required to finalize the Phase 1 system design.
The system currently has 18 locked features:
-
Campus Emergency Hotline
-
ERT Emergency Queue
-
Emergency Fallback & Escalation Path
-
Emergency Call Recording & Incident Logging
-
Ready-made SIP Client Deployment
-
Emergency Announcement & Paging
-
Incident Command Conference Rooms
-
Emergency Responder Directory & Numbering Plan
-
Responder Status & Availability
-
Emergency Voicemail & Missed-call Recovery
-
Emergency Call Transfer & Dispatch Workflow
-
LAN-only Infrastructure Boundary
-
SIP Security & Access Control
-
Device Provisioning & Extension Management
-
Local Wi-Fi-first Infrastructure Readiness
-
Local System Health Monitoring
-
Emergency SOP & Drill Mode
-
Backup, Restore & Configuration Export
Global System Decisions¶
A. Project Naming¶
- What is the final name of this emergency communication system? UPES-ECS
- Should the name sound official, technical, university-branded, or disaster-response-focused? official
- What short name/acronym should be used internally? UPES-ECS
- What name should appear in SOP documents? UPES-ECS
- What name should appear in student instructions? UPES-ECS
- What name should appear on SIP caller ID or app configuration guides? UPES-ECS
- Should the system be branded under the university name or as a standalone emergency platform? UPES-ECS
B. Core Terminology¶
-
What will the emergency response team be called?
- Emergency Response Team
-
What short form should be used?
- ERT
-
What should the control room be called? UPES-ERT-ROOM
-
What should the main emergency operator role be called?
-
What should the emergency lead role be called?
-
What should student users be called in documentation?
-
What should fixed phones/devices be called?
-
What should internal SIP accounts be called?
-
What should missed emergency records be called?
-
What should test/drill calls be called?
C. Network Naming¶
-
What local domain should SIP clients use?
-
asterisk.local -
asterisk.university.lan -
pbx.university.lan -
Direct IP only
-
Other?
-
-
What should the Asterisk server hostname be?
-
What should the SIP realm/domain be?
-
What should the local monitoring dashboard be called?
-
What should the local admin panel be called?
-
What Wi-Fi SSID will users connect from?
-
Will SIP clients use the normal campus Wi-Fi or a separate emergency/campus voice Wi-Fi?
-
Is client isolation enabled on the Wi-Fi network?
-
Will client isolation need to be disabled or bypassed for SIP access?
-
What LAN subnet is Asterisk on?
-
Which subnets are allowed to register to Asterisk?
D. Identity Model¶
-
Confirm: Should SAP ID be the SIP extension for every human user?
-
Confirm: Should SIP username also be SAP ID?
-
Should display name include both name and SAP ID?
-
What exact caller ID format should be used?
-
Name - SAP ID -
SAP ID - Name -
Name -
SAP ID
-
-
Should students be able to search a directory or only dial SAP IDs manually?
-
Should fixed devices use separate extensions instead of SAP IDs?
-
What fixed-device extension range should be reserved?
-
What service-code ranges should be reserved?
-
Should staff/faculty also use SAP ID as SIP extension?
-
Should ERT members use their personal SAP ID or dedicated ERT role extensions?
-
Should ERT desk phones have fixed device extensions in addition to ERT members’ SAP IDs?
Feature 1: Campus Emergency Hotline¶
Naming Decisions¶
-
What should this feature be officially called?
-
What should students see in posters/instructions?
-
Campus Emergency Hotline
-
University Emergency Line
-
Emergency 111
-
Other?
-
-
What should the emergency number be called in SOPs?
-
What should the Asterisk dialplan label/context name be?
-
What should the incident log label for this call type be?
Core Decisions¶
-
Confirm: Is the emergency number 111?
-
Should any alias numbers also route to the same emergency queue?
-
112
-
101
-
911
-
None
-
-
Should only authenticated SIP users call 111, or should any LAN SIP device be allowed?
-
Should students, staff, ERT, fixed devices, and system devices all be able to call 111?
-
Should guest devices ever be allowed to call 111?
-
Should 111 be reachable from all role contexts?
-
Should 111 always bypass normal calling restrictions?
-
Should 111 calls be prioritized over normal student-to-student calls?
-
Should 111 be shown as the primary emergency number everywhere?
-
Should there be posters/stickers for “Campus Emergency: Dial 111”?
Caller Experience Decisions¶
-
What should the caller hear when dialing 111?
-
Ringback only
-
Short announcement
-
Emergency hold message
-
-
Should the caller hear a message before ERT answers?
-
What should that message say?
-
Should there be different prompts for real calls and drill/test calls?
-
Should the caller be told that the call is recorded?
-
Should the system support multiple simultaneous 111 calls?
-
What should happen if multiple students call 111 at the same time?
Feature 2: ERT Emergency Queue¶
Naming Decisions¶
-
What should the emergency queue be named?
-
emergency_queue -
ert_queue -
campus_111_queue -
Other?
-
-
What should ERT agents be called?
-
What should the queue display name be?
-
What should the caller ID label show when 111 rings ERT?
-
What should queue logs call this queue?
Queue Membership Decisions¶
-
Who are the initial ERT queue members?
-
Will queue members be human SAP ID users, fixed desk phones, or both?
-
Should ERT desk phones be queue members?
-
Should ERT personal mobile SIP apps be queue members?
-
Should the ERT Lead be in the primary queue or escalation-only?
-
Should Medical/Security be direct queue members or dispatch targets only?
-
Should queue membership change by time of day?
-
Should there be active/inactive ERT shifts?
-
How many available responders are required for the queue to be considered healthy?
-
What is the minimum number of ERT agents for go-live?
Queue Behavior Decisions¶
-
What queue strategy should be used?
-
Ring all available
-
Round robin
-
Least recent
-
Fewest calls
-
Other?
-
-
Should all ERT devices ring at once?
-
Should the system avoid ringing busy responders?
-
Should paused responders be skipped?
-
Should offline responders be skipped?
-
How long should the queue ring before escalation?
-
15 seconds
-
20 seconds
-
Other?
-
-
What should the caller hear while waiting?
-
Should there be hold music?
-
Should hold music be disabled for emergency calls?
-
Should queue calls be recorded from the beginning?
Feature 3: Emergency Fallback & Escalation Path¶
Naming Decisions¶
-
What should this escalation feature be called?
-
What should the ERT Lead escalation group be named?
-
What should the backup emergency authority group be named?
-
What should missed escalation logs be called?
-
What should the final unanswered emergency status be called?
Escalation Structure Decisions¶
-
Who is the first escalation target after the ERT queue fails?
-
Is the ERT Lead a person, role extension, or fixed device?
-
What is the ERT Lead extension?
-
What is the timeout before calling the ERT Lead?
-
Who belongs to the backup emergency authority group?
-
Should the backup group ring all at once or in sequence?
-
What is the backup group timeout?
-
Should escalation be different during drills?
-
Should escalation be different during off-hours?
-
Should escalation stop after one person answers?
Final Fallback Decisions¶
-
Should unanswered calls go to emergency voicemail?
-
Should unanswered calls ever disconnect without voicemail?
-
What should the voicemail prompt say?
-
Should the missed call be marked Critical by default?
-
Who is responsible for reviewing unanswered emergency calls?
-
How quickly should missed emergency calls be reviewed?
-
Should missed escalation trigger a visible dashboard alert?
-
Should failed escalation be recorded in incident logs?
-
Should repeated calls from the same caller be grouped?
-
Should voicemail still be created if the caller hangs up before the prompt?
Feature 4: Emergency Call Recording & Incident Logging¶
Naming Decisions¶
-
What should emergency call recordings be called?
-
What should emergency call logs be called?
-
What should the incident ID format be?
-
INC-YYYY-00001 -
ERT-YYYYMMDD-0001 -
Other?
-
-
What should the recording file naming format be?
-
What should the log entry label for 111 calls be?
-
What should missed emergency records be called?
Recording Decisions¶
-
Confirm: Should only calls to 111 be recorded by default?
-
Should student-to-student calls be recorded?
-
Should emergency conference 9000 be recorded?
-
Should side conference rooms be recorded?
-
Should emergency paging audio be recorded?
-
Should recording start immediately when 111 is dialed?
-
Should recording continue through transfer/bridge?
-
Should recordings include caller hold time?
-
Should voicemail recordings be linked to the same incident ID?
-
Should callers be informed that emergency calls may be recorded?
Incident Logging Decisions¶
-
What fields are mandatory in every emergency log?
-
Should caller SAP ID be captured?
-
Should caller display name be captured?
-
Should caller device/IP be captured?
-
Should caller location be captured if fixed device?
-
Should ERT responder identity be captured?
-
Should answer time be captured?
-
Should queue wait time be captured?
-
Should escalation attempts be captured?
-
Should transfer/bridge actions be captured?
-
Should final incident status be mandatory?
-
Should every 111 call create an incident automatically?
-
Should false alarms still be logged?
-
Who can edit incident notes?
-
Who can close an incident?
Retention and Access Decisions¶
-
How long should emergency recordings be retained?
-
Who can listen to recordings?
-
Who can download recordings?
-
Should recording access be logged?
-
Should recordings be encrypted at rest?
-
Should recordings be backed up?
-
Who approves recording deletion?
-
Should recordings be deleted automatically after retention?
-
Should logs remain longer than audio recordings?
-
What is the university policy requirement for emergency records?
Feature 5: Ready-made SIP Client Deployment¶
Naming Decisions¶
-
What should the SIP app setup guide be called?
-
What SIP client will be recommended first?
-
Linphone
-
Zoiper
-
MicroSIP
-
Other?
-
-
What should the student setup profile be named?
-
What should the ERT setup profile be named?
-
What should the fixed-device configuration profile be named?
Client Selection Decisions¶
-
Which SIP app should be recommended for Android?
-
Which SIP app should be recommended for iOS?
-
Which SIP app should be recommended for Windows?
-
Which SIP app should be recommended for macOS/Linux?
-
Should all users use the same app where possible?
-
Should ERT use a different/more controlled client?
-
Should physical IP phones be used for ERT/control room?
-
Should students self-install SIP apps?
-
Should setup be admin-assisted?
-
Should QR provisioning be supported later?
User Setup Decisions¶
-
What server address should users enter?
-
What username should users enter?
-
What password delivery method will be used?
-
Will password be visible once or resettable?
-
Should users be allowed to change SIP passwords?
-
Should users be given screenshots for setup?
-
Should students be given a test number to verify registration?
-
Should users be trained to dial SAP IDs?
-
Should there be a student directory/search method?
-
Should support be available for SIP app setup issues?
Feature 6: Emergency Announcement & Paging¶
Naming Decisions¶
-
What should emergency paging be called?
-
What should all-campus broadcast be called?
-
What should each paging zone be named?
-
What should the paging extension range be?
-
What should paging attempts be called in logs?
Paging Code Decisions¶
-
Confirm: Should paging codes use the 700 range?
-
What should 700 do?
-
What should 701 do?
-
What should 702 do?
-
What should 703 do?
-
What should 704 do?
-
What should 705 do?
-
Are any zones missing?
-
Should paging codes be finalized now or after the roles/location drill?
-
Should paging zones map to buildings, hostels, or functional areas?
Access Decisions¶
-
Who can page all campus?
-
Who can page hostels?
-
Who can page academic blocks?
-
Who can page security gates?
-
Should ERT members page directly or only ERT Lead/control room?
-
Should students be blocked from all paging?
-
Should staff be blocked from paging?
-
Should paging require PIN?
-
Should paging require role-based access only?
-
Should paging attempts be logged?
Operational Decisions¶
-
Should paging be live only in Phase 1?
-
Should pre-recorded messages be added later?
-
Should multilingual announcements be added later?
-
Should paging audio be recorded?
-
Should paging be tested weekly/monthly?
-
Should paging tests require prior notice?
-
What exact phrase should paging messages begin with?
-
Who approves campus-wide paging?
-
Should paging be allowed during drills only with drill prefix?
-
Should unauthorized paging attempts trigger health/security logs?
Feature 7: Incident Command Conference Rooms¶
Naming Decisions¶
-
What should the main conference room be called?
-
Should 9000 be called “Main Incident Command Room”?
-
What should 9001 be called?
-
What should 9002 be called?
-
What should 9003 be called?
-
What should 9004 be called?
-
Should the 9000 range be reserved for emergency conferences?
-
What should conference logs be called?
Room Decisions¶
-
Confirm: Should 9000 be the main command room?
-
How many conference rooms are needed in Phase 1?
-
Should side rooms be enabled immediately or later?
-
Should every emergency room have a PIN?
-
Should only 9000 have a PIN?
-
Should ERT Lead be moderator for 9000?
-
Should participants hear join/leave tones?
-
Should maximum participant limits be set?
-
Should 9000 be recorded by default?
-
Should side rooms be recorded?
-
Should conference rooms be available all the time or activated per incident?
-
Should conference activity link to incident IDs?
Access Decisions¶
-
Who can join 9000?
-
Who can join security room?
-
Who can join medical room?
-
Who can join warden room?
-
Who can join operations room?
-
Can students join any conference room?
-
Can general staff join any conference room?
-
Can unauthorized users dial 9000 and hear rejection?
-
Should failed join attempts be logged?
-
Should conference access be controlled by context, PIN, or both?
Feature 8: Emergency Responder Directory & Numbering Plan¶
Naming Decisions¶
-
What should the responder directory be called?
-
What should the final numbering plan document be called?
-
What should fixed-device extensions be called?
-
What should service numbers be called?
-
What should SAP ID extensions be called?
-
What should the role-design drill be called?
Directory Scope Decisions¶
-
Which roles must appear in the emergency directory?
-
Which fixed locations must appear?
-
Which service codes must appear?
-
Should all students appear in the general directory?
-
Should all staff appear in the general directory?
-
Should emergency directory and student directory be separate?
-
Should personal mobile numbers be included?
-
Should only SIP extensions be included?
-
Should room/location phones be clearly marked?
-
Should directory entries show role, location, and permissions?
Numbering Decisions¶
-
What extension ranges are reserved for fixed devices?
-
What service codes are reserved?
-
What range is reserved for paging?
-
What range is reserved for conferences?
-
Are SAP IDs too long for manual dialing?
-
Should short aliases exist for critical fixed devices?
-
Should ERT desks have short numbers?
-
Should Medical Room have a short fixed extension?
-
Should Security Control Room have a short fixed extension?
-
Should students dial SAP IDs directly or use contact search?
Role-design Drill Decisions¶
-
Who will participate in the role-design drill?
-
What departments/teams need representation?
-
When will the final role list be created?
-
Who approves final extension assignments?
-
Who maintains the directory after launch?
-
How often should the directory be reviewed?
-
What is the process to add/remove emergency roles?
-
What is the process to change fixed-device ownership?
-
How will outdated directory entries be detected?
-
Where will the approved directory be published?
Feature 9: Responder Status & Availability¶
Naming Decisions¶
-
What should responder status be called?
-
What status labels should be used?
-
What should pause/unpause feature codes be named?
-
What should the responder status dashboard be called?
-
What should “unavailable” mean in SOP terms?
Status Decisions¶
-
Confirm Phase 1 statuses:
-
Available
-
Busy
-
Offline
-
Paused
-
-
Should “On Incident” be included in Phase 1 or later?
-
Should “Field Responding” be included later?
-
Should status come from Asterisk only in Phase 1?
-
Should manual status updates be avoided in Phase 1?
-
Should ERT members be allowed to pause themselves?
-
Should ERT Lead be able to pause/unpause others?
-
Should paused status require a reason?
-
Should offline critical devices trigger health warnings?
-
Should queue accept calls if zero responders are available?
Feature Code Decisions¶
-
What code pauses an ERT member from queue?
-
What code unpauses an ERT member?
-
Should codes be
*45and*46or different? -
Should only ERT users be able to use these codes?
-
Should pause/unpause actions be logged?
-
Should accidental pause be prevented?
-
Should a paused responder auto-unpause after some time?
-
Should ERT Lead see all paused users?
-
Should paused users still receive direct calls?
-
Should paused users still join conferences?
Feature 10: Emergency Voicemail & Missed-call Recovery¶
Naming Decisions¶
-
What should emergency voicemail be called?
-
What should missed emergency incidents be called?
-
What should the missed emergency list be named?
-
What status labels should be used for missed calls?
-
What should the voicemail prompt file be named?
Voicemail Decisions¶
-
Confirm: Should unanswered emergency calls go to voicemail?
-
What exact prompt should be used?
-
Should the prompt mention name, location, and emergency?
-
Should caller be asked to stay near the phone?
-
What is maximum voicemail duration?
-
What happens if caller says nothing?
-
What happens if caller hangs up before recording?
-
Should voicemail be automatically linked to incident ID?
-
Should voicemail be marked Critical by default?
-
Should voicemail access be restricted?
Review Workflow Decisions¶
-
Who reviews missed emergency voicemails?
-
What is the required review time?
-
Should every missed emergency remain pending until reviewed?
-
Should callback be mandatory when caller is known?
-
Should callback attempts be logged?
-
What statuses should be used?
-
Pending Review
-
Reviewed
-
Callback Attempted
-
Converted to Active Incident
-
Closed as Duplicate
-
Closed as False Alarm
-
-
Who can close missed emergency incidents?
-
Should missed voicemail appear on local dashboard?
-
Should repeated missed calls from same SAP ID be grouped?
-
Should missed voicemail be included in drill testing?
Feature 11: Emergency Call Transfer & Dispatch Workflow¶
Naming Decisions¶
-
What should this feature be called in SOP?
-
What should each dispatch mode be called?
-
What should dispatch logs be named?
-
What should handoff status labels be?
-
What should incident ownership be called?
Dispatch Mode Decisions¶
-
Confirm supported modes:
-
Dispatch without transfer
-
Warm transfer
-
Three-way bridge
-
-
Should dispatch without transfer be the default?
-
Should warm transfer be the preferred transfer method?
-
Should three-way bridge be used for serious/unclear cases?
-
Should blind transfer be restricted?
-
Should blind transfer be disabled entirely or only discouraged?
-
Who is allowed to use warm transfer?
-
Who is allowed to create a three-way bridge?
-
Can students transfer calls?
-
Can staff transfer calls?
Ownership Decisions¶
-
Who owns an incident after ERT answers?
-
When can ownership be reassigned?
-
Who can reassign ownership?
-
How is handoff confirmation recorded?
-
What happens if target responder does not answer?
-
Should ERT stay on call during critical handoffs?
-
Should ERT always log dispatch actions?
-
Should caller ever be transferred directly without explanation?
-
Should ERT be trained on dispatch modes?
-
Should dispatch workflow be tested during drills?
Logging Decisions¶
-
What fields are required for dispatch logs?
-
Should target extension/team be captured?
-
Should target answer status be captured?
-
Should transfer type be captured?
-
Should bridge participants be captured?
-
Should failed transfers be incidents?
-
Should dispatch notes be mandatory?
-
Should dispatch actions link to recording timestamps?
-
Should all dispatch events appear in incident timeline?
-
Who can edit dispatch logs?
Feature 12: LAN-only Infrastructure Boundary¶
Naming Decisions¶
-
What should the LAN-only boundary be called?
-
What should the internal network be called?
-
What should the local Asterisk server be called?
-
What should the SIP domain be called?
-
What should the system boundary diagram be titled?
Scope Decisions¶
-
Confirm: Is the system LAN-only?
-
Confirm: No public internet dependency?
-
Confirm: No external SIP trunk?
-
Confirm: No PSTN calling?
-
Confirm: No SMS/WhatsApp/email alerts in Phase 1?
-
Confirm: No remote users outside campus?
-
Confirm: No cloud PBX?
-
Confirm: No public SIP/RTP exposure?
-
Confirm: All core records stored locally?
-
Confirm: Local DNS or local IP only?
Network Boundary Decisions¶
-
Which LAN/Wi-Fi networks are allowed?
-
Which subnets can register SIP clients?
-
Which subnets can access admin/monitoring?
-
Which subnets contain fixed devices?
-
Should student Wi-Fi be allowed to reach Asterisk?
-
Should guest Wi-Fi be blocked?
-
Should management access be separated?
-
Should Asterisk have a static IP?
-
Should DNS fallback to IP be documented?
-
Should VLAN segmentation be added later?
Feature 13: SIP Security & Access Control¶
Naming Decisions¶
-
What should each role/context be named?
-
What should the student context be called?
-
What should the staff context be called?
-
What should the ERT context be called?
-
What should the ERT Lead context be called?
-
What should the control room context be called?
-
What should the fixed-device context be called?
-
What should restricted feature attempts be called in logs?
Student Access Decisions¶
-
Confirm: Can students call 111?
-
Confirm: Can students call other students?
-
Can students call staff/faculty?
-
Can students call fixed public campus phones?
-
Can students call ERT directly?
-
Can students receive calls from ERT?
-
Can students join conferences?
-
Can students use paging?
-
Can students transfer calls?
-
Can students access recordings/voicemail?
Staff Access Decisions¶
-
Can staff call students?
-
Can staff call other staff?
-
Can staff call 111?
-
Can staff call ERT directly?
-
Can staff use paging?
-
Can staff join conference rooms?
-
Can staff access recordings?
-
Which staff roles need emergency permissions?
-
Should faculty coordinators have special permissions?
-
Should staff access be same as students by default?
Emergency Role Decisions¶
-
Who can receive 111 queue calls?
-
Who can use paging?
-
Who can join 9000?
-
Who can review voicemails?
-
Who can access recordings?
-
Who can warm transfer emergency calls?
-
Who can create three-way bridges?
-
Who can pause/unpause queue status?
-
Who can manage SIP accounts?
-
Who can view health monitoring?
Security Policy Decisions¶
-
Should anonymous SIP be disabled?
-
Should every user have unique credentials?
-
Should shared credentials be banned except fixed devices?
-
What is the minimum password strength?
-
How are passwords delivered?
-
How are lost devices revoked?
-
Should failed registration attempts be logged?
-
Should unknown devices be blocked?
-
Should account abuse lead to suspension?
-
Who approves role elevation?
Feature 14: Device Provisioning & Extension Management¶
Naming Decisions¶
-
What should the provisioning process be called?
-
What should human SIP accounts be called?
-
What should fixed device accounts be called?
-
What should service codes be called?
-
What should the user onboarding guide be named?
-
What should the SIP password reset process be called?
SAP ID Decisions¶
-
Confirm: SAP ID is SIP extension for all human users?
-
Confirm: SAP ID is SIP username?
-
Should SAP ID be visible in caller ID?
-
Should display name include full name?
-
What happens if a SAP ID changes?
-
What happens when a student leaves?
-
What happens when a staff member leaves?
-
Can one SAP ID register on multiple devices?
-
What is the maximum devices per SAP ID?
-
Should device registration count be monitored?
Fixed Device Decisions¶
-
What extension range should fixed devices use?
-
How are fixed devices named?
-
Who owns each fixed device?
-
Where is each fixed device physically located?
-
Who can request a new fixed device extension?
-
Who can disable a fixed device?
-
Should fixed phones have static IPs?
-
Should fixed phones have restricted dialing?
-
Should fixed phones show location as caller ID?
-
Should fixed devices appear in the emergency directory?
Provisioning Decisions¶
-
Will users be manually provisioned first?
-
Will SAP ID import be CSV-based?
-
Will account creation be automated later?
-
How are SIP passwords generated?
-
How are SIP passwords delivered securely?
-
Should QR setup be supported?
-
Should there be setup guides per OS/app?
-
Who handles user support?
-
Who resets passwords?
-
Who revokes lost devices?
Lifecycle Decisions¶
-
What account states are needed?
-
Pending Setup
-
Active
-
Disabled
-
Password Reset Required
-
Lost Device
-
Archived
-
-
Who can move accounts between states?
-
Should disabled users retain historical logs?
-
Should extension reuse be allowed?
-
Should SAP ID ownership history be preserved?
-
What is the offboarding process?
-
What is the lost-device process?
-
What is the abuse process?
-
What is the bulk import process?
-
What is the audit/export process?
Feature 15: Local Wi-Fi-first Infrastructure Readiness¶
Naming Decisions¶
-
What should this infrastructure feature be called?
-
What should the mobile-first user path be called?
-
What should the ERT fixed-device path be called?
-
What should the local infrastructure diagram be titled?
-
What should the pilot environment be called?
Existing Infrastructure Decisions¶
-
What router is used?
-
What switch is used?
-
What access point is used?
-
What server runs Asterisk?
-
What OS runs on the Asterisk server?
-
What is the Asterisk server IP?
-
Is the Asterisk server static IP configured?
-
What Wi-Fi SSID is used?
-
Is Wi-Fi client isolation enabled?
-
Are SIP/RTP ports allowed inside LAN?
Mobile-first Decisions¶
-
Which mobile SIP app is primary?
-
Which phones will be used for pilot?
-
How many mobile users in pilot?
-
How many simultaneous calls should be tested?
-
Should student-to-student calls be enabled in pilot?
-
Should all pilot users use SAP ID login?
-
Should calls work when phone screen locks?
-
Should users keep SIP app running in background?
-
How will mobile app setup be supported?
-
How will mobile call quality be evaluated?
ERT / Fixed Device Decisions¶
-
Which fixed IP phones are required at launch?
-
Where will ERT answering device be placed?
-
Will ERT use IP phone, mobile SIP app, or both?
-
Will medical room have a fixed SIP phone?
-
Will security have a fixed SIP phone?
-
Will warden/admin have fixed SIP phones?
-
Will IP speakers be deployed in Phase 1?
-
Will paging devices be deployed in Phase 1?
-
Which devices are mandatory for go-live?
-
Which devices are staged for later?
Capacity and Reliability Decisions¶
-
How many users must register simultaneously?
-
How many simultaneous student calls should be supported?
-
How many simultaneous emergency calls should be supported?
-
How many ERT devices should be online?
-
What is acceptable call quality?
-
What is acceptable latency/jitter?
-
What happens if Wi-Fi is weak?
-
What happens if AP is overloaded?
-
Should emergency calls have priority over normal calls?
-
What minimum test results are required for rollout?
Feature 16: Local System Health Monitoring¶
Naming Decisions¶
-
What should the health dashboard be called?
-
What should health statuses be called?
-
OK
-
Warning
-
Critical
-
Offline
-
-
What should the daily readiness check be called?
-
What should the weekly drill health report be called?
-
What should a failed health check be called?
Monitoring Decisions¶
-
Should there be a local dashboard?
-
Is CLI/script-based monitoring enough for MVP?
-
Who checks system health daily?
-
Who checks system health before drills?
-
What devices are critical?
-
Which SIP registrations must always be online?
-
What makes the system unhealthy?
-
What makes the system degraded?
-
What makes the system ready?
-
Who can view health status?
Health Check Decisions¶
-
Should Asterisk service be checked?
-
Should SIP registrations be checked?
-
Should ERT queue availability be checked?
-
Should mobile SIP registration be checked?
-
Should fixed phones be checked?
-
Should recording path be checked?
-
Should voicemail be checked?
-
Should disk usage be checked?
-
Should paging be checked?
-
Should conference rooms be checked?
-
Should access-control violations be checked?
-
Should test call result be checked?
Threshold Decisions¶
-
What disk usage is Warning?
-
What disk usage is Critical?
-
What is minimum available ERT agents?
-
What is maximum acceptable queue wait time?
-
What is maximum acceptable failed SIP registrations?
-
What is acceptable AP/user load?
-
What is acceptable packet loss?
-
What is acceptable call setup time?
-
What should happen if recording fails?
-
What should happen if 111 test call fails?
Feature 17: Emergency SOP & Drill Mode¶
Naming Decisions¶
-
What should the SOP be called?
-
What should Drill Mode be called?
-
What should the test line be called?
-
What should the drill label be?
-
What should the post-drill review document be called?
SOP Decisions¶
-
What exact sentence should ERT say when answering 111?
-
What are the mandatory questions?
-
What are optional questions?
-
What incident categories should be used?
-
What is the dispatch decision tree?
-
When is paging allowed?
-
Who approves paging?
-
When is 9000 activated?
-
Who joins 9000?
-
How are missed voicemails reviewed?
-
How are incidents closed?
-
Who writes incident notes?
-
Who conducts post-incident review?
-
What response-time expectations exist?
-
What is the escalation instruction if ERT is unsure?
Drill Mode Decisions¶
-
Confirm: Should test number be 199?
-
Should 199 simulate the 111 flow?
-
Should 199 avoid real escalation?
-
Should 199 create drill logs only?
-
Should 199 be recorded?
-
Who can call 199?
-
How often should drills happen?
-
Should real 111 be tested during planned drills?
-
Should paging drills require prior notice?
-
Who approves full incident drills?
-
Should drill records be kept?
-
Should drill failures create action items?
-
Who owns action items?
-
What is the post-drill review format?
-
How are responders trained?
Feature 18: Backup, Restore & Configuration Export¶
Naming Decisions¶
-
What should the backup process be called?
-
What should backup snapshots be named?
-
What should config versions be called?
-
What should restore checklists be called?
-
What should export files be named?
-
What should the local Git repo be called?
Backup Scope Decisions¶
-
Should Asterisk config be backed up?
-
Should SIP account data be backed up?
-
Should SAP ID mappings be backed up?
-
Should fixed device mappings be backed up?
-
Should dialplan be backed up?
-
Should queue config be backed up?
-
Should voicemail config be backed up?
-
Should prompts be backed up?
-
Should recordings be backed up?
-
Should logs be backed up?
-
Should health monitoring config be backed up?
-
Should SOP/drill docs be backed up?
Backup Schedule Decisions¶
-
Should backup happen before every config change?
-
Should config be backed up daily?
-
Should logs be exported weekly?
-
Should directory be exported weekly?
-
Should recordings follow separate retention?
-
Should backups rotate automatically?
-
How many backup versions should be kept?
-
Where is the primary backup stored?
-
Where is the secondary backup stored?
-
Is there an encrypted offline copy?
Restore Decisions¶
-
Who can restore the system?
-
Where are restore instructions stored?
-
What is acceptable restore time?
-
What files are restored first?
-
What is the restore verification checklist?
-
Should restore be tested after major changes?
-
Should restore be tested monthly/quarterly?
-
Who signs off successful restore?
-
What happens if backup fails?
-
What happens if restore fails?
Security Decisions¶
-
Should backups be encrypted?
-
Which backups require encryption?
-
Who has backup access?
-
Where are credentials stored?
-
Are recordings included in encrypted backup?
-
Are SIP passwords stored as secrets?
-
Should backup access be logged?
-
Should USB/offline backup be locked physically?
-
Who approves deletion of old backups?
-
What retention policy applies?
Final Cross-feature Decisions¶
Go-live Decisions¶
-
What is the minimum feature set required before pilot?
-
Which features must be fully tested before real use?
-
Which features can be staged later?
-
How many pilot users are needed?
-
Which ERT members participate in pilot?
-
Which fixed devices are mandatory for pilot?
-
Which buildings/areas are included in pilot?
-
What is the go-live date?
-
Who approves go-live?
-
What are rollback conditions?
Phase 1 Success Criteria¶
-
Can mobile SIP clients register over Wi-Fi?
-
Can users call SAP ID to SAP ID?
-
Can any authenticated user call 111?
-
Does 111 reach ERT queue?
-
Does fallback/escalation work?
-
Does emergency voicemail work?
-
Does recording work for 111?
-
Are student calls not recorded by default?
-
Are paging codes restricted?
-
Are conference rooms restricted?
-
Can ERT dispatch using transfer/bridge?
-
Can health checks show system status?
-
Can config be backed up and restored?
-
Can drill mode test the system safely?
-
Are SOPs understood by responders?
Documents to Create After You Answer This¶
-
Final Feature Specification
-
Asterisk Dialplan Design
-
SIP Account and Role Matrix
-
Numbering Plan
-
ERT SOP
-
Drill/Test SOP
-
Student SIP Setup Guide
-
ERT SIP Setup Guide
-
Local Infrastructure Diagram
-
Health Monitoring Checklist
-
Backup and Restore Procedure
-
Rollout Plan
-
Pilot Test Plan
-
Security and Access Control Matrix
-
Incident Logging Schema
-
Emergency Recording and Retention Policy
-
Device Provisioning Sheet
-
Final Go-live Checklist