A SIP call made through the WCS server can be captured to an RTMP stream and rebroadcast to the specified RTMP server when the call is created. One usage example is publishing a call to Facebook or Youtube.
- The browser starts a call by sending the /call/startup REST query.
- WCS connects to the SIP server
- The SIP server sends the RTP stream of the call to WCS
- WCS connects to the RTMP server
- The RTMP server receives the RTMP stream
Quick manual on testing
1. For the test we use:
- two SIP accounts;
- a softphone to answer the call;
- the REST client in the Chrome browser;
- the RTMP server to receive the broadcast;
- the Player web application to play the stream from the RTMP server.
2. Open the REST client. Send /call/startup to the WCS server and specify in the parameters of the query the following data:
- parameters of your SIP account the call is made from;
- URL of the RTMP server the call is republished to, in this case - specify the URL of the WCS server;
- the name of the stream to rebroadcast the call to (the rtmpStream parameter), for instance, rtmp_stream1;
- the name of your second SIP account where the call is made to.
3. Receive and answer the call on the softphone:
4. Open the Player web application. Specify the URL of the RTMP server and the name of the RTMP stream the call is redirected to, then click the "Play" button. The call starts playing:
5. Terminate the call in the softphone.
Below is the call flow when using the SIP as RTMP example to create a call
1. Sending the /call/startup REST query:
2. Establishing a connection to the SIP server
3. Receiving confirmation from the SIP server
4. The RTP stream is sent to the WCS server
5. Publishing of the RTMP stream on the RTMP server
6. The RTMP stream is passed to the RTMP server
7. Sending the /call/terminate REST query:
8. Sending the command to the SIP server
9. Receiving confirmation from the SIP server
1. Stream captured from SIP call, can not be played, if RTP session is not initialized for this stream.
Symptoms: SIP stream is published on server, but can not be played.
Solution: enable RTP session initializing with the following parameter
2. SIP callee does not recognize DTMF signals if audio data generation is no enabled
Symptoms: SIP callee does not recognize PIN code sent as DTMF
Solution: enable audio and video data generation for SIP call with the following parameter
3. Freezes may occur, audio may be out of sync with video when republishing a SIP call stream as RTMP
Symptoms: freezes and audio/video out of sync are observed while playing an RTMP stream republished from a SIP call
Solution: add the delay to audio/video generator start