Hello
We are seeing an issue with DMCC where you attempt a single step transfer from an a-brdg appearance to an invalid number, then immediately try to transfer to a valid number DMCC errors with resourceBusy. If we wait ~5 sec between transfer attempts we do not see this error. We do not see the error on the primary appearance of the device.

5518 is the calling party
5721 is the line we are controlling via DMCC
1234 invalid single-step transfer number
5165 valid single-step transfer number

Here are logs from DMCC Dashboard

Aaron, please open a tech support request (ticket), and include the DMCC trace logs set to FINEST. Perhaps in them we can find some insight as to what is going on. The Client side behavior does not provide the best diagnostic information.

https://www.devconnectprogram.com/site/global/products_resources/avaya_aura_application_enablement_services/support/faq/dmcc/index.gsp?tab=other&accordion=faq-60

Thank you.

Thanks. We will reproduce and get logs from the DMCC server and open a ticket.