Recording application crashes when 16 or more extensions are in BCA and logged in.

[avc877669026754]

We have a recording application that runs on an application server and connects to the PBX via the TSAPI using SSC in combination with a DMCC port.

One of our customers has 16 or more extensions configured in a BCA.

The issue at hand:

Scenario 1:
15 or less extensions are logged in - When an incoming call lands on one of the extensions and the call is answered, the recording application records the entire conversation and processes all the incoming events.

Scenario 2:
16 or more extensions are logged in - When an incoming call lands on one of the extensikons and the call is answered, the recording application gets the call start event and crashes.

On analyzing further, we found that in Scenario 2, we do not seem to get a few events before the call start, which we get in Scenario 1.

Has anyone faced a this or a similar issue? If yes, please let me know how this was fixed.

[avc877669026754]

Another observation is that the crash almost always happens after the "OnHookSwitchUpdatedEvent" event handler is called. Could this be possible in the ServiceProvider dll?

[flynn1]

You say you are using TSAPI and DMCC. I presume you are not using the TSAPI and DMCC clients in the same executable. Therefore, I presume you have two executables. Which is crashing? Do you not get a core dump or exception to indicate which piece of code crashed?

[avc878171728818]

It sounds like you're dealing with a challenging issue related to the TSAPI connection and DMCC port usage in your recording application. Here are some potential avenues to explore based on the scenarios you've described:

• Check Resource Limits:
  • Verify TSAPI and DMCC license limits for simultaneous connections.
• Event Handling:
  • Ensure your application can efficiently process the volume of events.
  • Implement detailed logging to capture exceptions during event handling.
• Application Configuration:
  • Review thread management for handling concurrent connections.
  • Enhance error handling to prevent crashes.
• Version Compatibility:
  • Ensure all software versions (PBX, TSAPI, DMCC) are compatible and up to date.
• Testing and Simulation:
  • Conduct load testing to replicate the issue.
  • Isolate components to test specific event handling under load.
• Contact Support:
  • If issues persist, reach out to Avaya support for further assistance.

Hope this useful!

[avc877669026754]

You say you are using TSAPI and DMCC. I presume you are not using the TSAPI and DMCC clients in the same executable. Therefore, I presume you have two executables. Which is crashing? Do you not get a core dump or exception to indicate which piece of code crashed?

I use the TSAPI and DMCC clients in the same executable. I see the crash in the executable but the actual reason seems to be some where else. I suspect it might be the ServiceProvider dll we use. This comes with the Avaya TSAPI sample code.

[avc877669026754]

It sounds like you're dealing with a challenging issue related to the TSAPI connection and DMCC port usage in your recording application. Here are some potential avenues to explore based on the scenarios you've described:

• Check Resource Limits:
  • Verify TSAPI and DMCC license limits for simultaneous connections.
• Event Handling:
  • Ensure your application can efficiently process the volume of events.
  • Implement detailed logging to capture exceptions during event handling.
• Application Configuration:
  • Review thread management for handling concurrent connections.
  • Enhance error handling to prevent crashes.
• Version Compatibility:
  • Ensure all software versions (PBX, TSAPI, DMCC) are compatible and up to date.
• Testing and Simulation:
  • Conduct load testing to replicate the issue.
  • Isolate components to test specific event handling under load.
• Contact Support:
  • If issues persist, reach out to Avaya support for further assistance.

Hope this useful!

Thank you for your suggestions. I will look at those during this week and go accordingly.

[flynn1]

ServiceProvider dll does NOT come with the Avaya TSAPI sample code. They are very different things and are not designed to be used together.