![]() Secure audio and video transfer is now possible in all systems. Improvement (SRTP): The SRTP audio and video stream did not work in all environments.Asterisk and many other SIP PBX systems support this event. This event is sent by the PBX to the softphone in case the call is redirected. New feature (OnForwarded): This new event was added to the softphone to make it possible to handle SIP 181 redirect events.The addresses of the instant messages were not set properly. Improvement (SIP Messaging): The SIP/VoIP Instant messaging features has been improved.It did not parse the target field properly in all cases. Bug fix (Blind transfer): The blind transfer had a bug.This enables you to work with dinamically attached and removed devices more efficiently. In this version, the Ozeki library will allow you to query the plugged in device list unlimited times in a thread safe mode. Improvement (Audio and video device detection): To detect new audio/video devices plugged into the system you can use the built in functions of Windows.Note, that these functions are based on weak references, so it is not a problem if a developer forgets to call the dispose method. These managed functions make sure, that the speaker will be started/stoped/disposed only after all threads have completed their operations. These procedure make access to these devices thread safe, and ensures that multiple threads can use them without issues. New feature (StartManaged/StopManaged): If multiple threads want to access the physical audio/video devices in the system (for example the speaker), they should use the StartManaged/StopManaged and DisposeManaged procedures instead of Start/Stop/Dispose.New feature (sha 256): The SHA256 authentication algorithm is now supported.The update was necessary to support several projects and to resolve some conflicts that arose under Visual Studio 2022 NET Framework requirement of Ozeki SDK to. Update (.NET Framework): We have updated the minimum.This error was related to the introduction of new hashing algorithms to support better security. This resulted in an INVITE TIMEOUT error messages. Bug fix (INVITE TIMEOUT): On some systems the SIP INVITE message response parsing was invalid.So if you have two or more users accessing the same media devices swich to StartManaged/StopManaged/DisposeManaged to get better functionality. If you use these new methods, the two users will not effect each other. In this new version we have introduced new methods: StartManaged/StopManaged/DisposeManaged. If John starts the Microphone and Bob stops it, the microphone will stop at John as well. John and Bob) use the same hardware, their activity interact: for example John may start and Bob may stop the device. Improvement (Better device management): When you request access to a media device, such as a Speaker or Microphone, the same (single) instance of the device class is returned, because the same hardware device is accessed. ![]() This resulted in a CommonDependencyResolver exception. Bug fix (Common Dependency Resolver): When the SDK dll was installed in the Windows Global Assembly Cache, the applications based on it have loaded the dll twice.
0 Comments
Leave a Reply. |