@JasGot said in Recording calls on a SIP Trunk to a local Recorder/Logger:

@Skyetel Is there an API or other method to automate the downloading of the recordings? Are they available through FTP or RSync?

They are available via API. Check that out here: https://api.docs.skyetel.com/

@JasGot said in Recording calls on a SIP Trunk to a local Recorder/Logger:

Forgot to add this above, it may require two recording methods: since it is an in house pbx. Ext to Ext recording is required.

Oh - in that case It would depend on what PBX you are using. @JaredBusch would probably know about that than I would. However - most PBXs support call recording internally. That would be the best option if you can do it

If you plan on switching to us - you can just enable our own Call Recording:
https://support.skyetel.com/hc/en-us/articles/360040711534-Call-Recording

For Comment 1 - I would suggest against the idea of a "Conference Call" recording system because that won't preserve the channels of the call. They will get muxed together and you'll loose the ability to fun things like Transcription. It can also create issues where the recorder will drop the call.

For Comment 2 - If you need to use this system for internal reasons, this would be the better option. It's better to fork the audio the recorder instead of having it record inside the live call path. If the recorder is in the live call path, and it fails, or runs out of disk, you will loose your ability to place/receive calls. (Though that may be preferred depending on the industry you are in. I know a lot of debt collectors work like this).

@ing-joserivera26 said in VitalPBX 3:

@JaredBusch In that case you must put the host in the match field. I guess you must put: srv.skyetel.com

Skytel said in your blog:

SkyEtel

@dafyre said in SIP Registration:

@JaredBusch said in SIP Registration:

@Skyetel said in SIP Registration:

I'm interested in your gentle (cough Jared cough ) feedback.

@Skyetel -- you probably already know this... but...

Oh I know

@Pete-S said in SIP Registration:

@JaredBusch said in SIP Registration:

@Skyetel said in SIP Registration:

We are worried about fraud risk with SIP Registration.

A valid worry as highlighted by the "admin" that posted here

Domain/IP whitelisting?

Enter domain names/IPs that are allowed to register in your account setup.
Domain names are resolved and only IPs that are whitelisted can successfully register.

On prem PBX can even have dynamic IP then (with DDNS).

Quite a few services use this layered approach so that it requires both a valid IP and valid credentials.

Well, for customers with this config, we'd just tell them to use our existing IP Registration. We wouldn't need to offer that separately.

Hi All

We have decided to introduce SIP Registration support in a forthcoming update on Skyetel. Our goal it to roll it out in Mid-Late November, but it may come sooner or later than that depending on our testing period. I am posting this because I would like to see if anyone here is interested in acting as a beta tester for us when its further along in development.

While it is in Beta, there will be some limitations:

1. International Calling will not be supported
2. You will be limited to 30 concurrent calls on our network (15 per SIP Region - more on that later)
3. You will be limited to 1 call per second

Our SIP Registration deployment will support 2/4 regions - NW and NE. Your PBX will need to be configured to register to both regions and we will round robin from our regions to support multi-region redundancy. If we do decide to roll it out to all 4, your PBX would need to register to 4 regions in the config (which would be a pita to configure).

It is our intention to still strongly encourage the use of IP Authorization instead of SIP Registration. So we will probably have a few limitations for SIP Registration that do not exist with IP Auth. We also will not support connecting a desk phone or ATA directly to our network, even though technically it will be possible to do so.

A few things we're still thinking about:

1. We have not decided yet if we want to add registration to all 4 of our regions, or only support it in two.
2. We have not decided if we want to include SIP Registration in our SLA or leave it as a "Best effort" service. (TBH, I'm leaning toward including it in the SLA)
3. We have not decided on the Registration timeouts - some carriers enforce a full 1800 seconds and won't let you re-register faster than that. We're leaning toward a 6 minute Registration timeout, and providing guidance that you should re-register every 5 mins.
4. We are worried about fraud risk with SIP Registration. Since it is possible to get your carrier credentials compromised on an old PBX, it becomes possible for a Skyetel account to be compromised itself, rather than through a PBX. So we're thinking about having different balance requirements, or different verification methods, etc. We may also block SIP Registration on old PBXs (please people, stop using Trixbox for the love of god).

I'm interested in your gentle (cough Jared cough ) feedback. What have you guys had experience with, what suggestions or ideas do you have?

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.