After upgrading to 3.0.1, I try to set up streaming and, apparently, ran into problems.
I configure streamer on a separate VM
Enabled: true
SIP interfaces: tcp a: 5060, tls a: 5061
SIP key file: cmsstr.key
SIP certificate file: cmsstr.cer
SIP CA Bundle file: chain-n.cer
SIP Resolution: 1080p
SIP traffic trace: Disabled
Call Limit: none
Where cmsstr.cer (key) is the streamer certificate, chain-n.cer is the intermediate and root certificates.
On CMS1 (I have a cluster of 3 virtual machines) I configure in outgoing calls
Domain: streaming.local
SIP proxy to use: IP address of the recorer
Trunk type: Standard SIP
Encryption: Unencrypted
In CallProfile I specify streamer@streaming.local as sipStreamerUri and streaming type - automatic.
In CoSpace, which needs to be streamed, I indicate the path and password to WOWZA in the format
rtmp: // cms: password @ address / live / CMSSTREAM and specify CallProfile
As a result, I get the error Streaming Streamer "streamer@streaming.local" unavailable (connect failure)
A similar error occurred in version 2.9.X in the case of incorrectly specified TRUST BUNDLE, but in version 3.0 it is not used.
Perhaps you can tell me where I am wrong or what I do not understand in the new version of the CMS
