<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1491" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>My plan was to point all devices (Unity ports,
phones, etc) to a set of two subscribers while we upgrade the publisher, tftp
server and another set of two subscribers. Once the upgrades are complete, I
would point all devices to the set of two upgraded subscribers, then
upgrade the remaining two subscribers. Once the upgrades are complete and then
finally reset all the devices back to their original devices pools (subscribers
spanning buildings).</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>I'm confident with the devices, since I've done
that before, but it's the CRS apps that has me wondering.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>I'm guessing configuring the JTAPI portion is easy
enough and restart the engine. But is it OK to modify the directory and
repository as many times as I'd like? Do I loose all the scripts, or does it
upload what it has to the new settings?</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV>-----
-----<BR>Lelio Fulgenzi,
B.A.
<A href="mailto:lelio@uoguelph.ca.eh">lelio@uoguelph.ca.eh</A><BR>Network
Analyst (CCS)<BR>University of
Guelph
FAX:(519) 767-1060 JNHN<BR>Guelph, Ontario N1G
2W1
TEL:(519) 824-4120
x56354<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<BR>
remove the 1st letter of the canadian alphabet from my email, eh!</DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=andy@dignans.com href="mailto:andy@dignans.com">Andrew Dignan</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=lelio@uoguelph.ca
href="mailto:lelio@uoguelph.ca">Lelio Fulgenzi</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=cisco-voip@puck.nether.net
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Sunday, February 13, 2005 10:39
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [cisco-voip] Behaviour of
Agent Desktops and Phone Agents upon lossof communications with
publisher.</DIV>
<DIV><BR></DIV>Assuming your CRS server is setup to use the Subscriber not
just for JTAPI<BR>but also for your Directory and Repository setup, you could
function<BR>properly without the Publisher online. If Directory was
setup with the<BR>Publisher as Primary on CRS (PublisherIP, SubscriberIP) and
the Publisher<BR>were to fail, the agents would be kicked out and they would
need to login<BR>again.<BR><BR>Regards,<BR><BR>[andy]<BR><BR>> Just
wondering if anyone out there can comment on the behaviour of IPCC<BR>>
Express and logged in agents upon loss of communications with the<BR>>
publisher. From what I understand, as long as the agents are logged
in,<BR>> and the CTI ports are not registered to the publisher, everything
will<BR>> continue as normal.<BR>><BR>><BR>>
-----
-----<BR>> Lelio Fulgenzi,
B.A.
<A href="mailto:lelio@uoguelph.ca.eh">lelio@uoguelph.ca.eh</A><BR>> Network
Analyst (CCS)<BR>> University of
Guelph
FAX:(519) 767-1060 JNHN<BR>> Guelph, Ontario N1G
2W1
TEL:(519) 824-4120 x56354<BR>>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<BR>>
remove the 1st letter of the canadian alphabet from my email,<BR>>
eh!_______________________________________________<BR>> cisco-voip mailing
list<BR>> <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR>>
<A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>><BR></BLOCKQUOTE></BODY></HTML>