The second episode of a three-part miniseries sees Deep Learning with PolyAI continue exploring the intricate world of telephony and VoIP! Nikola welcomes back Oisin Glenn, VP of Solutions Consulting, to chat about the historical development, current technologies, and the complexities of modern telephony. They discuss everything from PBX systems, VoIP protocols, and the rise of WebRTC to the unique challenges of international deployments, codec differences, and the open-source revolution in telephony. Learn how traditional telephony infrastructure is being replaced by scalable, IP-based systems and what the future holds for the industry. Whether you're an industry veteran or a curious newbie, this episode offers valuable insights into the telephony landscape. Follow PolyAI on LinkedIn Watch this and other episodes of the Deep Learning pod on YouTube
Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.
Transcript
From the show. Tap a time to play from there.
Oisinthe ability to pass a gigantic amount of really rich context with the phone call is a huge benefit that that comes along with web or tc. And so I think it, it sort of DTMF starts to pale in, in comparison and for
NikolaHello everyone. Welcome to another late night episode of Deep Learning with Poly ai. We continue our sessions on telephony today with Hin Glenn, our VP of Solutions Consulting hin. Good to see you again. Have you been? I've been great. Great. I've
Oisinbeen looking forward to getting into the next segment of this year and talking more about this telephony and VoIP and all that good stuff.
NikolaYeah, I was gonna start it with a classic Damian style. You know, the only podcast where, you know, an Irishman living in New Jersey is explaining telephony to you. So I think it is honor. Maybe we kick off with just, we talked about the history of telephony came to be like where it's going, but we didn't get very technical. So I thought we could have, would just a set of like blitz questions around like. What's a PBX again?
OisinYeah, something that PBX stands for. Private branch exchange. It's essentially a phone system that you're generally running within your organization. You have a private numbering plan. Think about the extension numbers we deal with, like dialing extension, 1, 2, 3, stuff like that. So it's really a private mini phone network that's being delivered by some equipment or service that you have as an organization.
NikolaOkay. Okay. And then moving on, like we talked a bit about VoIP.
OisinSo VoIP. So I think, look, VoIP is a tricky one. So like voice over internet protocol and doesn't technically have to be over the internet. That could be within a lan, within a network of an organization, right? And, but it's using IP as the underlying protocol and I think. When we think about VOIP today, I think we primarily think about sip, which is session initiation protocol. There were some legacy or historical protocols before that. H 3 2 3 MGCP. Cisco had their skinny protocol that they were using with some of their devices.
OisinBut in general, today we really think about sip and I think it's important then to think about this as we think about VoIP, sipp. It's really organizing that session initiation. It's about organizing the phone call. The actual audio of the call is going on RTP realtime protocol, and that's like literally in most cases 50 packets per second in each direction, shooting back and forth with the actual audio. So SIP is essentially organizing the phone call and it's organizing how the RTP is gonna flow between things and then probably. The most modern end of that today would be web rtc.
OisinMm-hmm. Which breaks that tradition a little bit, where Web RTC can in fact be involved in both the media and the organization, although that doesn't always have to be the case, but those are the core protocols that tend to be under that umbrella term VoIP today.
NikolaOkay. Okay. So going into things that might be a bit more esoteric for the audience. Asterisk, I remember this from like the early days of poly ai when we. Didn't have guys like you. And I remember distinctly that I was fascinated'cause it was the first time in a while that I saw two of our engineers with a book, a hefty book. They just had asterisk on it, right? And they spent a lot of time with that thing as they were building out everything and stuff. So it was at that point that I realized that there's a relatively small number of people on this planet who know telephony really well.
NikolaThat knowledge is like not as easily commoditized in that you don't just go and stack overflow and paste a bunch of code. So can you tell me a bit more about asterisk and just like Yeah, the history of that thing?
Oisinyou're totally right. I think so first of all, I think asterisk and some of the things that came along, like whether it's Open Sips Open, sir Kamal free switch. The open source movement there really did bring a democratization to all this because it was super closed. Like before that when you were in the TDM world with PR or T ones Q 9 31, like you literally had to be in at this deep protocol level and it wasn't running over a more open network like an IP network. So, asterisk started, I think I looked it up.
OisinI made sure to check the date'cause I felt like I might have given an erroneous date last week. 1999 and then I think like Free switch started around 2006 and Free Switch was a fork from Asterisk, but essentially asterisk started with, this idea of building something where it could be an open source. Yeah. PBX. And I think, open source has been big in the web all that time. Right? You had open like things like Apache Open Source was really powering the web. But it wasn't at all powering telephony. I think this created at one, an ability to do these things in an open source fashion.
OisinAnd then they were generally very extensible. There were modules you could add to asterisk to do additional things. And I think all of those other open source things have really gone along that road, whether it's, things like Kamal Today or Free Switch. Here's an ability for people to extend and use their imagination and create things either that are very specific to themselves or they become very reusable over time. I would say at the start of it, dig and others. So dig a pretty big sponsor of the asterisk project in particular. There was an avenue here where you still probably needed to connect this to more traditional stuff.
OisinSo there were cards that you would connect either like TDM, phone lines to other things. So there was a bridge between this open source IP world and some of the old school TDM analog world. And these things were quite but in
NikolaOld World, right? What? What were the feuds? Like what were they protecting
OisinIf you go down to the very lowest level, so pots,'cause we love the acronym, so plain owned telephone service. So think about the two wire analog phone in your house. Of course I'm saying two wire, like that's obvious. Not everyone realizes there's just two wires needed to make that work. But essentially that was probably the best standard when you went up a level. So the analog phone would be the most basic thing. Up a level. You had what people called back in the day, pre VoIP, digital feature phones. Yeah. Every brand had their own protocoling for that.
OisinLike if you took a phone from an Avaya, it wouldn't work with a Nortel, it wouldn't work with a Mitel, et cetera. And then as you went up along, so these were proprietary ecosystems and so there was a lot of value in adding features or doing things like this, but it was lock-in. There was a huge amount of lock-in. And I think we remember we talked the other day like. At the very beginning of this, maybe only your national phone company could even sell you a PBX. So there was a lot of lock in, a lot of value protection that was going on, and it very much wasn't open. And I think asterisk other things like this really created that path towards open.
Nikolamaybe taking a quick detour, right. But when you mention kinda like national carriers and things, I mean there are things like codex and things that are different around the world, right? I know that in many of our deployments when they go like multinational multi continent, you get like different performances of speech recognizers and things de depending on exactly how like the audio is transmitted or just how many times it goes through. Whether you test through like VoIP as in you use something like Google Voice or I dunno, calling via Viber or whatever, it can make a very meaningful it can lead to a meaningful degradation compared to just calling on the phone from a network that is national.
NikolaHow did that come to be or how did it get, does it still exist? I know that in places like Japan it's still like pretty difficult.
OisinYeah, so this is a great point. So, and I'll use SIP as the reference for maybe some of this. 'cause I think it's an easy way to put it. So the sip, the session initiation protocol. Within that, there's something called SDP, session Definition Protocol, and that's where all of this. Happens and it's a negotiation. So if I'm calling Nicola, Hey Nicola, I'd love to have a conversation with you and here are the languages I can speak. And among those, and this is gonna be a very limited, my, my set of languages is gonna be the limiting factor here. 'cause Nicola speaks a lot more languages than I do.
OisinHow is your Irish? Uh, not as good as it should be. I'm gonna get myself in trouble here. So yeah, it should be better than it is. So was it mandatory when you were gonna school? Mandatory all the way through the end of high school, and I did pass the required examinations at the end of that, but I'm sadly lacking. Yeah, so, so in this case then you're gonna offer the codex that you are capable of interpreting, and you might even offer things like, here's how I'm able to understand and recognize DTMF tones. Yep,
Nikolayep, yep. DTMF
Oisinis a whole area where this gets problematic, but at the core level, standard voice on most of the world's network. The codec is G seven 11, but there is this split in that there's two flavors of G seven 11. Well, two primary flavors you'll see out in the wild G seven 11 U law or MU law and G seven 11 A law, and Japan and the US use the U law version and pretty much most of the rest of the world uses the A law version. They're really similar, but they're different enough that if you get it wrong, it'll sound like junk.
OisinIt'll sound like garbage. You want people to hear and. If you don't have a match between, like if I offer you only things that you can't speak and literally the phone call fails, or you need to put something in the middle that then does transcoding and so com, computational effort needs to be put to make this. Talk to each other, which slows things down, makes things more expensive. And if you get into the world anywhere, you wanna secure these phone calls, both of things were now encrypted. They both need to be decrypted, transcoded, re-encrypt, and sent on again, further complicating that type of negotiation process.
NikolaOkay. Like just maybe for then the, previously uninitiated viewer, there was this world of different codex and things, et cetera, and then VoIP and together with Asterisk and then like Ka Kamal and everything else came into kind of like, just try to offer a bit of a kind of like universal, kind of like adapter for that kind of stuff. And also to port it online, bring it closer to emerging world of the internet. And when did DTMF. Come about.
OisinOh I looked this up actually'cause I was curious myself after some of our conversation and it be, it was first used in the public network, I believe, like 65, 66, so reasonably long ago, but not way back at the start and DTMF is those tones that you hear on the phone. Yeah. Sounds you dual tone, multi frequency, and I think a key property there is that There's two. So for that. For that three for that, yeah. Yeah. Also, probably if you think about as you started to move from the rotary phone that was pull styling to using those tones as part of the dialing as well.
OisinThat was an all another use and it was a sound that would be very difficult or close to impossible for a human to make on their own. Was also in probably something for people to go Google, but there was something called freaking that went on for quite a while, which is an original type of hacking where people would have boxes that could generate these tones. And in the US in particular, you could select or route calls around carriers using these tones. And there was a whole freaking subculture in the US around this which essentially using DTMF tones to hack things and make free phone calls.
NikolaNice. had the rotary phone in Serbia. I still have it there. No longer works. I don't have a landline in that apartment, but I do have fond memories of this thing, and it worked even when you didn't have electricity, which was really cool.
OisinYeah. Like thinking about the evolution part is we talked about PBXA bunch and I. VoIP came into most people's worlds around that, right? Where maybe the phone on your desk was now a VoIP phone and it talked IP to the actual PBX, whether that was locally in a closet, sitting somewhere in the office, and then the evolution there. So I would call that premise based. And then the next step along that road for folks was probably to host it. And so. Hosted to me is like you had something that used to sit in the corner, now you've moved it to maybe a central data center or your main corporate office or stuff like that.
OisinBut you were, it was still yours. It was a single ownership model. And then I think the next evolution of that was to the as a service. So whether you think about unified communication as a service, contact center service where this thing truly moved to the cloud and they were delivered as multi-tenant platforms by other corporations. Interestingly, a lot of those organizations. Asterisk, free switch, Kamala, a lot of these things were very large building blocks for the people who built those cloud platforms. I think, there's DNA from those open source projects in a huge number of the cloud services we see today across UCCC, et cetera.
NikolaMaybe like, just think of like, we moved to the contact center. You mentioned like ucas Unified Communications as a service, right? There's also CCAS contact center as a service. So like to someone who's like working with CAS provider, say, I have a contact center, I've got 500 agents, right? You are Genesis or NICE inContact or five nine. How do you get me these 500 numbers? Do you even get me these numbers? 'cause they only have like my one 800 number, right? So how does this work in the backend?
OisinYeah, so in general some of these providers are registered as carriers and there's various designations of carriers depending on the country. A lot of them leverage other, incoming carriers. Either the large ones you think about your Verizon's at and t, British Telecom, et cetera. Sorry for not remember, or people like bandwidth.com or other folks like that. So there are people who really specialize. Providing numbers at scale in wholesale, and a lot of those CA UCaaS vendors would then use them and also then for coverage, right into different area codes, into different countries.
OisinI have a business that sells into 10 countries. I want a number in each one. They are using these wholesale vendors to get those numbers, and then they bring them in over shared resource into those platforms, into your application.
NikolaSo for example, even if you bought numbers on Twilio, you would basically be relying on whatever deal they made in that country to get those blocked phone numbers. Right.
OisinEssentially, Twilio's case, I think that's probably the case. They may have an ability to get numbers directly in some of the countries, but yeah, in most cases that's what's happening under the coverage. Yeah.
NikolaIt's fascinating. I remember in some of our early deployments, we relied on functionality where like the Dani, like the phone number of the caller was automatically recognized and'cause it was a kind of I think about 200 different pubs and it was A-P-S-T-N redirect. So it was it wasn't sip right? It was just rerouting the call to a different number that we got in bulk on Twilio. For some of them we would get the, any number of projects we wouldn't, we didn't really know how it was'cause we were just pulling random numbers that were sourced from, well, people with different implementations.
NikolaSo it was just so it's like a pretty deep water where you have to like, for, I think a lot of engineers coming into this, younger people who don't really have a history with telephony. Like you don't really have a place to look this up. And it was quite. A daunting experience early on. It's, it,
Oisinit is very hard and it's also, I would say a lot of it's very opaque. Like for example, like you get two people who are on two different phone companies who call each other. Did the call go from my phone company to your phone company? Or was there one or more intermediate phone companies? And I think in that way, the public network for phone for PSTN, it's analogous to the internet in that literally I could hang up and call again. And depending on lease cost routing, quality routing, it might not take the same number of hops in between.
OisinAnd I know you travel a lot internationally. I've got family back in Europe, like I am forever getting calls from like my dad and a random weird caller ID from Belgium will show up. My dad is not in Belgium generally, but yet this weird number comes up and it's probably because the interworking, the routing was different. So I think you, and it's completely opaque. Again, it's not like a network where you can get a P cap. You've no idea how many people are in between there at that moment in time.
NikolaAnd I guess maybe one difference from the internet, say we're on this call I assume that the packets and things are probably like. The route is changing as we talk. Actually, I dunno that for a fact. It probably depends on the implementation, but it's likely that it would, right? At the different layers of the com of the networking stack for a phone line, it does get established, right? Or it would sit, would it still be possible? 'cause calling someone back and then it working seems irrational. Like you're, a madman trying to get a different outcome, but you very well might get a different route.
OisinYeah, so I think, look, you can get to, and I think like again, it probably comes down to where there is diversity in network, but if you think about if you are on, any of the common unified communication or, uc tools today, like you should be able, if you're on a call, on your cell phone on the wifi and you start walking out, it moves over to the mobile network relatively seamlessly. So, if you think about that, that works. With your cell phone, it works with most uc apps that would work with, a zoom call, a teams call. Again, I don't wanna favor anyone in particular. So I think that stuff can work very well. There's some clever network engineering from those vendors to make that stuff work.
OisinBut in general, yeah, that an in progress call can move networks and certainly the hardest network to move is generally the first and the last network. Yeah, the ones in the middle are very easy to move because the Internet's really good at that. I think that's probably also a pivot point that happened where. Initially, people were super afraid that there weren't these dedicated pieces of wire running these phone calls. And so they were like, well, we're gonna do VoIP, but we're gonna put in a dedicated internet connection that's used for nothing else and for every 22 phone calls we need to double the size of it.
OisinAnd they really, they essentially just made it look like the thing they were really used to. And for a long time, you saw folks where if they were making phone calls, passing them between vendors or to their partners. They'd wanna use NPLS for that. And NPLS is a guaranteed type of service. It's not quite internet. I'm gonna say I have a massive bias here. I personally think the internet is more reliable, more scalable, and more self feelable than NPLS. And Damien, you're probably gonna get like a million comments about people calling me an idiot that this is practically a religious debate.
NikolaOne day, one day. So what is like SIP is introduced, adopted massively. Is there a post sip world? What's next?
OisinLook, I think Web R TC is probably for a lot of things, the successor. And so if you've ever made or taken a phone call or got on a meeting directly from a browser without installing an app, you're very likely to be using Web R tc. And essentially it's using HT P style protocols that are browser friendly to organize and make phone calls over the internet. And dealing with all of the complexities of how the hell to get out of your home network and how to get audio back into it.
OisinThere are technologies that are common to SIP and VoIP there. Turn and stone are things that are used to help navigate network address translation or separated networks. So it has inherited quite a bit of technology from the things that come before. But I would say for that as a first party user and as a kind of a person with a laptop or a phone, web or TC is probably the next. Generation of that technology. I would say in general, things have done a good job of the next generation takes over for the use cases were was really useful.
OisinI don't think WEC replaces SIP everywhere for the things for sip, like I think between poly AI and nice Genesis five nine. SIP is still a really great way to do that. But for getting someone in a browser or maybe in some other condition who doesn't have an actual phone in front of them to connect to poly AI or any of those other folks, web RTC is probably a better way of doing that. So I think we've done a good job of not just throwing stuff away just'cause there's a shiny new tech. Yeah. In this case. So some of these things have lasted for a really long time.
NikolaYeah. And so then with web RTC, that's slowly leaving some of the telephony artifacts back, does it support like DTMF.
OisinIt can, it doesn't, like, again, it's like you need to make it do it if you can. There's also really beautiful things like where, if you think about the problem you were describing with the pub folks, right? The only two things you had was what was the number you dialed to and maybe if you were lucky, you got the number you dialed from. Yeah. With Web R tc, if I click call from that browser page, we know. What cookies are in your browser, we might know which exact page you were on. We might know what you were just trying to do with that. So the ability to pass a gigantic amount of really rich context with the phone call is a huge benefit that that comes along with web or tc.
OisinAnd so I think it sort of DTMF starts to pale in, in comparison and for example, in that webpage. I might just start popping up menus and saying, pick the product you're more interested in. Right? It allows for these rich, multimodal things. Yeah. Where it puts DTMF to shame at that point. But again, when all you have is a phone and all you have is those 12 keys, you gotta work with what you got. Okay.
NikolaOkay. Amazing. Well, I think we're slowly running out of time. I think we'll do another part of the series, which is kinda like more looking at the future and where tele, maybe I'll leave you with one last one. In this world where like that infrastructure, the cables, everything for the old school telephony network was put in place in a world where that's been left behind for, the internet infrastructure being used instead. Are investments still being made around the world in the telephony infrastructure?
OisinIn, in, in the traditional sense of it? No. Some of the large legacy equipment carriers here in the US have actually offloaded all of that analog pot stuff and almost paid companies to take it off their hands in some cases. So it's still there. In countries like Australia and New Zealand are really leading the charge there. It's basically eradicated and everything is IP Now UK is doing a decent job. I, I hate saying it we're pretty far behind in that in the us but yeah, I think investment is very minimal. People are being forced to maintain it because it is lowest common denominator today.
OisinBut yeah, it's. It's all getting replaced by ip, whether you know it's IP or not.
NikolaYeah. Okay. Well I think that leaves us comfortably at what's happened and happening, and then I think next time we'll talk a bit more about the future of it all. It's the ways that it will impact the contact center and well, whatever else we can think of. Thank you for your time. Always a pleasure. And thank you all for listening to another episode of our podcast.
Three years ago, Simplyhealth's PolyAI deployment was only resolving simple FAQs over the phone. Today, they run voice, in-app, email, chat, and WhatsApp conversations on the platform. Nikola Mrkšić talks with Paul...
An agent that gets better every day compounds into a very different agent within months. That's the idea behind Wren, PolyAI's new release: an agent whose job is to make your other agents better. Some of what it finds...
Companies are pouring money into AI, but not everyone is getting the returns. Ian Jacobs, VP and Lead Analyst at Opus Research, thinks he knows why. In this episode, your host Nikola Mrkšić sits down with Ian to work...
When PolyAI built its Builder MCP, one client helped shape it: Vixxo Facility Solutions, one of the largest facilities providers in the US. In this episode, guest host Damian Sasso talks with Vixxo's CTO Derek Neighbors...
PolyAI just launched Dialog-RSN-1, its first audio-native model, and your host Nikola Mrkšić sat down with its builder, Matt Henderson, to unpack why it’s a game-changer for building voice agents. Most voice AI either...