Envox Developer Blog

A critical error occurred on the Envox Syntellect system, resulting in the denial of any calls trying to reach our service number. This error has already happened before, but had been de-prioritized due to the license error. Unfortnately, it pops up again. Our partner Bressner has been informed.

BTW, the HMP error mentioned in this section is a SIP Re-Registration error of the underlying Dialogic HMP system. The first registration succeeds, and any subsequent registrations do so as well (every 100 seconds), but for some yet unknown reason one re-registration fails resulting in a complete outage of the service number. Not good. We need to fix it.

Bressner and Syntellect replied immediately after receiving our error message. They have sent us a new Envox sample code which will supposedly fix the fax T.38 issue we have. I am eager to test it on our system!

Trying to complete all the open issues. Now fax is again on the table.

We got a script file .ens from envox syntellect support for the problem. This problem poped up last year sometime during the developpling process in October.

Maschine still says:

2010-02-16 21:07:03 Ch =     1  ErrCode =   50
Descr = (Failed) Could not enable some of the features!
Block = ringring2010_v9:Main:\FaxDetection\EnableFeature
Script= ringring2010_v9 [02B3DB0E]

Waiting now again for an answer from envox syntellect.

by the way the Bressner technology guys are really trying to get fast answers and solutions! That is good!

Turning on the report option causes an critical error „Reporting not initialized! Check license and configuration!“.

One thing is pretty sure: at least we have paid for the reporting …

… waiting for a new license file and/or a solution for our problem

There have been no operational issues with Envox after the guys at Syntellect brought in the last hot fix on Tue 2010/02/02.

It seems like they’ve eventually solved the issue.

The guys at Syntellect have installed a hot fix.

Let’s see, whether this will fix the repetitive license error.

Envox has to be restarted. Unknown reason…

Support from envox could not fix the problem. We had to restart the server again. Maybe we should choose another system…