You seem to have grasped the situation as it appears to me too...even <listLine> does not return Translation Pattern "lines" it seems. It _is_ possible for regular phones and other things that have a line (route points, hunt pilots, various profiles, etc.) to have DNs with a translation pattern format, e.g. '99XX',  so there is some conceptual overlap I guess.  However, the argument that <getPhone> should exclude Translation Patterns (since we already have the better-suited <getTransPattern> is a pretty compelling one IMHO.  However, the question then is, should it only return device lines (tkpatternusage = 2) or some other subset of typepatternusage?   ... View more

Sorry, it's CallControlCall.setConferenceEnable() and conference() It might be worth a trying with setConferencEnable, as this invokes the 'full/standard' consult conference subsystem and modeling.  If that doesn't help I would advise opening a Developer Support ticket to investigate in more detail... ... View more

- The setting you mention 'Party Entrance Tone' would apply, I would think - Are you performing the typical JTAPI setupConferenceEnable()->consult()->completeConference()? - The Party Entrance Tone param is present for the CallManager Service as well as individual DNs - can you confirm it is off/default for the devices in the scenario? - If indeed something different is happening only in CTI triggered scenarios, there may be some kind of limitation or defect there.  I would suggest opening a DevNet Developer Support ticket so we can dig into the trace logs and investigate deeper... ... View more

I've added the sipProfileName field to the Python example here, if it helps: https://github.com/CiscoDevNet/axl-python-zeep-samples/blob/master/axl_add_User_Line_Phone.py Its working for me on CUCM 12.5... Unfortunately, creating each of the three objects you want to associate - line/phone/user - requires three separate AXL requests.  Perhaps if we can understand your requirement to do it in 'one shot' in more detail we can make some alternate suggestions..? Note, it may theoretically be possible to do something using multiple transactions in an <executeSqlUpdate> request, as you can include multiple SQL statements in one request:   <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.cisco.com/AXL/API/12.5"> <soapenv:Header/> <soapenv:Body> <ns:executeSQLUpdate sequence="1"> <sql>insert into numplan... ; insert into device... ; insert into user... ; insert into devicenumplan map... ; insert into enduserdevicemap ...; </sql> </ns:executeSQLUpdate> </soapenv:Body> </soapenv:Envelope> However this would require extensive knowledge of the CUCM database schema, the order/tables/fields and object relationships used when creating each type of object, and extensive SQL experience.  The result would likely be difficult to maintain/expand, and could be brittle across CUCM versions. ... View more

<addPhone> can not directly associate the User. You must use <add | updateUser> to associate Users with Phones: --> <addLine> --> <addPhone><lines><line><dirn> --> <addUser><associatedDevices> ... View more

A few thoughts: - Jabber SDK is not a supported Finesse/UCCE agent device - this is usually a showstopper.  However, AFAIK it can function as a CTI-controlled SIP device in softphone mode, so it could work in theory.  Possibly agent login is filtered by supported devices in which case the agent would not be able to login, but not sure about that (might be worth a test...)  If not, perhaps you could experiment. - It would be possible for a tier-3 server (I guess here the CRM) to proxy the Finesse API calls so that only that server communicates directly with Finesse - Possible, I would suppose...the Jabber SDK can work via MRA and you would be proxying the Finesse APIs; however the final supportability of the solution by Cisco is a red flag IMHO ... View more

See the Readme also for how to get the Zeep WSDL type dump: python3 -mzeep schema/AXLAPI.wsdl > wsdl.txt This can be very helpful in deciphering how Zeep interprets the WSDL ... View more

Added examples for <addRegion> and <addLocation> to the repo here: https://github.com/CiscoDevNet/axl-python-zeep-samples Physical Location has only a single 'name' attribute, so it should be trivial to implement based on any of those samples. ... View more

True!  AXL is an abstraction layer that provides a bunch of requests that (mostly) end up manipulating the database, similarly to how the admin UI does things.  It's (usually) a lot easier to figure out how to do something using AXL, then to try and discern all the tables/fields/keys/constraints in the truly enormous CUCM database... ... View more

Added samples to cover add/update Device Pool MRGL and add Route Pattern: https://github.com/CiscoDevNet/axl-python-zeep-samples ... View more

To confirm, the Jabber SDK does not support multi-line in softphone mode ... View more