webrtc-as-rtmp-re-publishing-not-working

[Faraz Ahmed]

Hello @Max

How are you?
We are your old customer. W had cancelled that service 3 years ago due to some other features, Now we want to again use that feature.
We have installed web call server 5.2 on our server but its not going live to Facebook. Can you please check our server.
I have emailed SSH access to logs@flashphoner.com

Thanks,
Faraz

 

[Max]

Good day.
Please set the following parameters in flashphoner.properties file

rtmp_transponder_full_url=true
rtmp_transponder_stream_name_prefix=
rtmp_flash_ver_subscriber=LNX 76.219.189.0
rtmp_transponder_send_metadata=true

and restart WCS. If stream republishing to Facebook still don't work after this, please provide the following:
1. SSH access to the server.
2. RTMP URL and stream key to republish test stream to (should work 24/7).
Use this private form to provide the data.

 

[Faraz Ahmed]

Hi @Max

its not worked i have sent required information using private form.
Can you please check and configure it today

Thanks,
Faraz

 

[Max]

We checked the server.
First, you've not set the parameters recommended above:

rtmp_transponder_full_url=true
rtmp_transponder_stream_name_prefix=
rtmp_flash_ver_subscriber=LNX 76.219.189.0
rtmp_transponder_send_metadata=true

These parameters cover the most of RTMP ingest points (Youtube, FB, Twitch, AWS MediaLive etc)
But seems like FB rejects connection by the URL you've provided:
- connection from WCS:

- connection using ffmpeg:

Please check the RTMP URL and stream key.

 

[Faraz Ahmed]

Hi @Max

I had added that but when its still not working then removed it.
Its still not working even you added it. I have also tested it with YouTube please see below its failed.
Please check it and fix it we must need to fix it today. You can use your Facebook account stream key just to view on Facebook not go live.

 

[Max]

I had added that but when its still not working then removed it.

The settings are required for RTMP republishing to work. Perhaps that's why Youtube does not work.
We already checked (see above), and Facebook server closes the connection both from WCS and ffmpeg with Invalid URL message.
Please check if ffmpeg or OBS can publish an RTMP stream to Facebook using your credentials.

 

[Faraz Ahmed]

@Max can you please check it with YouTube or other social site.
Its also not working for other social sites

 

[Max]

@Max can you please check it with YouTube or other social site.
Its also not working for other social sites

Please provide RTMP URL and stream key to republish to Youtube using this form
Make sure that stream is publishing correctly from ffmpeg or OBS.

 

[Faraz Ahmed]

Hi @Max

I have checked with ffmpeg both Facebook and YouTube working for me with pre-recorded videos see below. I have also provided both stream keys and urls in the form

 

[Faraz Ahmed]

 

[Faraz Ahmed]

@Max you there? have you checked it?

 

[Max]

This is how it works:

1. Publish stream, i.e. 95ea

2. Set JSON body

{
"streamName": "95ea",
"rtmpUrl": "rtmp://a.rtmp.youtube.com/live2/2j0t-w4q7-6a52-achy-6tkx"
}

3. Send request to

http://IP:8081/rest-api/push/startup

4. Receive response 200 OK

{"mediaSessionId":"vncf7erhj5e7tkqv0qi77sq1fl","streamName":"2j0t-w4q7-6a52-achy-6tkx","rtmpUrl":"rtmp://a.rtmp.youtube.com/live2","rtmpFlashVersion":"LNX 76.219.189.0","rtmpTransponderStreamNamePrefix":"","width":0,"height":0,"fps":0,"bitrate":0,"keyFrameInterval":0,"rtmpTransponderKframeInterval":60,"muted":false,"soundEnabled":false,"rtmpTransponderForceKframeInterval":true,"rtmpTransponderFullUrl":true}

 

[Max]

Option 2.

rtmp_transponder_full_url=true

The setting will force you specify FULL RTMP URL including stream key

Therefore you set the full URL and it is woking as you can see on the screenshot:

rtmp://a.rtmp.youtube.com/live2/2j0t-w4q7-6a52-achy-6tkx

 

[Faraz Ahmed]

Hi @Max thanks for your explanation and help now its working for me.

 

[Faraz Ahmed]

Hi @Max

we are getting this error message "OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to staging.livepigeonapp.com:8081" while sending request to https://staging.livepigeonapp.com:8081/rest-api/push/startup
can you please let us know what should we need to fix in that case

 

[Faraz Ahmed]

@Max

 

[Faraz Ahmed]

 

[Faraz Ahmed]

Hi @Max

Looks like we have fixed it so ignore above messages

 

[Max]

we are getting this error message "OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to staging.livepigeonapp.com:8081" while sending request to https://staging.livepigeonapp.com:8081/rest-api/push/startup

By default, port 8081/tcp is used for unsecure connection and port 8443/tcp for secure one. You should use either https://wcs:8443/rest-api/push/startup or http://wcs:8081/rest-api/push/startup.

 

[Faraz Ahmed]

Hi @Max

when we use https://wcs:8443/rest-api/push/startup we get following error message "SSL certificate problem: unable to get local issuer certificate", Although we have already imported SSL from webcall server admin dashboard. Can you please let us know what's the issue

Thanks,
Faraz