McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 26

↗ View in doc context
page
26
source
unity-connection/v15/design-guide/design-guide.md
chunk_id
unity-connection::v15::design-guide::design-guide::7

Contacts can be configured as part of VPIM messaging and are accessible using directory access, name dialing access and Personal Call Transfer Rules. For more information on contacts, see the Contacts, on page 51 chapter. • Notification Templates: The notification feature allows alerting the user outside the context of a web page of an occurrence, such as the delivery of email or voice message. User accounts in Unity Connection can be configured for HTML notification on desired email addresses. The default notification templates or the ones customized by administrators provides an easy access to subscriber messages by enabling the HTML notification device. For example, the administrators can configure the HTML templates to include header, footer, logos, images, MWI status, and hyperlink to the Mini Web Inbox. For more information on notification templates, see the Notifications, on page 173 chapter. Configuring Telephony in Unity Connection Unity Connection integrations are built using a phone system configuration that includes one or more port groups. Each port group contain one or more ports that you can use to support connectivity between the phone system and Unity Connection. You can follow the below procedure to configure telephony integration in your organization. • Identifying the call agent for integrating Unity Connection. • Determining the integration type (SCCP/SIP/PIMG/TIMG/Secure SIP). • Configuring the phone system and adding ports as per the supported OVA and hardware requirements. • Defining the search space and partitions. • Mapping the routing rules with the call handlers as per your requirements. • Telephony Integration: It allows you to manage and integrate phone system in Unity Connection with a call agent for call processing functions, such as sending and receiving telephone calls. For more information on telephony integration, see the Telephony Integration, on page 61 chapter. • Phone System: A phone system in Unity Connection describes a single integration with a PBX or Cisco Unified CM system for call processing redundancy. The phone system contains global configurations that apply to the integrations, such as SIP and SCCP affecting all the port groups. For more information on phone system, see the Telephony Integration, on page 61 chapter. • Ports: Ports are endpoints in Unity Connection that answer calls (inbound) to record, retrieve messages, and handle call transfers.They can also initiate calls (outbound), as in the case of MWI and message notification. For example, if users use the clients (Cisco ViewMail for Microsoft Outlook) to retrieve voicemails, ports are not used for this operation, as long as they download the messages and listen using the workstation speakers. However, if users select IP phones to send or retrieve messages, a port is used. This operation requires a port to be configured for telephony record and playback (TRAP). Ports are associated to only one port group. For more information on ports, see the Telephony Integration, on page 61 chapter. • Port Groups: Port groups include one or more ports. Port groups contain most of the configuration settings for the integration, including the Message Waiting Indicator (MWI), IP address or hostname of the phone system, port numbers, advertised codecs, and other settings that apply to the ports within the port group. Multiple port groups can be configured depending on the type of integration method used for communication, such as SCCP or PIMG/TIMG. The multiple port groups are added under one phone system. For more information on port groups, see theTelephony Integration, on page 61 chapter. System Administration Guide 8 Introduction Configuring Telephony in Unity Connection