MiTAI events no longer provided for active monitors when MiTAI exception thrown, MiVB 8.0 SP2

[Megan G]

We have a third party call control system in place at many customer sites with no issues.

One customer site has a problem when multiple MiTAI monitors are active for more than about 1 hour. A single user/monitor can run all day without issue. We feel this suggests a resource issue.

The issue manifests for the users as no more MiTAI call events being provided FROM MiTAI. Call control requests TO MiTAI are still in passed successfully and MiTAI provides appropriate responses.

So, for instance, after the issue occurs, a new call might be delivered to a monitored device but no MiTAI event is provided to indicate a new call being delivered.

We note that an exception is seen in the MiTAI logs preceding each example of this issue:
2020/08/07 10:53:50, ERR , MiTAI exception in EventHandler Thread - MITEL Telephony Application Interface - Version 1.1.0.8 REMOTE.
Exception code: ACCESS_VIOLATION715)


We have the log and dmp files for the exception.

Is anyone familiar with exception or might anyone have a suggestion for root cause analysis?

MiVB version is 8.0 SP2
MiCC version is 9.3.0

 

[Valamagules]

Try this -

Check extensions in the MiCC and disable Real-time monitor on those that do not require them.
By default, MiCC enabled ALL extensions for Real-time, hence using up MiTai resource.
Once you have disabled Real-time, reboot both MiCC and MiVB.

Clever men learns what Wise men shares!

 

[Billz66]

or change Micc to maximum allowed for the platform

MiVB 7.0 SP1 and later MiTAI monitor limits
For hardware based MiVB the limit is 2000
For virtual MiVB the limit is 5600


If I never did anything I'd never done before , I'd never do anything.....