@ing-joserivera26 said in VitalPBX 3:
I will not continue posting on your blog.
This is not my blog. This is an public community targeting IT professionals.
I would (and have) posted on the VitalPBX community, but it seems that i'm eternally moderated.
@MontesVitalPBX said in VitalPBX 3:
@JaredBusch Hey, sorry I never got the email for this mention. We are looking into your post, but cannot find it. It appears that your account was not verified So that is why moderation was needed, but we weren't able to find your post. I have gone ahead and verified your account so you should be able to post once again. Now, it would be good if you can try again, so we can solve it, and continue running your issues on the VitalPBX forum so our support and dev team can take a look into it.
Moderated again..
@ing-joserivera26 said in VitalPBX 3:
@JaredBusch This is required depending on the type of authentication you are implementing. I guess that when you use user, password, and registration you don't need to define this parameter.
Except the point of making a GUI is not to make your users understand Asterisk requirements. The GUI should "know" these things.
This is why FreePBX disables the username and secret fields if you say no auth.
It is also why it automatically populates the match with the host unless you manually go to "advanced" settings and override it.
Stop being a butt hurt asshole because someone said things about your precious toy that you don't like.
No one said VitalPBX is a crappy piece of shit that should never be considered.
@ing-joserivera26 said in VitalPBX 3:
@JaredBusch As I told you, you can try putting srv.skyetel.com in the match field. You need to define the match parameter because is part of the identify section. You can put IP addresses or domains.
If it must be defined (which it must be), then VitalPBX should not accept it empty.
Or VitalPBX should automatically populate it behind the scenes with the host information as that is all that is known.
@ing-joserivera26 said in VitalPBX 3:
@JaredBusch In that case you must put the host in the match field. I guess you must put: srv.skyetel.com
Ou of date. That is from before the NA region even existed.
term.skyetel.com does not have SRV records.
srv.skyetel.com does not (or did not used to) have A records.
na.skyetel.com has both A records and SRV records.
@ing-joserivera26 said in VitalPBX 3:
You've created a tutorial for FPBX, and you defined the match field also as you did on VitalPBX. So, I guess that's the right process.
Nice try. That was before I spoke with the FreePBX developers about the subject. Try noting the date on that post.
@ing-joserivera26 said in VitalPBX 3:
@JaredBusch Match is required for incoming authentication. The remote host is for outbound calls.
I know what the fields are for.
Your link to the Asterisk github clearly tells you that it should work as I describe.
If the system was properly doing the SRV lookup, it should see these 4 addresses.
As soon as I remove them, the inbound options from Skyetel for keep alive fail.
@ing-joserivera26 Until I added the IP in the match, the Skyetel dashboard was showing the PBX offline and would not send calls.
If it is doing an SRV lookup, it is failing to do something right.
@MontesVitalPBX said in VitalPBX 3:
@JaredBusch Hey, sorry I never got the email for this mention. We are looking into your post, but cannot find it. It appears that your account was not verified So that is why moderation was needed, but we weren't able to find your post. I have gone ahead and verified your account so you should be able to post once again. Now, it would be good if you can try again, so we can solve it, and continue running your issues on the VitalPBX forum so our support and dev team can take a look into it.
I'll repost in a bit.
Just discovered that VitalPBX does not make use of SRV records, which is annoying.
Setup the PJSIP trunk to Skyetel and put in only na.skyetel.com for the host.
Calls would not terminate until I manually added all of the addresses in match. 
@Skyetel I can switch my personal account to registration. Or some spare numbers on our company account. I don't have a "spare" system that will get calls though. So if you can have registration from the same IP as a current endpoint, I can actually do it and have traffic.
Otherwise, it will be sporadic traffic from my personal account, currently hooked up to a VitalPBX instance I am testing.
I go back to the VitalPBX community today. and my post is gone.
So why should I look into this solution more?
@Pete-S yeah, there are plenty of things you can add to secure things. But like everything, you can’t fix stupid.
@siringo said in What Are You Doing Right Now:
holiday today for a sports match that isn't playing here this weekend.
good for those who get paid, not so good for us self employed types.
I schedule backup verifcation on days like that. Restore a back to an offline network etc.
@Skyetel said in SIP Registration:
What have you guys had experience with, what suggestions or ideas do you have?
Really, the only good thing about registration is when you have an on prem device. Registration will let you get around needing to open firewall ports.
@Skyetel said in SIP Registration:
We are worried about fraud risk with SIP Registration.
A valid worry as highlighted by the "admin" that posted here
@Skyetel said in SIP Registration:
We have not decided on the Registration timeouts - some carriers enforce a full 1800 seconds and won't let you re-register faster than that. We're leaning toward a 6 minute Registration timeout, and providing guidance that you should re-register every 5 mins.
FreePBX and VitalPBX both default to 3600 seconds (1 hour). So going less than that will lead to support calls from "admins" that don't RTFM.
@Skyetel said in SIP Registration:
We have not decided yet if we want to add registration to all 4 of our regions, or only support it in two.
You chose two just to have some kind of flexible path without having the complexity of making people set up 4 trunks?
Stick with 2 IMO.
@Skyetel said in SIP Registration:
We have not decided if we want to include SIP Registration in our SLA or leave it as a "Best effort" service. (TBH, I'm leaning toward including it in the SLA)
Absolutely leave it best effort. Registration is a legacy idea IMO.
@AdamF said in What Are You Doing Right Now:
@JaredBusch said in What Are You Doing Right Now:
RHEL 8 upstream for the Sangoma OS and PHP 7.
Nice! When will FPBX 16 be released? Will it be on Asterisk 16 or the new 18?
First half of '21 is what was said in chat.
Asterisk 17 is in FreePBX right now. Has been for quite a while.
@Dashrender said in VitalPBX and Microsoft 365:
@JasGot said in VitalPBX and Microsoft 365:
@Dashrender said in VitalPBX and Microsoft 365:
@JasGot said in VitalPBX and Microsoft 365:
@coliver Click a phone number in Outlook Contacts and have it dial the phone.
The phone on your desk, or a softphone?
Deskphone.
Interesting - Scott's above link leads you to software that should do this for you. I'll be trying it tomorrow... I have a few users that might like this.
This is standard click to call plug-in and not a new thing
@Dashrender said in Amazon Prime Day - Oct 2020:
1" - HAHA, so it's $770 for 57 square feet in reality.
umm wut?
You don't make it thicker than that in general.
You can go to 2", but this product is not designed to be the only insulation.
@scottalanmiller said in VitalPBX and Microsoft 365:
@JaredBusch said in VitalPBX and Microsoft 365:
@scottalanmiller said in VitalPBX and Microsoft 365:
@Dashrender said in VitalPBX and Microsoft 365:
and I read it completely differently... then again, when I saw this used 20 years ago, it was to make my deskphone dial, not the softphone... so I figured I'd ask.
That's the assumption, yes, that it is your physical desk phone hardware.
but it doesn't matter. because softphone or deskphone.. it is still your extension that it should be dialing.
Not call TO you, to initiate a call FROM you.
Right. The PBX initiates a call to your extension, and once you pickup initiates a call to whoever you are calling and then bridges the two channels.
@black3dynamite said in Roaming Profiles killing local copy:
@Dashrender said in Roaming Profiles killing local copy:
@travisdh1 said in Roaming Profiles killing local copy:
@flaxking said in Roaming Profiles killing local copy:
Just wondering if any of you with more experience with Roaming Profiles can explain this behaviour.
There's an old Roaming Profiles set-up that's been dragged along through the years and we're wanting to senset it.
One thing we're seeing is that for users who's roaming Profiles write-back haven't been working, (maybe permission error on some files) if we do something that might trigger it to star working again (like add folder exclusion), their local profile gets nuked.
It seems like this is only an issue with roaming Profiles that haven't been working, if they've been working, any changes we've made hadn't had the affect off killing the local profile and starting fresh.
I've check for any GPO settings that might be asking for the local profile to be deleted, but I haven't found anything. From what I understand, the profiles should only be merging.
Has anyone else seen behaviour like this before where a roaming profile goes from not working to working and it kills the local copy?
It's been a long, long time since I touched anything with roaming profiles. Just about everyone uses redirected folders now if they need that sort of functionality, and this is one of the reasons. Roaming profiles just proved very buggy historically.
man, I dislike redirecting things like the desktop... it's no longer a local folder and makes using it as a scratch pad super slow...
Ever since I embraced using OneDrive and Nextcloud, I would use junctions points. Folders like Desktop, Documents and so on would be stored in the OneDrive or Nextcloud folder and then I would use junction points. The user shell folders paths will still stay the same.
This is what I do.
@scottalanmiller said in VitalPBX and Microsoft 365:
@Dashrender said in VitalPBX and Microsoft 365:
and I read it completely differently... then again, when I saw this used 20 years ago, it was to make my deskphone dial, not the softphone... so I figured I'd ask.
That's the assumption, yes, that it is your physical desk phone hardware.
but it doesn't matter. because softphone or deskphone.. it is still your extension that it should be dialing.
RHEL 8 upstream for the Sangoma OS and PHP 7.
) feedback.
