Gather Caller Input Key Information

RE: Connection 8.6.2 - User Account Creation Type

2012-06-29T17:06:40Z

Hi Jeff, Thanks for checking. It seems strange that '3' isn't included. I'm not even sure how the AXL imported users got into the system. I use the REST API for ldap import or manual creation if they're not in LDAP but we had a 3rd party tool a while back that might have been using an import process through CUCM somehow. They're just deleting the VM account and recreating it through LDAP import to fix the authentication issue for now, so I'm trying to find a way to preserve the accounts. Later, Marty

RE: Connection 8.6.2 - User Account Creation Type

2012-06-29T16:05:19Z

Hello again, After looking through the user URI and Data Dictionary for 8.5.1 included in CUDLI (anyone know if 8.6.2 is in the latest CUDLI?) I found a field 'LdapType' which enumerates: 0 - "User does not have LDAP enabled." 1 - "LDAP synchronization enabled." 2 - "LDAP authentication enabled." 4 - "LDAP is enabled but temporariliy inactive for the user." My functional LDAP imported user account has a status of 3 which strangely enough isn't listed in the LdapType enumeration table that I have. The user account which is listed as imported through AXL is listed as 2 - "LDAP authentication enabled.". Is there a "safe" way of updating this field to '3' for testing? The AXL imported user account page shows the LDAP Integration Status as 'Integrate with LDAP Directory'. Thank you, Marty

Connection 8.6.2 - User Account Creation Type

2012-06-29T15:01:09Z

Hello, I'm trying to find a flag in Unity Connection DB that indicates how the account was created. Some say 'Active User Imported from LDAP Directory', 'User Imported through AXL' or nothing at all (manual creation). Does anyone know where to find this info? We're having some authentication issues with the AXL imported users which I need to track down. Thanks, Marty

RE: Gather Caller Input Key Information

2012-04-23T16:45:25Z

Hi Jeff, So I found that there's also an ODBC Perl DBI module that I could use to connect as well. Do you know if it would even be possible to connect up with the Informix module, or should I stick with the ODBC? I'm getting the different parts downloaded and installed and will also grab the Linux SDK from IBM's site, just wondering what your opinion would be on this one. Thanks, Marty

RE: Gather Caller Input Key Information

2012-04-21T05:41:19Z

Hey Jeff, Thanks again for the great information. The fast start project is something new to me and sounds very cool, I'll def check it out along with the hours of video which sounds like a great Saturday to me! I think you just shined a light on something I was missing with your last comment about the ODBC connection (guess I've been too focused on using the API). I'm using Perl with a DBI module to connect with other systems and it has a connector for Informix as well. Seems like I can just connect up with that and query for what I need (responsibly, of course.:-). I'll give it a shot in the lab and see what I get. I concur on the stateless API. Limitless ambiguity! I thank you for all the great tools man. You've helped here and in more other posts than you know. Cheers! Marty

RE: Gather Caller Input Key Information

2012-04-20T23:06:27Z

Jeff, You're all over it! Thanks very much for the info. I certainly didn't know that UDD could be scheduled.... Is their a Linux version that I don't know about :-)? I'll also look further into CUDLI tool. Just to be sure since I know you're the Unity guru, my aim is really to run this process from a script on a Linux box. Outside of the UDD and CUDLI, is my best bet to grab all the alias's and run through them to grab the info? In the end it's probably easier to use the tools that are available but we're trying to consolidate all of the data gathering for the systems and the API would be the most beneficial to that end. Thanks again for the info man. Marty

Gather Caller Input Key Information

2012-04-20T21:50:28Z

Hello, I'm needing to gather caller input for subscribers on our CUCX (8.5.1) cluster and was hoping to get some info on the best approach here. From what I can tell, I need to grab the subscriber URI and then get the call handler URI which will pull the input actions. In the details of that page, something like: https://cucx_ip/vmrest/handlers/callhandlers/c3e58a12-1383-4dc7-9cc4-5c4e122b62ba/menuentries/ I can see actions that are set for different keys, like . What I'm wondering is if I should assume a key is set to ignore if there is no listed? Also, we have about 7k subscribers and I need to pull this info daily for each one. Would the best approach be to get a list of all subscribers and then iterate through each gathering the caller input actions? I do a decent amount of work with the CUCM API and it seems to be a bit friendlier in accessing the DB with SQLSelects to pull the different tables together. There's also the Subscriber Dump but I'm hoping to schedule a job that runs automagically for us using the API. If anyone has travelled this path and has a recommendation on the most efficient way to gather the info, I would greatly appreaciate the input. Thanks, Marty [color=blue] [/color]