Does the routing affect CUBE Functionality
I did the Binding control/media on Loopback 0 , CUCM trunk pointed to this Loop0
ITSP pointed loop0 in our CUBE
outbound call to PSTN works well
Inbound call didn't work unless we change the binding from loop0 to G2 interface pointed to ITSP PoP Router
is that a logic or Bug or what
Nippon is absolutely correct you will need to do the bindings on the lan and towards the ISP. You would have agreed on an ip address to use with the ISP
@Nipun Singh Raghav wrote:
You need the CUBE to source packets from your internal/LAN/CUCM facing interface when routing calls to CUCM. When routing to ITSP, you would want to use a different IP which would be your public/ITSP facing interface. Why are you binding the same interface for both the traffic ? Your ITSP does not know how to route calls to an internal IP address.
Also with an incorrect bind, you cease the router's ability to listen to any other interface for 5060 port traffic.
Add correct binds to your dial-peers. LAN IP binded to CUCM facing dial-peers. Public IP binded to ITSP facing dial-peers.
This is NOT a bug.
I STRONGLY suggest you watch this Cisco Live session
SIP Trunking with Cisco Unified Border Element (CUBE/vCUBE) Enterprise and SRST Co-location - BRKCOL-2125