[cisco-voip] Selfdeployment

[Ryan Ratliff (rratliff)]

Look and see if a phone button template for that phone is hanging around.

This sql query may be handy:
select pt.name from phonetemplate pt where pt.name matches '*-Individual Template' and not exists (select 1 from device where fkphonetemplate = pt.pkid)

-Ryan

On Jul 11, 2014, at 1:53 PM, Leslie Meade <Leslie.Meade at lvs1.com<mailto:Leslie.Meade at lvs1.com>> wrote:

Yea the profile is not the default one but the system still tells me that it cannot be attached to the profile.
I delete the phone and set it to auto register again and still get the same thing



Leslie Meade


..................................................................
Mobile:778.228.4339 | Main: 604.676.5239
Email: leslie.meade at lvs1.com<mailto:leslie.meade at lvs1.com>

From: Bill Riley [mailto:bill at hitechconnection.net]
Sent: Friday, July 11, 2014 10:46 AM
To: Leslie Meade; cisco-voip (cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>)
Subject: Re: [cisco-voip] Selfdeployment

Sorry, you should assign a user profile to the user that is not the system default.

On 7/11/2014 12:34 PM, Bill Riley wrote:
Does the phone auto-register again?

Also I believe the work around is to not use a profile that is not the default and assign it to the user?

On 7/11/2014 11:33 AM, Leslie Meade wrote:
While I wait on a response back form TAC.

CUCM 10.5 with self-deployment running. I got one phone registered and it worked well. Then I decided to delete that phone and test it again.
Now I get the error of “This device could not be associated to your account. Please contact the System administrator to complete provisioning.”

I have used this doc.. and made sure that the UDT is on the user profiles.

I am also aware of the bug that states that the standard/default profiles can be broken and the work around is to manual create them or assign them to the user.

I look at the debug and see the devices that I am trying to register report that “SEP005056911998 ~ 1033/2 ~  inside isAlreadyProvisioned”
I assume that this is what is causing it to fault.

Any ideas ?






_______________________________________________

cisco-voip mailing list

cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>

https://puck.nether.net/mailman/listinfo/cisco-voip





_______________________________________________

cisco-voip mailing list

cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>

https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140711/0a3b3310/attachment.html>