We’d be able to use the POTS adapter much more if there was the ability to connect it with a VoIP service of our choice. It completely strips the ability to use Multicarrier SIMs as well. Please add this feature.
Hi Jon,
we get SIP requests from time to time and we would appreciate feedback on questions below.
- Security consideration for VoIP on cellular internet? E.g. are SIP TLS or SRTP required?
- How to ensure voice quality(QoS) on cellular internet? Volte QoS could be ensured by the carrier but voice over internet is not ensured.
- If an emergency call is required, is location positioning required and what’s the positioning protocol/method?
- How many FXS ports or line accounts are required for the VoIP device? Currently we support only one.
- Are there any special voice related services or SIP signaling required?
- How to manage the VoIP device remotely? Unlike VoLTE, there are some mandatory configurable settings for VoIP, such as server IP address/port, user account, etc. If it’s IC2, IC2 should also manage these settings.
- Would your face challenges due to cellular CGNAT?
- Any other special requirements we need to know or consider?
Hi Giedrius - thanks for your reply. Here are the answers as best as I can offer them:
- SIP TLS would be nice but not a requirement, same as SRTP, as our use cases are door phones, guard shacks, elevators and such
- This is a great question, we are hoping that somewhere down the line, these might be SFC capable. For now, there isn’t a way to ensure QoS. In our experience, Volte QoS is a mythical service like a unicorn… LOL
- We plan on using E911 services for ours, as we do that already
- We would love the existing device to allow us to give access to assign different numbers to the respective ports
- We would need SIP traffic (5060-5065) to be allowed along with RTP traffic
- I would love to be able to manage from Incontrol. I could see us using a DHCP type 66 configuration via Incontrol to download the configuration credentials and mac authentications, required to validate the sip interactions
- I don’t believe so, as long as the devices can get to our proxy servers the device changing its ip or route to us wouldn’t matter
- SFC and/or Speedfusion VPN enablement, GPS following through another device, WAN/Lan port activation through USB - C port/connector would all be very desirable
1 Like
Thank you Jon for your comments. We will continue to collect feedback before making a decision.
G.
Just a note, we could easily use an SBC with the POTS adapter as the SIP client to solve a lot of these concerns.
Chris - that’s a very valid point and I appreciate your input. However, we’re looking for the least amount of points of failure/hardware. We like the form factor of the POTS adapter as it literally almost fits anywhere and super easy to offer battery backup options along with that, we’d have a single pane of glass for enterprise wide portal. We could always just use an ATA off a Peplink but again back to an additional device. Out of curiosity, what SBC do you recommend in your solution?
@ChristopherSpitler An SBC won’t work here as the sip stack is directly behind the POTS adapter.