Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Apr 05 17:45

    avspeed on master

    add remove screen sharing event (compare)

  • Apr 05 17:45

    avspeed on master

    add remove screen sharing event (compare)

  • Apr 02 20:37

    avspeed on master

    MuteAudio/UnMuteAudio update u… (compare)

  • Apr 02 20:37

    avspeed on master

    MuteAudio/UnMuteAudio update u… (compare)

  • Apr 02 12:18

    avspeed on master

    fixed socket username property (compare)

  • Apr 02 12:18

    avspeed on master

    fixed socket username property (compare)

  • Apr 02 12:13

    avspeed on master

    added JoinWebMeeting - returns… (compare)

  • Apr 02 12:13

    avspeed on master

    added JoinWebMeeting - returns… (compare)

  • Mar 31 02:01

    avspeed on master

    added GetParticipants function (compare)

  • Mar 31 02:01

    avspeed on master

    added GetParticipants function (compare)

  • Mar 30 15:33

    avspeed on master

    trying out acknowledgements (compare)

  • Mar 30 15:33

    avspeed on master

    trying out acknowledgements (compare)

  • Mar 30 13:48

    avspeed on master

    added custom function call (compare)

  • Mar 30 13:48

    avspeed on master

    added custom function call (compare)

  • Mar 30 02:34

    avspeed on master

    Added function to get list of p… (compare)

  • Mar 30 02:34

    avspeed on master

    Added function to get list of p… (compare)

  • Mar 21 02:58

    avspeed on master

    remove unecessary code (compare)

  • Mar 21 02:58

    avspeed on master

    remove unecessary code (compare)

  • Mar 21 01:26

    avspeed on master

    use websockets (compare)

  • Mar 21 01:26

    avspeed on master

    use websockets (compare)

Team@AVSPEED
@avspeed
@LucioJSimoes great - glad that it is resolved
AlehD
@aleh4d
Hi, we want to use Kurento WebRTC Media Server with IConfRTCWPF control. How to setup a media server in IConfRTC?
suravi999
@suravi999
Hi, How to share screen?
viktor martinez
@ahal_tocob_twitter
Hi, download the example windowsform and run it, but nothing happened, only the panel was locked. I have to configure something?
Team@AVSPEED
@avspeed
@ahal_tocob_twitter Hello, ok any exceptions in the console ? What version of Visual Studio are you using ?
StonePaleAle
@StonePaleAle
Hello. Is there a way to get the latest licensed libraries? I have tried re-downloading my order, and still get the older dlls. Thanks
Team@AVSPEED
@avspeed
@StonePaleAle hello, please try again. All orders have been updated to get the latest licensed dlls - If you run into any issues please reach out. Thank you and sorry for the inconvenience
Team@AVSPEED
@avspeed
@StonePaleAle we are going to publish updated nugets/ demos as well sometimes tonight, and the updated licensed version will also be available for download
StonePaleAle
@StonePaleAle
@avspeed Got 'em. Thanks! There is an issue, though. Using the new licensed ddls in the latest example WPF app and connecting to the test server, I have no video (Connects, but no video displayed). Swapping them back out with the unlicensed dlls that are packaged with it, the video works.
Also, can you provide another zip containing the necessary files for running the signaling server locally (with node.exe)? The one I was sent previously works with my original licensed dlls. No issues there. The new dlls do not work with it, and I can’t get the Signaling-io-master on GitHub to work with any of them. (that is probably me, though)
Thanks! I am continuing on with the original libraries. I just wanted to take advantage of any updates that you all have added. I'll watch for the updated demos!
Team@AVSPEED
@avspeed
hello @StonePaleAle yes the latest dlls will not work with the old signaling server. We are working on updating everything tonight. We will post back here when completed - Thanks
Team@AVSPEED
@avspeed
@StonePaleAle All demos have been updated and the new signaling server is also on github
@StonePaleAle Please also note that in the latest version of the SDK, the video will not start automatically. In our demo you will see we call the StartVideo method when the user joins teh meeting. You can also have a button for example that starts the video for the user at any time. A few users complained about the privacy issue when auto starting the video, whcih makes sense. The audio however will start by default. You can mute/unmute at will
StonePaleAle
@StonePaleAle
@avspeed - Thanks! I got the latest demo, and retrieved the licensed dlls again. I see version 1.0.1.26. But - when I connect to the test signaling server, I still see the iConfRTC Trial Edition overlay on the video.
Team@AVSPEED
@avspeed
@StonePaleAle oops . Thanks for letting us know. Give us a few minutes and we will re-upload teh licensed dlls (without the trail message ) sorry about that
Team@AVSPEED
@avspeed
@StonePaleAle licensed dlls have been updated. Please try again - Thanks
StonePaleAle
@StonePaleAle
@avspeed Got 'em. Looks good. Connected the demo and my app to the test signaling server. Thanks!
StonePaleAle
@StonePaleAle
Anyone have luck getting the new signaling server to work? I get it to run locally, but I can't connect to it with the new libraries.
Team@AVSPEED
@avspeed
@StonePaleAle did you get it to work ? Dont for get the / at the end of your signaling url or ip address
abelm688
@abelm688
@StonePaleAle @avspeed I'm having the same issue. I haven't been able to get the newest licensed library to connect to the new signalling server. I also pulled the new WinForms demo app, and haven't been able to connect to signalling with it either. The signalling server will run locally, but never accepts a connection.
Team@AVSPEED
@avspeed
@abelm688 can you paste your <add key="SignalingUrl" key here ?
@abelm688 is your signaling server listening ?
abelm688
@abelm688
<add key="SignalingUrl" value="https://10.0.0.9:9000/" />
Netstat -q shows that the port is open and listening.
I sent an email to support@avspeed with some more details if that helps
Team@AVSPEED
@avspeed
can you switch to just 10.0.0.9:9000/
@abelm688 can you switch to just 10.0.0.9:9000/
abelm688
@abelm688
Changing to <add key="SignalingUrl" value="10.0.0.9:9000/" /> has the same result.
Team@AVSPEED
@avspeed
@abelm688 I am going to clone the signaling server that is on github and run a quick test. brb
abelm688
@abelm688
Ok. Thanks!
Team@AVSPEED
@avspeed
@b
@abelm688 can you try <add key="SignalingUrl" value="http://10.0.0.9:9000/" />
Team@AVSPEED
@avspeed
@abelm688 I just ran a quick test by cloning the repo, npm install the socket.io dependency and started listening on port 9000. I then chgange the config in the WEBRTCWinformTest demo to point to <add key="SignalingUrl" value="http://10.0.0.3:9000/" /> and I was able to join the meeting
StonePaleAle
@StonePaleAle
@avspeed Running with http allows it to attempt, but I am seeing this: info - unhandled socket.io url repeated every second or so.
abelm688
@abelm688
@avspeed Same here. The signalling server begins showing info - unhandled socket.io url, but the app never joins the conference. It stays on the join screen as before.
StonePaleAle
@StonePaleAle
@avspeed @abelm688 I was able to get it to work. I removed the extra folders from node_modules, and only included socket.io (from npm install). Connected right up.
abelm688
@abelm688
@StonePaleAle @avspeed Deleting the node_modules folder and re-running npm install socket.io worked for me. The demo app is now connecting properly. Thanks StonePaleAle!
Team@AVSPEED
@avspeed
@abelm688 @StonePaleAle glad that this is resolved. I just realized that the npm install step is missing from the github page. I will add it.
@abelm688 I saw your email about the licensed version. I appreciate the heads up about that.
abelm688
@abelm688
@avspeed Thanks for looking into the problem. I just finished more extensive testing and everything is working perfectly with this library version except for the device selection. Unfortunately the project I am working requires the use of a document camera that shows up as a webcam device, and the iConf control always uses the document camera instead of the actual webcam. I will send an email with the code I am using for device selection in case it is just something I am doing wrong.
@avspeed And no problem on the licensed email. It just seemed odd so I wanted to let you know.
StonePaleAle
@StonePaleAle
@abelm688 @avspeed Any update on the device selection issue? I haven't been able to get it to work with the latest version. No matter which IDs I pass in, it always selects the same camera. The old version worked fine, but the latest libraries do not. Thanks
abelm688
@abelm688
@StonePaleAle They released a new build, 1.0.1.36, yesterday that fixed the problem for me.
Team@AVSPEED
@avspeed
Thanks @abelm688 , @StonePaleAle yes. A new build was relased yesterday. The updated license version is also available for download that shodul fix the issue.
@StonePaleAle the demos are also up to date
@StonePaleAle iconfRTC.SelectDevice("HD Pro Webcam C920 (046d:082d)", DeviceType.Video);
A few things about the SelectDevice function
First we added a new parameter for the Device Type ( DeviceType.Video or DeviceType.Audio )
Second, we found out that with some cameras device ids randomly change , so the device "label" is more reliable to use for the device selection.
Thanks
StonePaleAle
@StonePaleAle
@avspeed @abelm688 Thank you both! It's working perfectly.
StonePaleAle
@StonePaleAle

@avspeed What is the secret to getting a signaling server running on heroku? I followed the instructions, and have it running :2019-02-26T23:52:12.797610+00:00 app[web.1]: AVSPEED RTC Signaling Server listening at 0.0.0.0:43867
Yet I can't connect to it. I can still connect to the provided test server process at https://rtc-signaling-service.herokuapp.com:443/

Is there something special I need to do on Heroku?
Thanks!

Team@AVSPEED
@avspeed
image.png
@StonePaleAle no secret, really .. our heroku instance of the signaling server is deployed directly from the github repo https://github.com/avspeed/RTCSignaling.io
Ultimately it does not matter which port you are listening on, you should connect to port :443
https://[yourherokuappurl]:443/