StartUP + SIP Registration w/ Skyetel

[Dragons Library]

Howdy, I have a local phone number on Skyetel that I have configured with SIP Registration Credentials, but for the life of me cannot get it to work with 3CX. I have followed the Configuring your US SIP Trunk Provider Skyetel with 3CX guide to the best of my ability, but the SIP trunk status remains red on 3CX.

I am on a 3CX StartUP Pro plan and do not have access to 3CX logs (as far as I can tell), but from the logs that Skyetel was able to share with me, the issue appears to be that SIP Registration frequency for my PBX instance coming from 3cx.reg.skyetel.com is occurring too frequently (~every 4 seconds) and that my 3CX registration IP has likely been blocked because it doesn't comply with the SIP Registration guidelines set by Skyetel:

Skyetel's SIP Registration does not accept registration more frequently than 100 seconds, and automatically expires the registration in 300 seconds. Do not set your PBX to register more frequently than 100 seconds - doing so will cause your PBX to be blocked by our network.

Additionally, from the Skyetel logs, it appears that no authorization header is being sent in the registration request. I have triple-checked my credentials and even generated new credentials.



Any guidance on what I'm doing wrong or how to fix this would be awesome!

For what its worth - the Configuring your US SIP Trunk Provider Skyetel with 3CX guide seems out of date as Skyetel SIP Credentials creation no longer offers a Device Type option, but rather offers two Routing Method options...
- Route using the phone number
- Route using the username

with the note:

If you are using an ATA or 3CX StartUP, we recommend using username routing. Most other PBXs should use phone number routing.

 

[Nathan@Voxtelesys]

Looks like your registration attempt is leaving the network based on the screenshot. If you want you can try another carrier like us (Voxtelesys), this would rule out if it is a StartUP problem (unlikely) or a provider problem.

Guide - https://www.3cx.com/docs/voxtelesys-us-sip-trunk
Signup - https://portal.voxtelesys.net/register

We have many trunks registered on 3CX StartUP and have tested the integration for ourselves, we can also do some live troubleshooting if you wish.
Feel free to give us a call or email if you have any issues getting setup on StartUP or 3CX!

 

[Skyetel]

Hi @Dragons Library

Thanks for posting this. You are correct that the issue is the registration frequency, with the added caveat that when a 3CX user provides an invalid credential set (they mis-type a password, or misconfigure an account) our security systems kick in and flag the IP. Our security systems are very robust - please accept our apologies for the inconvenience.

We are working with the 3CX team right now to get this resolved, and will be deploying a temporary adjustment to our network as a short-term solution.

 

[Dragons Library]

@Skyetel thanks for the info. Do you have a rough ETA for when this might be working again?

 

[Skyetel]

HI @Dragons Library

Our engineers pushed a security update/temp workaround for 3CX customers yesterday. So you should be good to go now. If not, please drop us a line in Support and we can get you all setup .

We've also been in touch with 3CX and have come up with a permanent solution. Props to @YiannisH_3CX for being so responsive to us

 

[Skyetel]

Hi All,

We've deployed an update to our routers and firewalls that should prevent this behavior from continuing. Unfortunately, we have to make one more update to our portal to correctly display the SIP Registration status in our portal. Right now it will show "Unknown" inaccurately for some SIP Registration usernames. (This will not impact your ability to place/receive calls - just to survey your boxes). This should be out by early next week.

It is important to note that this was a design flaw on our network, and not caused by 3CX's PBX.

So what happened?

Our SIP Registration platform was built with the idea that a modest number of credential sets would originate from an individual IP. The thinking would be that people would connect their PBXs to our network from their offices using dynamic IPs. Since 3CX StartUP architecture achieves multi-tenancy via SIP Registration - and that was an architecture our engineers did not plan for - our own security systems bit us in the butt. Basically, In our excitement to build out full support for 3CX StartUP, we fell victim to this architecture flaw until 3CX pointed it out to us when they began to hit volume. We are very grateful for their help on this.

It's embarrassing to admit that we made a mistake, and we are sorry about that .

 

[Dragons Library]

Thanks for the quick updates and fix here. And thank you very much for the transparency and taking ownership.

After the updates, everything seems to be working as expected now.

 

[joe.schwartz@securedispla]

Any updates on this issue, just trying to setup 3CX Startup and the configuration screens in the documentation are out of date. Newbie on this platform but have admin other IP phone systems before.

 

[cobaltit]

Where is the error? That shows the status on the Skyetel side is unknown, but that's not an error. What does it show on the 3CX side?

 

[YiannisH_3CX]

Any updates on this issue, just trying to setup 3CX Startup and the configuration screens in the documentation are out of date. Newbie on this platform but have admin other IP phone systems before.

Our documentation for Skyetel was updated very recently. Can you please take a look and let me know what is out of date?
https://www.3cx.com/docs/sip-trunk/skyetel-usa/