- Is loopback interface supported on Cisco CUBE to terminate SIP trunks?
- Can I configure a single Loopback interface with a new IP address and terminate multiple SIP trunks to this single Loopback interface?
Yes, you can most certainly use a loopback interface address for your SIP trunks. You just need to make sure the interface address is routable across the various networks. To use the same IP address across multiple tenants, you need to ensure that you don't have any IP address overlap.
That said, the challenge with "binding" to a central address on a CUBE is that you usually are looking to do topology hiding. If that isn't a requirement then I believe you can achieve your objective.
If you are doing topology hiding or you just want to segregate the tenants logically then you can do a bind command on individual VoIP dial-peers to make things more deterministic.
For example:
dial-peer voice 79002 voip
description SIP to UCM Cluster
preference 2
session protocol sipv2
session target ipv4:10.10.10.10:5060
destination e164-pattern-map 10
voice-class sip bind control source-interface
voice-class sip bind media source-interface
dtmf-relay rtp-nte
codec g711ulaw
ip qos dscp cs3 signaling
no vad
!
- Only If above is supported, is it recommended to use a single interface/IP to terminate all SIP trunks or configure multiple sub-interfaces to terminate each of the SIP trunk?
I am not sure about Cisco recommendations in this configuration scenario. I am typically doing a 2-sided CUBE. I think that if I had a scenario similar to yours, then I would create separate interfaces but that is because I am a control freak.
- Want to confirm,can a SIP trunk be directly established between client SBC & Cisco CUBE IP address or any other SIP server/device is required in the middle?
Generally speaking you should not require a 3rd SBC between two SBCs. The CUBE is essentially a SBC but it is "Unified", so that makes it extra special ;-)
HTH
-Bill (http://ucguerrilla.com)
