Videx GSM Lite 4000 Series - Troubleshooting; System Checks and Testing

66250756-EN - V2.1 - 05/11/19
- 47 -
4000 Series GSM Lite Audio Intercom - Technical Manual
4000 Series GSM Lite Audio Intercom
SYSTEM CHECKS AND TESTING
The following table can be used to help diagnose any potential issues that may be occur during installation and the system checks
that can be carried out to help resolve them.
SYMPTOM TEST / SOLUTION
Interference on the speech. Check the signal strength 1111SIG? (if the signal strength is too low the GSM module increases
it’s power to compensate, causing interference with the speech circuits). Try relocating the
antenna or using a more powerful or directional antenna (e.g. high gain antenna).
Ensure the antenna cables are not running close to the power supply cables or the microphone
wires inside the intercom panel.
Try a dierent SIM card from a dierent service provider as they may have better coverage in
that area.
The intercom panel repeatedly beeps
twice and the back lit name plate of
the module (not additional button
modules) does not illuminate.
Check the power supply has adequate voltage as described earlier in this manual (refer to
pages 7 and 23).
Try a full reset (refer to page 26), powering up with terminals g & 8 shorted.
Try a dierent SIM card.
The GSM LITE intercom module may have a fault.
Double beep, a single short beep
followed by a long beep.
No telephone number programmed for that button. Check the programming.
Check the SIM card is tted correctly (refer to page 25).
The intercom panel does not respond
to SMS messages.
Check the SIM card has an SMS service centre number stored. This will require putting the
SIM card into a mobile phone to check. Contact the SIM card provider if you are not sure.
Check the number you are sending the message to is correct (the number of the SIM card in
the GSM LITE intercom panel).
After sending an SMS message to the GSM LITE intercom listen for a single short beep from
the intercom panel. This will indicate that the message was received and understood. If a long
beep followed by a short beep is heard it indicates the message was either not understood or
the 4 digit master code was incorrect.
Try resetting the 4 digit master code to 1111 (refer to page 26), powering up with terminals
g & 7 shorted.
The GSM PRO intercom does not
respond to SMS messages, but all
other functions appear to operate ok,
e.g. DTO feature, adjusting speech
volumes, releasing the door/gate
when button 3 pressed on the phone
etc.
This issue can occur on smartphones where the SMS messaging input method is set to
UNICODE. Smartphones generally have 3 input methods: GSM alphabet, Automatic and
UNICODE. The UNICODE setting is typically used when emoticons/emojis are used in the
message so the GSM will not recognise text messages that are set to this mode.
Check that the SMS messaging input method setting on the smartphone is not set up as
UNICODE and is set to either GSM alphabet or Automatic. This can ususally be done via the
settings icon on the smartphone. If you are unsure of how to do this Videx recommend
consulting with the user’s manual that came with the smartphone or consulting directly
with the manufacturer of the smartphone.
The call keeps dropping out. Increase the call time (SPT) in programming (refer to page 33).
Check the signal strength and if necessary, move or change the antenna or try a dierent
SIM card provider.
Speech echoes and feeds back. Try lowering the speaker volume using the dip-switches on the back of the GSM LITE
intercom (refer to page 10).
Try adjusting the volume using the programmable settings during a call (refer to user
commands on page 43).
Check the microphone is tted correctly in the intercom panel and that the mic hole is not
blocked in any way.
ERROR message returned in SMS
when programming or no SMS
returned at all even though a ? was
included at the end of the message
sent.
Check over the message sent again and compare it with the examples in this manual.
Common errors include:
1. Using two apostrophe marks side by side instead of “. Note that these look the
same in the message. An easy way to see if this is the problem is to move the cursor
along in the message and if the cursor can get between the two “ then it is not the
correct character used.
2. Lower case letters instead of upper case. For example using stn when STN should be used.
Troubleshooting