Invantive EstateOutgoing Calls
You can fill in the profile options that start with bubs-interface-asterisk.
On the Asterisk server you will need to specify in manager.conf in the admin section that you are allowed to connect with database server connection using permit and deny, for example for the new user 'invantive':
[invantive]
secret=amplevoorbeeld
deny=0.0.0.0/0.0.0.0
permit=192.168.172.26/255.255.255.255
read=originate
write=originate
You can test this by making contact with telnet on port 5038 and executing the following statements:
Action: Login
Username: invantive
Secret: amplevoorbeeld
<ENTER>
You then combine this preferably with 'asterisk -rvvvvvvvvvvvv' on the command prompt.
Registration Conversations
Invantive Estate can be integrated with Asterisk. Final result of this integration is that the call-detail-records (CDRs) after the end of a conversation are saved from Asterisk in Invantive Estate as conversations.
To do so, follow these steps:
•Create a user in Invantive Estate via Persons.
•Create an associated Oracle user and connect it to the Invantive Estate-user.
•Give the Oracle user reading- and insert-rights on bubs_asterisk_cdr_r.
•Make it possible for Asterisk to store CDRs in Oracle.
•Install Oracle Instantclient Basic and Oracle Instantclient SQL*Plus for this.
•Configure the Oracle Instantclient in such a way that it is possible to connect with SQL*Plus from the Asterisk server with the Invantive Estate-environment.
•Install and configure unixODBC for the connection between Asterisk and ODBC. The ODBC.INI will then look, for example, like this:
[PRD11R1]
Application Attributes = T
Attributes = W
BatchAutocommitMode = IfAllSuccessful
BindAsFLOAT = F
CloseCursor = F
DisableDPM = F
DisableMTS = T
Driver = Oracle
DSN = PRD11R1
EXECSchemaOpt =
EXECSyntax = T
Failover = T
FailoverDelay = 10
FailoverRetryCount = 10
FetchBufferSize = 64000
ForceWCHAR = F
Lobs = T
Longs = T
MetadataIdDefault = F
QueryTimeout = T
ResultSets = T
ServerName = prd11r1.invantive.local
SQLGetData extensions = F
Translation DLL =
Translation Option = 0
DisableRULEHint = T
UserID =
•The odbcinst.ini will then look, for example, like this:
[Oracle]
Description = Oracle
Driver = /usr/lib/libsqora.so.11.1
Setup =
FileUsage =
CPTimeout =
CPReuse =
[ODBC]
Trace=No
TraceFile=/tmp/sql.log
ForceTrace=No
Pooling=No
•Configure Asterisk CDRs to save the CDRs in Oracle to write the following contents in cdr_odbc.conf:
;
; cdr_odbc.conf
;
[global]
dsn=PRD11R1
username=ESTATE-USERNAME
password=ESTATE-PASSWORD
loguniqueid=yes
dispositionstring=yes
table=bubs_asterisk_cdr_r
;usegmtime=no ; set to "yes" to log in GMT
The file res_odbc.conf should look like:
;
; odbc setup file
;
; ENV is a global set of environmental variables that will get set.
; Note that all environmental variables can be seen by all connections,
; so you can't have different values for different connections.
[ENV]
ORACLE_HOME=>/var/opt/oracle
TNS_ADMIN=>/var/opt/oracle/network/admin
NLS_LANG=>AMERICAN_AMERICA.AL32UTF
; Please note that UTF16 will be used by unixODBC, irrespective of what you tell above.
[PRD11R1]
enabled=>yes
dsn=>PRD11R1
username=>ESTATE-USERNAME
password=>ESTATE-PASSWORD
pre-connect=>yes
