08-22-2017 06:55 AM - edited 03-17-2019 11:02 AM
I have an 8821 which has registered against our Cluster no problem after the relevant device pack was installed and cluster wide reload etc..
Every few minutes (3 it seems) it disconnects and "Telephone Service is unavailable" message appears on screen.
Looking at the status messages (See below) this appears every time - It seems to be on the "Failback" message it happens.
However, if I make a call from the phone and leave the call open, the call never disconnects and stays open at both ends. I left it for 10 mins to test.
Is there some sort of keep alive for the SIP phone that i can amend? It seems to be related to something time senstive and the disconnects are happening within the same timeframe down to the minute.
Anyone? :-)
[14:29:59 22/08/17] SEP009AD2F05E4E.cnf.xml.sgn(HTTP)
[14:30:02 22/08/17] VPN not configured
[14:30:04 22/08/17] Error updating locale
[14:30:06 22/08/17] TFTP error : WLANRootCA.cer.sgn
[14:30:07 22/08/17] Phone-Reg-Rej
[14:30:10 22/08/17] ITL installed
[14:30:11 22/08/17] SEP009AD2F05E4E.cnf.xml.sgn(HTTP)
[14:30:13 22/08/17] VPN not configured
[14:30:15 22/08/17] Error updating locale
[14:30:17 22/08/17] TFTP error : WLANRootCA.cer.sgn
[14:32:22 22/08/17] Failback
[14:32:24 22/08/17] ITL installed
[14:32:26 22/08/17] SEP009AD2F05E4E.cnf.xml.sgn(HTTP)
08-22-2017 08:01 AM
Can you attach the phone console logs?
You can change the CM detectin failure in phone config from "normal "to "delayed" it you want the phone to wait more before keepalive failure.
Also check if correct phone button template is applied and disable is any expansion module is added to test.
08-22-2017 08:27 AM
08-22-2017 08:57 AM
Log says possible config issue as cucm is rejecting the registration with reason code 24.
Please can you disable any add on modules if any and make sure correct config is assigned for the phone model.
============================================================
1763 NOT Aug 22 16:15:06.016817 JAVA-SIPCC-SIP_REG: ccsip_handle_ev_4xx: SIP_REG_FAILURE_POSSIBLE_UCM_CONFIG_ISSUE - Received 4xx in ccm mode. Setting registration_reject to TRUE.
1764 NOT Aug 22 16:15:06.017012 JAVA-SIPCC-SIP_CC_PROV: ccsnap_gen_deviceEvent: event type : NOTIFYPROMPT
1765 ERR Aug 22 16:15:06.017241 JAVA-%Telephone service is unavailable
1767 NOT Aug 22 16:15:06.020363 JAVA-Thread-6|JPlatUi:setUnregReason - new unregister-reason:24
08-22-2017 09:21 AM
Hi Deepak,
Phone does seem to be configured OK as it does register with the CUCM Cluster and I am able to make calls, it just seems to lose connectivity every 3 minutes or so. I know it is not the actual WiFi as when on a call I can sit on it for as long as I want without any disconnections. It is puzzling to say the least.
I followed the document below - This is the wireless cisco mobile device and I can't see any option in the cucm config for add on modules to disable the option
02-09-2018 07:29 AM
Did this problem ever get resolved. Seems we are having the same issue. I am using the 8821 standard phone button template. Just seems odd that phone works then disconnects over and over again.
telephone service is unavailable
ReasonForOutOfServiceText=LastTimeFailback
ITL_TFTP_Server=OCCUCMSUB.ohiomachinery.comStatusCode=3
ReasonForOutOfServiceText=LastTimePhoneRegRej
02-09-2018 07:38 AM
We never got this resolved. We bought the wireless phone to get round a problem we were having. Fortunately we solved the problem and no longer required the wireless phone. It was a complete pain as you probably know 🙂. What wireless environment do you have? Cisco based? I would get this logged with TAC. I would also be interested in how you get on with the problem. Please keep me updated if you can.
02-09-2018 07:46 AM
03-06-2018 09:26 AM
Hi There,
Did you get anywhere with this at all?
05-24-2018 03:25 PM
I am having the exact same issue but we are testing Meraki wifi at the moment.
06-05-2018 08:29 PM
Any luck?
09-27-2018 05:43 AM
I seem to be having the same issue, however, it's only happening on one phone: Mine... We've got about 75 of these deployed and I haven't had any SR's submitted relating to this issue, but i'm curious to know what caused it on mine of all phones.. If I come across a solution, or am able to nail down the cause, I'll be sure to update this thread.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide