We are trying to deploy the push2phone application and when the web admin (a developer)tries to push a message to the phone, he gets a CiscoIPPhoneError with a value of 4. Checked the enterprise paramaters and found that the URL Authentication value is set for http://x.x.x.x:8080/ccmcip/authenticate.jsp. I have associated with his phone for him to push the message. Still it does not work. Need to know what I am doing wrong here. Thanks in advance.
Hey, does the developer authenticate when he is pushing? and the userid/password have a device association with the ipphone?
try this yourself 1st;
from a browser, go to an ipphone;
you should get a pop up, enter the userid and password of the user that the developer is using and see what happens (you should get a screenshot if it's i.e. a 3rd gen phone like 7941)
I am not 100% sure however if you can authenticate with an end user, or if it needs to be an application user...haven't tried, I always use an application user with no roles, and only a device association with all ipphones...
It does not show anything. I tried the same in another call manager and now the error code is 0. what does this authentication URL do? No help from the call manager page. :(
when you try to send a request to the ipphone, it will authenticate against the callmanager to verify you are allowed to do this.
what happens if you paste the url from enterprise parameters in your web browser?
In your authentication URL, if you have host name (as opposed to IP address), that might be causing this problem. I have seen it a few times and by changing the host name to IP fixed it. You will need to reboot the phones to make it effective.
I find that the authentication URL is using ip address instead of the DNS. I will try rebooting the phone and see if it fixes the problem. I tried extension mobility feature and it works like charm. Hopefully it also takes the same authentication URL for the phone. let me see how far this goes.
We found issues with the built-in authentication in CUCM, specially in 4.x days. We have developed our own authentication for PhoneTop Messenger product.
Yep. I am one of the lead developers.
This award-winning product is really easy to install and manage. It does audio paging, wave file broadcast, text notification, weather alerts, Amber alerts, surveys and more. You can download the eval. copy to play with.
Finally I got the ip phone error 4 to go away. Since our system was using LDAP for authentication, it was looking for case-sensitive user ids (in my case all caps). I have seen this happening with IPCC Express server and the CCM user pages and administration pages work just fine with lower case letters for authentication. Only the phone and IPCC servers (as far as I can see) look for case-sensitive user ids when authentication is done using LDAP. Interestingly, i have reported to the TAC and they are filing a defect case with the engineering team. hope it is corrected in the up-coming versions. :)