Download

You can download the latest version of Ozeki Camera Recorder by clicking on the link below. After download, you need to unzip it and run the installer in the zip package.

 OzekiCameraRecorder_10.4.18.zip 65.65MB 

1. New feature (SMS alerts): SMS network connections can be monitored and SMS messages can be sent when the monitored connection goes down
2. New feature (E-mail alerts): SMS network connections can be monitored and E-mail messages can be sent when the monitored connection goes down
3. New feature (WhatsApp alerts): SMS network connections can be monitored and WhatsApp messages can be sent when the monitored connection goes down

1. Improvement (SMPP): SMPP pdu encoding is imporoved
2. Improvement (Task scheduler): The task scheduler app in the system is improved and some bugs in it were fixed

1. New feature (Delivery report matching): The a new form was added to the server preferences, that allow you to configure the delivery report matching policy. This allows you to select the appropriate delivery report storage architecture for your environment. Standard lists, B-Tree, Non-cached file storage can be selected.
2. Improvement (Memory consumption): The memory consumption of the software is optimized to work with lower memory requirement.

1. New feature (Text to speech): The SMS Gateway can read out SMS messages on the PC speaker.
2. New feature (Play sound): The SMS Gateway can play a beep sound on the PC speaker if an SMS messages is sent or received (depending on configuration).
3. New feature (Play audio file): The SMS Gateway can play an audio file (e.g.: mp3, wav, etc) on the PC speaker if an SMS messages is sent or received.
4. Improvement (SMS delivery report matching): The SMS delivery report matching engine has been improved

1. Improvement (Boot time): The startup sequence was improved to offer faster load times
2. Improvement (Bulk messenger): The Bulk messenger has been improved to allow simultaneus job execution
3. Improvement (Bind limits): The number of allowed simultatnous TCP/IP links per user can be limited on SMPP connections. This feature is useful for SMPP service providers
4. Improvement (SMS connecttions): The type selection for SMS connections became better. New SMS service providers were added and the presentation of them was improved to find the appropriate SMS connection type easier.

1. New feature (Android SMS Logging): The communication with the Android SMS client is now logged fully. This allows better system management.
2. Improvement (REST): The segmentation and reassembly (SAR) protocol layer was removed from the REST SMS clients. This layer was never used, since these SMS service providers perform this functionlity.
3. Improvement (MADAPI): Small improvements and optimizations were done on the MADAPI SMS client

1. New feature (HTTP API): The HTTP API response can be configured to include the DTD header.
2. Improvement (Security): Some security updates have been implemented.
3. Improvement (Android): Commincation with the Android SMS client became more efficient.
4. Bug fix (VoIP): The VoIP instant messaging was not working properly on all devices. This poblem has been fixed.

1. Improvement (SMPP/Security): The TLS version can be configured for this connection type.
2. Improvement (UCP/Security): The TLS version can be configured for this connection type.
3. Improvement (CIMD2/Security): The TLS version can be configured for this connection type.

1. New feature (Mozeki.com): The Ozeki account is now integrated with myozeki.com
2. Improvement (Cluster): The custom connection string configuration data is preserved during cluster takeovers and server restarts

1. Improvement (Database reporting): The database reporting feature has been improved to provide longer timeouts for slow database connections
2. Improvement (Oracle): The database messaging feature has been improved to allow automatic database connection reestablishment in case of broken database links. This is especially important for Oracle databases.

1. Improvement (Chat protocol): A new chat protocol was introduced in this version. This protocol uses JSON/HTTP REST requests to communicate with the chat server, and can be supported by web based apis and mobile clients

1. New feature (Message scheduler): A new app is added to the system, that allows you to setup scheduled messages. You can define a calendor of holidays, business days/etc, and use working hours, and period events to setup your scheduled messaging jobs
2. Improvement (Log system): New connections are logging to the correct locations. Log files are removed after connection uninstallation. Several bugs and performance enhancements have been done in the logging system
3. Improvement (Chat system): The chat subsystem is improved to offer JSON/REST API access

1. Bug fix (Character encoding): A character encoding issue was fixed. It was effecting unicode characters on SMPP links

1. Improvement (Installer): The installer package has been improved

1. Improvement (HTTP API): The HTTP API performance has been improved and several bugs were fixed
2. Improvement (P2P): The P2P messaging capabilities were improved

1. Improvement (GUI): The graphical user interface was improved to provide better response times.
2. Improvement (SQL SMS): The SQL console of the SQL to SMS connection is improved to track configuration changes in the database connections

1. Improvement (GUI): The graphical user interface was improved to provide better response times.
2. Improvement (SQL SMS): The SQL console of the SQL to SMS connection is improved to track configuration changes in the database connections

1. Improvement (SMS Database): The database messaging feature has been improved. The sender and recipient phone numbers of SMS messages are stripped from special characters. For example phone numbers in the form +441234567@% are now inserted as +441234567.
2. Improvement (SMS Database): Four new keywords can bed used in the SQL templates for both incoming and outgoing SMS messages: $fromconnection, $fromaddress, $toconnection and $toaddress. For example in SMS messaging the $fromconnection and $twoconnection contains the names of the SMS service providers used to send and receive the SMS. The $fromaddress and $toaddress contain the sender and recipient phone numbers. This new feature can be used to have more information about each message.
3. Improvement (Cache): The client side caching of JavaScripts serving the graphical user interface (GUI), has often led to problems. This cache mechanism is improved, to make sure, that always the latest Javascripts are used in the browsers.

1. Improvement (Security updates): A major security review of the system was performed, and several features were updated to provide better security.
2. Improvement (Http connections): The HTTP client connections were improved. Now all SSL/Tls versions are supported and negoiated properly, and the SSL client and SSL server servtificate verification is customizable
3. Bug fix (Smaller bugs): Several smaller bugs related to SMS forwarding are fixed.

1. Improvement (Parallel call performance): Simiulatneious VoIP calls are handled more efficiently

1. Improvement (Oracle): The Oracle database capability was improved to handle columns with large data sizes.

1. New feature (SMPP): The address range parameter of SMPP bind requests can be adjusted independently of the primary phone number of the connection
2. New feature (Autoreply): Messages going through the autoreply look can now ask for delivery reports
3. Improvement (Security): Security updates were implemented.

1. Improvement (SSL certificates): The SSL certificates have been updated, because of expired dates
2. Improvement (GUI components): The performance of some GUI elements were improved
3. Bug fix (Minor bugfixes): Several smaller bugs were fixed

1. New feature (Text to speech): The robot developer app got text to speech capabilities
2. New feature (Safe logging): You can configure the system to hide phone numbers and message text in the logs.
3. Improvement (Uninstall button): The uninstall button was removed in the sms messenger app for standard users.
4. Improvement (Android): The SSL key management on Android phones are improved
5. Improvement (Android): Unnecessary permission requests are removed on Android
6. Improvement (Database messaging): The sms from database feature is improved. The logging is better.
7. Improvement (Service list): The advanced/services form of the SMS gateway displays more information now.
8. Bug fix (Database messaging): Periodic folder cleanup did not work for SQL messaging. It is fixed.
9. Bug fix (Http user): Periodic folder cleanup did not work for the HTTP user. It is fixed.
10. Bug fix (Http user): The XML response could not handle XML specific characters, such as tags and quotes. It is working now.
11. Bug fix (Browser cache): On mac laptops, the browser cache management had a problem, that needed a workaround. Some user pages were loaded from cache instead of the sms software.

1. Improvement (Compatibility): This version has several compatibility improvements with older Ozeki versions
2. Bug fix (Datbase ID): A bug was fixed in the SQL reporting related to database IDs

1. Bug fix (Vresion compatibility): The previous version had a compatibility issue with older versions. This is fixed.

1. New feature (HTTP REST API / message download): The json based http rest api got a new command, that allows you to download sms messages from the inbox of a particular user
2. New feature (HTTP REST API / message delete): The json based http rest api got a new command, that allows you to delete sms messages from the inbox of a particular user

1. New feature (Ozeki REST API): The SMS subsystem was extended with a new HTTP API. This API allows you to send SMS messages with JSON encoded HTTP post requests. The old HTTP API is still in place, and we have no plans to discard it. Both APIs, the HTTP GET/xml based API and the HTTP POST/Json API will be supported long term
2. New feature (HLR lookups): The SMS gateway can be configured to do HLR lookups for each SMS before it is sent. The HLR information can be used in routing and can be stored in the reporting database. More information is available in the how to do HLR lookups guide/li>
3. Improvement (Logging): Some unneccessary log messages have been removed.
4. Improvement (HTTP SMS API server side): Ozeki SMS Gateway is now able to accept HTTP requests in formats for various SMS service providers. If you are not happy with your current SMS service provider, and you wish to switch to Ozeki, you can do that without having to rewrite your code.You simply have to point to your Ozeki SMS Gateway HTTP API url. You can switch from Twilio, Infobip, Clicksend, Clickatell, Messagebird, Sinch, Telnyx, Vonage to Ozeki with ease.
5. Bug fix (Memory leak): A memory leak has been fixed.

1. New feature (HTTP Rest client): A customizable HTTP REST sms api connection is added. To support custom JSON and native HTTP SMS client connections
2. New feature (Sinch): A new sms service provider connection was added to allow direct connection to Sinch
3. New feature (Clickatel): A new sms service provider connection was added to allow direct connection to Clickatel
4. New feature (Vonage): A new sms service provider connection was added to allow direct connection to Vonage
5. New feature (Infobip): A new sms service provider connection was added to allow direct connection to Infobip
6. New feature (Clicksend): A new sms service provider connection was added to allow direct connection to Infobip
7. Improvement (Email to sms): The email to sms and sms to email features are improved, to support SMS addresses in the email subject line
8. Improvement (Android SMS): The android permission settings are improved. The software runs with a smaller number of permissions.
9. Bug fix (C# formula modifier): You can modify SMS messages with a C# algorithm. The C# algorithm can be added to a route in the routing table.
10. Bug fix (SMS encryption): You can encrypt/decrypt sms messages with a pre shared key in the routing table. This feature had a bug, that is fixed.
11. Bug fix (Android file manager): The Ozeki file manager on Android was not working properly. It is fixed.

1. Improvement (E-mail to SMS): Goggle mail support is improved
2. Improvement (Text file user): The text file to sms feature did not request delivery report by default. This is fixed.
3. Bug fix (GSM modem): The deliery report handling in the GSM modem had a bug, that was fixed.

1. New feature (HTTP REST API client): A new connection is created to send messages over HTTP REST API services. This connection can encode a message in JSON according to various specifiations. It makes it possible to post SMS messages as JSON requests to almost any HTTP REST API SMS service. User authentication (api keys, usernames, passwords, etc) can be included as JSON variables, or they can be put into the HTTP request header. This in excellent implementation.
2. New feature (HTTP REST API service): You can provide an HTTP REST API sms service to your users. The HTTP API of Ozeki 10 SMS gateway way improved to accept REST API requests. The users can encode their messages in JSON and post it to the built in Ozeki HTTP server. The Ozeki HTTP REST API is compatible with the request format of many SMS service providers, so switching to Ozeki from an existing service is very easy.
3. New feature (Twillio client): A new service provider connection was added to make it easy to connect to the Twillio SMS service
4. New feature (Telnyx client): A new service provider connection was added to make it easy to connect to the Telnyx SMS service
5. Bug fix (GSM modem): The GSM modem could not receive multipart SMS messags properly due to an error. This bug is fixed.
6. Bug fix (Android version): The logging on the SMS connections in the Android SMS Gateway was improved.
7. Bug fix (POP3): The POP3 client and server was reviewed and some bugs were fixed. A disconnect/reconnect issue that was due to special characters in the username was fixed.

1. New feature (Credit limits): A new feature was added, that allows you to set one time or daily, weekly, fortnightly or monthly credit limits for connections
2. Improvement (HTTP API): The HTTP API was reviewed and several bugs were fixed
3. Improvement (Android release): Tha android version has been improved.

1. Improvement (Android): Overall iomprovements and bugfixes in the Android version

1. New feature (Android): The first version of Ozeki 10 SMS Gateway for Android is released
2. Improvement (HTTP API): The HTTP API evaluates URL templates better

1. Improvement (HTTP API): The HTTP API compatibilitiy with previous versions have been improved
2. Bug fix (Database reporting): The database reporting details page did not work properly. This bug is fixed.

1. New feature (Android): The Ozeki SMS Gateway is now available for Android phones. It supports dual sim devices as well.
2. Improvement (SMS): The delivery report matching has been improved.
3. Improvement (Composer): The message composer form remembers the last phone number
4. Bug fix (Message validity): The message validity period takes into account the scheduled date
5. Bug fix (HTTP API): If multiple messages were sent on the HTTP API, the XML response was invalid. This is fixed.
6. Compatibility (HTTP API): The HTTP API was improved to make it compatible with Ozeki NG SMS Gateway

1. New feature (Uninstall button): Uninstall buttons were added to the connections, to make uninstallation easier
2. Improvement (GUI): The MPM label is improved to provide accurate measurement for slow connections.
3. Improvement (Ozeki Account): The Ozeki Account security has been improved
4. Improvement (SMPP): The submit reference matching is improved. Delviery reports are metched with upper, lower and mixed case submit reference strings.
5. Improvement (SQL persistence): The sql query evaluation is improved to provide more protection from SQL injection threats.
6. Bug fix (Addrebook): The address book import feature had a bug, that prevented phone numbers being imported. This bug is fixed.
7. Bug fix (GUI): The browsre cache prevented the update of the configuration form in some cases. A workaround was put in place to handle this issue

1. Bug fix (SMS): The configuration forms did not preserve some values. This bug is fixed.
2. Bug fix (Chat): A bug could cause a message loop. This bug is fixed.

1. New feature (Context menu): The context menu was improved, to support file open with the right click
2. Improvement (Addressing): There was an inconsistency in the addressing scheme. In a message therere are 3 types of addresses: station ID, connection ID, address. The station ID referes to the computer where the messages is coming from. The connection ID contains the name of the connection, for example SMPPlink1, the address contains the actual address, eg. +36123467. The inconsistency happened when the address field was empty. In this case, in some parts of the code the connection ID was inserted in place of the address, in other situations it was left empty. This inconsistency is resolved. The connection ID is NOT inserted into the address fieled if it is left empty. If you did not configure a default address for a connection (e.g. a default phone number in the SMPP link), make sure you have one configured now.
3. Bug fix (Route link): The route name link did not work properly. It pointed to an invalid URL. It is fixed.

1. New feature (Chat server): The chat server has been improved. The store and forward capability is much faster now.

1. Improvement (Chat): The chat client has been improved to support forms and HTML content.

1. New feature (SMTP server): The built in SMTP server now support SSL. Two methods can be used: STARTTLS and SSL / TLS.
2. New feature (SMTP server): A new authentication method was added to the SMTP server. It can authenticate clients with a username present in the E-mail header. A special e-mail header field was introduced called x-ozeki-auth. And username and password can be provided in the following format: x-ozeki-auth: user; password
3. Improvement (IMAP server): Microsoft Outlook support is added to the built in IMAP server. Outlook uses some non-standard parameters which are now supported in Ozeki
4. Bug fix (Chat): The chat client displayed duplicate messages on some slow systems. This bug is fixed.

1. New feature (SQL reporting): SQL reporting used by SMS service providers is improved. A new tabpage was added to the SQL console (check the bottom), that allows manual modification of SQL templates used for querying the database.
2. Improvement (Licensing): The product activation system removes trial license codes automaticall if active codes are enterd
3. Improvement (Keepalive): The keepalive algorithm now monitors network traffic. It will only send out keepalive requests if there is no traffic for a configured amount of time on the link. This improves connection speeds on high capacity IP SMS links, because no keepalive traffic is generated under heavy loads.
4. Improvement (SMS submit timeout): The submit timeout value of IP SMS connections have been increased from 10 seconds to 25 seconds. The change was applied to support providers accessed through very slow connections and to support providers who provide a slow service.
5. Bug fix (Reporting database): The reporting database configuration form did not allow the password to be changed. If you have updated the password, it still tried to connect with the old. This bug is fixed.
6. Bug fix (SMS outbox): In some routing configurations SMS messages could get stuck in the outbox of users. This bug is fixed.

1. New feature (Access): Microsoft Access support is added to make it easy to send/receive chat messages and sms messages from Access database tables.
2. New feature (Excel): The HTTP API was improved to support Microsoft Excel. Now Micrsoft Excel can be used to send chat messages and sms messages. This feature is loved by office users, because they like to create excel spreadsheats with a list of phone numbers and messages texts. Now they can send message directly from Excel with the click of a button.
3. Improvement (SMPP client): The delivery report matching feature of the SMPP client has been improved. In case the SMPP service provider returns the submit reference in lower case hex digits, and after this it returns the delivery report reference as an integer, the delivery report will be matched. (In the previous version we expected upper case hex representation. This version handles both: upper case and lower case)
4. Improvement (Chat GUI): The chat GUI had some cosmetic improvements to make it look nicer
5. Compatiblity (HTTP API): The compatibility of the HTTP API is improved to support HTTP clients developed to operate with Ozeki NG SMS Gateway.

1. New feature (Logs): Daily log rotation is introduced to save disk space
2. New feature (SQL to chat): Chat messages can be sent from SQL databases
3. New feature (HTTP to chat): Chat messages can be sent using HTTP requests
4. Improvement (Logs): The log file names are updated to make them free of spaces and special characters
5. Improvement (Control panel): The help section of the control panel app is improved

1. New feature (Logs): Daily log rotation is introduced to save disk space
2. New feature (SQL to chat): Chat messages can be sent from SQL databases
3. New feature (HTTP to chat): Chat messages can be sent using HTTP requests
4. Improvement (Logs): The log file names are updated to make them free of spaces and special characters
5. Improvement (Control panel): The help section of the control panel app is improved

1. Improvement (P2Pl): The P2P network connection setup is improvied
2. Improvement (Routing): The advanced page of the routing match conditions did not make it possible to install new custom conditions. This issue is resolved. Now you can install and configure custom matching conditions
3. Bug fix (Routing GUI): The text matching routing rule GUI did not provide correct examples for matching patterns. The examples are corrected.
4. Bug fix (UCP connection GUI): The GUI had two configuration tabs. Now there is only one.

1. Improvement (P2P stack): The link setup between chat clients and the server discovery was improved.

1. New feature (Installer): A new dialog window is created to help you follow the progress of the installation from the app store
2. Improvement (Installer): The ozeki store / installer feature now downloads all components before it starts the installation. The previous version did the two steps simultaneously, which could lead to errors in case of instable network environments.
3. Improvement (P2P): The chat network link setup functionality is improved.
4. Improvement (P2P): The chat server is improved. It allows simultaneous connections from multiple (e.g.: LAN and WAN ip-s).
5. Improvement (Keepalive): The keepalive/automatic reconnect functionality is more intelligent in messaging connections, such as SMPP
6. Bug fix (SMTP): The built in E-mail server (SMTP) had a bug, that prevented it to accept some e-mails. This bug is fixed.
7. Bug fix (SMPP): The password box of the SMPP client did not work porperly. It is fixed.

1. Improvement (Security): The login form security is improved
2. Improvement (Security): Remote chat clients are not allowed to commicate with local connections unless explicit permission is granted
3. Improvement (Security): Chat users are only allowed to login on the local computer
4. Improvement (Security): Friendships are not established automatically in the chat client
5. Improvement (Security): Tunnels used for voice calls are not enabled by default
6. Improvement (Ozeki account): The Ozeki Account app allows you to edit your security details, such as login e-mail, password, etc.
7. Improvement (UDP): The UDP link management for all services based on UDP/IP is improved
8. Bug fix (Keepalive): The automatic reconnect of lost network connections feature had a bug, that prevented the reconnection in some cases
9. Bug fix (Imap): The Imap client had a bug, that is fixed.
10. Bug fix (Database): The SQL query building had a bug, that is fixed. This prevented some SMS messages to be saved into the database. (Happened very rarely, but it had to be fixed)

1. New feature (Unified version numbers): The version numbers are synchronized accross Ozeki products, to help compatibility when multiple products are installed on the same computer. This is why you see a big jump in the versioning of some products.
2. New feature (IMAP): We have implemented the IMAP client protocol. Now you can connect your system to e-mail servers through IMAP (both plain and SSL connections are supported). This allows you to create great e-mail gateway setups, such ash e-mail to chat or e-mail to SMS.
3. New feature (SMS to Chat): If you install the Ozeki Chat server and the Ozeki SMS Gateway apps, you can chat with mobile phones in SMS. This gives the same experience you would get in a standard chat application.
4. New feature (Email to Chat): If you install the Ozeki Chat server and the configure an IMAP or POP3 client connection, you can chat with e-mail contacts, as you would chat in a standard chat application
5. Improvement (Chat): The chat transport now supports both UDP and TCP connections
6. Bug fix (HTTP API): The HTTP API did not work because of an obfuscation error. This bug is fixed.

1. Bug fix (Friendship delete): If a P2P friendship was deleted, the information was not transfered to all clients. This bug is fixed.
2. Bug fix (File transfer): The P2P file transfer for encrypted connections had a bug, that is fixed now.

1. New feature (SMPP user): On the SMPP user s config form, in the Advanced tab page in the delivery report group box you can select Hex formatted submit reporting. If you enable this option, the SMS submit reports returned to incoming SMS messages to your SMPP customers, will be in Hex format. Note that the delivery reports will contain the format as Integer numbers.
2. Improvement (Delivery reports): Some SMPP providers return the submit reference in Hex format and the reference in the delivery report is sent by them in int format. Our previous SMS gateway, Ozeki NG SMS Gateway were able to handle this setup, it could match delivery reports in this case. This functionality was added to the SMPP client connections in Ozeki 10. If you use SMPP SMS connections in this product, and you experienced problems with delivery reports, this fix will solve the problem.
3. Improvement (Password form): The appearance of the password change form is improved
4. Bug fix (Memory leak): Another memory leak was discovered, that could impact long term operations. This is fixed.

1. New feature (Automatic updates): Automatic updates are available from this version on.
2. New feature (Chat): If P2P communication is used availabilty of remote parties are handled more efficiently
3. Improvement (Logging): The overall quality of log entries have been improved. Several meaningless leg entries were removed from the logging system.
4. Improvement (Text to speech): The text to speech capability is improved. Now individual browsers and browser tab pages can be address to read out text.
5. Improvement (Database reporting): The reporting system (e.g. reporting database) is not recording suplementary messages.
6. Bug fix (Memory): A memory leak was discovered. It is fixed.
7. Bug fix (Stability): An unexpected exception could occur during heavy network, that could cause the Ozeki service to stop unexpectedly. This bug is fixed.
8. Bug fix (GUI): In cases of parallel GUI access some GUI components were duplicated on the screen. This bug is fixed.

1. New feature (Installer): The Ozeki installer that allows easy updates are included in this package.
2. New feature (P2P): The P2P file exchange feature is improved.
3. Bug fix (Stability): The service could stop unexpectedly in previous version. This bug is fixed.

1. Improvement (Diagnostic): The system has been moved to different product to save resources.
2. Bug fix: (Memory leek bug has been fixed.)
3. Bug fix: (The messages could get stuck in the outbox folder. This bug is fixed.)
4. Bug fix: (User interface bugs has been fixed.)

1. Improvement (The throughput performance is improved.)

1. New feature (MS SQL Fast): A new reporting module is added, called MS SQL Fast. This module supports database reporting for high capacity systems. It is using MS SQL. It uses a more compact database layout, with short column names, and shorter datatypes. It also relies on a smaller number of queries than our tradition SQL reporting engine.
2. Improvement (Performance): The overall throughput performance is improved.
3. Improvement (Reporting): The report management is much faster.

1. Improvement (Camera compatibility): More IP cameras are supported in this version.

1. Bug fix (Memory leak): The system had a memory leak for some IP cameras. This bug is fixed.

1. New feature (SMS alerts): You can send SMS alerts when motion is detected, or if any other computer vision event occurs.
2. New feature (E-mail alerts): You can send E-mail alerts when motion is detected, or if any other computer vision event occurs.
3. Improvement (Http alerts): You can send HTTP alerts when motion is detected, or if any other computer vision event occurs.

1. Ozeki Camera Recorder is a great product that allows you to view and record camera streams of IP cameras, USB cameras and remote video streams in real time. You may also use Onvif features, if your camera support Pan-Tilt-Zoom (PTZ), you have access to those features as well. The configuration is great, you can flip the camera image horizontally or vertically and you may setup various image processing functionality, such as motion detection, face detetion, etc.
2. As the name suggests this camera app is designed for recording camera streams on a PC. You can schedule recording jobs or you can setup continuous recordings. You may also define event triggers, that will start recording events.