<!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.2900.2769" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Thanks for your note. I searched the 3.1 and 3.5
SRND and did not find anything - didn't think of looking in the release notes
for reference to earlier versions. I can understand how FAC/CMC should not be
enabled on route patterns used by CRS as explained in the release notes - but to
go so far as to say that if you use FACs at all you have to install CRS on a
seperate cluster? I'm really hoping someone made a mistake in this document. I'm
at CIPTUG next week so hope to get clarification.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Can you explain the ask-icd mailing list a bit
more? Do I subscribe to it or just post questions? Is there an archive available
to search?</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Lelio</FONT></DIV>
<DIV> </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=erickbe@yahoo.com href="mailto:erickbe@yahoo.com">Erick B.</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=lelio@uoguelph.ca
href="mailto:lelio@uoguelph.ca">Lelio Fulgenzi</A> ; <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>Cc:</B> <A title=cipcon@listserv.uoguelph.ca
href="mailto:cipcon@listserv.uoguelph.ca">cipcon@listserv.uoguelph.ca</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Friday, November 25, 2005 6:04
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [cisco-voip] IPCC Express
v4.0 SRND - no FACs/CMCs allowed????</DIV>
<DIV><BR></DIV>You're probably better off asking these questions on<BR>the <A
href="mailto:ask-icd-ivr-support@external.cisco.com">ask-icd-ivr-support@external.cisco.com</A>
mailing<BR>list. I know this was heavily discussed earlier on<BR>that list for
the earlier versions and answer was<BR>FAC/CMC is not supported. <BR><BR>This
is mentioned in CRS release notes dating back to<BR>3.1 also, but the 4.x SRND
outright saids no.<BR><BR>The following can be read in the release notes of
CRA<BR>3.5(3):<BR><BR>Unsupported Features in Cisco CallManager<BR>The
following Cisco CallManager features are not<BR>supported by<BR>Cisco CRA
3.5(3). These features are disabled by<BR>default and should not be enabled
for Cisco CRA.<BR>â?¢ Block External to External Transfer<BR>â?¢ Drop Adhoc
Conference When Creator Leaves<BR>â?¢ Q Signalling (QSIG) Path Replacement
(PR).<BR><BR>Release Notes for Cisco Customer Response
Applications<BR>3.5(3)<BR>This feature must be disabled when Cisco CRS
is<BR>deployed. To disable this<BR>feature, set the Cisco CallManager service
parameters<BR>Path Replacement<BR>Enabled and Path Replacement on Tromboned
Calls to<BR>False.<BR><BR>â?¢ Forced Authorization Code and Client Matter
Code.<BR>Because these feature can be enabled per route<BR>pattern, they
should be turned<BR>off for all route patterns in the Cisco
CallManager<BR>cluster that Cisco CRS<BR>might use. Enabling these features
for route patterns<BR>that Cisco CRS does not<BR>use will not affect Cisco
CRS.<BR><BR>The following can be read in the release notes of
CRA<BR>3.1(3):<BR><BR>"Unsupported Features in Cisco Callmanager 3.3(4)<BR>The
following new features introduced with Cisco<BR>CallManager 3.3(4) are not
supported by Cisco CRA 3.1.<BR>These features are disabled by default and
should not<BR>be enabled for Cisco CRA.<BR><BR>â?¢ Forced Authorization Codes
and Client Matter Codes<BR>(FAC/CMC)<BR>â?¢ Block External to External
Transfer<BR>â?¢ Drop Adhoc Conference When Creator Leaves" <BR><BR>--- Lelio
Fulgenzi <<A href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</A>>
wrote:<BR><BR>> A very interesting 'design consideration' in the<BR>>
IPCC Express v4.0 SRND:<BR>> CallManager Forced Authorization
Codes and Client<BR>> Matter Codes are not allowed to be used on the
same<BR>> CallManager cluster where IPCC Express is installed.<BR>> This
is for any CallManager phones and users- not<BR>> just IPCC Express agents.
The resolution to this is<BR>> to deploy two separate CCM clusters.<BR>>
We are heavy users of FACs (as are many other<BR>> educational
institutions) and are keen on going to<BR>> IPCCX v4.x for the redundancy
features.<BR>> <BR>> Any Cisco folk still in the office on a
Friday<BR>> afternoon care to comment? ;)<BR>> <BR>>
<BR>><BR>--------------------------------------------------------------------------------<BR>>
Lelio Fulgenzi, B.A.<BR>> Network Analyst (CCS) * University of Guelph
*<BR>> Guelph, Ontario N1G 2W1<BR>> (519) 824-4120 x56354 (519) 767-1060
FAX
(JNHN)<BR>><BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<BR>>
<BR>> "I had a coffee and Coke at lunch today...and now,<BR>> I've got
more jitter than an<BR>> IP phone on a long haul 10base2
connection"
<BR>>
LFJ><BR>_______________________________________________<BR>> cisco-voip
mailing list<BR>> <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR>>
<A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>>
<BR><BR><BR><BR><BR><BR>__________________________________ <BR>Yahoo! Mail -
PC Magazine Editors' Choice 2005 <BR><A
href="http://mail.yahoo.com">http://mail.yahoo.com</A><BR></BLOCKQUOTE></BODY></HTML>