05-04-2022 11:45 AM
Newbie glorified end user holding no Cisco Cert's. Selected the wrong device prior to initiating Super Copy of a 8851. After Super Copy completed, deleted copied device. Selected correct device. Ran Super Copy. Message on LCD, "Telephone service not available." CUCM indicates new device status "Rejected". Deleted new device. Factory Reset new device. Try Super Copy again. Same result. New device "Rejected". I tried a 2nd 8851. It too gets rejected. NEED HELP! Thank you.
Solved! Go to Solution.
05-04-2022 12:17 PM
Please share a photo of the label on the back of your phone and a screenshot of your device configuration in CM.
05-04-2022 10:38 PM
There are couple of things to check.
05-05-2022 05:39 AM
I am assuming that there is no auto registration configured. Is that correct? It does take a moment for everything to propagate before the phone config is registered. My suggestion would be to have the phone not connected to the network until everything is ready. You could even take a more extreme (but not service affecting) step of restarting the TFTP service on each of the CM nodes. After that is complete, then plug the phone in. If it still fails, it is likely a problem with the device type as @Nithin Eluvathingal mentioned. If you see it with a "registration rejected message" in CM, click on the phone IP and see what shows in the phone logs. That should give you an idea where to go. Failing that, why not just create a new phone with the MAC in question and see if you can get the phone to register? Debug one thing at a time.
05-04-2022 12:17 PM
Please share a photo of the label on the back of your phone and a screenshot of your device configuration in CM.
05-05-2022 05:49 AM
Roger, Thank you for reaching out. I figured out the issue was me. I reference the wrong phone model. Frank
05-04-2022 10:38 PM
There are couple of things to check.
05-05-2022 05:49 AM
Nithin, Thank you for reaching out. I figured out the issue was me. I reference the wrong phone model. Frank
05-05-2022 05:39 AM
I am assuming that there is no auto registration configured. Is that correct? It does take a moment for everything to propagate before the phone config is registered. My suggestion would be to have the phone not connected to the network until everything is ready. You could even take a more extreme (but not service affecting) step of restarting the TFTP service on each of the CM nodes. After that is complete, then plug the phone in. If it still fails, it is likely a problem with the device type as @Nithin Eluvathingal mentioned. If you see it with a "registration rejected message" in CM, click on the phone IP and see what shows in the phone logs. That should give you an idea where to go. Failing that, why not just create a new phone with the MAC in question and see if you can get the phone to register? Debug one thing at a time.
05-05-2022 05:50 AM
Elliot, Thank you for reaching out. I figured out the issue was me. I reference the wrong phone model. Frank
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