the usual voip dial-peer when we configure in gateway can only take the voice call to one-hop..
suppose we have 3 gateways A,B,C and A wants to call to C. If the call goes through B, there are 2 ways.. 1)B just routes the call as it routes a normal data packet...no call-processing logic needed..just functions as a pure router 2) B will use its call-processing "intelligence" to route the call inorder to do 1), its easy the dial-peer in the A should point to ip address of C. So noone knows that there is "B"..hence it just transparently routes... In this scenario The call must terminate at C..ie it must ring a pstn phone/pbx plugged to an analogue port in C. In such a case IP2IP GW aka cube is not required. In case 2), we need B to act as a IP2IP GW / CUBE.. so that B can become an active participant and the call is actually "routed" to multiple hops... A-B, B-C..so 2 hops here..for this the dial-peer of A must point to "B" and not to "C".. It will be the dial-peer of "B" that will have reference to "C".. hence A need not know "C" ip address at all during signalling... but then whether it needs to know the real "C" ip adress for rtp depends on CUBE config..read other resources and you will know more about it... feel free to shoot any questions to osl ;P Also whenever u need H323 gateway in CUCM u need CUBE..coz its always more-than-one-hop.. practically every gatway configuration that does call processing...other than CUCME needs CUBE... u can get away with using "dial-peer" without CUBE only for a single-hop... when IPPHONES come into picture this single-hop becomes history...its min 2 hops from then on ;P. NOTE: if intermediate routers only route transparently then they dont need CUBE...but if you want to terminate call to a router and it exceeds a single hop then u need CUBE. ofcourse there are more reasons for CUBE..eg for nat-security... read more about it and you will understand. Joel. On Fri, Aug 21, 2009 at 9:26 AM, Aamir Panjwani < [email protected]> wrote: > Please read last chapter on “CUBE” in CVOICE Cisco press book for > excellent explanation > > > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *devang patel > *Sent:* Friday, 21 August 2009 1:37 PM > *To:* [email protected] > *Subject:* [OSL | CCIE_Voice] IP To IP gateway > > > > Hi, > > > I am still trying to understand IP TO IP Gateway functionality. As per my > understanding we need Gateway when we have two different media to > communicate with each other. It will be great if some one can clear my doubt > about it. > > thanks, > Dev > > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > ______________________________________________________________________ > > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > ______________________________________________________________________ > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > -- "it's not the years in your life that count. It's the life in your years." Abraham Lincoln
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
