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

ATA186 - phone duplicate association attempt

Hi!

I have a problem with ATA186 registration (SCCP) with Cisco Call Manager Express 4.1.

Here is output of 'debug ephone messages and debug ephone register'

Oct 27 09:43.782: ephone-(42)[42] StationRegisterMessage (49/49/96) from 10.90.110.42

Oct 27 09:29:43.782: ephone-(42)[42] Register StationIdentifier DeviceName ATA001E7AC450E9

Oct 27 09:29:43.782: ephone-(42)[42] StationIdentifier Instance 1 deviceType 12

Oct 27 09:29:43.782: ephone-42[42]:stationIpAddr 10.90.110.42

Oct 27 09:29:43.782: ephone-42[42][ATA001E7AC450E9]:maxStreams 0

Oct 27 09:29:43.782: ephone-42[42][ATA001E7AC450E9]:protocol Ver 0x1

Oct 27 09:29:43.782: ephone-42[42][ATA001E7AC450E9]:phone-size 5404 dn-size 680

Oct 27 09:29:43.782: ephone-(42) Allow any Skinny Server IP address 10.90.103.1

Oct 27 09:29:43.782: ephone-42[42][ATA001E7AC450E9]:Found entry 41 for 001E7AC450E9

Oct 27 09:29:43.782: ephone-42[42][ATA001E7AC450E9]:phone duplicate association attempt on socket [42]

Oct 27 09:29:43.782: Failed SkinnyAssociatePhone for ATA001E7AC450E9 tag 42

Oct 27 09:29:43.782: Skinny register (phones=49/49/96) REJECT from IP 10.90.110.42

Oct 27 09:29:43.782: Sending message 0x48936C48 to phone 42, sock 42, tcb 0x47AA2480, SkinnyMessageID = StationRegisterRejectMessageID

Oct 27 09:30:03.695: Received message from phone 42, sock 42, tcb 0x47AA2480, SkinnyMessageID = StationAlarmMessageID

Oct 27 09:30:03.695: %IPPHONE-6-REG_ALARM: Name=ATA001E7AC450E9 Load=ATA030203SCCP051201A.zup Last=Initialized

Oct 27 09:30:03.695: Skinny StationAlarmMessage on socket [42] 10.90.110.42 ATA001E7AC450E9

Oct 27 09:30:03.695: severityInformational p1=0 [0x0] p2=0 [0x0]

Oct 27 09:30:03.695: Name=ATA001E7AC450E9 Load=ATA030203SCCP051201A.zup Last=Initialized

Oct 27 09:30:03.795: Received message from phone 42, sock 42, tcb 0x47AA2480, SkinnyMessageID = StationRegisterMessageID

Oct 27 09:30:03.795: Received StationRegisterMessage from phone ATA001E7AC450E9, sock 42, tcb 0x47AA2480

Oct 27 09:30:03.795: ephone-(42)[42] StationRegisterMessage (49/49/96) from 10.90.110.42

Oct 27 09:30:03.795: ephone-(42)[42] Register StationIdentifier DeviceName ATA001E7AC450E9

Oct 27 09:30:03.795: ephone-(42)[42] StationIdentifier Instance 1 deviceType 12

Oct 27 09:30:03.795: ephone-42[42]:stationIpAddr 10.90.110.42

Oct 27 09:30:03.795: ephone-42[42][ATA001E7AC450E9]:maxStreams 0

Oct 27 09:30:03.795: ephone-42[42][ATA001E7AC450E9]:protocol Ver 0x1

Oct 27 09:30:03.795: ephone-42[42][ATA001E7AC450E9]:phone-size 5404 dn-size 680

Oct 27 09:30:03.795: ephone-(42) Allow any Skinny Server IP address 10.90.103.1

Oct 27 09:30:03.795: ephone-42[42][ATA001E7AC450E9]:Found entry 41 for 001E7AC450E9

Oct 27 09:30:03.795: ephone-42[42][ATA001E7AC450E9]:phone duplicate association attempt on socket [42]

Oct 27 09:30:03.795: Failed SkinnyAssociatePhone for ATA001E7AC450E9 tag 42

Oct 27 09:30:03.795: Skinny register (phones=49/49/96) REJECT from IP 10.90.110.42

Oct 27 09:30:03.795: Sending message 0x48936C48 to phone 42, sock 42, tcb 0x47AA2480, SkinnyMessageID = StationRegisterRejectMessag

ATA tries to register with CCME, but CCME discards registration with reply

Oct 27 09:31:09.775: ephone-42[46][ATA001E7AC450E9]:Found entry 41 for 001E7AC450E9

Oct 27 09:31:09.775: ephone-42[46][ATA001E7AC450E9]:phone duplicate association attempt on socket [46]

Oct 27 09:31:09.775: Failed SkinnyAssociatePhone for ATA001E7AC450E9 tag 42

Here is ATA ephone configuration

ephone 42

device-security-mode none

mac-address 001E.7AC4.50E9

paging-dn 33

codec g729r8

type ata

button 1:53

!

And here is ephone 41 (CCME thinks that ATA already associated with id 41

ephone 41

device-security-mode none

ephone-template 1

mac-address 0019.AA68.377C

paging-dn 33

type 7912

button 1:26

!

I tried to remove all telephone-service configuration and aply it again. All ephones registered with different IDs but this ATA has the same problem - CCME thinks that this MAC is already associated with previous ephone ID.

Arseny

1 ACCEPTED SOLUTION

Accepted Solutions
New Member

Re: ATA186 - phone duplicate association attempt

If you have previously assigned the ATA's MAC to the ephone 41, and then moved it to ephone 42, you should rebuild the configuration files for the phones (and the ATA).

if this is the case, then from global config mode issue:

telephony-service

create cnf files

reset all

! or just reset the ata and the 7912 phone

HTH

Regards,

Vasil

2 REPLIES
New Member

Re: ATA186 - phone duplicate association attempt

If you have previously assigned the ATA's MAC to the ephone 41, and then moved it to ephone 42, you should rebuild the configuration files for the phones (and the ATA).

if this is the case, then from global config mode issue:

telephony-service

create cnf files

reset all

! or just reset the ata and the 7912 phone

HTH

Regards,

Vasil

New Member

Re: ATA186 - phone duplicate association attempt

Dear Vasil,

Thanks for your helpful reply :)

311
Views
0
Helpful
2
Replies
CreatePlease to create content