Hey Guys,

We released our Tenant Billing solution today. Check it out:
https://skyetel.com/introducing-end-user-billing/

Chime isn't really intended for MSPs, it's more of a platform to build services like Slack or Teams on top of. That's why they don't include CNAM or 911. Their support is going to be tailored for those kinds of customers, as will their integrations. So be mindful to try and not fit a square peg in a round hole.

Below is the link for Chime's pricing

DID: $1.00

Inbound Calling:
United States of America $0.002216

Outbound Calling:
United States of America $ 0.004800

https://aws.amazon.com/chime/pricing/

Friendly reminder that Chime prices do not include support, and that is an additional (high) charge, whereas our pricing includes support.

But what about the same user on multiple machines, since the system is designed 1:1, that's a show stopping oversight.

It feels like artificial limitations being put in that block user functionality, why not leave it open to being useful? Is there some simple code to be removed to fix these issues? Is it that simple?

The single login per computer is probably pretty easy to change, and I can add that to the change request. That would allow for both multiple logins on different computers, and would allow for something like "[email protected]" for the main company number.

Both of these limitations are related to security concerns our developers had. We've seen people transmit information via SMS that they really shouldn't (credit card numbers, SSNs, etc), and so they went a little heavy on the security.

The 1:1 relationship between a user and a phone number is by design. We didn't build it to allow for more than one user corresponding on a particular phone number at a time (hence the can only login in one place at a time).

The Address Book should be unique per user, but user 2 not being able to add a duplicate value sounds like a bug.

Login persistence between sessions (the F5 annoying thing) is simply incomplete. So you can classify it as a bug for now, and will be fixed in version 1.2.

@scottalanmiller said in Install Skyetel Postcards on CentOS 7:

@JasGot said in Install Skyetel Postcards on CentOS 7:

@scottalanmiller Works ok with 2GB? I remember someone saying it really needs 4gb.

Perfectly fine in 2GB. Going to test 1GB soon. Only using 480MB according to free.

It takes 2GB to build, but then its very lightweight. 4GB is recommended if you are have other things running on the server that is hosting Postcards.

It is a Cloudflare outage, and it impacts about 30% of the internet. Details here: https://www.cloudflarestatus.com/

I wanted to make sure I followed up and let you all know that we confirmed that there was no bug. There was a propagation delay that impacted @JasGot which caused it to appear that the 10 digit vs 11 digit input mattered.

@JasGot said in Wrong Caller ID:

@Skyetel said in Wrong Caller ID:

Would you please open a support ticket so we can ask for PII?

Done:
#82411

Great, thanks. We've already replied

@JasGot said in Wrong Caller ID:

@krzykat said in Wrong Caller ID:

@JasGot What are you referencing? The DIP at Skyetel or ?

For the Caller ID Editor.

Without the "1" They accept it, tell you it has processed, then do nothing with it......

With the "1", they accept it, tell you it has processed, then they actually submit it to the Caller ID database in the sky (or wherever it is)

Looks like this isn't a bug, but without more details we can't troubleshoot further.

Would you please open a support ticket so we can ask for PII?