CME_MUM#
CME_ MUM (config-if)# interface loopback0 (choose an interface that would be used to register as an h323 endpoint to the gatekeeper)
CME_ MUM (config-if)#h323-gateway voip interface
CME_ MUM (config-if)#h323-gateway voip id Zone_Mumbai 142.102.64.1
CME_ MUM (config-if)#h323-gateway voip h323-id CME_MUM (does not have to be the hostname)
CME_ MUM (config-if)#tech-prefix 0091
CME_MUM(config)# gateway (the cme endpoint won’t register without the “gateway”command)
Registering the CUCM endpoint to the Gatekeeper:
Devices – Gatekeeper – Add the Gatekeeper by specifying the IP Address/Hostname of the Gatekeeper:
Devices – Trunks – H225 Gatekeeper Controller Trunk – Give the Trunk a name (CUCM_SYD) and then to the end of the page enter the endpoint details (Zone: in our example would be Zone_Sydney, Gatekeeper select from the drop down, tech-prefix 0061)
Note: The gatekeeper will automatically register all the cucm’s in the cluster by adding a number to the end of the trunk name (so in our case it would register both the CUCM endpoints as CUCM_SYD_1 and CUCM_SYD_2)
Important: Make sure you reset the trunk or you won’t see it register to the Gatekeeper...
Tech Prefix: So let’s say you want to make a call from PH1_LON to a number 0091222636104 (this is an actual landline PSTN number in Mumbai, India)... so you would want to send that call to the gatekeeper as a voip call and you would then want the gatekeeper to forward that call to your CME in Mumbai (CME_MUM) and hop off from there as a local call...
Whenever a call comes in to the Gatekeeper it first begins to match the first few digits of the called number to the tech-prefix of any of the endpoints registered to it, so in this case it would match that called number to the tech-prefix of the CME_MUM endpoint since we registered the CME_MUM endpoint above with the tech-prefix 0091, it then strips off that tech prefix and tries to match the remainder of the number (in our example, 0091 would be stripped off and 222636104 would be matched against a configured zone-prefix)... ..
Zone Prefix: The zone-prefix would tell the gatekeeper what zone that call is to be routed to (the above tech-prefix states what endpoint the call is to be routed to and the zone prefix says what zone of all the configured local zones is the call to be routed to)
GK(config-gk)# zone-prefix Zone_Mumbai 22....... (so this would tell the gatekeeper that all called numbers starting with a 22 followed by 7 digits would be sent to an endpoint in the local zone “Zone_Mumbai” and the endpoint within this local zone that the call gets routed to is determined by the Tech-Prefix that was already matched above 0091 which is CME_MUM).
So now since the gatekeeper has the tech-prefix matched and the zone-prefix matched it knows exactly which endpoint to send that call to which in our example is endpoint CME_MUM registered in zone Zone_Mumbai...
CME_ MUM (config-if)# interface loopback0 (choose an interface that would be used to register as an h323 endpoint to the gatekeeper)
CME_ MUM (config-if)#h323-gateway voip interface
CME_ MUM (config-if)#h323-gateway voip id Zone_Mumbai 142.102.64.1
CME_ MUM (config-if)#h323-gateway voip h323-id CME_MUM (does not have to be the hostname)
CME_ MUM (config-if)#tech-prefix 0091
CME_MUM(config)# gateway (the cme endpoint won’t register without the “gateway”command)
Registering the CUCM endpoint to the Gatekeeper:
Devices – Gatekeeper – Add the Gatekeeper by specifying the IP Address/Hostname of the Gatekeeper:
Devices – Trunks – H225 Gatekeeper Controller Trunk – Give the Trunk a name (CUCM_SYD) and then to the end of the page enter the endpoint details (Zone: in our example would be Zone_Sydney, Gatekeeper select from the drop down, tech-prefix 0061)
Note: The gatekeeper will automatically register all the cucm’s in the cluster by adding a number to the end of the trunk name (so in our case it would register both the CUCM endpoints as CUCM_SYD_1 and CUCM_SYD_2)
Important: Make sure you reset the trunk or you won’t see it register to the Gatekeeper...
Tech Prefix: So let’s say you want to make a call from PH1_LON to a number 0091222636104 (this is an actual landline PSTN number in Mumbai, India)... so you would want to send that call to the gatekeeper as a voip call and you would then want the gatekeeper to forward that call to your CME in Mumbai (CME_MUM) and hop off from there as a local call...
Whenever a call comes in to the Gatekeeper it first begins to match the first few digits of the called number to the tech-prefix of any of the endpoints registered to it, so in this case it would match that called number to the tech-prefix of the CME_MUM endpoint since we registered the CME_MUM endpoint above with the tech-prefix 0091, it then strips off that tech prefix and tries to match the remainder of the number (in our example, 0091 would be stripped off and 222636104 would be matched against a configured zone-prefix)... ..
Zone Prefix: The zone-prefix would tell the gatekeeper what zone that call is to be routed to (the above tech-prefix states what endpoint the call is to be routed to and the zone prefix says what zone of all the configured local zones is the call to be routed to)
GK(config-gk)# zone-prefix Zone_Mumbai 22....... (so this would tell the gatekeeper that all called numbers starting with a 22 followed by 7 digits would be sent to an endpoint in the local zone “Zone_Mumbai” and the endpoint within this local zone that the call gets routed to is determined by the Tech-Prefix that was already matched above 0091 which is CME_MUM).
So now since the gatekeeper has the tech-prefix matched and the zone-prefix matched it knows exactly which endpoint to send that call to which in our example is endpoint CME_MUM registered in zone Zone_Mumbai...
No comments:
Post a Comment