viazones have always been one of the most misunderstood topics- hence this email to provide some clarity.
In a nutshell- Invia is always checked (for ARQ and for LRQ) before outvia but outvia is used more often. Let's look at an example. Imagine that we have UCM and CME each registered in their own independent local zone and also a third remote Backbone zone defined on another gatekeeper. Extension 4XXX is routed to the CME and international calls (numbers beginning with 011) are routed to the backbone zone. Config below: gatekeeper zone local zoneUCM abc.com zone local zoneCME abc.com zone remote BB abc.com 1.1.1.1 1719 zone prefix zoneCME 4... zone prefix BB 011* no shut Let's look at two calls. UCM > GK > CME and also UCM > GK > BB. Note - in both cases zoneUCM is the source zone and zoneCME/BB are the destination zones for the two calls respectively. If we add a CUBE to the config we can invoke the CUBE in two ways. INVIA gatekeeper zone local zoneUCM abc.com invia VIAZONE zone local zoneCME abc.com zone local VIAZONE abc.com zone remote BB abc.com 1.1.1.1 1719 zone prefix zoneCME 4... zone prefix BB 011* no shut In this instance the CUBE will be invoked for both types of calls since the source zone has been configured with an invia command. And in both types of calls that we are making the source zone is zoneUCM. Note- If we configure outvia for zoneUCM the CUBE will not be invoked since it is the invia that is used on source zones. OUTVIA With the invia configuration above we invoke CUBE for any call coming from the UCM zone. We don't care where the call is destined for- as long as the call comes from zoneUCM we invoke the CUBE. If we only wanted to invoke CUBE for calls to the backbone (and not for calls from UCM > GK > CME) then do as follows: gatekeeper zone local zoneUCM abc.com zone local zoneCME abc.com zone local VIAZONE abc.com zone remote BB abc.com 1.1.1.1 1719 outvia VIAZONE zone prefix zoneCME 4... zone prefix BB 011* no shut For the call UCM > GK > BB the CUBE is invoked since the destination zone has been configured with an outvia. For the call UCM > GK > CME the CUBE is not invoked since neither the source zone (zoneUCM) nor the destination zone (zoneCME) has been configured with an invia/outvia. One last thing to mention- if the source zone has been configured with an invia AND the destination zone has been configured with an outvia, the invia trumps the outvia and the outvia is not used (CUBE is not invoked twice). On Feb 7, 2012, at 12:03 PM, datucha123 datucha123 wrote: > Outvia is more accurate. > > Invia, in most cases, is used for incoming LRQs. > > On Tue, Feb 7, 2012 at 11:13 PM, mercy forall <[email protected]> > wrote: > Hi All > > now in outvia and invia ,, > > Are is it deference if i use it in local zone or remote zone ? > > As per Doc, outvia for any traffic leave this zone , so are this same if i > use outvia in local or remote zone > > > I need to send the call form local zone to remote zone through CUBE as local > zone , > > what is the correct [zone remote with outvia OR with invia CUBE ] ? > > thanks > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > Are you a CCNP or CCIE and looking for a job? Check out > www.PlatinumPlacement.com > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > Are you a CCNP or CCIE and looking for a job? Check out > www.PlatinumPlacement.com
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
