Looks like 12 may be a good time to get started?

With Nextcloud I assume you can provide a local network file share as well as sync to remote clients. Basically what dropbox, ODfB and Google drive doesnt? Maybe Citrix Sharefile has this feature site (but I have only read, never tried)

I should also mention, for at least 5 years, DID peering has dramatically cut wholesale/CLEC costs on the backend (with no benefit to the retail side).

DID peering means carriers router calls directly to each other before hitting the telephone network. We charge each other .00001 or less for these connections.

The printer redirection has improved drastically since my last go around with RDSH.

Also @Dashrender I notice in the admin session you can see all printer sessions, but users only see their own redirected printers.

@coliver said in Twilio as a SIP provider:

Can you explain 60/60 vs 6/6?

From the sound of it you get charged for a full 60 seconds whether you use the entire thing or not. 6/6 sound the same but only for 6 seconds?

In telecom the first number is the minimum number of seconds you will be billed for the call. The second number is the minimum increments you will be billed in seconds for the remainder of the call.

As a CLEC or wholesaler you will see a little of 6/1. On the retail side Origination (even Flowroute) is 60/60 where there outbound is 30/6.

For retail Twilio has the best origination deal you will (.0045) find and Telnyx has the best termination I have seen.

Wholesale requires minimum monthly commitments and at least 1mmou (million minutes of monthly usage). In wholesale we mostly LCR through providers that do not provide 100% guaranteed call completion. With Twilio on wholesale you can get down to .0025.

@JaredBusch said in Twilio as a SIP provider:

@bigbear said in Twilio as a SIP provider:

Twilio is per minute billing in/out. You got 10 seconds over you pay for the whole minute.

Telnyx offers 6/6 billing in and out.

My suggestion was to use Twilio for inbound .0045 and Telnyx for termination .0075.

Twilio has no intention of going 6/6 as they don't want to deal with bad Average Seizure Rations (call center dialing). After you have established a couple MMOU with them they will make exceptions.

60/60 instead of 6/6 can make a big difference. At that rate of .0045 it is the same as VoIP.ms at .009, but VoIP.MS bills at 6/6.

In my experience you save about 12% on origination with 6/6, Maybe up to 20% on termination. For a single business usually much less on the latter even.

You will never touch the .0045 average for origination twilio charges with .009 at 6/6.

You should dump a CDR and round-up your minutes and apply the rate. I bet its at least 30% cheaper and likely more...

Its been a while for Windows Server and me, and I have never been a pro. I have a VULTR instance that crashed today and I see to remember you used to be able to get a memory dump (whocrashed) from C:\windows\memory.dmp or something of that nature.

Hoping some Windows 2016 expert will have some insight into the current tools to figure out why it crashed. Its running on VULTR so I opened to a ticket to see if there was any issue. I doubt it, its probably me. Just trying to do some investigating...

@Dashrender said in IPP Printing to Konica Minolta C224e over the internet(Citrix/RDSH Deployment):

The problem with printer redirection is that all those printers seen from the clients will be seen in the RDSH server. Personally never liked that.

Yeah and that is exactly how I would be printing remotely to our printer. lol.

Twilio is per minute billing in/out. You got 10 seconds over you pay for the whole minute.

Telnyx offers 6/6 billing in and out.

My suggestion was to use Twilio for inbound .0045 and Telnyx for termination .0075.

Twilio has no intention of going 6/6 as they don't want to deal with bad Average Seizure Rations (call center dialing). After you have established a couple MMOU with them they will make exceptions.

Today at 12:05 EST one of my new NJ Server 2016 instances was booted. The server sees it as if the power was unplugged.

I opened a ticket and I am trying to find some insight. Haven't had a server reboot in Chicago data center before, but haven't run Windows Server yet.

I have this particular instance firewalled with an allowed connection from my WAN IP. So I don't know if it could still be an outside attach like I was getting before. Thought about turning on DDoS attack protection but hate to be wasteful if that's not the issue.

Im twice as close to Chicago as NY/NJ but the latency to NJ is generally better than Chicago. So I just made the switch to NY.

@triple9 S7 was the industry lingo even in the early 90's when I got started. Another term that died off in the nineties was "cloud" ironically lol. And speaking of bad security who remembers Frame Relay?

I am noticing several sold out instances in NJ/NY Vultr data centers. Are these typically short lived or might they be unavailable for months?

For example I was going to deploy a $160 VM and they appear to be sold out of everything above $80.

@scottalanmiller said in Twilio as a SIP provider:

@EddieJennings said in Twilio as a SIP provider:

@scottalanmiller said in Twilio as a SIP provider:

@EddieJennings said in Twilio as a SIP provider:

I'm curious as to how significant "Secure Trunking" is: https://www.twilio.com/sip-trunking/pricing It's nice that the traffic from my PBX to Twilio is encrypted, but that seems a bit useless since once the traffic leaves Twilio there's no guarantee of encryption.

The S7 is not encrypted nor at all secure. But it is also not on the Internet.

Forgive my ignorance: S7?

The phone network. S7 is the protocol of the PSTN. All things we refer to as "normal phone calls" go over it no matter where they originate or terminate.

When we started providing phone service we were transcoding local interconnect ports to VoIP. How many years has it been since you got a "All Circuits Busy" message. lol. Good ol "breakage"

I have been using Twilio with FreePBX for however it was that I first joined this form. Have also used inbound Twilio for 2 years to ACME packet SBC's for inbound. Have ported customers to them every month outside of our local market (away form Level 3 and Verizon) and by then end of the year all our extended area inbound will be twilio. We have a cross connect with them but OTT worked flawlessly.

Have never had an outage. Best kept secret around.

It is 6/6 billing, even when you are 10mmou. Its 60/60 for inbound and outbound. For your avergae single account 6/6 only nets you 12% savings, where there rates are 55% cheaper on inbound

Outbound subaccount calling is difficult to configure. Inbound requires you peer to all of the market IP addresses in freePBX separately.

But it works great.

EDIT: If you are going to use them I suggest Telnyx for outbound. Its 6/6 pricing for .0075 for outbound. Its also easier to configure than outbound on twilio sub accounts (assuming youare reselling)

@scottalanmiller is right. The bottleneck is always the customer router. And not so much bandwidth as much as packets per second. Your dropbox sync is killing your phone calls 50 to 1 over bandwidth 99% of the time. Your $50 linksys router can't handle a million pps.

Most ISP's are little more than Broadsoft resellers with no interconnects in their local market. Even on the WISP side speeds are so good now that bundling voice isn't relevant.

For all the trouble I have gone through to get RDSH working, Next Cloud still makes me wonder...

And does Anyone use Libre Office as a full replacement for Office 2016?

I was able to get printer redirection working on my single server setup.

I was just thinking I may wanna do something akin to google cloud print the IPP. The copiers all seem to support it.

I am working on a VIrtual Desktop (RDSH) of sorts and I am thinking about whether I want to do all the printer mapping through thin clients vs setting up IPP printing.

The security would be simple enough, publishing ports via the firewall and restricting traffic to originate only from my RDSH deployment IP address. Not sure if its feasible. Also not sure if I want to rely on WIndows 2016 Server's generic printer driver to do all the work.

Appreciate anyones thoughts on the matter...

@Mike-Davis it seems like RDP guard would be simpler than a VPN for the purpose of allowing users to access the system "wherever" they are, mobile devices etc included.

However I wonder if Vultr ip ranges are scanned more frequently than Azure. I setup a couple honey potts and the attacks are 10 to 2 Vultr vs Amazon thus far.

In regards to ZT it might work, reminds me a lot of Himachi.

Since the remote client wouldn't be part of the domain DNS wouldn't be a concern. It would be less exposure to risk than RDPGuard (which I am still gonna try first).