Could not connect to Restcomm IVR? - ivr

I have simple restcomm IVR tree at http://54.249.98.150:8080/restcomm-rvd. Registered a number as:93878460 at http://54.249.98.150:8080/restcomm-management/#/numbers/incoming and assigned my version of RVD to it. I have downloaded Linphone and tried to connect as sip:93878460#54.249.98.150:5080 but could not hear anything. However I saw some logs though at http://54.249.98.150:8080/restcomm-management/#/logs/calls. Could you please help connecting this tree for navigating the tree too. This is dockerized in AMI where necessary ports are open. -thanks.

Related

How to wait for network connectivity before starting a service in Windows?

I'm attempting to use Suricata IDS for monitoring the network events in a specific interface.
I have been able to install the service and I am able to execute it.
Everything seems to be working fine, except for the fact that the service might fail to start at computer startup.
The service in fact necessarily needs to have the connection ready and available (assigned IP, etc.) when Windows starts it.
So, the service is working correctly at startup ONLY when the network is up and running for that interface.
If for some reason the network connection comes up later than usual, the service fails to start, and Windows seems to not try again to start it.
I've been looking at other stackoverflow questions in order to correctly set the dependencies for the network connection and for what I'm trying to do, but they seem to not be working.
So, what are the correct dependencies to add to my service for instructing Windows to wait for the network connection to be up and running (IP already assigned, DNS already set, etc.) before starting it?
If you have an alternative idea on how to solve the problem you're welcome to post a reply.
Any suggestion is appreciated.

IoT management page with P2P connection

I'm really looking for advice and a starting point more than anything. So I'll try my best to explain my end goals and the challenge. I want to set up a local WiFi connection (P2P) between a Rpi3 (or any embedded system really, running linux) and a laptop. The Pi should be the server and laptop the client. The raspberry PI is going to be reading samples over USB from an SDR. I want the laptop to be able to connect to the network the pi throws up, and be able open a browser and view the results. I'm guessing what i need to read up on is ports/sockets and web programming in general. The cheepy IoT sensors and light bulbs seem to be able to do this (opening network and forwarding data) relatively easily but i cannot find any information online to aid in my quest. All the Best and thanks in advance.
Since the embedded system will be running Linux, you can do something along the following lines:
setup the wifi as an Access Point (example). Also setup DHCP Server (example), so the wifi will assign an IP address to connecting laptop.
Install a webserver (e.g. Apache).
Create the webpage/ web application you need to "serve" the data. Install this into Apache.
Ask follow-up questions if you like.

Setting Up Restcomm on Ubuntu 14.04 (EC2)

I am completely new to Restcomm and currently experimenting with the application.
I want to setup a restcomm apps on my EC2 instance. I am aware that i can easily deploy Restcomm via the AWS Marketplace, however it only allows me to deploy on N.Virgina (whereas i want to deploy it on Singapore region)
After following the instruction described on this page Installing from Github
I get the following message when i run
./start-restcomm.sh
When i try to access it via MY_PUBLIC_IP:8080/olympus i always get "Unable to Connect" message.
My restcomm.conf is as follows:
If i have to guess, i think restcomm is currently listening to my Private IP instead of my Public IP. I am really new at this and hoping that someone can help with this.
This is my security group configuration, in case you need to know:
And ifconfig spits out this:
ps: I think someone really need to create a new tag "restcomm" for this kind of question.
It seems that you are missing 5082 port in the security group configuration for SIP over Websockets. Can you connect to restcomm-management (Admin UI) correctly?

standalone dlux communication with opendaylight controller

We have cloned opendaylight controller and dlux into a machine
Did "mvn clean install" in opendaylight controller project and started it. By default odl-restconf-all bundle is not installed, as it is required, we installed it (it internally installed many dependent features which we could see using the command "feature list -i")
netstat -anp | grep ":8181"
this command confirmed us that the port is been consumed by the controller
Brought up the dlux server using the command "grunt live", it is listening on port number 9000
we also ensured that dlux-web/config/developement.json and production.json are pointing to the proper controller IP (as controller is running in a different OSGI container but same machine)
Launched the browser using the below url
http://localhost:9000/dlux/index.html
on the page "Cannot GET /dlux/index.html"
http://localhost:9000
page is shown blank
we have no idea what is missed in those to establish communication between them, can somebody let us know how to debug this issue?
or something from the dlux project should be pasted into the controller project?
After debugging the issue, found that app.module.js has some required variables commented, after enabling them, it started working.
no idea, why they are commented in that script
if someone has an idea about it, please update

Selenium Grid Hub Operation timed out

I am trying to run Behat Tests on the Windows 7 VM node installed using my Mountain Lion Mac computer as hub.
I am using the latest seleniun (2.39.0)
I run the following command on the node VM
java -jar selenium-server-standalone-2.39.0.jar -role node -hub http://10.0.2.2:4444/grid/register -browser "browserName=internet explorer,version=8,maxinstances=1" -Dwebdriver.ie.driver="D:\tools\IEDriverServer.exe"
This sends the request to the hub machine, and it "seems" as though the hub has received this, this is because when I access localhost:4444/grid/console on the hub machine it shows the registered node (see screenshot below)
But the error comes when the hub tries to send a request to the node and it can't because the connection is refused. But I have disabled the windows firewall so this connection should go through right?
Any help would be appreciated!
So, I figured out my problem and it was nothing to do with the commands posted here. I did not give enough network permissions to my VM to allow the connection. Easiest solution was to make the VM act as a seperate computer on the network, which solved all the problems :).

Resources