VoiceOps
By thread
voiceops@voiceops.org
By month
Messages by month
- ----- 2026 -----
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
December 2015
- 56 participants
- 178 messages
Future of the Traditional PSTN vs VOIP and VoLTE
by abalashov@evaristesys.com
?I could also see the Tier 1s enthusiastically supporting a system that appears to rationalise anyone below themselves out of the supply chain. :-)?
They're getting better and better at delivering smaller transactions. It started out with the stereotypical, "Level3 won't talk to you unless you've got at least $25k/mo to commit", but where we are today is that just about anyone can have MFN pricing with a $500 deposit and a miniscule commit. Soon anyone with $10 will be able to terminate US domestic at $0.001.
The proposed system might just hasten this process along, as the big CLECs that feed the industry ask, "Why do we need resellers again?"
--
Alex?Balashov?|?Principal?|?Evariste?Systems?LLC
303?Perimeter?Center?North,?Suite?300
Atlanta,?GA?30346
United?States
Tel:?+1-800-250-5920?(toll-free)?/?+1-678-954-0671 (direct)
Web:?http://www.evaristesys.com/, http://www.csrpswitch.com/
Sent?from?my?BlackBerry.
Dec. 8, 2015
Future of the Traditional PSTN vs VOIP and VoLTE
by peeip989@gmail.com
In this scenario:
NANPA -> Level3 -> reseller A -> reseller B -> reseller C -> end-user
Only reseller C and the end user knows where the chain ends. So, what about some OSPF-like mechanism? Let's say that in this scenario Level3 has direct connections with both resellers A and C. It would know that it has two paths to C (the terminating switch) but would prefer the direct link to C unless it became unavailable.
> On Dec 7, 2015, at 21:09, Peter Beckman <beckman at angryox.com> wrote:
>
> NANPA -> Level3 -> reseller A -> reseller B -> reseller C -> end-user
Dec. 8, 2015
Future of the Traditional PSTN vs VOIP and VoLTE
by beckman@angryox.com
And who has the rights to announce?
With IP, you are disincentivized from having all the traffic flow through
one's network if it can be avoided, because that is additional cost that
the customer doesn't want to pay and additional overhead and management for
the IP provider. So they say "hey, this is our IP space, but we will
delegate it to you and you can announce it to the Internet" and that way
the traffic goes a hopefully more direct and cost-controlled route.
With phone numbers, carriers get to charge a fee for the privilege of
having calls flow through their network. They've always gotten a fee. The
whole industry relies on that fee. And it is because they "own" the phone
numbers from the central authority, NANPA. And that central authority holds
the LRN database. Which is their carrier of record for a phone number. To
be the carrier of record, you have to be a CLEC or ILEC and "pay" to be
trusted by the central authority.
But in reality, the LRN database isn't the business that provides the
end-user service.
What we could do is simply create a numbering space that worked on existing
phones. What if we had a numbering system that enabled a device to have an
address that worked everywhere? Hmmm... don't we have that? IPv6? "500"
numbers? https://www.neustar.biz/blog/story-500-numbers
Alas... the carriers have control of this industry. They won't delegate
authority to their resellers because they would lose revenue, and they
already have the infrastructure to handle the traffic. We can try and build
a system to circumvent them, but it must automatically and
cryptographically ensure that the company that says "Send calls to this
number to this set of IP addresses" actually is responsible for the
end-user termination.
And since any customer in the chain can perform such a registration, with
no real automated way to determine hierarchy, the system will be flawed.
NANPA -> Level3 -> reseller A -> reseller B -> reseller C -> end-user
Level3 could say "Send calls to me!" with this system
Reseller A, B, or C (or all three!) could say "Send calls to me!"
A sophisticated end-user could say "Send calls to me!"
But unless we know that hierarchy above, who is right? Which company cuts
out the most middle-men? And I'm pretty sure that any reseller chain would
require the participation of all resellers, and frankly, they EACH get a
tenth of a cent or more per minute, so WHY would they? And how would the
purchaser know or determine the reseller chain? Most companies do not
disclose their ULCs.
Plus if any of the resellers offer value-add services to the receiver,
those are lost in this scenario. Though many of us may do all the value-add
on our ends, many do not.
But if we can figure it out, man will it make troubleshooting calls a lot
more simple (though simultaneously complicated because you have to call
someone else for each problematic call, but at least no more "we're waiting
on the ULC to respond").
Beckman
On Mon, 7 Dec 2015, Alex Balashov wrote:
> On 12/07/2015 04:42 PM, Peter Beckman wrote:
>
>> But this has a flaw. What if the reseller does this, and the reseller's
>> reseller does this. Who wins? As a reseller, I'd want the calls hitting me
>> first, so I can bill my reseller for minutes. But my reseller wants calls
>> going straight to them so they don't have to pay me for minutes.
>
> This would probably be fixable if all DIDs from ULCs were delegated out of
> larger blocks that fall on decimal boundaries, which would be analogous to an
> opaque BGP announcement of a shorter prefix by an upstream aggregator.
>
> But, because many numbers are ported in, this would be akin to announcing
> lots of /32s and, as you mentioned, without the critical component of
> physical connections constraining the routing topology.
>
> Any such scheme would have to incorporate the notion of a reseller chain into
> its mechanics and a security model that allows downstream resellers to modify
> the physical parameters of their receipt of the call but not the fundamental
> routing chain.
>
> -- Alex
>
> --
> Alex Balashov | Principal | Evariste Systems LLC
> 303 Perimeter Center North, Suite 300
> Atlanta, GA 30346
> United States
>
> Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
> Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
---------------------------------------------------------------------------
Peter Beckman Internet Guy
beckman at angryox.com http://www.angryox.com/
---------------------------------------------------------------------------
Dec. 8, 2015
Future of the Traditional PSTN vs VOIP and VoLTE
by abalashov@evaristesys.com
On 12/07/2015 02:22 PM, Jay R. Ashworth wrote:
> And no company is guaranteed the right to continue to make a living,
> by the law, in whatever field it is currently engaged in. Didn't a
> Supreme Court Justice say that in an opinion?
By that same token, though, there is some question as to whether
companies have an obligation to streamline or make maximally convenient
the process by which their competitors cannibalise their profit margins. :-)
Of course, we've all churned through the rationale here. Inasmuch as the
telecom majors take in billions in taxpayer subsidies of all sorts, they
are something tantamount to a public utility, they are - notionally -
required to open up their networks to uses we would otherwise expect
them to reject.
-- Alex
--
Alex Balashov | Principal | Evariste Systems LLC
303 Perimeter Center North, Suite 300
Atlanta, GA 30346
United States
Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
Dec. 8, 2015
Future of the Traditional PSTN vs VOIP and VoLTE
by peeip989@gmail.com
This is a really interesting idea, Mark. I only have a high-level understanding of Bitcoin but it definitely seems very similar to what we're talking about as for number ownership. It doesn't completely answer the trust question but there's definitely something here...
On Dec 7, 2015, at 16:54, Mark R Lindsey <lindsey at e-c-group.com> wrote:
The ownership of phone numbers can be published in a bitcoin-style Blockchain (a la Bitcoin, but not necessarily using the same chain). This way everybody can confirm who has rights to use the number, and no central authority "e164.arpa" needs to be trusted.
In addition to publishing the "owner" of an E.164 number, we could also publish the authorized parties for routing to that owner, and for routing from that owner. (A bit like MX and SPF DNS records.)
For example, I might say that I'll be routing calls from my +1-229-316-0013 number outbound through Level(3) and Bandwidth, but that Bandwidth is the only legitimate path to send calls to +1-229-316-0013.
> On Dec 7, 2015, at 16:42 , Peter Beckman <beckman at angryox.com> wrote:
>
> BGP relies on physical interconnections that have large contracts behind
> them. You don't just get a full BGP feed from your upstream and they accept
> all your announcements blindly.
>
> You can broadcast to your upstream that you are a route for all IPs in
> AS701, but if you are directly connected to me and I only gave you a single
> Class C , that doesn't make sense, so I'll blackhole your announcement
> because "I know better." At least the good ISPs do that. And when they
> don't, AS701 says "hey we didn't do that fix it now" and AS701 shuts down
> interconnects, it gets fixed quickly.
>
> Phone numbers and phone calls are an entirely different realm.
>
> Who owns the phone number? Who is allowed to publish that "Hey send calls
> to this number directly here!" Level3? Their reseller? Their reseller's
> reseller? Who's right if there are conflicting announcements? How do you
> make sure that the route that is correct today is correct tomorrow? Do you
> verify with an automated phone call? [1]
>
> Now Level3 could publish a record that says "Ask the reseller for where to
> send calls." And the reseller could publish a record that says "Ask OUR
> reseller where to send calls." But they won't because that would rob them
> of billable inbound minutes and potentially outbound minutes.
>
> You think fraudulent number ports and snapbacks are a pain...
>
> How do I know I can trust people in the group? What if we let someone in
> and then they publish a bunch of records and they are valid today but it
> was part of a mass port out tomorrow, and now some "cooperative group" is
> sending all the calls to this person but they no longer "own" the numbers.
>
> If this is to be done successfully, it must be done without trust.
>
> Beckman
>
> [1] I have some ideas here. You make an API call to "the cooperative
> group." They tell you a phone call will come to you from CallerID X to
> Phone Number Y to verify that you are in the series of hops when terminated
> through the PSTN to verify that you would get the call. If it succeeds,
> your record is published (or continues to be published) by the group, for
> group consumption for routing.
>
> But this has a flaw. What if the reseller does this, and the reseller's
> reseller does this. Who wins? As a reseller, I'd want the calls hitting me
> first, so I can bill my reseller for minutes. But my reseller wants calls
> going straight to them so they don't have to pay me for minutes.
>
>
>
>
>
>
>
>
>
>> On Mon, 7 Dec 2015, Pete E wrote:
>>
>> These are the crux of the issue. If there were a cooperative group willing
>> to peer to circumvent the PSTN, and if the group were large enough, then it
>> could offer *some* competitive pressure to get the ILEC's to change. In
>> fairness, Verizon and AT&T have been petitioning and hit some roadblocks by
>> the FCC to retire their legacy networks. Some of these concerns are legit,
>> some are not. Now, I'm not naive enough to believe these petitions are for
>> the good of the consumer or for anyone other than Verizon and AT&T. But
>> technologically, it's a step in the right direction.
>>
>> But for the signaling issue mentioned above, there could potentially be a
>> new DNS record type created which defines accepted signaling.
>>
>> Trust is a whole different problem. Without a central authority, it could
>> be chaotic and really difficult to manage. But I think the BGP analogy is a
>> good one. If there could be a method of passing info and then either
>> allowing or blocking it would be ideal, but it is a really big shift in
>> VoIP security, as was pointed out.
>>
>> That said, anyone interested in setting up a lab environment to hash this
>> out?
>>
>>> On Sat, Dec 5, 2015 at 5:19 PM, Paul Timmins <paul at timmins.net> wrote:
>>>
>>> Ah, but how would you know what IPs your inbound call should be trusted
>>> from for your SBCs? It's hard enough to get people properly interopped when
>>> the calling activity is planned, let alone have random endpoints hit your
>>> network. Are they going to use E.164? Should they send npdi/rn data? Should
>>> you trust the calling party information being sent? How do you know the
>>> original caller is even a legitimate telco and not some telemarketer going
>>> on a rampage connecting directly with everything? If you are getting
>>> problematic (abusive, illegal) inbound calls, how do you look up that IP to
>>> know who to complain about? Is WHOIS enough?
>>>
>>> -Paul
>>>
>>>
>>> On Dec 5, 2015, at 15:14, Erik Flournoy <erik at eespro.com> wrote:
>>>
>>> Additionally to come to Neustar NPAC extremely LATE proposal rescue of
>>> using the IP and SMS fields in the NPAC to packet route calls instead of
>>> via the TDM/SS7 Path that would kinda remove IQ from the path and allow
>>> carriers to directly connect via packets. Put the call on the IP packet
>>> path if it's voice and use TDM only for faxing which I wish would disappear
>>> for goodness sakes.
>>>
>>> On Sat, Dec 5, 2015 at 12:09 PM, Alex Balashov <abalashov at evaristesys.com>
>>> wrote:
>>>
>>>> On 12/05/2015 05:05 PM, Erik Flournoy wrote:
>>>>
>>>> If a packet transverses your entire network as a packet then it's never
>>>>> a toll charge. It's a packet.
>>>>
>>>> Well, right. :-) No provider of voice networks wants value-added services
>>>> to go away and be replaced by OTT applications for whom they're just a
>>>> low-margin, flat-rate, 95% percentile-billed transport layer.
>>>>
>>>> To a point, you can understand where they're coming from. They do the
>>>> hard, capital-intensive work of building out the network, while some clever
>>>> mobile app out of Silicon Valley pockets all the profits. That wasn't the
>>>> assumption from which they built anything.
>>>>
>>>>
>>>> --
>>>> Alex Balashov | Principal | Evariste Systems LLC
>>>> 303 Perimeter Center North, Suite 300
>>>> Atlanta, GA 30346
>>>> United States
>>>>
>>>> Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
>>>> Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
>>>> _______________________________________________
>>>> VoiceOps mailing list
>>>> VoiceOps at voiceops.org
>>>> https://puck.nether.net/mailman/listinfo/voiceops
>>>
>>> _______________________________________________
>>> VoiceOps mailing list
>>> VoiceOps at voiceops.org
>>> https://puck.nether.net/mailman/listinfo/voiceops
>>>
>>>
>>>
>>> _______________________________________________
>>> VoiceOps mailing list
>>> VoiceOps at voiceops.org
>>> https://puck.nether.net/mailman/listinfo/voiceops
>
> ---------------------------------------------------------------------------
> Peter Beckman Internet Guy
> beckman at angryox.com http://www.angryox.com/
> ---------------------------------------------------------------------------_______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
Dec. 7, 2015
Reliable Virtual Fax Provider Wholesale
by beckman@angryox.com
I'm looking for recommendations for a Virtual Fax Wholesale provider who
owns their own systems (not a reseller of someone else's service), is
reliable, responsive and smashingly brilliant, and has an API so I can
resell their services. And has a pay-per-page model, not a X number of
pages included per month.
Beckman
---------------------------------------------------------------------------
Peter Beckman Internet Guy
beckman at angryox.com http://www.angryox.com/
---------------------------------------------------------------------------
Dec. 7, 2015
Future of the Traditional PSTN vs VOIP and VoLTE
by abalashov@evaristesys.com
On 12/07/2015 04:42 PM, Peter Beckman wrote:
> But this has a flaw. What if the reseller does this, and the reseller's
> reseller does this. Who wins? As a reseller, I'd want the calls hitting me
> first, so I can bill my reseller for minutes. But my reseller wants calls
> going straight to them so they don't have to pay me for minutes.
This would probably be fixable if all DIDs from ULCs were delegated out
of larger blocks that fall on decimal boundaries, which would be
analogous to an opaque BGP announcement of a shorter prefix by an
upstream aggregator.
But, because many numbers are ported in, this would be akin to
announcing lots of /32s and, as you mentioned, without the critical
component of physical connections constraining the routing topology.
Any such scheme would have to incorporate the notion of a reseller chain
into its mechanics and a security model that allows downstream resellers
to modify the physical parameters of their receipt of the call but not
the fundamental routing chain.
-- Alex
--
Alex Balashov | Principal | Evariste Systems LLC
303 Perimeter Center North, Suite 300
Atlanta, GA 30346
United States
Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
Dec. 7, 2015
Future of the Traditional PSTN vs VOIP and VoLTE
by lindsey@e-c-group.com
The ownership of phone numbers can be published in a bitcoin-style Blockchain (a la Bitcoin, but not necessarily using the same chain). This way everybody can confirm who has rights to use the number, and no central authority "e164.arpa" needs to be trusted.
In addition to publishing the "owner" of an E.164 number, we could also publish the authorized parties for routing to that owner, and for routing from that owner. (A bit like MX and SPF DNS records.)
For example, I might say that I'll be routing calls from my +1-229-316-0013 number outbound through Level(3) and Bandwidth, but that Bandwidth is the only legitimate path to send calls to +1-229-316-0013.
> On Dec 7, 2015, at 16:42 , Peter Beckman <beckman at angryox.com> wrote:
>
> BGP relies on physical interconnections that have large contracts behind
> them. You don't just get a full BGP feed from your upstream and they accept
> all your announcements blindly.
>
> You can broadcast to your upstream that you are a route for all IPs in
> AS701, but if you are directly connected to me and I only gave you a single
> Class C , that doesn't make sense, so I'll blackhole your announcement
> because "I know better." At least the good ISPs do that. And when they
> don't, AS701 says "hey we didn't do that fix it now" and AS701 shuts down
> interconnects, it gets fixed quickly.
>
> Phone numbers and phone calls are an entirely different realm.
>
> Who owns the phone number? Who is allowed to publish that "Hey send calls
> to this number directly here!" Level3? Their reseller? Their reseller's
> reseller? Who's right if there are conflicting announcements? How do you
> make sure that the route that is correct today is correct tomorrow? Do you
> verify with an automated phone call? [1]
>
> Now Level3 could publish a record that says "Ask the reseller for where to
> send calls." And the reseller could publish a record that says "Ask OUR
> reseller where to send calls." But they won't because that would rob them
> of billable inbound minutes and potentially outbound minutes.
>
> You think fraudulent number ports and snapbacks are a pain...
>
> How do I know I can trust people in the group? What if we let someone in
> and then they publish a bunch of records and they are valid today but it
> was part of a mass port out tomorrow, and now some "cooperative group" is
> sending all the calls to this person but they no longer "own" the numbers.
>
> If this is to be done successfully, it must be done without trust.
>
> Beckman
>
> [1] I have some ideas here. You make an API call to "the cooperative
> group." They tell you a phone call will come to you from CallerID X to
> Phone Number Y to verify that you are in the series of hops when terminated
> through the PSTN to verify that you would get the call. If it succeeds,
> your record is published (or continues to be published) by the group, for
> group consumption for routing.
>
> But this has a flaw. What if the reseller does this, and the reseller's
> reseller does this. Who wins? As a reseller, I'd want the calls hitting me
> first, so I can bill my reseller for minutes. But my reseller wants calls
> going straight to them so they don't have to pay me for minutes.
>
>
>
>
>
>
>
>
>
> On Mon, 7 Dec 2015, Pete E wrote:
>
>> These are the crux of the issue. If there were a cooperative group willing
>> to peer to circumvent the PSTN, and if the group were large enough, then it
>> could offer *some* competitive pressure to get the ILEC's to change. In
>> fairness, Verizon and AT&T have been petitioning and hit some roadblocks by
>> the FCC to retire their legacy networks. Some of these concerns are legit,
>> some are not. Now, I'm not naive enough to believe these petitions are for
>> the good of the consumer or for anyone other than Verizon and AT&T. But
>> technologically, it's a step in the right direction.
>>
>> But for the signaling issue mentioned above, there could potentially be a
>> new DNS record type created which defines accepted signaling.
>>
>> Trust is a whole different problem. Without a central authority, it could
>> be chaotic and really difficult to manage. But I think the BGP analogy is a
>> good one. If there could be a method of passing info and then either
>> allowing or blocking it would be ideal, but it is a really big shift in
>> VoIP security, as was pointed out.
>>
>> That said, anyone interested in setting up a lab environment to hash this
>> out?
>>
>> On Sat, Dec 5, 2015 at 5:19 PM, Paul Timmins <paul at timmins.net> wrote:
>>
>>> Ah, but how would you know what IPs your inbound call should be trusted
>>> from for your SBCs? It's hard enough to get people properly interopped when
>>> the calling activity is planned, let alone have random endpoints hit your
>>> network. Are they going to use E.164? Should they send npdi/rn data? Should
>>> you trust the calling party information being sent? How do you know the
>>> original caller is even a legitimate telco and not some telemarketer going
>>> on a rampage connecting directly with everything? If you are getting
>>> problematic (abusive, illegal) inbound calls, how do you look up that IP to
>>> know who to complain about? Is WHOIS enough?
>>>
>>> -Paul
>>>
>>>
>>> On Dec 5, 2015, at 15:14, Erik Flournoy <erik at eespro.com> wrote:
>>>
>>> Additionally to come to Neustar NPAC extremely LATE proposal rescue of
>>> using the IP and SMS fields in the NPAC to packet route calls instead of
>>> via the TDM/SS7 Path that would kinda remove IQ from the path and allow
>>> carriers to directly connect via packets. Put the call on the IP packet
>>> path if it's voice and use TDM only for faxing which I wish would disappear
>>> for goodness sakes.
>>>
>>> On Sat, Dec 5, 2015 at 12:09 PM, Alex Balashov <abalashov at evaristesys.com>
>>> wrote:
>>>
>>>> On 12/05/2015 05:05 PM, Erik Flournoy wrote:
>>>>
>>>> If a packet transverses your entire network as a packet then it's never
>>>>> a toll charge. It's a packet.
>>>>>
>>>>
>>>> Well, right. :-) No provider of voice networks wants value-added services
>>>> to go away and be replaced by OTT applications for whom they're just a
>>>> low-margin, flat-rate, 95% percentile-billed transport layer.
>>>>
>>>> To a point, you can understand where they're coming from. They do the
>>>> hard, capital-intensive work of building out the network, while some clever
>>>> mobile app out of Silicon Valley pockets all the profits. That wasn't the
>>>> assumption from which they built anything.
>>>>
>>>>
>>>> --
>>>> Alex Balashov | Principal | Evariste Systems LLC
>>>> 303 Perimeter Center North, Suite 300
>>>> Atlanta, GA 30346
>>>> United States
>>>>
>>>> Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
>>>> Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
>>>> _______________________________________________
>>>> VoiceOps mailing list
>>>> VoiceOps at voiceops.org
>>>> https://puck.nether.net/mailman/listinfo/voiceops
>>>>
>>>
>>> _______________________________________________
>>> VoiceOps mailing list
>>> VoiceOps at voiceops.org
>>> https://puck.nether.net/mailman/listinfo/voiceops
>>>
>>>
>>>
>>> _______________________________________________
>>> VoiceOps mailing list
>>> VoiceOps at voiceops.org
>>> https://puck.nether.net/mailman/listinfo/voiceops
>>>
>>>
>>
>
> ---------------------------------------------------------------------------
> Peter Beckman Internet Guy
> beckman at angryox.com http://www.angryox.com/
> ---------------------------------------------------------------------------_______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
Dec. 7, 2015
Future of the Traditional PSTN vs VOIP and VoLTE
by beckman@angryox.com
BGP relies on physical interconnections that have large contracts behind
them. You don't just get a full BGP feed from your upstream and they accept
all your announcements blindly.
You can broadcast to your upstream that you are a route for all IPs in
AS701, but if you are directly connected to me and I only gave you a single
Class C , that doesn't make sense, so I'll blackhole your announcement
because "I know better." At least the good ISPs do that. And when they
don't, AS701 says "hey we didn't do that fix it now" and AS701 shuts down
interconnects, it gets fixed quickly.
Phone numbers and phone calls are an entirely different realm.
Who owns the phone number? Who is allowed to publish that "Hey send calls
to this number directly here!" Level3? Their reseller? Their reseller's
reseller? Who's right if there are conflicting announcements? How do you
make sure that the route that is correct today is correct tomorrow? Do you
verify with an automated phone call? [1]
Now Level3 could publish a record that says "Ask the reseller for where to
send calls." And the reseller could publish a record that says "Ask OUR
reseller where to send calls." But they won't because that would rob them
of billable inbound minutes and potentially outbound minutes.
You think fraudulent number ports and snapbacks are a pain...
How do I know I can trust people in the group? What if we let someone in
and then they publish a bunch of records and they are valid today but it
was part of a mass port out tomorrow, and now some "cooperative group" is
sending all the calls to this person but they no longer "own" the numbers.
If this is to be done successfully, it must be done without trust.
Beckman
[1] I have some ideas here. You make an API call to "the cooperative
group." They tell you a phone call will come to you from CallerID X to
Phone Number Y to verify that you are in the series of hops when terminated
through the PSTN to verify that you would get the call. If it succeeds,
your record is published (or continues to be published) by the group, for
group consumption for routing.
But this has a flaw. What if the reseller does this, and the reseller's
reseller does this. Who wins? As a reseller, I'd want the calls hitting me
first, so I can bill my reseller for minutes. But my reseller wants calls
going straight to them so they don't have to pay me for minutes.
On Mon, 7 Dec 2015, Pete E wrote:
> These are the crux of the issue. If there were a cooperative group willing
> to peer to circumvent the PSTN, and if the group were large enough, then it
> could offer *some* competitive pressure to get the ILEC's to change. In
> fairness, Verizon and AT&T have been petitioning and hit some roadblocks by
> the FCC to retire their legacy networks. Some of these concerns are legit,
> some are not. Now, I'm not naive enough to believe these petitions are for
> the good of the consumer or for anyone other than Verizon and AT&T. But
> technologically, it's a step in the right direction.
>
> But for the signaling issue mentioned above, there could potentially be a
> new DNS record type created which defines accepted signaling.
>
> Trust is a whole different problem. Without a central authority, it could
> be chaotic and really difficult to manage. But I think the BGP analogy is a
> good one. If there could be a method of passing info and then either
> allowing or blocking it would be ideal, but it is a really big shift in
> VoIP security, as was pointed out.
>
> That said, anyone interested in setting up a lab environment to hash this
> out?
>
> On Sat, Dec 5, 2015 at 5:19 PM, Paul Timmins <paul at timmins.net> wrote:
>
>> Ah, but how would you know what IPs your inbound call should be trusted
>> from for your SBCs? It's hard enough to get people properly interopped when
>> the calling activity is planned, let alone have random endpoints hit your
>> network. Are they going to use E.164? Should they send npdi/rn data? Should
>> you trust the calling party information being sent? How do you know the
>> original caller is even a legitimate telco and not some telemarketer going
>> on a rampage connecting directly with everything? If you are getting
>> problematic (abusive, illegal) inbound calls, how do you look up that IP to
>> know who to complain about? Is WHOIS enough?
>>
>> -Paul
>>
>>
>> On Dec 5, 2015, at 15:14, Erik Flournoy <erik at eespro.com> wrote:
>>
>> Additionally to come to Neustar NPAC extremely LATE proposal rescue of
>> using the IP and SMS fields in the NPAC to packet route calls instead of
>> via the TDM/SS7 Path that would kinda remove IQ from the path and allow
>> carriers to directly connect via packets. Put the call on the IP packet
>> path if it's voice and use TDM only for faxing which I wish would disappear
>> for goodness sakes.
>>
>> On Sat, Dec 5, 2015 at 12:09 PM, Alex Balashov <abalashov at evaristesys.com>
>> wrote:
>>
>>> On 12/05/2015 05:05 PM, Erik Flournoy wrote:
>>>
>>> If a packet transverses your entire network as a packet then it's never
>>>> a toll charge. It's a packet.
>>>>
>>>
>>> Well, right. :-) No provider of voice networks wants value-added services
>>> to go away and be replaced by OTT applications for whom they're just a
>>> low-margin, flat-rate, 95% percentile-billed transport layer.
>>>
>>> To a point, you can understand where they're coming from. They do the
>>> hard, capital-intensive work of building out the network, while some clever
>>> mobile app out of Silicon Valley pockets all the profits. That wasn't the
>>> assumption from which they built anything.
>>>
>>>
>>> --
>>> Alex Balashov | Principal | Evariste Systems LLC
>>> 303 Perimeter Center North, Suite 300
>>> Atlanta, GA 30346
>>> United States
>>>
>>> Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
>>> Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
>>> _______________________________________________
>>> VoiceOps mailing list
>>> VoiceOps at voiceops.org
>>> https://puck.nether.net/mailman/listinfo/voiceops
>>>
>>
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>>
>>
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>>
>
---------------------------------------------------------------------------
Peter Beckman Internet Guy
beckman at angryox.com http://www.angryox.com/
---------------------------------------------------------------------------
Dec. 7, 2015
Future of the Traditional PSTN vs VOIP and VoLTE
by erik@eespro.com
Pete
Count me in for testing and development.
On Dec 7, 2015 7:01 AM, "Pete E" <peeip989 at gmail.com> wrote:
> These are the crux of the issue. If there were a cooperative group willing
> to peer to circumvent the PSTN, and if the group were large enough, then it
> could offer *some* competitive pressure to get the ILEC's to change. In
> fairness, Verizon and AT&T have been petitioning and hit some roadblocks by
> the FCC to retire their legacy networks. Some of these concerns are legit,
> some are not. Now, I'm not naive enough to believe these petitions are for
> the good of the consumer or for anyone other than Verizon and AT&T. But
> technologically, it's a step in the right direction.
>
> But for the signaling issue mentioned above, there could potentially be a
> new DNS record type created which defines accepted signaling.
>
> Trust is a whole different problem. Without a central authority, it could
> be chaotic and really difficult to manage. But I think the BGP analogy is a
> good one. If there could be a method of passing info and then either
> allowing or blocking it would be ideal, but it is a really big shift in
> VoIP security, as was pointed out.
>
> That said, anyone interested in setting up a lab environment to hash this
> out?
>
> On Sat, Dec 5, 2015 at 5:19 PM, Paul Timmins <paul at timmins.net> wrote:
>
>> Ah, but how would you know what IPs your inbound call should be trusted
>> from for your SBCs? It's hard enough to get people properly interopped when
>> the calling activity is planned, let alone have random endpoints hit your
>> network. Are they going to use E.164? Should they send npdi/rn data? Should
>> you trust the calling party information being sent? How do you know the
>> original caller is even a legitimate telco and not some telemarketer going
>> on a rampage connecting directly with everything? If you are getting
>> problematic (abusive, illegal) inbound calls, how do you look up that IP to
>> know who to complain about? Is WHOIS enough?
>>
>> -Paul
>>
>>
>> On Dec 5, 2015, at 15:14, Erik Flournoy <erik at eespro.com> wrote:
>>
>> Additionally to come to Neustar NPAC extremely LATE proposal rescue of
>> using the IP and SMS fields in the NPAC to packet route calls instead of
>> via the TDM/SS7 Path that would kinda remove IQ from the path and allow
>> carriers to directly connect via packets. Put the call on the IP packet
>> path if it's voice and use TDM only for faxing which I wish would disappear
>> for goodness sakes.
>>
>> On Sat, Dec 5, 2015 at 12:09 PM, Alex Balashov <abalashov at evaristesys.com
>> > wrote:
>>
>>> On 12/05/2015 05:05 PM, Erik Flournoy wrote:
>>>
>>> If a packet transverses your entire network as a packet then it's never
>>>> a toll charge. It's a packet.
>>>>
>>>
>>> Well, right. :-) No provider of voice networks wants value-added
>>> services to go away and be replaced by OTT applications for whom they're
>>> just a low-margin, flat-rate, 95% percentile-billed transport layer.
>>>
>>> To a point, you can understand where they're coming from. They do the
>>> hard, capital-intensive work of building out the network, while some clever
>>> mobile app out of Silicon Valley pockets all the profits. That wasn't the
>>> assumption from which they built anything.
>>>
>>>
>>> --
>>> Alex Balashov | Principal | Evariste Systems LLC
>>> 303 Perimeter Center North, Suite 300
>>> Atlanta, GA 30346
>>> United States
>>>
>>> Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
>>> Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
>>> _______________________________________________
>>> VoiceOps mailing list
>>> VoiceOps at voiceops.org
>>> https://puck.nether.net/mailman/listinfo/voiceops
>>>
>>
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>>
>>
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
Dec. 7, 2015