<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:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (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>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
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","serif";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.ecmsonormal, li.ecmsonormal, div.ecmsonormal
{mso-style-name:ec_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","serif";}
span.ecmsohyperlink
{mso-style-name:ec_msohyperlink;}
span.ecmsohyperlinkfollowed
{mso-style-name:ec_msohyperlinkfollowed;}
span.ecemailstyle17
{mso-style-name:ec_emailstyle17;}
p.ecmsonormal1, li.ecmsonormal1, div.ecmsonormal1
{mso-style-name:ec_msonormal1;
mso-margin-top-alt:auto;
margin-right:0in;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.ecmsohyperlink1
{mso-style-name:ec_msohyperlink1;
color:blue;
text-decoration:underline;}
span.ecmsohyperlinkfollowed1
{mso-style-name:ec_msohyperlinkfollowed1;
color:purple;
text-decoration:underline;}
span.ecemailstyle171
{mso-style-name:ec_emailstyle171;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle28
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[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>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thanks Khalid for the link. I will give it a shot. Have you
tried doing it w/ translation patterns in Call Manager before sending it to the
voice gateway? Also, Can you think of any side effects of using Trunk Groups
for the fxo ports in instances like this?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Syed Khalid Ali
[mailto:khalid_khursheed@hotmail.com] <br>
<b>Sent:</b> Thursday, June 19, 2008 4:23 PM<br>
<b>To:</b> Roush, David; cisco-voip@puck.nether.net<br>
<b>Subject:</b> RE: [cisco-voip] H323 w/ a PRI and 8 Copper Line for Subtenant<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>Hi,<br>
<br>
I had a similar problem where some of executives had to have a dedicated phone
line. However major calls were done via 2 x PRIs. Check this link for
mapping out calls to FXO ports:<br>
<br>
<i>http://www.cisco.com/en/US/tech/tk652/tk90/technologies_configuration_example09186a00801bc341.shtml</i><br>
<br>
I hope this helps!<br>
<br>
regards,<br>
<br>
Khalid<o:p></o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>Date: Thu, 19 Jun 2008 14:15:20 -0400<br>
From: droush@mckennalong.com<br>
To: cisco-voip@puck.nether.net<br>
Subject: [cisco-voip] H323 w/ a PRI and 8 Copper Line for Subtenant<o:p></o:p></span></p>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>I’m
about to migrate one of our remote offices from an Avaya G3 to Call Manager
4.2(3) and they have a subtenant. Our office calls come/go via a single PRI and
the Subtenant uses 8 Analog Lines for their calls. We would like to continue
this pattern, but I’m having a hard time figuring out how to route the
subtenant’s calls out the analog ports. We will be using a 2851 w/ a
VWIC2-2MFT for the PRI and 2 x VIC2-4FXO cards for the 8 analog lines. The
gateway is going to be setup using H323. I figure I can separate
everything using Partitions and Calling Search Spaces, but I can’t figure
out how to force the subtenant calls out via the fxo ports. My first thought
was to setup the gateway as both H323 and MGCP and create separate Route
Groups/Route List. Use H323 for PRI and MGCP for the FXO ports. Then create
route patterns and assign them to the proper Route List. Another thought was to
create a translation pattern for outgoing calls for the subtenant to translate
it from 9 to another digit and create a matching dial-peer and send it out the
fxo ports. Is there an easier way of handling this?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Thanks<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><br>
David <o:p></o:p></span></p>
</div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p> </o:p></span></p>
<pre style='margin-bottom:12.0pt'>CONFIDENTIALITY NOTICE: <br>
This e-mail and any attachments contain information from <br>
the law firm of McKenna Long & Aldridge LLP, and are <br>
intended solely for the use of the named recipient or <br>
recipients. This e-mail may contain privileged <br>
attorney/client communications or work product. Any <br>
dissemination of this e-mail by anyone other than an <br>
intended recipient is strictly prohibited. If you are not a<br>
named recipient, you are prohibited from any further <br>
viewing of the e-mail or any attachments or from making any <br>
use of the e-mail or attachments. If you believe you have <br>
received this e-mail in error, notify the sender <br>
immediately and permanently delete the e-mail, any <br>
attachments, and all copies thereof from any drives or <br>
storage media and destroy any printouts of the e-mail or <br>
attachments.<o:p></o:p></pre>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p> </o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Invite
your mail contacts to join your friends list with Windows Live Spaces. It's
easy! <a
href="http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mkt=en-us"
target="_new">Try it!</a><o:p></o:p></span></p>
</div>
<P><pre wrap>CONFIDENTIALITY NOTICE:
This e-mail and any attachments contain information from
the law firm of McKenna Long & Aldridge LLP, and are
intended solely for the use of the named recipient or
recipients. This e-mail may contain privileged
attorney/client communications or work product. Any
dissemination of this e-mail by anyone other than an
intended recipient is strictly prohibited. If you are not a
named recipient, you are prohibited from any further
viewing of the e-mail or any attachments or from making any
use of the e-mail or attachments. If you believe you have
received this e-mail in error, notify the sender
immediately and permanently delete the e-mail, any
attachments, and all copies thereof from any drives or
storage media and destroy any printouts of the e-mail or
attachments.
</pre></P></body>
</html>