Author |
Message |
teq Brekeke Newbie
Joined: 13 Nov 2018 Posts: 1
|
Posted: Tue Nov 13, 2018 8:47 pm Post subject: Problem connecting to a 3rd party registered DB |
|
|
1. Brekeke Product Name and Version: Brekeke SIP Server , version 2.4.8.6 Standard
2. Java version: 1.6.0_30 OpenJDK Runtime Environm (IceTea6 1.13.3) (rhel-5.1.13.3.e15_10-i386)
OpenJDK Client VM (Build 23.25-b01, mixed mode)
3. OS type and the version: Centos 5.10
4. UA (phone), gateway or other hardware/software involved:
5. Your problem:
I have configured to connect to my 3rd party MSSQL DB.
When I try to start the proxy, it gives me below error:
"Cannot open registered DB. Check Entries under Configuration Database, then try restarting SIP Server"
I have set the following
Registered Database URL: jdbc:jtds:sqlserver://192.168.1.100:1433/Callback
Registered Database Driver : net.sourceforge.jtds.jdbc.Driver
I have another similar Brekeke server with the same setting and that works fine. A little difference in the OS and java version, as below.
1. Brekeke Product Name and Version: Brekeke SIP Server , version 2.4.5.5 Standard
2. Java version: 1.6.0 OpenJDK Runtime Environm (build 1.6.0-b09)
OpenJDK Server VM(Build 1.6.0-b09, mixed mode)
3. OS type and the version: Centos 5.50
Would appreciated if someone can tell me why I cannot connect to the 3rd party DB.
Thank you so much.
Regards,
hp |
|
Back to top |
|
Tata Brekeke Master Guru
Joined: 27 Jan 2008 Posts: 223
|
Posted: Wed Nov 14, 2018 11:35 am Post subject: |
|
|
There are several checkpoints.
- Have you put the JDBC driver file under Tomcat's lib folder?
- It seems you are using jTDS's JDBC driver.
Does it compatible with your MS SQL Server's version?
- Does it compatible with the Java 1.6?
I think Java 1.6 is too old to use recent JDBC drivers...
For the best performance, I recommend:
- Use the latest version of Brekeke SIP Server.
It is version 3.8.6.4.
The version 2.4.8.6 is too old because it was released 7 years ago.
FYI: http://wiki.brekeke.com/wiki/BSS_History
- Use Microsoft's official JDBC driver.
FYI: https://docs.microsoft.com/en-us/sql/connect/jdbc/download-microsoft-jdbc-driver-for-sql-server?view=sql-server-2017
- Use Oracle Java 1.8.
If you want to stick with OpenJDK, use OpenJDK 1.8. |
|
Back to top |
|
Bahena Brekeke Newbie
Joined: 21 Nov 2018 Posts: 1
|
Posted: Thu Nov 22, 2018 4:25 am Post subject: |
|
|
Tata wrote: |
There are several recommended rangefinders for hunting and checkpoints.
- Have you put the JDBC driver file under Tomcat's lib folder?
- It seems you are using jTDS's JDBC driver.
Does it compatible with your MS SQL Server's version?
- Does it compatible with the Java 1.6?
I think Java 1.6 is too old to use recent JDBC drivers...
|
Having a very similar if not the same issue. How do we make sure that the JDBC driver is compatible with our MS SQL Server's version, Tata? Is there a list I can check somewhere on what's compatible with what?
Last edited by Bahena on Fri Jan 12, 2024 4:53 am; edited 2 times in total |
|
Back to top |
|
Tata Brekeke Master Guru
Joined: 27 Jan 2008 Posts: 223
|
Posted: Mon Nov 26, 2018 1:15 pm Post subject: |
|
|
Bahena, are you using jTDSs JDBC driver instead of Microsoft's official JDBC driver?
The jTDSs's web site said..
Quote: |
jTDS is an open source 100% pure Java (type 4) JDBC 3.0 driver for Microsoft SQL Server (6.5, 7, 2000, 2005, 2008 and 2012) |
So it will not be compatible with newer version of MS SQL Server such as 2017.
For avoiding an issue, I can recommend that you udde MS's official JDBC driver. |
|
Back to top |
|
|