User Community Feedback

One of the good features in CUCM is the ability to copy items to create new items, suchas phones, templates, etc. However, in all my years working with CUCM, and my years as a Cisco Partner, I hear customers and other engineers occasionally ask why can't we copy SIP trunks. I see the use case of having different destinations for call routing, different sip trunks, different route patterns, but the same or very similar configuration. I realize in some cases, such as SIP TLS, that the SIP security profile would need to be changed as the FQDN for the certificates are different, but you can copy SIP security profiles. The ability to copy SIP trunks in CUCM, could speed up configuration and setting up/adding SIP trunks.