02-21-2018 02:10 PM - edited 03-17-2019 12:15 PM
Dear All,
I would like to use the new-ish CUBE multivrf feature (documented here). One of the limitations is:
Multi-VRF is not supported on TDM-SIP gateway
What is actually meant by this? If I wanted to run say an MGCP controlled NIM-4FXS on the same router as the CUBE, could it be done?
Many thanks
James.
Solved! Go to Solution.
02-22-2018 08:15 AM
02-21-2018 02:25 PM
02-22-2018 12:33 AM
Thank you Nipun, but my question really is about whether it's possible to combine CUBE with Multi-VRF and still host an analog card on the same router. The business case is to supply a single fax line at the site without purchasing an additional device.
Regards
James
02-22-2018 01:12 AM
02-22-2018 01:34 AM
Thanks Nipun. So, if I want to run CUBE with MultiVRF and then have a separate loopback (in the default vrf) which is binded to MGCP and controlling an analog card, that would be a supported setup?
Sorry to keep pressing this question, but i basically want to clarify what Cisco mean by "not supported on TDM-SIP gateway".
02-22-2018 04:07 AM
02-22-2018 04:14 AM
> what is the purpose of having vrf’s in your network ?
To keep the routing tables of various ITSPs segregated. It's a security and manageability feature.
> Do you have vrf’s configured already ?
Yes
> Is there a reason for using mgcp ?
I think we're going round in circles here..Let me rephrase the question. "With CUBE MultiVRF configured, can I add an analog card into the CUBE and make this card MCGP controlled?"
02-22-2018 05:23 AM
02-22-2018 08:09 AM
Thanks Nipun, but I'm still not quite 100% clear on what's meant by:
1. Multi-VRF is only supported on SIP to SIP call flows.
Let's say we have:
Fax -> VG224 -> MGCP -> CUCM -> SIP -> CUBE_MULTIVRF -> SIP Itsp
This is not a SIP call end-to-end, but is it is SIP on either side of the CUBE itself. Is this supported?
Regards
James.
02-22-2018 08:15 AM
03-08-2023 06:57 AM
This is an old post, but I can see that in IOS-XE 17.6+ the limitation ("Multi-VRF is not supported on TDM-SIP") has gone.
Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards, then look at Restrictions.
03-31-2024 10:21 AM
Just a quick shout out to anyone implementing CUBE MultiVRF and using IOS-XE v17.x (that should be most people at the time of writing), there is a bug which prevents calls matching the incoming dial-peer if a SIP message (e.g. Options Ping) arrives during router bootup:
https://bst.cisco.com/bugsearch/bug/CSCwj06857
Luckily, this can easily be worked-around by binding the control and media interface under 'voice service voip' and you can still override at the dial-peer level to achieve MultiVRF separation.
i.e. If you are running MultiVRF and IOS-XE v17.x. make sure this is configured:
voice service voip
sip bind control source-interface x
bind media source-interface x
exit
03-31-2024 03:12 PM - edited 03-31-2024 10:46 PM
Great information. However per the bug note a better, or at least more specific, workaround is to use tenant configuration bindings for different types of dial peers, for example to CM or ITSP.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide