How to dial-in conference in nexmo? - tokbox

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.

Related

Can't use phone ase controller

I want to test my airconsole game on a smartphone before publishing. The problem is, I can't connect it to the simulator.
If i try to connect (Chrome on Android) it says connecting, after a few seconds it shows the enter code screen but no input is possible. After about 30 seconds I get the message download the app for next time. (Screenshots attached)
Do you know where the problem is?
My files are hosted on a webserver, accessible from everywhere.
Kind regards
Make sure your screen.html and controller.html are accessible from all devices.
Let's assume you are running your local web server on http://192.168.0.2:8080/
Try to access http://192.168.0.2:8080/screen.html and http://192.168.0.2:8080/controller.html using a normal web browser on the device that doesn't work. It should display the screen/controller html.
If you can't access http://192.168.0.2:8080/controller.html from your phone, but from your computer, make sure you are in the same network and that your router does not have "Client Isolation" activated.
If you are testing with real smartphones, make sure you do not use http://localhost/ or http://127.0.0.1/, because localhost is not your computer on the phone but the phone itself!
If you are still unable to connect your phone, you can use the ngrok tool to forward your local url. See our Ngrok Unity Guide for how to do this in the Unity Engine: https://developers.airconsole.com/#!/guides/unity-ngrok

Kurento: Kurento-room without webcam

I've seen that kurento-room isn't able of managing a user that enters only with microphone(no webcam).
The user actually appears in the room, with a black screen in the place where the webcam is normally located, but no audio is received from him either.
Why can this be happening?
That's an error in the connection of WebRTC endpoints. The thing is that the endpoint only negotiates audio, but the connection was made with audio and video profiles, and the media server committed seppuku. It should be fixed by now, providing the right media profiles in the connect method.

How can I register my WP device in dev account?

I have trouble with registration WP8.1 device to developer account. My account is active. Device early was active, but I reset phone (Nokia 620) and after that Developer tools don't active this phone.
In list (in dev acc) this phone was remove.
after I press "register" show this window:
and that's all. Second window close after few seconds and register process don't finish. Please help :)
Make sure your computer have internet connection. I had similar issue when network proxy was configured incorrectly .
Also try after clearing internet explorer cached content (history,password,cookies etc.)

My app with GCM works for some but not for others

I've written an Android chat progam that makes use of Google Cloud Messaging.
It works. People are able to chat.
However, some people are not because the app does not register with GCM from their device.
This could be due to:
The user not having a Google account on their device.
A firewall is preventing them from accessing ports: 5228, 5229, and 5230
It seems impossible to diagnose from my end since it works for some people but not others and all my devices work.
I'm looking for other ways to diagnose this problem. Any ideas will be appreciated.
I have added prompts to give the user a clue as to the problem, based on what GCMIntentService onError returns.

Wireless Authentication Page iOS app

I'm not really sure how to word this exactly, so hopefully someone can make sense of it. I've been working on an iPad app that syncs files from a server to your iPad and lets you build presentations with the various files. The corporation I'm working with on this app has a wireless network that requires you to re-authenticate every hour. So every hour instead of getting the expected JSON api response, any HTTP request pulls down the page needed to reauth with the wireless network. I was wondering is there is a specific HTTP response code related to getting sent that page or a "best-practice" way of testing for that page as opposed to JSON.
Granted I could just test to see if the response is HTML, but that doesn't account for other redirect responses that I haven't found yet. I could just test part of the HTML to see if it matches a predetermined portion of the html, but I'm an outside contractor. I can't guarantee they won't change the markup or verbiage of the page after I've made my deliverable.
So does anyone out in the ether know a "best practices" methodology for testing if the app needs to reauth before syncing?
I noticed that on Mac OS X and maybe even iOS, when you connect to a new Wi-Fi network, it will try to contact www.apple.com. This is being done to check if the internet connectivity is available. If it's not available, the Captive Network Assistant will pop-up, showing you the authentication page, or sometimes when I'm in Starbucks, an advertisement.
Following your question, since Apple themselves is doing it this way, I think you could check for HTTP response code, look for something in the HTML markup (slightly discouraged though) or trying to connect to a known server (Reachability).
For a corporation practicing well-documented projects, I am quite sure they won't be changing things without making sure that your app, once deployed will continue to work.