This document will go over how to configure your SonicWALL for use with the SingleComm platform.
1. Address object configuration:
You'll want to configure an address object for the SingleComm domain ($yourcompanyname.singlecomm.com).
The domain name will be configured once you get onboarded as a client with us.
To configure the domain name object, go to the "Network" tab and then the "Address object" subheading.
You'll see a list of default objects and object groups (will go through later).
Scroll down and hit "Add" under the Address objects table.
Then give the object a friendly name and then set it to the WAN zone.
After that, enter the FQDN that you will be using to connect to SingleComm and then hit "OK".
NOTE: Repeat this for all the SingleComm FQDN's that you'll be connecting to.
There is a table at the bottom of this page you can use as a reference.
2. Address object group configuration:
SonicWALL's can add multiple singular address objects to an overarching group.
That way you don't have to reference all the specific objects in your firewall rules..just the group.
To do this, scroll up on the address object page and hit "Add Group".
This will take you to the following window:
Give your group a name and then choose what objects you want in the group from the list on the left (this will be the names of the objects you created in step 1.
Hit "OK" and confirm the group shows up in that table.
3. Service object/group configuration:
Now you'll need to configure the traffic that you want to allow from/to those objects.
Head over to the "Services" section on the firewall:
This follows the same pattern as the object creation (create a singular object for each service, add those objects to an overarching group)...the services that you'll need to allow are in the table at the bottom of this document.
Above shows how to add the individual services to the service group. Just add all the services you configured to this group and you're good to go.
Now we can configure the firewall rules to allow the traffic inbound/outbound to our infrastructure.
4. Firewall rules configuration:
You'll want to create 2 firewall rules. One will be for inbound traffic and one will be for outbound traffic.
The above shows the inbound rule. This says "From the internet to me, allow any connection that's on the SingleComm service group.
You'll basically copy this rule and change the WAN > LAN portion to LAN > WAN for outbound connections.
Let us know if you need help with this part and we can walk you through it.
That's it! You're now ready to make calls on our platform
The table below can be used as a reference to all the ports/FQDN's that you'll need to create rules/objects for.
Usage | Port | Protocol | DNS |
Web (ACD) | 443 | TCP (HTTPs) | CUSNAME.singlecomm.com |
Web (Scripter) | 443 | TCP (HTTPs) | CUSNAME.singlecomm.net |
Web (Scripter) | 443 | TCP (websocket and HTTPs) | CUSNAME.sngl.cm |
Main signalling | 1776 | TCP (websocket) | CUSNAME.singlecomm.com |
Main Signalling Broadcaster | 1777 | TCP (websocket) | CUSNAME.singlecomm.com |
Agent Signalling Server | 1778 | TCP (websocket) | CUSNAME.singlecomm.com |
Agent Signalling Broadcaster | 1779 | TCP (websocket) | CUSNAME.singlecomm.com |
Supervisor Signalling Broadcaster | 1780 | TCP (websocket) | CUSNAME.singlecomm.com |
Stats Signalling Server | 1781 | TCP (websocket) | CUSNAME.singlecomm.com |
Chat Signalling Server | 1782 | TCP (websocket) | CUSNAME.singlecomm.com |
Chat Transport | 1783 | TCP (websocket) | CUSNAME.singlecomm.com |
Stat signalling | 1784 | TCP (websocket) | CUSNAME.singlecomm.com |
Scrub Manager Queue | 1785 | TCP (websocket) | CUSNAME.singlecomm.com |
OBTM Manager | 1786 | TCP (websocket) | CUSNAME.singlecomm.com |
Event Dispatcher | 1787 | TCP (websocket) | CUSNAME.singlecomm.com |
General Purpose DSS Server | 1788 | TCP (websocket) | CUSNAME.singlecomm.com |
Traffic Control DSS Server | 1789 | TCP (websocket) | CUSNAME.singlecomm.com |
STUN Server (Main LB) | 19302 | TCP/UDP (HTTPs) | stun.l.google.com |
STUN Server | 19302 | TCP/UDP (HTTPs) | stun1.l.google.com |
STUN Server | 19302 | TCP/UDP (HTTPs) | stun2.l.google.com |
STUN Server | 19302 | TCP/UDP (HTTPs) | stun3.l.google.com |
STUN Server | 19302 | TCP/UDP (HTTPs) | stun4.l.google.com |
Phone server | 5067 | TCP (SIP) |
CUSNAME-fs01.singlecomm.com CUSNAME-fs02.singlecomm.com Contact SingleComm for a full list of your phone servers. |
Phone Server | 16384 - 32768 | UDP (WS) |
CUSNAME-fs01.singlecomm.com CUSNAME-fs02.singlecomm.com Contact SingleComm for a full list of your phone servers. |
Contact SingleComm for a full list of your phone servers.
Comments
1 comment
Nike Air Max
Ugg
Supreme Clothing
Birkenstock
Under Armour Outlet
Pandora Charms
Yeezy Supply
North Face
Champion T Shirt
North Face Outlet
Ugg UK
Goyard Wallet
Bottega Veneta Wallet
Valentino Sandals
Giuseppe Zanotti
Off White Shoes
Longchamp Tote
Fjallraven Backpack
Adidas Yeezy
Timberland Sale
Off White Hoodie
Brooks Tennis Shoes
Pandora
Prada Glasses
Uggs For Men
Polo Ralph Lauren
Fjallraven UK
Hydro Flask 40 OZ
Moncler Jackets
Ugg Canada
Skechers UK
Moncler Sale
Kate Spade
Hydro Flask 40 OZ
Hydro Flask Sale
Moncler T Shirt
Ugg Slippers
Birkenstock Outlet
Skechers Boots
Nike Outlet
Hydro Flask Lids
Pandora Charms
Supreme Hoodie
Under Armour UK
Asics Tiger
Fjallraven Backpack
North Face Jacket
Saucony Shoes
YSL Bags
Mont Blanc Fountain Pen
MCM
Fila Sneakers
Calvin Klein Dresses
Yeezy Trainers
Michael Kors Outlet
Fitflop Sale
Jordan Retro 11
Nike Trainers
Ultra Boost
Skechers Sandals
Fjallraven Backpack
Hydro Flask Sale
Balenciaga Trainers
Off White
North Face Outlet
North Face Jacket
Nike
Valentino Shoes
Jordan Retro 11
Birkenstock UK
Golden Goose Sale
Balenciaga Shoes
Off White Hoodie
Coach
Pandora Bracelet
Vans Old Skool
Supreme
Mizuno
Burberry Scarf
Hydro Flask
Yeezy Static
Timberland Boots Men
Birkenstock
Valentino Shoes
Saucony
Golden Goose
Timberland Shoes
Moncler
Karen Millen Outlet
North Face Canada
Nike Shoes
Skechers Outlet
Ralph Lauren Com
Brooks
Golden Goose Sneakers
Please sign in to leave a comment.