<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=utf-8">
<META content="MSHTML 6.00.2900.3492" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px">
<DIV>Nick,</DIV>
<DIV> </DIV>
<DIV>Do you have a link that details VRF support for these features? I for one am particularly interested in using VRF with CUBE for an IP Trunking implementation. </DIV>
<DIV> </DIV>
<DIV>Thanks,</DIV>
<DIV>Steve</DIV>
<DIV> </DIV>
<DIV>
<DIV><FONT face=Arial color=#006600 size=2>Please consider the impact on our environment before printing this e-mail.</FONT> </DIV><BR><BR>>>> Nick Matthews <matthnick@gmail.com> 3/3/2009 4:37 PM >>><BR>VRF support was introduced into 12.4(22)T for some features such as:<BR>CME<BR>MGCP<BR>SIP<BR>H323<BR>CUBE<BR>SCCP<BR><BR>It still does not have full support for every feature (like RSVP), so<BR>this is probably correct. That, or the document was written before<BR>this feature was released.<BR><BR><BR>-nick<BR><BR>On Tue, Mar 3, 2009 at 3:29 PM, Lelio Fulgenzi <lelio@uoguelph.ca> wrote:<BR>> A colleague forwarded this on....do a CTRL F for voip<BR>><BR>> <A href="http://www.cisco.com/application/pdf/en/us/guest/netsol/ns171/c649/ccmigration_09186a0080851cc6.pdf">http://www.cisco.com/application/pdf/en/us/guest/netsol/ns171/c649/ccmigration_09186a0080851cc6.pdf</A><BR>><BR>> When deploying a VoIP architecture to be integrated in a virtualized<BR>> network, the current best practice design recommends to keep the main<BR>> components of the voice infrastructure (VoIP handsets, Cisco CallManagers,<BR>> Cisco Unity Servers, and so on) in the global table, together with all the<BR>> users that use voice services (using Cisco Communicator software, VT<BR>> Advantage, and so on). Reasons for following this recommendation in this<BR>> phase of the technology include the following:<BR>> –Current lack of VRF-aware voice services such as Survivable Remote Site<BR>> Telephony (SRST) or Resource Reservation Protocol (RSVP) for Call Admission<BR>> Control (CAC), which would prevent a successful deployment of VoIP<BR>> technologies at remote locations (without the burden of replicating the<BR>> physical network infrastructure, which is against one of the main drivers<BR>> for virtualizing the network). Also, Cisco CallManager does not currently<BR>> officially support multi-tenant environments.<BR>> - Complex configuration required at the services edge of the network to<BR>> allow the establishment<BR>> of voice flows between entities belonging to separate VPNs. This would also<BR>> require<BR>> “punching” holes in the firewall deployed in this area of the network,<BR>> increasing the security<BR>> concerns of the overall solution.<BR>> - VoIP can be secured without requiring the creation of a dedicated logical<BR>> partition for the voice<BR>> infrastructure. There are proven tools and design recommendations that can<BR>> be used for<BR>> hardening the voice systems that are inherent in the system and do not<BR>> require any form of<BR>> network virtualization to be implemented. For more information, see the<BR>> Voice SRND at the<BR>> following URL:<BR>> <A href="http://www.cisco.com/en/US/netsol/ns656/networking_solutions_design_guidances_list.html#">http://www.cisco.com/en/US/netsol/ns656/networking_solutions_design_guidances_list.html#</A><BR>> anchor10<BR>> When the VoIP infrastructure is deployed in the global table, the direct<BR>> consequence is the recommendation of keeping all the internal users that<BR>> make use of VoIP applications (such as Cisco Communicator clients, for<BR>> example) in the same domain, to not complicate the design too much when<BR>> there is a need to establish voice flows between these users and, for<BR>> example, the VoIP handsets. This is inline with the recommendation given in<BR>> the first bullet point dictating the creation of virtual networks only for<BR>> specific purposes.<BR>><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>> "Bad grammar makes me [sic]" - Tshirt<BR>><BR>><BR>> _______________________________________________<BR>> cisco-voip mailing list<BR>> cisco-voip@puck.nether.net<BR>> <A href="https://puck.nether.net/mailman/listinfo/cisco">https://puck.nether.net/mailman/listinfo/cisco</A>-voip<BR>><BR>><BR>_______________________________________________<BR>cisco-voip mailing list<BR>cisco-voip@puck.nether.net<BR><A href="https://puck.nether.net/mailman/listinfo/cisco">https://puck.nether.net/mailman/listinfo/cisco</A>-voip<BR><BR></DIV><pre>************************************
This email may contain privileged and/or confidential information that is intended solely for the use of the addressee. If you are not the intended recipient or entity, you are strictly prohibited from disclosing, copying, distributing or using any of the information contained in the transmission. If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. This communication may contain nonpublic personal information about consumers subject to the restrictions of the Gramm-Leach-Bliley Act and the Sarbanes-Oxley Act. You may not directly or indirectly reuse or disclose such information for any purpose other than to provide the services for which you are receiving the information.
There are risks associated with the use of electronic transmission. The sender of this information does not control the method of transmittal or service providers and assumes no duty or obligation for the security, receipt, or third party interception of this transmission.
************************************
</pre></BODY></HTML>