Cisco Unity Connection Provisioning Interface (CUPI) API for SMTP Configuration

Publisher

Cisco Systems

URL

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/REST-API/CUPI_API/b_CUPI-API/m_smtp_configuration.html

Published

2022-06-20

Updated

unknown

Accessed

2026-10-02

HTTP status

200

License

Cisco documentation; all rights reserved; no-redistribution; short excerpts and locators only

Source notes citing this source

• Unity Connection's documented smart host authentication is a username and password, and no OAuth option was found. So a Unity Connection smart host pointed at smtp.office365.com with Use Authentication likely depends on Basic-auth SMTP AUTH and is exposed to Microsoft's retirement of it. inferred in context
• Per the CUPI SMTP client API, with IsClientSecure unchecked Unity Connection connects to the smart host on port 25 without STARTTLS, and with IsClientSecure checked it connects on port 587 using STARTTLS. in context
• Secure (STARTTLS) and authenticated SMTP client communication from Unity Connection to a smart host is supported from Unity Connection 14SU2 onward. in context
• Whether Unity Connection can run STARTTLS to a smart host on port 25 is unclear. The admin guide heading and the CUPI requirement both mention secure communication on ports 25 and 587, but the CUPI IsClientSecure description ties secure mode to port 587 and non-secure mode to port 25. inferred in context

Cite this source record

APA

WarmTransfer. (2022, June 20). Cisco Unity Connection Provisioning Interface (CUPI) API for SMTP Configuration. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-cupi-smtp-client-config

BibTeX

@misc{warmtransfer-cisco-cupi-smtp-client-config,
  title  = {Cisco Unity Connection Provisioning Interface (CUPI) API for SMTP Configuration},
  author = {{WarmTransfer}},
  year   = {2022},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-cupi-smtp-client-config},
  note   = {Cisco Systems, accessed 2026-10-02}
}