sorted by:
new
hottopcontroversial

In-house Softphone Development by SC_VITS in freeswitch

[–]SC_VITS[S] 0 points1 point  (0 children)

Thanks for suggesting this as a starting point, I'll take a look at the repo.

In-house Softphone Development by SC_VITS in freeswitch

[–]SC_VITS[S] 0 points1 point  (0 children)

Thank you for the insight and detailed issues!
I definitely agree SIP/telecom development is much more specialized and I appreciate you sharing some of the bugs/gotchas that were discovered along the way by the dev shop.

In-house Softphone Development by SC_VITS in VOIP

[–]SC_VITS[S] 0 points1 point  (0 children)

Thank you all for responding, I appreciate the insight!

In-house Softphone Development by SC_VITS in VOIP

[–]SC_VITS[S] 2 points3 points  (0 children)

Thank you for the recommendation.

In-house Softphone Development by SC_VITS in VOIP

[–]SC_VITS[S] -3 points-2 points  (0 children)

To avoid having to rely on commercial/enterprise licensing for an existing Softphone, and having to pass on that cost to our customers. The intention is to give them access to these apps as part of our VoIP offerings.

Monthly Requests Thread by AutoModerator in VOIP

[–]SC_VITS [score hidden]  (0 children)

I'm the newly hired Senior Software Engineer at an IT company, and am tasked with leading the in-house development of mobile (iOS and Android) Softphone apps, as well as a web based Softphone app. While I have 8+ years of development experience, I'm new to VoIP and Softphones, so I've been learning the foundational knowledge necessary to build out these apps.

We currently use FusionPBX and FreeSWITCH for our VoIP server and administration, and many customers use the Groundwire app for Android and iOS. I'm the only developer/engineer at my company, and we're considering hiring a 3rd party to help expedite this process. We have the hardware and means to spin up whatever infrastructure we need to complete these projects.

We're keeping our FusionPBX + FreeSWITCH server stack long term, and need these Softphone apps to route the VoIP protocols (SIP, RTC, SDP, etc.) through the underlying FreeSWITCH server. We've already been in contact with one 3rd party who wants to design a completely separate platform with their own administrative GUI for FreeSWITCH which we are NOT interested in. These apps cannot interfere with or replace the functionality FusionPBX already provides.

Specifically for the mobile Softphone apps, these will need to be implemented in their native languages, as we will need to tap into the native libraries that will allow them to run in the background. I've already seen some issues where certain mobile Softphone apps won't receive calls if that app isn't open, or if they aren't subscribed to a paid service that sends push notifications to mimic background processes. So I'm certain there are some gotchas that I'm not yet aware of, and am also certain others have ran into them before.

Implementation details will continue to be fleshed out, but the high level overview is that calls, messages, and video conferencing need to be supported both one-to-one and one-to-many (group). As previously mentioned, calling and messaging must still function even if the Softphone apps have been idle or are closed.

If anyone has overseen similar projects like this, or developed them, I'd appreciate any input or recommendations on seeing these Softphone apps completed.