Houston, we have a platform.

Well, we've been busy – sorry for not keeping you better updated. Let's run through some updates quickly, shall we?

• We had a ton of fun at CypherCon and BSides MKE testing our voice agents running Call Center Village!
• As Call Center Village continues to expand, we're looking for more partners (call centers) to receive social-engineering test calls.
• We launched our free, open training on voice-cloning, voice-agents, and social-engineering over at voice-training.callcentervillage.com
• Our alternative scripting tool for Intelligent Series is coming together nicely. It continues to go through rapid progression, so you'll have to stop by office hours if you want to see this one.

Other non-product efforts & updates:

• After an unnecessarily long time, we've finally completed our migration off of Google Workspace for Business.
• We're dumping Zoom in favor of Proton Meet. Customers will receive updated calendar invitations with the new links over the next several weeks.
• Our blog has joined the Fediverse! You can follow us on any ActivityPub supported social-network at @sigint@blog.calltheory.com
• We're trying out IRCv3 over at chat.calltheory.com as an eventual replacement for our (mostly-dead) Slack community. We will continue to maintain customer-specific workspace Slack support!

Already on IRC? Join #support on irc.calltheory.com:6697

• We're taking Call Center Village to WISCON, a new cyber-security conference taking place in Madison, WI in June! We'll see you there!?

WISCON 2026 - Wisconsin Information Security Conference

Wisconsin Information Security Conference (WISCON) 2026 - Premier cybersecurity conference for IT professionals, students, and security enthusiasts.

WISCON Logo

Tech Talk

These are a few random problems we've been working on that we thought would be worth sharing.

1. We've seen several instances of elevated STUN timeouts when using stun:stun.counterpath.com:3478 from Microsoft Azure. Check your Asterisk consoles for warnings/errors to determine if you should change STUN servers. You can also use sngrep to see if you're carrier is cancelling calls due to timeout issues. If you have continued problems connecting to STUN, try an alternate port (like stun:stun.l.google.com:19302.)

My guess is that CounterPath turned off backwards compatibility so reflexive address-mapping stopped working for incompatible clients. Asterisk (via res_stun_monitor) requires MAPPED-ADDRESS from RFC3489 and effectively ignores XOR-MAPPED-ADDRESSES from modern STUN (RFC5389/RFC8489.) Of course, this is all speculation on my part because I had to do the same thing on our STUN server to get it working with Asterisk.

2. If you're on Amtelco's Intelligent Series v5.6+ which includes the System Email functionality, you should avoid using it in conjunction with MergeComm accounts. Specifying a System Email reference in a Client account's Email Accounts section will cause MergeComm triggers to be skipped. Instead, you should select the Custom option, and configure the details directly in the Client account.

If you run into an issue where MergeComm jobs are being sent to an account as a Dispatch Job instead of hitting your trigger, it's worth checking on this. Also, if you migrate from Inbound SMTP accounts to the MSGraph Receive, you should use POP3 triggers instead of SMTP triggers. This isn't immediately apparent from the documentation.

3. When setting up accounts for use with MSGraph Receive in Microsoft Office (or whatever it's called these days) you should setup an Enterprise App, API permissions, Security Tokens, Mail-enabled security groups, and App Policies independently for EACH account you need to receive email.

I initially made the mistake of trying to use the same Enterprise App registration with different mail-enabled security groups and app-policies but couldn't get the POP3 isolation working. Learn from my mistakes (or teach me something new?)

Hopefully, one of these is helpful to someone out there.

Our new platform, Orbital.

Even as our new call-center platform was coming into shape, we had trouble coming up with good names. Nothing was really sticking – although CallAxe came pretty close.

Call Axe: We cut the waits...

Really has a nice ring to it, no? Also fits the "Agent Exchange" ("AX") product category naming we're trying to create. But still, it wasn't quite what we wanted.

If you couldn't already tell, I have a strong affinity for space. Prior and active product names include Shuttle, Mission Control, Starbase, Wormhole, and Satcom. While we were traveling to Milwaukee, the Artemis II mission launched. And then, we saw the return of the astronauts safely after we got back.

Watching the Artemis II return to earth, it got me thinking about the Artemis IV taking humans to the lunar surface one day, and – well, I couldn't get this one word out of my mind...orbit. And with a small tweak, we had a winner.

Orbital is a modern call-center platform with native support for both live operators and AI agents. No constraints, quotas, usage caps, or artificial restrictions.

• Your Servers;
• Your Carriers;
• Your Customers;
• Your Agents;
• Your AI;
• Your Data;

We are testing Orbital with a few trusted customers, and if everything goes well we'll be expanding to more of you shortly. If you're an active customer and want to see more or join the beta, let us know in our next meeting!

Orbital | Call Theory

Orbital is a self-hosted, multi-tenant call center platform. Run your own answering service with AI and human operators side by side — on your own infrastructure.

Call Theory

We'll have significant more details, screenshots, documentation, and more – once I figure out how to do that whole "marketing" thing. In the meantime, consider joining us at our weekly office hours to get a glimpse! Not a customer? Email support@calltheory.com to get a temporary link to join! (Most Tuesdays, 3pm Eastern)

Expect an official product roadmap to track platform-progress and feature-requests in our next newsletter.