SIP Registration
-
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:
- International Calling will not be supported
- You will be limited to 30 concurrent calls on our network (15 per SIP Region - more on that later)
- 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:
- We have not decided yet if we want to add registration to all 4 of our regions, or only support it in two.
- 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)
- 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.
- 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? -
@Skyetel said in SIP Registration:
Mid-Late November, but it may come sooner or later than that depending on our testing period.
Sounds like the Covid-19 vaccine that is being promised by President Trump.
Ha, sorry, just had too.
-
@Skyetel said in SIP Registration:
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)
Absolutely leave it best effort. Registration is a legacy idea IMO.
-
@Skyetel said in SIP Registration:
We have not decided yet if we want to add registration to all 4 of our regions, or only support it in two.
You chose two just to have some kind of flexible path without having the complexity of making people set up 4 trunks?
Stick with 2 IMO.
-
@Skyetel said in SIP Registration:
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.
FreePBX and VitalPBX both default to 3600 seconds (1 hour). So going less than that will lead to support calls from "admins" that don't RTFM.
-
@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
-
-
@Skyetel said in SIP Registration:
What have you guys had experience with, what suggestions or ideas do you have?
Really, the only good thing about registration is when you have an on prem device. Registration will let you get around needing to open firewall ports.
-
I'm sure we can beta test.
-
-
@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.
-
@Pete-S yeah, there are plenty of things you can add to secure things. But like everything, you can’t fix stupid.
-
@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...
-
@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.
-
@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
-
@Skyetel I can switch my personal account to registration. Or some spare numbers on our company account. I don't have a "spare" system that will get calls though. So if you can have registration from the same IP as a current endpoint, I can actually do it and have traffic.
Otherwise, it will be sporadic traffic from my personal account, currently hooked up to a VitalPBX instance I am testing.
