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
USF is 33.4% for 2Q2021
by edguy@eguy.org
Peter,
> Where did your understanding come from?
My info could now be called 'Myth' - I've been out of the retail business for about 9 years.
For cellular in US, we had to keep track of originating party jurisdiction, terminating party jurisdiction,
and any O/T cells involved. Then the tax wizards ran some formula to break it up.
The tax and billing software & services were more expensive than the communications systems.
Alex, I recall a lot of discussion about 'Safe Harbor' tax payments - rather than detailed per call billing, using
broad formulas to distribute the tax... Was particularly useful for flat-rate bundled plans. The tax man seemed unconcerned
as long as they got their money. (Again, I would classify my retained knowledge as 'myth' )
/ed
**
A couple more data points -
$350 verizon wireless bill:
Surcharges $2.64
Fed Universal Service Charge $0.48
Regulatory Charge $0.21
Administrative Charge $1.95
Taxes and gov fees $1.27
NJ 911 System/Emerg. Resp. Fee $0.90
NJ State Sls Tax-Telco $0.37
Phone.com:
05/12/2021 - 06/11/2021 Virtual Office plan $14.88
05/13/2021 Regulatory recovery fee $0.38
05/12/2021 - 05/13/2021 FUSF (VoIP) $3.32
05/12/2021 - 05/13/2021 FCC regulatory fee (VoIP) $0.05
05/12/2021 - 05/13/2021 Sales tax $1.25
?On 6/10/21, 3:58 PM, "Peter Beckman" <beckman at angryox.com> wrote:
Ed -- I'd love to see more data on this. Where did your understanding come
from?
I looked at my cellular bill last night, and on 4 lines, the "Fed Universal
Service Charge" was a total of $1.88 on a total bill of about $180 (about
$160 of it was just the monthly fee for 4 plans).
Does anyone know how the wireless companies pay USF? E.g. they are paying
33.4% on what exactly?
Beckman
On Thu, 10 Jun 2021, Ed Guy wrote:
> What service features of the service are subject to USF?
> is it only charged on retail land-line replacement or at multiple levels as a value-add?
> My understanding is that cellular services do not pay USF ( but, when we had a
> cell company several years ago, all taxes were outsourced..)
>
>
> On 6/10/21, 1:07 PM, "VoiceOps on behalf of Alex Balashov"
> <voiceops-bounces at voiceops.org on behalf of abalashov at evaristesys.com>
> wrote:
>
> That, and, while I am not at all an expert on what can and can't be
> recovered from customers, it was my impression that not 100% of USF can
> be passed on.
>
> On 6/10/21 1:03 PM, Carlos Alvarez wrote:
>
> > Except that some of us specifically sell "bottom line" pricing that is
> > not variable and not padded with 20 lines of fees and taxes. Because
> > our ILEC is known for quoting $100 and billing $130-150 actual price.
> >
> > On Thu, Jun 10, 2021 at 9:38 AM Paul Timmins <paul at timmins.net> wrote:
> >
> > On 6/10/21 6:23 AM, Alex Balashov wrote:
> > >
> > > Yeah, observing it as an outsider who is not a service provider,
> > I'm a
> > > little shocked to say the least. It's hard to understand where that
> > > kind of money is supposed to come from with the margins in this
> > business.
> > >
> > Passthru fees to the end user, duh. There's nothing us telcos can't
> > cram
> > on the bottom of the bill.
> >
> > Customers are gonna be ticked, but what ya gonna do. It's a line item
> > now, and a line item later.
---------------------------------------------------------------------------
Peter Beckman Internet Guy
beckman at angryox.com http://www.angryox.com/
---------------------------------------------------------------------------
June 10, 2021
USF is 33.4% for 2Q2021
by voiceops@ics-il.net
I had thought it was, "here's the safe harbor. If you want to substitute your own traffic study go ahead. We won't define how it is calculated, just don't screw it up, or you'll get our boot in your backside."
I figured it was as macro or micro as you wanted it to be and could support.
-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
Midwest Internet Exchange
http://www.midwest-ix.com
----- Original Message -----
From: "Alex Balashov" <abalashov at evaristesys.com>
To: voiceops at voiceops.org
Sent: Thursday, June 10, 2021 3:29:08 PM
Subject: Re: [VoiceOps] USF is 33.4% for 2Q2021
On 6/10/21 4:19 PM, Mike Hammett wrote:
> $3.19 is right around 24% of 33.4% of $39.95. Maybe Comcast's traffic
> studies show that 24% of phone traffic is interstate, so that's the
> amount that gets the USF charge?
It had been my impression that the FCC rather particularly insisted on a
small number of standardised methodologies for calculating the USF fees
recovered from end-customers. That would be in order to prevent opaque
schemes in which the fees are marked up further through some convoluted,
abstruse arithmetic.
Based on that, it seems doubtful that they one can just amortise the
aggregate pro rata share of interstate revenue across the entire
customer base, regardless of whether the customer in question does much
interstate calling themselves.
Or am I wrong?
-- Alex
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
June 10, 2021
"Timeout" on VoIP call traversing Verizon data
by dovid@telecurve.com
Mark,
We are not using MetaSwitch. What I am saying is because we ran into this
issue in the past the only thing we found to get around it was to send
OPTIONS every 60 seconds. In the past we have used TCP and we actually had
a lot more problems with TCP then UDP (I never dug too much into it to see
why, simply moving to UDP fixed it). Does meta have an option to use an
alternate port? A lot of carriers have "issues" with 5060.
On Thu, Jun 10, 2021 at 9:21 AM Mark Wiles <mwiles at akabis.com> wrote:
> Hi Dovid,
>
>
>
> So just thinking about this? granted, there wasn?t SIP traffic for ?X?
> amount of time? but there would have been RTP? so wouldn?t that have been
> seen as traffic?
>
> Hmmm? but as soon as I typed that, SIP traffic?s on one port? RTP
> traffic?s on another port? so even with the RTP flowing along and happy?
> the SIP?s another matter? right? Duh! (I?ve not had my coffee yet)
>
>
>
> Are you saying that you?re using Metaswitch MaX UC and you?re doing a SIP
> OPTIONS message every 49 seconds?
>
> I totally agree it does sound like a NAT pinhole is closing. It would
> seem that if that?s the case, Meta would have run into this before and had
> ?recommendations? to address this.
>
> I?ll bounce your thoughts off of them.
>
>
>
> Thanks!
>
>
>
> Mark
>
>
>
>
>
>
>
>
>
>
>
> *From:* Dovid Bender <dovid at telecurve.com>
> *Sent:* Thursday, June 10, 2021 8:47 AM
> *To:* Mark Wiles <mwiles at akabis.com>
> *Cc:* voiceops at voiceops.org
> *Subject:* Re: [VoiceOps] "Timeout" on VoIP call traversing Verizon data
>
>
>
> If I had to guess Verizon is using CGNAT and since there is no traffic for
> X amount of time the NAT hole for the SIP traffic is closed. When you send
> a re-invite at the 30 minute mark that session as far as Verizon's CGNAT
> devices are concerned have been closed a long time ago. You would need to
> send a packet to the phone or have the phone send to your switch some sort
> of traffic (we send SIP OPTIONS every 49 seconds) to ensure that the
> session stays alive.
>
>
>
>
>
>
>
> On Wed, Jun 9, 2021 at 3:27 PM Mark Wiles <mwiles at akabis.com> wrote:
>
> If there?s a Verizon cellular data guru monitoring here, I?d love to get
> your insight!
>
>
>
> Otherwise, let me toss this out to the group for thoughts and opinions
> please?
>
>
>
> We?re a Metaswitch shop, and use their MaX UC mobile softphone client
> (iPhone/Android).
>
>
>
> We had a customer using the MaX UC client on a long call? they were using
> Verizon cellular data (confirmed by IP address).
>
> At thirty (30) minutes into the call, the call ?dropped?. The call was
> re-established, and again, after thirty minutes, the call dropped.
>
> We?re pretty sure the user was in a static position (non-mobile)? and
> logically *assume* they were on the same cell tower for both calls that
> dropped (the Verizon IP was the same).
>
>
>
> Looking at Metaswitch SAS (their diagnostics tool), at the thirty minute
> mark, we send out a re-INVITE message to the softphone client? and we
> receive no reply? so after ten seconds, we breakdown the call assuming
> they?re gone. Then about eight seconds later, we see an INVITE message
> from the softphone?s same IP address (with the same Call ID)? however, it?s
> coming from a different port. So to be clear, the original call setup and
> connection was using 1.2.3.4:6789? then eight seconds after we ended the
> call with a BYE (assuming they were gone due to lack of reply), we get an
> INVITE (with the same Call ID) from 1.2.3.4:9876.
>
>
>
> Metaswitch looked at the diags from the softphone (we downloaded them),
> and they?re confirming that the softphone never received our re-INVITE at
> the 30 minute mark.
>
>
>
> Metaswitch also looked at the bug/crash logs on the softphone, and
> confirmed neither was the case.
>
>
>
> It almost sounds like a NAT thing going on? but I?m pretty ignorant when
> it comes to cellular data. It looks to me as if the Verizon side simply
> changed port numbers, and assumed we?d know maybe via mental telepathy?
> ?
>
>
>
> Has anyone had experience with such an occurrence? or any thoughts?
>
>
>
> Thank you!
>
>
>
> Mark
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
> <https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fpuck.nether.net%2fmailm…>
>
>
June 10, 2021
USF is 33.4% for 2Q2021
by abalashov@evaristesys.com
On 6/10/21 4:19 PM, Mike Hammett wrote:
> $3.19 is right around 24% of 33.4% of $39.95. Maybe Comcast's traffic
> studies show that 24% of phone traffic is interstate, so that's the
> amount that gets the USF charge?
It had been my impression that the FCC rather particularly insisted on a
small number of standardised methodologies for calculating the USF fees
recovered from end-customers. That would be in order to prevent opaque
schemes in which the fees are marked up further through some convoluted,
abstruse arithmetic.
Based on that, it seems doubtful that they one can just amortise the
aggregate pro rata share of interstate revenue across the entire
customer base, regardless of whether the customer in question does much
interstate calling themselves.
Or am I wrong?
-- Alex
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
June 10, 2021
LERG Access
by voiceops@ics-il.net
Those of you that have LERG access, what do you have?
I've ran this network for a few years without it. I'm assuming I'm missing something I should have.
-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
Midwest Internet Exchange
http://www.midwest-ix.com
June 10, 2021
"Timeout" on VoIP call traversing Verizon data
by abalashov@evaristesys.com
Not to muddy the waters here with needless pedantry, but:
While UDP may be "connectionless", the only way UDP, and in particular,
symmetric SIP signalling, can work through NAT is if a stateful firewall
+ NAT gateway has some awareness (that is, state) of UDP "flows", or
groups of packets flowing between ports consistently in some kind of
temporary logical association--one might say, the endpoints have a
"connection" of sorts...
-- Alex
On 6/10/21 4:07 PM, Peter Beckman wrote:
> uhhhh.... SIP here is UDP, no?
>
> There's no connection to close for UDP.
>
> The source port for UDP doesn't matter. It's not part of the whole
> conversation, unless your switch cares that all communications continue to
> come from the source port. It's connectionless.
>
> TCP 5060 isn't even listening on our switches.
>
> So, maybe you're doing SIP over TCP?
>
> On Thu, 10 Jun 2021, Mark Wiles wrote:
>
>> Hi Dovid,
>>
>> So just thinking about this? granted, there wasn?t SIP traffic for ?X?
>> amount of time? but there would have been RTP? so wouldn?t that have
>> been seen as traffic?
>> Hmmm? but as soon as I typed that, SIP traffic?s on one port? RTP
>> traffic?s on another port? so even with the RTP flowing along and
>> happy? the SIP?s another matter? right?? Duh!? (I?ve not had my coffee
>> yet)
>>
>> Are you saying that you?re using Metaswitch MaX UC and you?re doing a
>> SIP OPTIONS message every 49 seconds?
>> I totally agree it does sound like a NAT pinhole is closing.? It would
>> seem that if that?s the case, Meta would have run into this before and
>> had ?recommendations? to address this.
>> I?ll bounce your thoughts off of them.
>>
>> Thanks!
>>
>> Mark
>>
>>
>>
>>
>>
>> From: Dovid Bender <dovid at telecurve.com>
>> Sent: Thursday, June 10, 2021 8:47 AM
>> To: Mark Wiles <mwiles at akabis.com>
>> Cc: voiceops at voiceops.org
>> Subject: Re: [VoiceOps] "Timeout" on VoIP call traversing Verizon data
>>
>> If I had to guess Verizon is using CGNAT and since there is no traffic
>> for X amount of time the NAT hole for the SIP traffic is closed. When
>> you send a re-invite at the 30 minute mark that session as far as
>> Verizon's CGNAT devices are concerned have been closed a long time
>> ago. You would need to send a packet to the phone or have the phone
>> send to your switch some sort of traffic (we send SIP OPTIONS every 49
>> seconds) to ensure that the session stays alive.
>>
>>
>>
>> On Wed, Jun 9, 2021 at 3:27 PM Mark Wiles
>> <mwiles at akabis.com<mailto:mwiles at akabis.com>> wrote:
>> If there?s a Verizon cellular data guru monitoring here, I?d love to
>> get your insight!
>>
>> Otherwise, let me toss this out to the group for thoughts and opinions
>> please?
>>
>> We?re a Metaswitch shop, and use their MaX UC mobile softphone client
>> (iPhone/Android).
>>
>> We had a customer using the MaX UC client on a long call? they were
>> using Verizon cellular data (confirmed by IP address).
>> At thirty (30) minutes into the call, the call ?dropped?.? The call
>> was re-established, and again, after thirty minutes, the call dropped.
>> We?re pretty sure the user was in a static position (non-mobile)? and
>> logically assume they were on the same cell tower for both calls that
>> dropped (the Verizon IP was the same).
>>
>> Looking at Metaswitch SAS (their diagnostics tool), at the thirty
>> minute mark, we send out a re-INVITE message to the softphone client?
>> and we receive no reply? so after ten seconds, we breakdown the call
>> assuming they?re gone.? Then about eight seconds later, we see an
>> INVITE message from the softphone?s same IP address (with the same
>> Call ID)? however, it?s coming from a different port.? So to be clear,
>> the original call setup and connection was using 1.2.3.4:6789? then
>> eight seconds after we ended the call with a BYE (assuming they were
>> gone due to lack of reply), we get an INVITE (with the same Call ID)
>> from 1.2.3.4:9876<http://1.2.3.4:9876>.
>>
>> Metaswitch looked at the diags from the softphone (we downloaded
>> them), and they?re confirming that the softphone never received our
>> re-INVITE at the 30 minute mark.
>>
>> Metaswitch also looked at the bug/crash logs on the softphone, and
>> confirmed neither was the case.
>>
>> It almost sounds like a NAT thing going on? but I?m pretty ignorant
>> when it comes to cellular data.? It looks to me as if the Verizon side
>> simply changed port numbers, and assumed we?d know maybe via mental
>> telepathy?? ?
>>
>> Has anyone had experience with such an occurrence? or any thoughts?
>>
>> Thank you!
>>
>> Mark
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
>> https://puck.nether.net/mailman/listinfo/voiceops<https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fpuck.nether.net%2fmailm…>
>>
>>
>
> ---------------------------------------------------------------------------
> 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
>
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
June 10, 2021
USF is 33.4% for 2Q2021
by voiceops@ics-il.net
$3.19 is right around 24% of 33.4% of $39.95. Maybe Comcast's traffic studies show that 24% of phone traffic is interstate, so that's the amount that gets the USF charge?
-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
Midwest Internet Exchange
http://www.midwest-ix.com
----- Original Message -----
From: "Matthew Yaklin" <myaklin at firstlight.net>
To: "Peter Beckman" <beckman at angryox.com>, "Ed Guy" <edguy at eguy.org>
Cc: voiceops at voiceops.org
Sent: Thursday, June 10, 2021 3:07:53 PM
Subject: Re: [VoiceOps] USF is 33.4% for 2Q2021
A comcast business package looks like this right now for a small biz:
Internet - 69.95
Voice line - 39.95
Voice equipment fee - 18.45 (that is hilarious to convert their coax signal to fxs)
FUSF - 3.19
Regulatory cost recovery - 1.36
Voice network investment - 3.00 (wtf)
Directory listing mgmt fee - 2.00
Sales tax - 4.22
911 fees - 1.50
Grand total - 143.62
Where and how is that 3.19 calculated?
I am curious as well.
Matt
-----Original Message-----
From: VoiceOps <voiceops-bounces at voiceops.org> On Behalf Of Peter Beckman
Sent: Thursday, June 10, 2021 3:58 PM
To: Ed Guy <edguy at eguy.org>
Cc: voiceops at voiceops.org
Subject: Re: [VoiceOps] USF is 33.4% for 2Q2021
Ed -- I'd love to see more data on this. Where did your understanding come from?
I looked at my cellular bill last night, and on 4 lines, the "Fed Universal Service Charge" was a total of $1.88 on a total bill of about $180 (about
$160 of it was just the monthly fee for 4 plans).
Does anyone know how the wireless companies pay USF? E.g. they are paying 33.4% on what exactly?
Beckman
On Thu, 10 Jun 2021, Ed Guy wrote:
> What service features of the service are subject to USF?
> is it only charged on retail land-line replacement or at multiple levels as a value-add?
> My understanding is that cellular services do not pay USF ( but, when
> we had a cell company several years ago, all taxes were outsourced..)
>
>
> On 6/10/21, 1:07 PM, "VoiceOps on behalf of Alex Balashov"
> <voiceops-bounces at voiceops.org on behalf of abalashov at evaristesys.com>
> wrote:
>
> That, and, while I am not at all an expert on what can and can't be
> recovered from customers, it was my impression that not 100% of USF can
> be passed on.
>
> On 6/10/21 1:03 PM, Carlos Alvarez wrote:
>
> > Except that some of us specifically sell "bottom line" pricing that is
> > not variable and not padded with 20 lines of fees and taxes. Because
> > our ILEC is known for quoting $100 and billing $130-150 actual price.
> >
> > On Thu, Jun 10, 2021 at 9:38 AM Paul Timmins <paul at timmins.net> wrote:
> >
> > On 6/10/21 6:23 AM, Alex Balashov wrote:
> > >
> > > Yeah, observing it as an outsider who is not a service provider,
> > I'm a
> > > little shocked to say the least. It's hard to understand where that
> > > kind of money is supposed to come from with the margins in this
> > business.
> > >
> > Passthru fees to the end user, duh. There's nothing us telcos can't
> > cram
> > on the bottom of the bill.
> >
> > Customers are gonna be ticked, but what ya gonna do. It's a line item
> > now, and a line item later.
---------------------------------------------------------------------------
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
June 10, 2021
"Timeout" on VoIP call traversing Verizon data
by mwiles@akabis.com
Yes, I think the softphone client does use TCP.
-----Original Message-----
From: Peter Beckman <beckman at angryox.com>
Sent: Thursday, June 10, 2021 4:07 PM
To: Mark Wiles <mwiles at akabis.com>
Cc: Dovid Bender <dovid at telecurve.com>; voiceops at voiceops.org
Subject: Re: [VoiceOps] "Timeout" on VoIP call traversing Verizon data
uhhhh.... SIP here is UDP, no?
There's no connection to close for UDP.
The source port for UDP doesn't matter. It's not part of the whole conversation, unless your switch cares that all communications continue to come from the source port. It's connectionless.
TCP 5060 isn't even listening on our switches.
So, maybe you're doing SIP over TCP?
On Thu, 10 Jun 2021, Mark Wiles wrote:
> Hi Dovid,
>
> So just thinking about this? granted, there wasn?t SIP traffic for ?X? amount of time? but there would have been RTP? so wouldn?t that have been seen as traffic?
> Hmmm? but as soon as I typed that, SIP traffic?s on one port? RTP
> traffic?s on another port? so even with the RTP flowing along and
> happy? the SIP?s another matter? right? Duh! (I?ve not had my coffee
> yet)
>
> Are you saying that you?re using Metaswitch MaX UC and you?re doing a SIP OPTIONS message every 49 seconds?
> I totally agree it does sound like a NAT pinhole is closing. It would seem that if that?s the case, Meta would have run into this before and had ?recommendations? to address this.
> I?ll bounce your thoughts off of them.
>
> Thanks!
>
> Mark
>
>
>
>
>
> From: Dovid Bender <dovid at telecurve.com>
> Sent: Thursday, June 10, 2021 8:47 AM
> To: Mark Wiles <mwiles at akabis.com>
> Cc: voiceops at voiceops.org
> Subject: Re: [VoiceOps] "Timeout" on VoIP call traversing Verizon data
>
> If I had to guess Verizon is using CGNAT and since there is no traffic for X amount of time the NAT hole for the SIP traffic is closed. When you send a re-invite at the 30 minute mark that session as far as Verizon's CGNAT devices are concerned have been closed a long time ago. You would need to send a packet to the phone or have the phone send to your switch some sort of traffic (we send SIP OPTIONS every 49 seconds) to ensure that the session stays alive.
>
>
>
> On Wed, Jun 9, 2021 at 3:27 PM Mark Wiles <mwiles at akabis.com<mailto:mwiles at akabis.com>> wrote:
> If there?s a Verizon cellular data guru monitoring here, I?d love to get your insight!
>
> Otherwise, let me toss this out to the group for thoughts and opinions
> please?
>
> We?re a Metaswitch shop, and use their MaX UC mobile softphone client (iPhone/Android).
>
> We had a customer using the MaX UC client on a long call? they were using Verizon cellular data (confirmed by IP address).
> At thirty (30) minutes into the call, the call ?dropped?. The call was re-established, and again, after thirty minutes, the call dropped.
> We?re pretty sure the user was in a static position (non-mobile)? and logically assume they were on the same cell tower for both calls that dropped (the Verizon IP was the same).
>
> Looking at Metaswitch SAS (their diagnostics tool), at the thirty minute mark, we send out a re-INVITE message to the softphone client? and we receive no reply? so after ten seconds, we breakdown the call assuming they?re gone. Then about eight seconds later, we see an INVITE message from the softphone?s same IP address (with the same Call ID)? however, it?s coming from a different port. So to be clear, the original call setup and connection was using 1.2.3.4:6789? then eight seconds after we ended the call with a BYE (assuming they were gone due to lack of reply), we get an INVITE (with the same Call ID) from 1.2.3.4:9876<http://1.2.3.4:9876>.
>
> Metaswitch looked at the diags from the softphone (we downloaded them), and they?re confirming that the softphone never received our re-INVITE at the 30 minute mark.
>
> Metaswitch also looked at the bug/crash logs on the softphone, and confirmed neither was the case.
>
> It almost sounds like a NAT thing going on? but I?m pretty ignorant
> when it comes to cellular data. It looks to me as if the Verizon side
> simply changed port numbers, and assumed we?d know maybe via mental
> telepathy? ?
>
> Has anyone had experience with such an occurrence? or any thoughts?
>
> Thank you!
>
> Mark
>
>
>
>
>
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
> https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fpuck.nether.net%2f
> mailman%2flistinfo%2fvoiceops&c=E,1,no2UwuzPowJk-FvIbVFfN7iDcR76xtEq05
> 6zI_8HqIS4C6el29j0Nho5rwTu6Bue8Wae7bxoYPWpF0Jleg1NU4BEeq9vbdWc_e3VIIUt
> 4BN8UmTI&typo=1<https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fpu
> ck.nether.net%2fmailman%2flistinfo%2fvoiceops&c=E,1,lh_KPqz2X9PUlHuKPJ
> 5xHOv6u61RFEXqn0IsKcXIj8NwnKlOz0fW5zqT3A9VPfn4xZipprpMy9tXkVyIfmOS7R3S
> B2CeIgsA5IPv6mEk65Mh92RokKDZDpu9AsXm&typo=1>
>
---------------------------------------------------------------------------
Peter Beckman Internet Guy
beckman at angryox.com https://linkprotect.cudasvc.com/url?a=http%3a%2f%2fwww.angryox.com%2f&c=E,1…
---------------------------------------------------------------------------
June 10, 2021
USF is 33.4% for 2Q2021
by myaklin@firstlight.net
A comcast business package looks like this right now for a small biz:
Internet - 69.95
Voice line - 39.95
Voice equipment fee - 18.45 (that is hilarious to convert their coax signal to fxs)
FUSF - 3.19
Regulatory cost recovery - 1.36
Voice network investment - 3.00 (wtf)
Directory listing mgmt fee - 2.00
Sales tax - 4.22
911 fees - 1.50
Grand total - 143.62
Where and how is that 3.19 calculated?
I am curious as well.
Matt
-----Original Message-----
From: VoiceOps <voiceops-bounces at voiceops.org> On Behalf Of Peter Beckman
Sent: Thursday, June 10, 2021 3:58 PM
To: Ed Guy <edguy at eguy.org>
Cc: voiceops at voiceops.org
Subject: Re: [VoiceOps] USF is 33.4% for 2Q2021
Ed -- I'd love to see more data on this. Where did your understanding come from?
I looked at my cellular bill last night, and on 4 lines, the "Fed Universal Service Charge" was a total of $1.88 on a total bill of about $180 (about
$160 of it was just the monthly fee for 4 plans).
Does anyone know how the wireless companies pay USF? E.g. they are paying 33.4% on what exactly?
Beckman
On Thu, 10 Jun 2021, Ed Guy wrote:
> What service features of the service are subject to USF?
> is it only charged on retail land-line replacement or at multiple levels as a value-add?
> My understanding is that cellular services do not pay USF ( but, when
> we had a cell company several years ago, all taxes were outsourced..)
>
>
> On 6/10/21, 1:07 PM, "VoiceOps on behalf of Alex Balashov"
> <voiceops-bounces at voiceops.org on behalf of abalashov at evaristesys.com>
> wrote:
>
> That, and, while I am not at all an expert on what can and can't be
> recovered from customers, it was my impression that not 100% of USF can
> be passed on.
>
> On 6/10/21 1:03 PM, Carlos Alvarez wrote:
>
> > Except that some of us specifically sell "bottom line" pricing that is
> > not variable and not padded with 20 lines of fees and taxes. Because
> > our ILEC is known for quoting $100 and billing $130-150 actual price.
> >
> > On Thu, Jun 10, 2021 at 9:38 AM Paul Timmins <paul at timmins.net> wrote:
> >
> > On 6/10/21 6:23 AM, Alex Balashov wrote:
> > >
> > > Yeah, observing it as an outsider who is not a service provider,
> > I'm a
> > > little shocked to say the least. It's hard to understand where that
> > > kind of money is supposed to come from with the margins in this
> > business.
> > >
> > Passthru fees to the end user, duh. There's nothing us telcos can't
> > cram
> > on the bottom of the bill.
> >
> > Customers are gonna be ticked, but what ya gonna do. It's a line item
> > now, and a line item later.
---------------------------------------------------------------------------
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
June 10, 2021
"Timeout" on VoIP call traversing Verizon data
by beckman@angryox.com
uhhhh.... SIP here is UDP, no?
There's no connection to close for UDP.
The source port for UDP doesn't matter. It's not part of the whole
conversation, unless your switch cares that all communications continue to
come from the source port. It's connectionless.
TCP 5060 isn't even listening on our switches.
So, maybe you're doing SIP over TCP?
On Thu, 10 Jun 2021, Mark Wiles wrote:
> Hi Dovid,
>
> So just thinking about this? granted, there wasn?t SIP traffic for ?X? amount of time? but there would have been RTP? so wouldn?t that have been seen as traffic?
> Hmmm? but as soon as I typed that, SIP traffic?s on one port? RTP traffic?s on another port? so even with the RTP flowing along and happy? the SIP?s another matter? right? Duh! (I?ve not had my coffee yet)
>
> Are you saying that you?re using Metaswitch MaX UC and you?re doing a SIP OPTIONS message every 49 seconds?
> I totally agree it does sound like a NAT pinhole is closing. It would seem that if that?s the case, Meta would have run into this before and had ?recommendations? to address this.
> I?ll bounce your thoughts off of them.
>
> Thanks!
>
> Mark
>
>
>
>
>
> From: Dovid Bender <dovid at telecurve.com>
> Sent: Thursday, June 10, 2021 8:47 AM
> To: Mark Wiles <mwiles at akabis.com>
> Cc: voiceops at voiceops.org
> Subject: Re: [VoiceOps] "Timeout" on VoIP call traversing Verizon data
>
> If I had to guess Verizon is using CGNAT and since there is no traffic for X amount of time the NAT hole for the SIP traffic is closed. When you send a re-invite at the 30 minute mark that session as far as Verizon's CGNAT devices are concerned have been closed a long time ago. You would need to send a packet to the phone or have the phone send to your switch some sort of traffic (we send SIP OPTIONS every 49 seconds) to ensure that the session stays alive.
>
>
>
> On Wed, Jun 9, 2021 at 3:27 PM Mark Wiles <mwiles at akabis.com<mailto:mwiles at akabis.com>> wrote:
> If there?s a Verizon cellular data guru monitoring here, I?d love to get your insight!
>
> Otherwise, let me toss this out to the group for thoughts and opinions please?
>
> We?re a Metaswitch shop, and use their MaX UC mobile softphone client (iPhone/Android).
>
> We had a customer using the MaX UC client on a long call? they were using Verizon cellular data (confirmed by IP address).
> At thirty (30) minutes into the call, the call ?dropped?. The call was re-established, and again, after thirty minutes, the call dropped.
> We?re pretty sure the user was in a static position (non-mobile)? and logically assume they were on the same cell tower for both calls that dropped (the Verizon IP was the same).
>
> Looking at Metaswitch SAS (their diagnostics tool), at the thirty minute mark, we send out a re-INVITE message to the softphone client? and we receive no reply? so after ten seconds, we breakdown the call assuming they?re gone. Then about eight seconds later, we see an INVITE message from the softphone?s same IP address (with the same Call ID)? however, it?s coming from a different port. So to be clear, the original call setup and connection was using 1.2.3.4:6789? then eight seconds after we ended the call with a BYE (assuming they were gone due to lack of reply), we get an INVITE (with the same Call ID) from 1.2.3.4:9876<http://1.2.3.4:9876>.
>
> Metaswitch looked at the diags from the softphone (we downloaded them), and they?re confirming that the softphone never received our re-INVITE at the 30 minute mark.
>
> Metaswitch also looked at the bug/crash logs on the softphone, and confirmed neither was the case.
>
> It almost sounds like a NAT thing going on? but I?m pretty ignorant when it comes to cellular data. It looks to me as if the Verizon side simply changed port numbers, and assumed we?d know maybe via mental telepathy? ?
>
> Has anyone had experience with such an occurrence? or any thoughts?
>
> Thank you!
>
> Mark
>
>
>
>
>
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
> https://puck.nether.net/mailman/listinfo/voiceops<https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fpuck.nether.net%2fmailm…>
>
---------------------------------------------------------------------------
Peter Beckman Internet Guy
beckman at angryox.com http://www.angryox.com/
---------------------------------------------------------------------------
June 10, 2021