Following on from Cisco Spark Hybrid - Call Connector Setup Part 1; the following information relates to the setup of Call Service Aware which is a prerequisite to the Call Connector. On Cisco Unified CM Enable Spark users for CTI control. The following steps can be followed to add users to the Standard CTI Enabled user group. The steps can also be found here. Select User Management > End User Select the user you want to add to the group Select Add to User Group in the Permissions Information group Search for Standard CTI Enabled in the Find and List User Groups window Select Standard CTI Enabled user group Select Add Selected Select Save Configure an application user to monitor devices enabled for CTI control.

The following text and screenshots coincide with the Deploying Cisco Spark Hybrid Services guide, and specifically with the Call Service Prerequisites. Additional articles will cover the Call Service Aware Deployment Steps and the Call Service Connect Deployment Steps. On Cisco Unified CM Set the mail ID of the user or import it from the LDAP directory. The User Mail ID can be found in UCM Administration > User Management > End Users > User.

Configure the Windows NFS Folder After the Server for NFS role has been installed, set up the Windows NFS Folder. To do this I created a folder C:\_Recorder. Configure the folders NFS properties as follows. Configure CMS Recorder In this specific post, the recorder and call bridge are on the same CMS as it is a small demo/test environment. In production this should not be the case, refer to the CMS guides for up to date deployment information.

Support forums thread Cisco Prime Collaboration Assurance and Analytics: Grade VoIP Calls using SCSR Instead of MOS White Paper For an environment using Cisco Video Conferencing devices, when running the CAR, CDR > Search > By User/Phone Number/SIP URL. The Media Info value for all records is null. According to the Cisco Prime white paper, this is expected behaviour: Note that all audio quality metrics listed in Table 1 are stored in the CMR.

Cisco Meeting Server with Expressway X8.9 Expressway Configuration At a high level, the following standard Expressway configuration is required. For more detailed steps refer to the Expressway configuration guides Traversal zone between the Expressway-C and the Expressway-E Search rule on the Expressway-E directing the inbound calls to the target domain to the Expressway-C via the Traversal zone Neighbour zone on the Expressway-C to the CMS Call Bridge Search rule on the Expressway-C directing the inbound calls to the target domain to the CMS Neighbour zone for Microsoft SIP calls (Microsoft Variants) External SRV record for Federation noted in the table below External DNS record:

From the Office 365 Admin Center, navigate to the Skype for Business Admin Center Navigate to the online meetings menu object From this screen specify a logo if desired, the size can be no bigger than 188x30, and the format must be JPEG Specify the Footer text. For example the IVR SIP URI and WebRTC details for the CMS Click Save Changes can take an hour to replicate. Once they have, any new Skype Meeting in Outlook will reflect the changes.

SIP/2.0 503 Service Unavailable Observed in Expressway-C trace SIP/2.0 503 Service Unavailable Via: SIP/2.0/TCP 1.1.1.241_EXPC:5060;egress-zone=CEtcp192168994;branch=z9hG4bK3eca9d5dc4e26de65b1b83f501cea485458555;proxy-call-id=51ce23fa-d8d1-4c22-9579-ade0f631d257;rport,SIP/2.0/TLS 1.1.1.241_EXPC:5073;branch=z9hG4bK1e991e55187479dada6391ef5adf084024563;x-cisco-local-service=nettle;received=1.1.1.241_EXPC;rport=30979;ingress-zone=DefaultZone,SIP/2.0/TLS 1.1.1.241_EXPC:5061;egress-zone=DefaultZone;branch=z9hG4bKb340db4a70e04cc037ea7de16e55df58458554.3d8de2b0006ebe59e4c4ae2fde61ae57;proxy-call-id=1ceee43f-3413-4f0f-bfcb-aed8a3b2ad03;received=1.1.1.241_EXPC;rport=29605,SIP/2.0/TLS 1.1.1.246_EXPE:7001;egress-zone=UCtoEXPC2;branch=z9hG4bKf0e07263c19c7bfd6133775994af916998831.7b4bb0bfbe6838be4f4507d0ce70df61;proxy-call-id=bc3fdcb9-f10b-4f23-a0d1-1e59e49de578;received=1.1.1.246_EXPE;rport=7001;ingress-zone=UCtoEXPE2,SIP/2.0/TLS 0.0.0.0_USER:43932;branch=z9hG4bK00004aa4;received=2.2.2.2_EXPEPUB;rport=43932;ingress-zone=CollaborationEdgeZone Call-ID: aefdce71-0af2001c-00004664-00007833@0.0.0.0_USER CSeq: 101 INVITE From: “Jason Neurohr” <sip:30822@1.1.1.1_CUCM>;tag=aefdce710af2021f0000027c-00000f51 To: <sip:12345@domain.com.au>;tag=698699~2004fc79-b651-49b6-be90-35de0e0192d1-48112662 Server: Cisco-CUCM10.5 Date: Wed, 28 Dec 2016 02:37:57 GMT Allow-Events: presence Reason: Q.850 ;cause=41 Observed on CUCM trunk Status Reason local=2 Discussion This issue occurred on an Expressway pair where both MRA and B2B were configured. The zone towards CUCM was configured to use a non-standard port and this configuration was reciprocated on the CUCM trunk and security profile.

This document was written based on an environment with the following devices: UCM 11.0.1 (Required from CE8.2.0) TelePresence Conductor XC4.3 Virtual TelePresence Server 4.4(1.16) MX800 Dual CE8.3 CUCM Configuration Following best practices copy the existing Standard SIP Profile For TelePresence Conferencing and modify Timer Invite Expires (seconds) to be 30. Other requirements should already be satisfied when copying this profile, however specifically ensure: SDP Transparency Profile = Pass all unknown SDP attributes Allow iX Application Media = Checked Allow multiple codecs in answer SDP = Checked Configure regions such that call speed will be high enough to support multistream.

Acano KB article - Troubleshooting Web Bridge connectivity issues Unable to connect - try again later In this specific case the problem is due to the fact that the Web Bridge is not able to resolve the DNS SRV record for _xmpp-client._tcp.domain.com. Dec 19 01:57:00 user.info mmp health: average power usage in last 5 minutes: 171.9W; peak 174.2W; 37.9 kWh total since Fri Dec 9 23:21:27 2016 Dec 19 01:57:19 user.

Log into Cisco Unified OS Administration Navigate to Device > Device Settings > Device Defaults Note the current load information for the target device down Download the firmware from Cisco. E.g for the IX5000 the cop file is cmterm-IX.8-2-0-28R-K9.P3.cop.sgn Copy the COP file to an SFTP server (the rest of this text assumes the root has been used) Log into Cisco Unified OS Administration Navigate to Software Upgrades > Install/Upgrade Fill out the software location details substituting where appropriate Click Next, on the following screen select the COP file previously downloaded and copied to the SFTP server from the drop down list Once downloaded confirm the MD5 signature matches what is provided on the Cisco.