<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<STYLE>.hmmessage P {
PADDING-RIGHT: 0px; PADDING-LEFT: 0px; PADDING-BOTTOM: 0px; MARGIN: 0px; PADDING-TOP: 0px
}
BODY.hmmessage {
FONT-SIZE: 10pt; FONT-FAMILY: Tahoma
}
</STYLE>
<META content="MSHTML 6.00.2900.3395" name=GENERATOR></HEAD>
<BODY class=hmmessage bgColor=#ffffff>
<DIV><FONT face=Arial>I think for the most part people have answered the
questions. I just wanted to add to the differences between FACs and
CMCs:</FONT></DIV>
<UL>
<LI><FONT face=Arial>both FACs and CMCs have a "code" portion, this is used
when a route pattern is triggered which requires one or the other (or
both)</FONT></LI>
<LI><FONT face=Arial>both FACs and CMCs have a "description" portion but for
FACs, the "description" is entered into the CDR and for the CMC the code is
entered into the CDR.</FONT></LI>
<LI><FONT face=Arial>an FAC also has level associated to it, so based on the
level it can use particular route patterns</FONT></LI></UL>
<DIV>Lelio<BR>--------------------------------------------------------------------------------<BR>Lelio
Fulgenzi, B.A.<BR>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario
N1G 2W1<BR>(519) 824-4120 x56354 (519) 767-1060 FAX
(JNHN)<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
<BR>...seen on a Geek Squad patch cord: "While it is the same length, this 7'
crossover cable<BR>is not regulation issue for most competitive Manhattan double
dutch leagues.</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=khalid_khursheed@hotmail.com
href="mailto:khalid_khursheed@hotmail.com">Syed Khalid Ali</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</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> Wednesday, September 10, 2008 12:17
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> [cisco-voip] IPT QS: CSS and
Partitioning</DIV>
<DIV><BR></DIV>All,<BR><BR>I was reading CCM fundamentals 2nd edition and got
confused on the following verdicts:<BR><BR><SPAN
style="FONT-WEIGHT: bold">Partitions divide the set of all route patterns into
subsets of equally reachable destinations. </SPAN><SPAN class=docEmphasis
style="FONT-WEIGHT: bold">Equally reachable</SPAN><SPAN
style="FONT-WEIGHT: bold"> means that a user who can call any single member of
the subset can call all members of the subset.</SPAN><SPAN
style="FONT-STYLE: italic"><BR><BR><SPAN
style="FONT-STYLE: italic"></SPAN></SPAN>Then in subsequent paragraph the
author says:<BR><BR><SPAN style="FONT-WEIGHT: bold">A partition is an
attribute of an address. It belongs to called entities; it has no bearing on
who a device can call. Membership in a partition does not automatically mean
that a device can call other devices in the partition. The list of partitions
in a device's calling search space is the sole dictator of who it can
call.</SPAN><BR style="FONT-WEIGHT: bold"><SPAN
style="FONT-STYLE: italic"></SPAN><BR>Further,if we add devices to partitions
other than NONE, the NONE partition device loose access to other device. Is
this the case in opposite direction, that is visibility of route patterns in
NONE partition to devices in partition other than NONE.<BR><BR>What is the
difference b/w<SPAN style="FONT-WEIGHT: bold"> Force Authorization Code and
Client Matter Codes. </SPAN>What I understood that CMC allow the ability for
biliing and logging in CDR.<BR><BR>Need
Clarification!<BR><BR>Regards,<BR>Khalid<BR><BR>
<HR>
Explore the seven wonders of the world <A
href="http://search.msn.com/results.aspx?q=7+wonders+world&mkt=en-US&form=QBRE"
target=_new>Learn more!</A>
<P>
<HR>
<P></P>_______________________________________________<BR>cisco-voip mailing
list<BR>cisco-voip@puck.nether.net<BR>https://puck.nether.net/mailman/listinfo/cisco-voip<BR></BLOCKQUOTE></BODY></HTML>