Off the top of my head,  you’d want to move to SSO, or require Jabber to prompt for credential each time you sign in.   I believe SSO in this case can also utilize Kerberos for Windows based machines to make things a bit more transparent.  ... View more

You can do this with AXL and specify a new userID to effectively “rename” the record. Works just fine to do that and then sync. If you already sync users then you have to remove them as the userID cannot overlap. ... View more

As Will said, export, or maybe the API to pull a list in XML format. ... View more

Use the dialed number analyzer against the calling search space or spaces to see how it is routing and why it has made this choice, or at least get in the right direction. ... View more

There were not for me - the system is relatively robust managing the change queue. I ran this against about 5700 users and had no trouble. I’ve done work since then, the AXL interface will get slower if it needs to - and I didn’t handle timeout here. It shouldn’t be an issue but If it is, you’d just want to run smaller batches or add a sleep statement. Raw DB queries have a limitation and excessive queries will be killed or will clog the change queue. ... View more

Custom tabs just render HTML with the included engine. The custom directory application would have to include a HTML interface to display properly in the custom tab within Jabber. It will not parse on its own otherwise. There is some guidance as to the tab's properties in the Jabber documentation - the web design should be responsive so that it can handle the window sizing possibilities, however, note that this type of content may not load properly over MRA if it is internal only, depending on where resources are being loaded from. ... View more

Cat 5e works just fine. It is a Class 3 device, and it will negotiate 13.0W if it can, 15.4W otherwise. Based on the detail stats on some of my equipment, it draws an average of 3W, with a peak of 3.7W at some point, having been involved in a call. I don't know at what volume level, but no external mics or anything. ... View more

Not sure how you accidentally reset a phone, but, if it had a certificate you'll need to re-enroll it on the device configuration page before it will register. If it's over MRA then you would have to choose that service mode and domain, and sign in again. IIRC if it had a cert and it's over MRA then you have to bring it back to the corporate network to re-enroll the device. ... View more

If you have an 8841 you can just use that to develop against. Cisco IP Communicator is end of life and is a different beast to work with if you are targeting the 8800 series. I'm rather new at this myself but I've used Ruby/Rack to deliver an application, and PHP in the past - the biggest challenge for me was making sure to set the content type correctly. If you're going to use a serializer or something to dispense the XML and it doesn't do exactly what you want it will be a it obnoxious but not impossible. The document you're referencing is probably the best reference I've used, aside from searching for others who have stepped in bizarre bugs or issues. Just about anything I've thrown at the 8800 seems to work if it's close enough to spec. I feel like in these instead of the 7900s they are using some generic browser item with a parser that attempts to emulate earlier devices, so you can get away with a bit more as long as it makes it there. ... View more

It's "36 Line", you can make it 18 by running single column display, but the dropdown is for the hardware type attached, the layout you control with the phone button template and device settings. ... View more

If you’re going to do all that and dip with a SQL query why not just change the fkdirectorypluginconfig to the new sync relationship right off instead of adding extra steps? The difference in the UID attribute only matters for the directory configuration, not the end user table - it should not duplicate user records if the values are the same in both directories. The new sync should even just change it itself, whichever one runs later.      ... View more

The trunk incoming CSS from A to B will need to expose route patterns that lead to C, and vice versa. The level of specificity of the patterns and the need to prefix will be related to your dial plan between the three sites. Similarly C will need to call back to B, with the trunk defined and the proper addressing or B will ignore it. If your dialplan is more complex this example may not be what you want, but, if you define a route pattern for say 3XXX , assuming the extensions at C are in the 3000s and do not overlap, you can assign that route pattern to a trunk to C. That pattern then needs to be in a partition that the trunk from A has in its incoming CSS. There are other things that are a possible issue or concern with this relating to signaling and flow but assuming all items A, B, C, and their endpoints can talk to each other directly this works. ... View more

I think this is going to depend on how you have deployed the system , as to if you can make some assumptions about the data you’ll receive. Disclaimer, I am speaking from my limited knowledge of the system.   The relationships you’re asking for don’t really exist like that in the UCM.    Directory Numbers themselves are an object that are on their own, and don’t really tether to end users directly except via perhaps the primary extension (set in end user and not necessarily unique) or the directory URI (based on the primary extension for the automatic ones). If the descriptions are templated so they contain some identifying information then you could maybe use that.    Devices can have line appearances of those DNs. Devices can have an owner ID which can be queried directly but not via search or API, which may be set to the user, and thus you can get extensions associated with that user this way. But see above that you won’t know which is theirs if there are multiple unless it matches their primary. There are associated end users with the line appearance for presence which you can get via API, but only through the device. It could also be queried from the DB.   The end user object has everything you want if you deployed everything in place though. The primary extension can be there , obviously user info, and controlled devices , if you populate that. It is not the same as a device owner ID though. If you did that then you can dump end users or use the getuser api , and just parse out the device names in whatever format you need.    It is is a puzzle otherwise and not as easy to piece it together without knowing how things were (or weren’t) deployed. ... View more