This document was generated from CDN thread
Created by: Stefania Oliviero on 24-06-2013 08:58:49 AM
Hi to all,
We have some problem with som IPPhones we are monitoring via CTI. SOme phones stilll works moreover.
I don't know what happened but I can't receive CiscoTermInServiceEv and CiscoAddrInServiceEv after we add the observers.
Below you can find my application (test) logs, where SEP0C8525A67EAB never goes InService, while SEP08D09F9ECDEB works well.
Both IPPhones worked well untill yesterday. No changes were made....
Terminal:SEP0C8525A67EAB - class com.cisco.jtapi.TerminalImplAdding Call observer to address 6506Adding Adddress Observer to address 6506Adding Terminal Observer to TerminalSEP0C8525A67EABAdding Call observer to address 6506Adding Adddress Observer to address 6506Adding Terminal Observer to TerminalSEP0C8525A67EABReceived (P1-atmUser) [6506
TDN_Phones_65xx] CiscoAddrOutOfServiceEv [#2] Cause:100 CallCtlCause:0 CiscoCause:0 FeatReason:12for 6506Terminal:SEP08D09F9ECDEB - class com.cisco.jtapi.TerminalImplReceived (P1-atmUser) [SEP0C8525A67EAB] CiscoTermOutOfServiceEv [#3] Cause:100 CallCtlCause:0 CiscoCause:0 FeatReason:12for SEP0C8525A67EAB
Adding Call observer to address 6553Adding Adddress Observer to address 6553Adding Terminal Observer to TerminalSEP08D09F9ECDEBReceived (P1-atmUser) [6553TDN_Phones_65xx] CiscoAddrOutOfServiceEv [#6] Cause:100 CallCtlCause:0 CiscoCause:0 FeatReason:12for 6553Adding Call observer to address 6553Adding Adddress Observer to address 6553Adding Terminal Observer to TerminalSEP08D09F9ECDEBReceived (P1-atmUser) [6553TDN_Phones_65xx] CiscoAddrOutOfServiceEv [#6] Cause:100 CallCtlCause:0 CiscoCause:0 FeatReason:12for 6553Received (P1-atmUser) [6553TDN_Phones_65xx] CiscoAddrInServiceEv [#7] Cause:100 CallCtlCause:0 CiscoCause:0 FeatReason:12for 6553Received (P1-atmUser) [SEP08D09F9ECDEB] CiscoTermInServiceEv [#8] Cause:100 CallCtlCause:0 CiscoCause:0 FeatReason:12for SEP08D09F9ECDEB
Subject: RE: Can't receive CiscoTermInServiceEv or CiscoAddrInServiceEv,
Replied by: David Staudt on 24-06-2013 10:35:28 AM
Assuming the device is actually in-service/registered...?
It would be informative to restart some components (one by one) and see if/when you are able to recover function: device, application, CTI Manager service, Callmanager service.
Depending on your UCM version, I believe there have been a few defects which can result in devices not coming up in CTI in certain rare scenarios. It would be good to upgrade to the latest UCM version available (upgrading JTAPI on the app to the corresponding version) if possible.
For detailed troubleshooting or verification of a defect, please open a CDN Developer Support case:
http://developer.cisco.com/web/memberservices/support
If the issue can be recovered by restarting a UCM service, and then re-appears after a time, it would be best to collect JTAPI, CTI Manager, and Callmanager logs from the time of component restart until the problem arises (attach to case.)
Created by: Stefania Oliviero on 24-06-2013 08:58:49 AM
Hi to all,
We have some problem with som IPPhones we are monitoring via CTI. SOme phones stilll works moreover.
I don't know what happened but I can't receive CiscoTermInServiceEv and CiscoAddrInServiceEv after we add the observers.
Below you can find my application (test) logs, where SEP0C8525A67EAB never goes InService, while SEP08D09F9ECDEB works well.
Both IPPhones worked well untill yesterday. No changes were made....
Terminal:SEP0C8525A67EAB - class com.cisco.jtapi.TerminalImplAdding Call observer to address 6506Adding Adddress Observer to address 6506Adding Terminal Observer to TerminalSEP0C8525A67EABAdding Call observer to address 6506Adding Adddress Observer to address 6506Adding Terminal Observer to TerminalSEP0C8525A67EABReceived (P1-atmUser) [6506
TDN_Phones_65xx] CiscoAddrOutOfServiceEv [#2] Cause:100 CallCtlCause:0 CiscoCause:0 FeatReason:12for 6506Terminal:SEP08D09F9ECDEB - class com.cisco.jtapi.TerminalImplReceived (P1-atmUser) [SEP0C8525A67EAB] CiscoTermOutOfServiceEv [#3] Cause:100 CallCtlCause:0 CiscoCause:0 FeatReason:12for SEP0C8525A67EABAdding Call observer to address 6553Adding Adddress Observer to address 6553Adding Terminal Observer to TerminalSEP08D09F9ECDEBReceived (P1-atmUser) [6553
TDN_Phones_65xx] CiscoAddrOutOfServiceEv [#6] Cause:100 CallCtlCause:0 CiscoCause:0 FeatReason:12for 6553Adding Call observer to address 6553Adding Adddress Observer to address 6553Adding Terminal Observer to TerminalSEP08D09F9ECDEBReceived (P1-atmUser) [6553TDN_Phones_65xx] CiscoAddrOutOfServiceEv [#6] Cause:100 CallCtlCause:0 CiscoCause:0 FeatReason:12for 6553Received (P1-atmUser) [6553TDN_Phones_65xx] CiscoAddrInServiceEv [#7] Cause:100 CallCtlCause:0 CiscoCause:0 FeatReason:12for 6553Received (P1-atmUser) [SEP08D09F9ECDEB] CiscoTermInServiceEv [#8] Cause:100 CallCtlCause:0 CiscoCause:0 FeatReason:12for SEP08D09F9ECDEBSubject: RE: Can't receive CiscoTermInServiceEv or CiscoAddrInServiceEv,
Replied by: David Staudt on 24-06-2013 10:35:28 AM
Assuming the device is actually in-service/registered...?
It would be informative to restart some components (one by one) and see if/when you are able to recover function: device, application, CTI Manager service, Callmanager service.
Depending on your UCM version, I believe there have been a few defects which can result in devices not coming up in CTI in certain rare scenarios. It would be good to upgrade to the latest UCM version available (upgrading JTAPI on the app to the corresponding version) if possible.
For detailed troubleshooting or verification of a defect, please open a CDN Developer Support case:
http://developer.cisco.com/web/memberservices/support
If the issue can be recovered by restarting a UCM service, and then re-appears after a time, it would be best to collect JTAPI, CTI Manager, and Callmanager logs from the time of component restart until the problem arises (attach to case.)