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
June 2021
- 31 participants
- 107 messages
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
"Timeout" on VoIP call traversing Verizon data
by ptimmins@clearrate.com
Perimeta's fast register causes it to refresh faster than once a minute.
It doesn't log this in the SAS, but there's a way to verify at the
perimeta CLI it's occurring. You might want to have your SE verify that
the subscriber is being detected properly as NAT when on the verizon
towers, and if not, possibly just force nat all the time on max-uc
(since it's really rare there will be a max-uc session that's NOT behind
a nat)
On 6/10/21 2:30 PM, Mark Wiles wrote:
>
> Since I?m as dumb as a bag of hammers when it comes to cellular data?
> what do you think the NAT timeout might standardly be, before the
> pin-hole goes away?
>
> Strange we?ve not run into this before.
>
> *From:* VoiceOps <voiceops-bounces at voiceops.org> *On Behalf Of *Paul
> Timmins
> *Sent:* Thursday, June 10, 2021 11:12 AM
> *To:* voiceops at voiceops.org
> *Subject:* Re: [VoiceOps] "Timeout" on VoIP call traversing Verizon data
>
> The perimeta should auto-detect the NAT and start a "fast register" in
> their parlance. You might want to look into this and possibly force
> nat on your MaXUC instead of using nat autodetect, and make sure fast
> register is configured. It will handle keeping the signaling portion
> open for you.
>
> https://community.metaswitch.com/support/solutions/articles/76000007855-pro…
> <https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fcommunity.metaswitch.co…>-
>
> On 6/10/21 9:18 AM, 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>
> <mailto:dovid at telecurve.com>
> *Sent:* Thursday, June 10, 2021 8:47 AM
> *To:* Mark Wiles <mwiles at akabis.com> <mailto:mwiles at akabis.com>
> *Cc:* voiceops at voiceops.org <mailto: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…>
>
>
>
> _______________________________________________
>
> 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…>
>
> --
> Paul Timmins
> Clear Rate Communications
> Direct: (248) 556-4532
> Customer Support: (877) 877-4799
> 24 Hour Repair: (866) 366-4665
> Network Operations: (877) 877-1250
> www.clearrate.com <https://linkprotect.cudasvc.com/url?a=http%3a%2f%2fwww.clearrate.com&c=E,1,…>
> This message contains confidential information intended only for the use of the intended recipient(s) and may contain information that is privileged. If you are not the intended recipient, or the person responsible for delivering it to the intended recipient, you are hereby notified that reading, disseminating or copying this message is strictly prohibited.
> If you have received this message by mistake, please immediately send notification by replying to the message, indicate the message was received by mistake, and then delete the original message immediately thereafter. Thank you.
> Clear Rate Communications, Inc. 2600 W Big Beaver, Suite 450, Troy, MI 48034.
--
Paul Timmins
Clear Rate Communications
Direct: (248) 556-4532
Customer Support: (877) 877-4799
24 Hour Repair: (866) 366-4665
Network Operations: (877) 877-1250
www.clearrate.com
This message contains confidential information intended only for the use of the intended recipient(s) and may contain information that is privileged. If you are not the intended recipient, or the person responsible for delivering it to the intended recipient, you are hereby notified that reading, disseminating or copying this message is strictly prohibited.
If you have received this message by mistake, please immediately send notification by replying to the message, indicate the message was received by mistake, and then delete the original message immediately thereafter. Thank you.
Clear Rate Communications, Inc. 2600 W Big Beaver, Suite 450, Troy, MI 48034.
June 10, 2021
USF is 33.4% for 2Q2021
by beckman@angryox.com
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
"Timeout" on VoIP call traversing Verizon data
by mwiles@akabis.com
Since I?m as dumb as a bag of hammers when it comes to cellular data? what do you think the NAT timeout might standardly be, before the pin-hole goes away?
Strange we?ve not run into this before.
From: VoiceOps <voiceops-bounces at voiceops.org> On Behalf Of Paul Timmins
Sent: Thursday, June 10, 2021 11:12 AM
To: voiceops at voiceops.org
Subject: Re: [VoiceOps] "Timeout" on VoIP call traversing Verizon data
The perimeta should auto-detect the NAT and start a "fast register" in their parlance. You might want to look into this and possibly force nat on your MaXUC instead of using nat autodetect, and make sure fast register is configured. It will handle keeping the signaling portion open for you.
https://community.metaswitch.com/support/solutions/articles/76000007855-pro…<https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fcommunity.metaswitch.co…>-
On 6/10/21 9:18 AM, 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><mailto:dovid at telecurve.com>
Sent: Thursday, June 10, 2021 8:47 AM
To: Mark Wiles <mwiles at akabis.com><mailto:mwiles at akabis.com>
Cc: voiceops at voiceops.org<mailto: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…>
_______________________________________________
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…>
--
Paul Timmins
Clear Rate Communications
Direct: (248) 556-4532
Customer Support: (877) 877-4799
24 Hour Repair: (866) 366-4665
Network Operations: (877) 877-1250
www.clearrate.com<https://linkprotect.cudasvc.com/url?a=http%3a%2f%2fwww.clearrate.com&c=E,1,…>
This message contains confidential information intended only for the use of the intended recipient(s) and may contain information that is privileged. If you are not the intended recipient, or the person responsible for delivering it to the intended recipient, you are hereby notified that reading, disseminating or copying this message is strictly prohibited.
If you have received this message by mistake, please immediately send notification by replying to the message, indicate the message was received by mistake, and then delete the original message immediately thereafter. Thank you.
Clear Rate Communications, Inc. 2600 W Big Beaver, Suite 450, Troy, MI 48034.
June 10, 2021
"Timeout" on VoIP call traversing Verizon data
by pete@mac.geek.nz
49 seconds... how trusting! ;-)
We use 25.
Pete
(it's true, but said tongue-in-cheek as I'm sure you have your data to show where the bulk of NATs expire)
> On 11/06/2021, at 12:46 AM, Dovid Bender <dovid at telecurve.com> wrote:
>
> <snip> (we send SIP OPTIONS every 49 seconds) to ensure that the session stays alive.
June 10, 2021
"Timeout" on VoIP call traversing Verizon data
by mwiles@akabis.com
Paul, that was my thought on the Perimeta.
So far, we?ve only had two calls that this issue occurred on? but honestly, not sure how many have 30+ minutes calls on their softphone.
I just wonder if this was kind of a one-off issue with a specific Verizon cell?
From: VoiceOps <voiceops-bounces at voiceops.org> On Behalf Of Paul Timmins
Sent: Thursday, June 10, 2021 11:12 AM
To: voiceops at voiceops.org
Subject: Re: [VoiceOps] "Timeout" on VoIP call traversing Verizon data
The perimeta should auto-detect the NAT and start a "fast register" in their parlance. You might want to look into this and possibly force nat on your MaXUC instead of using nat autodetect, and make sure fast register is configured. It will handle keeping the signaling portion open for you.
https://community.metaswitch.com/support/solutions/articles/76000007855-pro…<https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fcommunity.metaswitch.co…>-
On 6/10/21 9:18 AM, 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><mailto:dovid at telecurve.com>
Sent: Thursday, June 10, 2021 8:47 AM
To: Mark Wiles <mwiles at akabis.com><mailto:mwiles at akabis.com>
Cc: voiceops at voiceops.org<mailto: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…>
_______________________________________________
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…>
--
Paul Timmins
Clear Rate Communications
Direct: (248) 556-4532
Customer Support: (877) 877-4799
24 Hour Repair: (866) 366-4665
Network Operations: (877) 877-1250
www.clearrate.com<https://linkprotect.cudasvc.com/url?a=http%3a%2f%2fwww.clearrate.com&c=E,1,…>
This message contains confidential information intended only for the use of the intended recipient(s) and may contain information that is privileged. If you are not the intended recipient, or the person responsible for delivering it to the intended recipient, you are hereby notified that reading, disseminating or copying this message is strictly prohibited.
If you have received this message by mistake, please immediately send notification by replying to the message, indicate the message was received by mistake, and then delete the original message immediately thereafter. Thank you.
Clear Rate Communications, Inc. 2600 W Big Beaver, Suite 450, Troy, MI 48034.
June 10, 2021
USF is 33.4% for 2Q2021
by edguy@eguy.org
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..)
Thanks
Ed
?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
> <mailto: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.
> >
> > -- Alex
> >
> 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.
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
> https://puck.nether.net/mailman/listinfo/voiceops
> <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/
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
June 10, 2021
USF is 33.4% for 2Q2021
by abalashov@evaristesys.com
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
> <mailto: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.
> >
> > -- Alex
> >
> 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.
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
> https://puck.nether.net/mailman/listinfo/voiceops
> <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 caalvarez@gmail.com
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.
> >
> > -- Alex
> >
> 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.
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
June 10, 2021