so you have a Ribbon SWe Lite on Azure, maybe without any VPN with your Corporate Network, and you wonder how to you can use Ribbon LX Syslog to troubleshoot it.
You have installed a Ribbon SWe Lite Virtual SBC on Azure, to use it with Teams Direct Routing and a SIP Trunk to a PSTN Carrier.
You have to troubleshoot an issue on the SBC, sending logs to a Ribbon LX Syslog server on your PC or on a server, but there is no VPN to Azure at all.
The scenario and the problem is very simple and I suppose will be more and more common with the spread of Virtual SBCs on Azure.
In this scenario you can use ngrok to open a TCP tunnel to reach your PC, without network changes and in few minutes.
Let’s see how.
Ribbon LX Syslog Setup
First of all, follow this guide to download and install LX Syslog from Ribbon Support Site.
Once installed, run it.
- Click on Syslog Server
- set Transport to TCP
- Click Start Listening
To use ngrok you have to go to ngrok.com and create a free account.
Follow these easy steps from 1 to 3
Now you are ready to run ngrok to establish the TCP Tunnel
ngrok.exe tcp <Syslog Listen IP>:514
You will see a window like this one, take note of the random port, we will use it later
Forwarding tcp://0.tcp.ngrok.io:<Random Port>
Leave running ngrok, do not close it.
Azure NSG inbound security rule
Open Azure Portal and go to your SWe Lite Resource Group.
Select the Network Security Group and add a new inbound security rule like the example below.
If you have concern about security holes, this rule is not a problem because it allow only Syslogs TPC traffic acknowledge, there isn't any 514 listening port on the SBC.
SWe Lite Log
Open your Ribbon SWe Lite web interface.
Go to Settings -> Logging Configuration -> Remote Log Servers -> + to create a new Remote Log Destination
Global Log Level: Informational Log Destination: <ngrok forwarding URL> (0.tcp.ngrok.io in this example) Port: <ngrok Random Port> (take it from previosu steps) Protocol: TCP
Go to Subsystems -> Apply Log Profiles to load a predefined set of logs. Choose the profile that best suit your need, Audio – SIP is one of the most used of course.
Be careful to choose Remote Log: 0.tcp.ngrok.io as Log Destination.
Click OK to save and start to receive your precious logs!
As always, I hope some of you will find these information useful.