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 jra@baylink.com
----- Original Message -----
> From: "Mike Ray, MBA, CNE, CTE" <mike at astrocompanies.com>
> I think you may have missed the main point of the ILEC proposals to ?modernize?.
> They still propose, post-?modernization?, to force CLECs to interconnect with
> TDM facilities and SS7 at each tandem as they have to today. That?s a huge
> revenue stream and they?re not going to willingly give that up. Their
> ?modernization? proposal is simply ?We want to get rid of all UNEs? in
> disguise. It?s totally anti-competitive. AT&T simply wants to take that wire
> that?s in the ground today that must be made available for UNEs and divest that
> wire to one of its subsidiaries which is not an ILEC. They will use that
> existing copper to provide both legacy and next-gen services but since it is no
> longer owned by the ILEC it?s no longer subject to being used for UNEs by
> CLECs. Viola! Network modernized! The old monopoly is new again and they
> didn?t even have to invest in new infrastructure.
Roughly akin to what they were trying to do after Sandy in NY, shifting
customers from regulated copper to unreg subsidiary (read: FiOS) fiber, IIRC.
Luckily, a statistically significant number of customers told them to fold it
until it was all sharp corners, and shove it SO FAR UP their... er, what now?
Cheers,
-- jra
--
Jay R. Ashworth Baylink jra at baylink.com
Designer The Things I Think RFC 2100
Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII
St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274
Dec. 7, 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 my heart bleeds for them.
>
> But so has my wallet, for decades; they've gotten their ROI.
:-)
I didn't mean to legitimate their crying poor house. I was just
illuminating their reasoning for resisting OTT and commoditisation.
--
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 jra@baylink.com
----- Original Message -----
> From: "Alex Balashov" <abalashov at evaristesys.com>
> 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.
And my heart bleeds for them.
But so has my wallet, for decades; they've gotten their ROI.
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?
Cheers,
-- jra
--
Jay R. Ashworth Baylink jra at baylink.com
Designer The Things I Think RFC 2100
Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII
St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274
Dec. 7, 2015
Future of the Traditional PSTN vs VOIP and VoLTE
by marylou@backuptelecom.com
You only need look at what the UNE circuit IDs are to know how the ILECs feel
about them.......DS1s and DS3s both have FU in them! LOL!
iconectiv used to be Telcordia, which was originally BellCore. In the past
Telcordia only produced Telecom documentation, sold industry codes, and
adminstered the BIRRDS database, which is what they produce the LERG and TPM
reports from. Some of Telcordia's documentation like the ASOG, LSOG and NC/NCI
list were not that helpful in the last 20 years because many of the fields could
be changed by the carrier so every ILEC used them in a different way. When I
said the ILEC published these codes on their website. I didn't mean it was easy
to find! In my opinion, putting everything on the web but the kitchen sink and
having it accompanied with a horrible search engine was their way of making it
as hard as possible for the CLEC to operate. I happen to know where they hide
most things because I've worked in the industry 19 years and documented their
location as much as possible so I could help my clients. However, if you're new
to the arena and trying to figure it out on your own it would be near impossible
to get anything done.
That's interesting that Ericsson is going to be taking over porting. I wonder if
that means they are taking all the arms that NEUSTAR claims are separate
entities. I've always described NEUSTAR's entities as kissing cousins because
they are really just divisions who all share the same name in their e-mail
communications(neustar.net, neustar,biz, etc). Those divisons include NANPA, the
Pooling Administration, NPAC, and NECA. A year or so ago they bought out Targus
(who handled CNAM storage) and TNSI who is one of the two largest SS7 providers.
So I guess my question would be are they taking over ALL of NEUSTAR or just the
the NPAC portion?
Mary Lou Carey
BackUP Telecom Consulting
615-791-9969
> On December 7, 2015 at 11:06 AM Peter Beckman <beckman at angryox.com> wrote:
>
>
> I hadn't heard of Iconectiv (one "n") before. I found this:
>
> http://www.ericsson.com/news/150326-fcc-authorizes-local-number-portability…
>
> Was it Neustar prior to this change?
>
> I dream of a process for LNP that goes like this:
>
> 1. Customer goes to current carrier, requests a Porting Authorization
> Code for a number (or set of numbers), either online or over the phone.
>
> 2. Current carrier generates a Porting Authorization Code and provides
> it to the Customer.
>
> 3. Customer goes to new carrier, provides Phone Number, Current
> Carrier, and the Porting Authorization Code.
>
> 4. New carrier submits port request to Current Carrer with the Number
> and Porting Authorization Code. No name, billing address, PIN/SSN,
> just those three things.
>
> 5. Current carrier matches the Porting Authorization Code with their
> records for that Number and the port goes through.
>
> Since all of this is centralized, just have Iconectiv manage it -- the
> Current Carrier uses an API with Iconectiv to register the number and get a
> code back. The New Carrier uses the API with Iconectiv with the number and
> the code to verify porting. Codes expire after x days.
>
> Will Iconectiv bring this level of sanity to porting in the NANP? Or will
> it be more of the same, with rejections for an incorrect street abbreviation?
>
> I know it's more complicated than that to implement, but it really ticks me
> off how difficult it is to port numbers these days if you aren't a Tier 1
> wireless carrier.
>
> Beckman
>
> On Sat, 5 Dec 2015, Erik Flournoy wrote:
>
> > Aloha Group,
> >
> > I'm curious to know others thoughts on where they believe the traditional
> > PSTN is going vs VOIP and VoLTE. Now that Iconnectiv will be administering
> > the LNP in the US I feel as though it's the best time to try and propose
> > new or more up to date solutions that allow smaller carriers to operate.
> >
> > For example there is no charge to have the ability to port numbers in NPAC,
> > but there is a monthly charge for the remote access to the NPAC. Then the
> > interconnectivity at the LEC level. The archaic ways of telecom have not
> > seemed to change much although VOIP is now in my opinion the standard of
> > telecom. VOIP will soon be able to get code blocks and route via SIP vs SS7
> > and LERG. LERG, ASR/LSR, SS7 all systems owned by one monopolizing company.
>
> ---------------------------------------------------------------------------
> 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
Mary Lou Carey
BackUP Telecom Consulting
Marylou at backuptelecom.com
Office: 615-791-9969
Cell: 615-796-1111
Dec. 7, 2015
Future of the Traditional PSTN vs VOIP and VoLTE
by mike@astrocompanies.com
I think you may have missed the main point of the ILEC proposals to ?modernize?. They still propose, post-?modernization?, to force CLECs to interconnect with TDM facilities and SS7 at each tandem as they have to today. That?s a huge revenue stream and they?re not going to willingly give that up. Their ?modernization? proposal is simply ?We want to get rid of all UNEs? in disguise. It?s totally anti-competitive. AT&T simply wants to take that wire that?s in the ground today that must be made available for UNEs and divest that wire to one of its subsidiaries which is not an ILEC. They will use that existing copper to provide both legacy and next-gen services but since it is no longer owned by the ILEC it?s no longer subject to being used for UNEs by CLECs. Viola! Network modernized! The old monopoly is new again and they didn?t even have to invest in new infrastructure.
Today, both AT&T and Verizon are still claiming that they are not technically capable of interconnecting over IP.
In a recent proceeding that I was involved in
http://www.floridapsc.com/utilities/telecomm/naats/NAATS_results.aspx? <http://www.floridapsc.com/utilities/telecomm/naats/NAATS_results.aspx?&star…> &startDate=4/4/2014&endDate=5/4/2016&numCos=1&compcode1=TY058%20&agreementType=ARBITRATION
AT&T/Bellsouth claimed that it was ?impossible? for it to provide our dispute IDs to us when it issues billing in response to our valid billing disputes. ?Impossible?. It made many similar claims as well in this proceeding.
This is the same standard of ?impossible? that they claim about interconnecting over IP, even though it?s clear that AT&T has other subsidiaries that do it every day. They think they can define what terms mean, like ?impossible?.
Beware of any such proposals from the ILECs. That term ?modernization? as they use it doesn?t mean what you think it means.
Mike
Mike Ray, MBA, CNE, CTE
Astro Companies, LLC
11523 Palm Brush Trail #401
Lakewood Ranch, FL 34202
DIRECT: call or text 941 600-0207
http://www.astrocompanies.com
From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Pete E
Sent: Monday, December 7, 2015 12:01 PM
To: Paul Timmins <paul at timmins.net>
Cc: voiceops at voiceops.org
Subject: Re: [VoiceOps] Future of the Traditional PSTN vs VOIP and VoLTE
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 <mailto: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 <mailto: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 <mailto: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 <tel:%2B1-800-250-5920> (toll-free) / +1-678-954-0671 <tel:%2B1-678-954-0671> (direct)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops
Dec. 7, 2015
Future of the Traditional PSTN vs VOIP and VoLTE
by paul@timmins.net
Honestly, I think the proper balance here (my 2c) would be creating a
rolodex of properly maintained carrier contact information (with
controlled distribution) so we could reach out to carriers we exchange a
useful amount of traffic with, and working out privately the contortions
necessary to connect to each other over SIP, and deciding then to route
the intercarrier calls to each other over a private trunk group. My
switches look up the LRN, and I can add anything to the translations for
a particular LRN, including ISDN PRI, MF, SS7, or SIP. I can probably do
H.323 to a carrier but you'll never hear me admit that (ugh!).
We have all the parts we need to convert the PSTN to SIP already. We
don't need FCC permission to do this, we just need to take it upon
ourselves to reach out, exchange information, and set up our
interconnections accordingly.
The biggest concern for me would be keeping that rolodex out of the
hands of sales departments so I don't get endless calls offering me LD
termination, etc etc. Or looney end users complaining about spoofed
numbers or collections agencies calling them from our codes and making
legal threats that nobody but their pretend internet lawyers would take
as a case.
-Paul
On 12/07/2015 12:00 PM, 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
> <mailto: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
>> <mailto: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 <mailto: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 <tel:%2B1-800-250-5920> (toll-free) /
>> +1-678-954-0671 <tel:%2B1-678-954-0671> (direct)
>> Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>>
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
>> https://puck.nether.net/mailman/listinfo/voiceops
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
Dec. 7, 2015
Future of the Traditional PSTN vs VOIP and VoLTE
by paul@timmins.net
No, it won't. The rejections the other side provides are largely
optional, and in fact the FCC has issued strict guidance about the
necessary level of matching on an LSR (I want to say it's telephone
number, account number, PIN if applicable, and zipcode, but I know
there's some conditional variations on this).
Making the customer request a code from their losing carrier violates
(at least the spirit, if not the letter of) current regulations by
giving the current carrier a chance to market to an existing customer,
threaten them, or make them pay a fee or contract termination price up
front to get the code, or create undue levels of complexity on getting
the code.
Currently, you can create subscriptions against a number and force the
issue, porting the number under hostile conditions is in fact
technically possible (in fact, i've done it before, with a service
provider placing a large quantity of numbers in conflict over a
unrelated dispute, conflict expiration window can be your friend if you
use it carefully). The only person who can complain about it is the
customer themselves as long as the numbers are active, so if they're on
your side and you're certain the number is active, the losing carrier
has little recourse. Adding a step where your ability to port relies on
the good graces of the losing carrier is going to create a far worse
situation.
-Paul
On 12/07/2015 11:06 AM, Peter Beckman wrote:
> I hadn't heard of Iconectiv (one "n") before. I found this:
>
> http://www.ericsson.com/news/150326-fcc-authorizes-local-number-portability…
>
>
> Was it Neustar prior to this change?
>
> I dream of a process for LNP that goes like this:
>
> 1. Customer goes to current carrier, requests a Porting Authorization
> Code for a number (or set of numbers), either online or over
> the phone.
>
> 2. Current carrier generates a Porting Authorization Code and
> provides
> it to the Customer.
>
> 3. Customer goes to new carrier, provides Phone Number, Current
> Carrier, and the Porting Authorization Code.
>
> 4. New carrier submits port request to Current Carrer with the Number
> and Porting Authorization Code. No name, billing address, PIN/SSN,
> just those three things.
>
> 5. Current carrier matches the Porting Authorization Code with their
> records for that Number and the port goes through.
>
> Since all of this is centralized, just have Iconectiv manage it -- the
> Current Carrier uses an API with Iconectiv to register the number and
> get a
> code back. The New Carrier uses the API with Iconectiv with the number
> and
> the code to verify porting. Codes expire after x days.
>
> Will Iconectiv bring this level of sanity to porting in the NANP? Or will
> it be more of the same, with rejections for an incorrect street
> abbreviation?
>
> I know it's more complicated than that to implement, but it really
> ticks me
> off how difficult it is to port numbers these days if you aren't a Tier 1
> wireless carrier.
>
> Beckman
>
> On Sat, 5 Dec 2015, Erik Flournoy wrote:
>
>> Aloha Group,
>>
>> I'm curious to know others thoughts on where they believe the
>> traditional
>> PSTN is going vs VOIP and VoLTE. Now that Iconnectiv will be
>> administering
>> the LNP in the US I feel as though it's the best time to try and propose
>> new or more up to date solutions that allow smaller carriers to operate.
>>
>> For example there is no charge to have the ability to port numbers in
>> NPAC,
>> but there is a monthly charge for the remote access to the NPAC. Then
>> the
>> interconnectivity at the LEC level. The archaic ways of telecom have not
>> seemed to change much although VOIP is now in my opinion the standard of
>> telecom. VOIP will soon be able to get code blocks and route via SIP
>> vs SS7
>> and LERG. LERG, ASR/LSR, SS7 all systems owned by one monopolizing
>> company.
>
> ---------------------------------------------------------------------------
>
> 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 peeip989@gmail.com
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
>
>
Dec. 7, 2015
Future of the Traditional PSTN vs VOIP and VoLTE
by peeip989@gmail.com
Haha, that was a fun read! (and pretty accurate)
>>
> Technically, ILECs publish a lot of stuff publicly, to comply with the
> letter of regulations requiring them to do so. However, most of it is not
> digestible or usable to those who work outside the world of ILEC
> provisioning, so it has to be processed into commercial databases like the
> LERG and LCADS. The same mafia then charges for access to these, for
> reasons motivated by profit and creating systemic barriers to entry for
> small competitors.
>
> If anyone balks at the seemingly surreal cocktail of having to sell one's
> kidney for access to notionally public information, the ILECs can always
> say: "You can download the 90 page local tariff yourself right there from
> our web site, you just have to know where to look! The commercial databases
> are just adding value by composing it into readily machine-processable
> form!"
>
> This is one of the most common cop-outs of New Gilded Age sociopaths;
> "we're complying with the letter of the law, and we reserve the right to
> charge a reasonable fee for putting the information into a convenient form
> for you..." Except, there wouldn't be a need to take 90 pages of arcane
> prose and turn it into a few table rows of values if they did not
> themselves dictate the rules; there is no "value add" in the LERG because
> it is a response to a artificial contrivance, a purely invented problem of
> the ILECs' own deliberate making. It exploits information asymmetries and
> differences of power between big and small actors in the same way as
> pseudoscientific chemistry gibberish on early 20th century quack remedies,
> or the fine print on 264-page subprime mortgage issuance binders.
>
> I think that's really the essence of Erik's grievance, and it's a valid
> one. Sure, you can participate in the PSTN*.
>
> * Expensive semi-proprietary decoder ring and beaucoup bucks required.
>
> -- Alex
>
>
Dec. 7, 2015
Future of the Traditional PSTN vs VOIP and VoLTE
by abalashov@evaristesys.com
?No, Iconectiv is what Telcordia's called this week.
--
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. 7, 2015