« Back to Technical Questions

CME UCXSI phone_ready issues

Combination View Flat View Tree View
Threads [ Previous | Next ]
CME UCXSI phone_ready issues
cme ucsxi phone_ready
Answer
8/31/11 3:42 PM
All,
 
I am experiecing odd behavior when integrating with my CME router using UCXSI. There are times when my phones go offline and when they come back online the phone_ready status is 'false'. Other times that same phone will drop off and on and will have a status of 'true'. Our integration is configured that when a phone successfully registers that the phone_ready status will be set to 'true', any help would be greatly appreciated. Below are some examples:


mac: E05FB9BC3710
device_ip_address: 10.159.160.253
device_model: 7925
device_product: 3
term_key_phone: true
device_name: SEPE05FB9BC3710
address_id: 264
device_description: Cisco IP Phone 7925
dir_status: true
device_status: registered
address_state: idle
dir_number: 0909
phone_ready: false

2011-08-30 14:30:00,586 DEBUG: Phone not added to the inventory
 
Other times it is set to 'true'


address_id": "8",
address_state":
"idle",
device_description": "IP
Phone 7921",
device_ip_address":
"10.42.18.81",
device_model": 7925,
device_model_string":
"Cisco ",
device_name":
"SEP001C58CD131D",
device_product": 6,
device_status": registered
dir_number": "4276",
dir_status": 1,
phone_ready": true,
term_key_phone":
"true"
2011-08-30 14:40:00,586 DEBUG: Phone added to the inventory
Flag

RE: CME UCXSI phone_ready issues
Answer
9/1/11 8:26 AM as a reply to Luke Krouse.
Hi Luke,

which UCXSI api's you are using to set and get the phone_ready status, is it ext staus ?, could you please send us your sample code to verify.

Thanks,
Raghavendra
Flag

RE: CME UCXSI phone_ready issues
Answer
9/1/11 2:08 PM as a reply to Luke Krouse.
Hi Luke,

which ucxsi api your are using ? could you please explain your complete call flow.

Thanks,
Raghavendra
Flag

RE: CME UCXSI phone_ready issues
Answer
9/1/11 3:07 PM as a reply to Raghavendra Gutty Veeranagappa.
Hi Luke,

which ucxsi api your are using ? could you please explain your complete call flow.

Thanks,
Raghavendra


 
We are using UCXSI SDK 1.0.1. The call flow is that when these devices are configured in CUCME with the appropriate configurations, our application monitors those phones and when they come online we allow other users to send messages to those phones. When the phones go offline, the users are not able to send messages to the phones. The issue that I am having is that even though the phone is online and registered properly in CUCME I am not getting the ADDRESS_ACTIVATION from the API which is required to make our integration work.
Flag

RE: CME UCXSI phone_ready issues
Answer
9/2/11 6:18 AM as a reply to Luke Krouse.
Hi Luke,

Thanks for explaining the call flow, i understand you are not getting ADDRESS_ACTIVATION even though you are phone is online and registered, is this problem occurs with one phone or for all the phones.

please send us the logs by enabling following debugs and also your running config to find the issue.

debug cti all
debug ccsip messages

Thanks,
Raghavendra
Flag

RE: CME UCXSI phone_ready issues
Answer
9/2/11 2:02 PM as a reply to Luke Krouse.
Hi Luke,

thanks for sharing logs and config,

Whenever a ephone-dn status goes from up to down (Eg phone shutdown, phone reset, user logout etc), an CMEOutOfServiceEvent is reported via CMECSTAListener.onNotification().

Whenever a ephone-dn status goes from down to up(Eg phone registers with CUCME, user login etc), a CMEBackInServiceEvent is reported via CMECSTAListener.onNotification().

so from the logs it clearly shows that when 4282 phone goes down it recieves OutOfServiceEvent and when 4282 phone goes up it recieves BackInServiceEvent , i did not find any issue with this.

BTW to receive ADDRESS_ACTIVATION event you need to use The CMEAbstractTerminal.addAddress() method it establishes an address-terminal object pair and
sends requests to CUCME for learning the status, capabilities and policies for this address-terminal pair.

Thanks,
Raghavendra
Flag