Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

UCM 6.13 BAT Problem

We are running into an issue with UCM 6.13 and BAT. When we add a phone with the dummy MAC address is gets created with a BAT prefix.

On 6.12 when you typed in the real MAC address the prefix would change from BAT to SEP, however in 6.13 & 6.13a the prefix does not change.

If we use TAPS to change the MAC address from the phone it works.

I'm going to open a case with Cisco in the morning, however I just wondering if any one else has run into this and has a fix…

I cannot downgrade to 6.12 as these clusters were installed from 6.13…

7 REPLIES
Red

Re: UCM 6.13 BAT Problem

It is a new change on 6.1.3 (and 7.0.1) - CSCso76664.

I'm still checking with development to see why they made that change.

Michael

http://htluo.blogspot.com/

New Member

Re: UCM 6.13 BAT Problem

Hmm, that bug is restricted...

Any idea if it has a workaround or a fixed in version...

Red

Re: UCM 6.13 BAT Problem

It's not a bug. It's a change they decided to make (not sure why though).

Michael

New Member

Re: UCM 6.13 BAT Problem

Any update on this? We just ran into this wonderful new change

Thanks!!!

New Member

Re: UCM 6.13 BAT Problem

The word from cisco is that this was a design change, in their view it was a bug that the extension did change from BAT to SEP when updating a phone. So they have "Fixed" the bug in that phones will no longer change from BAT to SEP.

My workaround, was to create my own program to change the phone's prefix via AXL...

You can of course use TAPS...

New Member

Re: UCM 6.13 BAT Problem

Thanks Jeff, that's what I was thinking, going the axl route with perl.

TAPS won't work for these phones since they have shared lines on them....

New Member

Re: UCM 6.13 BAT Problem

I experience the same issue and opened a TAC case. The word back from Cisco is:

"Phones added via dummy mac are "usually" used only with TAPS. This change

was intentional CSCsv25099 CSCso76664 so that phones added via dummy mac could later be used with TAPS.

MAC Address can be changed but the device prefix will still be BAT.

However I was able to find this other Fix CSCsy65451 which is a fix to

return the capabilities changed by CSCso76664. In previous releases of CUCM,

when uploading dummy MACs via BAT, customers could go into CCMAdministrator

--> Device --> Phone, select a phone, and edit the MAC address to include a

valid MAC. At this point, the 'BAT' prefix in the device name was replaced

with 'SEP'. With the introduction of CSCso76664, this expected behavior of

CUCM no longer occurs. The fact that the device name does not change to

'SEP+MAC' means that phones BAT'ed in with dummy MACs and later edited as a

single phone with a valid MAC cannot register with CUCM. This defect was put

in place to request the ability for customers to change the device name to

'SEP' if necessary on the phone configuration page of CCMAdministrator."

According to CSCsy65451 Bug Details the Device Names can be changed to SEP+MAC when updating the MAC on a BAT+MAC device in:

6.1(3.3102.1)

7.1(1.39000.151)

7.1(1.39000.152)

6.1(3.9901.133)

6.1(3.9999.1)

Tom Maurin

213
Views
0
Helpful
7
Replies