Archive for the ‘Gatekeeper’ Category

GK Call routing

Posted: September 18, 2006 by sankar in Gatekeeper

 Click to enlarge Click on link to enlarge the pic.


Gatekeeper – Viazone behaviour

Posted: September 11, 2006 by cciestudy in Cisco General, Gatekeeper

How to trigger via zone behaviour?

Local zones – always enable outvia on the destination zone

Remote zones – use invia or outvia on the remote zone

Via-zone gatekeepers differ from legacy gatekeepers in how LRQ and ARQ messages are used for call routing. Using via-zone gatekeepers will maintain normal clusters and functionality. Legacy gatekeepers examine incoming LRQs based on the called number, and more specifically the dialedDigits field in the destinationInfo portion of the LRQ. Via-zone gatekeepers look at the origination point of the LRQ before looking at the called number. If an LRQ comes from a gatekeeper listed in the via-zone gatekeeper’s remote zone configurations, the gatekeeper checks to see that the zone remote configuration contains an invia or outvia keyword. If the configuration contains these keywords, the gatekeeper uses the new via-zone behavior; if not, it uses legacy behavior.

For ARQ messages, the gatekeeper determines if an outvia keyword is configured on the destination zone. If the outvia keyword is configured, and the zone named with the outvia keyword is local to the gatekeeper, the call is directed to a Cisco Multiservice IP-to-IP Gateway in that zone by returning an ACF pointing to the Cisco Multiservice IP-to-IP Gateway. If the zone named with the outvia keyword is remote, the gatekeeper sends a location request to the outvia gatekeeper rather than the remote zone gatekeeper. The invia keyword is not used in processing the ARQ.

IPIPGW Gatekeeper lookup

Posted: August 13, 2006 by cciestudy in Gatekeeper

When using IPIPGW, you need to define a zone prefix to route calls. invia zones does not use the default technology.

Gatekeeper trunk redundancy

Posted: August 3, 2006 by cciestudy in Gatekeeper

If you have two gatekeeper trunks, one in a G711 region and the other in a G729 region and you setup the Route list with G711 as the first priority and G729 as the second priority and the gatekeeper does not have enough bandwidth to process a G711 call, then it will fallback and use the G729 trunk to process the call.

You do not need to enable BRQ to make this happen.

Gateway registration to gatekeeper

Posted: August 1, 2006 by cciestudy in Gatekeeper

For a gateway to register with a gatekeeper, there should be at least one voip dial-peer defined in the gateway.

If it is a CME router, then when you define ephones, that will create dial-peer and hence that will work fine.

If you define a zone prefix for a local zone , then it will prevent gateways from registering using E.164 ID to that zone.

zone local zone10
zone prefix zone10 5000

With this configuration, none of the gateways can register to zone10 using E.164 ID’s.

Coming soon……..