Skyetel Inbound SIP Trunk on FreePBX
-
@scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX:
@Dashrender said in Skyetel Inbound SIP Trunk on FreePBX:
@scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX:
@Dashrender said in Skyetel Inbound SIP Trunk on FreePBX:
@JaredBusch said in Skyetel Inbound SIP Trunk on FreePBX:
@scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX:
Setting an Inbound Route with a Skyetel SIP Trunk on FreePBX 14 with pjsip is very easy. Here is an example configuration...
The DID Number needs to be the eleven digit number of your Skyetel Trunk. That's it!
No registration? No thanks. I very much dislike IP auto based setups.
Why? because of the firewall setup requirements?
there isn't any firewall requirements beyond the normal.
with registration, you don't need to open any ports - at least not with VOIP.ms (I know this I tested it earlier this week). But with IP based, you do need open ports.
No, you don't. Not a special one. What are you thinking is needed?
With every trunk provider that I have dealt with to date, if you use a registered trunk there are zero needs to allow inbound port forwarding for a PBX that is behind NAT.
@Dashrender Part of the disconnect from @scottalanmiller is that he, probably, never does this on an internal system that is using NAT.
A PBX on a public IP has no issues by its design.
About 50% of my deployments are behind NAT.
-
@JaredBusch said in Skyetel Inbound SIP Trunk on FreePBX:
@scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX:
@Dashrender said in Skyetel Inbound SIP Trunk on FreePBX:
@scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX:
@Dashrender said in Skyetel Inbound SIP Trunk on FreePBX:
@JaredBusch said in Skyetel Inbound SIP Trunk on FreePBX:
@scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX:
Setting an Inbound Route with a Skyetel SIP Trunk on FreePBX 14 with pjsip is very easy. Here is an example configuration...
The DID Number needs to be the eleven digit number of your Skyetel Trunk. That's it!
No registration? No thanks. I very much dislike IP auto based setups.
Why? because of the firewall setup requirements?
there isn't any firewall requirements beyond the normal.
with registration, you don't need to open any ports - at least not with VOIP.ms (I know this I tested it earlier this week). But with IP based, you do need open ports.
No, you don't. Not a special one. What are you thinking is needed?
With every trunk provider that I have dealt with to date, if you use a registered trunk there are zero needs to allow inbound port forwarding for a PBX that is behind NAT.
@Dashrender Part of the disconnect from @scottalanmiller is that he, probably, never does this on an internal system that is using NAT.
A PBX on a public IP has no issues by its design.
About 50% of my deployments are behind NAT.
Awww - that would explain it.
-
@Dashrender said in Skyetel Inbound SIP Trunk on FreePBX:
@scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX:
@Dashrender said in Skyetel Inbound SIP Trunk on FreePBX:
@scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX:
@Dashrender said in Skyetel Inbound SIP Trunk on FreePBX:
@JaredBusch said in Skyetel Inbound SIP Trunk on FreePBX:
@scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX:
Setting an Inbound Route with a Skyetel SIP Trunk on FreePBX 14 with pjsip is very easy. Here is an example configuration...
The DID Number needs to be the eleven digit number of your Skyetel Trunk. That's it!
No registration? No thanks. I very much dislike IP auto based setups.
Why? because of the firewall setup requirements?
there isn't any firewall requirements beyond the normal.
with registration, you don't need to open any ports - at least not with VOIP.ms (I know this I tested it earlier this week). But with IP based, you do need open ports.
No, you don't. Not a special one. What are you thinking is needed?
Special? Well 5060 isn't special - but it's s till something you have to do. Otherwise you won't get notices on incoming calls. Or am I missing something?
Even if you are behind a NAT, as long as you have any external end points connecting it. We have PBX on NAT, but we need ports open for people to connect.
-
Now if you have an internal PBX and zero external connections.
-
I have an internal PBX, with zero external phones/devices. The only thing I'm using external is the SIP service. Since I'm using registration, I don't need any firewall rules to make it work.
-
@Dashrender said in Skyetel Inbound SIP Trunk on FreePBX:
I have an internal PBX, with zero external phones/devices. The only thing I'm using external is the SIP service. Since I'm using registration, I don't need any firewall rules to make it work.
You don't have a single user wanting another office, or a doctor wanting to make calls from home? That's getting to be pretty rare. Even our manufacturing customers tend to want phones at home.
-
@scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX:
@Dashrender said in Skyetel Inbound SIP Trunk on FreePBX:
I have an internal PBX, with zero external phones/devices. The only thing I'm using external is the SIP service. Since I'm using registration, I don't need any firewall rules to make it work.
You don't have a single user wanting another office, or a doctor wanting to make calls from home? That's getting to be pretty rare. Even our manufacturing customers tend to want phones at home.
Oh, of course we do - but they (the boss) doesn't want to pay for it.
But it's time to kill our dieing digital PBX, so I need to start another thread for that.
-
@scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX:
@Dashrender said in Skyetel Inbound SIP Trunk on FreePBX:
I have an internal PBX, with zero external phones/devices. The only thing I'm using external is the SIP service. Since I'm using registration, I don't need any firewall rules to make it work.
You don't have a single user wanting another office, or a doctor wanting to make calls from home? That's getting to be pretty rare. Even our manufacturing customers tend to want phones at home.
Not really. I see it consistently. Surprising to me, but I see it consistently.
-
@Dashrender said in Skyetel Inbound SIP Trunk on FreePBX:
@scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX:
@Dashrender said in Skyetel Inbound SIP Trunk on FreePBX:
I have an internal PBX, with zero external phones/devices. The only thing I'm using external is the SIP service. Since I'm using registration, I don't need any firewall rules to make it work.
You don't have a single user wanting another office, or a doctor wanting to make calls from home? That's getting to be pretty rare. Even our manufacturing customers tend to want phones at home.
Oh, of course we do - but they (the boss) doesn't want to pay for it.
How is that not free?
-
@scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX:
@Dashrender said in Skyetel Inbound SIP Trunk on FreePBX:
@scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX:
@Dashrender said in Skyetel Inbound SIP Trunk on FreePBX:
I have an internal PBX, with zero external phones/devices. The only thing I'm using external is the SIP service. Since I'm using registration, I don't need any firewall rules to make it work.
You don't have a single user wanting another office, or a doctor wanting to make calls from home? That's getting to be pretty rare. Even our manufacturing customers tend to want phones at home.
Oh, of course we do - but they (the boss) doesn't want to pay for it.
How is that not free?
He has Mitel and has to pay licensing for it.
-
@JaredBusch said in Skyetel Inbound SIP Trunk on FreePBX:
@scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX:
@Dashrender said in Skyetel Inbound SIP Trunk on FreePBX:
@scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX:
@Dashrender said in Skyetel Inbound SIP Trunk on FreePBX:
I have an internal PBX, with zero external phones/devices. The only thing I'm using external is the SIP service. Since I'm using registration, I don't need any firewall rules to make it work.
You don't have a single user wanting another office, or a doctor wanting to make calls from home? That's getting to be pretty rare. Even our manufacturing customers tend to want phones at home.
Oh, of course we do - but they (the boss) doesn't want to pay for it.
How is that not free?
He has Mitel and has to pay licensing for it.
He has to license each extension?
It's odd to use "not wanting to pay for it" in conjunction with "uses Mitel" which means that they "wanted to pay for things for no real reason." Paying for it is what they wanted to do that got them into the situation.
-
@scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX:
@JaredBusch said in Skyetel Inbound SIP Trunk on FreePBX:
@scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX:
@Dashrender said in Skyetel Inbound SIP Trunk on FreePBX:
@scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX:
@Dashrender said in Skyetel Inbound SIP Trunk on FreePBX:
I have an internal PBX, with zero external phones/devices. The only thing I'm using external is the SIP service. Since I'm using registration, I don't need any firewall rules to make it work.
You don't have a single user wanting another office, or a doctor wanting to make calls from home? That's getting to be pretty rare. Even our manufacturing customers tend to want phones at home.
Oh, of course we do - but they (the boss) doesn't want to pay for it.
How is that not free?
He has Mitel and has to pay licensing for it.
He has to license each extension?
It's odd to use "not wanting to pay for it" in conjunction with "uses Mitel" which means that they "wanted to pay for things for no real reason." Paying for it is what they wanted to do that got them into the situation.
Sunk cost. We've been down this road about his boss before.
Also he keeps sinking time into Mitel settings and enabling it to hobble along more. See his recent thread on Mitel and VoIP.ms.
-
@scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX:
@Dashrender said in Skyetel Inbound SIP Trunk on FreePBX:
@scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX:
@Dashrender said in Skyetel Inbound SIP Trunk on FreePBX:
I have an internal PBX, with zero external phones/devices. The only thing I'm using external is the SIP service. Since I'm using registration, I don't need any firewall rules to make it work.
You don't have a single user wanting another office, or a doctor wanting to make calls from home? That's getting to be pretty rare. Even our manufacturing customers tend to want phones at home.
Oh, of course we do - but they (the boss) doesn't want to pay for it.
How is that not free?
Mitel wants a million dollars to do anything.
Not really - but you get my point.
To get them remote access - I'd have to purchase another phone license $250, purchase a phone $250 or the phone client (no clue on price).
Basically - to add another phone is $500.
Then I'd have to open the firewall to allow it - and I'm not sure what I'd have to lock down on the PBX to ensure people aren't hacking it.
-
@scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX:
@JaredBusch said in Skyetel Inbound SIP Trunk on FreePBX:
@scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX:
@Dashrender said in Skyetel Inbound SIP Trunk on FreePBX:
@scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX:
@Dashrender said in Skyetel Inbound SIP Trunk on FreePBX:
I have an internal PBX, with zero external phones/devices. The only thing I'm using external is the SIP service. Since I'm using registration, I don't need any firewall rules to make it work.
You don't have a single user wanting another office, or a doctor wanting to make calls from home? That's getting to be pretty rare. Even our manufacturing customers tend to want phones at home.
Oh, of course we do - but they (the boss) doesn't want to pay for it.
How is that not free?
He has Mitel and has to pay licensing for it.
He has to license each extension?
It's odd to use "not wanting to pay for it" in conjunction with "uses Mitel" which means that they "wanted to pay for things for no real reason." Paying for it is what they wanted to do that got them into the situation.
it's worse - not only each extension - each connection. For example, As JB just mentioned, I recently got VOIP.ms to work with my PBX. This requires SIP licenses for each simultaneous call. Another $250+ per license.
-
@JaredBusch said in Skyetel Inbound SIP Trunk on FreePBX:
@scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX:
@JaredBusch said in Skyetel Inbound SIP Trunk on FreePBX:
@scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX:
@Dashrender said in Skyetel Inbound SIP Trunk on FreePBX:
@scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX:
@Dashrender said in Skyetel Inbound SIP Trunk on FreePBX:
I have an internal PBX, with zero external phones/devices. The only thing I'm using external is the SIP service. Since I'm using registration, I don't need any firewall rules to make it work.
You don't have a single user wanting another office, or a doctor wanting to make calls from home? That's getting to be pretty rare. Even our manufacturing customers tend to want phones at home.
Oh, of course we do - but they (the boss) doesn't want to pay for it.
How is that not free?
He has Mitel and has to pay licensing for it.
He has to license each extension?
It's odd to use "not wanting to pay for it" in conjunction with "uses Mitel" which means that they "wanted to pay for things for no real reason." Paying for it is what they wanted to do that got them into the situation.
Sunk cost. We've been down this road about his boss before.
I know. But it means that spending money unnecessarily was something that they wanted to do to get into the sunk cost scenario to begin with. In fact, sunk cost itself is effectively defined as as desire to spend money unnecessarily.
Sunk cost = wants to spend money.
-
@Dashrender said in Skyetel Inbound SIP Trunk on FreePBX:
Then I'd have to open the firewall to allow it - and I'm not sure what I'd have to lock down on the PBX to ensure people aren't hacking it.
Two seconds of work on FreePBX. Or on your firewall. Locking a port to a single IP is a trivial task for any gear, even consumer.
-
@scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX:
@Dashrender said in Skyetel Inbound SIP Trunk on FreePBX:
Then I'd have to open the firewall to allow it - and I'm not sure what I'd have to lock down on the PBX to ensure people aren't hacking it.
Two seconds of work on FreePBX. Or on your firewall. Locking a port to a single IP is a trivial task for any gear, even consumer.
Bzzt wrong answer.
You cannot do that with roaming users.
That works great for a trunk, but not your stated case of needing it open for remote phones.
-
@scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX:
Locking a port to a single IP is a trivial task for any gear, even consumer.
I wouldn't go that far.
-
@JaredBusch said in Skyetel Inbound SIP Trunk on FreePBX:
@scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX:
@Dashrender said in Skyetel Inbound SIP Trunk on FreePBX:
Then I'd have to open the firewall to allow it - and I'm not sure what I'd have to lock down on the PBX to ensure people aren't hacking it.
Two seconds of work on FreePBX. Or on your firewall. Locking a port to a single IP is a trivial task for any gear, even consumer.
Bzzt wrong answer.
You cannot do that with roaming users.
That works great for a trunk, but not your stated case of needing it open for remote phones.
I thought that he was talking about the trunk provider.
I mean I still think that, one IP (or one set of IPs), not roaming users. Setting this up for a situation like Skyetel. Nearly zero effort.
If he already had roaming users, it would already be open and be zero work.
-
@JaredBusch said in Skyetel Inbound SIP Trunk on FreePBX:
@scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX:
Locking a port to a single IP is a trivial task for any gear, even consumer.
I wouldn't go that far.
I don't know much consumer gear that doesn't make that easy.
