<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;}
/* 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.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.EmailStyle17
{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:1180466415;
mso-list-type:hybrid;
mso-list-template-ids:-534486122 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 l1
{mso-list-id:1624456303;
mso-list-type:hybrid;
mso-list-template-ids:-1823413048 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
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'>Hey Frog<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'>Couple of things for you:<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'>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<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'>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:<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![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'>Either it cannot see ANY CTI Devices<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![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'>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<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'>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)<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'>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. <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'>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…<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'>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…<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'>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.<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'>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?<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 separate note, which version of Arc Enterprise do you have –
there is no version 504 out there? Our latest is v5.0.2…<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";
color:blue'>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>
<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"'>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <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<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><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>
<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>