[cisco-voip] Selfprovisioning

[Pawlowski, Adam]

I know I'm dredging this one up, but to contribute to the knowledge base here - the IVR service will log a message with "isAlreadyProvisioned" anyways, regardless of if it is or if it isn't. 

The error message about associating the device to the account is related to the end user profile in some regard. I have one that works, and one that doesn't. The only differences being that there are already devices associated with one of them and a primary extension. I'll play with it more later, but this one wasted a bunch of my time already today - the IVR service doesn't log any clear message at the default trace level anyways as to why it plays that recording back. This occurs prior to asking for the PIN so there's clearly some qualifier there.

Regards,

Adam P
SUNYAB

>>>

Tired that there was a SCCP template that I deleted but still no go. 


Leslie Meade 


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

From: Ryan Ratliff (rratliff) [mailto:rratliff [at] cisco] 
Sent: Friday, July 11, 2014 11:10 AM 
To: Leslie Meade 
Cc: Bill Riley; cisco-voip voyp list 
Subject: Re: [cisco-voip] Selfdeployment 

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<mailto:Leslie.Meade [at] lvs1>> 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<mailto:leslie.meade [at] lvs1> 

From: Bill Riley [mailto:bill [at] hitechconnection] 
Sent: Friday, July 11, 2014 10:46 AM 
To: Leslie Meade; cisco-voip (cisco-voip [at] puck<mailto:cisco-voip [at] puck>) 
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<mailto:cisco-voip [at] puck> 

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






_______________________________________________ 

cisco-voip mailing list 

cisco-voip [at] puck<mailto:cisco-voip [at] puck> 

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

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