I have an account with them from when I used to do a lot of repairs and they have pretty decent service, I can usually get ~ $10 off screens since I used to do a good many.
SATA SSDs often make sense because they are cheaper and the protocol benefits of SAS really are not there in the same ways for SSDs.
So this brings up @DustinB3403 question of best practice or more aptly as you @scottalanmiller said implementation patterns - which ones as generically as you can be would go which way. I suppose it might be easier to say 'in these set of circumstances (list 1-4) you do this, generally in the rest you do that.'
Any question like this would technically be dependent on the PBX in question and could not be answered generically. That being said, I do not know of any system where this would cause a problem.
True. But a lot of email systems adopted the SPF record type and would not accept email from you if your system wasn't set up with one. I ran into that a few times before actually setting it up.
I always wondered why they just didn't use a TXT record for it, lol...
Holy crap, yeah, that's not useful at all. No wonder they do not publish the prices anywhere. The old rule of thumb applies: if the price isn't public, the price isn't good.
@scottalanmiller Yes... Everything works fine when I dialed in and pointed inbound route to an extension, rings and audio is perfect. Web interface, logs, Asterisk functions, modules loaded everything works fine. This is what confuses me the most. Unfortunately I cant just erase the entire server and start from scratch.
Sure, but this boils down to the 'You don't know what you don't know' situation.
Maybe, but you do know if you are looking for advice and engineering insight or not. If not, you have to assume that the priority was not that high. If you want a house built and feel that the design is important we all know that you high a trained architect. If not and you just want to be cheap, you just buy a book of blueprints and hope for the best. But we know what we don't know.
