Matrix Technical Support Mailer 29 Integration of Eternity with Cisco Call Manager



Similar documents
Matrix Technical Support Mailer 59 E1-GSM Gateway Application Using Eternity

Matrix Technical Support Mailer 44

Matrix Technical Support Mailer - 23 Basic Concept of VOIP

Matrix Technical Support Mailer 27 SIP to SIP & SIP to PSTN calling through SIP Registrar (ITSP)

Matrix Technical Support Mailer 148 Proxy Calling

Matrix Technical Support Mailer 139

Matrix Technical Support Mailer 124 Basic steps to configure SIP extensions in ETERNITY NE

Matrix Technical Support Mailer 61 SMDR [Offline & Online] Through Ethernet Port

Matrix Technical Support Mailer 41 Port & IP settings for accessing Security Dongle

Matrix Technical Support Mailer 33 COSEC Integrate (Import from Active Directory)

Matrix Technical Support Mailer 88

FREQUENTLY ASKED QUESTIONS

Matrix Technical Support Mailer - 72 Procedure for Image Upload through Server in SATATYA DVR,NVR & HVR

Matrix Technical Support Mailer 110 LDAP (Lightweight Directory Access Protocol) in SPARSH VP Phones

Matrix Technical Support Mailer-66 How To Upgrade ETERNITY ME/GE/PE & How To Take Configuration Back-Up?

Matrix Technical Support Mailer 167 NAVAN CNX200 PPTP VPN with Windows Client

FAQs on ETERNITY ME/GE/PE. 2. I have connected Analog line to the TWT port of ETERNITY, but line is not working. Why?

SIP Trunking with Allworx. Configuration Guide for Matrix SETU VoIP Gateways

2N NetStar. 2N NetStar as a PBX Booster. Quick guide. Version 1.00

Release Notes for NeoGate TE X

Release Notes for NeoGate TA410/TA X

Quick Installation Guide

SIP Trunking with Elastix. Configuration Guide for Matrix SETU VTEP

SIP Trunking using Optimum Business SIP Trunk Adaptor and the Allworx 6x IP PBX

Configuring Quadro IP PBXs with "SIP Connect"

QUESCOM FAX SOLUTION FOR ENTERPRISE, DEPLOYMENT GUIDE

How to Configure the Avaya IP Office 6.1 for use with Integra Telecom SIP Solutions

DID Destinations are as follows:

ADTRAN SBC and Cisco Unified Call Manager SIP Trunk Interoperability

Configuring Avaya IP Office 500 for Spitfire SIP Trunks

Introduction. VoIP to T1/E1 PRI Gateway

Get Started User Guide

Let's take a look at another example, which is based on the following diagram:

2N OfficeRoute. 2N OfficeRoute & Siemens HiPath (series 3000) connected via SIP trunk. Quick guide. Version 1.00

Configuring Avaya BCM 6.0 for Spitfire SIP Trunks

Allo PRI Gateway and Elastix Server

Table of Contents. Mitel 3000 Getting Started Guide

3CX Guide sip.orbtalk.co.uk

ScopTEL TM IP PBX Software. Managing Incoming Lines

Digium Switchvox AA65 PBX Configuration

Sample Configuration for H.323 Trunk between Avaya IP Office and Cisco Unified Communications Manager 7.0 Issue 1.0

Configuring 3CX for Spitfire SIP Trunks

Table of Contents. Cisco Mapping Outbound VoIP Calls to Specific Digital Voice Ports

Cisco EXAM Implementing Cisco IP Telephony and Video, Part 2 (CIPTV2) Buy Full Product.

TECH ARTICLE Date: 03/04/08

How to Configure the Cisco UC500 for use with Integra Telecom SIP Solutions

How to Connect MyPBX to NeoGate TG via SIP Trunking

Enterprise Communication with VoIP-GSM Gateway

Cisco CallManager 4.1 SIP Trunk Configuration Guide

IP Office Embedded Voic Mailbox User Guide

How to Config MTG1000B With T1 and Elastix

Intercommunication between two MyPBX (via VoIP Trunk)

THINKTEL COMMUNICATIONS DIGIUM G100/G200 PRI OVER IP SIP TRUNKING

SmartPTT Tutorial Telephone Interconnect

Configuring the Sonus SBC 2000 with Cisco Unified Call Manager 10.5 for Verizon Deployment

SIP Trunking using Optimum Business SIP Trunk Adaptor and the Cisco Call Manager Express Version 8.5

White Paper Integration of TTY Calls into a Call Center Using the Placeholder Call Technique Updated: February 2007

Evolution PBX User Guide for SIP Generic Devices

ETERNITY The Universal Telephony Gateway for Any Existing PBX

Application Notes for MultiTech FaxFinder IP with Avaya IP Office Issue 1.0

Certificate of Compatibility

AudioCodes Mediant 1000 Configuration Guide

Inmarsat Fleet F77 fax solutions

Feature and Technical

ACCELERATOR 6.3 ASTERISK 1.4 INTEGRATION GUIDE

Application Notes for Multi-Tech FaxFinder IP with Avaya IP Office Issue 1.0

IP Office Embedded Voic Mailbox User Guide

IP Office 4.2 Embedded Voic Mailbox

Peer-to-Peer SIP Mode with FXS and FXO Gateways

1/40, North Parade Road, PCM Colony, St. Thomas Mount, Chennai , India. Phone:

Avaya IP Office 8.1 Configuration Guide

How to Configure the Toshiba Strata CIX for use with Integra Telecom SIP Solutions

KISUMU LAW COURTS: SPECIFICATIONS FOR A UNIFIED COMMUNICATION SYSTEM / VOICE OVER INTERNET PROTOCOL (VOIP) SOLUTION. Page 54 of 60

Configuring the PBX Call Routing Table for outbound calls (with security against unsecured calls)

Alti-Mobile Extensions

Alcatel-Lucent OmniPCX Office R8.1 Maintenance Software

IP Office Technical Tip

How to Build a Simple Virtual Office PBX System Using TekSIP and TekIVR

Avaya IP Office SIP Trunk Configuration Guide

UX5000 with CommPartners SIP Trunks

Fonality. Optimum Business Trunking and the Fonality Trixbox Pro IP PBX Standard Edition V p13 Configuration Guide

G1E Series eri 40 Port P Hy H brid IP I Communication System

ETERNITY The Universal Telephony Gateway for Any Existing PBX

Cisco Unified Communications Manager SIP Trunk Configuration Guide for the VIP-821, VIP-822 and VIP-824

DINSTAR DAG1000-4S4O with Elastix Setup Guide

IP Office 8.1 Using Voic Pro in Intuity Mode

Skills Assessment Student Training Exam

NEC 2400 IMS --- T1 PRI

Configuration of Applied VoIP Sip Trunks with the Toshiba CIX40, 100, 200 and 670

Wildix W04FXO Whitepaper

Internet Telephony Terminology

IP-PBX Quick Start Guide

IP Office - Job Aid Remote Access

Digium IP-PBX. SIP Trunking using the Optimum Business SIP Trunk Adaptor and the Digium IP-PBX

Managing Legacy PBX Support

Transcription:

Matrix Technical Support Mailer 29 Integration of Eternity with Cisco Call Manager 24.09.2008 Dear Friends, This mailer provides the information related to call possibilities between Matrix Eternity and Cisco C.M. (Call Manager) using ISDN T1/E1/PRI card. It also covers the programming part of Eternity and points for expected configuration in CISCO C.M. Diagram for Integration of Eternity GE and Cisco C.M.

Call Possibilities 1. Internal calling between the extensions of Eternity GE [6XX] & Cisco C.M. [7XX]. 2. Landing of Airtel PRI s DDI numbers [02240014600.699] in Eternity GE on extension series [6XX]. 3. Landing of Airtel PRI s DDI numbers [02240014700.799] in Cisco C.M. directly on VoIP extension series [7XX]. 4. Landing of TATA PRI s DDI numbers [0226657700.799] in Cisco C.M. on VoIP extensions Series [7XX]. 5. Landing of TATA PRI s DDI numbers [0226657600.699] in Eternity GE on extension series [6XX]. 6. Extensions of Eternity GE [6XX] can make OG calls from Airtel PRI. 7. VoIP Extensions of Cisco C.M. [7XX] can make OG calls from TATA PRI. 8. Extensions of Eternity GE [6XX] can make OG calls from TATA PRI. 9. In above system in place of Cisco C.M. any system can be interfaced with Eternity GE/ME but ISDN protocols for both systems should be matched.

Programming Steps To Configure Eternity GE For This Application DDI Routing Table Configuration Table 001 is configured for two applications. 1. When Cisco VoIP extensions will dial any extensions in 6XX series then for landing of those numbers to particular extension in Eternity GE table 001 will be used. 2. If external caller will dial 022400146XX then for landing those DDI numbers to individual extensions in Eternity GE table 001 will be used. Table 002 is configured for below mentioned application. 1. If external caller will dial 022400147XX then for landing those DDI numbers to individual VoIP extensions in Cisco C.M table 002 will be used.

Incoming Reference Table Configuration Incoming Reference Table 01 and 02 are configured to relate DDI routing table with DS1 port parameters. So When ever any incoming call will process by DS1 Port parameters then DDI numbers will reach to DDI Routing table by taking reference from Incoming Reference Table.

Outgoing Reference Table configuration O.G. Reference Table 01 is used for these applications. 1. When any extension from Eternity GE [6XX] will dial VoIP extension of Cisco C.M. then to send CLI to those extensions this table will be used. 2. This 600 will work as Pilot number for internal calling. O.G. Reference Table 02 and 03 are used for this application. 1. When any extension from Eternity GE or Cisco C.M. will make O.G. calls from Airtel PRI [Installed in Eternity GE] then to send individual extension wise CLI to External called party this table will be used.

DS1 Port parameters configuration for PRI Port: 1 PRI port 1 is used for integration with Cisco Call Manager. When any VoIP Extension [7XX] will Dial extension number of Eternity GE [6XX] then it will reach to DDI Routing Table by taking Reference of I.C. Reference Table because here I.C. Reference ID 01 is assigned. When any extension of Eternity GE [6XX] will dial any VoIP extension of Cisco C.M. then extension will reach to destination with it s own CLI, by following OG Reference Table 01 because here O.G. Reference ID 01 is assigned.

DS1 Port parameters configuration for PRI Port: 2 PRI port 2 is used for Interfacing Airtel PRI. When any external caller will dial 022400146XX or 022400147XX then related DDI numbers will reach to DDI Routing Table by taking reference of Incoming Reference Table because here I.C. Reference ID 01 is configured. When any extension of Eternity GE [6XX] or any VoIP Extension [7XX] will dial external number from Airtel PRI then CLI will be displayed by following O.G. Reference table 02 because here O.G. Reference ID 02 is configured.

Outgoing Trunk Bundle configuration O.G. Trunk Bundle Template 01 is configured to access DS1-1, it will be used for internal calling between Eternity GE and Cisco C.M. using application of Closed User Group. O.G. Trunk Bundle Template 02 is configured to make O.G. Calls from Airtel PRI.

Outgoing Trunk Bundle Group configuration O.G. Trunk Bundle Group 01 is used to make O.G. Calls from Airtel PRI by dialing Trunk Access Code 0. O.G. Trunk Bundle Group 02 is used for C.U.G. [Closed User Group Application].

Closed User Group Table Configuration Route Code 7 is programmed so any extension of Eternity GE can dial VoIP extension directly without dialing any Trunk access codes. Route Code 5 can be any digit which is configured as Trunk Access Code in Cisco C.M. for making O.G. calls from TATA PRI.

Access Codes It is very important to take care about Digit conflict problems. To prevent the problem of Digit Conflict, remove or modify the Access codes [Only of Dial Phase] which are matching with Extension numbers or Route code entered in C.U.G. table.

Desired configuration from CISCO C.M. [or Any Other Third party Telecom Switch/ Gateway/ VoIP Call Manager] 1. Such Integration Applications can works with any other Telecom Switch, Gateways, VoIP call manager also, but first important parameter is to match the protocol of PRI for both devices. 2. Cisco C.M. PRI port should be configured in Network mode [NT], which will make routing more easily in Eternity GE and we can have maximum call possibilities. 3. Cisco C.M. should be configured perfectly to process digits received from Eternity GE. 4. For DDI incoming call landing from TATA PRI to Eternity GE, DDI routing table should be configured properly in Cisco C.M. Thanks & Regards Technical Support Team Matrix Telecom, Waghodia, India e-mail: Support@MatrixTeleSol.com Disclaimer: The information contained in this e-mail and/or attachments to it may contain confidential or privileged information. Unauthorized use, disclosure or copying is strictly prohibited and may constitute unlawful act and can possibly attract legal action, civil and/or criminal. The contents of this message need not necessarily reflect or endorse the views of Matrix Telecom Pvt. Ltd on any subject matter. Any action taken or omitted to be taken based on this message is entirely at your risk and neither the originator of this message nor Matrix Telecom Pvt. Ltd takes any responsibility or liability towards the same. If you are not the intended recipient, please notify us immediately and permanently delete the message.