Boris Starkov (ElevenLabs) explains how he reverse engineered the undocumented proprietary protocol of a Viking VoIP phone using Claude Code. After three senior engineers and ChatGPT failed to make the phone work, he brute forced all 676 two-letter command combinations (80 valid), ran a TCP proxy between a Windows XP virtual machine and the phone to intercept the proprietary software's traffic, and reverse engineered a one-byte checksum by testing known input/output pairs until a simple subtraction formula emerged. His role was physical: rebooting the phone and reporting beep counts while Claude orchestrated. The protocol is open sourced as a Claude Code skill; the demo at AI Engineer Europe was a red phone booth connected to a Michael Caine voice agent quizzing users on British AI history. # Channel Presentation Observations ## Explicit Self-Description - **Creator affiliation**: "I'm Boris. I work for 11 Labs. Usually we do agents voice agents like all things voice." - **Team's claimed scope**: Eleven Labs is presented as building **voice agents** and "all things voice" products. - **Creator's self-assessed skill level**: "I'm not a security engineer whatsoever. I'm actually like just a normal software engineer" — a stated claim framing the talk's premise (an AI tool doing reverse engineering beyond the speaker's expertise). ## Intended Audience - **In-person developer/conference audience**: The talk is delivered live at a summit (Twilio mentioned as organizer; lunch scheduling; "Next session is at 11"). - **Developer-tooling-aware audience**: Assumes familiarity with nmap, TCP proxies, SIP trunks, virtual machines, PoE — presented without beginner-level explanation. - **Audience invited to try the demo**: "On the third floor we have this red telephone booth... you should totally try it." ## Claimed Scope of the Content - **Demonstrating Claude Code for hardware reverse engineering**, not just application building: "How to use Claude code not just to build applications, but how to use it to actually like reverse engineer some hardware." - **Open-sourced output**: "I put all of this as a skill and open sourced it" so others can program Viking phones without Windows software. - **Generality claim**: "I think this is extendable to other hardware as well... you can connect to any like piece of hardware in your house." ## Observable Presentation Patterns - **Narrative case-study format**: A single end-to-end project (legacy Viking VOIP phone → Twilio → Eleven Labs agent) told chronologically, with failure points (settings not persisting) and resolutions. - **Anthropic-tool-centric framing**: Claude Code is the agent of nearly every action — "Claude code started exploring it," "it nmapped all of the ports," "Claude didn't give up at this point." The speaker repeatedly credits the tool: "It just made it possible." - **Human-in-the-loop disclosure**: "I was actually like the agent for Cloud. Like Cloud was orchestrating the whole thing" — including the anecdote about counting beeps. - **Cost transparency**: When asked about token usage, the speaker estimates "between 10 and 100 dollars" using corporate tokens. - **Terminology care**: "I'm really trying to avoid the word hack... I reverse engineered it." - **Meta use of the tool**: "These slides are fully fully made by Claude code as well." ## Supported vs. Unsupported Distinctions - **Supported by transcript**: All items above are quoted or directly paraphrased from the transcript. - **No channel-wide metadata** was supplied, so observations are limited to this single talk; no subscription claims, upload patterns, or broader channel identity can be assessed. - **Private motivation**: Only stated motives are cited (the demo, the summit booth); none inferred. # Delivery Observation: Boris Starkov — "Reverse engineering a Viking VOIP phone protocol with Claude Code" ## Overall Delivery Style A **conversational, improvised technical talk** delivered in a casual, self-deprecating register. The speaker uses heavy **verbal fillers** ("um," "uh") throughout, suggesting an unscripted walkthrough rather than a rehearsed presentation. - **Filler density** is very high, e.g., *"Uh so we couldn't really like easily set it up."* and *"Um Yeah, the problem. I have a Mac."* - Sentences frequently **restart and self-correct**: *"it can only make a phone call to a phone number"* preceded by *"Uh it can only make a phone call to—"* style revisions. ## Vocabulary and Word Choices ### Distinctive vocabulary - **"Crack"** as a recurring verb: *"then I tried to crack it hack it, reverse engineer it using Claude code"*, *"at this point the phone was pretty much cracked"*, *"if you want to crack some other hardware."* - **Explicit vocabulary self-monitoring**: *"I'm really trying to avoid the word hack uh that I hacked the phone. I reverse engineered it."* — a notable metalinguistic moment. - Technical shorthand delivered casually: *"nmapped all of the ports"*, *"man in the middle attack kind of"*, *"brute force"* / *"brute forcing."* ### Recurring terminology - **"Skill"** (in the Claude Code sense): *"I put all of this as a skill and open sourced it"* — used at least three times. - **"Closed loop"**: *"make it fully like close the close the loop"* and *"it was kind of like closed loop iteration."* ## Recurring Phrases and Rhetorical Patterns ### Repetition for emphasis A very stable habit is **immediate word repetition**: - *"we we we asked them to send it to to London"* - *"It it it's not just it made it 10 times faster, it just made it possible"* - *"the the the problem I stated in the beginning"* This is frequent enough across the whole talk to be a **stable delivery trait**. ### Marketing/audience-engagement refrains - The demo plug is repeated near-verbatim at open and close: *"you should totally give it a try"* / *"you should totally try it"* — a deliberate framing device. - *"It's it's it feels magical."* ### Self-deprecating competence framing A recurring pattern of downplaying his own expertise: - *"I'm not a security security engineer whatsoever. I'm actually like just a normal software engineer"* - *"I had no idea what was going on... It was just smarter than me, I think."* - *"I was too lazy so I just did what it told me to do."* ## Teaching Habits and Structure ### Narrative problem–solution arc Delivery follows a **chronological debugging story**: failed setup → port discovery → brute force → dead end → proxy interception → checksum reverse engineering → open-sourced skill. Each step is introduced as a mini-cliffhanger: *"But the problem is the moment the phone got rebooted they all were gone."* ### Attributing agency to the tool A consistent rhetorical move: framing **Claude Code as the actor**, with himself as assistant: - *"by saying I started exploring, uh Claude code started exploring it"* - *"It it was orchestrating it. Like I had no idea what was going on."* - *"I was the hands for Cloud"* (note: transcript renders "Claude" as "Cloud" at several points, likely an ASR artifact — treat those as the same word). - The memorable anecdote: *"It was like, 'You idiot, it's either two or four.'"* ### Interactive hand-raising moments The speaker polls the audience repeatedly: *"Did anyone? Oh my god. Okay."* — repeated later as *"How many of you have tried it? Have has anyone? Oh my god."* The identical reaction suggests a rehearsed or habitual bit. ### Meta-commentary on slides He narrates slide authorship and even slide failures: *"I don't know if the slides are going to show this"* and *"By the way, I'm not sure Okay, I'm not sure what this is."* — an informal, transparent delivery habit. ## Uncertainty Markers The speaker frequently **hedges or expresses genuine uncertainty aloud**: - *"SA for status kind of makes sense. I don't know if it makes sense."* - *"I think it took me like couple of days"* - *"it took me like couple of days to to reverse engineer it"* (approximate figures) ## Q&A Delivery - **Short, candid answers** with humor: on token cost — *"[sighs]... I used Eleven Labs our corporate tokens... between 10 and 100 dollars. So, quite reasonable."* - Willingness to admit limits: *"intellectually I couldn't unblock it... I unblocked it by like actually like rebooting like physically rebooting the phone."* ## Summary of Stable vs. Isolated Features - **Stable patterns** (well-attested by repetition): filler-heavy conversational tone, immediate word repetition, Claude-as-agent framing, problem/solution narrative structure, audience-polling plugs for the demo. - **Isolated moments** (insufficient repetition to call habits): the "avoid the word hack" disclaimer, the "You idiot" anecdote, slide-failure commentary. These are notable but occur only once each. # Observation Record: Reverse Engineering a Viking VOIP Phone Protocol with Claude Code **Speaker:** Boris Starkov, Eleven Labs (per video metadata and self-introduction) ## Context and Project Goal - Starkov works at Eleven Labs, which builds **voice agents**. - The project: connect a **retro Viking phone** (in a Twilio red phone booth demo at the summit) to an **Eleven Labs conversational AI agent** with an approved Michael Caine voice, walking callers through five questions on British AI history with swag rewards. - Architecture stated: **Viking phone → Twilio (handling SIP domain complexity) → Eleven Labs**, since the phone can only call a phone number. - The presentation slides themselves were generated by Claude Code from the project conversation transcript. ## The Problem - The phone shipped only with **Windows XP-compatible software**; nobody at Eleven Labs had a Windows laptop (all Macs), and virtual environments had driver issues. - The San Francisco team bought the phone a year earlier; **three senior software engineers plus ChatGPT** could not make it work, and the phone sat unused for a year before being shipped to London. ## Reverse Engineering Process (attributed to Claude Code, narrated by Starkov) ### Discovery - Starkov connected his laptop to the phone via a **router** (phone on **Power over Ethernet**). - Claude Code nmap-scanned ports: port 1001 was a wrong lead (electronics tunnel); it iterated to find the actual communication port. - Claude Code sent a test sequence; the phone responded, confirming a live protocol — but one with **no public documentation**. - Invalid input returned `ER` + the string, inferred to be an error response. ### Brute-forcing commands - Claude Code determined the phone uses **two-letter command codes**. - It brute-forced all two-letter combinations: most returned errors, but **~80 were valid commands**; some names were interpretable (e.g., "SA" possibly status — Starkov expressed uncertainty). ### Persistence dead end - Credentials for the Twilio SIP trunk could be written to the phone but were lost on **reboot** (temporary memory only). - Claude Code spent a **multi-hour** effort, including iterating all three-letter commands and reasonable words, without finding a save mechanism. This matched where the San Francisco team had stalled a year earlier. ### Man-in-the-middle via Windows VM - Claude Code's solution: run the vendor's Windows software in a VM to intercept its traffic with the phone. - Constraint stated: **Wi-Fi cannot be bridged to macOS VMs**, so no VM internet access. - Workaround: Claude Code set up a **TCP proxy on the Mac** relaying VM traffic to the phone while **logging everything**. ### Checksum cracking - Intercepted traffic revealed the previously unexplained **TS command** with binary payload. - Parameters were mostly interpretable except a **one-byte checksum** — small enough to brute force. - The "encryption" turned out to be simple arithmetic (a simple one-byte addition/subtraction on the checksum). - Starkov emphasized Claude Code **verified the algorithm via closed-loop iteration** on more values, not just guessed it. ### Resolution and outcome - A specific command sequence was found to **persist settings to memory**, plus a 256-byte memory region was also cracked. - Starkov **factory-reset the phone** and now programs it directly without the VM; he packaged the knowledge as an **open-sourced Claude Code skill**. - Connecting to the Eleven Labs agent was "super easy" compared to the reverse engineering, which took "a couple of days." - Starkov preferred the term **"reverse engineered"** over "hacked." ## Claims About Protocol and Lessons - The protocol has **two layers**. - Luck mattered: the single-byte checksum was easy; harder encryption would have been much harder to break. - Persistence required the intermediate proxy server between the Windows VM and the phone. - **Claim:** Without Claude Code the demo would not have been possible at all — not merely 10x faster — because Starkov is a general software engineer, not a security engineer ("What is 0x?"). - **Claim:** The approach generalizes to other hardware; previously proprietary vendor software was required, now direct network connection suffices for comparable devices. ## Q&A Positions - **Cost:** Between **$10 and $100** in tokens (corporate Eleven Labs tokens). - **Human role:** Starkov acted as Claude's "hands" — physically rebooting the phone, counting beeps ("It's either two or four"), controlling the VM. He suggested computer-use tooling could have closed the loop fully but he "was too lazy." - **Unblocking:** He could only unblock **physically**, not intellectually: "It was just smarter than me, I think." - **Physical connection:** PoE cable to a router; laptop on the same router's Wi-Fi; Claude Code scanned the network to find the phone. # Speaker Attribution Record ## Video **Title:** Reverse engineering a Viking VOIP phone protocol with Claude Code — Boris Starkov, Eleven Labs ## Speakers | Speaker | Role | Identification basis | |---|---|---| | **Boris Starkov** | **Creator / presenter** — sole presenter; self-identifies: *"I'm Boris. I work for 11 Labs."* | Explicit in transcript | | **Audience members (unnamed)** | **Other — Q&A questioners** | Ask questions after talk: token cost, whether Claude controlled the Windows/UTM setup, whether Claude got stuck, physical connection method | ## Speaker Roles Summary - Single-presenter talk with a Q&A segment. - Audience questions appear in transcript without names; they cannot be attributed to specific individuals. ## Provenance Facts ### Referenced entities / claims - **Eleven Labs** — Boris's employer; built the demo; supplies the AI agent and (per Boris) the Michael Caine voice ("approved"); promotional tie-in throughout. - **Twilio** — identified as **event organizer** ("This is Twilio by the way, the organizer") and referenced as intermediary for SIP trunking. - **Anthropic Claude Code** — tool used for reverse engineering; also generated the slides (per Boris). - **ChatGPT** — referenced as the tool available one year earlier when the San Francisco team first tried and failed. - **Viking phone** — third-party hardware, reverse engineered; protocol described as undocumented ("not Google-able"). ### Third-party claims (uncorroborated in transcript) - Demo phone connects to an AI agent with **Michael Caine's voice, "approved"** — Boris's claim only. - Token cost estimate: **"between 10 and 100 dollars"** using corporate Eleven Labs tokens — Boris's estimate. ## Promotional Segments (flagged) - **Opening and closing segments:** repeated promotion of the red telephone booth demo on the third floor ("You should totally give it a try… It feels magical"), with **swag giveaway from Eleven Labs** for answering quiz questions. - **Closing remarks:** "this step is super easy thanks to Eleven Labs." ## Availability / Limits - **Comments:** no comment availability information present in supplied material. - No timestamps present in transcript; roles inferred from speech content only. \>\> Hi everyone. Thank you for coming. Even though there is a lunch being served now. Really appreciate you coming here. Um I'm Boris. I work for 11 Labs. Usually we do agents voice agents like all things voice. But for this chat I just wanted to show you something else. Um you might have seen if you've been on the third floor, you might have seen this phone booth. This is Twilio by the way, the organizer. Um Um We've built it as a as a demo. Um demo for this summit. Uh there is this phone inside. Um and I don't know how many of you have went through it. Did anyone? You should totally give it a try. Oh my god. Okay. But uh the idea is that when when you pick it up, you actually end up talking to AI agent uh with the Michael Caine's voice uh approved. Um there you go. Who who then walks you through five questions about British AI history. And then if you answer at least one of them, you can get a swag from from 11 Labs. So that's the idea. But uh today I want to show you how I actually build it. So this is how it looks like now. And this is how it looked like last week. This is the um old I mean it's not that old. It still has a a controller inside, but it's a quite old piece of hardware, this phone. And the main problem when we tried to make this happen the main problem with the this piece of hardware was that um it only had uh Windows Windows XP compatible uh software. So it was very hard to set it up cuz it turned out that nobody at 11 Labs have a Windows uh laptop. Uh they all had Macs. But also when we tried to set up like a virtual environment, you know, also had some driver issues. So uh what happened to this phone? Um Our team in San Francisco purchased it 1 year ago for some other event. And three software engineers, three senior software engineers and a Claude uh sorry, ChatGPT at the time, they couldn't figure out how to make it work. So it was just for 1 year it was just laying there uh waiting for waiting to be rescued. And uh for this project we we we asked them to send it to to London. Um and uh then I tried to crack it hack it, reverse engineer it using Claude code. And this is what I wanted to talk about. How to use Claude code not just to build uh applications, but how to use it to actually like uh reverse engineer some hardware. So by the way, this slides are fully fully made by Claude code as well. So I the way I made them is I um put the whole conversation we had about this um process and then asked it to as a context and then asked it to make slides based on that. So the goal here uh what we want to achieve is uh they have this Viking phone. The uh retro legacy Viking phone. And we want to connect it to a conversational AI agent by 11 Labs. Uh it can only make a phone call to a phone number. So we need to put Twilio in between. Just um to handle that a SIP SIP domain complexity. So it goes Viking phone, then Twilio, then 11 Labs. Um Yeah, the problem. I have a Mac. Uh so we couldn't really like easily set it up. Uh so what we ended up doing, what I ended up doing instead, I uh connected the connected my laptop to the phone via router and uh started exploring. I mean, by saying I started exploring, uh Claude code started exploring it. So first it um nmapped all of the ports that were available. Uh so port 1001. Um Which turned out to be the wrong one. It was just uh electronics tunnel. Uh then it proceeded to iterate and the next one was the actual uh target port that could be used to communicate with the phone. So step one, Claude code found the way to communicate with the phone. Um then uh then it started discovering it. So it sent um some random sequence. I mean, not random Viking, but just random sequence. Um to the phone and the phone responded. So that's how Claude code realized that um that this is an actual interface, a protocol. But the protocol is not like Google-able. You can't There is no open documentation on what the exact protocol is. So it had to then um reverse engineer it, right? So first thing Claude noticed is that when you send a random string to the phone, it returns uh this ER and then the string itself. Meaning likely it's an error. Error that this string is not a correct command for the phone. So next um Yeah, next Claude figured out those commands that um that this this phone it operates using two-letter commands, command codes. Um some of them are non-existent, then it returns an error like on this slide. Other, however, they return something else. Um the next idea was that actually if it's two-letter commands, then we can just iterate through all of them, right? Uh brute forcing. So it wrote this this program and literally like tried out every single combination of two letters. Um and it turned out that most of them returned error codes, but 80 of them returned actual like something else, meaning they're actual valid commands. Uh those were some of them. By the way, I'm not sure Okay, I'm not sure what this is, but uh Yeah, then it then it some of the commands they kind of made sense based on the on the name. Maybe not those ones, but for example uh SA for status kind of makes sense. I don't know if it makes sense. Yeah. Uh Then then it proceeded to try to set up the actual credentials on the phone. So this is this is uh this is the phone memory. And it basically what they're trying to do here is to put the right credentials to the phone memory so that it knows where to call. We want to call Twilio SIP trunk, right? Um And it turned out that yes, these commands they worked and all of the settings got accepted. But the problem is the moment the phone got rebooted they all were gone. So they were not saved in the memory. They were just wrote to the temporary memory. And then uh we started me and Claude code we started like a multi-hour operation of trying to figure out how to actually save what you put to the put to this like temporary memory, how to make it actually um persistent. Like how to save it to the long-term memory of the phone. It tried everything. It tried different commands. And then it I don't know if the slides are going to show this, but it tried three-letter commands. It iterated over all three-letter commands, over all reasonable words. And it didn't find anything. Uh so this was the dead end situation. This was around the place where our team in San Francisco, when we just started exploring it the first time. Um They they could they couldn't figure out what to do next. But that was 1 year ago when um there was only ChatGPT. Now with Claude, Claude didn't give up at this point. Claude suggested that uh there is a Yeah, Claude figured figured out the problem and then it suggested a solution. So the solution at this uh step was was to set up a Windows virtual machine. However, uh the main problem with with Windows virtual machine is that you can't bridge Wi-Fi um to macOS. So there is no internet connection in the Windows virtual machine. So what Claude did next was actually a very smart thing. It set up a TCP proxy on the Mac so that the uh traffic from the virtual machine Oh, why are we setting up virtual machine? Because in the virtual in the Windows virtual machine, we can set we can um run the software of this phone that actually knows how to communicate with it. So the solution uh so what we're trying to do now, we're trying to uh put like a man in the middle attack kind of to intercept the traffic between the software and the phone to analyze it and to figure out how how it communicates, how it works. So, the software is running in Windows virtual machine now. Then it it's directed it communicates to the proxy on my Mac. The proxy is relaying it to the Viking phone, but also it logs everything so that to figure out what they're talking about and what's the protocol is, what are the what is the missing piece. Um very simple code. And then yeah, then it started capturing the communication. And it figured out that there was this command that uh that Cloud didn't understand before, which is TS. Um which had like some weird binary payload. And then that had like this format. And what you can see here is most of the most of the params of this uh command they kind of make sense except for the checksum. But checksum turned out to be only uh one byte. So, it's something that you can brute force as well. Um right. Yeah. Uh so, the way it it work it doesn't know the checksum, but it knows which data is being sent and it knows the result. So, it can easily reverse engineer the the encryption protocol. Which is just which turned out to be just adding a uh Yeah, basically doing a simple subtraction like adding a sim a simple one byte value uh to the checksum. It not just Cloud code, I want to highlight it. Cloud code didn't just figure out what the um format of the checksum is. It actually like managed to find it and then it confirmed it uh by running uh by running more values through it. So, it it was kind of like closed loop iteration. Um and at this point the phone was pretty much cracked. Um so now we managed to figure out how the software communicated to the phone. And uh we had the list of commands and we What was that? Yeah, and then we figured out how to actually the the problem I stated in the beginning, how to actually uh save what you what you put to the memory. We need um this uh to run this sequence of commands. Um and the last one the fun bit was that actually there is this uh 256 bytes um memory in the phone which um it also happened to crack. Um and then the the last bit the last bit of this process was that actually I didn't want to run Windows virtual machine every time. So, the last bit was actually uh now when I know the protocol, I know how to talk to the phone. I can just factory reset it and now I can use this skill this information to program it directly without having to run the virtual machine at all. So, what I did I put all of this as a skill and open sourced it so that now um now everyone if any of you by any chance have a Viking phone, you don't have to set up Windows machine. You can just ask Cloud code like give this uh skill to Cloud code and it will set it up. Um yeah, victory. Um it works. I mean, I didn't go into much details about how this step works because it's super easy thanks to Eleven Labs. We we really made it end video. I mean, this step is super easy. This one was the most painful part. I think it took me like couple of days to to reverse engineer it. I'm really trying to avoid the word hack uh that I hacked the phone. I reverse engineered it. Um Yeah. So, I mean, what we learned about the protocol it has two layers. Um the encryption it we were lucky that the encryption was just a single byte checksum because it if it was something harder than it would probably be much harder to break. And um yeah, and the persistence bit we had to run the server intermediate server between virtual Windows machine and and the phone. And that's how just yeah to comment on the step five here. Um without Cloud code it wouldn't be possible to to to do that demo. It it it's not just it made it 10 times faster, it just made it possible because I'm not a security security engineer whatsoever. I'm actually like just a normal software engineer and I had like when I looked at all this like programs, I was like, what what is that? What is that? What is zero X? Okay. Um Yeah, that's it. Um so, now uh the outcome of this is not just a nice demo that you can see on the third floor. It's also a skill that makes it much easier to to program the this this kind of phone and um the nice part is that I think this is extendable to other hardware as well. So, it's not just like Viking specific, but like if you want to crack some other hardware I would really recommend thinking about Well, you don't the the difference is that 1 year ago you actually needed the proprietary software interface that the provide the the company that made the hardware provides. Now you don't need it. You can connect to to the phone, but you can the same way you can connect to any like piece of hardware in your house. Um so, this is this is cool. Um yeah, this is how it started and the the actual demo again to people who just came here. On the third floor we have a this red telephone booth that lets you speak to Michael Caine. How many of you have tried it? Have has anyone? Oh my god. Okay, you should totally try it. It's it's it feels magical and I just uh told you how I how I made it into real life. Yeah. Um any I guess any questions? This is the booth. And this is Swiggy. \>\> tokens you burned? \>\> \[sighs\] \>\> I used Eleven Labs our corporate tokens. So, I I yeah, I think it was in order of between 10 and 100 dollars. So, quite reasonable. And and did you did you have the did you have Cloud So, you see you had some software installed on UTM on Windows. Did you have Cloud control that as well? Or or did somebody have to manually It it was a quite interesting because my participation in that was basically following Cloud's commands. \>\> Right. So, it would tell me like, "Hey, can you can you like take the handle and how many beeps can you hear?" And I would like listen and like, "Okay, I think three." It was like, "You idiot, it's either two or four." And I'm like, "Oh yeah, it's two." So, it was like I was actually like the agent for Cloud. Like Cloud was orchestrating the whole thing. And answering your No, answering your Basically, I was the hands for Cloud. It couldn't really I think if I use like computer user something I could make it fully like close the close the loop and make it control the virtual machine, but I was too lazy so I just did what it told me to do. Were there any places where Cloud got stuck and you had to unblock it? Uh stuck in in what sense? As in it couldn't figure out the next step. So, that's the thing. It it was orchestrating it. Like I had no idea what was going on. So, intellectually I couldn't unblock it. So, you just unblocked I unblocked it by like actually like rebooting like physically rebooting the phone or like controlling the virtual machine, but the intellectual part which is like cracking the cracking the algorithm I could I wouldn't be able to unblock it. I mean, it was just smarter than me, I think. Yeah. Um How how did you physically connect to the phone? Yeah, I I wish I had a picture. Um So, this phone you can see the black cable. It's uh called power over Ethernet, PoE. Yeah. Which is uh basically there is an Ethernet cable, the one that everyone probably has at home for home internet and there is also a power adapter and it brings them together. And I put a router in between which let me connect my So, this was connected to the router and my laptop was connected to the Wi-Fi router as well. And then yeah, and then there was this step of uh \>\> \[clears throat\] \>\> searching the network. So, this was the first step. Cloud just checked all of the devices connected to the router and found the the phone. Okay. And I have full time. Yeah. Next session is at 11. \>\> Thanks. Thanks everyone. Great. Um \>\> \[applause\]