cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1746
Views
0
Helpful
2
Replies

"Owner User ID" missing in phone export (cucm 8.6.2)

dmuizebelt
Level 1
Level 1

Hi,

I wanted to import a couple of thousand phones from a 7.1.3 cluster to an 8.6.2 cluster but the import process complained that it didn't know what the "Owner User ID" field was. I double checked but exporting existing phones on the 8.6.2 cluster didn't include the "Owner User ID" field as well.

So I come to the conclusion tat Cisco did not think the information was important enough to include it in the export/import process or the information got moved to a different file and not the phone.cvs.

This sort of limits the migratability of phones to a new cluster.

Has anybody encountered this problem as well and/or has an elegant solution for it?

Thanks,

-Danny

2 Replies 2

Rob Huffman
Hall of Fame
Hall of Fame

Hi Danny,

It looks like this bug;

CSCts16568 Bug Details Bug #6 of 32 | < Previous | Next >

No Owner User ID in Phone Export on 8x
Symptom:
No 'Owner User ID' field in csv when exporting phones via Bulk Administration Import/Export in CUCM 8x

Conditions:
Running CUCM version 8.x and up, export using BAT process:
Bulk Administration > Import/Export > Export
select phone under Device Data
submit job

In resulting csv file both columns AM and AN contain 'User ID 1'
Column AN should contain 'Owner User ID'

Workaround:
None
StatusStatus
Fixed             

Severity Severity
3 - moderate

Last Modified Last Modified
In Last 3 Days        

Product Product
Cisco Unified Communications Manager (CallManager)         

Technology Technology


1st Found-In 1st Found-in
8.5(1.10000.2)       
              
Fixed-In Fixed-in
8.6(2.98000.10)
8.6(2.98000.23)

I would look at the fixed-in versions or perhaps open a TAC case

Cheers!

Rob

Robert Thomas
Level 7
Level 7

What's wrong with changing the column AN to contain 'Owner User ID'?

This bug has been marked as resolved, but only on internal software versions so far. We would have to follow the bug to see what Public version the BU might integrate this fix into.