Recent content by fromin

  1. F

    SIP as RTMP not working again

    Any news? I need to get this done ASAP
  2. F

    SIP as RTMP not working again

    And yes I'm using the rtmp_ prefix when trying to play it (I'm trying it via the WCS dashboard)
  3. F

    SIP as RTMP not working again

    So I tried all of the combinations (restarted after modifying of course); results: sip_as_rtmp_use_new_engine=false **** streamnotfound when I tried to play the stream force_rtmp_audio_codec=speex16 ***** no sound (therefore no change when compared to the original settings)...
  4. F

    SIP as RTMP not working again

    The RTMP server is Wowza and I just checked that the Wowza configuration is identical
  5. F

    SIP as RTMP not working again

    Hmm, for some reason if I use the rtmp://dev.***.com as you did, it works, but with the other RTMP server (rtmp://staging.***.com), I'm not receiving the sound as I described earlier. I need this to work with staging
  6. F

    SIP as RTMP not working again

    Ok so I made some adjustments, the RTMP looks like it's capturing it correctly, but I cannot hear any sound, although the call is exactly 1 minute 16 seconds which it should be. Please try - I set up a dummy call that repeats "One two three" for 76 seconds.
  7. F

    SIP as RTMP not working again

    Ok I fixed the RTMP and it works now. Only thing is that getStatus now returns the stream ID, but on the other server it returns "ESTABLISHED" - is that because I have a newer version on this server?
  8. F

    SIP as RTMP not working again

    If it's the problem just with RTMP server not receiving the stream, why does the getStatus say "NO SUCH CALL" after 2 seconds of the call failing although the SIP call should take 100 seconds?
  9. F

    SIP as RTMP not working again

    Hi, so we tried to duplicate what we had working on our dev server to our live, but the call doesn't seem to be established correctly (after the first getStatus, it already returns "NO SUCH CALL" although the call should take over 100 seconds). I am sending an e-mail to logs@ now as well...
  10. F

    https?

    Never mind, works now, my mistake
  11. F

    https?

    It does work via the WCS dashboard though
  12. F

    https?

    Same if I try the 9091 port via https
  13. F

    https?

    Ok so I imported the keys successfully, the host:8888 now shows green https instead of crossed out red https which it was showing before, but a REST call to https://host:8888/RESTCall/call now returns 500 with empty body (no error message)
  14. F

    https?

    That does work for connecting to the admin, but not for RESTCall API; the API returns 500 with no body
  15. F

    https?

    How do I connect to the RESTCall API via https instead of http? Browsers won't allow http on an https website.
Top