|
|
Table Of Contents
Configuring Enhanced 911 Services for Cisco Unified CME in SRST Fallback Mode
Prerequisites for Enhanced 911 Services
Restrictions for Enhanced 911 Services
Information About Enhanced 911 Services
Overview of Enhanced 911 Services
Planning Your Implementation of Enhanced 911 Services
Interactions with Existing Cisco Unified CME Features
How to Configure Enhanced 911 Services for Cisco Unified CME in SRST Fallback Mode
Configuring the Emergency Response Location
Configuring a Dial Peer for Emergency Calls
Configuring a Dial Peer for Callbacks from the PSAP
Assigning an ERL to a Phone's IP Subnet
Assigning an ERL to a SIP Phone
Assigning an ERL to a Phone's Ephone
Assigning an ERL to a Dial Peer
Verifying Enhanced 911 Services
Troubleshooting Enhanced 911 Services
Configuration Examples for Enhanced 911 Services
Enhanced E911 Services with Cisco Unified CME in SRST Fallback Mode: Example
Feature Information for Enhanced 911 Services for Cisco Unified CME in SRST Fallback Mode
Configuring Enhanced 911 Services for Cisco Unified CME in SRST Fallback Mode
First Published: August 15, 2007This chapter describes the Enhanced 911 Services feature in Cisco Unified Communications Manager Express (Cisco Unified CME).
Finding Feature Information in This Module
Your Cisco Unified CME 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 for Cisco Unified CME in SRST Fallback Mode" section.
Contents
•
Prerequisites for Enhanced 911 Services
•
•
•
•
•
Prerequisites for Enhanced 911 Services
•
•
•
•
•
•
Restrictions for Enhanced 911 Services
•
•
•
•
•
•
•
Information About Enhanced 911 Services
To configure Enhanced 911 Services for Cisco Unified CME in SRST Fallback Mode, you should understand the following concepts:
•
•
•
•
Note
Overview of Enhanced 911 Services
Enhanced 911 Services for Cisco Unified CME in SRST Fallback Mode enables 911 operators to:
•
•
Before this feature was introduced, Cisco Unified CME 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 CME. 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 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 time limit of three hours.
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 CME is using direct-inward-dial numbers or the call is from another Cisco voice gateway that has already translated the extension to an ELIN.
Figure 45 shows a multiline phone system handling phones 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.
Figure 45 Implementation of Enhanced 911 for Cisco Unified CME in SRST Mode
When a 911 call is received by Cisco Unified CME, the initial call processing is the same as for any other call. Cisco Unified CME 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 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 three hours have passed after the call was originated. After the 911 call information is saved to the Last Caller table, 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 46 summarizes the procedure for processing a 911 call.
Figure 46 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 three hours have 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 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.
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. IP phones should not be used 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 (in other words, their 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 CME in SRST Fallback Mode:
Step 1
Be aware that you must use a CAMA/PRI interface to connect to each PSAP. Table 39 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 40 shows an example.
Table 40 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
You might need to configure multiple dial peers for different destination-patterns.
Step 5
Step 6
You have the following choices:
•
•
–
–
–
Table 42 shows examples of each of these options.
Table 42 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
Interactions with Existing Cisco Unified CME Features
Enhanced 911 Services interacts with several Cisco Unified CME 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 CME 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.
Caution
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.
How to Configure Enhanced 911 Services for Cisco Unified CME in SRST Fallback Mode
How you configure Enhanced 911 Services depends on which decision you made in Step 6 in the "Planning Your Implementation of Enhanced 911 Services" section. However, there are three basic components that you must configure regardless of your planning decisions:
•
•
•
In addition, you must specify an ERL for each phone. The type of phones that you have determines which of the following methods you will use to associate an ERL with your phones:
•
•
•
•
Configuring the Emergency Response Location
Perform this procedure to create the ERL. The ERL defines an area that allows emergency teams to quickly locate a caller.
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.
Prerequisites
Cisco Unified CME 4.1 or a later version.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Configuring a Dial Peer 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.
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 an ERL to a Phone's IP Subnet
This procedure is typically used 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 SIP Phone
Perform this procedure if you chose to assign a specific ERL to a SIP phone instead of using the phone's IP address to match a subnet defined for an ERL. For more information about this decision, see Step 6 in the "Planning Your Implementation of Enhanced 911 Services" section.
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 6 in the "Planning Your Implementation of Enhanced 911 Services" section.
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 6 in the "Planning Your Implementation of Enhanced 911 Services" section.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Verifying Enhanced 911 Services
Step 1
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 1Error 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
This section contains the following example:
•
Enhanced E911 Services with Cisco Unified CME in SRST Fallback Mode: Example
In this example, Enhanced 911 Services is configured to assign an ERL to the following:
•
•
•
•
Router#show running-configBuilding configuration...Current configuration : 7557 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 logging console!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!!telephony-servicesrst mode auto-provision noneload 7960-7940 P00307020200load 7970 TERM70.7-0-1-0sload 7912 CP7912060101SCCP050429B.sbinmax-ephones 50max-dn 190ip source-address 10.20.20.3 port 2000system message RM-SCCP-CME-SRSTmax-conferences 8 gain -6moh flash:music-on-hold.aumulticast moh 236.1.1.1 port 3000transfer-system full-consulttransfer-pattern .....transfer-pattern 911!!ephone-dn 1 dual-linenumber 31101!!ephone-dn 2 dual-linenumber 31201!!ephone-dn 3 dual-linenumber 31301!!ephone-dn 100 dual-linenumber 37101 secondary 37111name 7960-sccp-1!!ephone-dn 101 dual-linenumber 37102!!ephone-dn 102 dual-linenumber 37103!!ephone-dn 105number 37201!!ephone-dn 106 dual-linenumber 37101!!ephone-dn 107 dual-linenumber 37302!!ephone-dn 108 dual-linenumber 37303!!ephone-dn 110 dual-linenumber 37401!!ephone-dn 111 dual-linenumber 37402!!ephone 1mac-address DCC0.1111.0001type 7960button 1:1!!ephone 2mac-address DCC0.1111.0002type 7960button 1:2!!ephone 3mac-address DCC0.1111.0003type 7970button 1:3!!ephone 40mac-address 0013.1AA6.7DCFtype 7960button 1:100 2:101 3:102!!ephone 41mac-address 0012.0034.82CDtype 7912button 1:105!!ephone 42mac-address 0014.F237.E000emergency response location 2type 7940button 1:107 2:108!!ephone 43mac-address 000F.90B0.BE0Btype 7960button 1:110 2:111!!line con 0exec-timeout 0 0line aux 0line vty 0 4login!scheduler allocate 20000 1000!endAdditional References
The following sections provide references related to Enhanced 911 Services for Cisco Unified CME in SRST fallback mode.
Related Documents
Cisco Unified CME configuration
•
Cisco IOS voice configuration
•
•
•
Phone documentation for Cisco Unified CME
•
Technical Assistance
Feature Information for Enhanced 911 Services for Cisco Unified CME in SRST Fallback Mode
Table 43 lists the enhancements to the Enhanced 911 Services feature by version.
To determine the correct Cisco IOS release to support a specific Cisco Unified CME 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
Table 43 Feature Information for Enhanced 911 Services
VersionEnhanced 911 Services
4.1
Enhanced 911 Services was introduced.
Posted: Wed Aug 15 17:11:23 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
