All,
I am having troble finding documentation on the notifications/events we should receive when a terminal registers with CUCME. 
 
Initially, we use a CMEXmlHttpConnection to obtain a list of all terminals and addresses configured in the CUCME. Then, through the provider object, we create the terminal and address and execute the terminal.addAddress() method with a listener. 
 
As seems appropriate, for any phones that are not actually turned on at the moment, we receive an ADDRESS_ACTIVATION_FAILED notification. I understand that.
 
However, my issue is that when the phone does get turned on and registers with CUCME, we don't know about it. Is there a way to get notified of when phones register?
 
Thanks,
Chris
 

But there is the problem. I am not getting the BACK_IN_SERVICE notification. Here is the scenerio.

Phone is turned off. I start my application and call the terminal.addAddress() method. The listener rece3ives an ADDRESS_ACTIVATION_FAILED notification.

Later, I turn the phone on. The phone is obviously working, but I never receive the notification fort the BACK_IN_SERVICE. Why not is my question.

Thanks,
Chris

I have attached logs and the source code for a sample application demonstrating the problem. The output of the appliation is as follows.

Attachments:

Hi Chris,

I have tested your sample in my local lab i am able to get ADDRESS_ACTIVATED event, it looks like config issue could you please send your running config.

Sep 6 14:56:29.225: VOICE_REG_POOL: No entry for (203_001C58CD131D) found in contact table

Thanks,
Raghavendra


 
Raghavendra,
 
I have attached the running-config for Chris' appliance.

Attachments:

Hi Chris,

All the configs are intact as pers ours except the following
10.42.22.201 address being used for the BVI interface and nat being enabled for the same. I am not very sure whether this is restricting address activation. Could you please give a try by disabling them.

Thanks,
Anusha

Hi Chris,

I was able to reproduce your issue with our local lab setup

[Caffeine 3.1.2.152] [] INFO - com.cisco.cme.cti.siputil.SipManager@31:
Cisco Caffeine SIP Stack version 3.1.2.152 (rel) built on Apr 19, 2008 8:04 AM ... on thread main
Provider initializing
Provider in service
received event:ADDRESS_ACTIVATION_FAILED


The problem is 'no mac address' being assigned to the ephones. From your configs

!
ephone 16
device-security-mode none
!
!
!
ephone 18
device-security-mode none
!

Also the ephone 17 is missing.Please configure the ephones and assign the mac address to the ephones. It should work.

Thanks,
Anusha


 
Anusha,
 
There are no phones associated with those ephones. I have taken the liberty of removing those ephones if you believe that will help.

Attachments:

Just to clarify and make sure we are testing the same thing, we are starting with the phone with DN 203 turned off, then we start the application. Once we have received the ADDRESS_ACTIVATION_FAILED message, we turn the phone on and never receive any notifications about it.

Hi Luke,

There is a mismatch in the mac address mentioned in the source code and configured in the router.

From configs:
-------------
!
ephone-dn 12 dual-line
session-server 1
number 203 no-reg primary
label 203
description 203
name 203
cti watch
allow watch
!
!
ephone 12
device-security-mode none
mac-address 0026.CB3B.0125
ephone-template 19
keyphone
type 7962
button 1:15
!
!

From source code:
-----------------
CMEAbstractAddress address = cmeProvider.createAddress("203", CMEAbstractAddress.Type.USER);
CMEAbstractTerminal terminal = cmeProvider.createTerminal("001C58CD131D", CMEAbstractTerminal.Type.PHONE, "SEP001C58CD131D");


Please change the mac address accordingly and give a try.

Thanks,
Anusha

If the ephone-dn status is DOWN or there¿s no physical phone associate with the number, the cti session will not be granted. If you want to monitor a number before the phone is registered to the CME. You need to configure ¿cti notify¿ under ephone-dn and use virtual terminal type. This is designed for Extension mobility usage which can be used here as well. The cti session will have no MAC associated. Once the phone register or EM user login, CME will send Back-In-Service notice to the session and associate the phone MAC to the cti session. BTW, the ¿cti notify¿ CLI will keep the dn in ¿UP¿ status.



Thanks,

Howard





From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Thursday, September 08, 2011 9:39 AM
To: cdicuser@developer.cisco.com
Subject: New Message from Luke Krouse in UC Express Services Interface - Technical Questions: RE: ADDRESS_ACTIVATION_FAILED and how to monitor when a phone registers



Luke Krouse has created a new message in the forum "Technical Questions":

--------------------------------------------------------------

Hi Luke,

There is a mismatch in the mac address mentioned in the source code and configured in the router.

From configs:
-------------
!
ephone-dn 12 dual-line
session-server 1
number 203 no-reg primary
label 203
description 203
name 203
cti watch
allow watch
!
!
ephone 12
device-security-mode none
mac-address 0026.CB3B.0125
ephone-template 19
keyphone
type 7962
button 1:15
!
!

From source code:
-----------------
CMEAbstractAddress address = cmeProvider.createAddress("203", CMEAbstractAddress.Type.USER);
CMEAbstractTerminal terminal = cmeProvider.createTerminal("001C58CD131D", CMEAbstractTerminal.Type.PHONE, "SEP001C58CD131D");


Please change the mac address accordingly and give a try.

Thanks,
Anusha





Anusha,

I think that you are looking at the wrong ephone configuration. ephone 12 is referring to ephone-dn 15. We are working on ephone 6. Which points correctly to ephone-dn 12.

<pre>ephone 6
device-security-mode none
video
mac-address 001C.58CD.131D
ephone-template 19
keyphone
max-calls-per-button 4
type 7921
button 1:12

ephone-dn 12 dual-line
session-server 1
number 203 no-reg primary
label 203
description 203
name 203
cti watch
allow watch

</pre>
--
To respond to this post, please click the following link:

<http://developer.cisco.com/web/ucxapi/forums/-/message_boards/view_message/4461296>

or simply reply to this email.

Howard,

The issue I see with that is that we never get notified when the phone is DOWN. Since CUCME maintains the UP status we always assume that the phone still occupies that IP, however, if the phone is off for several days, a new phone could grab that IP and then we have 2 phones with the same IP.