Hi, I dont know if it would be "problematic".. but of course it would be analized case-by-case. At least here in Brazil does not seems to be a big problem. About the MMS traffic, the protocol deals with the reliability, and it is "by design" very reliable, even more than email. Regarding to the cost, this is a real issue. Most providers have expensive rates (if you look at the data amount you are sending, it is one of the most expensive rates for data delivery), but at the same time, some providers have special promotions, with monthly plans. Here in Brazil my operator (vivo) has a plan for ilimited SMS messages for 1 dollar/week, but I dont know the KB limit for these messages. (depends os smpp configuration, but I can make tests here). I found one contract for another plan that was limiting it to 10.000 sms messages per month, so this can vary a lot.
About the voip, this is a valid scenario, but we were thinking in situations like a security team protecting someone. Sometimes they just need to communicate easily with each other, in the field, in a true secure channel, with something that does not need a high power transmitter (radio) and not in a laptop (that can have an open mic too). []s, Ricardo Mello 2015-11-17 23:39 GMT-02:00 Steve Underwood <[email protected]>: > I suspect the use of MMS might be very problematic. The MMS market never > took off, and I doubt most networks are well configured to carry > significant amounts of MMS traffic. Also, in most places it would cost a > fortune to send large amounts as MMS. Most places have internet support > on their networks these days, so most people would just go for encrypted > VoIP across an internet connection these days. > > Regards, > Steve > > On 11/17/2015 09:13 PM, Ricardo Andere de Mello wrote: > > Hi, > > > > I have thought several times about a secure GSM phone, and one thing > > that I paticularly dont like is the fact that GSM phones, even if > > connected through audio jacks or bluetooth mics, can still operate in > > a non secure way. > > The the GSM module firmware is usually not open, and they can in > > theory open the internal mic to hear us at any time. > > > > So... my idea is pretty simple. why DO NOT HAVE MIC AT ALL? > > If you use a GSM raw module, you dont need the mic, speaker, and all > > audio stuff. > > > > ok... so... how to transmit the data if we dont have a mic? > > > > just use encrypted codec2 payloads over MMS. :) > > MMS supports at minimum 300kb (enough for push-to-talk conversation) > > At the same time, both ends would be encrypted, and this is the best > > encryption system I can think since it is totally under your control. > > > > If you need some help with this, drop me a line. > > > > []s, Ricardo Mello > > > > > > 2015-11-12 11:02 GMT-02:00 Nouman Khalid/A-XEN R&D/NRTC > > <[email protected] <mailto:[email protected]>>: > > > > Hello List, > > I am working on sm1000 for secure gsm phone > > project just like jackpair. I initially learned to work in the > > LINUX environment and built some basic codes for sm1000 and tested > > them. Then I built sm1000 firmware of codec2 and tested it > > successfully. As far as gsm phone is concerned, is it possible to > > connect sm1000 with gsm phone directly as jackpair is doing? I am > > asking this because mobile phone will also use its own codec for > > compression and if we apply an already compressed voice on audio > > jack of mobile phone; will it be able to retrieved as encryption > > will be added in FreeDV mode? Please guide me how I can make > > sm1000 work in full duplex mode? > > > > > > Thanks and Regards > > Nauman Khalid > > Assistant Executive Engineer > > Research & Development – NRTC, Pakistan > > Phone: +92-995-666-646 <tel:%2B92-995-666-646>/634 > > Mobile:+92-3008098569 <tel:%2B92-3008098569>/+923208098569 > > <tel:%2B923208098569> > > Email : [email protected] <mailto:[email protected]> > > Web : www.nrtc.com.pk <http://www.nrtc.com.pk> > > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > > Freetel-codec2 mailing list > > [email protected] > > <mailto:[email protected]> > > https://lists.sourceforge.net/lists/listinfo/freetel-codec2 > > > > > > > > > > > ------------------------------------------------------------------------------ > > > > > > _______________________________________________ > > Freetel-codec2 mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/freetel-codec2 > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Freetel-codec2 mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/freetel-codec2 >
------------------------------------------------------------------------------
_______________________________________________ Freetel-codec2 mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freetel-codec2
