<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40"
xmlns:ns0="http://schemas.microsoft.com/sharepoint/soap/workflow/"
xmlns:ns1="http://schemas.openxmlformats.org/markup-compatibility/2006"
xmlns:ns2="http://schemas.microsoft.com/office/2004/12/omml"
xmlns:ns3="http://schemas.openxmlformats.org/package/2006/relationships"
xmlns:ns4="http://schemas.microsoft.com/exchange/services/2006/types"
xmlns:ns5="http://schemas.microsoft.com/exchange/services/2006/messages"
xmlns:ns6="urn:schemas-microsoft-com:">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--a:link
{mso-style-priority:99;}
span.MSOHYPERLINK
{mso-style-priority:99;}
a:visited
{mso-style-priority:99;}
span.MSOHYPERLINKFOLLOWED
{mso-style-priority:99;}
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";
mso-believe-normal-left:yes;}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:Calibri;
color:#1F497D;}
span.EmailStyle18
{mso-style-type:personal;
font-family:Calibri;
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<![if mso 9]>
<style>
p.MsoNormal
{margin-left:3.0pt;}
</style>
<![endif]><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple style='margin-left:3.0pt;margin-top:
3.0pt;margin-right:3.0pt;margin-bottom:.75pt'>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Very valid point Jason, but if they have,
say, 6 PRI’s, they can break it up into 2 NFAS groups and create a trunk
group from A to B on the Telco side. With 6 trunks, they only gain 1
channel, but as it scales up after that.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>DNFAS (distributed) should be something
that cisco is working on if they’re not. I would have to think that
NFAS can’t be any chattier than something like SCCP or MGCP. Supporting
NFAS through MGCP would be cool to, especially since all the D-Channels are
backhauled anyway.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>But these are just 2 of the things that I
think could be done that aren’t (i.e. friggin FXO caller ID on MGCP which
is finally coming to pass). <o:p></o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='margin:0in;margin-bottom:.0001pt;
text-align:center'><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</span></font></b><font
size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Jason Aarons (US)<br>
<b><span style='font-weight:bold'>Sent:</span></b> Tuesday, July 29, 2008 2:58
PM<br>
<b><span style='font-weight:bold'>To:</span></b> James Buchanan; STEVEN CASPER;
cisco-voip@puck.nether.net<br>
<b><span style='font-weight:bold'>Cc:</span></b> RAWLE GORDON<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [cisco-voip] NFAS
with D Channel Back Up</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>IOS NFAS requires
the PRIs be on same chassis with H323 which defeats high availability. I
would work with telco to issue change order to remove the NFAS and split the
PRIs between two or more 28xx/38xx. You can then have telco use Trunk Groups
for incoming and you can use Route Groups/Route Lists for outgoing.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>NFAS was great when
you had one really big refrigerator PBX with full redundancy, but when you have
distributed routers it doesn’t fit as well.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p> </o:p></span></font></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</span></font></b><font
size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <b><span style='font-weight:bold'>On
Behalf Of </span></b>James Buchanan<br>
<b><span style='font-weight:bold'>Sent:</span></b> Tuesday, July 29, 2008 2:51
PM<br>
<b><span style='font-weight:bold'>To:</span></b> STEVEN CASPER;
cisco-voip@puck.nether.net<br>
<b><span style='font-weight:bold'>Cc:</span></b> RAWLE GORDON<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [cisco-voip] NFAS
with D Channel Back Up<o:p></o:p></span></font></p>
</div>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>You can use NFAS
since the requirement is that you use H323. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p> </o:p></span></font></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</span></font></b><font
size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b><span
style='font-weight:bold'>On Behalf Of </span></b>STEVEN CASPER<br>
<b><span style='font-weight:bold'>Sent:</span></b> Tuesday, July 29, 2008 1:47
PM<br>
<b><span style='font-weight:bold'>To:</span></b> cisco-voip@puck.nether.net<br>
<b><span style='font-weight:bold'>Cc:</span></b> RAWLE GORDON<br>
<b><span style='font-weight:bold'>Subject:</span></b> [cisco-voip] NFAS with D
Channel Back Up<o:p></o:p></span></font></p>
</div>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> Getting
ready to finally convert PSTN trunking from some larger Nortel PBX systems to
Cisco gateways. Up to this point we have been using PRI tie lines between the
PBXs and Cisco gateways and routing PSTN calls via the PBX. On the PBXs
we are using various PSTN PRIs using primary and backup D channels and in some
cases NFAS. Can these connectivity options be recreated in a Call
Manager 6.1 environment or will I need to order new PRIs with individual D-Channels?
Can not seem to find any info on this<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>We use a
combination or 28xx and 38xx gateways<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>Thanks!<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>Steve<o:p></o:p></span></font></p>
</div>
</div>
</body>
</html>
<HTML><BODY><P><hr size=1></P>
<P><STRONG>
Disclaimer:
This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you.
</STRONG></P></BODY>