@JaredBusch What size instance did you use? Please remember that Postcards requires 2GB of Ram (we recommend 4).

@JaredBusch

Let’s table this till next week. I’ll have one of our other engineers update the install script to be more inclusive for Operating Systems.

@JaredBusch said in Introducing Postcards - Our SMS & MMS UI:

@Skyetel said in Introducing Postcards - Our SMS & MMS UI:

@JaredBusch yes, he’s legit. Cody is one of our rockstars so be nice

Your nice or mine?

Whichever is nicer

@JaredBusch yes, he’s legit. Cody is one of our rockstars so be nice

I'll check to see if a non-docker install method is doable.

So the short answer to this question is "no," but we might modify the installation to switch to RHEL's k8s so you can use Centos 8. Our developers live and breathe containers, and trying to get them to go old school is... challenging lol.

However, we are going to be writing a few guides for users to be able to install postcards on cloud platforms like this:
https://www.digitalocean.com/products/kubernetes/ & https://aws.amazon.com/fargate/

We're also going to draft some guides that show people how to the HTML source to make changes for themselves (ideally by being able to FTP into the Postcards Server and modify the HTML - but the exact method is up in the air).

@JaredBusch said in Introducing Postcards - Our SMS & MMS UI:

So the CentOS 8 problem and the Fedora 32 problem both stem from this.

This is 100% a docker problem.

So @Skyetel can we get a non-docker install method "supported"

It looks like Red Hat dropped support for Docker altogether:
http://crunchtools.com/why-no-docker/

So we need to update our readme to recommend Centos 7 or Debian/Ubuntu.

I'll check to see if a non-docker install method is doable.

@JaredBusch said in Introducing Postcards - Our SMS & MMS UI:

also, how do I submit bug reports in bitbucket? I don't see anything like the normal "issues" in gitlab or github.

Here you go:
https://skyetel.atlassian.net/secure/CreateIssueDetails!init.jspa?pid=10202&issuetype=10200&priority=4&summary=Feedback on Postcards

@JaredBusch Oops

Okay - it's official. New version is out:
https://skyetel.com/postcards-1-1-now-available/

@JasGot I don’t believe the install methods have changed. So the existing guides should work.

@JasGot It was technically released today - so you should be able to install it and start using it now. We'll be doing the formal announcement on Monday (apparently there is a small known bug that our developers want to fix before we release it).

Feel free to spin one up and try it - but I'd suggest waiting until you get the formal email on Monday before putting it in production. I don't personally know what the bug was.

@Dashrender Here you go:
https://mangolassi.it/topic/19453/skyetel-relationship-pricing

You can watch the commits here:
https://bitbucket.org/skyetel/postcards-backend/commits/
https://bitbucket.org/skyetel/postcards-ui/commits/

@scottalanmiller said in Introducing Postcards - Our SMS & MMS UI:

@JasGot said in Introducing Postcards - Our SMS & MMS UI:

Any updates to this app? Any plans to update it or replace it? It's still VERY VERY basic.

A couple of things I could really use are:

1. Import phone numbers and names
2. Send "bulk" to the people I've entered.

It's a demo app, not really meant to be used. It's meant to show how to build your own tooling using their API.

Version 1.1 is going to be released in about 2 weeks. It will include:

1. Upload Contacts via CSV
2. Search - Ability to search through messages & contacts
3. Automated image scaling for images that run larger than 1.5Mb
4. Giphy Integration - Send Giphys in SMS!
5. Send Emojis - Send Emojis!
6. Templates - Have pre-set messages that can be sent with a click of a mouse
7. Archive Conversations - Ability to close a conversation and hide it from view
8. Bulk SMS Sending - Ability to send 1 message to multiple recipients via some kind of Queue. We're calling it announcements
9. Auto Replies - Be able to automatically reply to a new message
10. Schedule Sending SMS - Ability to deliver an SMS at a pre-set time
11. Email Notifications - Ability to notify users that they’ve received an SMS by email using end-user supplied SMTP servers
12. Postcards Updater - Add the ability to update from one version of Postcards to the next version

I wouldn't say that it is a "Demo App." We do want people to be able to use it as a solid solution, but it's not our company's focus. If you have some development expertise, you can fork it and expand on it. Otherwise you have to just wait for us to give it some TLC. We are going to try to do twice a year updates on it.

Well - it looks like we have to issue an update about this.

Unfortunately, 4.skyetel.com clashes with some systems that do not support numerical values in DNS entries (yes, thats a real thing) and so please use na.skyetel.com instead. We will be sending out an email tomorrow asking everyone to please use na.skyetel.com instead of 4.skyetel.com. Sorry for the headache guys.

@JaredBusch said in Skyetel's 4th Region:

@Skyetel said in Skyetel's 4th Region:

It also has TCP support

TLS/SRTP support coming? Or just setting up TCP for those unlucky people that have to use it?

Just for those who have to use TCP.

TLS/SRTP forces us to get into the audio path and we’re not super excited to do that. Upstream PSTN networks don’t support it either.

@JaredBusch said in Skyetel's 4th Region:

Also, since 4.skyetel.com has both A records and SRV records, it works perfectly in FreePBX without any extra firewall settings or the need for the match/permit setting in advanced.

[jbusch@pbx ~]$ dig 4.skyetel.com @1.1.1.1

; <<>> DiG 9.9.4-RedHat-9.9.4-74.el7_6.1 <<>> 4.skyetel.com @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17708
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1452
;; QUESTION SECTION:
;4.skyetel.com.			IN	A

;; ANSWER SECTION:
4.skyetel.com.		229	IN	A	52.8.201.128
4.skyetel.com.		229	IN	A	52.60.138.31
4.skyetel.com.		229	IN	A	52.41.52.34
4.skyetel.com.		229	IN	A	50.17.48.216

;; Query time: 3 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Thu Apr 23 21:38:56 CDT 2020
;; MSG SIZE  rcvd: 119

[jbusch@pbx ~]$ dig SRV _sip._udp.4.skyetel.com @1.1.1.1

; <<>> DiG 9.9.4-RedHat-9.9.4-74.el7_6.1 <<>> SRV _sip._udp.4.skyetel.com @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28558
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1452
;; QUESTION SECTION:
;_sip._udp.4.skyetel.com.	IN	SRV

;; ANSWER SECTION:
_sip._udp.4.skyetel.com. 269	IN	SRV	10 10 5060 ca1.skyetel.com.
_sip._udp.4.skyetel.com. 269	IN	SRV	10 10 5060 va1.skyetel.com.
_sip._udp.4.skyetel.com. 269	IN	SRV	10 10 5060 or1.skyetel.com.
_sip._udp.4.skyetel.com. 269	IN	SRV	10 10 5060 eh.skyetel.com.

;; Query time: 3 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Thu Apr 23 21:39:03 CDT 2020
;; MSG SIZE  rcvd: 214

It also has TCP support

@JaredBusch said in Skyetel's 4th Region:

@Skyetel how new is 4.skyetel.com my PBX doesn't see the A record now.

So my initial test was valid, but seems DNS is not solid yet or something.

This was our mistake - we reset our DNS settings for 4.skyetel.com in preparation for tomorrow mornings announcement. Should be solid now that it’s been deployed to our production settings on Cloudflare. (It needed TCP support)

@JaredBusch lol, yes. yes we did lol.

Hey Guys,

I'm giving you all first notice about this since a lot of you guys have helped us with bugs and provided us with other feedback.

We are going to be adding our 4th Region to our routing tables in June. Most of you guys are already good to go, but for those of you who aren't, please have a quick look at this: https://support.skyetel.com/hc/en-us/articles/360046703354-Skyetel-s-4th-Region

Would you guys be willing to test na.skyetel.com with your PBXs to verify that they are indeed routing outbound calls to all 4 of our IPs?

Thanks!

(edit - updated with na.skyetel.com)