Avaya Definity CM2.0 using T1 QSIG to Cisco Unified Communications Manager 6.0 and Cisco Emergency Responder 2.0
Disclaimer
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS DOCUMENT ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS DOCUMENT ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE CUSTOMER ASSUMES ALL RESPONSIBILITY FOR PROPERLY CONFIGURING THE CISCO EMERGENCY RESPONDER. CISCO HEREBY DISCLAIMS ANY AND ALL LIABILITY ARISING FROM OR IN CONNECTION WITH A USERS INABILITY TO REACH EMERGENCY SERVICE RESPONDERS (INCLUDING INABILITY TO ACCESS A PUBLIC SAFETY ANSWERING POINT) OR THE INABILITY OF EMERGENCY SERVICE RESPONDERS TO IDENTIFY A USERS LOCATION. CISCO STRONGLY RECOMMENDS THAT ALL CUSTOMERS VERIFY AND TEST CONFIGURATION OF THE CISCO EMERGENCY RESPONDER IMMEDIATELY FOLLOWING INITIAL CONFIGURATION AND ON A PERIODIC BASIS THEREAFTER. CISCO FURTHER RECOMMENDS THAT ALL CUSTOMERS PROVIDE ADEQUATE TRUNK AND BANDWIDTH CAPACITY TO ENSURE THAT AUDIO PATHS ARE AVAILABLE FOR EMERGENCY CALLS.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS PRODUCT, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
July 11, 2007 Initial version
Table of Contents
Introduction
The following is an Application Note for E911 Interoperability of a Cisco Unified Communications Manager 6.0 and Cisco Emergency Responder 2.0 to a Avaya Definity G3 CM 2.0 PBX via a Cisco Media Module CMM T1-QSIG trunk. The CUCM system is connected to a simulated E911 PSAP (Public Safety Answering Point) via a Cisco 3845 w/ CAMA trunk registered using H323.
The Network Topology diagram shows the test set-up for interoperability between the Cisco Unified Communictaions Manager and Cisco Emergency Responder connected to the PBX via a T1 QSIG trunk using Cisco WS-SVC-CMM-6T1 MGCP gateway and connection to E911 PSAP using a Cisco 3825 H323 gateway via a CAMA trunk.
Network Topology
.
Figure 1. Network Topology or Test Setup
Limitations
Unique DID numbers must be used to associate with each Emergency Response Location to allow the return call if the 911 caller is disconnected.
Each available calling party that might dial 911 from the PBX side must have that calling party number configured in the Manually Configured Phones screen of the Cisco Emergency Responder.
System Components
Hardware Requirements
Cisco Hardware
Cisco 3825 Gateway with VIC2-4FXO (CAMA trunk)
Cisco WS-SVC-CMM-6T1 Communications Media Module (inserted into cat6K)
Cisco Cat6K switch
Cisco Unified Communications Manager server
Cisco Emergency Responder server
AVAYA Definity PBX
Software Requirements
IOS Software release "c3825-ipvoice-mz.124-11.T"
IOS Software release "wscmm-ipvoicek9-mz.124-11.T
PBX Software: G3si MV1.1
Cisco CallManager 6.0
Cisco Emergency Responder 2.0
Features
Key features supported
Calling Number
E911 ERL DID number passed to PSAP
Incoming DID calling to disconnected 911originating caller
Conclusion
Test emergency 911 call from a PBX digital station was routed to the T1 QSIG trunk, of the Cisco WS-SVC-CMM-6T1 (CMM) MGCP gateway, and was correctly associated to the appropriate Emergency Response Location. The call was connected through the Cisco 3825 CAMA trunk to the PSAP Emulator. The Emergency Response Location associated the ten digit DID call back number (ELIN) correctly and sent it to the PSAP, audio connection was also achieved. The PBX digital station was then disconnected.
A return call was originated from an incoming trunk (PSTN side) in the same Cisco CallManager Partition. The number dialed was the DID digits of the 10 digit call back number sent to the PSAP on the previous 911 call (ELIN number). The call was routed through to the PBX digital station that had originated the E911 call. The call was disconnected and an alternate trunk was used to dial the same DID number and the call was routed through, again, to the PBX digital station that had originated the E911 call.
Test emergency 911calls were made from each PBX digital station and Cisco IP phone. All calls were confirmed to select its associated Emergency Response Location and the associated 10 digit DID call back number. In each case, the call was disconnected and the call back number was confirmed to reach the phone that had originated the E911 call.
Emergency 911calls made from an AVAYA CM 2.0 PBX utilizing a T1 QSIG trunk configured as ISO, associates with the correct Emergency Response Location and routes to the associated PSAP with the correctly formatted 10 digit DID call back number.
The call back DID number routes the return call to the correct phone that had originated the E911 call from the PBX digital phone.
Configuration
Cisco Communications Manager configuration
Partitions
Phone Partition
E911 Partition
Calling Search Space
CSS phones
CSS E911
CCM IP phones
CTI Route Points
CTI Route Point 911
CTI Route Point 913
Note: A Backup CER server was not used during testing therefore CTI route point for 912 was not created.
set interface sc0 109 172.20.8.20/255.255.255.0 172.20.8.255
AVAYA Definity Configuration
DS1 CIRCUIT PACK
SIGNALING GROUP
TRUNK GROUP
Acronyms
Acronym
Definitions
CAMA
Analog "Centralized Automatic Message Accounting" E911 Trunk
PSAP
Public Service Answering Point
Important Information
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Corporate Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 526-4100
European Headquarters
Cisco Systems International BV
Haarlerbergpark
Haarlerbergweg 13-19
1101 CH Amsterdam
The Netherlands
www-europe.cisco.com
Tel: 31 0 20 357 1000
Fax: 31 0 20 357 1100
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
www.cisco.com
Tel: 408 526-7660
Fax: 408 527-0883
Asia Pacific Headquarters
Cisco Systems, Inc.
Capital Tower
168 Robinson Road
#22-01 to #29-01
Singapore 068912
www.cisco.com
Tel: +65 317 7777
Fax: +65 317 7799
Cisco Systems has more than 200 offices in the following countries and regions. Addresses, phone numbers, and fax numbers are listed on the Cisco Web site at www.cisco.com/go/offices.
Argentina · Australia · Austria · Belgium · Brazil · Bulgaria · Canada · Chile · China PRC · Colombia · Costa Rica · Croatia · Czech Republic · Denmark · Dubai, UAE · Finland · France · Germany · Greece · Hong Kong SAR · Hungary · India · Indonesia · Ireland · Israel · Italy · Japan · Korea · Luxembourg · Malaysia · Mexico · The Netherlands · New Zealand · Norway · Peru · Philippines · Poland · Portugal · Puerto Rico · Romania · Russia · Saudi Arabia · Scotland · Singapore · Slovakia · Slovenia · South Africa · Spain · Sweden · Switzerland · Taiwan · Thailand · Turkey Ukraine · United Kingdom · United States · Venezuela · Vietnam · Zimbabwe
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0502R)