Michael, Thanks for the response, much appreciated.
You say it covers ANY scenario where the GW or GK can not complete the call. Is this correct? My understanding was it comes into play when the cause code returned for a call failure is 'unallocated number'. Something like ISDN cause code 0x81. Apologies for not being clear in my original mail. What I was asking was specific scenarios where it may actually be of use, in our sort of environment. For example. RL with GK primary and GW secondary. I dial 3009 - an unassigned number at BR2. The call is attempted via the GK first. The far end responds unallocated. If this param is set to FALSE then it will try the GW. But since the number is unallocated there is no point in setting this param and trying to reach the unallocated number a second time, is there? What I am looking for is a scenario where this param is actual of use, in our environment. Many thanks. On Sat, Oct 25, 2008 at 4:58 PM, Michael Shavrov <[EMAIL PROTECTED]>wrote: > Everyone uses it. Basically what it does - when call goes to a gateway or > gatekeeper, and the gateway cannot complete the call (for whatever reason - > remote side is down, no bandwidth, etc.), CallManager continues searching > for other Route Grous in the Route List. Without this parameter (when it set > to True), if CallManager receives "Unallocated Number" signal, it will stop > searching for other "paths" and give you fast busy (basically gateway > redundancy will not work). > > > > ----- Original Message ----- > *From:* jonny vegas <[EMAIL PROTECTED]> > *To:* [EMAIL PROTECTED] <ccie_voice@onlinestudylist.com> > *Sent:* Saturday, October 25, 2008 10:51 AM > *Subject:* [OSL | CCIE_Voice] Stop routing on unallocated number service > param > > Anyone got scenarios where we would specifically use this param. > > Thanks > >
