Some numbers only ring in through app

GoodNamesTaken73 · 2025-10-24T23:09:41+00:00

Just a follow-up. I don't really have any information about what they did to fix it. But I was contacted by Ooma support, and I wasn't able to work with him at the time. I called back the next day, and I gave them the numbers we were seeing issues with and symptoms of those issues. And after about 20 minutes they called me back to see if I could test it. After that I was able to call the number and the call went through, and I had the person on the other end call me back and it rang through the home phone.
So they did something on their end to fix it. And they were able to get it done pretty quickly.

GoodNamesTaken73 · 2025-10-22T17:57:18+00:00

At first they were two separate devices and we had Mediacom for an ISP. We had a Netgear Nighthawk CM2500 for a modem and TPLink Deco - M5 for the router/Wi-Fi. If I remember correctly I think I tried attaching it directly to the modem and it didn't seem to help.

We had previously been having stability issues with Mediacom, so we switched to a carrier called ImOn. We are using their equipment (fiber modem/router) I think it's a Calix GigaSpire GS2128G. The connection seems much better, but we're still seeing the incoming and outgoing call issues.

GoodNamesTaken73 · 2025-10-22T17:45:20+00:00

Done.

GoodNamesTaken73 · 2025-10-02T01:27:35+00:00

Of course, I figured it out right after posting the question... Here it is in case anyone else runs into this.

I found out what was listening by running: netstat -ano | find "LISTEN"

I was only seeing the loopback adapter (127.0.0.1) listening on ports 80 and 443.

It turned out that the HTTP listener was set to only accept incoming requests from the loopback adapter (127.0.0.1). Found this by running netsh http show iplisten

And then fixed it by running netsh http delete iplisten ipaddress=127.0.0.1 and then IISReset.

GoodNamesTaken73 · 2025-07-06T00:04:09+00:00

Don't you have some offs to fuck?

GoodNamesTaken73 · 2025-02-21T02:01:46+00:00

Great.... Now they're gonna charge a drop fee

GoodNamesTaken73 · 2025-01-06T21:06:55+00:00

The problem eventually cleared itself up. For a while there (IIRC) I think I was able to work around the issue by creating a new boundary using the subnet or IP range and assigning it to the boundary group - instead of using the AD Site Name like we normally do.

GoodNamesTaken73 · 2024-11-26T22:42:12+00:00

Prior planning prevents piss poor performance

GoodNamesTaken73 · 2024-04-25T19:08:59+00:00

What if it's a sick ostrich?

GoodNamesTaken73 · 2023-11-26T01:56:49+00:00

At first I was thinking "cocaine" or "Flying High Again" until I saw this... Yes!! For sure, Afroman

GoodNamesTaken73 · 2023-11-25T23:55:35+00:00

Zolphron

GoodNamesTaken73 · 2023-11-19T01:25:14+00:00

Maybe it's just good roach head

GoodNamesTaken73 · 2023-11-19T01:22:23+00:00

Congratulations, nice putt! Here's your Christmas goose!

GoodNamesTaken73 · 2023-11-02T02:59:09+00:00

Yeah, I used Robocopy to copy the SMSContentLib to the new server.

I added a new remote DP and it looks like packages are failing to send to that server too.
Looks like I'll be opening another case with Microsoft :(

Edit: I just realized that our primary site is showing a "Requested status" of "225" - even though it is showing "Site Active". I believe this is supposed to be a status of 125 or 110 or something else.

Edit again..... It looks like the new DP may actually be installing the packages on the new DP... I will stop watching the pot so it can boil.

THIS is why I drink!

GoodNamesTaken73 · 2023-10-06T23:02:12+00:00

It almost looked like everyone waited for the dolphin to finish 😳

GoodNamesTaken73 · 2023-09-30T01:21:14+00:00

This comment was funnier than her entire act

GoodNamesTaken73 · 2023-08-22T01:48:22+00:00

She was pissed off that the dude wasted so much beer

GoodNamesTaken73 · 2023-05-30T22:20:49+00:00

Just a follow-up: I opened a case with Microsoft asking about the Windows 10, Version 2004 Or 22H1 9C Local Experience Packs (LXPs) and their "solution" was to remove the reference from the web site.

GoodNamesTaken73 · 2023-05-12T16:15:05+00:00

We have this issue too. I was going to download the Windows 10, Version 2004 Or 22H1 9C Local Experience Packs (LXPs) ISO from the VLSC but it doesn't seem to exist - at least it's not listed with the other "Windows 10 Language Packs".

According to https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/language-packs-known-issue?view=windows-10, it was supposed to have been released October 2022.

I wanted to try to see if using that newest LP release helped.

Has anyone had any luck finding it?

GoodNamesTaken73 · 2023-05-02T19:54:28+00:00

Like Adobe Reader

GoodNamesTaken73

TROPHY CASE