Ed,
All phones re-registering is expected behavior for when any CallManager,
CAPF, or TVS certificate on any node in the cluster is regenerated. This
is to allow phones to download an updated ITL before another certificate
change is made. This is also the same reason all phones re-register when
Ed.
All changes that cause an ITL file to update, such as regenerating
certain certificates or changing host or domain names (which cause cert
regens themselves) cause an Enterprise Phone Reset. Changing names
(certs) on multiple CUCM servers causes multiple enterprise resets. This
is by design
It is not possible to modify this list outside of Cisco releasing a COP
file.
https://developer.cisco.com/media/UCM10.5DataDictionary/UCM10.5DataDictionary.htm#productsupportsfeature
I would suggest opening a feature enhancement request through your account
team to make this user configurable
Hey mate,
I’ve used SCCP and SIP inspection in the past
Bit rusty maybe, but here is the jist
- If you have a firewall with Jabber clients on one side, phones on
the other, and maybe a CUCM in a separate segment, maybe even a voice gateway
in another segment
- With
Brian:
If so, you'll want to use a Collab Edge architecture as it's not safe to open
up CUCM/IMP directly.
On this sort of campus, I still struggle with this concept. Network access
isn't controlled with 100% lockdown hosts and computers. I can't see anyone
buying a hybrid model where some
