Created by: David Oxley on 20-08-2013 09:04:17 AM I believe I have stumbled across a bug in version 8.5 of the AXL API for Call Manager - specifically, "getPhone" does not return roamingDevicePoolName when requested. We're using CUCM 18.104.22.16846-1. This functionality works* on the same Call Manager when exercised with the 7.1 API, but not when the 8.5 API is employed. I've attached some sample requests/responses. Note that it's the same call manager and the same application user in each case; the only thing that changes is the version of the API.
* - well, it returns a UUID rather than a name, but I can live with that.
This seems like a bug to me (getPhone happily returns everything else that we've asked for) but would be happy for someone to point it out if I'm making a mistake.
Subject: RE: AXL (8.5) getPhone does not return roamingDevicePoolName Replied by: David Staudt on 21-08-2013 04:49:29 PM This is likely a defect, where roamingDevicePoolName is not implemented, but before generating a defect ID need to request a few details: - Is the device in fact roaming and registered in an EMCC configuration at the time of the request? - If not, any chance that device pool with UUID of '1a1de63b-f3af-9044-527e-2c0b66132246' is in fact named 'FOO'..? - Assuming the above check out, can you enable the detailed level AXL logs and attach here? http://developer.cisco.com/web/axl-developer/gather-axl-logs
Subject: RE: AXL (8.5) getPhone does not return roamingDevicePoolName Replied by: David Oxley on 22-08-2013 08:52:58 AM David,
Thanks for the reply.
>- Is the device in fact roaming and registered in an EMCC configuration at the time of the request? I'm not sure what you mean in terms of EMCC configuration (we're not using Cross Cluster Extension Mobility) but, yes, the device is roaming. By this I mean the phone displays the message "Device in Roaming Location" and when I click "View Current Device Mobility Settings" I see that the Roaming Device Pool field is populated. (I'd include a screenshot but I can't see how to attach things to a reply.)
> any chance that device pool with UUID of '1a1de63b-f3af-9044-527e-2c0b66132246' is in fact named 'FOO'..? Actually no. At the time of my initial post, 1a1de63b-f3af-9044-527e-2c0b66132246 was actually BAR:
1admin:run sql select name from devicepool where pkid = '1a1de63b-f3af-9044-527e-2c0b66132246' 2name 3==== 4BAR
(we've since swapped them around for other testing, hence the edit.)
> can you enable the detailed level AXL logs and attach here? Yep - I wanted to get ball rolling with a reply - I'll append the logs shortly.
We have custom integration jars deployed in CVP that previously leveraged log4j1.x FileAppenders and such to allow for creation of individual LOG files for each integration. For example, integration A resulted in a dedicated integrationA.log file in addit...
Hello, we're using UCCX 12.5. We faced issue, where we cannot change agent's status to Ready after login in to Finesse app and external app controlling our devices. Everything is fine when we are using only Finesse app. Problem is present only in sit...
My request works fine in 22.214.171.12400-20 but gives back 599 unsupported header in 126.96.36.19900-132. DId something change in SU1 ? I have tried with both v12 and v14 database and fails with SU1. Works fine in older verson of CallManager 14, jus...
Hello,1-what is the difference between gadget and non gadget samples. I can see that both can be html files and calling JS at the back end. finessenongadget.js and finesse.js2- Regarding gadgets , if we need to call an API (for example answer ca...