I am using this repo:
https://github.com/opentok/opentok-nexmo-sip/tree/master/Dial-In-Conference
Bought nexmo virtual number and created new tokbox app.Set up all credentials. Changed only voicename and text in server.js. For local testing purposes I am using tunnel through ngrok, so in nexmo dashboard I've put my actual ngrok url for endpoints with ending eg. /nexmo-answer and /nexmo-events.
When I start app and go to new room eg. room/2 I can see, my app is working, camera and microphone works perfectly also my coworker can go to my link through tunnel and we can talk.
The problem is that nobody can dial into our conference. Anyone calling can hear welcome message and pin prompt, after inputting correct pin, the phone apparently connects (doesn't disconnect automatically) but we can't hear or send any sound. Any advice?
I managed to solve my error. App needs to dial out into nexmo's virtual number's room.
I'm previewing the MobileFirst app (Cordova) on both browser and iOS Emulator but there doesn't seem to be any response when I call WLAuthorizationManager.obtainAccessToken().
I've tried to allow cross origin request but still face the same issue. Does anyone have any suggestions for what I should look at?
I had a similar issue on the iOS emulator. I even used Wireshark to see what was happening and the app never fired the authorisation request.
In the end I found that if you're running XCode 8.x, you have to enable keychain sharing by selecting the project -> Capabilities -> Keychain Sharing, and setting it to On.
After that I had to register the app again and all worked fine.
Make sure when you register or push the app and you're prompted for the version number, that you enter x.x.x instead of x.x - otherwise the server will not recognise the app.
Another thing to double check is the mfp:server runtime and url values in the config.xml file, if your pc's ip address has changed then the url value could be incorrect.
Okay, I'm developing a web app using Dart, I'm making encrypter - which works fine at home. But, I'm in college and I need to run my Dart app from a USB stick. When I run my Dart app, the version of Chrome that comes with Dart opens but nothing loads. I have the "stop loading this page" button showing, which tells me that it is trying to load something, but I've left it for half an hour and nothing happens. I think it's because I cannot give Dart any Firewall privileges, because I'm not an admin, the VM that Dart uses won't launch. Has anybody got any tips of how to get around this?
I disconnected my notebook from the network and Darteditor runs just fine. I can start web pages without any problem.
Probably Darteditor tries to download pub dependencies which won't work without a network connection.
If you can open a public website like google.com in your browser then it's probably not a firewall limitation. AFAIK Dart uses only HTTP port 80 which is usually open.
If your HTTP connection goes over a proxy that might not work - that is a common problem with Dart.
I am in the means of setting up of android web driver and followed the same steps as mentioned in the url : http://code.google.com/p/selenium/wiki/AndroidDriver
1) Downloaded the android SDK for windows and unpacked and placed in the path of selenium repository
2) Set up the emulator and created the new AVD ( android virtual device )
3)Installed the webdriver apk 4)port forwarding in order to forward traffic from the host machine to the emulator.
In a terminal type:
$./adb -s forward tcp:8085 tcp:8085(since 8080 is occupied I'm using 8085)
5) This will make the android server available at //localhost:8085/wd/hub from my system.
But when i went to localhost:8085/wd/hub it displayed could not connect to www.localhost.com:8085. May I know why? Kindly help me to fix this.
When you say, "But when I went to" do you mean you visit the url in your browser? It sounds like your browser does not know what to do with the url and tries to be smart for you and assume you mean www.localhost.com:8085. If so, just add a protocol to your request. In stead of localhost:8085/wd/hub use http://localhost:8085/wd/hub.
Typically I develop my websites on trunk, then merge changes to a testing branch where they are put on a 'beta' website, and then finally they are merged onto a live branch and put onto the live website.
With a Facebook application things are a bit tricky. As you can't view a Facebook application through a normal web browser (it has to go through the Facebook servers) you can't easily give each developer their own version of the website to work with and test.
I have not come across anything about the best way to develop and test a Facebook application while continuing to have a stable live website that users can use. My question is this, what is the best practice for organising the development and testing of a Facebook application?
Try updating your hosts file (for windows users # c:\windows\System32\Drivers\etc\hosts) with an entry that will route all requests from your live domain back to your machine.
So 127.0.0.1 mywebappthatusesfacebook.com.
Then make sure that your app is running at the root of your webserver. # http://localhost/ Then goto mywebappthatusesfacebook.com in your browser and it should redirect right back to your local machine. Facebook won't know the difference. Hope this helps
The way I and my partner did it was we each made our own private Facebook applications, that pointed to our IP address where we worked on it. Since we worked in the same place, we each picked a different port, and had our router forward that port to our local IP address. It was kinda slow to refresh a page, but it worked very nicely.
You'll have to add both trunk and test versions as different applications and test them using test accounts. You may also use a single application and switch its target URL between cycles.
Testing FB apps is still a rather primitive process.
I generally setup a test application that is a complete copy of the production settings inside the FB development environment that uses an SSH tunnel to point to my development server. You can setup as many applications as you need inside FB - I generally have a development application, a staging app and production. Staging and Production are both on "live" servers rather than an SSH tunnel.
In your application you then use whatever language/framework/server tools are at your disposal to switch the FB configuration based on the server. In Rails, the Facebooker gem actually has built in support for different FB configurations.
Once all of that is done, testing is, unfortunately, still a matter of running the app within FB itself. I use Selenium to automate as much of this as possible.
Best way to do this:
Remove 'App Domain' from 'Basic Info'
Set website's 'Site URL' to : "http://localhost/" .
That simple.
(This only apply if you don't have a live system running in parallel to the test env. In that case get yourself another key.)
We have it setup much like Toby. A series of config files for each developer, that has the Facebook APP Id info (a different app for each developer), separate pages where the app is hosted, and git ignores the config files. We're LAMP with Code Igniter, and it's similar to Rails in that we can set the environment in 1 file, which points to the config with the Facebook constants.
Branching out into Selenium, using unit tests for model-testing.
For local testing we simply use a different app than for the server. In our case the Canvas-URL is set to localhost.local:8000.
You only have to make sure that when you use facebook connect that you type in localhost.local into the address field of the browser and not just localhost.
For testing a canvas or tab app it is faster if you use the 'open iframe in new tab' command of Firefox. This way the session and cookies from Facebook are preserved.
Another solution is NGROK
https://ngrok.com/
It opens a public tunnel to your local app
Example on my rails application by simply typing
./ngrok 3000
I get
http://630066fe.ngrok.com -> 127.0.0.1:3000