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
- 14 participants
- 10512 messages
Mediant 3000 SIP-I
by admin@dc4.us
Does anyone know if the AudioCodes Mediant 3000 Media Gateway supports the SIP-I interworking of ISUP to SIP standard? (Q.1912.5?) Specifically with support for ANSI88 or ITU-92+?Asides from Telcobridges, Metaswitch, AudioCodes & Dialogic hardware does anyone have any cost effective SS7 capable Media Gateway recommendations that do SIP-I?The Dialogic IMG2020 looks like it would have been awesome but it looks to be discontinued if I am not mistaken.What about Cisco hardware? Did Cisco ever make carrier-grade media gateways with SIP-I support?Thanks,Dylan Cruz Livewire Telecom407-999-0000
Nov. 7, 2023
Sales contacts at Ribbon, Audiocodes
by ross@tajvar.io
Does anyone have sales contacts at Ribbon or Audiocodes (for SBCs) they
could share with me? I'm allergic to filling out "contact us" forms, and
apparently my old contacts have moved on.
Nov. 7, 2023
troubleshooting RTP loss - and does anyone use webair/opti9?
by anthony.caiozzo@telchemy.com
Mike - appreciate the pointer - seems very similar to Windows pathping.
It's also identical the methodology we leverage inside the DVQattest tool I
described earlier today - but instead we send RTP packets with decreasing
TTLs to effectively map out the exact path that the voice traffic took.
-anthony
-----Original Message-----
From: VoiceOps <voiceops-bounces at voiceops.org> On Behalf Of Mike Johnston
via VoiceOps
Sent: Monday, October 30, 2023 4:38 PM
To: Voiceops.org <voiceops at voiceops.org>
Subject: Re: [VoiceOps] troubleshooting RTP loss - and does anyone use
webair/opti9?
mtr
https://en.wikipedia.org/wiki/MTR_(software)
It isn't specific to VoIP. But it is still a very good first step in
troubleshooting which hop the packet loss begins at. Unlike the basic
traceroute tools that come with Linux or Windows, it can run continuously
for however long you need, even days. This can be especially useful if the
packet loss is intermittent.
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
Oct. 30, 2023
troubleshooting RTP loss - and does anyone use webair/opti9?
by mjohnston@wiktel.com
mtr
https://en.wikipedia.org/wiki/MTR_(software)
It isn't specific to VoIP. But it is still a very good first step in
troubleshooting which hop the packet loss begins at. Unlike the basic
traceroute tools that come with Linux or Windows, it can run
continuously for however long you need, even days. This can be
especially useful if the packet loss is intermittent.
Oct. 30, 2023
troubleshooting RTP loss - and does anyone use webair/opti9?
by twolf@wolftechgroup.com
AppNeta by Broadcom is an awesome tool and includes this type of troubleshooting
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-ma…
[cid:image001.jpg at 01DA0B40.4D766C30]
From: VoiceOps <voiceops-bounces at voiceops.org> On Behalf Of Izzy Goldstein - TeleGo via VoiceOps
Sent: Monday, October 30, 2023 2:06 PM
To: Voiceops.org <voiceops at voiceops.org>
Subject: [VoiceOps] troubleshooting RTP loss - and does anyone use webair/opti9?
HI team
we recently noticed packet loss happening every morning from 6AM to 11AM, our MOS drops during that time
our datacenter in garden City Long island (formerly Webair / now Opti9) claims it is outside of their network and can't do anything - but they have been unable to identify where the loss is occurring
so i have 2 questions
1)
Is there anyone in this group using the same datacenter, and if so, do you have any RTP issues ?
maybe the issue is with one of our SIP providers, etc and not the Datacenter directly
2)
What's a good tool / method to determine where the packet loss is happening ?
i am using VoipMonitor - but willing to start using other tools to find the root cause
--
Izzy Goldstein
Chief Technology Officer - DevOps Master
Main: (212) 477-1000 x 2085<tel:(212)%20477-1000>
Direct: (929) 477-2085<tel:(929)%20477-2085>
Website: https://telego.com/
[https://telego.com/wp-content/uploads/telego-signature-logo.png]
Confidentiality Notice: This e-mail may contain confidential and/or privileged information. If you are not the intended recipient or have received this e-mail in error please notify us immediately by email reply and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of TeleGo (T). Employees of TeleGo are expressly required not to make defamatory statements and not to infringe or authorize any infringement of copyright or any other legal right by email communications. Any such communication is contrary to TeleGo policy and outside the scope of the employment of the individual concerned. TeleGo will not accept any liability in respect of such communication, and the employee responsible will be personally liable for any damages or other liability arising.
TeleGo Hosted PBX<https://youtu.be/DaT8YAZ4V0w>
Oct. 30, 2023
troubleshooting RTP loss - and does anyone use webair/opti9?
by neimanpinchas@gmail.com
Not too experienced, but my 2 cents
If it's based on a faulty router.
do a traceroute in the morning and in the afternoon a few days maybe you
will find a correlation to a specific route.
In morning hours try to ping every hop from the traceroute with BIG
packets so you could find how far you can get without packet loss.
the latter will also help If it is based on congestion
On Mon, Oct 30, 2023 at 2:07?PM Izzy Goldstein - TeleGo via VoiceOps <
voiceops at voiceops.org> wrote:
> HI team
>
> we recently noticed packet loss happening every morning from 6AM to 11AM,
> our MOS drops during that time
> our datacenter in garden City Long island (formerly Webair / now Opti9)
> claims it is outside of their network and can't do anything - but they have
> been unable to identify where the loss is occurring
>
> so i have 2 questions
>
> 1)
> Is there anyone in this group using the same datacenter, and if so, do you
> have any RTP issues ?
> maybe the issue is with one of our SIP providers, etc and not the
> Datacenter directly
>
> 2)
> What's a good tool / method to determine where the packet loss is
> happening ?
>
> i am using VoipMonitor - but willing to start using other tools to find
> the root cause
>
>
> --
>
> Izzy Goldstein
>
> Chief Technology Officer - DevOps Master
>
> Main: (212) 477-1000 x 2085 <(212)%20477-1000>
>
> Direct: (929) 477-2085
>
> Website: https://telego.com/
>
>
>
>
> Confidentiality Notice: This e-mail may contain confidential and/or
> privileged information. If you are not the intended recipient or have
> received this e-mail in error please notify us immediately by email reply
> and destroy this e-mail. Any unauthorized copying, disclosure or
> distribution of the material in this e-mail is strictly forbidden. Any
> views or opinions presented in this email are solely those of the author
> and do not necessarily represent those of TeleGo (T). Employees of TeleGo
> are expressly required not to make defamatory statements and not to
> infringe or authorize any infringement of copyright or any other legal
> right by email communications. Any such communication is contrary to TeleGo
> policy and outside the scope of the employment of the individual concerned.
> TeleGo will not accept any liability in respect of such communication, and
> the employee responsible will be personally liable for any damages or other
> liability arising.
>
>
> TeleGo Hosted PBX <https://youtu.be/DaT8YAZ4V0w>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
--
*Pinchas S. Neiman*
Software Engineer At ESEQ Technology Corp.
845.213.1229 #2
Oct. 30, 2023
troubleshooting RTP loss - and does anyone use webair/opti9?
by anthony.caiozzo@telchemy.com
Izzy ? feel your pain ? this is exactly why we built out our active testing capabilities so we can point you exactly @ where this degradation is occurring.
SQmediator / DVQattest creates synthetic traffic that emulates voice as well as video transactions and supports a wide range of traditional and modern day codecs. It emulates the adaptive codecs used by webRTC as well as SILK, SATIN and many others. The platform enables one to test fully end-to-end ? plus you can deploy ?hub? agents in the core that can respond to multiple incoming call requests from edge agents to create a variety of deployment configurations.
More info available @ www.telchemy.com/sqmediator.php.
Will follow up with you directly to dig deeper ? but responded here as well in case anyone else on the list can leverage this info and benefit from this diagnostic functionality.
-anthony
Anthony Caiozzo | 617-312-5189
Support: 678-387-3000 or <http://www.telchemy.com/custportal> www.telchemy.com/custportal to open a ticket
From: VoiceOps <voiceops-bounces at voiceops.org> On Behalf Of Izzy Goldstein - TeleGo via VoiceOps
Sent: Monday, October 30, 2023 2:06 PM
To: Voiceops.org <voiceops at voiceops.org>
Subject: [VoiceOps] troubleshooting RTP loss - and does anyone use webair/opti9?
HI team
we recently noticed packet loss happening every morning from 6AM to 11AM, our MOS drops during that time
our datacenter in garden City Long island (formerly Webair / now Opti9) claims it is outside of their network and can't do anything - but they have been unable to identify where the loss is occurring
so i have 2 questions
1)
Is there anyone in this group using the same datacenter, and if so, do you have any RTP issues ?
maybe the issue is with one of our SIP providers, etc and not the Datacenter directly
2)
What's a good tool / method to determine where the packet loss is happening ?
i am using VoipMonitor - but willing to start using other tools to find the root cause
--
Izzy Goldstein
Chief Technology Officer - DevOps Master
Main: <tel:(212)%20477-1000> (212) 477-1000 x 2085
Direct: <tel:(929)%20477-2085> (929) 477-2085
Website: <https://telego.com/> https://telego.com/
<https://telego.com/wp-content/uploads/telego-signature-logo.png>
Confidentiality Notice: This e-mail may contain confidential and/or privileged information. If you are not the intended recipient or have received this e-mail in error please notify us immediately by email reply and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of TeleGo (T). Employees of TeleGo are expressly required not to make defamatory statements and not to infringe or authorize any infringement of copyright or any other legal right by email communications. Any such communication is contrary to TeleGo policy and outside the scope of the employment of the individual concerned. TeleGo will not accept any liability in respect of such communication, and the employee responsible will be personally liable for any damages or other liability arising.
<https://youtu.be/DaT8YAZ4V0w> TeleGo Hosted PBX
Oct. 30, 2023
troubleshooting RTP loss - and does anyone use webair/opti9?
by igoldstein@telego.net
HI team
we recently noticed packet loss happening every morning from 6AM to 11AM,
our MOS drops during that time
our datacenter in garden City Long island (formerly Webair / now Opti9)
claims it is outside of their network and can't do anything - but they have
been unable to identify where the loss is occurring
so i have 2 questions
1)
Is there anyone in this group using the same datacenter, and if so, do you
have any RTP issues ?
maybe the issue is with one of our SIP providers, etc and not the
Datacenter directly
2)
What's a good tool / method to determine where the packet loss is happening
?
i am using VoipMonitor - but willing to start using other tools to find the
root cause
--
Izzy Goldstein
Chief Technology Officer - DevOps Master
Main: (212) 477-1000 x 2085 <(212)%20477-1000>
Direct: (929) 477-2085
Website: https://telego.com/
Confidentiality Notice: This e-mail may contain confidential and/or
privileged information. If you are not the intended recipient or have
received this e-mail in error please notify us immediately by email reply
and destroy this e-mail. Any unauthorized copying, disclosure or
distribution of the material in this e-mail is strictly forbidden. Any
views or opinions presented in this email are solely those of the author
and do not necessarily represent those of TeleGo (T). Employees of TeleGo
are expressly required not to make defamatory statements and not to
infringe or authorize any infringement of copyright or any other legal
right by email communications. Any such communication is contrary to TeleGo
policy and outside the scope of the employment of the individual concerned.
TeleGo will not accept any liability in respect of such communication, and
the employee responsible will be personally liable for any damages or other
liability arising.
TeleGo Hosted PBX <https://youtu.be/DaT8YAZ4V0w>
Oct. 30, 2023
Voice Peering
by beckman@angryox.com
On Wed, 25 Oct 2023, Mike Johnston via VoiceOps wrote:
> Anyways, say your system is getting a call from 555-555-1234. So you do a
> DNS query against...I do not know.
>
> dig TXT 4.3.2.1.5.5.5.5.5.5.i-do-not-know.....
How do you take an incoming call, from an IP you do not know, turn that IP
and/or phone number into a Domain Name, and then query it?
If you get a domain name, you now automatically trust that the incoming call is
worthy of your trust, because I can set up "allyourbase.com" and send a
call to you and you check my SPF record and I say "totally ip4:0.0.0.0/24"
(the entire internet) and you go "Cool! I'll take the call!"
Yet what entity is actually sending you the call?
SPF works because what you are sending (email) is also part of the domain
name. And even if you added a SIP header with a domain, all you are doing
is looking up a SPF/TXT record for the domain the call says they are
coming from, but now you have to implement DKIM-signing so someone cannot
pretend to be calling from a different domain. Then YOU the call receiver
have to decide if you trust the entity that is sending the call!!! And you
still haven't solved the problem of how the caller found out your Endpoint
in the first place to make the SIP call.
There are DNS SRV records, which tell you HOW to access a certain service
given a domain name.
e.g.
--> dig srv _sip._udp.srv.lcr.thinq.com
; <<>> DiG 9.10.6 <<>> srv _sip._udp.srv.lcr.thinq.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27421
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;_sip._udp.srv.lcr.thinq.com. IN SRV
;; ANSWER SECTION:
_sip._udp.srv.lcr.thinq.com. 20384 IN SRV 100 50 5060 lcr-lb02.rdu.thinq.com.
_sip._udp.srv.lcr.thinq.com. 20384 IN SRV 200 50 5060 lcr-lb02.dfw.thinq.com.
_sip._udp.srv.lcr.thinq.com. 20384 IN SRV 200 50 5060 lcr-lb01.dfw.thinq.com.
_sip._udp.srv.lcr.thinq.com. 20384 IN SRV 100 50 5060 lcr-lb01.rdu.thinq.com.
;; Query time: 5 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Wed Oct 25 18:47:53 EDT 2023
;; MSG SIZE rcvd: 224
That's great, so I know where to send a call, if I know that Thinq is the
endpoint of record for a phone numbe . But how do I take +1 202 456 1111
and authoritatively know what endpoint/domain/entity to reach out to? And
how does that endpoint know to trust me?
Due to Number Porting and a lack of any way for any leasee of a number to
publish such information with the blessing of NANPA ($govt-entity) and the
assigned Tier 0 carrier, or have any fallback if your endpoint is offline or
unavailable, there's no hierarchy to implement.
I suppose something like this could work:
NANPA (root) gets request for 12024561111, tells you to check with IQ at a
certain hostname
IQ (delegate) gets request for 12024561111, tells you to check with
FrogTele at a certain hostname
FrogTele gives you a response that confirms that one can call them and
reach the endpoint
A SRV query is made to determine what host(s) within FrogTele can
handle a UDP SIP call
You place the call
If it fails, maybe you can go to IQ as a backup and call through them.
If FrogTele says "no I do not service that number," then what do you do, go
back to IQ?
For ANY of this to work, NANPA and Tier 0 carriers who get numbers directly
from NANPA (NANPA only knows about its direct customers, not resellers, or
Tier 1+ carriers) would have to build it and participate.
Even if they did, currently all this is implemented either through security
through obscurity (which this model breaks) or IP firewalls & whitelists.
Most of the authentication stuff is weak or static, which is another
security risk.
Now that all the Internet knows what carrier is handling a specific phone
number, which potentially discloses PII, which an attacker could then use
to target the website and web account of the target with a re-used password
from another hack, and your customer loses their account (granted because
of their bad security practices) because you wanted to save a few tenths of
a cent per minute.
TRUST is the problem. MONEY is the problem.
NANPA has no financial nor governmental incentive to do this.
Tier 0 carriers have a negative financial incentive to do this.
Without NANPA and Tier 0 carriers involvement, anyone can self-publish a
record somewhere saying "Call me here!" and nobody will know if that can be
trusted, because the trust chain is non-existent without NANPA and Tier 0
carriers involvement.
Like Alex said, Technically this is achievable.
Politically and Financially this is Dead on Arrival, at least until the
incentives change.
On Wed, 25 Oct 2023, Mike Johnston via VoiceOps wrote:
> Who can source email from a domain is more-or-less a solved problem by using
> DNS SPF records.
>
> An SPF record is a list of IP addresses[1] that is allowed to send email for
> a domain. When an email server receives an email, best practice is to do a
> DNS lookup for the SPF of the alleged sender domain. If the server
> attempting to send the email is not mentioned in the SPF, then you can reject
> the incoming email.
>
> Does anybody know if something like SPF has been adapted to voice?
>
> For example, say anything from 54.239.16.0/24 is allowed as that is where
> your phone switches are. And 20.112.88.88/29 can also make calls, as that is
> one of those School Auto-Dialer services[2]. (Or whatever, make up your own
> scenarios.)
>
> When you receive calls, you would need to do a DNS lookup to get the list of
> allowed senders. If it's not in the list, reject the call.
>
> The exact query, and who we are querying, is a good question, though. Who
> owns the phone number?
>
> Anyways, say your system is getting a call from 555-555-1234. So you do a
> DNS query against...I do not know.
>
> dig TXT 4.3.2.1.5.5.5.5.5.5.i-do-not-know.....
How do you take an incoming call, from an IP you do not know, turn that IP
and/or phone number into a Domain Name, and then query it?
If you get that, you now automatically trust that the incoming call is
worthy of your trust, because I can set up "allyourbase.com" and send a
call to you and you check my SPF record and I say "totally ip4:0.0.0.0/24"
(the entire internet) and you go "Cool! I'll take the call!"
Yet what entity is actually sending you the call?
> And say you got this back from the DNS query:
>
> "v=spf1 ip4:54.239.16.0/24 ip4:20.112.88.88/29 -all"
>
> If the server sending you the call is not in 54.239.16.0/24 or
> 20.112.88.88/29, then reject the call.
>
> [1] An SPF record can have more than just IP addresses, but can also
> "include" other domain names.
> [2] You might do your DNS in such a way, that 20.112.88.88/29 is only
> returned for the specific number(s) that you expect them to be sending from,
> not ALL of your numbers.
>
> Further reading:
> https://en.wikipedia.org/wiki/Sender_Policy_Framework
> https://www.cloudflare.com/learning/dns/dns-records/dns-spf-record/
> https://support.google.com/a/answer/10685031?hl=en
---------------------------------------------------------------------------
Peter Beckman Internet Guy
beckman at angryox.com https://www.angryox.com/
---------------------------------------------------------------------------
Oct. 25, 2023
Voice Peering
by jawaid@bazyar.net
Well, in any kind of fully-distributed scenario some type of security
mechanism that might not look all that dissimilar from STIR/SHAKEN would be
implied.
What I've heard so far is many different potential implementations at just
about every level of the business stack that exists today, so I'd say that
question is still unresolved.
On Wed, Oct 25, 2023 at 5:08?PM Peter Beckman <beckman at angryox.com> wrote:
> This whole conversation, and topic, is "Voice Peering" -- ORIGINATING CALLS
> directly to the endpoint rather than me passing to Level3 who passes to IQ
> who passes to their customer who passes to their customer who has a VoIP
> device that I could reach directly if I only had the ability to do so.
>
> This has nothing to do with rejecting incoming calls signed with
> STIR/SHAKEN.
>
> The call cannot start until I know where to send the call. <-- problem
> that we are discussing
>
> Beckman
>
> On Wed, 25 Oct 2023, Matthew Crocker wrote:
>
> >
> > I never said STIR/SHAKEN would be used to ?look up? for call routing.
> >
> > Earlier someone mentioned an issue with open peering is spam calls.
> STIR/SHAKEN can solve that issue.
> >
> > You can certainly use STIR/SHAKEN to reject calls from $COMPANY once you
> have determined you don?t like $COMPANY. That can easily be done off line
> by CDR analysis. Sure you let a couple dozen calls in but you can pretty
> quickly find ?$BAD_COMPANY? and start rejecting their calls. The system
> would settle our fairly quickly
> >
> > From: Peter Beckman <beckman at angryox.com>
> > Date: Wednesday, October 25, 2023 at 12:04 PM
> > To: Matthew Crocker <matthew at corp.crocker.com>
> > Cc: Pinchas Neiman <neimanpinchas at gmail.com>, Jawaid Bazyar <
> jawaid at bazyar.net>, voiceops <voiceops at voiceops.org>
> > Subject: Re: [VoiceOps] Voice Peering
> > CAUTION: This email originated from outside of Crocker. Do not click
> links or open attachments unless you recognize the sender and know the
> content is safe.
> >
> >
> > STIR/SHAKEN does not delegate any authority to anyone.
> >
> > It merely allows me to sign a call that I originate, so that someone else
> > can say "Oh this came from $COMPANY."
> >
> > Besides, STIR/SHAKEN is done at the time of an origination call, it
> cannot
> > be "looked up" to see where to route a call.
> >
> > The suggestion that STIR/SHAKEN could be used to authoritatively assign a
> > DID endpoint to someone demonstrates a lack of understanding in how it
> > works and what it does and does not do.
> >
> > Beckman
> >
> > On Wed, 25 Oct 2023, Matthew Crocker via VoiceOps wrote:
> >
> >>
> >> With STIR/SHAKEN (in theory) all calls will be signed, authenticated so
> you can trace the originating carrier. In an open peering environment you
> can use it to accept/reject calls
> >>
> >> Open SIP proxy handles all of the SIP traffic, RTP goes directly
> between carriers.
> >> All calls originated must be signed (STIRred)
> >>
> >> * Call isn?t signed, gets rejected by the SIP peering proxy
> >> Terminating carrier can validate the signed calls (SHAKEN)
> >>
> >> * Don?t like the signing CA? reject the call
> >> * Don?t like the signing carrier? Reject the call
> >> * Carrier sending too many spam calls, adjust treatment based on
> customer spam settings
> >>
> >>
> >> Routing is handled between terminating carrier and SIP peering proxy.
> Originating carrier sends all calls to peering proxy first, if proxy
> doesn?t have the route it sends a 4XX error back and originating carrier
> can continue routing on other paths.
> >>
> >> So terminating carriers would need to export/upload (hacked BGP?)
> numbers they are willing to receive calls on to the peering proxy.
> >>
> >> Proxies can be spun up in various AWS/Azure/GoogleCloud VPS
> >>
> >>
> >> From: Pinchas Neiman <neimanpinchas at gmail.com>
> >> Date: Wednesday, October 25, 2023 at 11:18 AM
> >> To: Jawaid Bazyar <jawaid at bazyar.net>
> >> Cc: Matthew Crocker <matthew at corp.crocker.com>, voiceops <
> voiceops at voiceops.org>
> >> Subject: Re: [VoiceOps] Voice Peering
> >> CAUTION: This email originated from outside of Crocker. Do not click
> links or open attachments unless you recognize the sender and know the
> content is safe.
> >>
> >> By reading the RFCs I was able to grasp 75% of it, it's well written
> and covers your clear constraint, at least on how to verify the SIP header
> comes from a trustworthy authority (If you agree on the root authority)
> >> Practically implementing STIR/SHAKEN has bureaucracy involved.
> >>
> >> On Tue, Oct 24, 2023 at 9:38?PM Jawaid Bazyar via VoiceOps <
> voiceops at voiceops.org<mailto:voiceops at voiceops.org>> wrote:
> >> Is there a good clear document somewhere describing how STIR/SHAKEN is
> supposed to work?
> >>
> >> On Tue, Oct 24, 2023 at 9:33?PM Matthew Crocker via VoiceOps <
> voiceops at voiceops.org<mailto:voiceops at voiceops.org>> wrote:
> >>
> >>
> >>> On Oct 24, 2023, at 9:13 PM, Peter Beckman via VoiceOps <
> voiceops at voiceops.org<mailto:voiceops at voiceops.org>> wrote:
> >>>
> >>> ?CAUTION: This email originated from outside of Crocker. Do not click
> links or open attachments unless you recognize the sender and know the
> content is safe.
> >>>
> >>>
> >>> The challenge is how do you authenticate the end "carrier" or service
> >>> provider?
> >>>
> >>
> >> STIR/SHAKEN
> >>
> >>
> >>> Sure, anyone who leases numbers directly from NANPA can look up the
> carrier
> >>> of record and exchange traffic directly, but any business who also
> leases
> >>> numbers INDIRECTLY gets cut out and still needs to pay their upstream
> >>> carrier(s) to place/receive calls, either by channels or per minute,
> even
> >>> if their upstream is directly peered and not transiting the PSTN at
> all.
> >>>
> >>> If this would be for the end user, then NANPA would have to delegate
> to the
> >>> leasee, the leasee delegate to the reseller, the reseller to the end
> user,
> >>> then the end user could publish their VoIP contact info, and anyone
> could
> >>> call directly via VoIP, cutting out all of the middle peers.
> >>>
> >>> But, as another person said, this is ripe for abuse, and with no
> motivation
> >>> by NANPA or the larger carriers to make calls less expensive for the
> >>> reseller or end user, I see this going nowhere. Until there is some
> value
> >>> in NANPA (plus all the other country telephony organizations) and the
> >>> direct carriers leasing numbers to do so.
> >>>
> >>> Beckman
> >>>
> >>>> On Tue, 24 Oct 2023, Ross Tajvar via VoiceOps wrote:
> >>>>
> >>>> I can think of a few ways that could be adapted into a platform more
> like
> >>>> an Internet exchange, but as others have said, it just doesn't seem
> worth
> >>>> it.
> >>>>
> >>>> On Tue, Oct 24, 2023, 5:31?PM Jawaid Bazyar via VoiceOps <
> >>>> voiceops at voiceops.org<mailto:voiceops at voiceops.org>> wrote:
> >>>>
> >>>>> I think schemes like DUNDI (and some of the others mentioned here)
> suffer
> >>>>> from a trust issue ? what?s to prevent operator X from poisoning the
> >>>>> protocol with bogus ?stolen? numbers?
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Tue, Oct 24, 2023 at 5:25?PM Jared Smith via VoiceOps <
> >>>>> voiceops at voiceops.org<mailto:voiceops at voiceops.org>> wrote:
> >>>>>
> >>>>>> On Tue, Oct 24, 2023 at 8:49?AM Mike Hammett via VoiceOps <
> >>>>>> voiceops at voiceops.org<mailto:voiceops at voiceops.org>> wrote:
> >>>>>>
> >>>>>>> This was in another thread, but I broke it out into it's own
> >>>>>>> conversation. Someone had asked:
> >>>>>>>
> >>>>>>> ---
> >>>>>>> I am joining this thread late, but, would anyone out there be
> interested
> >>>>>>> in exchanging traffic with other carriers directly over SIP?
> >>>>>>>
> >>>>>>
> >>>>>> Just another point of VoIP history trivia at this point... but in
> >>>>>> addition to things like ENUM and ITAD, Mark Spencer of Asterisk
> fame also
> >>>>>> invented Dundi, which was an encrypted peer-to-peer protocol for
> route
> >>>>>> advertisement and discovery. As far as I know, very few people
> besides me
> >>>>>> ever put it in production, but it worked really well at the time.
> (Of
> >>>>>> course, it's been about 17 or 18 years now since I used it in
> production.)
> >>>>>>
> >>>>>> -Jared
> >>>>>> _______________________________________________
> >>>>>> 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
> >>>>>
> >>>>
> >>>
> >>>
> ---------------------------------------------------------------------------
> >>> Peter Beckman
> Internet Guy
> >>> beckman at angryox.com<mailto:beckman at angryox.com>
> https://www.angryox.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
> >> _______________________________________________
> >> VoiceOps mailing list
> >> VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
> >> https://puck.nether.net/mailman/listinfo/voiceops
> >>
> >>
> >> --
> >> Pinchas S. Neiman
> >> Software Engineer At ESEQ Technology Corp.
> >> 845.213.1229 #2
> >> [Image removed by sender.]
> >>
> >
> >
> ---------------------------------------------------------------------------
> > Peter Beckman Internet
> Guy
> > beckman at angryox.com
> https://www.angryox.com/
> >
> ---------------------------------------------------------------------------
> >
>
> ---------------------------------------------------------------------------
> Peter Beckman Internet Guy
> beckman at angryox.com
> https://www.angryox.com/
> ---------------------------------------------------------------------------
Oct. 25, 2023