<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: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=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@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
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">I’ve seen it come two ways, riding your same MPLS circuit, in which case if you have a dedicated VG you just default route that to your MPLS router and there you go.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">The other way is like you say and I’ve done that with at&t and I didn’t have to route with them, they NAT’d everything on their side to me. So I just routed their couple SBC IPs/Subnets across that handoff and
my default still goes into my LAN.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I’m sure there are other ways as well.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;color:#1F497D">Matthew G. Loraditch – CCNP-Voice, CCNA-R&S, CCDA<br>
Network Engineer<br>
Direct Voice: 443.541.1518</span><span style="color:#1F497D"><br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><a href="https://www.facebook.com/heliontech?ref=hl"><span style="font-size:8.0pt;color:blue">Facebook</span></a></span><span style="font-size:8.0pt;color:#1F497D"> |
</span><span style="color:#1F497D"><a href="https://twitter.com/HelionTech"><span style="font-size:8.0pt;color:blue">Twitter</span></a></span><span style="font-size:8.0pt;color:#1F497D"> |
</span><span style="color:#1F497D"><a href="https://www.linkedin.com/company/helion-technologies?trk=top_nav_home"><span style="font-size:8.0pt;color:blue">LinkedIn</span></a></span><span style="font-size:8.0pt;color:#1F497D"> |
</span><span style="color:#1F497D"><a href="https://plus.google.com/+Heliontechnologies/posts"><span style="font-size:8.0pt;color:blue">G+</span></a><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> cisco-voip [mailto:cisco-voip-bounces@puck.nether.net]
<b>On Behalf Of </b>Norton, Mike<br>
<b>Sent:</b> Wednesday, February 04, 2015 5:05 PM<br>
<b>To:</b> Erick<br>
<b>Cc:</b> cisco-voip@puck.nether.net<br>
<b>Subject:</b> Re: [cisco-voip] CUBE across VRFs<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-CA" style="color:#1F497D">What I’m failing to understand is... if I set the CUBE’s default route to be my router on my network, then how will CUBE be able to reach the SIP provider’s call servers on the SIP provider’s network?
It seems like I will need a routing protocol on whichever side of the CUBE doesn’t get a default route. Is that a normal requirement?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="color:#1F497D">Just to back up a bit, I have been assuming CUBE would have two interfaces – one on my network, one on the SIP provider’s network. I’ve always assumed that this was the normal way of deploying CUBE
but maybe I’m off base there and getting myself confused.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="color:#1F497D">-mn<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"></a><span lang="EN-CA" style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Erick [<a href="mailto:erickbee@gmail.com">mailto:erickbee@gmail.com</a>]
<br>
<b>Sent:</b> February-03-15 6:50 PM<br>
<b>To:</b> Norton, Mike<br>
<b>Cc:</b> Jason Aarons (AM); <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> Re: [cisco-voip] CUBE across VRFs<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-CA">Only one voice vrf can be defined in IOS. Global under voice service voip.</span><span lang="EN-CA" style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-CA">Cube-SP lets you do multiple vrf's but is EoL and way different configuration. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-CA">If you plop a cube off your router and router interface is in a vrf and your separate cube is on that network then it should be fine as the cube is just a host then .... with default route to router.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-CA"><br>
Sent from my iPhone<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-CA"><br>
On Feb 3, 2015, at 6:08 PM, "Norton, Mike" <<a href="mailto:mikenorton@pwsd76.ab.ca">mikenorton@pwsd76.ab.ca</a>> wrote:<o:p></o:p></span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span lang="EN-CA" style="color:#1F497D">Doesn’t have to be two VRFs, could be one VRF and the global route table, if that makes a difference. This idea is no connectivity between them, other than the application-layer connectivity provided
by CUBE. This is hypothetical – I’m just trying to understand how/if this would work. I’m looking to plop a CUBE between my network and a SIP provider’s network without having to participate in routing protocol on either side.</span><span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="color:#1F497D"> </span><span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="color:#1F497D">-mn</span><span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="color:#1F497D"> </span><span lang="EN-CA"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Jason Aarons (AM) [<a href="mailto:jason.aarons@dimensiondata.com">mailto:jason.aarons@dimensiondata.com</a>]
<br>
<b>Sent:</b> February-03-15 5:02 PM<br>
<b>To:</b> Norton, Mike; <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> RE: CUBE across VRFs<span lang="EN-CA"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-CA"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">You have two VRFs, do they have connectivity between them?</span><span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span lang="EN-CA"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> cisco-voip [<a href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>]
<b>On Behalf Of </b>Norton, Mike<br>
<b>Sent:</b> Tuesday, February 3, 2015 4:36 PM<br>
<b>To:</b> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> [cisco-voip] CUBE across VRFs<span lang="EN-CA"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"> <span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> </span><span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal">Can CUBE sit across two separate VRFs? I’ve never used it, but I’m envisioning an ISR having a VRF-Lite with default route pointed at my network, and a VRF-Lite with default route pointed at the SIP provider’s network. I’m thinking this
would be the preferred way to do it, but maybe I’m missing something?<span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal"> <span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal">My Googling is dredging up a lot of really old info that I’m not sure is still relevant.<span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal"> <span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal">-- <span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal">Mike Norton<span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
<br>
<span style="color:white">itevomcid</span> </span><span lang="EN-CA"><o:p></o:p></span></p>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:12.0pt;font-family:"Times New Roman",serif">_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></span></p>
</div>
</blockquote>
</div>
</body>
</html>