Hi all, I have a dial-peer with no preference and another dial-peer with preference 10 which is a backup. I use 2 dial-peer to outbound calls to remote gatekeeper1 (dial-peer 1) or remote gatekeeper2 (dial-peer 2). Usually outbound calls match gatekeeper1 with higher preference but sometimes also gatekeeper2 (even though gatekeeper1 is working properly). Is there any other way more then just setting preference to route outbound calls this way?
One possibility could be that Gatekeeper1 is not responding to some request in a timely manner. If the request to Gatekeeper1 times out, then the router will use the dial-peer with the next preference and try Gatekeeper2.
By enabling "debug h225 asn1" on the gateway, you should be able to see if this is the case.
thank you, I'm going to try. Actually I have a "local" gatekeeper, 2 remote gatekeepers with high preference (one is near, the other really not) and a backup remote gatekeeper (dial peer preference 10). Could it be that my gatekeeper use round robin so when it sends calls to the far remote gatekeeper there is a time-out and so the call is switched to the backup gatekeeper?
So it really depends how gatekeeper are configured. If they are clustered together, then gatekeeper with higher priority will route the call to its destination.
In this case if you have 2 dialpeers pointing 1 to primary GK and other to secondary GK. If a call fails on the primary,it depends on what is the cause code of that failed call? As an alternative you can use "voice hunt xxxxx" command in the global mode to reroute the call based on the cause code received from other side. It will hunt the next dialpeer.
Another option is to use alternative endpoints and prioritize them.
You can also set hunting preferences on the dialpeers so that the first dialpeer will match:
C2811(config)#dial-peer hunt ?
<0-7> Dial-peer hunting choices, listed in hunting order within each choice:
0 - Longest match in phone number, explicit preference, random selection.
1 - Longest match in phone number, explicit preference, least recent use.
2 - Explicit preference, longest match in phone number, random selection.
3 - Explicit preference, longest match in phone number, least recent use.
4 - Least recent use, longest match in phone number, explicit preference.
5 - Least recent use, explicit preference, longest match in phone number.
Thanks for the config. In your case this GW is registered to GKA. Primarily it should always use GKA unless there is a IP failure and it is not reachable, then GKB should be used. I recommend you to use GK clustering for GKA and GKB. It is a seamless process.
Now since you are using tech-prefix routing in this case, GK will route the call based on tech-prefix match.
You will want to manually define zone prefix's
and zone prefix priorities in your gatekeeper.
Within the context of zone prefix configuration you have the option to define gateway priorities.
Use the gw-priority option to define how the gatekeeper selects gateways in its local zone for calls
to numbers beginning with prefix e164-prefix. Use values from 0 to 10. A 0 value prevents the
gatekeeper from using the gateway gw-alias for that prefix. Value 10 places the highest priority on
gateway gw-alias. If you do not specify a priority value for a gateway, the value 5 is assigned.
In addition, you will want to use the technology called RAI. This is because the T1 will not
unregister with the gateway if it goes down and the GK will not know that it can't route the call to
the gateway just because the T1 is down. With RAI, the gateway and the gatekeepers are constantly
talking about the availability of the T1.
Here is a link for defining zone prefix priorities.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...