Downloads |
 Feedback
|
Table Of Contents
Information About Enhanced 911 Services
Planning Your Implementation of Enhanced 911 Services
Interactions with Existing Cisco Unified SRST Features
Configuring Enhanced 911 Services
Configuring the Emergency Response Location
Configuring Locations under Emergency Response Zones
Configuring Outgoing Dial Peers for Enhanced 911 Services
Configuring Dial Peers for Emergency Calls
Configuring Dial Peers for Emergency Response Zones
Configuring a Dial Peer for Callbacks from the PSAP
Assigning an ERL to a Phone's IP Subnet
Assigning an ERL to a Phone's Ephone
Assigning an ERL to a Dial Peer
Configuring Customized Settings
Using the Address Command for Two ELINS
Output from a RADIUS Accounting Server
Output from the show call history voice Command
For Version 4.1 and Version 4.2
Troubleshooting Enhanced 911 Services
Configuration Examples for Enhanced 911 Services
For Version 4.1 and Version 4.2
Feature Information for Enhanced 911 Services
Enhanced 911 Services
Last Updated: December 15, 2007This chapter describes the Enhanced 911 Services feature.
Finding Feature Information in This Module
Your Cisco Unified SRST version may not support all of the features documented in this module. For a list of the versions in which each feature is supported, see the "Feature Information for Enhanced 911 Services" section.
Contents
•
Information About Enhanced 911 Services
•
•
•
Prerequisites
•
•
•
•
•
•
Restrictions
•
•
•
•
•
•
Information About Enhanced 911 Services
This section contains the following information about Enhanced 911 Services:
•
•
•
Overview
Enhanced 911 Services for Cisco Unified SRST enables 911 operators to:
•
•
Before this feature was introduced, Cisco Unified SRST supported only outbound calls to 911. With basic 911 functionality, calls were simply routed to a public safety answering point (PSAP). The 911 operator at the PSAP would then have to verbally gather the emergency information and location from the caller, before dispatching a response team from the ambulance service, fire department, or police department. Calls could not be routed to different PSAPs, based on the specific geographic areas that they cover.
With Enhanced 911 Services, 911 calls are selectively routed to the closest PSAP based on the caller's location. In addition, the caller's phone number and address automatically display on a terminal at the PSAP. Therefore, the PSAP can quickly dispatch emergency help, even if the caller is unable to communicate the location. Also, if the caller disconnects prematurely, the PSAP has the information it needs to contact the 911 caller.
To use Enhanced 911 Services, you must define an emergency response location (ERL) for each of the geographic areas needed to cover all of the phones supported by Cisco Unified SRST. The geographic specifications for ERLs are determined by local law. For example, you might have to define an ERL for each floor of a building because an ERL must be less than 7000 square feet in area. Because the ERL defines a known, specific location, this information is uploaded to the PSAP's database and is used by the 911 dispatcher to help the emergency response team to quickly locate a caller.
To determine which ERL is assigned to a 911 caller, the PSAP uses the caller's unique phone number, which is also known as the emergency location identification number (ELIN). Before you can use Enhanced 911 Services you must supply the PSAP with a list of your ELINs and street addresses for each ERL. This information is saved in the PSAP's automatic location identification (ALI) database. Typically, you give this information to the PSAP when your phone system is installed.
With the address information in the ALI database, the PSAP can find the caller's location and can also use the ELIN to callback the 911 caller within a specified time limit. This limit applies to the Last Caller table, which provides the PSAP with the 911 caller's ELIN. If no time limit is specified for the Last Caller table, the default expiry time is three hours.
In addition to saving call formation in the temporary Last Caller table, you can configure permanent call detail records. You can view the attributes in these records from RADIUS accounting, the syslog service, or CLI show commands.
You have the option of configuring zero, one, or two ELINs for each ERL. If you configure two ELINs, the system uses a round-robin algorithm to select which ELIN is sent to the PSAP. If you do not define an ELIN for an ERL, the PSAP sees the original calling number. You may not want to define an ELIN if Cisco Unified SRST is using direct-inward-dial numbers or the call is from another Cisco voice gateway that has already translated the extension to an ELIN.
Optionally define a default ELIN that the PSAP can use if a 911 caller's IP phone's address does not match the IP subnet of any location in any zone. This default ELIN can be an existing ELIN that is already defined for one of the ERLs or it can be a unique ELIN. If no default ELIN is defined and the 911 caller's IP Address does not match any of the ERLs' IP subnets, a syslog message is issued stating that no default ELIN is defined, and the original ANI remains intact.
You can also define a designated callback number that is used when the callback information is lost in the Last Caller table because of an expiry timeout or system restart or when the PSAP cannot reach the 911 caller at the caller's ELIN or the default ELIN for any other reason.
You can further customize your system by specifying the expiry time for data in the Last Caller table and by enabling syslog messages that announce all emergency calls
For large installations, you can optionally specify that calls from specific ERLs are routed to specific PSAPs. This is done by configuring emergency response zones, which lists the ERLs within each zone. This list of ERLs also includes a ranking of the locations which controls the order of ERL searches when there are multiple PSAPs. You do not need to configure emergency response zones if all 911 calls on your system are routed to a single PSAP.
One or more ERLs can be grouped into a zone which could be equivalent to the area serviced by a PSAP. When an outbound emergency call is placed, configured emergency response zones allow the searching of a subset of the ERLs in any order. The ERLs can be ranked in the order of desired usage.
Zones are also used to selectively route 911 calls to different PSAPs.You can configure selective routing by creating a zone with a list of unique locations and assigning each zone to a different outbound dial peer. In this case, zones route the call based on the caller's ERL. When an emergency call is made, each dial peer matching the called number uses the zone's list of locations to find a matching IP subnet to the calling phone's IP address. If an ERL and ELIN are found, the dial peer's interface is used to route the call. If no ERL or ELIN is found, the next matched dial peer checks its zone.
Note
Duplicate location tags are not allowed in the same zone. However, the same location tag can be defined in multiple zones. You are allowed to enter duplicate location priorities in the same zone, however, the existing location's priority is then increased to the next number. For example, if you configure "location 36 priority 5" followed by "location 19 priority 5," location 19 has priority 5 and location 36 becomes priority 6. Also, if two locations are assigned priority 100, rather than bump the first location to priority 101, the first location becomes the first nonprioritized location.
Figure 1 shows a an example configuration for 911 services. In this example, the phone system handles calls from multiple floors in multiple buildings. Five ERLs are defined, with one ELIN defined for each ERL. At the PSAP, the ELIN is used to find the caller's physical address from the ALI database. In this example, building 2 is closer to the PSAP in San Francisco and Building 40 is closer to the PSAP in San Jose. Therefore, in this case, we recommend that you configure two emergency response zones to ensure that 911 calls are routed to the PSAP closest to the caller. In this example, you can configure an emergency response zone that includes all of the ERLS in building 2 and another zone that includes the ERLs in building 40. If you choose to not configure emergency response zones, 911 calls will be routed based on matching with the destination number configured for the outgoing dial peers.
Figure 1 Implementation of Enhanced 911
Call Processing
When a 911 call is received by Cisco Unified SRST, the initial call processing is the same as for any other call. Cisco Unified SRST takes the called-number and searches for dial peers that can be used to route the call to that called-number.
The Enhanced 911 feature also analyzes the outgoing dial peer to see if it is going to a PSAP. If the outgoing dial peer is configured with the emergency response zone command, the system is notified that the call needs Enhanced 911 handling. If the outgoing dial peer is not configured with the emergency response zone command, the Enhanced 911 functionality is not activated and the caller's number is not translated to an ELIN.
When the Enhanced 911 functionality is activated, the first step in Enhanced 911 handling is to determine which ERL is assigned to the caller. There are two ways to determine the caller's ERL.
•
•
After the caller's ERL is determined, the caller's number is translated to that ERL's ELIN. If no ERLs are implicitly or explicitly assigned to a particular call, you can define a default ERL for IP phones. This default ERL does not apply to nonIP-phone endpoints, such as phones on VoIP trunks or FXS/FXO trunks.
After an ELIN is determined for the call, the following information is saved to the Last Caller table:
•
•
•
The Last Caller table contains this information for the most recent emergency callers from each ERL. A caller's information is purged from the table when the specified expiry time has passed after the call was originated. If no time limit is specified, the default expiry time is three hours.
After the 911 call information is saved to the Last Caller table, the system determines whether an emergency response zone is configured that contains the caller's ERL. If no emergency response zone is configured with the ERL, all ERLs are searched sequentially to match the caller's IP address and then route the 911 call to the appropriate PSAP. If an ERL is included in a zone, the 911 call is routed to the PSAP associated with that zone.
After the 911 call is routed to appropriate PSAP, Enhanced 911 processing is complete. Call processing then proceeds as it does for basic calls, except that the ELIN replaces the original calling number for the outbound setup request.
Figure 2 summarizes the procedure for processing a 911 call.
Figure 2 Processing a 911 Call
The 911 operator is unable to find information about a call in the Last Caller table if the router was rebooted or specified expiry time (three hours by default) has passed after the call was originated. If this is the case, the 911 operator hears the reorder tone. To prevent the 911 operator from getting this tone, you can configure the default callback as described in the "Configuring Outgoing Dial Peers for Enhanced 911 Services" section. Alternately, you can configure a call forward number on the dial peer that goes to an operator or primary contact at the business.
Because the 911 callback feature tracks the last caller by its extension number, if you change the configuration of your ephone-dns in-between a 911 call and a 911 callback and within the expiry time, the PSAP might not be able to successfully contact the last 911 caller.
If two 911 calls are made from different phones in the same ERL within a short period of time, the first caller's information is overwritten in the Last Caller table with the information for the second caller. Because the table can contain information about only one caller from each ERL, the 911 operator does not have the information needed to contact the first caller.
In most cases, if Cisco Emergency Responder is configured, you should configure Enhanced 911 Services with the same data for the ELIN and ERL as used by Cisco Emergency Responder.
New Features for Version 4.2
Version 4.2 of Enhanced 911 Services includes these new features:
•
•
•
•
•
Precautions for Mobile Phones
Emergency calls placed from phones that have been removed from their primary site might not be answered by local safety authorities. Do not use IP phones to place emergency calls if removed from the site where it was initially configured. Therefore, we recommend that you require your mobile phone users to agree to a policy similar to the one stated below.
Telecommuters, remote office, and traveling personnel must place emergency calls on a locally configured hotel, office, or home phone landline. If they must use a remote IP phone for emergency calls while away from their configured site, they must be prepared to provide specific information regarding their location (their country, city, state, street address, and so on) to the answering safety authority or security operations center personnel.
By accepting this policy your mobile phone users are confirming that they:
•
•
By not responding to or declining to accept this policy, your mobile phone users are confirming that they understand that all remote IP phone devices associated with them will be disconnected, and no future requests for these services will be fulfilled.
Planning Your Implementation of Enhanced 911 Services
Before you configure Enhanced 911 Services for Cisco Unified SRST, plan your installation as described in the following procedure.
Note
Step 1
Be aware that you must use a CAMA/PRI interface to connect to each PSAP. Table 1 shows an example of the information that you need to gather.
.
Step 2
According to the National Emergency Number Association (NENA) model legislation, make the location specific enough to provide a reasonable opportunity for the emergency response team to quickly locate a caller anywhere within it. Table 2 shows an example.
Table 2 ERL Calculation
Building 2
200,000
3
3
Building 40
7000
2
1
Step 3
You must contact your phone service provider to request phone numbers that are designated as ELINs.
Step 4
Step 5
You might need to configure multiple dial peers for different destination-patterns.
Step 6
Step 7
You have the following choices:
•
•
•
–
–
–
Table 4 shows examples of each of these options.
Table 4 Explicit ERL Assignment Per Phone
Ephone 100
3
Dial-peer voice 213 pots
3
Dial-peer voice 214 voip
4
Voice register pool 1
2
Step 8
Step 9
Step 10
Step 11
Interactions with Existing Cisco Unified SRST Features
Enhanced 911 Services interacts with several existing Cisco Unified SRST features. The interactions with each of the following features are described in separate sections below:
Note
Multiple Usages of an ELIN
Caution
Examples of using ELINs for other purposes include configuring an ELIN for use as an actual phone number (ephone-dn, voice register dn, FXS destination-pattern), a Call Pickup number, or an alias rerouting number.
Using ELINs as an actual phone number causes problems when calls are made to that number. If a 911 call occurs and the last caller information has not expired from the Last Caller table, any outside callers will reach the last 911 caller instead of the actual phone. We recommend that you do not share the phone numbers used for ELINs with real phones.
There is no impact on outbound 911 calls if you use the same number for an ELIN and a real phone number.
Number Translation
The Enhanced 911 feature translates the calling number to an ELIN during an outbound 911 call, and translates the called-number to the last caller's extension during a 911 callback (when the PSAP makes a callback to the 911 caller). Alternative methods of number translation can conflict with the translation done by the Enhanced 911 software, such as:
•
•
•
•
•
•
•
•
Configuring these translation features impacts the Enhanced 911 feature if they translate patterns that are part of your ELINs' patterns. For an outgoing 911 call, these features might translate an Enhanced 911 ELIN to a different number, giving the PSAP a number they cannot look-up in their ALI databases. If the 911 callback number (ELIN) is translated before Enhanced 911 callback processing, the Enhanced 911 feature is unable to find the last caller's history.
Call Transfer
If a phone in a Cisco Unified SRST environment performs a semiattended or consultative transfer to the PSAP that involves another phone that is in a different ERL, the PSAP will use the wrong ELIN. The PSAP will see the ELIN of the transferor party, not the transferred party.
There is no impact on 911 callbacks (calls made by the PSAP back to a 911 caller) or transfers that are made by the PSAP.
A 911 caller can transfer the PSAP to another party if there is a valid reason to do so. Otherwise, we recommend that the 911 caller remain connected to the PSAP at all times.
Call Forward
There is no impact if an IP phone user calls another phone that is configured to forward calls to the PSAP.
If the PSAP makes a callback to a 911 caller that is using a phone that has Call Forward enabled, the PSAP is redirected to a party that is not the original 911 caller.
Call Blocking Features
Outbound 911 calls can be blocked by features such as After-Hours Call Blocking if the system administrator does not create an exception to 911 calls.
911 callbacks will not reach the 911 caller if the phone is configured with a blocking feature (for example, Do Not Disturb).
Call Waiting
After a 911 call is established with a PSAP, call waiting can interrupt the call. The 911 caller has the choice of putting the operator on hold. Although holding is not prohibited, we recommend that the 911 caller remain connected to the PSAP until the call is over.
Three-Way Conference
Although the 911 caller is allowed to activate three-way conferencing when talking to the PSAP, we recommend that the 911 caller remain connected privately to the PSAP until the call is over.
Dial-Peer Rotary
If a 911 caller uses a rotary phone, you must configure each dial peer with the emergency response zone command for the call to be processed as an Enhanced 911 call. Otherwise, calls received on dial peers that are not configured for Enhanced 911 functionality are treated as regular calls and there is no ELIN translation.
Do not configure two dial peers with the same destination-pattern to route to different PSAPs. The caller's number will not be translated to two different ELINs and the two dial peers will not route to different PSAPs. However, you can route calls to different PSAPs if you configure the dial peers with different destination-patterns (for example, 9911 and 95105558911). You might need to use the number translation feature or add prefix/forward-digits to change the 95105558911 to 9911 for the second dial peer if a specific called-number is required by the service provider.
Tip
Dial Plan Patterns
Dial plan patterns expand the caller's original extension number into a fully qualified E.164 number. If an ERL is found for a 911 caller, the expanded number is translated to an ELIN.
For 911 callbacks, the called-number is translated to the 911 caller's expanded number.
Caller ID Blocking
When you set Caller ID Blocking for an ephone or voice-port configuration, the far-end gateway device blocks the display of the calling party information. This feature is overridden when an Enhanced 911 call is placed because the PSAP must receive the ELIN (the calling party information).
The Caller ID Blocking feature does not impact callbacks.
Shared Line
The Shared Line feature allows multiple phones to share a common directory number. When a shared line receives an incoming call, each phone rings. Only the first user that answers the call is connected to the caller.
The Shared Line feature does not affect outbound 911 calls.
For 911 callbacks, all phones sharing the directory number will ring. Therefore, someone who did not originate the 911 call might answer the phone and get connected to the PSAP. This could cause confusion if the PSAP needs to talk only with the 911 caller.
Configuring Enhanced 911 Services
This section contains the following:
•
•
•
•
•
•
•
•
•
Configuring the Emergency Response Location
The ERL can define zero, one, or two ELINs. If one ELIN is defined, this ELIN is always used for phones calling from this ERL. If you define two ELINs, the system alternates using each ELIN for phones calling from this ERL. If you define no ELINs and phones use this ERL, the outbound calls do not have their calling numbers translated. The PSAP sees the original calling numbers for these 911 calls.
If multiple ERLs are created, the Enhanced 911 software uses the ERL tag number to determine which ELIN to use. The Enhanced 911 software searches the ERLs sequentially from tag 1 to 2147483647. The first ERL that has a subnet mask encompassing the caller's IP address is used for ELIN translation.
Note
Prerequisites
•
•
•
Restrictions
The name and address fields are not available for Cisco Unified SRST Version 4.1.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
Configuring Locations under Emergency Response Zones
In the configuration of emergency response zones, a list of locations within a zone is created using location tags. The zone configuration allows a ranking of the locations which controls the order of ERL searches when there are multiple PSAPs. The zone command is not used if all 911 calls on the system are routed to a single PSAP.
Prerequisites
•
•
Restrictions
This feature is not available for Cisco Unified SRST Version 4.1.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Configuring Outgoing Dial Peers for Enhanced 911 Services
Depending on whether you decided to configure emergency response zones while you planned your 911 configuration as described in "Planning Your Implementation of Enhanced 911 Services" section, use one of the following procedures:
•
•
Note
Configuring Dial Peers for Emergency Calls
Perform this procedure to create a dial peer for emergency calls to the PSAP. The destination-pattern of this dial peer is usually some variation of 911, such as 9911. This dial peer uses the port number of the CAMA or PRI network interface card. The new command emergency response zone specifies that this dial peer translates the calling number of any outgoing call's to an ELIN.
PREREQUISITES
Cisco Unified SRST Version 4.2 or Version 4.1 must be installed
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
Configuring Dial Peers for Emergency Response Zones
In Cisco Unified SRST, you can selectively route a 911 call based on the ERL by assigning different zones to a dial peer. The emergency response zone command identifies the dial peer that routes the 911 call and the voice interface to use. The zone tag to this command allows only ERLs that are defined in that zone to be routed on the dial peer. Callers dialing the same emergency number are routed to different voice interfaces based on the zone that includes its ERL.
PREREQUISITES
•
–
–
•
RESTRICTIONS
This feature is not available for Cisco Unified SRST Version 4.1.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
Configuring a Dial Peer for Callbacks from the PSAP
Perform this procedure to create a dial peer for 911 callbacks from the PSAP. This dial peer enables the PSAP to use the ELIN to make callbacks. When a call arrives that matches this dial peer, the emergency response callback command instructs the system to find the last caller that used the ELIN and translate the destination number of the incoming call to the extension of the last caller.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
Assigning ERLs to Phones
Both versions of Cisco Unified SRST can use the same procedures to assign ERLs a phones. The type of phones that you have determines which of the following methods you will use, as explained in Step 7 in the "Planning Your Implementation of Enhanced 911 Services" section. Use one of the following procedures:
•
•
•
Prerequisites
•
•
Assigning an ERL to a Phone's IP Subnet
Use this procedure typically when you have a group of phones that are on the same subnet. You can configure an ERL to be associated with one or two unique IP subnets. This indicates to the Enhanced 911 software that all IP phones that fall into a specific subnet will use the ELIN defined in this ERL.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Assigning an ERL to a Phone's Ephone
Perform this procedure if you chose to assign an ERL to a phone's ephone instead of configuring an ERL to be associated with IP subnets. For more information about this decision, see Step 7 in the "Planning Your Implementation of Enhanced 911 Services" section.
Note
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Assigning an ERL to a Dial Peer
Perform this procedure to assign an ERL to a FXS/FXO or VoIP dial peer. Because these interfaces do not have IP addresses associated with them, you must use this procedure instead of configuring an ERL to be associated with IP subnets. For more information about this decision, see Step 7 in the "Planning Your Implementation of Enhanced 911 Services" section.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Configuring Customized Settings
The E911 settings you can customize are:
•
•
•
•
%E911-5-EMERGENCY_CALL_PLACED: calling #[4085550100] called#[911] ELIN [4085550199]Prerequisites
Cisco Unified SRST Version 4.2 must be installed
Restrictions
This feature is not available for Cisco Unified SRST Version 4.1.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
Using the Address Command for Two ELINS
Note
For ERLs that have two ELINs defined, you cannot use just one address field to have two address entries for each ELIN in the ALI database. Instead of entering the specific phone number, a key phrase is entered to represent each ELIN. The show voice emergency address command produces output that replaces the key phrase with the ELIN information and generates two lines of addresses.
To define the expression, use the keyword elin (context-insensitive), followed by a period, the starting position of the ELIN to use, followed by another period, and finally the ending position of the ELIN. For example:
address I,ELIN.1.3,ELIN.4.7,678 ,Alder Drive ,Milpitas ,CA,95035In the example, the second parameter of address following I are digits 1-3 of each ELIN. The third parameter are digits 4-7 of each ELIN. When you enter the show voice emergency address command, the output will replace the key phrase as seen in the following:
I,408,5550101,678,Alder Drive ,Milpitas ,CA,95035I,408,5550190,678,Alder Drive ,Milpitas ,CA,95035Enabling Call Detail Records
Note
To conform to internal policy or external regulations, you may be required to save 911 call history data including the following information:
•
•
•
•
These attributes are visible from the RADIUS accounting server and syslog server output, or by using the show call history voice command.
Note
Output from a RADIUS Accounting Server
For RADIUS accounting, the emergency call information is under a feature-vsa record. The fields are:
•
•
•
•
•
•
•
•
The following shows an output example from a RADIUS server:
*Jul 18 15:37:43.691: RADIUS: Cisco AVpair [1] 202 "feature-vsa=fn:EMR,ft:07/18/2007 15:37:32.227,frs:0,fid:6,fcid:A2444CAF347B11DC8822F63A1B4078DE,legID:57EC,cgn:6045550101,elin:6045550199,cdn:911,erl:2,erln:Fisco,cip:1.5.6.200,etag:0"Output from a Syslog Server
If gateway accounting is directed to the syslog server, a VOIP_FEAT_HISTORY system message appears. The feature-vsa parameters are the same ones described for RADIUS accounting.
The following shows an output example from a syslog server:
*Jul 18 15:37:43.675: %VOIPAAA-5-VOIP_FEAT_HISTORY: FEAT_VSA=fn:EMR,ft:07/18/200715:37:32.227,frs:0,fid:6,fcid:A2444CAF347B11DC8822F63A1B4078DE,legID:57EC,cgn:6045550199,elin:6045550100,cdn:911,erl:2,erln:ABCDEFGHIJKLMNOPQRSTUVWXYZ123,cip:1.5.6.200,etag:0,bguid:A23F6AD7347B11DC881DF63A1B4078DEOutput from the show call history voice Command
View emergency call information on the gateway using show call active voice and show call history voice. Some emergency call information is already in existing fields. The original caller's number is under OriginalCallingNumber. The ELIN is at TranslatedCallingNumber. The four new fields are the ERL, ERL name, the calling phone's IP address, and any explicit ERL assignments. These fields only appear if an ELIN translation occurs. For example, any 911 calls from an ERL with no ELIN defined do not print the four emergency fields in the show call commands. If no ERLs match the calling phone and the default ELIN is used, the ERL field displays No Match.
The following shows an output example using the show call history voice command:
EmergencyResponseLocation=3 (Cisco Systems 3)ERLAssignment=3DeviceIPAddress=1.5.6.202Verifying E911 Configuration
For Version 4.2 Only
New show commands are introduced to display E911 configuration or usage.
•
Router# show voice emergencyEMERGENCY RESPONSE LOCATIONSERL | ELIN 1 | ELIN2 | SUBNET 1 | SUBNET 21 | 6045550101 | | 10.0.0.0 | 255.0.0.02 | 6045550102 | 6045550106 | 192.168.0.0 | 255.255.0.03 | | 6045550107 | 172.16.0.0 | 255.255.0.04 | 6045550103 | | 192.168.0.0 | 255.255.0.05 | 6045550105 | | 209.165.200.224 | 255.0.0.06 6045550198 | | 6045550109 | 209.165.201.0 | 255.255.255.224•
Router# show voice emergency addresses3850 Zanker Rd, San Jose,604,5550101225 W Tasman Dr, San Jose,604,5550102275 W Tasman Dr, San Jose,604,5550103518 Bellew Dr,Milpitas,604,5550104400 Tasman Dr,San Jose,604,55501053675 Cisco Way,San Jose,604,5550106•
Router# show voice emergency allVOICE EMERGENCY RESPONSE SETTINGSCallback Number: 6045550103Emergency Line ID Number: 6045550155Expiry: 2 minutesLogging EnabledEMERGENCY RESPONSE LOCATION 1Name: Cisco Systems 1Address: 3850 Zanker Rd, San Jose,elin.1.3,elin.4.10IP Address 1: 209.165.200.226 IP mask 1: 255.255.255.254IP Address 2: 209.165.202.129 IP mask 2: 255.255.0.0Emergency Line ID 1: 6045550180Emergency Line ID 2:Last Caller: 6045550188 [Jan 30 2007 16:05.52 PM]Next ELIN For Emergency Call: 6045550166EMERGENCY RESPONSE LOCATION 3Name: Cisco Systems 3Address: 225 W Tasman Dr, San Jose,elin.1.3,elin.4.10IP Address 1: 209.165.202.133 IP mask 1: 255.255.0.0IP Address 2: 209.165.202.130 IP mask 2: 255.0.0.0Emergency Line ID 1:Emergency Line ID 2: 6045550150Last Caller:Next ELIN For Emergency Call: 6045550151•
Router# show voice emergency zoneEMERGENCY RESPONSE ZONESzone 90location 4location 5location 6location 7location 2147483647zone 100location 1 priority 1location 2 priority 2location 3 priority 3For Version 4.1 and Version 4.2
Use the show voice emergency callers command to see the translations made by outbound 911 calls. This command lists the originating number, the ELIN used, and the time for each 911 call. This history is active for only three hours after the call is placed. Expired calls are not shown in this output.
router# show voice emergency callersEMERGENCY CALLS CALL BACK TABLEELIN | CALLER | TIME6045550100 | 6045550150 | Oct 12 2006 03:59:436045550110 | 8155550124 | Oct 12 2006 04:05:21Troubleshooting Enhanced 911 Services
Step 1
This example shows the debug output when a call to 911 is made:
router# debug voice application errorrouter# debug voice application callsetupNov 10 23:49:05.855: //emrgncy_resp_xlate_callingNum: InDialPeer[20001], OutDialPeer[911] callingNum[6046692003]Nov 10 23:49:05.855: //ER_HistTbl_Find_CallHistory: 6046699100Nov 10 23:49:05.855: //59//Dest:/DestProcessEmergencyCall: Emergency Call detected: Using ELIN 6046699100This example shows the debug output when a PSAP calls back an emergency caller:
router# debug voice application errorrouter# debug voice application callsetupNov 10 23:49:37.279: //emrgncy_resp_xlate_calledNum: calledNum[6046699100], dpeerTag[6046699]Nov 10 23:49:37.279: //ER_HistTbl_Find_CallHistory: 6046699100Nov 10 23:49:37.279: //HasERHistoryExpired: elapsedTime[10 minutes]Nov 10 23:49:37.279: //67//Dest:/DestProcessEmergencyCallback: Emergency Response Callback: Forward to 6046692003.Nov 10 23:49:37.279: //67//Dest:/DestCaptureCallForward: forwarded to 6046692003 reason 1
Error Messages
The Enhanced 911 feature introduces a new system error message. The following error message displays if a 911 callback cannot route to the last 911 caller because the saved history was lost because of a reboot, an expiration of an entry, or a software error:
%E911_NO_CALLER: Unable to contact last 911 caller.Configuration Examples for Enhanced 911 Services
For Version 4.2 Only
Emergency response settings are:
•
•
•
Zone 1 has four locations, 1, 2, 3, and 4, and a name, address, and elin are defined for each location. Each of the four locations is assigned a priority. In this example, because location 4 has been assigned the highest priority, it is the first that is searched for IP subnet matches to identify the ELIN assigned to the 911 caller's phone. A dial peer is configured to route 911 calls to the PSAP (voice port 1/0/0). Callback dial peers are also configured.
voice emergency response settingselin 6045550120expiry 180callback 6045550199voice emergency response location 1name Bldg C, Floor 1address I,604,5550135, ,184 ,Main St,Kansas City,KS,1,elin 1 6045550125subnet 1 172.16.0.0 255.255.0.0!voice emergency response location 2name Bldg C, Floor 2address I,elin.1.3,elin.4.7, ,184 ,Main St,Kansas City,KS,2,elin 1 6045550126elin 2 6045550127subnet 1 192.168.0.0 255.255.0.0!voice emergency response location 3name Bldg C, Floor 3address I,604,5550138, ,184 ,Main St,Kansas City,KS,3,elin 2 6045550128subnet 1 209.165.200.225 255.255.0.0subnet 2 209.165.200.240 255.255.0.0!voice emergency response location 4name Bldg Daddress I,604,5550139, ,192 ,Main St,Kansas City,KS,elin 1 6045550129subnet 1 209.165.200.231 255.255.0.0!voice emergency response zone 1location 4 priority 1location 3 priority 2location 2 priority 3location 1 priority 4!dial-peer voice 911 potsdescription Public Safety Answering Pointemergency response zone 1destination-pattern 911port 1/0/0!dial-peer voice 6045550 voipemergency response callbackdestination-pattern 6045550...session target loopback:rtpcodec g711ulaw!dial-peer voice 1222 potsemergency response location 4destination-pattern 6045550130port 1/0/1!dial-peer voice 5550144 voipemergency response callbacksession target ipv4:1.5.6.10incoming called-number 604555....codec g711ulaw!
For Version 4.1 and Version 4.2
In this example, Enhanced 911 Services is configured to assign an ERL to the following:
•
•
•
Router#show running-config
Building configuration...Current configuration : 6241 bytes!version 12.4service timestamps debug datetime msecservice timestamps log datetime msecno service password-encryption!!hostname rm-uut3-2821!boot-start-markerboot-end-marker!no aaa new-modelnetwork-clock-participate wic 1network-clock-participate wic 2no network-clock-participate wic 3!!ip cefno ip dhcp use vrf connected!ip dhcp pool sccp-7912-phone1host 10.20.20.122 255.255.0.0client-identifier 0100.1200.3482.cddefault-router 10.20.20.3option 150 ip 10.21.20.218!ip dhcp pool sccp-7960-phone2host 10.20.20.123 255.255.0.0client-identifier 0100.131a.a67d.cfdefault-router 10.20.20.3option 150 ip 10.21.20.218dns-server 10.20.20.3!ip dhcp pool sip-phone1host 10.20.20.121 255.255.0.0client-identifier 0100.15f9.b38b.a6default-router 10.20.20.3option 150 ip 10.21.20.218!ip dhcp pool sccp-7960-phone1host 10.20.20.124 255.255.0.0client-identifier 0100.14f2.37e0.00default-router 10.20.20.3option 150 ip 10.21.20.218dns-server 10.20.20.3!!no ip domain lookupip host rm-uut3-c2821 10.20.20.3ip host RescuMe01 10.21.20.218multilink bundle-name authenticated!isdn switch-type basic-net3!!voice service voipallow-connections h323 to h323allow-connections h323 to sipallow-connections sip to h323allow-connections sip to sipsupplementary-service h450.12sipregistrar server!!voice register globalsystem message RM-SIP-SRSTmax-dn 192max-pool 48!voice register dn 1number 32101!voice register dn 185number 38301!voice register dn 190number 38201!voice register dn 191number 38202!voice register dn 192number 38204!voice register pool 1id mac DCC0.2222.0001number 1 dn 1emergency response location 2100!voice register pool 45id mac 0015.F9B3.8BA6number 1 dn 185!voice emergency response location 1elin 1 22222subnet 1 10.20.20.0 255.255.255.0!voice emergency response location 2elin 1 21111elin 2 21112!!voice-card 0no dspfarm!!archivelog confighidekeys!!controller T1 0/1/0framing esflinecode b8zspri-group timeslots 8,24!controller T1 0/1/1framing esflinecode b8zspri-group timeslots 2,24!controller T1 0/2/0framing esfclock source internallinecode b8zsds0-group 1 timeslots 2 type e&m-immediate-start !controller T1 0/2/1framing esflinecode b8zspri-group timeslots 2,24!!translation-rule 5Rule 0 ^37103 1!!translation-rule 6Rule 6 ^2 911!!interface GigabitEthernet0/0ip address 31.20.0.3 255.255.0.0duplex autospeed auto!interface GigabitEthernet0/1ip address 10.20.20.3 255.255.0.0duplex autospeed auto!interface Serial0/1/0:23no ip addressencapsulation hdlcisdn switch-type primary-5essisdn incoming-voice voiceno cdp enable!interface Serial0/1/1:23no ip addressencapsulation hdlcisdn switch-type primary-net5isdn incoming-voice voiceno cdp enable!interface Serial0/2/1:23no ip addressencapsulation hdlcisdn switch-type primary-net5isdn incoming-voice voiceno cdp enable!interface BRI0/3/0no ip addressisdn switch-type basic-5essisdn twait-disableisdn point-to-point-setupisdn autodetectisdn incoming-voice voiceno keepalive!interface BRI0/3/1no ip addressisdn switch-type basic-5essisdn point-to-point-setup!!ip http server!!voice-port 0/0/0!voice-port 0/0/1!voice-port 0/1/0:23!voice-port 0/2/0:1!voice-port 0/1/1:23!voice-port 0/2/1:23!voice-port 0/3/0!voice-port 0/3/1!!dial-peer voice 2002 potsshutdowndestination-pattern 2....port 0/2/0:1forward-digits all!dial-peer voice 2005 potsdescription for-cme2-408-priemergency response location 2000shutdownincoming called-number 911direct-inward-dialport 0/2/1:23forward-digits all!dial-peer voice 2004 voipdescription for-cme2-408-thru-ipemergency response location 2000shutdownsession target loopback:rtpincoming called-number 911!dial-peer voice 1052 potsdescription 911callbackto-cme2-3shutdownincoming called-number .....direct-inward-dialport 0/1/1:23forward-digits all!dial-peer voice 1013 potsdescription for-analogdestination-pattern 39101port 0/0/0forward-digits all!dial-peer voice 1014 potsdescription for-analog-2destination-pattern 39201port 0/0/1forward-digits all!dial-peer voice 3111 potsemergency response Zonedestination-pattern 9....port 0/1/0:23forward-digits all!dial-peer voice 3121 potsemergency response callbackincoming called-number 2....direct-inward-dialport 0/1/0:23forward-digits all!!call-manager-fallbackmax-conferences 8 gain -6transfer-system full-consultip source-address 10.20.20.3 port 2000max-ephones 3max-dn 3 dual-line preference 1system message primary SRST-UUT3-2851keepalive 45!!line con 0exec-timeout 0 0line aux 0line vty 0 4login!scheduler allocate 20000 1000!endrm-uut3-2821#$Additional References
The following sections provide references related to Enhanced 911 Services for Cisco Unified SRST.
Related Documents
Cisco Unified SRST configuration
•
Cisco IOS voice configuration
•
•
•
Phone documentation for Cisco Unified SRST
•
Obtaining Documentation
Obtaining Support
Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
•
whatsnew.html
Standards
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
RFCs
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
—
Technical Assistance
Feature Information for Enhanced 911 Services
Table 5 lists the enhancements to the Enhanced 911 Services feature by version.
To determine the correct Cisco IOS release to support a specific Cisco Unified SRST version, see the Cisco Unified CME and Cisco IOS Software Version Compatibility Matrix at http://www.cisco.com/en/US/products/sw/voicesw/ps4625/products_documentation_roadmap09186a0080189132.html.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
