Guest access to the GSM barrier: call, link and revoke rights
If the barrier is already opened by a call from an authorized number, guest access can be organized through the list of its controller or through an additional GSM gateway. In the second option, the controller receives calls from the gateway, and the rights of the guests are checked before dialing. The choice depends on who manages the property, how often users change, and what login methods they need.
For the administrator of a parking lot, hotel or warehouse, the task is usually broader than one opening: grant access to a specific person, explain the method of entry, then revoke the right and deal with the unsuccessful request. Below is a selection and testing diagram for an existing GSM barrier. This is not a guide to bypassing its allowed list: the participation of the owner or administrator of the equipment is required.
First find out how the installed controller works
Collect the object's passport: the GSM controller model, its SIM card number, how to change allowed numbers and the administrator's contact. Clarify whether the calling number should be determined by how the device terminates the call and what action triggers the call back. These conditions are checked according to the instructions and on an agreed test.
The capabilities vary markedly even within the same manufacturer's line. For example, IPRo describes models with different communication channels and control methods, including call and application. Therefore, having a SIM card does not prove support for guest links, the cloud panel, or the mode of operation you want.
Before ordering, it is useful to answer five questions:
- Does the barrier open with a regular voice call from an authorized number?
- Who can add and remove a number in the controller?
- Do regular users, occasional guests, or both need access?
- Is there a person at the site who will help in case of communication failure?
- Do you only need to send a command or also confirm the boom position and travel?
The last question has implications for architecture. A successful outgoing call and the actual passage are different events. Monitoring a position or vehicle requires appropriate feedback, not just a phone log.
Three ways to organize guest access
| Scheme | Where are the rights stored? | When to consider it | What to check |
|---|---|---|---|
| The guest number is added to the controller | In the GSM controller itself | There are few guests, it is convenient for the administrator to work with the current settings | Adding, deleting, list capacity, change processing time |
| Use the manufacturer's standard service | In the system provided by the manufacturer | The installed model already supports the required guest functions | Model compatibility, roles, terms of service, access revocation |
| Connect an additional gateway | In a gateway system; its SIM is enabled in the controller | It is necessary to expand the management of existing call access | Request verification, originating number, communication, load and failure behavior |
Start with standard capabilities. If they close the task, a separate gateway may not be needed. The add-on becomes useful when you need to change guests frequently, need a different admin interface, or want to tie granting access to a company's workflow.
You cannot compare these options based only on the cost of the board. The calculation includes setup, communication, support, administrator training and actions in the event of system unavailability. For a one-time task, a simple list may be more convenient than developing your own interface.
How does the GSM barrier add-on work?
In the scheme with an additional gateway, two numbers are involved. The first belongs to the device that verifies the user's request. The second is for the existing barrier controller. The administrator adds the gateway SIM card number to the controller's allowed list.
The sequence then looks like this:
- The user accesses the gateway system using the selected method.
- The system checks whether the request is allowed.
- The gateway makes an outgoing call to the controller number.
- The controller recognizes the allowed number and performs the action according to its configuration.
This approach is used in X-CASE CallGate from NBM-IT. The published project describes an ESP32 with a SIM800 GSM module, checking incoming numbers, dialing, SMS with links and a web panel. This is a description of a specific implementation; link duration parameters, limits and additional integrations must be agreed upon for delivery.
You can check the basic conditions of the object on the page CallGate for existing GSM barriers. To do this, it is enough to know whether opening by call works and whether it is possible to add an authorized number. Positive answers allow us to proceed to model verification, but do not yet confirm the compatibility of the entire system.
Call or link: which is more convenient for the guest
A call from a trusted number is suitable for a person who regularly comes to the site and uses one phone. He needs to know the number to contact and call from an authorized SIM card. The instructions should explicitly indicate this condition, especially if the phone has two SIM cards.
A link is useful when it is easier to convey a clear open button to the guest. However, the link, access rights and SMS delivery are separate parts of the system. Receiving a message does not mean that the link is valid indefinitely; a successful link check does not prove that the call reached the controller. The interface must distinguish between these states.
When designing link access, consider:
- to whom and for what object it is issued;
- can it be transferred to another person and is additional verification required;
- when the right begins and ceases to operate;
- the permissible number of uses, if such a limit is needed;
- method of immediate withdrawal;
- message for invalid link;
- help channel if the guest is already at the entrance.
This is a list of requirements for the selected system, and not a list of functions that are automatically present in any GSM gateway. It is especially important to check the feedback: deleting an entry in the panel should lead to the refusal of the next request, and not just hide the user from the list.
How to separate admin and guest roles
The guest has enough information about entry and the actions available to him. The administrator needs the issuance and revocation of rights, a clear device state and request history. The service technician may need communication parameters and diagnostics. It is useful to separate these roles in the implementation task.
For example, the front desk employee must grant access to the guest, but does not have to change the target dial-in number. Otherwise, normal work with visitors may accidentally change the settings of the entire object. It is better to allocate rights to change the configuration separately and check upon acceptance.
Do not send screenshots of the administrative panel with numbers, link keys and service commands to guests. Prepare short instructions: where the entrance is, how to perform the action, what the refusal looks like and who to contact. Use demo data in test instructions.
Communication, power and repeat requests
The call and the web link have different dependencies. To make a voice call, you need a suitable module, a SIM card with available voice communications, and an operator network. To open a web link, you need internet on your phone; further delivery of the command depends on the system design.
In the documentation SIMCom SIM800C GSM/GPRS and voice functions are indicated. Therefore, when choosing equipment in this category, check the availability of the corresponding network and tariff at the installation site. Support for another standard in a region does not in itself confirm that a particular module will be able to make a call. The exact module and antenna must be checked against the package.
Pressing again also requires rules. If the person did not see the result and clicked again, the system should predictably process the request: show the current state, put it in a queue, or reject the replay according to the agreed logic. A repeated call cannot be considered safe in advance - the action is determined by the controller.
For a property with a flow of visitors, discuss simultaneous calls separately. Don't promise arbitrary throughput based solely on the ESP32's power: limitations may lie in the phone channel, the controller, and the drive itself. Check the load corresponding to the actual site scenario.
Acceptance: you need to check both permission and refusal
Create a table before installation. It should have an expected result that can be observed without guesswork.
| Check | Expected result |
|---|---|
| Request a trusted user | The system resolves the request and starts the intended dialing |
| Request for an unknown number | The opening is not initiated; refusal is reflected according to agreed rules |
| Valid link | Eligibility check and agreed action is performed |
| Revoked access | New request is rejected |
| Press again | The specified retry logic is applied, without random additional commands |
| No cell service | The user or operator receives a clear status, success is not simulated |
| Power restoration | The device returns to a consistent state without an unauthorized command |
| Target number error | Diagnostics detect incorrect settings |
Separately check the operation of the normal authorized users of the barrier after implementation. Write down the current configuration and how to revert to it. If the new service is not available, the administrator must understand what the entity's consistent access method remains.
What to include in your quote request
Provide the executor with the controller model, opening method, number of objects, user types, and guest access requirements. Specify where the gateway can be placed, what power and communications are available, and who manages the allow list. For your own interface, attach an example of the workflow, and not just the wish “administrator needed.”
In the estimate, ask to separate equipment, configuration, software changes, integrations, maintenance and communication services. If you need to link to bookings or an internal system, describe the moment of issuance and revocation of the right. This is a separate data exchange task that cannot be considered ready just by mentioning the API.
For a non-standard process, you can start with software development for microcontrollers. If the dialing scheme is already suitable, send a description of the object via NBM IoT form: So the discussion will begin with compatibility and scope of work.
FAQ
Is it possible to connect an add-on without access to the barrier settings?
The allowed gateway number scheme requires controller administrator participation. If he cannot add the number, he must first agree on an available connection method. The mere presence of a barrier's telephone number does not give control rights.
Does the guest need to know the number of the GSM controller itself?
In a plug-in design, the guest accesses a gateway or issued link. The target number is stored in the system configuration. This is convenient organizationally, but does not replace checking rights and the ability to revoke them.
Is it possible to guarantee free opening by calling?
Conditions depend on the tariff and call processing by the controller. Check voice calls, SMS and other communication services before connecting. Without this check, the promise of zero costs is incorrect.
How to prove that the guest really checked in?
The request or call log does not prove this. For such a task, it is necessary to separately determine the source of confirmation: the state of the equipment or the travel accounting system, and connect the events with each other.