Need feedback on Ozeki (Voice Over IP) VoIP SIP SDK

I work for a small company, and my boss told me to look back at the market for SDKs for voice and video. I found one called the Ozeki VoIP SIP SDK.

As per the description on their website, this looks promising. If someone has already used this SDK, please share a few thoughts with me so that I can better inform my boss.

+4
source share
4 answers

I bought and tested the OZEKI VOIP SDK for several months, the development is simple, but there are serious problems with this SDK:

1- This is unreliable and after several hours of operation, the processor goes 100%, or memory corruption occurs. 2- No relevant documentation. 3- There are many patterns, but incomplete and almost the same. 4- Support is not very good and sometimes there is no answer.

I recommend VaxTele www.vaxvoip.com , which is more reliable and has good support.

+2
source

Update : after working with the Ozeki VoIP SDK for almost a year, I would like to change:

  • we found a few questions that Ozeki usually voiced over the course of several weeks.
  • The default value for the Audio-API is known to cause poor sound quality.
  • changing the Audio API can cause the speakers to not produce sound at all.
    • in our case, this is a 100% reproducible problem, but Ozeki did not want and could not fix it for 6 months ( read more ).

To summarize, I would currently strongly advise against buying / using the Ozeki VoIP SDK .

Original post:

My two cents (currently I am evaluating several VoIP libraries):

  • wise function seems quite complete
  • There is quite a lot of online documentation on how VoIP works, and that’s great.
  • their mail server was down when I tried to send an email twice. It seems to be working again.
  • The API is not very good with clear / clean code. Here is what I wrote down for our internal review documentation:
    • The API document is mostly generated automatically and contains some, but not very useful information.
    • At least there are many examples (online), unfortunately, many of them are incomplete. In addition, doc sometimes requires quite a bit of API know-how. This know-how is not mentioned. For example, see http://voip-sip-sdk.com/p_379-voip-peer-to-peer-call-voip.html - it is not complete regarding how to set up a call and how to create some of the necessary objects (code does not compile!).
    • on IPhoneCall , you can call .Start() twice, there is no exception, that is always the case. The same goes for .HangUp() . You cannot reuse the IPhoneCall object to place another call.
    • The API is not very pleasant regarding async / long running tasks. In the case of a phone call, a state change event occurs, but if the call cannot fail, it is not possible to automatically generate an exception or the like (p.Ex. await phone.Call(); not supported out of the box)
+1
source

If you are looking for an easy way to develop VoIP SIP applications, then Ozeki is the best for you. The code is pretty well documented and displays a large number of samples, but if you want to start from scratch, you better start looking for another SDK. Here you have it.

0
source

I have been using the Ozeki VoIP SIP SDK for about 3 months, I am using this sdk to develop a simple automatic dialer and speech application in a text application.

I started using version 10.1.1, it supports all functions, and after so many studies I successfully got a speech in a text application.

But they release a new version every one or half a month once.

Now they have released 10.1.5, they said that they improved the speech in the text engine, and you can customize the speech engine. but there is no relevant documentation for a newer version.

But I changed my old code with a newer version of the SDK, but did not understand it correctly. Old version 10.1.1 and later.

http://www.voip-sip-sdk.com/p_21-download-ozeki-voip-sip-sdk-voip.html

0
source

All Articles