Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
In working with devicelistx, I have found that every so often I get a record with a status code (s=) of 3. Thus far I have not found any doc that enumerates what 3 means. It is a relatively uncommon occurence. On clusters with an average size of 6...
Greetings,We have developed some internal caching apps leveraging the use of the Cisco-provided devicelistx.asp. We have used the tool to evaluate and verify environment changes before/after a change control.Everything works fine, except we have fou...
I have a custom app that connects to devicelistX asp and pulls down device information for follow up apps/scripts. It has been working very well for a while now.My issue is that we recently consolidated two clusters and we have well over 9,000 total...
Not sure I follow how this is related.Anyway, I found out that the status code of "3" refers to a device that is experiencing registration failures.An example is a phone that is configured as a 7936 in CM, but is actually a 7960.Regards,Bill
Same concept, different DNS feature. We use CNAME records and can push changes to the DNS server. This requires that you have a relatively short lifetime on DNS auth. responses.Another approach, if you have the equipment, is to use a load balancer ...
Depending on the nature of your environment and roles of the people involved, you could use IPMA to achieve this behavior. IPMA comes with some extra baggage that may be unattractive, but it is an option.
There are several methods, some of which are:1. (all gateway types)Put translation pattern for ingress calls in partition only visible from TDM gateway. Set CSS of translation pattern to allow visibility on your line side partition(2), service parti...