Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 9 years ago.
Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Questions asking for code must demonstrate a minimal understanding of the problem being solved. Include attempted solutions, why they didn't work, and the expected results. See also: Stack Overflow question checklist
Improve this question
How can I make my application send SMS using C#? My current configuration sends E-mail alerts but SMS alerts are better suited for my purpose. Any way I can do that for free/paid?
You need an SMS provider. One such provider is clickatell.com who I have bought in bulk from before. They have a good service, and an extensive API. You have to pay for the SMS, but like everything in life, the better quality stuff costs more. I've found them reliable and their phone support is good.
There are a few free ones out there, but they are obviously going to be heavily restricted and finding one that allows use for commercial products would be hard to find. You also have to be careful with user data, free ones may auto sign your numbers on for marketting etc, so make sure your users are aware of that if that's the route you wish to take.
Just a disclaimer that I have no affiliation with Clickatell, and there are lots more options out there, but beware of resellers who provide sub par service at inflated prices.
Second vote for ClickATell for fast, flexible, simultaneous SMS delivery (and full tracking of SMS message delivery status).
An alternative is that you could use a USB/serial GSM modem (WaveCom) or cell phone and send SMS's via the venerable 'AT' command set. For serial-based SMS, there are quite a few .NET component sets, to make it easier. One such component set is TOxygenSMS. Going the serial route means each SMS takes about 5 seconds and must be sent in series.
I have used both with great success. Use a SMS gateway if you have Internet access and a GSM modem in other cases.
We have been using Essendex for a while now and it works well and pretty reliable.
without a SMS sending gateway it is not possible. you need a services provider who provide you a services to sending sms see here a aticle
http://www.developershome.com/sms/howToChooseSMSGateway.asp
If this is for a small application the you don't need to pay for a gateway. Assuming that you know the provider, you can just use this list of SMS transit providers. For the most part, the big players offer it but they may have some limitations for number of texts per day. It works very well - you just have to send an email to: 1234567890#sms.provider.com.
I have written a C# library for Twilio that lets you send SMS in two lines of code.
Note that while I now work at Twilio, I released this library prior to working here.
A free option to get text message alerts is actually just create an account on www.totxt.com and you can just send an email to USER_NAME#totxt.com and receive it via SMS. This is better for alerts for a small group then for bulk SMS.
alternative to SMS Gateway is using a Modem maybe a phone or a GSM Modem and study of AT Commands.
you can use .net SerialPort Class
Related
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I was wondering if anyone can suggest a third-party solution to do the following?
I'm a developer/freelancer. I need an online solution to let beta-testers and other developers communicate bug reports, submit feature requestes (from "internal" beta-testers, and just not software users) back and forth between our small team. Preferably the system that can be updated from both ends: developers - beta-testers, that could also keep history of all such communication.
I have a webform to a local mailbox that triggers a mail to my personal account when there's something to read (that means: when unread inbox messages count changes from 0 to 1). When the message requires an answer I send an email to the user (users are required to provide a valid email on registration).
In extreme cases I leave a personal message to the user popping as a simple javascript alert next time he/she logs in or (if already logged in) requests a page. If I need to make sure he/she will read it I use confirm method and keep showing it in every page loaded until accept button is pressed.
You can set up a free online chat applet on a webpage to complement that. Check this one out, for example: http://www.phpfreechat.net/demo
Facebook also works quite good (instant messaging, posting to everybody).
A Blog with RSS (any CMS: wordpress, drupal... includes a number of modules to set up a blog in a minute with just a few wizard steps) is also a good way to communicate news and updates.
A Forum (phpBB for example) is very easy to set up, but more difficult to maintain (repeated posts, scattered info without structure, etc... It's less resource efficient than other systems, in my opinion).
A wiki is a good solution for FAQs and user manuals. You can read more about it here: http://www.wikihow.com/Start-a-Wiki
A dedicated Q&A site can also be a good idea because people vote the most interesting and useful topics, but it has the same drawbacks as the forum, though they're (in my opinion) easier to handle. There are many precooked Q&A opensource projects with almost if not all the functions you can find here on the stackexchange network, ready to deploy in a minute. I particularly like this one: http://www.question2answer.org/
A bugtracker is quite technical but it works as a charm with experienced users (If your beta testers belong to the programmers community don't even think it twice: just have it online ASAP!). I like bugzilla, but you have many different ones to choose from. A comparison of bugtracking systems can be found on wikipedia: http://en.wikipedia.org/wiki/Comparison_of_issue-tracking_systems
Finally, but not the less important, don't discard deploying surveys, they're very good to make statistics on your project's weak and strong points and also on user experience and expectations (functionalities to add/improve and fix). Some sites like surveymonkey.com make this very easy.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 9 years ago.
Improve this question
I am developing a very basic DNS server for my own purpose. The way I understand it, the DNS server receives UDP packets containing the requested domain name and returns the corresponding IP under some kind of standard form.
There is a standard library for reading/writing UDP packets from/to binary format. But where can I find a C# library for serialising/deserialising DNS requests/responses?
The open source ARSoft.Tools.Net library contains a DNS Server component (see documentation).
You could use this library directly, or just use the source as a starting point for building your own DNS request serializer.
As far as I can tell, I couldn't find a library for C# which handles DNS packet serialization/deserialization, which means it's likely you'll have to roll your own.
Edit: I came across this network packet sniffer project on Code Project which might have what you need. Claims to be able to to parse TCP/UDP/DNS
I did find this very helpful site for TCP/IP which has a pretty comprehensive set of pages describing DNS packet types including the general message format.
There might be some additional help from this previous SO question though.
If you look at wikipedia you find a list over all RFC's for the dns protocol, i find rfc's to be the best way to implement a network protocol!
now the dns protocol has rather many rfc's so i dont know if this is the best way to read up on the protocol but you get all the information you need atleast.
http://en.wikipedia.org/wiki/Domain_Name_System#Internet_standards
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
I am a little confused with SMS and how to send them. I been searching around and I see you can purchase sms texts. I seen some where you get 10k text msgs for $490 but I find this very expensive and I am wonder if there is a better way that would be well free.
I know many sites use have SMS reminders such as google calendar. I am sure google hosts there own server or something.
I also know of alot smaller sites that charge $3/month for their service and one of the features in their service is to send you sms alerts. I highly doubt that they are paying 4cents at text and allow unlimited reminders.
So is there a gateway that I can host myself that is free? Preferably something that works on windows machines.
Or do these sites use like email to sms or something like that and thats how they get it for free?
I am trying to figure out how to make it free on my end to send. I find it kinda stupid that services have to pay to send these messages. I would have figured it would be like email where you can send them for free.
I understand the person receiving the SMS message might have to pay but that depends on their cell phone plan.
Your options:
Email-to-SMS Gateway
Pros
Free
Cons
Delivery not as reliable as native
Non-standard message formatting between carriers
Subject to stricter 'spam' guards that can catch non-spam messages
You have to know what carrier your user is using, and they have to notify you if it changes
SMS Gateway
Pros
More reliable
Consistent formatting
Easily handle replies
Virtually indistinguishable to a carrier from text messages sent from a human
Most offer a simple API
Cons
Costs money. This won't change until the carriers stop charging for them on both ends, which I wouldn't hold your breath for since it's such a huge profit center for them.
Do-it-yourself
Pros
You get to learn how GSM modems and AT commands work making you a 1337 hax0r.
Cons
Complicated
Still have to pay carriers per message
Doesn't scale.
I happen to work for a gateway (Twilio) so I deal with this question a lot. We frequently have customers that started down the email route and gave up due to the hassles associated with that method. You can get away with email-to-SMS for small volume, non-important messages. If you're serious about it, sign up for a gateway. There are a lot of them out there.
One way to do this is to use an email to sms gateway. Here, you just send a short plaintext email to a special address like #vzwtext.com for a Verizon number.
A quick search turned up this list: http://www.mutube.com/projects/open-email-to-sms/gateway-list/.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking for code must demonstrate a minimal understanding of the problem being solved. Include attempted solutions, why they didn't work, and the expected results. See also: Stack Overflow question checklist
Closed 9 years ago.
Improve this question
How can I send an SMS message to a cellular phone number from an ASP.NET web site?
If you know the service provider you can send an email to their phone, which is then converted into an sms message. For instance with Verizon Wireless phones it would be phonenumber#vtext.com
Here is a list of popular US carriers and the email addresses they use.
If you don't you could try an SMS gateway service. I'm not sure of any because I have never tried.
You will need to use an SMS service provider. They will have an API, such as a web service or some other url, which you will call to send the SMS.
There are two ways:
1) Get a contract with the network onto which you want to send SMS.
it will probably be quite expensive if your not sending alot of messages.
You will need a new contract with each network provider you want to use.
2) Use a sms service provider.
Which one to use depends on where you live and what networks you want to send to.
we use http://www.cellsynt.com/en/ simple and reliable.
You could ofcourse use some Mail2SMS provider, but then you need to know what network the number is on. In case of sending SMS to your friend that is an option but if there could be any other number your better of using option 2 until you send tons of messages then option 1 might be cheaper.
As most people have already said you can use a service provider, you can also get a connection to a carrier's SMSC (unlikely) another option is using a GSM modem. They usually come with an API that will allow you to among other things send SMS messages.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
Anyone know of a free SMS library or webservice for .NET that will allow me to send text messages to people's cell phones?
What are you looking for actually? a Library or a Proxy?
a Library is just an API that you can program to in a user-friendly way... that, there are hundreds out there, because that you need to add all the payed proxies, they all give you an API to program to.
If you are talking about Proxies, 98% of the proxies out there are not for free, and you need to pay a monthly basis amount of per SMS sent, it's up to you. All of them have trial versions (for example 100 SMS that you can send for free... normally called Credits).
There is some open source projects for SMS proxies, but for the Linux world like Kannel.
You can make your own using COMM interface and have a old mobile with a card that you can send commands to and make your own API interface based on that (there are plenty of SMS free packages and you might have it as well in your country)
for now... try this link:
http://email2sms.ru/sms.php
and a nice but old article on how to send sms using your own phone:
http://www.oreillynet.com/pub/a/wireless/2003/10/10/sms.html
Try bulksms, very cheap and provide an incoming and outgoing service in pretty much every country for local SMS rates.
ReadWriteWeb
http://www.readwriteweb.com/archives/zeep_mobile_free_sms_gateway.php
Clickatel and most other SMS gateway providers provide some trial credits. And some service providers provide Email2SMS conversion. i.e You can send an email to +94xxxxxxx#yourprovider.com and it will be sent as an SMS.
These information does not answer your question directly but they would be useful in your taks..
Use a SMS provider like clickatell. Sending a SMS is just a matter of sending a correct HTTP GET request containing your account information, the message and the recipient. See: http://support.clickatell.com/guides/clickatell/api_guide.php.
From .NET, you simply use the System.Net.WebClient class to create a correct HTTP GET request. Docs: http://msdn.microsoft.com/en-us/library/system.net.webclient(VS.80).aspx
Actually I found a pretty good one called PennySMS. It has a pretty good and simple web service I can consume and seems to work with all different types of cell phones.