Setting Up Restcomm on Ubuntu 14.04 (EC2) - amazon-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?

Related

How to login to Jenkins from any network

I’m an absolute beginner when it comes to setting up a Jenkins environment but I have just installed Jenkins on a MAC v10.15.5 using home-brew and would like the capability to:
Open a web browser
Login to Jenkins from any machine on any network
Trigger a job.
I’m able to do this using a different machine on the same network but unable to do this using a machine on a different network. I changed the "httpListenAddress" value within the jenkins-lts.plist file to 0.0.0.0 to allow the web interface to be accessible from anywhere as mentioned at https://www.macminivault.com/installing-jenkins-on-macos/ but apart from that I’m not sure where to go from here.
I’ve heard about Apache Tomcat but not sure if it's necessary for what I need to do. If anyone can provide instructions / safe approaches about how to login to the Jenkins environment on my MAC from any network that would be appreciated.
To get jenkins web interface use $JENKINS_HOST_IP:8080 (by default jenkins uses port 8080) and then make first-run-configure.
Login to Jenkins from any machine on any network - it depends on network topology, what is used in your organisation. So, to reach jenkins host from any network where should be allowed traffic from/into network where jenkins host is placed.
Trigger a job - where are a lot of triggers you can use. Take a look at official documentation here

IKEV2 VPN Macbook/OSX add static route, Azure Point to Site connectivity

I am unable to access all of the resources in my peered network in Azure when I do a VPN from macbook (VPN type IKEV2) have tried add routes didn't worked.
In windows to get this working was to edit the routes.txt file and add static routes in.
How will I go adding the same in Mac.
System Details
Mac osx - 10.13.2
Looking for
Ability to add/define static routes for my peered virtual network for IKEV2 type VPN in mac.
We found a bug in the P2S VPN gateway that prevent this from working out of the box. The fix is currently being rolled out in Azure. You can wait until next week when we complete the rollout, or open a Service Request from Azure Portal and our support engineer can apply the fix directly to your Azure Gateway. Sorry for the issue you are running into.
Thanks,
Yushun [MSFT]

WSO2 ESB proxy service on Windows

i'm using the WSO2 ESB to integrate several services on the Windows virtual machine.
I used the simple proxy to map the services deployed on it. But the problem is what i can't access them from outside it nevetheless the port 8280 where services are deployed is open for internet, but i can see only blank page instead. What could be wrong?
Another question is i was trying to map the WSO2 ESB management console itself to be availbe from outside the machine using simple proxy, and i'm failed, it loads me the this is what i see on trying the service.
Could you please give me a hint on how to resolve this issue? is it possible to share the esb mgmt console using the ESB itself?
Thanks a lot in advance,
Do u have proxy in the middle? It looks like on screenshot webpage missing all pictures, meanwhile css was loaded successfully.
Another question which kind of virtual machine u use? For example in virtualbox by default virtual machine behind NAT.
I wasn't able to connect to server on virtual machine from host only opposite way server on host available in virtual machine.
To make server in virtual machine available on host need to configure network as bridge.
Not sure if it helps, but I think I had a similar problem in our corporate network after I applied all the security patches (poodle,Diffie-Hellman etc.). I had to configure the addresses in catalina.xml (if i remember right) that are/under which allowed to access the admin console. Cannot tell you more details because I'm on holiday :-)
Maybe it's worth to give it a try.
Another example from real life. HTTP Response from external resource was application/json, status of response 200 OK. ESB configured to use
<messageFormatter contentType="application/json"
class="org.apache.synapse.commons.json.JsonStreamFormatter"/>
but content was simple text/plain.
During parsing body of http response exception was thrown and just silently was written to log, without any fault message processing. Just empty response to client.
To clarify that services reachable, there is echo service by default on server, which respond content equal to request. Try to use it.
was trying to map the WSO2 ESB management console itself to be availbe
from outside the machine using simple proxy
By default the management console tries to enforce the port 9443 for dynamic links (JSP) pages. That's why you see only part of the pages and you shouldn't be able to log on.
what you can do is edit the repository/conf/tomcat/catalina-server.xml and to the Connector running the port 9443 you can add an attribute proxyPort="443", the carbon console will be happy to run on 443.
For the services, my educated guess would be on the firewall / network rules, however without other information I cannot answer (or - they are working, just you may not try to access them by simple browser request)

Could not connect to Restcomm 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.

Accessing WSO2 ESB, GREG and AS from external machine

I worked over the last weeks with wso2 products using some of the tutorials which were posted on the wso2 site.
Unfortunately I only found tutorials, where all the products run on the same machine.
What do I have to do, if I want to run the products on different machines. I want a configuration where:
- ESB runs on machine 1
- AS and GREG run onmachine 2
- Proxy-services in the ESB or a web servcie in AS are invoked from machine 3
I run these examples on some macs, I think the main problem are the ports which are used. Can somebody help me with the configuration?
Can you elaborate your configurarion problem?
With this configuration you have to be sure that from one server you can ping the another servers and that in each server you have the ports 9443 and 9763 (by default) open to the network. this is the only requirement you need.
What you are trying is nothing new. In a typical production deployment each of the servers run in their own physical/virtual machines.
when you are calling a service, you calling an endpoint uniquely identified by IP address:port/contextPath
If the setup is in the same local machine the IP address would be 'localhost'.
First you have to learn the tcp/ip basics, the question is not related to wso2 servers IMHO.

Resources