IVR Portal Deployment and Installation Guide Ver 1.0.0
IVR Portal Deployment and Installation Guide Ver 1.0.0
IVR Portal Deployment and Installation Guide Ver 1.0.0
Installation Guide
Ver 1.0.0
Author(s): Pradeep.D
Date: 24/05/2007
Reviewer(s): Sunil.TM
Date: 21/05/2007
Date:
REVISION HISTORY
Document Title:
Document No:
Revision No.
Revision Date
Change Details
Approved by
Table of Contents
1. Introduction.................................................................................5
1.1 Using this Guide...........................................................................................5
1.2 Related Documents.......................................................................................5
2. Installation Prerequisites.................................................................6
2.1 Media Connectivity Requirements for IVR Portal...................................................6
2.2 Switch requirements.....................................................................................6
2.3 LAN requirements......................................................................................... 6
2.4 Power requirements......................................................................................7
1. Introduction
DaVinci Voice Portal system allows callers to interact with pre-recorded messages over the mobile
phones. IVRS allows one to efficiently and easily access Value added services, by navigation through
the user-friendly voice prompts. System prompts the caller to respond either verbally (ASR) or by
pressing a touchtone key (DTMF), and provides the caller with information based on responses
made.
2. Installation Prerequisites
2.1 Media Connectivity Requirements for IVR Portal
1. Cabling of five E1s, fourE1s for voice (30 voice channels each) and one E1 ss7signaling link
2. OPC (Originating point code)
3. DPC (Originating point code)
4. SLC (signaling link code)
5. CIC (circuit identification code)
6. SSF (service switching function)
7. Signaling time slot
6.
Depth (imperial/metric)
20.6 in
Height (imperial/metric)
15.3 in
Width (imperial/metric)
8.5 in
1kva
Voltage
230v AC
Frequency
50 Hz
5A
DPKwin.exe
Inbound
Tomcat
SMSGateway
3.1.1
Hardware Requirements
CT Bus Cable
Development Package
ISDN protocol
Demos
5. Hardware Installations
Dialogic System Release 6.0
5.1.1
Installation Steps
Please wait while it installs the driver for your dialogic card
Now the Dialogic Software Installation is complete. Click on Finish to restart the Server.
1. After the server is restarted, open the Dialogic Configuration Manager from Start Menu.
If CRC value is OFF then select the media load (.config) file from the {Dialogic}\data\ folder
Voice & Signaling on same E1
E1 Termination
Media Load
gul1_qsb_4_ts16.fcd
(ML1)/
Dialogic
gul10_qsb_4_ts16.fcd(ML 10b)
gul1_qsb_4_net5.fcd
(ML1)/
Septel
Voice and signaling on different E1
E1 termination
Dialogic
gul10b_qsb_4_net5.fcd
Media Load
gul1_qsb_4_net5.fcd
8. Go the same folder(please specify the folder name) from command prompt and execute the
following command Fcdgen and the {mediaload} .config file name
1. Click on the dpkwin.exe to install Septel Card, the following screen will appear
2. Click on Next, a Finish Screen would appear. Click on Finish screen that would complete
the installation procedure for Septel Card
Before configuring the septel card, a file has to be copied from an URL; this file is used to configure
the SS7.DC3 settings.
1. SS7.DC3 Settings
Download
SS7.DC3
and
Isp_nt.exe
from
internet
with
the
following
8. Click on Next
9. Put the name dk0
URL
After configuring the above details, Gcss7.cfg file has to be configured.The following section shows
the exact details of the file and the parameters which have to be changed in the file are marked in
a different colour.
5.2.2
Gcss7.cfg Configurations
#
# Intel (Dialogic) Global Call SS7 Configuration File (gcss7.cfg)
#
#
for Windows
#
# !!! NOTE: all the entries and parameters are CASE SENSITIVE!!!
################################
# Type of System Configuration #
################################
# Leave commented out or set to "None" when not using Dialogic SS7.
# Depending on the value of this parameter, the sections below, that
# are specific to some configurations (SeptelCard, SIU, SIU.Dual) will be
# used or not.
# Format: String - ["None", "Card", "SIU", "DualSIU"]
System.Configuration = "None"
Change this line to
System.Configuration = "Card"
##########################################################
# Parameters for the Global Call SS7 Call Control Library #
##########################################################
# If defined, this parameter will cause the library logging to be
# activated at the first gc_Open () of an SS7 circuit and the trace
# File will have the specified name.
# Format: String
Library.LogFile = "ss7.log"
# Logging Level for the library
# Format: String - ["None", "Errors", "All"]
# Default: "Errors" (and Warnings)
Library.LogLevels = "All"
# Maximum size of the library log in kilobytes
Doc. No./IMI/DaVinci VP/DIG/T14
Ver. 1.0.0
#SIU.B.RemoteConfigDir = "."
# Maximum timeout (in seconds) for how long the service will keep calls in speech after
# control of a circuit group was transfered to other unit due to SIU/RSI/etc. failure
# Format: Integer; Default: 600 seconds; 0 means the feature is disabled
#SIU.Dual.TolerateCallTime = 20
#############################################
# Parameters that are related to config.txt #
#############################################
# MTP Link source - it can be specified in System.Configuration = "Card" mode only
# "link_id" must match the value in config.txt
# "link_source" parameter must be one of the valid dti interfaces carrying SS7 signalling, for ex.:
"dtiB1T31"
If the s7 Link is on the Dialogic then configure this
# MtpLink <link_id> <"link_source">
MtpLink 0 dtiB1
# Circuit Group configuration, Group ID must match the value in config.txt
# "trunk_name" could be any of "dkBx", "dtiBy" or "dumBz"
# "base_TS" parameter defaults to 1 if not set, it must be set if "Pref_SIU" is to be specified
# "Pref_SIU" parameter can have "SIUA" or "SIUB" values only
# CGrp <gid> <"trunk_name"> [<base_TS> [<"Pref_SIU">]]
CGrp 0 dtiB1
(In Case of SS7 Link on the dialogic and SS7 Link on the Septel with only carry signaling) either
this one or
CGrp 0 dkB1 (in case the E1 with ss7 link & Voice on the Septel )
#
# End of gcss7.cfg
#
SS7 Configurations
Configure Config.txt and System.txt in C:\Septel folder as below.
Config.txt
SEPTELPCI_BOARD 0 0x00c2 ss7.dc3 MTP
* Configure individual E1/T1 interfaces:
* LIU_CONFIG <board_id> <liu_id> <liu_type> <line_code> <frame_format> <crc_mode>
Doc. No./IMI/DaVinci VP/DIG/T14
Ver. 1.0.0
LIU_CONFIG 0 0 5 1 1 1
* MTP Parameters:
* MTP_CONFIG <reserved> <reserved> <options>
MTP_CONFIG 0 0 0x0000
*
* Define link sets:
* MTP_LINKSET <linkset_id> <adjacent_spc> <num_links> <flags> <local_spc> <ssf>
MTP_LINKSET 0 665 1 0x0000 964 0x0c
(Change adjacent_spc , local_spc & SSF as per the switch configurations)
*
* Define signaling links:
* MTP_LINK <link_id> <linkset_id> <link_ref> <slc> <board_id> <blink> <stream> <timeslot> <flags>
(In Case of SS7 Link on the dialogic which carry voice and signaling both)
MTP_LINK 0 0 0 0 0 0 0x83 0 0x0006
(change the slc and timeslot as per the switch. Always put time slot 0)
(In Case of SS7 Link on the septel)
MTP_LINK 0 0 0 0 0 0 0 16 0x0006
(change the slc and timeslot as per the switch)
*
* Define a route for each remote signaling point:
* MTP_ROUTE <dpc> <linkset_id> <user_part_mask>
MTP_ROUTE 665 0 0x0020
(Change the dpc as per the switch configurations)
*
* Configure ISUP module:
* ISUP_CONFIG <reserved> <reserved> <reserved> <options> <num_grps> <num_ccts>
ISUP_CONFIG 0 0 0x4d 0x0474 4 128
*
* Configure ISUP circuit groups:
* ISUP_CFG_CCTGRP <gid> <dpc> <base_cic> <base_cid> <cic_mask> <options>
*
*[dtiB1]*
ISUP_CFG_CCTGRP 0 665 0x01 0x01 0x7fff7fff 0x001c 0 0x4d 964 0x0c 0 0x00 (Change the dpc and
opc as per the switch configurations)
*[dtiB2]*
ISUP_CFG_CCTGRP 1 665 0x21 0x21 0x7fff7fff 0x001c 0 0x4d 964 0x0c 0 0x00
(Change the dpc and opc as per the switch configurations)
System.txt
*
* Example system.txt for the DataKinetics Windows NT Development
* Package.
*
* Essential modules running on host:
*
LOCAL
0x20
LOCAL
0x00
*
* Optional modules running on the host:
*
LOCAL
0xcf
LOCAL
0xef
LOCAL
0x2d
LOCAL
0x4d
LOCAL
0x5d
LOCAL
0x6d
LOCAL
0x7d
LOCAL
0x8d
LOCAL
0x9d
LOCAL
0x23
*
* Modules running on the board (all redirected via ssd):
*
REDIRECT
0x22
0x20
* MTP3 module
REDIRECT
0x71
0x20
* MTP2 module
REDIRECT
0x10
0x20
REDIRECT
0x8e
0x20
*
* Redirection of status indications:
*
REDIRECT
0xdf
0xef
*REDIRECT
0xdf
0x4d
*
FORK_PROCESS ssds.exe
FORK_PROCESS tim_nt.exe
FORK_PROCESS tick_nt.exe
FORK_PROCESS s7_mgt.exe -i0x4d -d
FORK_PROCESS s7_log.exe
FORK_PROCESS isp_nt.exe
Doc. No./IMI/DaVinci VP/DIG/T14
Ver. 1.0.0
Go to Command Prompt
2.
Go to septel folder
3.
Type Gctload -d
4.
5.
After starting the DCM, We will get DESTINATION AVIALABLE on the gctload window.
8. Tools
Tools section Checks whether physical Link is up or not
1. Go to command prompt and run this command lineadmin board 0
2. If the physical link is up then in alarm Status section signal status will be green.
Here in above figure following are the details
Line
01
02
03
04
05
Details
Frame Loss
Physical Connectivity problem
Physical Connectivity problem
Physical Connectivity problem
Physical Up