@Dashrender said in Looking for a 10 inch or so android tablet:

@JaredBusch said in Looking for a 10 inch or so android tablet:

@Dashrender said in Looking for a 10 inch or so android tablet:

$250 seems pretty cheap for such a use... you expect what - 5 years out of it, so $50/year... seems reasonable.

It is. But taking 5 minutes to post a discussion was well worth it. I’ll buy an Acer also and see how it works comparatively.

Actually, depending on the possible cost savings, maybe not. If you buy two and compare them, that billable time could eat much of that savings. - Could, no idea if it will or not. Though I'll agree the post just for info sake was likely worthwhile.

$250 vs $150 is significant. I'm not talking single quantity.

@DimS said in Pitney Bowes hit by crypto:

Well, if the backups were stored off-site, a single days worth of data could have been the only loss there, which is the exact schedule they should be made for a service provider of their scale.

Hell yeah, this is a major company with gobs of customer data.

@JaredBusch

Hi

Play with this :

https://docs.saltstack.com/en/latest/ref/states/all/salt.states.win_lgpo.html

If you have windows minions and set it to run every 30/60/90 mins, and BAM you have AD without MS BS

While you can use salt grains to target OSes, I like to diffrentiate them with good naming system:

WIN.001
LIN.001
SRV.001

You might ask how to differentiate between windows SRV and Linux SRV, well frankly my dear i dont give damn, and i dont run Windows servers.

@black3dynamite said in Copy SSH public key to ssem behind a jump box:

# From your host to your JUMPBOX # Not needed if your public key is already in placed cat ~/.ssh/id_ed25519.pub | ssh jump.domain.com 'umask 0077; mkdir -p .ssh; cat >> .ssh/authorized_keys'

ssh-copy-id should do this

Ok, so junction points don't support mapping to network path, symlinks do, and hardlinks can only be created for files, not folders. Try creating symlink and then create junction to the symlink and see if Crashplan can be fooled that way. So mklink /D C:\fake-Backup \\server01\Share\Subfolder and mklink /J c:\backup c:\fake-backup .

@JaredBusch said in Skyetel support:

Never heard back from T-Mobile, but calls now connect.

Ain't that always the way.

@quintana said in First look at the Wazo Platform:

@scottalanmiller With the API?

API would be interesting. I think for most users, without an API would be the more useful guide. Both, is ideal 😉

That's been around for ages 😛

@quintana said in Wazo to sponsor Astricon 2019:

@JaredBusch I have a small demo for creating your own call control with our API. Find the source code here, it's in python, but i only use the rest api an websocket in the platform https://github.com/sboily/wazo-demo-programmable. I'm using the application API. http://www.wazo-platform.org/documentation/api/application.html#tag/applications

Will look into it later this week. thanks.

@pmoncho said in You cannot fix stupid vendors:

@Dashrender said in You cannot fix stupid vendors:

@IRJ said in You cannot fix stupid vendors:

@scottalanmiller said in You cannot fix stupid vendors:

@IRJ said in You cannot fix stupid vendors:

@JaredBusch said in You cannot fix stupid vendors:

Instead you simply refuse to purchase form them when possible. When not possible, you do the absolute minimum required to implement and keep any change documented in order to prevent stupid shit they do from coming back on IT.

This is where it is nice to have policies in place that only allow secure apps to be deployed that meet a a defined criteria. This policy is then signed by CEO and CTO. So when they want the software, you show them it doesnt meet the policy they signed and is it creates unnecessary risk

Great idea.

Another thing to write on the policy is that if there are any exceptions to this they must be signed off and documented. You will find out how quickly the c levels or even directors will not want to sign anything off and accept responsibility for the risk.

My office wouldn't care..

My guess is they don't care because there are no ramifications. Most of what I have seen is all talk and no action. Add to that, even if you show the signed sheet, blame will be shuffled on down the line.

yeah, when the owners are the shareholders, they don't have to give a shit.

Super helpful, Thanks!

For those who are curious, our international rates and their corresponding tiers are here:
https://files.skyetel.com/SkyetelHighCostPrices.xlsx

@Skyetel Do you have a blog somewhere that you do rant on STIR/SHAKEN? Even better, post it in a new thread here!

@JaredBusch said in MS SQL on Linux rpm missing in repo:

Good work Microsoft......

4fa92e0a-5451-4bf7-a310-aaad98001f48-image.png

msodbcsql17-17.4.1.1-1.x86_64. FAILED https://packages.microsoft.com/rhel/7/prod/msodbcsql17-17.4.1.1-1.x86_64.rpm: [Errno 14] HTTPS Error 404 - Not Found --:--:-- ETA Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. mssql-tools-17.4.1.1-1.x86_64. FAILED https://packages.microsoft.com/rhel/7/prod/mssql-tools-17.4.1.1-1.x86_64.rpm: [Errno 14] HTTPS Error 404 - Not Found --:--:-- ETA Trying other mirror. Error downloading packages: mssql-tools-17.4.1.1-1.x86_64: [Errno 256] No more mirrors to try. msodbcsql17-17.4.1.1-1.x86_64: [Errno 256] No more mirrors to try.

There is no 17.4 in the repo... https://packages.microsoft.com/rhel/7/prod/

Something they released and then pulled, maybe?

@cdbrush said in Setting up FreePBX to send a X-Tenant SIP header for Skyetel Tenant tracking:

This is great. Thanks.

What is this significance to the numbers within the "{OUTBOUND_ROUTE_NAME:0:4}" preceding the route name?

That’s a substring. Look at the route name, starting at character zero and going for 4 characters.

@Skyetel said in Skyetel needs to get over 11 digit numbers:

@Skyetel said in Skyetel needs to get over 11 digit numbers:

@JaredBusch said in Skyetel needs to get over 11 digit numbers:

FFS I cannot do a damned thing in their system without issues with fucking 11 digit numbers..

Today it was opening a support ticket.

Yes, I intentionally did not put the 1 in there. I knew that it would probably bitch. Point 1 is not important though, as I do not have a DID that comes to me. That DID goes to an IVR. So I have to put an extension in there. But no, you can only ever use an 11 digit number on anything you ever do in the Skyetel portal. Aside form the extension issue, like my point about the tenant contact info, the contact info for the person they need to call need not be a US based person. Just because I am working with a US based carrier on a US based number does not mean that I have to buy a US based number for you to call me when I am in Tokyo or London or WTF ever.

@Skyetel Have you all never thought about anything like this at all? Seriously?

11e5f493-56c3-4a2a-ab4b-3e9b57ed2a4d-image.png

Okay. You're right. We're over it.

Now you can use 10 digits so long as the first digit does not start with 1 ❤

... and you can add extensions into the support ticket request form 😄

Signups will do the same tomorrow.

Might want to look at Tenant contact info also. But I do note the new error "only 10 or 11 are supported"!! Awesome.

bdc2cc1c-fb25-439e-9132-082fff8e7fc3-image.png

@Skyetel said in Skyetel port in promo code:

@JaredBusch said in Skyetel port in promo code:

@Skyetel submitting port requests!

gods the paperwork...

Ha - yea, tell me about it. You should see what we have to deal with behind the curtain. 😛

You could streamline things if there was a way to see the requested port in information after submitted, but prior to your entering the DID into the system.

I had a lot of duplicated typing that would have been awesome to have a copy previous request button or something. Mostly because everything was 1 req for the normal DID and 1 req for the toll free DID.

So, to circle back on this.

First, the number port completed perfectly. All things working.

But my concern about the number being entered and routable was 100% valid.

I received an email about 6pm that the number for port A had a FOC and was now entered into my Skyetel dashboard.

I then dialed said number from my personal Skyetel account and it was terminated to my client's PBX.
From any other service the number still terminated at the losing carrier.

The next day was a repeat of an email near 6pm for port B.

I did not specify an endpoint as @Skyetel describes in post 4 because I didn't know I needed to. But as this was a new turn up to Skyetel I only had one endpoint and it was pointed there by default I assume.

The ports completed as scheduled and calls flowed in as they should.

But during that couple of days it was 100% possible that calls could have went the wrong place if I had multiple endpoint groups setup and such as I wold on a bigger design.

A revamp of this process to include the ability to specify the endpoint group or documentation at the least to instruct users to note an endpoint group on the port request will definitely smooth this bump out.

Tagging @MontesVitalPBX