- VoiceOps - lists.voiceops.org

Carrier Robocall Blocking
by calvin.ellison＠voxox.com May 27, 2020

May 27, 2020

What solutions are people using to stop robocalls at the carrier level? We're dealing with aggregator and international gateway traffic that sometimes needs aggressive filtering. Regards, *Calvin Ellison* Senior Voice Operations Engineer calvin.ellison at voxox.com

2 2

Canadian Mobile/Landline TN lookup
by ivan.kovacevic＠startelecom.ca May 21, 2020

May 21, 2020

Anyone have an idea on where/how to find accurate near-real time TN lookups for Canada to determine whether a number is mobile or landline? As a blunt tool, we have used NPA-NXX/X ranges but this doesn't cover ported numbers, which is what we are after for a client. Thanks in advance! Ivan -- NOTE: This email message and any attachments are for the sole use of the intended recipient(s) and may contain confidential and/or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by replying to this email, and destroy all copies of the original message.

2 2

Inteliquent contact
by nathana＠fsr.com May 19, 2020

May 19, 2020

Is there anybody from Inteliquent subscribed to this list who wouldn't mind reaching out to me off-list? Specifically looking for someone knowledgeable about port-ins, IQ's voice network, and its coverage, and the subject is of a time-sensitive nature. I have tried reaching out to a couple of contacts I've been pointed to by others outside of their org, but have received zero responses. Thanks much, -- Nathan Anderson First Step Internet, LLC nathana at fsr.com

2 1

Three Digit Numbers
by voiceops＠ics-il.net May 15, 2020

May 15, 2020

What three digit numbers are commonly in use and how are people routing them? Obviously there's 911 and that has a whole routing ecosystem. What about 811? 311? X11? What other special numbers are people handling? ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com

18 33

Fwd: 911 and Softphones
by voiceops＠ics-il.net May 15, 2020

May 15, 2020

The pitfalls of having my email address mirror the mailing lists I'm on, I get list submissions. :-) ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com ----- Original Message ----- From: "Christopher Aloi" <ctaloi at gmail.com> To: voiceops at ics-il.net Sent: Thursday, May 14, 2020 9:39:41 AM Subject: 911 and Softphones Hey All, With the recent migration to everyone working from home we are seeing a huge increase in soft phone usage. How is everyone handling location updates for 911 with soft phones? Our switch has the concept of sites and users fall within a site but can also travel across sites. An out pulsed number is bound to the site when 911 is dialed from within the site. We are looking at building individual sites for each user so they can have a dedicated unique outbound number only for 911. Does your company consider a soft phone the same as a "hard" phone with regards to 911? From the reading I have done I see no delineation between the two. Thanks, Chris

8 10

Toll Free Caller ID
by calvin.ellison＠voxox.com May 14, 2020

May 14, 2020

It looks like Somos is pushing TFN CNAM, press release below from Mar 30, 2020. I've always understood TF ANI to be invalid. What's the news on using TFN as a caller ID? Does this require a local charge number in P-Charge-Info or P_Asserted_Identity or elsewhere? Has the FCC or anyone else approved TFN as ANI? Is TF ANI supported for STIR/SHAKEN? https://www.prnewswire.com/news-releases/toll-free-caller-id-information-he… Regards, *Calvin Ellison* Senior Voice Operations Engineer calvin.ellison at voxox.com

4 5

Analog Phone Lines - Timesouce for PBX System
by colton.conor＠gmail.com May 14, 2020

May 14, 2020

We had a customer that had Frontier Analog phone lines going into their Panasonic TDA-50 PBX system. We recently ported the numbers from Frontier to our Broadsoft, and deployed a Poly OBI508 ATA onsite. We also replaced their router and internet connection. Customer is complaining that their phones are displaying the wrong time. We explained to them that we did not mess with their phone system PBX only the input lines. My question is, do oldschool, onsite PBX systems, like a Panasonic TDA-50, use the analog FXS input lines from the provider (us) as a timing source? If so, what protocol is this, and where would be change it on the adapter? I would think most PBX systems are like computers, and would use NTP as the timing source.

4 4

One device’s TCP SIP and UDP RTP audio leaving wireless carrier from different IP addresses?
by SVentura＠allworx.com May 5, 2020

May 5, 2020

Hello! Several users of our product have reported no audio when using our VoIP mobile app on cellular networks. Our server product and our mobile app rely on the TCP SIP socket?s source address being the same as the audio?s source address. When the addresses don?t match, the server has no way to know the two addresses are a single device. We have a packet capture from one user?s server that shows a single mobile device communicating from two different IP addresses: one for the TCP SIP connection (166.181.252.181), and a second one for the UDP RTP audio (166.181.255.39). In this capture, our server sends audio to 166.181.252.181 and discards the inbound audio from 166.181.255.39. The port numbers in the audio packets from the 39 address match the port numbers negotiated over the TCP connection with the 181 address, which is why I believe them to be the same device. We retested today with the same customer device but connecting to a different server. In today?s test, the capture shows that the TCP SIP connection arrived from 166.181.251.203 and the UDP RTP arrived from 166.181.255.32. All of these addresses are in a block assigned to ?Wireless Data Service Providers' Corporation (SPCo)?. The user reports their carrier as US Cellular, which is a voting member of SPCo. Does anyone have a technical contact at US Cellular we can ask about this? Has anyone observed this multiple-address NAT being employed by other service providers? Thank you! Scott Ventura Senior Software Engineer Allworx This email message and any attachments are for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message and any attachments.

2 1

One device’s TCP SIP and UDP RTP audio leaving wireless carrier from different IP addresses?
by clintm＠ringcentral.com May 5, 2020

May 5, 2020

That?s odd. Never seen it before. What happens if you switch the SIP transport to UDP? Sounds like the carrier may be struggling to keep up with NAT overload demands on their network. From: VoiceOps <voiceops-bounces at voiceops.org> on behalf of "Ventura, Scott D" <SVentura at allworx.com> Date: Tuesday, May 5, 2020 at 2:23 PM To: "voiceops at voiceops.org" <voiceops at voiceops.org> Subject: [VoiceOps] One device?s TCP SIP and UDP RTP audio leaving wireless carrier from different IP addresses? [EXTERNAL] Hello! Several users of our product have reported no audio when using our VoIP mobile app on cellular networks. Our server product and our mobile app rely on the TCP SIP socket?s source address being the same as the audio?s source address. When the addresses don?t match, the server has no way to know the two addresses are a single device. We have a packet capture from one user?s server that shows a single mobile device communicating from two different IP addresses: one for the TCP SIP connection (166.181.252.181), and a second one for the UDP RTP audio (166.181.255.39). In this capture, our server sends audio to 166.181.252.181 and discards the inbound audio from 166.181.255.39. The port numbers in the audio packets from the 39 address match the port numbers negotiated over the TCP connection with the 181 address, which is why I believe them to be the same device. We retested today with the same customer device but connecting to a different server. In today?s test, the capture shows that the TCP SIP connection arrived from 166.181.251.203 and the UDP RTP arrived from 166.181.255.32. All of these addresses are in a block assigned to ?Wireless Data Service Providers' Corporation (SPCo)?. The user reports their carrier as US Cellular, which is a voting member of SPCo. Does anyone have a technical contact at US Cellular we can ask about this? Has anyone observed this multiple-address NAT being employed by other service providers? Thank you! Scott Ventura Senior Software Engineer Allworx This email message and any attachments are for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message and any attachments.

1 0

Yealink/Crestron
by ryan＠finnesey.com May 2, 2020

May 2, 2020

I wanted to get some feedback from the group regarding Yealink and Crestron Phones. Curious to know your experiences deploying the phones and working with the two companies Cheers Ryan

1 0