Pcf Cannot Read Timeout Reached Type: Blobstore Verifier

This document describes the steps to configure and troubleshoot Cisco Coming together Server (CMS) integration with Next Generation Streamer and Uploader. The Next Generation Streamer was introduced from CMS version iii.0 and is Session Initiation Protocol(SIP)-Based.

Requirements

Cisco recommends that yous accept knowledge of these topics:

• CMS Callbridge(s) Version iii.0 or later on with Recording/Streaming license(due south). (one recording license will permit one streaming telephone call)
• Vbrick Distributed Media Engine (DME) (used for publishing the live stream from CMS Streaming service)
• Vbrick Rev (optional: but required if Live Streaming need to be shared outside internal network or multicast
• Network File System (NFS) directory is needed, and information technology can be setup on Windows Server or Linux.
• For Windows server, follow the steps toDeploy Network File system (NFS) on Windows
• For Linux, follow the steps toDeploy Network File systemon Linux

Components Used

The information in this document is based on these software and hardware versions:

• CMS three.2and higher up with 'Recorder' and/or 'Streamer' license(due south). (recorder license will also let y'all to stream)
• VBrick Distributed Media Engine (DME) iii.15.0 Rhel7
• Vbrick Rev(Uploader is used with vBrick Rev server. No transmission importing of recordings is required)
• Windows Server 2012 R2 with NFS

CMS Version 2.1 and afterwards introduced support for live streaming with the CMS streamer using standard Real-Time Messaging Protocol (RTMP). In CMS 3.0, the Next Generation Streamer was introduced which is a SIP-based component. Prior version than three.0 usedExtensible Messaging and Presence Protocol (XMPP) . CMS version 3.1 and in a higher place support RTMPS protocol and thus communcation betwixt the CMS streamer component and external server tin be encrypted. This allows for the CMS streamer to integrate with whatsoever streaming platform that supports RTMP(S) (Youtube, Facebook, Wowza, then on). Currently the CMS Streamer has been tested with Vbrick DME as an external streaming server and is the recommended platform for integration.

Live Streaming (Webcast) integration with VBrick DME let users to sentinel any live streamed CMS conference anywhere inside the network from different devices. Additionally, when VBrick Rev is used forth VBrick DME, this extends this capability for viewing from exterior the internal network for every VBrick Rev authorized user.Also, CMS Uploader component simplifies the work menses for uploading Meeting Server recordings to the video content manager, Vbrick, from a configured NFS continued to a Meeting Server. No manual importing of recordings is required. In one case the Uploader component is configured and enabled, recordings are pushed from the NFS to Vbrick.

Streamer

The information in this certificate was created from the devices in a specific lab environment. All of the devices used in here started with cleared (default) configurations. If your network is alive, brand sure that you understand the potential impact of whatsoever control.

Uploader

The Uploader component tin exist installed on the same server as the Recorder component, or on a separate server. If installed on the aforementioned server as the Recorder, then add a couple of vCPUs for it to use. If run on a unlike server, and so use the same server specification as for the Recorder: defended VM with a minimum of 4 concrete cores and 4GB of RAM.

The Coming together Server running the Uploader will require  Read and Write permissions for the Network File Sharing (NFS). The Uploader must run on a different Meeting Server and non on Call Span hosting the conferences.

Network Diagram

In that location are several scenarios supported to deploy Streamer and Uploader with CMS such as: single callbridge with multiple streaming servers, a callbridge cluster with a single streaming server and callbridge cluster with multiple streaming servers. This document is based on a basic deployment with a cluster of callbridge connecting to a single streamer, Uploader server as all the configuration steps with this scenario apply to other scenarios likewise.

As shown in the higher up image

CMS CallBridge Cluster

CMS Streamer/Recorder

CMS Uploader

VBrick DME For Streaming

VBrick Rev For Streaming

Configurations

Streamer

It is causeless that the callbridge is already setup and accepting calls.

Step 1. Certificates

The new streamer components practise not require to listen https connections, however, information technology heed to SIP connections , the streamer server must take a valid certificate for TLS communication.

          streamer> pki csr tac CN:.*.tptac9.com subjectAltName:streamer.tptac9.com .............. ...... Created key file tac.key and CSR tac.csr CSR file tac.csr ready for download via SFTP        

Become the certificate signed from local Certificate Potency (CA). Upload the generate certificate using Secure File Transfer Protocol (SFTP) to the Streamer server. Checked to confirm the certificates uploaded successfully.

In this document wildcard certificates are used for streamer. Please utilise the document guide for reference.

https://www.cisco.com/c/dam/en/us/td/docs/conferencing/ciscoMeetingServer/Deployment_Guide/Version-iii-one/Document-Guidelines-for-all-Deployments-iii-1.pdf

          streamer> pki list User supplied certificates and keys: tac.key tac.cer ROOTCA.cer instance.primal example.csr tac.csr        

Step ii. MMP/SSH Configuration

• Configure the listening interface of the streamer and the SIP TCP and TLS ports to heed on using the MMP control

       streamer sip listen <interface> <tcp-port|none> <tls-port|none>

       streamer> streamer sip listen a 7000 7001

       To apply just TLS sip connectedness. Configure TCP sip connexion as "none" the control is beneath

       streamer> streamer sip listen a none 7001

• Apply certificates for the streamer server
     streamer> streamer sip certs tac.cardinal tac.cer

• Select the quality for streaming

       streamer> streamer sip resolution 720p

• Enable streamer

       streamer> streamer enable

• Optionally, if TLS is configured, yous can perform TLS verification for SIP on the streamer

       streamer> tls sip trust ROOTCA.cer

Note: For the TLS connectedness to be secure nosotros recommend enabling TLS verification.
streamer> tls sip verify enable

• Verfiy the configuration information entered above is correct

          streamer> streamer Enabled                 : false SIP interfaces          : tcp a:7000, tls a:7001 SIP key file            : tac.key SIP certificate file    : tac.cer SIP CA Packet file      : none SIP Resolution          : 720p SIP traffic trace       : Disabled Telephone call Limit              : none        

• Enable the streamer by using command: "streamer enable". All bulletin must show "SUCCESS" as below

          streamer> streamer enable SUCCESS: Key and certificate pair lucifer SUCCESS: Streamer enabled        

Step 3.API configuration

This configuration is performed in the CMS hosting CallBridge. Below, API on Webadmin interface of CMS. Any Remainder client like Postman, Poster tin can also be used to perform this.
In one case the new SIP streamer is enabled, it tin be configured and used in the Call Bridge nether /callProfiles for sipStreamerUri.

To apply API on CMS server. Become To  Webadmin > Configuration > API

• Create Telephone call Contour

• Configure sipStreamuri=demo@streamer.com & StreamingMode= Automatic/Manual

          The user part of the configured "sipStreamuri" (i.e. the part before '@' symbol) has no meaning meaning, and for the new SIP streamer component, although required, it can usually exist anything, e.g. "streamer@streamer.com".The of import role of the URI is the "domain" part.        

Configure sipStreamuri=demo@streamer.com & StreamingMode= Automatic/Manual

• Add the created streamer callProfile above to the /organization/profiles. This is a global configuration and the configured "sipStreamerUri" volition be used for streamer functioning.

Add the callProfile to arrangement/profiles

• Add the VBrick 'streamURL' to the infinite(s) used for streaming. For reference, a space called 'Stream' was created using the CMS web interface

Infinite used for Streaming

• Modify the space to add together "StreamURL". The 'streamURL' in the following format:rtmp://<VBrickBroadcastUsername>:<VBrickBroadcastPassword>@<VBrick IP or FQDN>/alive/NameoftheStream. In instance I configured it as "rtmp://circulate:broadcast@x.106.81.40/live/SpaceStream77"

Step 4. Create "Outbound Rules"

Configure, a custom URI that maps to an outboundDialPlan dominion (the domain can be anything for example "streamer.com"). Please configure an outboundDialPlan rule to match the domain used in streamerUri to route.

Create outbound rules

Equally shown in the above prototype, for SIP streamer, if default ports for SIP (5060,5061) are not used, then Information technology is mandatory to specify ports in the configuration of the streamer and include the following port number to connect to the "sip proxy to utilise" field when outboundDialPlanRule is configured for the service.

          streamer> streamer Enabled                 : true SIP interfaces          : tcp a:7000, tls a:7001 SIP key file            : tac.primal SIP certificate file    : tac.cer SIP CA Bundle file      : none SIP Resolution          : 720p SIP traffic trace       : Disabled Call Limit              : none        

Uploader

• Specify the NFS and directory where recordings will be stored that the Uploader volition monitor

    streamer> uploader nfs 192.168.xv.38:Recording

• Specify the Meeting Server that the Uploader will query for recording information

    streamer> uploader cms host join.mextp.local

• Specify the Spider web Admin port on the Coming together Server running the Call Bridge

    streamer> uploader cms port 445

• Specify the user with API admission on the Coming together Server running the Call Bridge

    streamer> uploader cms user apiadmin
    streamer> uploader cms password
    Please enter countersign:

• Add the certificate bundle from CMS to the Meeting Server trust store
   Create a certificate parcel (crt-bundle) holding a re-create of the Root CA's document and all intermediate certificates in the chain for the Web Admin on the Coming together Server running the Phone call Bridge.
   streamer> uploader cms trust ROOTCA.cer
• Configure the Vbrick host and the port to which the Uploader volition connect
   streamer> uploader rev host ciscotac.rev-na.demo.vbrick.com
   streamer> uploader rev port 443

Note: The port defaults to 443 unless otherwise specified​

• Add together a Vbrick Rev user who has API permission to upload video recordings
  streamer> uploader rev user tacuser
  streamer> uploader rev password
  Please enter password:
• Add the certificate parcel to the Vbrick Rev trust store

      Create a certificate bundle (crt-packet) belongings a re-create of the Root CA's document and all intermediate certificates in the concatenation for the Vbrick Rev serve
      streamer> uploader rev trust vbrickbundle.cer

• Cheque uploader configuration and enable uploader

          streamer> uploader Enabled                          : simulated NFS hostname                     : 192.168.15.38 NFS directory                    : Recording CMS host                         : join.mextp.local CMS port                         : 445 CMS user                         : apiadmin CMS trust packet                 : ROOTCA.cer Vbrick Rev hostname              : ciscotac.rev-na.demo.vbrick.com Vbrick Rev port                  : 443 Vbrick Rev username              : tacuser Vbrick Rev trust bundle          : brick.cer View access                      : Public cospace_member_access            : edit recording_owned_by_cospace_owner : false fallback_owner                   : admin comments_enabled                 : true ratings_enabled                  : true downloads_enabled                : true active_upon_upload               : truthful delete_after_upload              : false        

 If configuration is right, use "uploader enable" command to enable the Uploader component. All bulletin must show "SUCCESS" every bit shown beneath.

          streamer> uploader enable SUCCESS: uploader enabled        

 Streamer

Streaming working and a sip streaming telephone call continued

Uploader

 Yous can meet log for a successful event in syslog follow of uploader.

          Jun 17 22:24:41.867 user.info cms-02 Uploader[1]: scanning directory: /mnt/recordings/forwardedCalls Jun 17 22:24:41.867 user.info cms-02 Uploader[1]: scanning directory: /mnt/recordings/spaces Jun 17 22:24:41.869 user.info cms-02 Uploader[ane]: checking the status of /mnt/recordings/spaces/8a7076e2-6db6-47e9-98ee-3bd063e32559/20210618032309+0000_vid-id=c4605aaf-dc49-4cd7-9174-c46185ba1983@vbrick.mp4 Jun 17 22:24:41.870 user.info cms-02 Uploader[one]: Getting from: https://ciscotac.rev-na.demo.vbrick.com:443/api/v1/videos/c4605aaf-dc49-4cd7-9174-c46185ba1983/status Jun 17 22:24:42.035 user.info cms-02 Uploader[1]: Received vbrick response condition code: 200 Jun 17 22:24:42.035 user.info cms-02 Uploader[one]: vbrick response: main.vbrickStatusResp{Status:"Ready"} Jun 17 22:24:42.035 user.info cms-02 Uploader[ane]: file 20210618032309+0000_vid-id=c4605aaf-dc49-4cd7-9174-c46185ba1983@vbrick.mp4 vid c4605aaf-dc49-4cd7-9174-c46185ba1983 status Ready Jun 17 22:24:42.035 user.info cms-02 Uploader[i]: Getting from: https://ciscotac.rev-na.demo.vbrick.com:443/api/v1/videos/c4605aaf-dc49-4cd7-9174-c46185ba1983/playback-url Jun 17 22:24:42.200 user.info cms-02 Uploader[1]: Received vbrick response 200        

Streamer

one. No License

Streamer required "recorder" licnese on the server having callbridge component. If that is not at that place, or bereft license is nowadays, and then errors as shown below will exist seen in Event Logs.

Brand certain to add required license. Status of license tin can be checked CLI using the command "license"

          cms1> license Feature: callbridge status: Activated death: 2023-April-28 (690 days remain) Feature: plough status: Activated expiry: 2023-Apr-28 (690 days remain) Feature: webbridge status: Activated expiry: 2023-Apr-28 (690 days remain) Feature: customizations condition: Activated decease: 2023-Apr-28 (690 days remain) Feature: local_license_mode status: Activated expiry: 2023-Apr-28 (690 days remain) Feature: recording status: Activated expiry: 2023-April-28 (690 days remain) Feature: personal condition: Activated expiry: 2023-Apr-28 (690 days remain) Feature: shared condition: Activated expiry: 2023-Apr-28 (690 days remain)        

2.TLS port

• If TLS port configured and no certificates are practical. Configure certs for streamer to use TLS

• If certificate are not available. Configure the TCP port only

          streamer> streamer sip listen a 7000 7001 streamer> streamer enable FAILURE: TLS port set but no certificates configured FAILURE: Streamer configuration not complete        

Now you have 2 options, either to remove TLS Port, or to add SIP TLS Trust and Streamer Document

Cisco recommends to have TLS Port enabled.

iii. RTMP Sream not configured correctly

You volition see fault in logs

          daemon.info streamer streamer-sip[2280]:  144500.368 : INFO    : call three: retrieved stream URL from RTCP: "rtmp://broadcast:broadcast@x.106.81.40/test" daemon.info streamer streamer-sip[2280]:  144500.368 : INFO    : call 3: parsing rtmp://broadcast:broadcast@10.106.81.40/examination daemon.info streamer streamer-sip[2280]:  144500.368 : INFO    : call 3: RTMP stream="test" daemon.info streamer streamer-sip[2280]:  144500.368 : INFO    : call 3: RTMP server="rtmp://ten.106.81.40:1935/test" daemon.info streamer streamer-sip[2280]:  144500.370 : INFO    : phone call iii: Connected to RTMP server daemon.info streamer streamer-sip[2280]:  144500.370 : INFO    : call 3: C2 pending - len 1536 daemon.info streamer streamer-sip[2280]:  144500.370 :         : phone call iii: snd: create new chunk stream 2 daemon.info streamer streamer-sip[2280]:  144500.370 :         : call iii: snd: create new chunk stream 3 daemon.info streamer streamer-sip[2280]:  144500.370 : INFO    : call 3: RTMP sent chunk size of 4096 and connect message daemon.info streamer streamer-sip[2280]:  144500.410 : ERROR   : call three: connectedness : far end closed connexion v        

Please check the process in streamer configuration and configure RTMP URL correctly in the  format " rtmp://<VBrickBroadcastUsername>:<VBrickBroadcastPassword>@<VBrick IP or FQDN>/alive/NameoftheStream"

four.Call Routing Related Issues

Because the CMS streamer is a SIP-based client and as discussed earlier, information technology requires routing to be in place. This could cause scenarios where calls might neglect. Consider this example, where the CMS Callbridge sent an outbound call, just information technology failed with the following'transaction timeout - no provisional responses sending INVITE' error

2021-06-28  17:37:02.412  Info     user 'guest300535034' starting streaming (space 'exam') 2021-06-28  17:37:02.413  Info     API telephone call leg bc0917df-589c-4628-887d-79481d322fed in telephone call 63f0b174-831e-4a12-b4ee-27186d4162af (API call 00286960-9af9-4d5d-9ca7-20dd40425292) 2021-06-28  17:37:02.413  Info     call 44: outgoing SIP telephone call to "demo@streamer.com" from space "test" 2021-06-28  17:37:02.413  Info     call 44: configured - API call leg bc0917df-589c-4628-887d-79481d322fed with SIP call ID "7d37a80e-7996-4e8d-aa87-77c9d4729cec" 2021-06-28  17:37:04.482  Info     call 42: receiver written report 1 interval for rx video 0 = 6113ms (period 6108ms) 00000000 2021-06-28  17:37:22.074  Info     call 44: falling back to unencrypted control connection... 2021-06-28  17:37:54.075  Info     telephone call 44: catastrophe; local SIP teardown with reason 7 (transaction timeout - no provisional responses sending INVITE) - non connected after 0:52 2021-06-28  17:37:54.075  Info     call 44: destroying API call leg bc0917df-589c-4628-887d-79481d322fed 2021-06-28  17:37:54.076  Info     streaming call leg for space 'examination' disconnected with reason 7 (transaction timeout - no provisional responses sending INVITE)

Review the Outbound calls settings on the CMS Callbridge servers to validate the location information technology is being sent to and if being ready correctly. Also check if the callprofile is configured with correct streamer URI and same is associated with Cospace.

Uploader

ane. Vbrick detials not correct.

You lot tin can see error in Uploader log

          Jun 27 11:29:27.864 user.info streamer Uploader[1]: Received vbrick response 500 Jun 27 11:29:27.864 user.info streamer Uploader[ane]: posting to: https://sales.vbrick.com:443/api/v1/user/login Jun 27 xi:29:47.870 user.info streamer Uploader[1]: Received vbrick response 500 Jun 27 11:29:47.870 user.err streamer Uploader[ane]: Failed to initialise Vbrick Customer Jun 27 11:29:47.870 user.err streamer Uploader[one]: vbrick returned status code: 500        

Make sure to have configured the correct credentials and port for the vbrick server.  Besides make sure Uploader should exist able to reach CMS callbridge webadmin port.

pulversatione.blogspot.com

Source: https://www.cisco.com/c/en/us/support/docs/conferencing/meeting-server/217320-configure-cisco-meeting-server-cms-ver.html

Share this post