Underground PBX Guide: Features, Codes and Risks
Explore the phreak.ing underground PBX, its dial codes, conference rooms and privacy claims. Learn what to verify and how to use it responsibly.
Inside phreak.ing: A Practical Guide to an Underground Phone Switch
An old-school phone switch has a certain appeal: dial a short code, get a voice feature, and let the network handle the rest. phreak.ing takes that idea and puts it into a small, internet-connected PBX. It lists features like voicemail, call parking, conference rooms, paging, radio, and a bridge to other phone networks. Some calls can ring a phone and a browser at the same time.
That mix makes the service interesting both as telephony culture and as a lightweight communications tool. It also leaves you with some practical questions. What does each feature actually do? Which commands are worth trying? And what should you believe about an anonymous service's privacy claims?
This guide walks through the features phreak.ing lists, how to think about using them, and where the limits are. The key distinction is authorization: use these controls only for your own extension, or with clear permission from the people and systems involved. A short code can be convenient, but it doesn't remove the need for consent, basic security, and common sense.
What phreak.ing is
phreak.ing calls itself an underground phone switch: a PBX-style service you access through phone extensions and dial codes. A PBX (private branch exchange) routes calls inside a group and can connect those calls to outside destinations or other services. In an office, that might mean extensions, voicemail, transfers, and conference bridges. Here, the same general idea shows up with a more experimental, community-leaning set of features.
The service's listed functions cover several use cases:
- Calling and call handling: place calls, return the last call, park calls, or pick them up from another extension.
- Voice features: run an echo test, listen to a test tone, or access voicemail.
- Group communication: join conference rooms, a voice room, or a live radio stream.
- Extension controls: set do-not-disturb, forward calls, or use intercom and paging functions.
- Text interaction: send a text that posts to the community's
#phreakIRC channel, or request the command list.
It's not presented as a polished business phone system. The public description is short, the features are accessed via dial codes instead of a standard settings interface, and it directs users to an IRC channel. If you're coming from enterprise phone tools, expect to verify how things behave instead of assuming familiar controls are available.
Extensions are the basic unit
phreak.ing says extensions can be any 3-10 digit number. An extension is the address used to reach a user or endpoint on the switch. The description also says calls can ring a phone and a browser, which suggests an extension may map to more than one endpoint. The source doesn't spell out how registration, authentication, or endpoint management works, so check those details before you rely on anything.
Treat an extension as an identifier, not as proof of identity. A short, memorable, or guessable number might be convenient, but it's not a substitute for real account security. Don't assume that picking a longer extension automatically makes your mailbox, phone, or other features more private. Ask what actually protects access and what happens if someone learns your extension (or PIN).
A tool for experiments, not a default business phone system
A compact switch like this can help you understand how call routing and PBX features work together. It can also give you a shared place for voice conversations without setting up a full office phone platform. Still, a feature list isn't the same thing as an operating guarantee.
If you want to use a community-run telephony service for work, customer support, or anything sensitive, confirm the basics first: who operates it, how availability is handled, what call data is retained, and how accounts are protected. If those answers aren't clear, keep your use case low-risk.
Dial codes and what they do
The phreak.ing page lists short codes for its features. The notes below follow that published list; they don't guarantee that every command is active for every user or that behavior matches exactly. Try commands only on your own account - or anywhere you have explicit permission.
Calling, testing, and voicemail
- Call an extension: enter the extension to call someone. The service says the call rings their phone and browser.
- Echo test (
600or*43): use this to check whether audio is reaching the service and coming back to you. It can help narrow down whether the problem is your microphone, your network, or something about the specific caller. - Millwatt tone (
*1004): plays a steady 1004 Hz test tone, a classic telephony signal used for line testing. It's a diagnostic sound - not a conversation feature. - Voicemail (
*97): access your own voicemail. - Voicemail (
*98): access another mailbox by entering its number and PIN. Only do this for a mailbox you own or are authorized to manage. A PIN prompt is an access control, not an invitation to guess credentials. - Last-call return (
*69): call back the number associated with the last incoming call, based on the service's description. Check who you're calling before you proceed - callback features can hit the wrong person if caller information is incomplete or misleading.
Call handling and extension settings
- Answer a ringing extension (
** ext): answer a ringing phone at an extension. Use this only if you're entitled to take the call - like on a shared team line with an agreed pickup arrangement. - Park a call (
70): transfer a call to a parking slot, which the system reads out. A colleague can then retrieve it from another phone. - Retrieve a parked call (
71-79): pick up a parked call using the relevant slot. The page says an unanswered parked call rings back after five minutes. - Do not disturb (
*78/*79): turn do-not-disturb on or off for your phone. - Call forwarding (
*72 ext): forward your calls to an extension. The page lists*73as the code to stop forwarding.
Call parking and forwarding are standard PBX tools, but the details matter. A parked call may time out, and forwarding can send calls to the wrong endpoint if the destination is mistyped. Confirm the destination and tell affected users before using these for anything important.
Intercom, paging, rooms, and extras
The service lists intercom commands that can make a desk phone answer on speaker. It describes *80 ext as two-way and *81 ext as one-way. Because speakerphone activation can expose what's happening around a person, treat these as consent-based features. Use them only with extensions that have opted in and under an agreed policy - don't use them to monitor or surprise someone.
Other group features include:
- Page opted-in desk phones (
*500): broadcast a page to phones that have opted in. Opt-in matters; don't treat this like a way to reach every endpoint without permission. - Conference rooms (
*801-*899): join rooms described as open to anyone. Don't assume a room is private just because the conversation feels informal. - Hardchats voice room (
*3501250): connect to the voice room listed at hardchats.com. - Acid-radio (
*49): listen to the live radio stream described by the service. - Text to IRC (
742735): send a text from a phone to post in#phreak. - Command list (
411or*#101#): request or hear the published list, depending on the command. - Party mode (
*#06#): the page calls this a toggle, but it doesn't say what changes. Check the current service documentation before you use it.
The service also lists 311 as a bridge into PhreakNet and C*NET, with instructions involving a 2600 Hz tone and a KP-number-ST sequence. That's a specialized network feature, not a general-purpose calling shortcut. Don't use it to access other systems or networks unless you have clear authorization and understand the rules for that connection.
Privacy, safety, and operational limits
phreak.ing says it's an anonymous PBX, doesn't keep logs, and asks users not to share personal information. It also advises users not to sign up with their real phone number. Those are meaningful claims, but the public description alone doesn't prove how the service is run - or what data might be visible to hosting providers, upstream carriers, connected networks, or other participants.
A good rule of thumb is: treat privacy statements as things to verify, not as a security guarantee. Don't use an anonymous service for calls that would create serious legal, financial, or personal risk if they were exposed. Avoid sharing passwords, payment details, customer information, medical information, or anything else sensitive in open rooms - or through an operator whose controls you haven't assessed.
A short pre-use checklist
Before you try a feature, check:
- Authorization: Is this your extension, mailbox, call, or opted-in device? If not, get permission first.
- Audience: Is the destination a private conversation, an open conference room, a public IRC post, or something more like a broadcast?
- Credentials: Use a distinct mailbox PIN and don't reuse an important password. Never guess another person's PIN.
- Privacy: Assume a call or message could be visible to the service operator or other participants unless you've independently verified otherwise.
- Reliability: Don't rely on the switch for emergency calls or business-critical communication unless you've confirmed it supports those needs.
- Local rules: Caller-ID handling, recording, unsolicited calls, and telecom access vary by location. A dial code doesn't make an otherwise prohibited action acceptable.
The page lists *67 ext as a way to call with caller ID hidden. Caller-ID restriction isn't the same as anonymity: the service or network may still have technical information about the call, and the receiving system may treat restricted calls differently. Use it for legitimate privacy needs, not to dodge accountability or to contact someone who asked not to be contacted.
What the source does not tell you
The published feature list doesn't explain how sign-up works, whether extensions are reserved, how mailbox PINs are set, whether calls are encrypted, how abuse reports are handled, or what uptime looks like. It also doesn't define exactly how every code behaves. Those gaps aren't proof that the service is unsafe - they're just a reason not to assume.
For a casual experiment, uncertainty might be fine. For a business deployment or a sensitive conversation, it usually isn't. Ask for documentation, test with non-sensitive data, and keep a fallback channel. If you can't get a clear answer to a question that matters for your use case, pick a better-documented provider.
How it compares with mainstream calling tools
A conventional hosted PBX or business phone service usually focuses on predictable administration: provisioning, support, documented call flows, and business-oriented controls. Collaboration apps often focus more on video meetings, chat, file sharing, and directory integration. phreak.ing takes a different route: dial-code interaction plus a bundle of voice features tied to a community environment.
| Use case | phreak.ing's listed approach | What to verify or consider |
|---|---|---|
| Learning PBX concepts | Short codes expose call and voicemail functions | Test on your own extension; documentation is brief |
| Informal group voice | Conference rooms and a listed voice room | Rooms may be open; avoid sensitive discussion |
| Small team call handling | Parking, pickup, forwarding, and voicemail | Confirm access controls, availability, and fallback plans |
| Customer or business calls | The source does not describe business guarantees | Prefer a provider with support and clear operational terms |
| Privacy-sensitive calls | The service claims not to keep logs | Verify the claim; don't assume end-to-end confidentiality |
The right choice often comes down to what happens when it fails. If you're exploring telecom features or joining a community voice room, an experimental switch might be enough. If missed calls affect revenue, customers, or safety, then you should base the decision on support, reliability, security, and compliance - not just on how long the dial-code list is.
If you want a simple way to evaluate any phone service, score it across four needs: control, reliability, privacy, and recovery. Can you control who reaches an extension? Does it stay up when you need it? Are data practices clear enough to trust? Can you recover if a device is lost, a mailbox locks out, or there's an outage? A tool that works well on one dimension can still be the wrong fit overall.
Conclusion
phreak.ing is a compact, dial-code-driven phone switch with more than a basic voice line behind it: voicemail, call parking, forwarding, rooms, paging, and community integrations are all listed. Its appeal is mainly the directness of the interface and the experimental feel of the service. Its limitation is that the public description doesn't answer key operational questions.
Use it for low-risk exploration, stay inside consent and access boundaries, and treat privacy and availability claims as something to verify until you can confirm them yourself. If you're evaluating the service, start with your own extension, test non-sensitive features, and ask the operator the questions that actually matter for your use case. That's a better way to judge a phone system than assuming a feature list tells the whole story.