Member Avatar for Javalan

Hi,

I am interested in understanding a little about how Automated Teller Machines communicated "fault alerts" back to central control departments.

What I know so far is that ATM's have senors that can be triggered should say a cash jam occur. So a 'fault message' is first created locally and is then communicated accross the network back to some sort of monitoring software system such as 'Gasper'.

Would such a fault message be coded as XML and then interpreted by the monitoring software. Or would the fault message be stored in a lower level in a IP packet payload, especially if it were a legacy system?

Any info in this area would be of great interest to me. Thanks

  • 3 Contributors
  • 3 Replies
  • 179 Views
  • 3 Months Discussion Span
  • Latest Post Latest Post by doduncan

Dani AI

Generated

Short answer for : there isn’t a single universal wire format — ATM fault reporting depends on the ATM vendor, the local software stack and the monitoring product in use. Modern management platforms commonly accept SNMP traps or agent‑forwarded messages and can also consume web‑service style XML/HTTPS (SOAP or REST); older/legacy estates sometimes carry status inside host protocols or proprietary binary messages. (scribd.com)

How the alert is generated inside the machine is more stable: device drivers and service providers expose state and events via the WOSA/CEN XFS device API (the ATM app or a local agent sees a dispenser jam, cassette empty, door open, etc.). Those local events are converted to whatever the ATM’s monitoring component uses to communicate with the backend. (post.gov.tw)

Vendor examples help explain the options. Gasper/Gasper Vantage historically maps ATM status codes and accepts SNMP traps (it opens tickets, escalates and dispatches); NCR APTRA Vision can receive data from SNMP or from vendor agents and can also be fed transaction‑level insight by tools that sniff ISO‑8583 traffic. That mix (SNMP, agent -> XML/HTTP, or transaction‑derived alerts) is why you’ll see both XML and lower‑level payloads in the wild. (scribd.com)

Practical checks: look for an SNMP agent or vendor agent process on the ATM, inspect open ports (netstat) and the monitoring server’s supported interfaces, or capture the control channel with a SPAN/TAP in a PCI‑compliant way (mask any PANs). Expect legacy link types such as dial‑up, X.25 or leased lines on older deployments. Note that some details are tightly restricted for security reasons (as hinted). Good starting references: WOSA/CEN XFS, Gasper product notes and APTRA/Vision material. (en.wikipedia.org)

Member Avatar for stokes1900

I think no body will help you on this question . it is for to avoid bank robberies.

Member Avatar for Javalan

I think no body will help you on this question . it is for to avoid bank robberies.

You obviously did not understand the question correctly I should have explained more. I have since found out everything I need to know about the subject, no great mystery really!

Although maybe it is to you haha

Edited by Javalan because: n/a
Member Avatar for doduncan

Hi Javalan.

I am Dennis. I am interested in knowing where you got the information regarding ATM monitoring. Can you share with me please?

Regards

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.