<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:m="http://schemas.microsoft.com/office/2004/12/omml" 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 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:2089381131;
mso-list-type:hybrid;
mso-list-template-ids:-2046508398 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</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=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>OK, I think I understand now:<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>This is an IP Communicator with 2 lines on it. Arc is a “Device”
centric application, so isn’t too specific around how many “lines”
you specifically have on a device. However, I know that associating a “device
with multiple lines” to the CUCM user should not cause such an issue.
Again, it sounds that the CTI Manager is getting confused – reporting devices
as Out_of_Service, and therefore the Arc Server cannot start…<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Could you try the following:<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>1)<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Start the Arc Server WITHOUT the IPC associated (should start
fine from what I understand)<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;
mso-list:l0 level2 lfo1'><![if !supportLists]><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>a.<span
style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Test
the system – put calls into queues and make sure it all works fine<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>2)<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>THEN, associate the IPC device – DO NOT RESTART THE ARC
SERVER<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;
mso-list:l0 level2 lfo1'><![if !supportLists]><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>a.<span
style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Test
the system again – put calls into queues again, does it still work as it
did before?<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>3)<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>If it does still work, stop/start the Arc Server – does it
come back up?<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;
mso-list:l0 level2 lfo1'><![if !supportLists]><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>a.<span
style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>If
not, send me the ICDInit.log file as mentioned before – should give an
indication as to where the problem is<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;
mso-list:l0 level2 lfo1'><![if !supportLists]><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>b.<span
style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>If
not, download the “TAPI Softphone” from <a
href="http://www.julmar.com">www.julmar.com</a> (freeware) – try and
control a CTI Port or IP Phone through this application and make a call to
another device – does it work?<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:1.5in;text-indent:-1.5in;
mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo1'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'><span style='font:7.0pt "Times New Roman"'>
</span>i.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>This application is nothing to do with Arc, and something we use
to narrow down issues like this – i.e. if it is a general CTI issue, or if
its specific to Arc applications<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>If possible, could you try this with real hardphone (i.e. valid
MAC address) instead of a softphone – wouldn’t mind seeing if this
is related to a dummy MAC address or not. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Either way, this is a CTI issue – the Arc Server doesn’t
seem to be able to control the CTI Ports (“Host PBX Gateway”
devices) when you have this device associated – the ICDInit.log file
should confirm this. Therefore, I don’t think VMWare will have a bearing
on this – it “shouldn’t” make a difference<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>On a different note, do you need to have this device associated
anyway? You don’t need to associate the device in order to be able to
transfer to it?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thanks<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><b><span lang=EN-GB style='font-size:11.0pt;font-family:
"Arial","sans-serif";color:navy'>Bennie Grant<br>
</span></b><i><span lang=EN-GB style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:navy'>VP - Operations<br>
</span></i><b><span lang=EN-GB style='font-size:11.0pt;font-family:"Arial","sans-serif";
color:navy'>Arc Solutions (International) Inc<br>
</span></b><span lang=EN-GB style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:navy'>Part of the Mettoni group | </span><span lang=EN-GB
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a
href="http://www.mettoni.com/"><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>www.mettoni.com</span></a>
<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> FrogOnDSCP46EF
[mailto:ciscoboy2006@gmail.com] <br>
<b>Sent:</b> Monday, May 18, 2009 10:06 PM<br>
<b>To:</b> Jason Burns<br>
<b>Cc:</b> Bennie Grant; cisco-voip voyp list<br>
<b>Subject:</b> Re: [cisco-voip] Arc Enterprise v504.485 with CUCM702<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>Hi Jason,<br>
Yes, its IP communicator and I have also tested with IPBLUE.<br>
CCM reckonises this device as a VALID and It registers okay with CCM. I have
tested another real phone with real MAC and issue is the same.<br>
<br>
Just did a fresh install and it's happening again. This could be coz I am
runing them in a VMWARE win2003?<br>
<br>
<o:p></o:p></p>
<div>
<p class=MsoNormal>On Tue, May 19, 2009 at 11:22 AM, Jason Burns <<a
href="mailto:burns.jason@gmail.com">burns.jason@gmail.com</a>> wrote:<o:p></o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>Is this device Cisco IP
Communicator? Is that why is has Device Name SEP888888888888? I think the
reason Bennie asked the question again is that 8888.8888.8888 is not a valid
MAC address to be assigned to a physical device.<o:p></o:p></p>
<div>
<div>
<div>
<p class=MsoNormal>On Mon, May 18, 2009 at 12:51 PM, FrogOnDSCP46EF <<a
href="mailto:ciscoboy2006@gmail.com" target="_blank">ciscoboy2006@gmail.com</a>>
wrote:<o:p></o:p></p>
</div>
</div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>
<div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'>Comments are inline below:<o:p></o:p></p>
<div>
<div>
<p class=MsoNormal>On Mon, May 18, 2009 at 11:28 PM, Bennie Grant <<a
href="mailto:Bennie.Grant@mettoni.com" target="_blank">Bennie.Grant@mettoni.com</a>>
wrote:<o:p></o:p></p>
<div>
<div>
<p><span style='font-size:11.0pt;color:#1F497D'>It would be the same theory
that I mentioned earlier – the CTI layer is getting confused for some
reason when we see 2 devices with the same MAC address. I could see why this
might happen, but I cant believe you’re the first person to be trying
this configuration!</span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'>I have the same question from
my previous email:</span><o:p></o:p></p>
<p style='margin-left:.5in;text-indent:-.25in'><span style='font-size:11.0pt;
color:#1F497D'>1)</span><span style='font-size:7.0pt;color:#1F497D'>
</span><span style='font-size:11.0pt;color:#1F497D'>Why do you have the same
MAC address (this 888888888888 number) – I just want to understand the
“real world application” for this config</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class=MsoNormal><br>
<FROG> hey Bernie, its one device SEP8888888888 with 2 lines 2002 and
3002. A user want operator to transfer a call on both DN's e.g. 9am to 2pm on
2002 DN (On same MAC/Device) and after 2pm to 3002. This is the
application. <o:p></o:p></p>
</div>
<div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>
<div>
<div>
<p style='margin-left:.5in;text-indent:-.25in'><span style='font-size:11.0pt;
color:#1F497D'>2)</span><span style='font-size:7.0pt;color:#1F497D'>
</span><span style='font-size:11.0pt;color:#1F497D'>Could you try changing the MAC
address of one of these devices by one digit, and see if this then works?</span><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<div>
<p class=MsoNormal><frog>No, I can't change MAC. The situation is one IP
phone device with 2DNs. <br>
I have tried with 3 phones - same result<o:p></o:p></p>
</div>
<div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>
<div>
<div>
<p><span style='font-size:11.0pt;color:#1F497D'>Also, when the issue happens,
could you look at the “ICDINIT.log” file – this file is the
“initialization” file that is created when the Arc Server starts,
and this may highlight some sort of error. However, from the earlier trace it
does look like the CTI Manager is sending “out of service” events
– so you may need to get TAC involved</span><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<div>
<p class=MsoNormal><frog> Can your TAC guys test this in the lab? -
1 phone/1mac with 2 lines and associate both lines with ARC_TAPI user.<br>
See if your lab version also getting the same issue. <o:p></o:p></p>
</div>
<div>
<div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>
<div>
<div>
<div>
<p><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'>Thanks</span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p><b><span lang=EN-GB style='font-size:11.0pt;color:navy'>Bennie Grant<br>
</span></b><i><span lang=EN-GB style='font-size:8.0pt;color:navy'>VP -
Operations<br>
</span></i><b><span lang=EN-GB style='font-size:11.0pt;color:navy'>Arc
Solutions (International) Inc<br>
</span></b><span lang=EN-GB style='font-size:8.0pt;color:navy'>Part of the
Mettoni group | </span><span lang=EN-GB style='font-size:11.0pt;color:#1F497D'><a
href="http://www.mettoni.com/" target="_blank"><span style='font-size:8.0pt'>www.mettoni.com</span></a>
</span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
</div>
<div style='border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0in 0in 0in;
border-color:-moz-use-text-color -moz-use-text-color'>
<p><b><span style='font-size:10.0pt'>From:</span></b><span style='font-size:
10.0pt'> FrogOnDSCP46EF [mailto:<a href="mailto:ciscoboy2006@gmail.com"
target="_blank">ciscoboy2006@gmail.com</a>] <br>
<b>Sent:</b> Sunday, May 17, 2009 11:57 AM<br>
<b>To:</b> Bennie Grant<br>
<b>Cc:</b> cisco-voip voyp list<br>
<b>Subject:</b> Re: [cisco-voip] Arc Enterprise v504.485 with CUCM702</span><o:p></o:p></p>
</div>
<div>
<div>
<p> <o:p></o:p></p>
<p style='margin-bottom:12.0pt'>Hi Bernie,<br>
Thanks for your detailed msg. <br>
the version i am using is 5.0.2(485)<br>
<br>
My observation are when I associate ARC_TAPI user with a Phone device which has
two different DN causes ARC CT-Server start/shutdown loop.<br>
<br>
The log I posted in previous mail had a device SEP888888888888 with 2002 and
3002 DN (not shared one).<br>
<br>
If I deassociate 3002 from ARC_TAPI user then CT server is all good. I just
tested it again and when I associated 3002 it start shutingdown / coming up
automatically and its kinda loop.<br>
<br>
Somehow single MAC with 2 different DN are tricking CTserver.<br>
<br>
I have tried adding real phone with 2 DN and the CT server behaves the same. <br>
<br>
-frog<br>
<br>
<o:p></o:p></p>
<div>
<p>On Mon, May 18, 2009 at 12:26 AM, Bennie Grant <<a
href="mailto:Bennie.Grant@mettoni.com" target="_blank">Bennie.Grant@mettoni.com</a>>
wrote:<o:p></o:p></p>
<div>
<div>
<p><span style='font-size:11.0pt;color:#1F497D'>Hey Frog</span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'>Couple of things for you:</span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'>The CTI Server is not essential.
This is a new module that allows the BLF to scale clusterwide – using the
TAPI Superprovider feature on the CUCM. If you don’t want/need this, then
you don’t need the CTI Server. However, the CTI Server does also act as
the Server module for the Arc Click-to-Dial product, so if you want that
you’ll need this module too</span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'>To do with the Arc Server
shutting down automatically – it is worth understanding “why”
or “when” this will happen. The Arc Server will only automatically
shut itself down if the CTI communication with the CUCM is not working:</span><o:p></o:p></p>
<p style='text-indent:-.25in'><span style='font-size:11.0pt;color:#1F497D'>1)</span><span
style='font-size:7.0pt;color:#1F497D'> </span><span
style='font-size:11.0pt;color:#1F497D'>Either it cannot see ANY CTI Devices</span><o:p></o:p></p>
<p style='text-indent:-.25in'><span style='font-size:11.0pt;color:#1F497D'>2)</span><span
style='font-size:7.0pt;color:#1F497D'> </span><span
style='font-size:11.0pt;color:#1F497D'>It can see the devices, but cannot
control the Host PBX Gateway (CTI Ports) – because they are “out of
service”, Cisco TAPI Wave Driver not installed correctly, etc etc</span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'>Specifically, if the Arc Server
cannot see/control the Host PBX Gateway devices FOR ANY REASON, then it will
automatically shut down the server module and try and restart itself. This is
because these devices are used for queuing the calls – if these devices
are not available, then the Arc Server cannot work. Therefore it shuts itself
down and tries to reinitialize the CTI Ports (on earlier versions of CUCM,
there was a bug that this often fixed)</span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'>So, associating two devices
with the same DN;s should have no impact on this whatsoever – I’ve
seen it done literally hundreds of times with no impact. </span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'>However, the CTI Port devices
must remain with unique DNs – so if the other devices has the same DN as
the CTI ports, then this will cause problems with the Cisco CTI Layer, and
therefore Arc will not be able to control the CTI Ports, and therefore the
server will not start…</span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'>Looking at the trace below, you
can see that the CTI layer (Cisco CTI Manager Service) is stating that the
devices are “out_of_service” (OOS) – which means that we
cannot control them. The question is, why are these devices going out of
service when you associate the extra device/line? This is something I
haven’t seen before, and something that TAC/DE would need to get involved
in if it is proven that this is the case. Because the devices are out of
service, Arc has no way to control anything on the CUCM and that’s why it
isn’t working…</span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'>All that being said though, why
do you have the same MAC address (this 888888888888 number) – I can
understand shared DN’s/lines – but of course this is impossible in
reality. It may be possible that you’ve stumbled across a CTI bug where
multiple duplicate MAC addresses cause the Cisco TSP to make devices OOS or something
similar.</span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'>What are these devices
you’re associating, are they regular phones or something else? Could you
try changing the MAC address of one of these devices by one digit, and see if
this then works?</span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'>On a separate note, which
version of Arc Enterprise do you have – there is no version 504 out
there? Our latest is v5.0.2…</span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'>Thanks</span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p><b><span lang=EN-GB style='font-size:11.0pt;color:navy'>Bennie Grant<br>
</span></b><i><span lang=EN-GB style='font-size:8.0pt;color:navy'>VP -
Operations<br>
</span></i><b><span lang=EN-GB style='font-size:11.0pt;color:navy'>Arc
Solutions (International) Inc<br>
</span></b><span lang=EN-GB style='font-size:8.0pt;color:navy'>Part of the
Mettoni group | </span><span lang=EN-GB style='font-size:11.0pt;color:#1F497D'><a
href="http://www.mettoni.com/" target="_blank"><span style='font-size:8.0pt'>www.mettoni.com</span></a>
</span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<div style='border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0in 0in 0in;
border-color:-moz-use-text-color'>
<p><b><span style='font-size:10.0pt'>From:</span></b><span style='font-size:
10.0pt'> <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>
[mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>]
<b>On Behalf Of </b>FrogOnDSCP46EF<br>
<b>Sent:</b> Sunday, May 17, 2009 5:12 AM<br>
<b>To:</b> cisco-voip voyp list<br>
<b>Subject:</b> [cisco-voip] Arc Enterprise v504.485 with CUCM702</span><o:p></o:p></p>
</div>
<div>
<div>
<p> <o:p></o:p></p>
<p><br>
Hi Guys,<br>
<br>
I was playing with the Arc 504 enterprise "arc connect CT server"
integration with CCM702.10000,18<br clear=all>
<br>
When there is a double line from same MAC address/device, ARC CT server is
going banana. It is keep shutting down the arc ct server and restarting it.<br>
Once I de-associated the 2nd line from ARC TAPI user in CCM, of same device
then its okay. it doesn't shut/restart.<br>
<br>
Q1: Is there any fix for this bug for Arc console? End user can easily do this
kind of mistake (associate both phone lines) and can loose the whole console.<br>
<br>
Q2: is CTI server from ARC is a must to install? I found its working without
Arc CTI server. Calls are routed. <br>
<br>
Is ARC CTI server in Enterprise v5 for pulling users info from ccm without a
need of associatng each and every ccm phone manually? It pulls using
application user all devices from ccm?<br>
or is there any other purpose?<br>
<br>
Here are the ccm and arc server logs:<br>
<br>
<br>
CCM CTI SDL traces<br>
============================================================<br>
<br>
<br>
<br>
000016201| 2009/05/17 08:56:26.304| 001| AppInfo
|
|
| CTIHandler(1,200,16,15)
|
|
| Send CTI Server Heartbeat<br>
000016202| 2009/05/17 08:56:26.573| 001| SdlSig |
CtiClientHeartbeatTimer
| ready
| CTIHandler(1,200,16,15) |
SdlTimerService(1,200,3,1) |
(1,200,15,1).1450-(*:*)
| [R:HP - HP: 0, NP: 0, LP: 0, VLP: 0, LZP: 0 DBP: 0]<br>
000016203| 2009/05/17 08:56:56.130| 001| AppInfo
|
|
| CTIHandler(1,200,16,15)
|
|
| [CTI-APP] [CTIHandler::processIncomingMessage]
CTI Client Heartbeat ( application
name=CiscoTSP001-142.2.64.51)<br>
000016204| 2009/05/17 08:56:56.130| 001| SdlSig |
CtiHeartbeat
| ready
| CTIHandler(1,200,16,15) |
CTIHandler(1,200,16,15) |
(1,200,15,1).1510-(*:*)
| [R:NP - HP: 0, NP: 0, LP: 0, VLP: 0, LZP: 0 DBP: 0] <br>
000016205| 2009/05/17 08:56:56.320| 001| SdlSig |
CtiServerHeartbeatTimer
|
ready
| CTIHandler(1,200,16,15) |
SdlTimerService(1,200,3,1) |
(1,200,15,1).1450-(*:*)
| [R:HP - HP: 0, NP: 0, LP: 0, VLP: 0, LZP: 0 DBP: 0]<br>
000016206| 2009/05/17 08:56:56.320| 001| AppInfo
|
|
| CTIHandler(1,200,16,15)
|
|
| [CTI-APP] [CTIHandler::OutputCtiMessage
] CTI Server Heartbeat (
application name=CiscoTSP001-142.2.64.51)<br>
000016207| 2009/05/17 08:56:56.320| 001| AppInfo
|
|
| CTIHandler(1,200,16,15)
|
|
| Send CTI Server Heartbeat<br>
000016208| 2009/05/17 08:56:56.578| 001| SdlSig |
CtiClientHeartbeatTimer
| ready
| CTIHandler(1,200,16,15) |
SdlTimerService(1,200,3,1) |
(1,200,15,1).1450-(*:*)
| [R:HP - HP: 0, NP: 0, LP: 0, VLP: 0, LZP: 0 DBP: 0]<br>
000016209| 2009/05/17 08:57:26.153| 001| AppInfo
|
|
| CTIHandler(1,200,16,15)
|
|
| [CTI-APP] [CTIHandler::processIncomingMessage]
CTI Client Heartbeat ( application
name=CiscoTSP001-142.2.64.51)<br>
000016210| 2009/05/17 08:57:26.153| 001| SdlSig |
CtiHeartbeat
| ready
| CTIHandler(1,200,16,15) |
CTIHandler(1,200,16,15) |
(1,200,15,1).1511-(*:*)
| [R:NP - HP: 0, NP: 0, LP: 0, VLP: 0, LZP: 0 DBP: 0] <br>
000016211| 2009/05/17 08:57:26.338| 001| SdlSig |
CtiServerHeartbeatTimer
| ready
| CTIHandler(1,200,16,15) |
SdlTimerService(1,200,3,1) |
(1,200,15,1).1450-(*:*)
| [R:HP - HP: 0, NP: 0, LP: 0, VLP: 0, LZP: 0 DBP: 0]<br>
000016212| 2009/05/17 08:57:26.338| 001| AppInfo
|
|
| CTIHandler(1,200,16,15)
|
|
| [CTI-APP] [CTIHandler::OutputCtiMessage
] CTI Server Heartbeat (
application name=CiscoTSP001-142.2.64.51)<br>
000016213| 2009/05/17 08:57:26.338| 001| AppInfo
|
|
| CTIHandler(1,200,16,15)
|
|
| Send CTI Server Heartbeat<br>
000016214| 2009/05/17 08:57:26.592| 001| SdlSig |
CtiClientHeartbeatTimer
|
ready
| CTIHandler(1,200,16,15) |
SdlTimerService(1,200,3,1) |
(1,200,15,1).1450-(*:*)
| [R:HP - HP: 0, NP: 0, LP: 0, VLP: 0, LZP: 0 DBP: 0]<br>
000016215| 2009/05/17 08:57:56.132| 001| AppInfo
|
|
| CTIHandler(1,200,16,15)
|
|
| [CTI-APP] [CTIHandler::processIncomingMessage]
CTI Client Heartbeat ( application
name=CiscoTSP001-142.2.64.51)<br>
000016216| 2009/05/17 08:57:56.132| 001| SdlSig |
CtiHeartbeat
| ready
| CTIHandler(1,200,16,15) |
CTIHandler(1,200,16,15) |
(1,200,15,1).1512-(*:*)
| [R:NP - HP: 0, NP: 0, LP: 0, VLP: 0, LZP: 0 DBP: 0] <br>
000016217| 2009/05/17 08:57:56.349| 001| SdlSig |
CtiServerHeartbeatTimer
| ready
| CTIHandler(1,200,16,15) |
SdlTimerService(1,200,3,1) |
(1,200,15,1).1450-(*:*)
| [R:HP - HP: 0, NP: 0, LP: 0, VLP: 0, LZP: 0 DBP: 0]<br>
000016218| 2009/05/17 08:57:56.350| 001| AppInfo
|
|
| CTIHandler(1,200,16,15)
|
|
| [CTI-APP] [CTIHandler::OutputCtiMessage
] CTI Server Heartbeat (
application name=CiscoTSP001-142.2.64.51)<br>
000016219| 2009/05/17 08:57:56.350| 001| AppInfo |
|
| CTIHandler(1,200,16,15)
|
|
| Send CTI Server Heartbeat<br>
000016220| 2009/05/17 08:57:56.598| 001| SdlSig |
CtiClientHeartbeatTimer
|
ready
| CTIHandler(1,200,16,15) |
SdlTimerService(1,200,3,1) |
(1,200,15,1).1450-(*:*)
| [R:HP - HP: 0, NP: 0, LP: 0, VLP: 0, LZP: 0 DBP: 0]<br>
000016221| 2009/05/17 08:58:26.133| 001| AppInfo
|
|
| CTIHandler(1,200,16,15)
|
|
| [CTI-APP] [CTIHandler::processIncomingMessage]
CTI Client Heartbeat ( application
name=CiscoTSP001-142.2.64.51)<br>
000016222| 2009/05/17 08:58:26.133| 001| SdlSig |
CtiHeartbeat
| ready
| CTIHandler(1,200,16,15) |
CTIHandler(1,200,16,15) |
(1,200,15,1).1513-(*:*)
| [R:NP - HP: 0, NP: 0, LP: 0, VLP: 0, LZP: 0 DBP: 0] <br>
000016223| 2009/05/17 08:58:26.358| 001| SdlSig |
CtiServerHeartbeatTimer
| ready
| CTIHandler(1,200,16,15) |
SdlTimerService(1,200,3,1) |
(1,200,15,1).1450-(*:*)
| [R:HP - HP: 0, NP: 0, LP: 0, VLP: 0, LZP: 0 DBP: 0]<br>
000016224| 2009/05/17 08:58:26.358| 001| AppInfo
|
|
| CTIHandler(1,200,16,15)
|
|
| [CTI-APP] [CTIHandler::OutputCtiMessage
] CTI Server Heartbeat (
application name=CiscoTSP001-142.2.64.51)<br>
000016225| 2009/05/17 08:58:26.358| 001| AppInfo
|
|
| CTIHandler(1,200,16,15)
|
|
| Send CTI Server Heartbeat<br>
000016226| 2009/05/17 08:58:26.614|<br>
<br>
ARC logs:<br>
==================================================================<br>
<br>
17/5/2009 18:45:53.187|R|XML>Reply, ET=304, TR=, OS=2002, RT=, RE=, RD= <br>
17/5/2009 18:45:53.187|R|XML>DeviceStatus, Received, "2002",
Capability=N, Service=N, MAC=SEP888888888888 <br>
17/5/2009
18:45:53.187|M|"DeviceFeatureNE","RouterEvent","2002""
<br>
17/5/2009 18:45:53.187|R|XML>Reply, ET=304, TR=, OS=2002, RT=, RE=, RD= <br>
17/5/2009 18:45:53.187|R|XML>DeviceStatus, Received, "2002",
Capability=N, Service=N, MAC=SEP888888888888 <br>
17/5/2009
18:45:53.187|M|"DeviceFeatureNE","RouterEvent","2002""
<br>
17/5/2009 18:45:53.187|R|XML>Reply, ET=304, TR=, OS=3002, RT=, RE=, RD= <br>
17/5/2009 18:45:53.187|R|XML>DeviceStatus, Received, "3002",
Capability=Y, Service=N, MAC=SEP888888888888 <br>
17/5/2009
18:45:53.187|M|"DeviceFeatureNE","RouterEvent","3002""
<br>
17/5/2009 18:45:53.187|R|XML>Reply, ET=304, TR=, OS=2002, RT=, RE=, RD= <br>
17/5/2009 18:45:53.187|R|XML>DeviceStatus, Received, "2002",
Capability=N, Service=N, MAC=SEP888888888888 <br>
17/5/2009
18:45:53.187|M|"DeviceFeatureNE","RouterEvent","2002""
<br>
17/5/2009 18:45:53.187|R|XML>Reply, ET=304, TR=, OS=3002, RT=, RE=, RD= <br>
17/5/2009 18:45:53.187|R|XML>DeviceStatus, Received, "3002",
Capability=Y, Service=N, MAC=SEP888888888888 <br>
17/5/2009
18:45:53.187|M|"DeviceFeatureNE","RouterEvent","3002""
<br>
17/5/2009 18:45:53.187|R|"TimerEvent","Event Relay [41]" <br>
17/5/2009
18:45:53.187|R|CT>"CTCE","Invalid","I:13","S:0","E:0
[0x00000000]" <br>
17/5/2009
18:45:53.187|R|CT>"CTEE","SEVT_MONITOR","E:10","2002","SNo:SEP888888888888"
<br>
17/5/2009
18:45:53.187|R|CT>"CTEE","SEVT_MONITOR","2002","State:Y"
<br>
17/5/2009
18:45:53.187|M|"DeviceFeatureNE","RouterEvent","2002""
<br>
17/5/2009
18:45:53.187|R|CT>"TQueryForward","TQueryForward(Request)","2002","TQueryForward('2002')"
<br>
17/5/2009
18:45:53.187|R|CT>"TQueryForward","TQueryForward(Response)","2002","TQueryForward()
= SUCCESS" <br>
17/5/2009
18:45:53.187|R|CT>"CTEE","SEVT_DEVICE","E:97","2002","SNo:SEP888888888888"
<br>
17/5/2009
18:45:53.187|R|CT>"CTEE","SEVT_DEVICE","EEVT_OUTOFSERVICE","2002"
<br>
17/5/2009 18:45:53.187|R|"DeviceFailureEvent","2002" <br>
17/5/2009
18:45:53.187|R|"TIEnv.CTLAShutdownDP","Generate(teShutdown)","Devices.OutOfService:1","EventDelay:30000"
<br>
17/5/2009
18:45:53.187|R|CT>"CTEE","SEVT_MONITOR","E:10","2002","SNo:SEP888888888888"
<br>
17/5/2009
18:45:53.187|R|CT>"CTEE","SEVT_DEVICE","E:97","2002","SNo:SEP888888888888"
<br>
17/5/2009
18:45:53.187|R|CT>"CTEE","SEVT_DEVICE","EEVT_OUTOFSERVICE","2002"
<br>
17/5/2009 18:45:53.187|R|"DeviceFailureEvent","2002" <br>
17/5/2009 18:45:53.187|R|"TIEnv.CTLAShutdownDP","Already(teShutdown)","Devices.OutOfService:1"
<br>
17/5/2009
18:45:53.187|R|"teMonitorBLFDevices","EventNotify" <br>
17/5/2009
18:45:53.187|R|CT>"MonitorDevice","MonitorStartDevice(Request)","3002","MonitorStartDevice('3002','',MT_MONITOR)"
<br>
17/5/2009
18:45:53.187|R|CT>"MonitorDevice","MonitorStartDevice(Response)","3002","MonitorStartDevice()
= FAILURE(15)" <br>
17/5/2009
18:45:53.187|R|"TimerEvent","Recycle","Generate(teMonitorBLFDevices)","CurrentIndex:1","BLFDevicesCount:2"
<br>
17/5/2009 18:45:53.203|R|"TimerEvent","Event Relay [41]" <br>
17/5/2009
18:45:53.203|R|"teMonitorBLFDevices","EventNotify" <br>
17/5/2009 18:45:53.203|R|"teMonitorBLFDevices","No More BLF
Device Left to be
Monitored","CurrentIndex:2","BLFDevicesCount:2" <br>
17/5/2009 18:45:53.203|R|CT>"CTCE","Invalid","I:15","S:0","E:0
[0x00000000]" <br>
17/5/2009
18:45:53.203|R|CT>"CTEE","SEVT_MONITOR","E:10","3002","SNo:SEP888888888888"
<br>
17/5/2009
18:45:53.203|R|CT>"CTEE","SEVT_MONITOR","3002","State:Y"
<br>
17/5/2009 18:45:53.203|M|"DeviceFeatureNE","RouterEvent","3002""
<br>
17/5/2009
18:45:53.203|R|CT>"TQueryForward","TQueryForward(Request)","3002","TQueryForward('3002')"
<br>
17/5/2009
18:45:53.203|R|CT>"TQueryForward","TQueryForward(Response)","3002","TQueryForward()
= SUCCESS" <br>
17/5/2009 18:45:53.203|R|CT>"CTEE","SEVT_DEVICE","E:97","3002","SNo:SEP888888888888"
<br>
17/5/2009
18:45:53.203|R|CT>"CTEE","SEVT_DEVICE","EEVT_OUTOFSERVICE","3002"
<br>
17/5/2009 18:45:53.203|R|"DeviceFailureEvent","3002" <br>
17/5/2009
18:45:56.656|M|"InitializeICDSystemLog","Initialize","Success"
<br>
17/5/2009
18:46:23.203|R|"TimerEvent","teShutdown","Status:Y","RT:1","CTLF:Y","GCTLS:4""
<br>
17/5/2009
18:46:23.203|R|"TIEnv.CTLAShutdownDP","Error(Event.Iteration)","Devices.OutOfService:1"
<br>
17/5/2009 18:46:23.203|R|"TIEnv.CTLAShutdownDP","AutoRestartOnDeviceFail.Disabled","Devices.OutOfService:1","EventDelay:30000"
<br>
17/5/2009
18:46:23.203|R|"TIEnv.CTLAShutdownDP","Error(NoGatewayDevices)","Shutdown.Imminent","gctlsFail"
<br>
17/5/2009
18:46:23.203|M|"CTServerStatusNE","RouterEvent","CTServerStatus","1","1",""
<br>
17/5/2009 18:46:23.203|M|"CTServerStatusNE","Server
Shutdown\Restarted","CT Link Error" <br>
17/5/2009 18:46:23.234|M|"StopEMSCalendarClient","Started" <br>
17/5/2009 18:46:23.234|CL|"StopEMSClient","Current Client
State:EMSUnknown","Last Client State:EMSUnknown" <br>
17/5/2009 18:46:23.234|CL|"DisconnectRecovery: Started " <br>
17/5/2009 18:46:23.234|CL|"DisconnectRecovery: End " <br>
17/5/2009 18:46:23.234|CL|"StopEMSClient","Success" <br>
17/5/2009 18:46:23.234|M|"StopEMSCalendarClient","Success" <br>
17/5/2009 18:46:23.234|M|"StopEMSCalendarClient","Shutdown","Started"
<br>
17/5/2009
18:46:23.234|M|"StopEMSCalendarClient","Shutdown","Success"
<br>
17/5/2009
18:46:23.234|M|"PMS>ShutdownPresenceManager","Status=pssStopped"
<br>
17/5/2009
18:46:23.234|M|"ShutdownServices","Shutdown","Started"
<br>
17/5/2009
18:46:23.234|M|"VoiceServerClient","ShutdownMonitor","Success"
<br>
17/5/2009
18:46:23.234|R|"TIEnv","Destructor","Terminating event
services..." <br>
17/5/2009
18:46:23.234|R|"FilterPriorityRoutingExecution.RouteManager.Stopped" <br>
17/5/2009 18:46:23.234|R|XML>Status, mssRunning -> mssShutdownREQ <br>
17/5/2009 18:46:23.234|R|XML>Reply, ET=301, TR=, OS=, RT=, RE=, RD= <br>
17/5/2009 18:46:23.234|R|XML>Status, mssShutdownREQ -> mssShutdown <br>
17/5/2009 18:46:23.234|R|XML>Reply, ET=304, TR=, OS=2002, RT=, RE=, RD= <br>
17/5/2009 18:46:23.234|R|XML>DeviceStatus, Received, "2002",
Capability=N, Service=N, MAC=SEP888888888888 <br>
17/5/2009
18:46:23.234|M|"DeviceFeatureNE","RouterEvent","2002""
<br>
17/5/2009 18:46:23.234|R|XML>Reply, ET=304, TR=, OS=3002, RT=, RE=, RD= <br>
17/5/2009 18:46:23.234|R|XML>DeviceStatus, Received, "3002",
Capability=Y, Service=N, MAC=SEP888888888888 <br>
17/5/2009
18:46:23.234|M|"DeviceFeatureNE","RouterEvent","3002""
<br>
17/5/2009 18:46:23.234|R|XML>Reply, ET=301, TR=, OS=, RT=, RE=, RD= <br>
17/5/2009 18:46:23.234|R|XML>Status, mssShutdown -> mssStopped <br>
17/5/2009 18:46:23.234|R|XML>Failover <br>
17/5/2009 18:46:23.234|R|XML>FailoverDevices <br>
17/5/2009 18:46:25.250|R|XML>TPGShutDown=0[0x00000000] <br>
17/5/2009 18:46:25.250|R|"ICD Routing Thread","Shutdown
Started" <br>
17/5/2009 18:46:25.250|R|"ICD Routing Thread","Shutdown CT
Calls" <br>
17/5/2009 18:46:25.250|R|"ICD Routing Thread","Shutdown CT
Link" <br>
17/5/2009
18:46:25.250|R|CT>"ICDRouter","TLogOutServer","TLogOutServer(Request)","TLogOutServer()"
<br>
17/5/2009 18:46:26.937|R|CT>"ICDRouter","TLogOutServer","TLogOutServer(Response)","TLogOutServer()
= 0" <br>
17/5/2009 18:46:27.031|R|"ICD Routing Thread","Shutdown
Complete" <br>
17/5/2009
18:46:27.031|R|"TIEnv","Destructor","Terminating
callbacks..." <br>
17/5/2009 18:46:27.031|R|"TIEnv","Destructor","Terminating
event objects..." <br>
17/5/2009
18:46:27.031|M|"ICDRouter","Shutdown","Success" <br>
17/5/2009
18:46:27.046|M|"ICDCommunications","Shutdown","Success"
<br>
17/5/2009
18:46:27.046|M|"ShutdownDBObjects","Shutdown","Start"
<br>
17/5/2009 18:46:27.046|M|"ShutdownDBObjects","Shutdown","Terminate
Call Objects..." <br>
17/5/2009
18:46:27.046|M|"ShutdownDBObjects","Shutdown","Terminate
Agent Objects..." <br>
17/5/2009
18:46:27.046|M|"ShutdownDBConnectionObject","Shutdown","SID:","CLF:10","CLF:1"
<br>
17/5/2009 18:46:27.046|M|"ShutdownDBObjects","Shutdown","Complete"
<br>
17/5/2009
18:46:27.046|M|"ICDDataBase","ShutdownDBObjects","Success"
<br>
17/5/2009
18:46:27.046|M|"ICDDataBase","Shutdown","Success"
<br>
17/5/2009
18:46:27.046|M|"RecordInterface","Shutdown","Success"
<br>
17/5/2009
18:46:27.046|M|"ICDDataBase","Shutdown","Success"
<br>
17/5/2009 18:46:27.046|M|"COM>SetCOMEnvironment.CoUninitialize" <br>
17/5/2009
18:46:27.046|M|"ShutdownServices","Shutdown","Completed"
<br>
17/5/2009
18:46:27.046|M|"ShutdownVoiceServices","Shutdown","Started"
<br>
17/5/2009
18:46:27.046|M|"VoiceServerClient","Shutdown","Success"
<br>
17/5/2009
18:46:27.046|M|"ShutdownVoiceServices","Shutdown","Completed"
<br>
17/5/2009 18:46:27.046|M|"Voice Process Error
Logging","Uninitialize","Disabled","Ok" <br>
-- <br>
Smile, you'll save someone else's day!<br>
Frog<o:p></o:p></p>
</div>
</div>
</div>
<pre>*************************************************************************<o:p></o:p></pre><pre>This email and any files transmitted with it are confidential and<o:p></o:p></pre><pre>intended solely for the use of the individual or entity to whom they<o:p></o:p></pre><pre>are addressed. If you have received this email in error please notify<o:p></o:p></pre><pre>the system manager. <a
href="http://www.mettoni.com" target="_blank">http://www.mettoni.com</a><o:p></o:p></pre><pre> <o:p></o:p></pre><pre>Mettoni Ltd<o:p></o:p></pre><pre>Registered in England and Wales: 4485956<o:p></o:p></pre><pre>9400 Garsington Road, Oxford Business Park, Oxford, OX4 2HN<o:p></o:p></pre><pre>*************************************************************************<o:p></o:p></pre></div>
</div>
<p><br>
<br clear=all>
<br>
-- <br>
Smile, you'll save someone else's day!<br>
Frog<o:p></o:p></p>
</div>
</div>
</div>
<div>
<div><pre>*************************************************************************<o:p></o:p></pre><pre>This email and any files transmitted with it are confidential and<o:p></o:p></pre><pre>intended solely for the use of the individual or entity to whom they<o:p></o:p></pre><pre>are addressed. If you have received this email in error please notify<o:p></o:p></pre><pre>the system manager. <a
href="http://www.mettoni.com" target="_blank">http://www.mettoni.com</a><o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Mettoni Ltd<o:p></o:p></pre><pre>Registered in England and Wales: 4485956<o:p></o:p></pre><pre>9400 Garsington Road, Oxford Business Park, Oxford, OX4 2HN<o:p></o:p></pre><pre>*************************************************************************<o:p></o:p></pre></div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
<div>
<div>
<p class=MsoNormal><br>
<br clear=all>
<br>
-- <br>
Smile, you'll save someone else's day!<br>
Frog<o:p></o:p></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></p>
</blockquote>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<p class=MsoNormal><br>
<br clear=all>
<br>
-- <br>
Smile, you'll save someone else's day!<br>
Frog<o:p></o:p></p>
</div>
<PRE>*************************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager. http://www.mettoni.com
Mettoni Ltd
Registered in England and Wales: 4485956
9400 Garsington Road, Oxford Business Park, Oxford, OX4 2HN
*************************************************************************
</PRE></body>
</html>