Issue - when a site that isnt using LRG calls a site that is --> and the called party has their phone forarded to Mobile/Cell Phone --> the call fails.
Question 1: A:Why is this ??
B: Is it Normal behaviour?
C:Can you have the sites in the cluster running with LRG and other not LRG
If the forwarded phone is hitting a Route Pattern which, in turn, is associated to a Route List that only has "Local Route Group" defined then yes, this is expected behavior. Basically, when the CUCM call routing routines encounter an entry for "Local Route Group" in a Route List, CUCM will check the device pool of the calling party. If that device pool does not have a LRG assigned, then CUCM will go to the next entry in the Route List. If there is no such entry, the CUCM has no way of knowing how to route the call.
In response to question 1C, yes you can have LRG and non-LRG running at the same time. So, you can have a route list which contains a reference to Local Route Group and have zero or more other "standard" route groups. Further Local Route Group can occur at any priority position in a Route List.
Is there a service Parametre to change this bevaiour to say in an event the calling parties gateway in LRG are down use the called parties LRG to route the call???
No such option exists today. You would need to design your dial plan to account for issues like the ones you have described. For instance, if you had one central site with more trunk capacity than other sites, you could designate that site for failover or overflow situations at other sites. Same basic rules as pre-LRG.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
[toc:faq]CUCM Database Replication is an area in which Cisco customers
and partners have asked for more in-depth training in being able to
properly assess a replication problem and potentially resolve an issue
without involving TAC. This document discusse...