/
SIP integration for VoH and ViQ

SIP integration for VoH and ViQ

Owned by Kiss, Mate
Jul 31, 2018

Configuration checklist for UCM

Step 1 - Create SIP trunk

Step 2 - Create Video On Hold Server (Media Resources\Video On Hold Server)

    • Default Video Content Identifier should be a number which on Verba side is assigned to a video clip. See this configuration later.
    • SIP Trunk is either a trunk list or trunk selected from the available trunks, pointing to Verba Cisco Announcement service

 

Step 3 - Assign Video On Hold to a Media Resource Group / Media Resource Group List

 

Step 4 - Assign the Media Resource Group List containing MRG/VOH to the desired devices either via Device Pool\Media Resource Group List or Device\Media Resource Group List

Please note if hold is initiated on voice only call then still the Verba service will provide MOH for these devices streaming the voice/audio part of the clips

Step 5 - For testing purpose, a route pattern might be set for the same number as provisioned in VOH server config. Calling this number the routing to trunk and streaming can be tested from the video endpoints

Step 6 - Check CAC and Codec Region settings to ensure video bitrate is configured properly between Verba trunk region and other regions

 

Configuration checklist for Verba

Step 1 - Activate Verba Cisco Announcement service. For full configuration reference click here

Step 2 - Create SIP port to terminate trunk from CUCM

    • With SIP Ports + icon add a new port
    • Fill SIP port (port on which service listens). On CUCM as trunk destination this address should be configured, see Step 1 CUCM side configuration
    • If secure trunk is configurated set the SSL/TLS certificate to use with this port. 
      • The certificate can be either a local PEM/PFX file (in this case file path and key password should be filled) or certificate stored in Windows Certificate Store Local Computer\Personal folder (in this case the certificate's thumbprint should be provided and key should be exportable and available)
      • If mutual authentication is desired set Trust list based on which Verba can validate incoming SIP connections. The setting can be:
        • empty: no validation on Verba side
        • thumbprint: either self-signed certificate with the thumbprint or CA-signed certificate where CA certificate matches the thumbprint is accepted
        • *: use windows top-level CA store
        • PEM file path: the file should contain certificate chain for CUCM

Step 3 - Start the service and reset the trunk on CUCM side


 

 

 

Related content