Hi John,

The application will get the button list and press a button. Are you saying that we shouldn't have a problem if there are already potentially 3 other DMCC connections for that phone eg OneX & Dual recorders?

I was thinking there would be a problem with instances, when we call getDeviceId with Instance=0 on two DMCC Dashboard test tools, the second one fails with resource busy.

On a system with dual recording, the 3 instances we can use for controlling devices can be consumed by the dual recorders and a OneX softphone, this leaves no ability to connect an application as 3 is the limit.

Is there any way around this, or any plans to change this limit?

Hi is there any way a DMCC application could register with a terminal without providing the station password?

I had this, the structure that stored the cross reference is incorrectly using a signed long

Firstly apologies if this is the wrong forum, I couldn't find an appropriate one.

We ceased support for IP Office with our product back at version 3.1 of IP Office. I am looking into what's changed in that time.

I remember there were a few issues that caused problems:

1. Limit of 500 devices accessible to TAPI (you couldn't determine which ones)
2. If the database was altered eg a device/group removed the list TAPI used updated but our application had no way of knowing so you have a lineOpen on extension 2005, lets say someone deletes extension 2001 and our line could now actually be controlling 2004.

I have read through the release notes for IP Office and cannot find this level of detail or anything concerning TAPI.

Can you answer my questions or direct me to the answers?

Regards
Stewart Ponsford

Hi is the Breeze Snap store available in the uk?

I think there is something going a bit wrong in the aes as the response time to answer call seems to climb to 9 seconds then this happens.

I will push them to investigate the health of the AES and in the meantime I will make sure our product copes with this error.

Thanks

Hi,

On one of our sites we have started getting the above in response to a make predictive call, NO_ACTIVE_CALL is not listed as an error code to expect from this api call. Can you tell me what this error code could mean in relation to make predictive call?

The version 7 Client says it supports AES 6.3.x and 5.2.x, so I take it no support for 6.1,6.2?

Hi John,

Our product is handling outbound predictive and inbound routing. The outbound side isn't checking the value and just routing and there are no problems there. The inbound part has a check on the value being >0 so isn't routing inbound calls.

All the cross ref IDs on the site at the moment are negative and it seems to me that the numbers are incrementing as if they are treated as unsigned long. The tsapi structure has the value declared as a long but I am assuming it is actually treated as an unsigned long. It is a simple fix for me to handle this at our end I just wanted to be sure this is a valid situation.

I noticed on one of our customer sites that we received some CSTARouteRequestExtEvent with a routingCrossRefID that was less than zero, we handle this value in a long variable so it is signed, the routerequest structure also uses a long.

Can you confirm that a negative value is valid as I can't find an answer to this in the documentation?

Cheers
Stew

I got log4net working on my test system but I had to make a small change to code. I will push to get this build on site as I think it would get us to the root of the problem.

I'm not familiar with log4net, but if you can get me some details on how I could set it up I will see what I can do.

Not encountered any issues with my testing.

Avaya support are saying that SDK 6.2 is not compatible with AES 6.1.2. My feeling is the customer will need to upgrade and we may not find a cause for this issue. Hopefully upgrading the AES will help. I do think there is mileage in optimising the application to not stop /start monitors so frequently.

Thanks John. Will do. Not found a problem yet but I have a newer AES , that may affect things.