You are browsing as a guest. Sign up (or log in) to start making projects!

ryank

@ryank

Joined June 20th, 2026

  • 9Devlogs
  • 9Projects
  • 3Ships
  • 45Votes
Hey folks, My name is ryan, and I like Security and Fire alarms, Cybersecurity, and Telephony! I run my own CUCM (Cisco Unified Communications Manager) system, and also run a community phone system! I've been in the telephone hobbiest community for over 4 years now, and I know a lot about Commercial Security and Fire Protection systems. I am based off of Denton, Texas, and if you want to talk to me, feel free to talk to me in slack!
Ship Pending review

@ryank on CSP RP-01

I made a Alarm Reporting Protocol called CSP RC-01. One thing that was challenging was to figure out how the format will work, and also coming up with a list of standardised event codes. One part that was easy was to make a demo/sample python script that will run a demo receiver for y'all to try out. If y'all want to test out this protocol, you will need to implement it in your own project, and then get monitored by CSP Alarm monitoring. To implement it within your own hardware projects, i recommend you look at my codebase and see how the protocol works. If you have any questions, please contact me on slack or my email at [email protected]

  • 3 devlogs
  • 2h
Try project → See source code →
Open comments for this post

@ryank on CSP RP-01

28m 18s logged

Now implementing checksums, to ensure data integrity! The way checksums will work is that, the receievr will respond with an ack to the panel followed by exactly what the panel sent, and if the panel validates it, it will send another ack!

0
0
1
Open comments for this post

@ryank on CSP RP-01

53m 10s logged

The rough draft of the receiver has been made! The receiver is receiving events, and the next step is to write the initisl specifications of the reporting protocol.

0
0
2
Open comments for this post

@ryank on MeMusicPad

58m 10s logged

Unfortunately the 4 hours spent on working on the PCB design was lost because, I did not know I had to use laspe, but here is my project so far, I currently have the PCB finished, and the case finished

0
0
4
Ship

@ryank on Telephone Tools SlackBot

I made a Slack bot that utilizes my telco tools API. this bot will let you look up the Caller Name (CNAME), and Location Routing Number (LRN) information of a given phone number. you can either make your lookup public, or private by using the -private addon on the command. I had to rewrite some parts of the CSP LRN API to better format it for slack, but since i already had the connections with telco switches for information, it was pretty eassy to setup. When testing, make sure you put in the full 11 digit phone number, and note, it will only work on United States Toll and Toll free number. If you are out of the us, you could test it out with a public company number!

Try project → See source code →
Ship

@ryank on CNAME Tool

I have made a webpage that lets you look up United States phone numbers, and it will return the Caller Name under their carrier account. Some parts that was easy was getting a lookup API, because I already had a API made from my PBX purposes a couple years ago, so I only had to make a web UI that fetches. One part that was challenging was to get flask to work. I had to use *some* AI assistance to get flask working properly. Please read the API TOS in the github repo before using this tool to make sure you follow all local laws and regulations. This tool will only work on Phone Number IF they have a Caller Name associated with it, AND only if the phone number is based in the US

  • 1 devlog
  • 1h
  • 5.69x multiplier
  • 3 Stardust
Try project → See source code →

Followers

Loading…