Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
app-notes:hayes-modem-at-simulator [2018/05/08 17:04] cakir [AT Modem Emulator] |
app-notes:hayes-modem-at-simulator [2021/11/29 12:32] (current) schmitt |
||
|---|---|---|---|
| Line 17: | Line 17: | ||
| The Modem Emulator will only replace the AT Command Set on the serial side. The Communication between the NB1600 and another Endpoint will be done as a transparent tcp Connection. | The Modem Emulator will only replace the AT Command Set on the serial side. The Communication between the NB1600 and another Endpoint will be done as a transparent tcp Connection. | ||
| - | This way you can provide the old legacy functionality over modern IP Connections. Depending on your infrastracture you could secure your communication with a VPN Layer or work straight with public IP adresses. | + | This way you can provide the old legacy functionality over modern IP Connections. Depending on your infrastructure you could secure your communication with a VPN Layer or work straight with public IP addresses. |
| - | ===== Adressing ===== | + | ===== Addressing ===== |
| An important Part on the Dial-In/Dial-Out Installations is the addressing of the Endpoints. | An important Part on the Dial-In/Dial-Out Installations is the addressing of the Endpoints. | ||
| - | The old addressing concept were based on phone numbers. With the Modem Emulator the Adresses will switch on an ip-address/port based addressing. | + | The old addressing concept were based on phone numbers. With the Modem Emulator the Addresses will switch on an ip-address/port based addressing. |
| - | But for backward compatibiliy we integrated a Phonebook Feature, so that you can keep the old phone-number based addresseing and we woll resolv them into ip-address/ports. | + | But for backward compatibility we integrated a Phonebook Feature, so that you can keep the old phone-number based addressing and we will resolve them into ip-address/ports. |
| ===== Configuration ===== | ===== Configuration ===== | ||
| Line 31: | Line 31: | ||
| After you applied the mode "modem emulator" you will find the detailed options. | After you applied the mode "modem emulator" you will find the detailed options. | ||
| - | {{ :app-notes:modememu0.png?nolink |}} | + | {{ :app-notes:modemu0.png?nolink |}} |
| {{ :app-notes:modememu1.png?nolink |}} | {{ :app-notes:modememu1.png?nolink |}} | ||
| Line 41: | Line 41: | ||
| Please set the Baud Rate accordingly to you attached device. Also set the "Hardware flow control to your needs. Any further configuration of the serial interface can be done via the hayes command set. | Please set the Baud Rate accordingly to you attached device. Also set the "Hardware flow control to your needs. Any further configuration of the serial interface can be done via the hayes command set. | ||
| - | Any incoming connection will be received on the TelnetPort configured. This Port need also to be accessible on the IP Adress to you like to reach the Modem Emulator from the Outside. Keep this in mind for any Firewall configurations. Despite the Name "Telnet Port" it has nothing to do with the Telnet server at services->telnet, it's a plain tcp port listeing on incoming connections. | + | Any incoming connection will be received on the TelnetPort configured. This Port need also to be accessible on the IP Address to you like to reach the Modem Emulator from the Outside. Keep this in mind for any Firewall configurations. Despite the Name "Telnet Port" it has nothing to do with the Telnet server at services->telnet, it's a plain tcp port listening on incoming connections. |
| - | The Phonebook section of the configuration will keep the aliases of any Phonenumbers so that you don't need to reconfigure you device and can use the old adressing scheme. | + | The Phonebook section of the configuration will keep the aliases of any Phonenumbers so that you don't need to reconfigure you device and can use the old addressing scheme. |
| The new dial command would be: | The new dial command would be: | ||
| Line 66: | Line 66: | ||
| * Connect your Device to the Serial Interface | * Connect your Device to the Serial Interface | ||
| - | If you are working via the OpenVPN Server you will have following Adressing: | + | If you are working via the OpenVPN Server you will have following Addressing: |
| * OpenVPN Server: **10.8.0.1** | * OpenVPN Server: **10.8.0.1** | ||
| Line 73: | Line 73: | ||
| {{ :app-notes:openvpn_status.png?nolink |}} | {{ :app-notes:openvpn_status.png?nolink |}} | ||
| - | Based on this Adressing you can call the the device in the field as follows: | + | Based on this Addressing you can call the the device in the field as follows: |
| ==== Full Legacy Mode ==== | ==== Full Legacy Mode ==== | ||
| Line 83: | Line 83: | ||
| ==== Field Legacy Mode ==== | ==== Field Legacy Mode ==== | ||
| - | In Case you want to have the connection from a central point to the devices in the fields there is no need to integrade the model emulator on the server side. | + | In Case you want to have the connection from a central point to the devices in the fields there is no need to integrate the model emulator on the server side. |
| - | If you can skip the AT Commands on the Server side you can just initiate a tcp connection to the tcp Port of the field devices. It initiate the same procedure as an incomming call and will have the same output on the serial interface as in the full legacy Mode. | + | If you can skip the AT Commands on the Server side you can just initiate a tcp connection to the tcp Port of the field devices. It initiate the same procedure as an incoming call and will have the same output on the serial interface as in the full legacy Mode. |
| Line 117: | Line 117: | ||
| - | until the incoming Connection will be acceptet with an ATA and confirmed with a CONNECT 115200 | + | until the incoming Connection will be accepted with an ATA and confirmed with a CONNECT 115200 |