you are on the right tracks...
the DMCC dashboard (bundled in the .NET version of DMCC SDK) is a useful tool to figure out button numbers to signal with during development, but you actually have to query for button info (with button 0) and get a dump of what is provisioned on the phone, and locate the vu-Stats button and use that button number. The DMCC Dashboard has a phone mockup that can be used to do some discovery with. There is a description of how to automate button number discovery in the Mastering DMCC ebook if I recall properly.
Buttons are numbered based on 'modules' and then a count within module, (these two values are combined into a single number) so the actual values you signal with look pretty funny.
https://www.devconnectprogram.com/site/global/products_resources/avaya_aura_application_enablement_services/interfaces/dmcc/development_tools_configurations/dmcc_dashboard/index.gsp
https://www.devconnectprogram.com/site/global/products_resources/avaya_aura_application_enablement_services/educational_resources/ebooks/mastering_dmcc/index.gsp
If that info doesn't help, write back and I will get the actual SME to provide some more more detailed info.
|