<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
..shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>This is TAC supported and the main configuration
for third party CDR server applications. We have a 3<sup>rd</sup> party CDR
reporting product that access the CDR database using SQL Server Authentication
and we got the okay from the Cisco CallManager developers and confirmation that
the servers will continue to be a TAC supported system.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Aman Chugh<br>
<b><span style='font-weight:bold'>Sent:</span></b> Monday, September 18, 2006
3:07 PM<br>
<b><span style='font-weight:bold'>To:</span></b> Mike Lay (milay)<br>
<b><span style='font-weight:bold'>Cc:</span></b> cisco-voip@puck.nether.net<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [cisco-voip] Is it
safe to use SQL Server Authenticationinstead ofWindows Authentication?</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>I would suggest not to change it as if you apply any callmanager
upgrades or service releases those check the database authentication setting
and might cause it to fail,Also I am sure this not TAC supported.Creating a
windows user with rights on that database would be a easier way out <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>Aman<br>
<br>
<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><span class=gmailquote><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'>On 9/19/06, <b><span style='font-weight:bold'>Mike Lay
(milay)</span></b> <<a href="mailto:milay@cisco.com">milay@cisco.com</a>>
wrote:</span></font></span> <o:p></o:p></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>You can change this with no negative impact on the server performance.<br>
However this was changed as part of making the server more secure. <br>
<br>
Mike<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>
[mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net
</a>] On Behalf Of Peter Pauly<br>
Sent: Monday, September 11, 2006 12:25 PM<br>
To: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
Subject: [cisco-voip] Is it safe to use SQL Server Authentication <br>
instead ofWindows Authentication?<br>
<br>
I want to access the CDR database from outside CallManager. Is is safe<br>
to change the database properties from "Use Windows Authentication"
to<br>
"Use SQL Server Authentication"? <br>
<br>
Would it be better to leave it as is and create a local windows account?<br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net </a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck..nether.net/mailman/listinfo/cisco-voip</a><br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck..nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
</body>
</html>
<HTML><BODY><P><hr size=1></P><br>
<P><STRONG><br>
Disclaimer:<br>
<br>
This e-mail communication and any attachments may contain<br>
confidential and privileged information and is for use by the<br>
designated addressee(s) named above only. If you are not the<br>
intended addressee, you are hereby notified that you have received<br>
this communication in error and that any use or reproduction of<br>
this email or its contents is strictly prohibited and may be<br>
unlawful. If you have received this communication in error, please<br>
notify us immediately by replying to this message and deleting it<br>
from your computer. Thank you.<br>
</STRONG></P></BODY></HTML>