Hello everyone,
We've been facing issues with JTAPI implementation on our simple call app.
Basically, The application is working fine most of the time, but sometimes there's the error: Address is out service in the call events.
We are using a hardware device IP cisco phone that the app is controlling, the phone is responsible for its own media registration with UCM automatically.
The app suddenly 3 o 4 agents begin to have issues with Address is out service on all calls, but the other agents continue working fine, then the next day agents has no issues at all.
It seems like sporadic issue.
we don't know the cause of this strange behavior, has somebody faced this issue before?
Error log:
outOfServ CAUSE:100 META-CODE: 136
com.cisco.jtapi.InvalidStateExceptionImpl: Address is out of service
Any ideas, might this issue came up from call manager as itself or might be the implementation that we used?.
JTAPI LIB INFO:
Specification-Version: 1.2
Implementation-Version: 11.5(1.14900)-10 Release
Our implementation is based on, cisco JTAPI example guide: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/jtapi_dev/9_0_1/jtapidevguide/examples.pdf
Also, we already reviewed:
https://community.cisco.com/t5/collaboration-documents/the-famous-address-is-out-of-service/ta-p/3615226
#CUCM
#VOIP
