|
Home > Archive > Voice over IP Cisco > November 2005 > IPCC Express v4.0 SRND - no FACs/CMCs allowed????
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
IPCC Express v4.0 SRND - no FACs/CMCs allowed????
|
|
| Lelio Fulgenzi 2005-11-25, 5:45 pm |
| 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
| |
| Erick B. 2005-11-25, 5:45 pm |
| You're probably better off asking these questions on
the ask-icd-ivr-support@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.
=E2=80=A2 Block External to External Transfer
=E2=80=A2 Drop Adhoc Conference When Creator Leaves
=E2=80=A2 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.
=E2=80=A2 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.
=E2=80=A2 Forced Authorization Codes and Client Matter Codes
(FAC/CMC)
=E2=80=A2 Block External to External Transfer
=E2=80=A2 Drop Adhoc Conference When Creator Leaves" =
--- Lelio Fulgenzi <lelio@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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> =
=
=
__________________________________ =
Yahoo! Mail - PC Magazine Editors' Choice 2005 =
http://mail.yahoo.com
| |
| Lelio Fulgenzi 2005-11-25, 8:45 pm |
| 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@puck.nether.net
Cc: cipcon@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@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@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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
__________________________________
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
| |
| Erick B. 2005-11-26, 2:45 am |
| You can subscribe, or just send a email to the list
and then get replies if people are able to help.
I believe to subscribe, you send email to
mailer@cisco.com
then in the message body, =
subscribe ask-icd-ivr-support
--- Lelio Fulgenzi <lelio@uoguelph.ca> wrote:
> 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@puck.nether.net =
> Cc: cipcon@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@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.
> =EF=BF=BD?=EF=BF=BD Block External to External Transfer
> =EF=BF=BD?=EF=BF=BD Drop Adhoc Conference When Creator Leaves
> =EF=BF=BD?=EF=BF=BD 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.
> =
> =EF=BF=BD?=EF=BF=BD 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.
> =
> =EF=BF=BD?=EF=BF=BD Forced Authorization Codes and Client
Matter
> Codes
> (FAC/CMC)
> =EF=BF=BD?=EF=BF=BD Block External to External Transfer
> =EF=BF=BD?=EF=BF=BD Drop Adhoc Conference When Creator Leaves"
> =
> --- Lelio Fulgenzi <lelio@uoguelph.ca> wrote:
> =
> Client
> same
> installed.
> not
> is
> to
[vbcol=seagreen]
[vbcol=seagreen]
[vbcol=seagreen]
> =
>
---------------------------------------------------------------------------=
-----
> =
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[vbcol=seagreen]
> now,
[vbcol=seagreen]
> =
> ________________________________________
_______
> https://puck.nether.net/mailman/listinfo/cisco-voip
[vbcol=seagreen]
> =
> =
> =
> =
> =
> __________________________________ =
> Yahoo! Mail - PC Magazine Editors' Choice 2005 =
> http://mail.yahoo.com
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> =
=
=
__________________________________ =
Yahoo! Mail - PC Magazine Editors' Choice 2005 =
http://mail.yahoo.com
| |
| Philip Walenta 2005-11-26, 2:45 am |
| I remember asking the BU about these several months back.
It's not that these functions inherently "break" CRS, it's that the BU has
not sufficiently tested them, therefore they consider them "not to be used".
One of the comments I received said, as long as they don't interfere, it
shouldn't be a problem. However, TAC may think differently ;-)
_____
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Lelio Fulgenzi
Sent: Friday, November 25, 2005 5:54 PM
To: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] IPCC Express v4.0 SRND - no FACs/CMCs allowed????
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. <mailto:erickbe@yahoo.com>
To: Lelio Fulgenzi <mailto:lelio@uoguelph.ca> ; cisco-voip@puck.nether.net
Cc: cipcon@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@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@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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
__________________________________
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
|
|
|
|
|