@hubtechagain said in SIP registrations failing for 2 phones:

their bridge mode isn't a true bridge either. just FYI

Right. I was reading up on that a bit. People seem to call it a "pseudo bridge mode."

@JaredBusch said in Vitelity inbound calling is failing:

@fuznutz04 said in Vitelity inbound calling is failing:

@JaredBusch Good idea to manually down the trunk. However, I think you're right, Not sure if it would have done anything as the calls were coming into Vitelity but then not working 100% Such a random event.

I've had decent luck with Vitelity so far. Let's hope this is just a special case.

I quit using Vitelity because of these types of issues repeatedly happening a few times a year.

You typically use voip.ms right?

@JaredBusch Good idea to manually down the trunk. However, I think you're right, Not sure if it would have done anything as the calls were coming into Vitelity but then not working 100% Such a random event.

I've had decent luck with Vitelity so far. Let's hope this is just a special case.

Official response on the portal:

Monday November 21st 2016, 11:18am MST - Vitelity noticed several large loops that caused one of our inbound processing nodes to become overloaded. Vitelity worked with our vendor to block the loops and harden the routing policies to the Vitelity network. If you experience anything further open a support ticket.

Looks like it is back up in this area. This brings up the topic of inbound calling failover. In this case, the call technically wasn't "failing" due to the provider not being able to connect to the PBX. The call was failing because of other issues, but not failing "enough" to be considered a failed call, where the call would failover to a backup number. So it begs the question... how is this avoidable or at the very minimum, mitigated to some degree?

So sounds like regional. Their outage banner just says " reports of inbound calling issues ". No further info from their phone support people.

Lancaster PA Area

@Minion-Queen I have 2 so far

Looks like inbound calls make it to the Pbx, but no audio is passing through.

Vitelity inbound calling is not working . Is there another outage somewhere that anyone knows about?

@JaredBusch

True. I didn't because there were people on the phone at the time.

Big lessons learned here with Comcast equipment. Hopefully I don't run into this again but if I do, lots of notes were taken.

Thanks everyone for helping to think through this one with me.

So finally go this working earlier today. At one point, as I was scratching my head, everything started working. The only thing that I changed today on the Comcast gateway was a setting that was under "True Static IP Port Management."

The option to "disable all rules and allow all inbound traffic through."

I checked this box, and nothing changed. Then without doing anything else on the Comcast box, or the ERL, about 20 minutes later, all the phones started functioning properly.

@JaredBusch

Excellent. So then the only entries needed would be any device that has a static IP address.

EdgeOS is getting better all the time.

@JaredBusch

I will still need to put in static entries, even though I enable this ?

set service dhcp-server use-dnsmasq enable

@Dashrender said in WINs/DNS on Edge Router:

@fuznutz04 said in WINs/DNS on Edge Router:

@scottalanmiller said in WINs/DNS on Edge Router:

@fuznutz04 said in WINs/DNS on Edge Router:

@Dashrender said in WINs/DNS on Edge Router:

WINS eh? I seriously doubt it.

You have apps that are still relying on NetBIOS for something? Can't solve this with DNS?

It's a copier that is trying to access by computer name. I guess a simple solutions would just be to change the copier to use IPs instead.

The copier is trying to use NetBIOS instead of DNS? Are you positive? That's so incredibly unlikely, I've never heard of that scenario before.

The copier was set to use \computername\scan as a location to send files for the "scan to PC" function. It wasn't resolving properly after I installed the ERL.

What was doing DNS resolution before the ERL? I'm guessing it was using broadcasting, though I don't know why the ERL would stop that part from working.

The only thing in place prior to the ERL was the Comcast gateway device which was also handing out DHCP to the internal LAN.

@scottalanmiller said in WINs/DNS on Edge Router:

@fuznutz04 said in WINs/DNS on Edge Router:

@Dashrender said in WINs/DNS on Edge Router:

WINS eh? I seriously doubt it.

You have apps that are still relying on NetBIOS for something? Can't solve this with DNS?

It's a copier that is trying to access by computer name. I guess a simple solutions would just be to change the copier to use IPs instead.

The copier is trying to use NetBIOS instead of DNS? Are you positive? That's so incredibly unlikely, I've never heard of that scenario before.

The copier was set to use \computername\scan as a location to send files for the "scan to PC" function. It wasn't resolving properly after I installed the ERL.

@JaredBusch said in WINs/DNS on Edge Router:

@fuznutz04

TO be clear, this is how your DNS should be set up in your EdgeRouter.

configure
# proper EdgeOS DNS configuration assuming eth1 is your LAN
set service dns forwarding listen-on eth1
set service dns forwarding cache-size 150
set system name-server 127.0.0.1
# Change the forwarding DNS to whoever you prefer for DNS lookups. 
# The example here is Google DNS
set service dns forwarding name-server 8.8.8.8
set service dns forwarding name-server 8.8.4.4
# make sure your router has a domain name listed, even if your stuff is on a workgroup. 
# I like to use the full MS recommended format.
set system domain-name home.jaredbusch.com
commit
save
exit

Now you can setup any static host mappings you want as I listed in the prior post.
Obviously change these appropriately.

set system static-host-mapping host-name ad.bundystl.com inet 10.254.0.21
set system static-host-mapping host-name bundydemo.bundystl.com inet 10.254.0.28
set system static-host-mapping host-name bundyhv01 inet 10.254.0.20

If you have your firmware updated to version 1.9.0 then you can use DNSMasq also to get better lookup from DHCP assigned stuff, if your EdgeRouter is also the DHCP server.

configure
set service dhcp-server use-dnsmasq enable
commit
save
exit

Great guide and feedback, thanks. I left before I saw this second post, but I did setup the static entries like you mentioned in your previous post:

set system static-host-mapping host-name ad.bundystl.com inet 10.254.0.21
set system static-host-mapping host-name bundydemo.bundystl.com inet 10.254.0.28
set system static-host-mapping host-name bundyhv01 inet 10.254.0.20

Pinging names from being logged into the ERL, properly resolves now. However, pinging by name from clients was still failing. To get them working quickly, I changed the entries in the printer to just point to the IP addresses of the PCs (which as statically set by DHCP reservation.

@Dashrender said in WINs/DNS on Edge Router:

WINS eh? I seriously doubt it.

You have apps that are still relying on NetBIOS for something? Can't solve this with DNS?

It's a copier that is trying to access by computer name. I guess a simple solutions would just be to change the copier to use IPs instead.

Can the Edge Router function as a WINS server? I need to resolve IPs by hostname in a non domain environment. Can I either setup the edge router to function as a WINS server or add static entries in the edge router?

@scottalanmiller said in SIP registrations failing for 2 phones:

Basically what Comcast is telling you is that they don't have any business offering.

Which is a joke, because it is their "business class" service. There has to be a way to bypass this. I know of others with Comcast business gateways that operate fine. I was reading many forums this evening and some people are saying that certain models of the business gateway have issues with VoIP and that I should request a new/different model from comcast.