@darek-hamann Been running Hyper-V 2016 and Server 2016 for a while but haven't tried Core/Nano.

@wls-itguy There is more than one way to skin a catfish...

@francesco-provino Makes sense then to go ahead and use fiber. You are already at 300m too. I never buy pre-term but make sure you spend the extra few dollars and have them install a pulling eye or loop for you. Makes it a lot easier.

I do this both ways but usually lean towards fiber when I can't stay far enough away from electrical conduits. A major factor with fiber is that it is immune to noise from electrical circuits and can be run very close to them. I think fiber is cheap and I don't mind working with it. Yes, you can run 10G over CAT6 and it will also work well but you are limited on distance.

My iPhone 6s is cosmetically in good shape but the battery is shot. Aftermarket batteries don't seem to hold up either. I thought about giving Android a try (again) but can't make up my mind.

Upper 70's today in the Houston area. Very nice outside right now.

@dave247 Yes. I don't remember the model before that one but it was IBM as well.

Power 720 for core as well.

@jaredbusch I will make the change later today. I would rather follow the best practices and methods. I have zero issues with that. It is definitely different than using POTS lines because that is what I was used to with legacy systems. I've learned a TON since first installing FreePBX last year. Wish I would have tried it a long time ago.

I do have caller ID specified in the trunk as it shows in my attached image above. I has not given any error messages or anything. Seems to be working correctly. What is the recommended way to handle outbound CID?

All is good now. I REALLY APPRECIATE the assistance. I wish I would have used separate trunks paths from the beginning and avoided the mess. It was a learning experience for sure. I will monitor it and see if anything changes. Again, thank you.

@jaredbusch Ok. Making those changes now.

Voip.ms is set like your example on NANPA for both trunks.

I changed the trunk to houston2 and now outbound calls are flowing..... I wish I would have known that would cause an issue. I'm learning though and that is what matters. Edit: I did change it inside voip.ms before I changed it in FreePBX. That trunk was NOT registered. It was yesterday.

@jaredbusch They just pick up the phone and dial a 10-digit number. No prefix. No special anything.

@jaredbusch There is no manipulation on the trunk.

Ok... I will do that now. I will report back.

Both trunks are registered in VOIP.MS and show online in the FreePBX dashboard. Inbound calls are working with no issues.