Comments are inline below:<br><br><div class="gmail_quote">On Mon, May 18, 2009 at 11:28 PM, Bennie Grant <span dir="ltr"><<a href="mailto:Bennie.Grant@mettoni.com">Bennie.Grant@mettoni.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">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></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">I have the same question from my previous email:</span></p>
<p style="margin-left: 0.5in; text-indent: -0.25in;"><span style="font-size: 11pt; color: rgb(31, 73, 125);"><span>1)<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;">
</span></span></span><span style="font-size: 11pt; color: rgb(31, 73, 125);">Why do you have the same MAC address (this 888888888888 number)
– I just want to understand the “real world application” for
this config</span></p></div></div></blockquote><div><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. <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div link="blue" vlink="purple" lang="EN-US"><div><p style="margin-left: 0.5in; text-indent: -0.25in;">
<span style="font-size: 11pt; color: rgb(31, 73, 125);"></span><span></span></p>
<p style="margin-left: 0.5in; text-indent: -0.25in;"><span style="font-size: 11pt; color: rgb(31, 73, 125);"><span>2)<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;">
</span></span></span><span style="font-size: 11pt; color: rgb(31, 73, 125);">Could you try changing the MAC address of one of these devices
by one digit, and see if this then works?</span><span></span></p></div></div></blockquote><div><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<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div link="blue" vlink="purple" lang="EN-US"><div><p style="margin-left: 0.5in; text-indent: -0.25in;">
</p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">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></p><div class="im">
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"></span></p></div></div></div></blockquote><div><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. <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div link="blue" vlink="purple" lang="EN-US">
<div><div class="im"><p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">Thanks</span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p><b><span style="font-size: 11pt; color: navy;" lang="EN-GB">Bennie Grant<br>
</span></b><i><span style="font-size: 8pt; color: navy;" lang="EN-GB">VP - Operations<br>
</span></i><b><span style="font-size: 11pt; color: navy;" lang="EN-GB">Arc Solutions (International) Inc<br>
</span></b><span style="font-size: 8pt; color: navy;" lang="EN-GB">Part of the Mettoni group | </span><span style="font-size: 11pt; color: rgb(31, 73, 125);" lang="EN-GB"><a href="http://www.mettoni.com/" target="_blank"><span style="font-size: 8pt;">www.mettoni.com</span></a>
</span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
</div><div style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
<p><b><span style="font-size: 10pt;">From:</span></b><span style="font-size: 10pt;"> 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></p>
</div><div><div></div><div class="h5">
<p> </p>
<p style="margin-bottom: 12pt;">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>
<br>
</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:</p>
<div>
<div>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">Hey Frog</span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">Couple of things for you:</span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">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></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">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></p>
<p style="text-indent: -0.25in;"><span style="font-size: 11pt; color: rgb(31, 73, 125);">1)</span><span style="font-size: 7pt; color: rgb(31, 73, 125);"> </span><span style="font-size: 11pt; color: rgb(31, 73, 125);">Either it cannot see ANY CTI Devices</span></p>
<p style="text-indent: -0.25in;"><span style="font-size: 11pt; color: rgb(31, 73, 125);">2)</span><span style="font-size: 7pt; color: rgb(31, 73, 125);"> </span><span style="font-size: 11pt; color: rgb(31, 73, 125);">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></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">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></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">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></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">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></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">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></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">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></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">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></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">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></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">Thanks</span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p><b><span style="font-size: 11pt; color: navy;" lang="EN-GB">Bennie Grant<br>
</span></b><i><span style="font-size: 8pt; color: navy;" lang="EN-GB">VP -
Operations<br>
</span></i><b><span style="font-size: 11pt; color: navy;" lang="EN-GB">Arc
Solutions (International) Inc<br>
</span></b><span style="font-size: 8pt; color: navy;" lang="EN-GB">Part of the
Mettoni group | </span><span style="font-size: 11pt; color: rgb(31, 73, 125);" lang="EN-GB"><a href="http://www.mettoni.com/" target="_blank"><span style="font-size: 8pt;">www.mettoni.com</span></a>
</span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<div style="border-style: solid none none; border-color: -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
<p><b><span style="font-size: 10pt;">From:</span></b><span style="font-size: 10pt;"> <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></p>
</div>
<div>
<div>
<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</p>
</div>
</div>
</div>
<pre>*************************************************************************</pre><pre>This email and any files transmitted with it are confidential and</pre><pre>intended solely for the use of the individual or entity to whom they</pre>
<pre>are addressed. If you have received this email in error please notify</pre><pre>the system manager. <a href="http://www.mettoni.com" target="_blank">http://www.mettoni.com</a></pre><pre> </pre><pre>Mettoni Ltd</pre>
<pre>Registered in England and Wales: 4485956</pre><pre>9400 Garsington Road, Oxford Business Park, Oxford, OX4 2HN</pre><pre>*************************************************************************</pre></div>
</div>
<p><br>
<br clear="all">
<br>
-- <br>
Smile, you'll save someone else's day!<br>
Frog</p>
</div></div></div><div><div></div><div class="h5">
<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. <a href="http://www.mettoni.com" target="_blank">http://www.mettoni.com</a>
Mettoni Ltd
Registered in England and Wales: 4485956
9400 Garsington Road, Oxford Business Park, Oxford, OX4 2HN
*************************************************************************
</pre></div></div></div>
</blockquote></div><br><br clear="all"><br>-- <br>Smile, you'll save someone else's day!<br>Frog<br>