[cisco-voip] CCM 6.1 Node Configuration Data for Certificate

[Jonathan Charles]

What kind of security do you think there is on the other end of that
SIP provider?

Just curious...



Jonathan

On Tue, Apr 15, 2008 at 5:37 PM, STEVEN CASPER <SCASPER at mtb.com> wrote:
>
>
> sigh.......I know, but I am a customer running a VoIP implementation at a
> large financial institution. If added security is available for any
> application it will be considered. Also maybe not anytime soon but I think
> the days of the Butt Set and the 66 block and its cousins are numbered for
> large enterprise PSTN customers. Centralized or regional SIP trunking holds
> a lot of promise both feature wise and financially. Just my two cents.
>
>  So all Certificate Signing Request related fields common across servers or
> not? Then again it seems you would set them up for the appropriate State and
> building location...and I wonder what unit is supposed to designate!
>
> Steve
>
> >>> "Jonathan Charles" <jonvoip at gmail.com> 4/15/2008 12:51 PM >>>
>
>
> You will?
>
> Why?
>
> Any time a cust says they want security, I pull out a Butts set and go
> to their 66 block.... you can do the same thing at telco...
>
>
>
> Jonathan
>
> On Tue, Apr 15, 2008 at 11:46 AM, STEVEN CASPER <SCASPER at mtb.com> wrote:
> >
> >
> > Thanks Jonathan,
> >
> > That is one of my concerns. I imagine at some point in the future I will
> > need to secure the phones. So it sounds like these fields should match
> > across servers if possible.....?
> >
> > >>> "Jonathan Charles" <jonvoip at gmail.com> 4/15/2008 11:13 AM >>>
> >
> >
> > This info is just for the TLS certificate for the web page... it would
> > be cool if it matched across nodes, but it doesn't matter, unless you
> > are securing your phones too...
> >
> >
> >
> > Jonathan
> >
> > On Tue, Apr 15, 2008 at 9:54 AM, STEVEN CASPER <SCASPER at mtb.com> wrote:
> > >
> > >
> > > Question about a couple of parameters associated with setting up the
> > > Certificate Signing Request during the 6.1 upgrade. These are:
> > >
> > > Country
> > > Location
> > > Organization
> > > State
> > > Unit
> > >
> > > Does it matter if this info is identical across Call Manager servers or
> > > should at least one field be unique?
> > >
> > > Thanks!
> > > Steve
> > >
> > >
> > >
> > >
> > >
> > > ************************************
> > >  This email may contain privileged and/or confidential information that
> is
> > > intended solely for the use of the addressee. If you are not the
> intended
> > > recipient or entity, you are strictly prohibited from disclosing,
> copying,
> > > distributing or using any of the information contained in the
> > transmission.
> > > If you received this communication in error, please contact the sender
> > > immediately and destroy the material in its entirety, whether electronic
> > or
> > > hard copy. This communication may contain nonpublic personal information
> > > about consumers subject to the restrictions of the Gramm-Leach-Bliley
> Act
> > > and the Sarbanes-Oxley Act. You may not directly or indirectly reuse or
> > > disclose such information for any purpose other than to provide the
> > services
> > > for which you are receiving the information.
> > >  There are risks associated with the use of electronic transmission. The
> > > sender of this information does not control the method of transmittal or
> > > service providers and assumes no duty or obligation for the security,
> > > receipt, or third party interception of this transmission.
> > >  ************************************
> > >
> > > _______________________________________________
> > >  cisco-voip mailing list
> > >  cisco-voip at puck.nether.net
> > >  https://puck.nether.net/mailman/listinfo/cisco-voip
> > >
> > >
> >
> >
> >
> >
> >
> > ************************************
> >  This email may contain privileged and/or confidential information that is
> > intended solely for the use of the addressee. If you are not the intended
> > recipient or entity, you are strictly prohibited from disclosing, copying,
> > distributing or using any of the information contained in the
> transmission.
> > If you received this communication in error, please contact the sender
> > immediately and destroy the material in its entirety, whether electronic
> or
> > hard copy. This communication may contain nonpublic personal information
> > about consumers subject to the restrictions of the Gramm-Leach-Bliley Act
> > and the Sarbanes-Oxley Act. You may not directly or indirectly reuse or
> > disclose such information for any purpose other than to provide the
> services
> > for which you are receiving the information.
> >  There are risks associated with the use of electronic transmission. The
> > sender of this information does not control the method of transmittal or
> > service providers and assumes no duty or obligation for the security,
> > receipt, or third party interception of this transmission.
> >  ************************************
> >
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
>
>
> ************************************
>  This email may contain privileged and/or confidential information that is
> intended solely for the use of the addressee. If you are not the intended
> recipient or entity, you are strictly prohibited from disclosing, copying,
> distributing or using any of the information contained in the transmission.
> If you received this communication in error, please contact the sender
> immediately and destroy the material in its entirety, whether electronic or
> hard copy. This communication may contain nonpublic personal information
> about consumers subject to the restrictions of the Gramm-Leach-Bliley Act
> and the Sarbanes-Oxley Act. You may not directly or indirectly reuse or
> disclose such information for any purpose other than to provide the services
> for which you are receiving the information.
>  There are risks associated with the use of electronic transmission. The
> sender of this information does not control the method of transmittal or
> service providers and assumes no duty or obligation for the security,
> receipt, or third party interception of this transmission.
>  ************************************
>