Please enable JavaScript to view this site.

Invantive Estate Estate Forums

Navigation: Invantive Estate > Koppelingen

Asterisk VOIP Interface

Outgoing 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

X

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

  • Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
  • Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
  • Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
  • Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
  • Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
  • Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
  • Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
  • Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.
  
Disclaimer