4.3Gateway

Gateway is the first entry in the Server tab. It describes the box that runs the project: its name, where it is, how clients reach it, what its KNX address is, and who may sign in to the apps. It has no Enabled switch.

#What it does

The values are saved in the project and go to the gateway when you deploy. The Configurator uses the Local IP Address as the address to deploy to. The gateway uses the KNX address for its KNX bridge, the latitude, longitude and timezone for the Solar Engine and prayer times, and the local IP address as the realm of its SIP server.

#Before you start

• Give the gateway a fixed IP address on the site network, for example with a reservation in the router. A changing address breaks deploys and the apps.
• Know the gateway's KNX individual address. Use one that is free on the installation.
• The project wizard already asks for most of these values. Come back here to change them later.

#Settings

The properties are shown as a table with a name on the left and the value on the right. The three small buttons above the table switch the view between Categorized (the default), Alphabetical and Declaration order. A click on a group heading collapses it. Edits are part of the project: they are saved by Save (or by Autosave, see Settings) and reach the gateway when you deploy.

#Gateway Properties

#Location (GPS)

If the project was made with the wizard, the country, city, latitude, longitude and timezone are already filled in from the city you picked.

#Network

#Cloud Connection Policy

When Local + Remote is selected, a note appears: Remote access requires two ports forwarded to this gateway on the site's router: 8889/TCP and 8189/UDP. Without both, remote viewers fall back to Cloud, if it is enabled, or cannot reach the camera away from the local network.

#Deploy token

The gateway only accepts projects from a Configurator that has its deploy token. Open the gateway console in a browser, go to the Cloud tab, find Deploy Pairing and click Copy deploy token. Paste the token into Deploy Token here. You do this once per gateway. Deploy uses the token automatically from then on, instead of asking for it each time. If the token on the gateway is regenerated, paste the new one. See Gateway console and logs.

#Time server

With Time Server enabled, the gateway writes its current date and time to the KNX bus once a minute, for other devices on the bus to follow. Enter the group addresses in the three rows that appear:

A row left empty is skipped. The KNX engine must be running, and the time is the project's local time (see the timezone note).

#App users

The Users row (under Access) lists the people and panels that may sign in to the apps. It shows Click to edit..., or the number of users. Click it to open the Users dialog. The users are part of the project and become active on the gateway when you deploy. On deploy, every user is given the role user. App users are not gateway administrators. The gateway console has its own administrator login.

The list is on the left, with Add User on top and a trash icon on each user. Click a user to edit it on the right. A new user is shown at once, ready for editing. The first user is created in the project wizard.

Click Save to leave the dialog. It checks that every user has a username and a password and that no username is used twice, and shows a message at the bottom if not. Close (or the X) leaves the dialog without checking. The edits you made are already in the project.

#SIP extensions

With the SIP Gateway enabled, the gateway creates an intercom account for every user that has an extension. For ring groups and door stations see Intercom and door stations. The accounts on the gateway's SIP server exist only while the SIP Gateway is enabled.

#Idle return

When Idle Return is on for the signed-in user, the app goes to the Return Page after Idle Seconds without use.

• The Return Page list shows the project's pages, grouped by panel.
• If the page is empty or has been deleted, the Veltnova client goes to the first page.
• In the Veltnova client, the countdown is paused while a call is ringing or in progress and starts again when the call ends.

#How it works on the gateway

• KNX address. On every deploy the gateway rebuilds its KNX bridge from this address and reserves the addresses after it for ETS tunnelling clients. If the field is empty or not a valid area.line.device address, the gateway uses 1.1.250 instead.
• Public / NAT IP. With a Remote policy the gateway also asks a public STUN server for its public address at start, after every deploy and at intervals, and keeps it in its own copy of the project.
• Local IP Address. Also used as the realm of the gateway's SIP server. The Configurator deploys to port 3127 unless you type address:port in the field.
• Time Server. The gateway writes the three group addresses once a minute, on the minute.

#Example

A villa in Dubai with remote access:

1. Open Server > Gateway. Set System Name Villa Marina and Location Dubai, United Arab Emirates.
2. Set Latitude 25.0657, Longitude 55.1713 and Timezone Asia/Dubai.
3. Set Local IP Address 192.168.1.20, KNX Individual Address 15.15.250 and Cloud Connection Policy Local + Remote.
4. Forward 8889/TCP and 8189/UDP on the router to the gateway, and type the router's public IP address in Public / NAT IP.
5. Paste the Deploy Token from the gateway console.
6. Deploy.

#Tips and common problems

• Deploy cannot reach the gateway: check Local IP Address. If it is empty the Configurator tries 192.168.1.15. See Common problems.
• Deploy says a deploy token is required: the token is missing or was regenerated. Paste the current one in Deploy Token.
• A user cannot sign in after being added: users exist on the gateway only after a deploy. Deploy again.
• The Users dialog will not close with Save: read the message at the bottom. A user without a username or a password, or two users with the same username, stops it.
• An app does not ring on an intercom call: check that the user has a SIP extension, that the SIP Gateway is enabled and that the project was deployed.
• Sun or prayer times are off by hours: check Latitude, Longitude and the timezone note above.
• The Solar Engine says no location is configured: Latitude and Longitude are empty or not numbers.
• Remote camera does not work from outside: both router ports in the note are needed, and the policy must contain Remote.

#See also

• Settings
• KNX
• Solar Engine
• SIP Gateway
• Deploying to a gateway
• Connecting the apps