[cisco-voip] IPCC Express v4.0 SRND - no FACs/CMCs allowed????

[Lelio Fulgenzi]

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.

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?

Lelio

  ----- Original Message ----- 
  From: Erick B. 
  To: Lelio Fulgenzi ; cisco-voip at puck.nether.net 
  Cc: cipcon at listserv.uoguelph.ca 
  Sent: Friday, November 25, 2005 6:04 PM
  Subject: Re: [cisco-voip] IPCC Express v4.0 SRND - no FACs/CMCs allowed????


  You're probably better off asking these questions on
  the ask-icd-ivr-support at external.cisco.com mailing
  list. I know this was heavily discussed earlier on
  that list for the earlier versions and answer was
  FAC/CMC is not supported. 

  This is mentioned in CRS release notes dating back to
  3.1 also, but the 4.x SRND outright saids no.

  The following can be read in the release notes of CRA
  3.5(3):

  Unsupported Features in Cisco CallManager
  The following Cisco CallManager features are not
  supported by
  Cisco CRA 3.5(3). These features are disabled by
  default and should not be enabled for Cisco CRA.
  â?¢ Block External to External Transfer
  â?¢ Drop Adhoc Conference When Creator Leaves
  â?¢ Q Signalling (QSIG) Path Replacement (PR).

  Release Notes for Cisco Customer Response Applications
  3.5(3)
  This feature must be disabled when Cisco CRS is
  deployed. To disable this
  feature, set the Cisco CallManager service parameters
  Path Replacement
  Enabled and Path Replacement on Tromboned Calls to
  False.

  â?¢ Forced Authorization Code and Client Matter Code.
  Because these feature can be enabled per route
  pattern, they should be turned
  off for all route patterns in the Cisco CallManager
  cluster that Cisco CRS
  might use. Enabling these features for route patterns
  that Cisco CRS does not
  use will not affect Cisco CRS.

  The following can be read in the release notes of CRA
  3.1(3):

  "Unsupported Features in Cisco Callmanager 3.3(4)
  The following new features introduced with Cisco
  CallManager 3.3(4) are not supported by Cisco CRA 3.1.
  These features are disabled by default and should not
  be enabled for Cisco CRA.

  â?¢ Forced Authorization Codes and Client Matter Codes
  (FAC/CMC)
  â?¢ Block External to External Transfer
  â?¢ Drop Adhoc Conference When Creator Leaves" 

  --- Lelio Fulgenzi <lelio at uoguelph.ca> wrote:

  > A very interesting 'design consideration' in the
  > IPCC Express v4.0 SRND:
  >   CallManager Forced Authorization Codes and Client
  > Matter Codes are not allowed to be used on the same
  > CallManager cluster where IPCC Express is installed.
  > This is for any CallManager phones and users- not
  > just IPCC Express agents. The resolution to this is
  > to deploy two separate CCM clusters.
  > We are heavy users of FACs (as are many other
  > educational institutions) and are keen on going to
  > IPCCX v4.x for the redundancy features.
  > 
  > Any Cisco folk still in the office on a Friday
  > afternoon care to comment? ;)
  > 
  > 
  >
  --------------------------------------------------------------------------------
  > Lelio Fulgenzi, B.A.
  > Network Analyst (CCS) * University of Guelph *
  > Guelph, Ontario N1G 2W1
  > (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
  >
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  > 
  > "I had a coffee and Coke at lunch today...and now,
  > I've got more jitter than an
  > IP phone on a long haul 10base2 connection"         
  >                                  LFJ>
  _______________________________________________
  > cisco-voip mailing list
  > cisco-voip at puck.nether.net
  > https://puck.nether.net/mailman/listinfo/cisco-voip
  > 





  __________________________________ 
  Yahoo! Mail - PC Magazine Editors' Choice 2005 
  http://mail.yahoo.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20051125/680f3513/attachment.html