VM PRO in Linux interactions with databases

[Jimmyjoe1975]

Hi,
The release 10.1 of VM Pro based in Linux is working with database interactions. In previous releases it was forbidden.
According to the documentation:

For Linux-based voicemail servers (IP Office Server Edition and IP Office Application Server), from Release
10.1, database interoperation is supported with external PostgreSQL and MySQL databases. However,
database actions are not supported on the Unified Communications Module.

Does anyone knows if it is also working with SQL Server Databases or it is limited to PostgreSQL and MySQL?
It doesn't any sense if it is only limited to those databases.
Regards

 

[IPGuru]

the docs state it is limited to PostgreSQL & MySQL

it makes perfect sense because those are both open source enterprise grade database engines that run Linux (And windows) and (iirc) as they are both GPL* do not incur any cost to distribute.



* actual postgresql ha its own licensing terms but they are very similar to the BSD licence which has almost no restrictions

Permission to use, copy, modify, and distribute this software and its documentation for any purpose, without fee, and without a written agreement is hereby granted, provided that the above copyright notice and this paragraph and the following two paragraphs appear in all copies.

IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND THE UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.

These two paragraphs (or close facsimiles thereof) appear in all proprietary licences as well so no big deal there.

it is also the DB engine used by contact store/recorder for precisely the same reasons.

It should be a relatively trivial task to write a scheduled task that would copy relevant data from a MSSql server to Postgreql on the IP Office server as required.




Do things on the cheap & it will cost you dear

 

[sizbut]

It doesn't any sense if it is only limited to those databases." - Why?

Stuck in a never ending cycle of file copying.

 

[Jimmyjoe1975]

Because could be plenty of enterprises willing enough to pay for that SQL Server connector as my own company. Once Avaya has developed the connector against one DDBB working with Linux I assume the develop efforts to do it with SQL Server will be insignificant. But for sure the reasons are as IPGuru said.

Regards

 

[janni78]

Avaya hasn't developed the connectors, they are using standard ODBC connectors in Linux and seems to have started with supporting MySQL and PostGRESQL.

I wouldn't be surprised if support for MSSQL comes in a later release. but it seems like you should be able to install it yourself if you really want looking at how it's implemented in AppServer.
It's on my "Test when bored list" but that day hasn't come yet =|

"Trying is the first step to failure..." - Homer

 

[dbuxton101]

I believe Microsoft have already written an ODBC driver for linux for free that Avaya can use. Having said this however the IP office SE uses unixODBC as the driver manager but for some reason they are using version unixODBC-2.2.14-14. The Microsoft SQL ODBC driver requires unixODBC-2.3.0.

https://docs.microsoft.com/en-us/sq...ling-the-microsoft-odbc-driver-for-sql-server