If any one knows TEHO configuration please help me?
I Configured HQ with h323 gatway along with CUCM 7.1 and branches has 2801-CCME bundles
Check out the SRND link for some information
Thanks for immediate reply. Can you please provide more techincal document.Let me expalin you my scenarion again
1: HQ,we have CUCM7.1 with Cisco2851 voice gateway.Gateway is configured on H323(not MGCP gateway)
2: Branches are connected using Cisco2801-CCME bundles
HQ is connected with branches using non-gatekeeper controlled trunks(inter cluster trunks)
So please provide more detailed technical document
As an example let us say CCM is at HQ(New York) and one of the CCME is in San Jose. If a user in NY wants to dial an area code in San Jose and do TEHO, then let us say you define a route pattern 408111XXXX and any other area codes in 408 you want to do TEHO. This route pattern will point toward your CCME as H323 gateway. On the CCME router you have a VOIP dial peer that matches that pattern and basically sends it out the local trunks
Thanks for your reply.
But i have here the issue of creating route groups and adding gateways to it.
As i explained to you i have created non gatekeeper controlled trunks.So i am creating the route groups and then trying to add the remote gateway, which gateway has to be selected first(remote should be)?As i dont find the remote gateway in the list.
Do i need to add the remote gateways in the CUCM first?
I have created below one but still i need to do some config on gateway:
1: Created first route group and added remote gateway
2: created second route group and added local voice gateway
3: Created route list and added route groups in order
4: then created route pattern
Now i need some configuration of voice gateway(dial-peers).Do i need to do some digit manipulation on voice gateway or its enough if we do on cucm
The use of route groups and route lists allow the administrator to massage a number prior to egress. In MGCP GW's, we use CUCM to modify the called party to match the local GW. With H323, you can either transform the number on the CUCM at the RG level or you can send a standard E.164 number and let the dial-peers on the GW modify the called party number to match the local connection. Either way will work.
Technical Marketing Engineer
Thanks for your reply.I transformed the number in RG level in cucm and created dialpeer preferences in GW.But still call is going to through the local gateway it is not going through wan remote gateway.
Let me explain you my scenario:
1: I have One HO installed CUCM & Cisco 2851 gateway configured as H323
2: Six branches has Cisco2801-CCME connected with HO.In CUCM i created Non-Gatekeeper controlled trunks to connect with branch offices.
My questions is that do i need to installed Gatekeeper to handle the TEHO call.Or shall i go with this config
You might be running into a nuance of CUCM that is not well understood in the field. If you look at your GW's that are defined in the RL, where are they registered?
Based on your description, I believe that the 'local' GW is registered to the same CUCM as the Route List. Up until 8.5, a RL would choose a local gateway over other gateways in a route group if the gateway was registered to the same node as the RL. This behavior would baffle some customers that expected different GW selection. There have been changes in CUCM 8.5 to change this behavior.
Do i need to add the remote gateway in gateway list for selection of first priority gateway in RL or shall i use existing trunk?
I'm not sure what you mean. A Route Group is the collection of a gateways that have similar dialing requirements (area code or digit strip). When you add devices to a RG, calls should be round robined w/in the group. If all gateways in the RG are at capacity, then CUCM will chose the next RG in the Route List. If you want to guarantee a call to egress a specific gateway first using RL/RG, then you will need to create a RG that contains just that GW and make that RG the first entry in the RL.
Technical Marketing Engineer
Retrieving data ...