[cisco-voip] CTL/Security Token question

[Jason Aarons (AM)]

I would call TAC, installing a new CTL would mean visiting each phone (or use UnifiedFX) and resetting the CTL. Not something you want to have happen.

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Antonio Soares
Sent: Thursday, May 05, 2011 7:38 AM
To: 'Wes Sisk'; 'Ed Leatherman'
Cc: 'Cisco VOIP'
Subject: Re: [cisco-voip] CTL/Security Token question

I have a customer that failed the Security Token Password 3 times and now the token is locked.
Anyone knows how to solve this problem ?
Do I need to replace the token via RMA ?


Thanks.
Regards,

Antonio Soares, CCIE #18473 (R&S/SP)
amsoares at netcabo.pt
http://www.ccie18473.net



-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Wes Sisk
Sent: segunda-feira, 4 de Abril de 2011 16:45
To: Ed Leatherman
Cc: Cisco VOIP
Subject: Re: [cisco-voip] CTL/Security Token question

We do this in our labs.  Just be careful to keep track of password changes.  Using the tokens requires a password.  Guess the wrong password too many times and they do self destruct.  This would effectively lock you out of all clusters that use that key.

Regards,
Wes

On 4/4/2011 10:27 AM, Ed Leatherman wrote:
> Hello,
>
> I'm doing some studying on control/media encryption for call manager, 
> and was wondering if someone could answer a (hopefully simple) 
> question about signing CTL's. Does the act of signing a CTL actually 
> affect the security token(s) in any way? Can I buy a set of security 
> tokens, use them to configure everything on lab CM, and then re-use 
> the same tokens in production?
>
> The documentation seems to infer this (along with a best practice of 
> building in test first), but it doesn't come right out and say you can 
> reuse the same tokens. Would be kind of goofy if it locked them to a 
> particular cluster some how and I don't think that's the case. I was 
> hoping for a bit of confirmation though.
>
> Thanks!
>
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

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

-----------------------------------------
Disclaimer:

This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only.  If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful.  If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110505/e51fa5cf/attachment.html>