[mc_]

Understood. I don't want to deter you; I will instead suggest taking a little more time to learn about telecom, SIP, and running telecom infrastructure. Just glancing at your repo, I see you are trying to send/receive the SIP yourself, which is ambitious. SIP interop probably accounts for a larger-than-it-should-be percentage of support issues; non-negligible amounts of time are spent arguing with other carriers and phone manufacturers about interpretations of the SIP RFCs.

Spend some time trawling the various soft-switch mailing lists. Join the VoiceOps mailing list and trawl through there. Read the SIP RFCs and curse their use of MAY and MIGHT and SHOULD! :)

There's a lot of wisdom baked into the projects about how to handle phone calls; I don't know that there's money to be made redoing their work to be honest. Scratch the itch for sure! But be honest in your expectations - you're probably looking at years before your project becomes viable (unless there's a JS/Node SIP stack out there you could plug into already?) in a commercial sense.

Best of luck!

[zackify]

Thanks for all the tips! Yes I have been reading through the SIP RFC’s haha. Making this for the company I work at so I have a small amount of phones. I may publish a list of the ones the library will support. But I figure, if it gets big enough, other people can help fix the issues between phones. Everything just feels so old school and a pain to configure. It’s worth trying, who knows if I’ll get it to a working state. But I truly think it’ll be way better than anything out there!