date:20170831

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

2017-08-31 Thread Lelio Fulgenzi

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 shouldn't see it?

Sent from my iPhone

On Aug 31, 2017, at 5:13 PM, Brian Meade 
> wrote:

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

Sent from my iPad

On 31 Aug 2017, at 21:37, Anthony Holloway 
> wrote:

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 the device table.

  *   Anything that is a pattern is in the numplan table

  *   End Users are in the enduser table, while Application Users are in the 
applicationuser table

  *   The database is a relational database, meaning that data from one table 
will have a relationship to data in another table

  *   Some tables are joined by holding a GUID in their PKID column, which 
other tables refer to with a column name in their own table, named "fk" + 
tablename E.g., device.fkenduser = enduser.pkid

  *   Some tables are joined by holding an enum (number) in their enum column, 
which other tables refer to with a column name in their own table, named "tk" + 
tablename E.g., device.tkmodel = typemodel.enum (slightly different that fk)

  *   Some data objects are mapped together to form a new object in a third 
table named: tablename1 + tablename2 + "map"  E.g., devicenumplanmap holds line 
appearances for phones and DNs

  *   To find a list of table names: select tabname from systables order by 
tabname

  *   To find a list of columns in a table: select colname from syscolumns 
where tabid = (select tabid from systables where tabname = 'numplan') order by 
colname

  *   Sometimes when I don't know what the name of something is in the 
database, I just access the resource in the web admin, and then look at logs
This tip is courtesy of Wes Sisk: 
http://cisco-voip.markmail.org/thread/vtoasdkgieadmou3

  *   Other times I just look at the HTML on the web page to find out the name 
of the field, which is usually the name of the column (99% of the time)

On Thu, Aug 31, 2017 at 2:08 PM Ben Amick 
> wrote:
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 route 
points, etc to just automagically generate all my documentation, but I have not 
nearly enough knowledge about hot to use the API or the database structure in 
general. You wouldn’t happen to have a crash course on all that, would you?

From: cisco-voip 
[mailto:cisco-voip-boun...@puck.nether.net]
 On Behalf Of Brian Meade
Sent: Wednesday, August 30, 2017 5:28 PM
To: Tim Reimers >
Cc: cisco-voip >
Subject: Re: [cisco-voip] Automatically exporting just the DN and Description 
fields

Use the AXL API and the following SQL query to automate this:

select dnorpattern,description from numplan where tkpatternusage='2'

You can put "run sql" before the query to run via SSH to CUCM.

On Wed, Aug 30, 2017 at 4:45 PM, Tim Reimers 
> wrote:
Hi all-

In CUCM 9.12
I'm trying to figure out how to export just a few of the fields from the UCM 
database.
What we're after is simply the DN number, and the contents of the Description 
field associated with that DN

I've done a Phone export, and the resulting CSV is so huge it's unusable in 
Google Sheets.
I know I can set up an Export as a repeated schedule, but I have two questions.

- Can I somehow reduce the export query to a limited set of details about lines 
only. I don't need phone info particularly.
- Is there a way to transfer the file off the UCM environment automatically, so 
that it's available to another automated process that will  automatically 
consume the resulting file and use that data? Right now, I have to manually 
download the export job file.

Thanks, Tim

--

Quis custodiet ipsos

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

2017-08-31 Thread Ryan Ratliff (rratliff)

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:

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, very little 
in UCCX (mostly callcontactdetail), and none at all for other products.

On Thu, Aug 31, 2017 at 3: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

Sent from my iPad

On 31 Aug 2017, at 21:37, Anthony Holloway 
> wrote:

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 the device table.

  *   Anything that is a pattern is in the numplan table

  *   End Users are in the enduser table, while Application Users are in the 
applicationuser table

  *   The database is a relational database, meaning that data from one table 
will have a relationship to data in another table

  *   Some tables are joined by holding a GUID in their PKID column, which 
other tables refer to with a column name in their own table, named "fk" + 
tablename E.g., device.fkenduser = enduser.pkid

  *   Some tables are joined by holding an enum (number) in their enum column, 
which other tables refer to with a column name in their own table, named "tk" + 
tablename E.g., device.tkmodel = typemodel.enum (slightly different that fk)

  *   Some data objects are mapped together to form a new object in a third 
table named: tablename1 + tablename2 + "map"  E.g., devicenumplanmap holds line 
appearances for phones and DNs

  *   To find a list of table names: select tabname from systables order by 
tabname

  *   To find a list of columns in a table: select colname from syscolumns 
where tabid = (select tabid from systables where tabname = 'numplan') order by 
colname

  *   Sometimes when I don't know what the name of something is in the 
database, I just access the resource in the web admin, and then look at logs
This tip is courtesy of Wes Sisk: 
http://cisco-voip.markmail.org/thread/vtoasdkgieadmou3

  *   Other times I just look at the HTML on the web page to find out the name 
of the field, which is usually the name of the column (99% of the time)

  *   

On Thu, Aug 31, 2017 at 2:08 PM Ben Amick 
> wrote:
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 route 
points, etc to just automagically generate all my documentation, but I have not 
nearly enough knowledge about hot to use the API or the database structure in 
general. You wouldn’t happen to have a crash course on all that, would you?

From: cisco-voip 
[mailto:cisco-voip-boun...@puck.nether.net]
 On Behalf Of Brian Meade
Sent: Wednesday, August 30, 2017 5:28 PM
To: Tim Reimers >
Cc: cisco-voip >
Subject: Re: [cisco-voip] Automatically exporting just the DN and Description 
fields

Use the AXL API and the following SQL query to automate this:

select dnorpattern,description from numplan where tkpatternusage='2'

You can put "run sql" before the query to run via SSH to CUCM.

On Wed, Aug 30, 2017 at 4:45 PM, Tim Reimers 
> wrote:
Hi all-

In CUCM 9.12
I'm trying to figure out how to export just a few of the fields from the UCM 
database.
What we're after is simply the DN number, and the contents of the Description 
field associated with that DN

I've done a Phone export, and the resulting CSV is so huge it's unusable in 
Google Sheets.
I know I can set up an Export as a repeated schedule, but I have two questions.

- Can I somehow reduce the export query to a limited set of details about lines 
only. I don't need phone info particularly.
- Is there a way to transfer the file off the UCM environment automatically, so 
that it's available

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

2017-08-31 Thread Anthony Holloway

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 ,
very little in UCCX (mostly callcontactdetail), and none at all for other
products.

On Thu, Aug 31, 2017 at 3: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
>
> Sent from my iPad
>
> On 31 Aug 2017, at 21:37, Anthony Holloway <
> avholloway+cisco-v...@gmail.com> wrote:
>
> 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 the device table.
>
>- Anything that is a pattern is in the numplan table
>
>- End Users are in the enduser table, while Application Users are in
>the applicationuser table
>
>- The database is a relational database, meaning that data from one
>table will have a relationship to data in another table
>
>- Some tables are joined by holding a GUID in their PKID column, which
>other tables refer to with a column name in their own table, named "fk" +
>tablename E.g., device.fkenduser = enduser.pkid
>
>- Some tables are joined by holding an enum (number) in their enum
>column, which other tables refer to with a column name in their own table,
>named "tk" + tablename E.g., device.tkmodel = typemodel.enum (slightly
>different that fk)
>
>- Some data objects are mapped together to form a new object in a
>third table named: tablename1 + tablename2 + "map"  E.g., devicenumplanmap
>holds line appearances for phones and DNs
>
>- To find a list of table names: select tabname from systables order
>by tabname
>
>- To find a list of columns in a table: select colname from syscolumns
>where tabid = (select tabid from systables where tabname = 'numplan') order
>by colname
>
>- Sometimes when I don't know what the name of something is in the
>database, I just access the resource in the web admin, and then look at 
> logs
>This tip is courtesy of Wes Sisk:
>http://cisco-voip.markmail.org/thread/vtoasdkgieadmou3
>
>
>
>- Other times I just look at the HTML on the web page to find out the
>name of the field, which is usually the name of the column (99% of the 
> time)
>
>
>
>- 
>
>
> On Thu, Aug 31, 2017 at 2:08 PM Ben Amick  wrote:
>
>> 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
>> route points, etc to just automagically generate all my documentation, but
>> I have not nearly enough knowledge about hot to use the API or the database
>> structure in general. You wouldn’t happen to have a crash course on all
>> that, would you?
>>
>>
>>
>> *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] *On
>> Behalf Of *Brian Meade
>> *Sent:* Wednesday, August 30, 2017 5:28 PM
>> *To:* Tim Reimers 
>> *Cc:* cisco-voip 
>> *Subject:* Re: [cisco-voip] Automatically exporting just the DN and
>> Description fields
>>
>>
>>
>> Use the AXL API and the following SQL query to automate this:
>>
>>
>>
>> select dnorpattern,description from numplan where tkpatternusage='2'
>>
>>
>>
>> You can put "run sql" before the query to run via SSH to CUCM.
>>
>>
>>
>> On Wed, Aug 30, 2017 at 4:45 PM, Tim Reimers 
>> wrote:
>>
>> Hi all-
>>
>>
>>
>> In CUCM 9.12
>>
>> I'm trying to figure out how to export just a few of the fields from the
>> UCM database.
>>
>> What we're after is simply the DN number, and the contents of the
>> Description field associated with that DN
>>
>>
>>
>> I've done a Phone export, and the resulting CSV is so huge it's unusable
>> in Google Sheets.
>>
>> I know I can set up an Export as a repeated schedule, but I have two
>> questions.
>>
>>
>>
>> - Can I somehow reduce the export query to a limited set of details about
>> lines only. I don't need phone info particularly.
>>
>> - Is there a way to transfer the file off the UCM environment
>> automatically, so that it's available to another automated process that
>> will  automatically consume the resulting file and use that data? Right
>> now, I have to manually download the export job file.
>>
>>
>>
>> Thanks, Tim
>>
>>
>>
>> --
>>
>>

[cisco-voip] more UCS goodness

2017-08-31 Thread Lelio Fulgenzi


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 listed on the UCS HW/SW 
compatibility tool which worries me.


---
Lelio Fulgenzi, B.A.
Senior Analyst, Network Infrastructure
Computing and Communications Services (CCS)
University of Guelph

519-824-4120 Ext 56354
le...@uoguelph.ca
www.uoguelph.ca/ccs
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1

<>___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

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

2017-08-31 Thread Brian Meade

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
>
> Sent from my iPad
>
> On 31 Aug 2017, at 21:37, Anthony Holloway  com> wrote:
>
> 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 the device table.
>
>- Anything that is a pattern is in the numplan table
>
>- End Users are in the enduser table, while Application Users are in
>the applicationuser table
>
>- The database is a relational database, meaning that data from one
>table will have a relationship to data in another table
>
>- Some tables are joined by holding a GUID in their PKID column, which
>other tables refer to with a column name in their own table, named "fk" +
>tablename E.g., device.fkenduser = enduser.pkid
>
>- Some tables are joined by holding an enum (number) in their enum
>column, which other tables refer to with a column name in their own table,
>named "tk" + tablename E.g., device.tkmodel = typemodel.enum (slightly
>different that fk)
>
>- Some data objects are mapped together to form a new object in a
>third table named: tablename1 + tablename2 + "map"  E.g., devicenumplanmap
>holds line appearances for phones and DNs
>
>- To find a list of table names: select tabname from systables order
>by tabname
>
>- To find a list of columns in a table: select colname from syscolumns
>where tabid = (select tabid from systables where tabname = 'numplan') order
>by colname
>
>- Sometimes when I don't know what the name of something is in the
>database, I just access the resource in the web admin, and then look at 
> logs
>This tip is courtesy of Wes Sisk: http://cisco-voip.markmail.
>org/thread/vtoasdkgieadmou3
>
>- Other times I just look at the HTML on the web page to find out the
>name of the field, which is usually the name of the column (99% of the 
> time)
>
>
>
>
> On Thu, Aug 31, 2017 at 2:08 PM Ben Amick  wrote:
>
>> 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
>> route points, etc to just automagically generate all my documentation, but
>> I have not nearly enough knowledge about hot to use the API or the database
>> structure in general. You wouldn’t happen to have a crash course on all
>> that, would you?
>>
>>
>>
>> *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] *On
>> Behalf Of *Brian Meade
>> *Sent:* Wednesday, August 30, 2017 5:28 PM
>> *To:* Tim Reimers 
>> *Cc:* cisco-voip 
>> *Subject:* Re: [cisco-voip] Automatically exporting just the DN and
>> Description fields
>>
>>
>>
>> Use the AXL API and the following SQL query to automate this:
>>
>>
>>
>> select dnorpattern,description from numplan where tkpatternusage='2'
>>
>>
>>
>> You can put "run sql" before the query to run via SSH to CUCM.
>>
>>
>>
>> On Wed, Aug 30, 2017 at 4:45 PM, Tim Reimers 
>> wrote:
>>
>> Hi all-
>>
>>
>>
>> In CUCM 9.12
>>
>> I'm trying to figure out how to export just a few of the fields from the
>> UCM database.
>>
>> What we're after is simply the DN number, and the contents of the
>> Description field associated with that DN
>>
>>
>>
>> I've done a Phone export, and the resulting CSV is so huge it's unusable
>> in Google Sheets.
>>
>> I know I can set up an Export as a repeated schedule, but I have two
>> questions.
>>
>>
>>
>> - Can I somehow reduce the export query to a limited set of details about
>> lines only. I don't need phone info particularly.
>>
>> - Is there a way to transfer the file off the UCM environment
>> automatically, so that it's available to another automated process that
>> will  automatically consume the resulting file and use that data? Right
>> now, I have to manually download the export job file.
>>
>>
>>
>> Thanks, Tim
>>
>>
>>
>> --
>>
>> *Quis custodiet ipsos
>>

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

2017-08-31 Thread Stephen Welsh



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, 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 the device table.

  *   Anything that is a pattern is in the numplan table

  *   End Users are in the enduser table, while Application Users are in the 
applicationuser table

  *   The database is a relational database, meaning that data from one table 
will have a relationship to data in another table

  *   Some tables are joined by holding a GUID in their PKID column, which 
other tables refer to with a column name in their own table, named "fk" + 
tablename E.g., device.fkenduser = enduser.pkid

  *   Some tables are joined by holding an enum (number) in their enum column, 
which other tables refer to with a column name in their own table, named "tk" + 
tablename E.g., device.tkmodel = typemodel.enum (slightly different that fk)

  *   Some data objects are mapped together to form a new object in a third 
table named: tablename1 + tablename2 + "map"  E.g., devicenumplanmap holds line 
appearances for phones and DNs

  *   To find a list of table names: select tabname from systables order by 
tabname

  *   To find a list of columns in a table: select colname from syscolumns 
where tabid = (select tabid from systables where tabname = 'numplan') order by 
colname

  *   Sometimes when I don't know what the name of something is in the 
database, I just access the resource in the web admin, and then look at logs
This tip is courtesy of Wes Sisk: 
http://cisco-voip.markmail.org/thread/vtoasdkgieadmou3

  *   Other times I just look at the HTML on the web page to find out the name 
of the field, which is usually the name of the column (99% of the time)



On Thu, Aug 31, 2017 at 2:08 PM Ben Amick 
> wrote:
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 route 
points, etc to just automagically generate all my documentation, but I have not 
nearly enough knowledge about hot to use the API or the database structure in 
general. You wouldn’t happen to have a crash course on all that, would you?

From: cisco-voip 
[mailto:cisco-voip-boun...@puck.nether.net]
 On Behalf Of Brian Meade
Sent: Wednesday, August 30, 2017 5:28 PM
To: Tim Reimers >
Cc: cisco-voip >
Subject: Re: [cisco-voip] Automatically exporting just the DN and Description 
fields

Use the AXL API and the following SQL query to automate this:

select dnorpattern,description from numplan where tkpatternusage='2'

You can put "run sql" before the query to run via SSH to CUCM.

On Wed, Aug 30, 2017 at 4:45 PM, Tim Reimers 
> wrote:
Hi all-

In CUCM 9.12
I'm trying to figure out how to export just a few of the fields from the UCM 
database.
What we're after is simply the DN number, and the contents of the Description 
field associated with that DN

I've done a Phone export, and the resulting CSV is so huge it's unusable in 
Google Sheets.
I know I can set up an Export as a repeated schedule, but I have two questions.

- Can I somehow reduce the export query to a limited set of details about lines 
only. I don't need phone info particularly.
- Is there a way to transfer the file off the UCM environment automatically, so 
that it's available to another automated process that will  automatically 
consume the resulting file and use that data? Right now, I have to manually 
download the export job file.

Thanks, Tim

--

Quis custodiet ipsos 

 opus reticulatum

Tim Reimers

Network Administrator

I.T Services

City of Asheville

treim...@ashevillenc.gov

(desk) 828-259-5512

(cell)   828-552-1585

Please do NOT

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

2017-08-31 Thread Anthony Holloway

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 the device table.

   - Anything that is a pattern is in the numplan table

   - End Users are in the enduser table, while Application Users are in the
   applicationuser table

   - The database is a relational database, meaning that data from one
   table will have a relationship to data in another table

   - Some tables are joined by holding a GUID in their PKID column, which
   other tables refer to with a column name in their own table, named "fk" +
   tablename E.g., device.fkenduser = enduser.pkid

   - Some tables are joined by holding an enum (number) in their enum
   column, which other tables refer to with a column name in their own table,
   named "tk" + tablename E.g., device.tkmodel = typemodel.enum (slightly
   different that fk)

   - Some data objects are mapped together to form a new object in a third
   table named: tablename1 + tablename2 + "map"  E.g., devicenumplanmap holds
   line appearances for phones and DNs

   - To find a list of table names: select tabname from systables order by
   tabname

   - To find a list of columns in a table: select colname from syscolumns
   where tabid = (select tabid from systables where tabname = 'numplan') order
   by colname

   - Sometimes when I don't know what the name of something is in the
   database, I just access the resource in the web admin, and then look at logs
   This tip is courtesy of Wes Sisk:
   http://cisco-voip.markmail.org/thread/vtoasdkgieadmou3

   - Other times I just look at the HTML on the web page to find out the
   name of the field, which is usually the name of the column (99% of the time)

   [image: image.png]


On Thu, Aug 31, 2017 at 2:08 PM Ben Amick  wrote:

> 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
> route points, etc to just automagically generate all my documentation, but
> I have not nearly enough knowledge about hot to use the API or the database
> structure in general. You wouldn’t happen to have a crash course on all
> that, would you?
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] *On Behalf
> Of *Brian Meade
> *Sent:* Wednesday, August 30, 2017 5:28 PM
> *To:* Tim Reimers 
> *Cc:* cisco-voip 
> *Subject:* Re: [cisco-voip] Automatically exporting just the DN and
> Description fields
>
>
>
> Use the AXL API and the following SQL query to automate this:
>
>
>
> select dnorpattern,description from numplan where tkpatternusage='2'
>
>
>
> You can put "run sql" before the query to run via SSH to CUCM.
>
>
>
> On Wed, Aug 30, 2017 at 4:45 PM, Tim Reimers 
> wrote:
>
> Hi all-
>
>
>
> In CUCM 9.12
>
> I'm trying to figure out how to export just a few of the fields from the
> UCM database.
>
> What we're after is simply the DN number, and the contents of the
> Description field associated with that DN
>
>
>
> I've done a Phone export, and the resulting CSV is so huge it's unusable
> in Google Sheets.
>
> I know I can set up an Export as a repeated schedule, but I have two
> questions.
>
>
>
> - Can I somehow reduce the export query to a limited set of details about
> lines only. I don't need phone info particularly.
>
> - Is there a way to transfer the file off the UCM environment
> automatically, so that it's available to another automated process that
> will  automatically consume the resulting file and use that data? Right
> now, I have to manually download the export job file.
>
>
>
> Thanks, Tim
>
>
>
> --
>
> *Quis custodiet ipsos
> **opus
> reticulatum*
>
> Tim Reimers
>
> Network Administrator
>
> I.T Services
>
> City of Asheville
>
> treim...@ashevillenc.gov
>
> (desk) 828-259-5512 <(828)%20259-5512>
>
> (cell)   828-552-1585 <(828)%20552-1585>
>
> Please do NOT use the contact information above for unsolicited sales
> contacts.
>
> All unsolicited sales calls > /dev/null
>
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>

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

2017-08-31 Thread Brian Meade

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, 2017 at 3:06 PM, Ben Amick  wrote:

> 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
> route points, etc to just automagically generate all my documentation, but
> I have not nearly enough knowledge about hot to use the API or the database
> structure in general. You wouldn’t happen to have a crash course on all
> that, would you?
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] *On Behalf
> Of *Brian Meade
> *Sent:* Wednesday, August 30, 2017 5:28 PM
> *To:* Tim Reimers 
> *Cc:* cisco-voip 
> *Subject:* Re: [cisco-voip] Automatically exporting just the DN and
> Description fields
>
>
>
> Use the AXL API and the following SQL query to automate this:
>
>
>
> select dnorpattern,description from numplan where tkpatternusage='2'
>
>
>
> You can put "run sql" before the query to run via SSH to CUCM.
>
>
>
> On Wed, Aug 30, 2017 at 4:45 PM, Tim Reimers 
> wrote:
>
> Hi all-
>
>
>
> In CUCM 9.12
>
> I'm trying to figure out how to export just a few of the fields from the
> UCM database.
>
> What we're after is simply the DN number, and the contents of the
> Description field associated with that DN
>
>
>
> I've done a Phone export, and the resulting CSV is so huge it's unusable
> in Google Sheets.
>
> I know I can set up an Export as a repeated schedule, but I have two
> questions.
>
>
>
> - Can I somehow reduce the export query to a limited set of details about
> lines only. I don't need phone info particularly.
>
> - Is there a way to transfer the file off the UCM environment
> automatically, so that it's available to another automated process that
> will  automatically consume the resulting file and use that data? Right
> now, I have to manually download the export job file.
>
>
>
> Thanks, Tim
>
>
>
> --
>
> *Quis custodiet ipsos
> **opus
> reticulatum*
>
> Tim Reimers
>
> Network Administrator
>
> I.T Services
>
> City of Asheville
>
> treim...@ashevillenc.gov
>
> (desk) 828-259-5512 <(828)%20259-5512>
>
> (cell)   828-552-1585 <(828)%20552-1585>
>
> Please do NOT use the contact information above for unsolicited sales
> contacts.
>
> All unsolicited sales calls > /dev/null
>
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> 
>
>
>
> Confidentiality Note: This message is intended for use only by the
> individual or entity to which it is addressed and may contain information
> that is privileged, confidential, and exempt from disclosure under
> applicable law. If the reader of this message is not the intended recipient
> or the employee or agent responsible for delivering the message to the
> intended recipient, you are hereby notified that any dissemination,
> distribution or copying of this communication is strictly prohibited. If
> you have received this communication in error, please contact the sender
> immediately and destroy the material in its entirety, whether electronic or
> hard copy. Thank you
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

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

2017-08-31 Thread Ben Amick

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 route 
points, etc to just automagically generate all my documentation, but I have not 
nearly enough knowledge about hot to use the API or the database structure in 
general. You wouldn’t happen to have a crash course on all that, would you?

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Brian 
Meade
Sent: Wednesday, August 30, 2017 5:28 PM
To: Tim Reimers 
Cc: cisco-voip 
Subject: Re: [cisco-voip] Automatically exporting just the DN and Description 
fields

Use the AXL API and the following SQL query to automate this:

select dnorpattern,description from numplan where tkpatternusage='2'

You can put "run sql" before the query to run via SSH to CUCM.

On Wed, Aug 30, 2017 at 4:45 PM, Tim Reimers 
> wrote:
Hi all-

In CUCM 9.12
I'm trying to figure out how to export just a few of the fields from the UCM 
database.
What we're after is simply the DN number, and the contents of the Description 
field associated with that DN

I've done a Phone export, and the resulting CSV is so huge it's unusable in 
Google Sheets.
I know I can set up an Export as a repeated schedule, but I have two questions.

- Can I somehow reduce the export query to a limited set of details about lines 
only. I don't need phone info particularly.
- Is there a way to transfer the file off the UCM environment automatically, so 
that it's available to another automated process that will  automatically 
consume the resulting file and use that data? Right now, I have to manually 
download the export job file.

Thanks, Tim

--

Quis custodiet ipsos 

 opus reticulatum

Tim Reimers

Network Administrator

I.T Services

City of Asheville

treim...@ashevillenc.gov

(desk) 828-259-5512

(cell)   828-552-1585

Please do NOT use the contact information above for unsolicited sales contacts.

All unsolicited sales calls > /dev/null

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip



Confidentiality Note: This message is intended for use only by the individual 
or entity to which it is addressed and may contain information that is 
privileged, confidential, and exempt from disclosure under applicable law. If 
the reader of this message is not the intended recipient or the employee or 
agent responsible for delivering the message to the intended recipient, you are 
hereby notified that any dissemination, distribution or copying of this 
communication is strictly prohibited. If you have received this communication 
in error, please contact the sender immediately and destroy the material in its 
entirety, whether electronic or hard copy. Thank you___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

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

2017-08-31 Thread Ryan Huff

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 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 list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[cisco-voip] Office 365 CUC 11.5.1 and Speechview

2017-08-31 Thread Sean E. Knight via cisco-voip

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 list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

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

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

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

[cisco-voip] more UCS goodness

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

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

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

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

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

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

[cisco-voip] Office 365 CUC 11.5.1 and Speechview

11 matches

Site Navigation

Mail list logo

Footer information