Re: [cisco-voip] Automatically exporting just the DN and Description fields

Agreed. Amazing. This might actually give me what I need to start thinking about programming some scripts. Silly question though. Passwords. Do you store these in your scripts? Do you pass them via an argument read from a file? How do you ensure this password is not "revealed" to those who

Re: [cisco-voip] Automatically exporting just the DN and Description fields

If you really want to dive into the UCM database you can find the data dictionaries in the AXL section of developer.cisco.com. -Ryan On Aug 31, 2017, at 5:53 PM, Anthony Holloway > wrote:

Re: [cisco-voip] Automatically exporting just the DN and Description fields

Thanks! I wrote that off the top of my head too. I know there's like 50 more things to know, but if you master those basics, you can figure out the rest with very little additional effort. I've spent a lot of time in the tables on CUCM, a fair but careful amount in CUC

[cisco-voip] more UCS goodness

Just found out that I need Unity Express v9 to communicate with CUCM v11.5. I also found out that the SRE modules I have don't support CUE v9 which means UCS-E modules. Anyone have any good or bad experiences with these modules? Are they the odd child out of the UCS family? They're not even

Re: [cisco-voip] Automatically exporting just the DN and Description fields

Yea, great job putting all that info together Anthony! On Thu, Aug 31, 2017 at 4:40 PM, Stephen Welsh wrote: >  > > Wow, that’s the best advice I’ve every seen on getting to grips with > CUCM’s database. > > Kind Regards > > Stephen Welsh > CTO > UnifiedFX > >

Re: [cisco-voip] Automatically exporting just the DN and Description fields

 Wow, that’s the best advice I’ve every seen on getting to grips with CUCM’s database. Kind Regards Stephen Welsh CTO UnifiedFX Sent from my iPad On 31 Aug 2017, at 21:37, Anthony Holloway > wrote: For the record,

Re: [cisco-voip] Automatically exporting just the DN and Description fields

For the record, the API part is not necessary, you can just run your SQL queries on the CLI. However, using the AXL API method to run the SQL query for you, allows you to do so programmatically. As for the database, here are a few key points: - Anything that registers is a Device and is in

Re: [cisco-voip] Automatically exporting just the DN and Description fields

Here's the full data dictionary- https://developer.cisco.com/media/UCM10.5DataDictionary/UCM10.5DataDictionary.htm Once you find a few connections, it's easy to see the structure. I'd also recommend Uplinx for getting some good configuration reports out of CUCM for projects. On Thu, Aug 31,

Re: [cisco-voip] Automatically exporting just the DN and Description fields

Do you have a quick reference sheet of the field names? I’d like to do something similar to this but also including the RNA timer/destination, user associations, external number mask, and the recording setting for each line. Really, I’d like to do a run against all my translations, phones, CTI

Re: [cisco-voip] Office 365 CUC 11.5.1 and Speechview

Unity Connection v11.5.1 should work with O365 for Unified Messaging. What type of error are you encountering? -RH On Aug 31, 2017, at 1:14 PM, Sean E. Knight via cisco-voip > wrote: We had Unified Messaging and Exchange 2010 and

[cisco-voip] Office 365 CUC 11.5.1 and Speechview

We had Unified Messaging and Exchange 2010 and worked fine and then we are moving to 365 and UM does not work with 365. I just found out that Speechview does not either. Any alternatives that anyone can suggest? Thank you ___ cisco-voip mailing