Keba KeContact M20 Manual De Configuración página 291

M20
●
●
●
●
Ports for communication via OCPP
For communication with an OCPP backend, the following ports must be en-
abled in the network:
Custom
(1025 -
65535)
Custom
Supported messages
The following table provides an overview of the supported messages.
Authorize
BootNotification
ChangeAvailability
ChangeConfiguration
ClearCache
DataTransfer
GetConfiguration
Heartbeat
MeterValues
RemoteStartTransaction
RemoteStopTransaction
Configuration manual V1.01
© KEBA 2022
Since the OCPP backend is usually not in the same network, the charg-
ing station must be assigned a "public IP address" which is routed to the
internal IP address (NAT).
The firewall must be configured so that communication between the
charging station and the OCPP backend is possible.
For a connection via VPN, the IP address of the VPN must be specified
in the configuration (web interface) for the downlink.
In the case of a mobile communications connection, it may be necessary
for the required ports to be activated by the cellular service provider.
Port Protocol
Can be reached externally
TCP
(incoming)
Access to external (outgo-
TCP
ing)
123 UDP Incoming and outgoing
Message
Definition
OCPP Charge Point Service: This
service is related to the OCPP
backend.
●
●
Port at which the OCPP backend
can be reached.
Port for the time server of the
charging station.
OCPP 1.5
Functions
Description
The port can be freely selected
or it is specified by the OCPP
backend. However, the port
may only be located in the
range from 1025 to 65535.
The selected port must be
configured on the charging
station.
OCPP 1.6
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
291