Guest

Preview Tool

Cisco Bug: CSCsz12400 - BAT AddLines_SampleFile.txt lists incorrect header names

Last Modified

Nov 03, 2012

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

7.0(1.21022.2)

Description (partial)

Symptom:

Unable to add lines to a phone using using BAT bat due to incorrect field names in the CSV example file.

Conditions:

Using the sample file the customer/[partner will derive the incorrect field strings in the CSV file. If there were a specified header example like in the add phone this would not be an issue. Without this information the customer will not be able to add lines & will generate a TAC case(s) to find the correct format.

Derived from the information below:

MAC Address,Line Index,Directory Number,Display,Line Text Label,Forward Busy External,Forward No Answer External,Forward No Coverage External,Forward Busy Internal,Forward No Answer Internal,Forward No Coverage Internal,Call Pickup Group


Correct fields, verified in LAB:

MAC ADDRESS,Line Index,Directory Number,Display,Line Text Label,Forward Busy External Destination,Forward No Answer External Destination,Forward No Coverage External Destination,Forward Busy Internal Destination,Forward No Answer Internal Destination,Forward No Coverage Internal Destination,Call Pickup Group


SNIP frm Sample file:

Sample string from CSV file:
1231123245AB,1,9728437154,9728437154,Mike,9725557172,9725557196,9725557126,9725557148,9725557166,9725557171,Marketing

Sample string defined:

1231123245AB,1,9725557154,9725557154,Mike,9725557172,9725557196,9725557126,9725557148,9725557166,9725557171,Marketing
|__________| | |_________| |_______| |__| |________| |________| |________| |________| |________| |________| |_______|
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | Call Pickup Group(up to 50 characters, optional)
| | | | | | | | | | |
| | | | | | | | | | Forward No Coverage Internal(up to 50 numerals, optional)
| | | | | | | | | |
| | | | | | | | | Forward No Answer Internal(up to 50 numerals, optional)
| | | | | | | | |
| | | | | | | | Forward Busy Internal(up to 50 numerals, optional)
| | | | | | | |
| | | | | | | Forward No Coverage External(up to 50 numerals, optional)
| | | | | | |
| | | | | | Forward No Answer External(up to 50 numerals, optional)
| | | | | |
| | | | | Forward Busy External(up to 50 numerals, optional)
| | | | |
| | | | Line Text Label(up to 30 characters, optional)
| | | |
| | | Display(Internal Caller ID)(up to 30 characters, optional)
| | |
| | Directory Number(up to 24 numerals, optional)
| |
| Line Index (up to 2 characters, mandatory)
|
MAC Address(12 characters, mandatory)for Phones
or
Device Profile Name(upto 50 characters, mandatory)for UDPs
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.