Permalink
Browse files

Latest changes.

  • Loading branch information...
1 parent 8a65b16 commit f69cd0026940182456946b049b0655b7ba322dd4 attdevsupport committed Jul 18, 2012
Showing with 1,759 additions and 870 deletions.
  1. +7 −0 MMS/Csharp/app1/Default.aspx
  2. +64 −38 MMS/Csharp/app1/README.txt
  3. +7 −0 MMS/Csharp/app2/Default.aspx
  4. +80 −42 MMS/Csharp/app2/README.txt
  5. +8 −1 MMS/Csharp/app3/Default.aspx
  6. +8 −1 MMS/Csharp/app3/Listener.aspx
  7. +54 −32 MMS/Csharp/app3/README.txt
  8. +7 −0 MMS/Vb/app1/Default.aspx
  9. +1 −1 MMS/Vb/app1/Default.aspx.vb
  10. +64 −38 MMS/Vb/app1/README.txt
  11. +7 −0 MMS/Vb/app2/Default.aspx
  12. +1 −1 MMS/Vb/app2/Default.aspx.vb
  13. +80 −42 MMS/Vb/app2/README.txt
  14. +8 −1 MMS/Vb/app3/Default.aspx
  15. +1 −1 MMS/Vb/app3/Default.aspx.vb
  16. +8 −1 MMS/Vb/app3/Listener.aspx
  17. +1 −1 MMS/Vb/app3/Listener.aspx.vb
  18. +54 −32 MMS/Vb/app3/README.txt
  19. +7 −0 Notary/Csharp/app1/Default.aspx
  20. +8 −1 Notary/Csharp/app1/Default.aspx.cs
  21. +81 −38 Notary/Csharp/app1/README.txt
  22. +7 −0 Notary/Vb/app1/Default.aspx
  23. +8 −1 Notary/Vb/app1/Default.aspx.vb
  24. +81 −38 Notary/Vb/app1/README.txt
  25. +7 −0 Payment/Csharp/app1/Default.aspx
  26. +96 −61 Payment/Csharp/app1/README.txt
  27. +8 −1 Payment/Csharp/app1/listener/Default.aspx
  28. +4 −3 Payment/Csharp/app1/listener/Default.aspx.cs
  29. +7 −0 Payment/Csharp/app2/Default.aspx
  30. +114 −60 Payment/Csharp/app2/README.txt
  31. +8 −1 Payment/Csharp/app2/listener/Default.aspx
  32. +4 −3 Payment/Csharp/app2/listener/Default.aspx.cs
  33. +7 −0 Payment/Vb/app1/Default.aspx
  34. +1 −1 Payment/Vb/app1/Default.aspx.vb
  35. +98 −45 Payment/Vb/app1/README.txt
  36. +8 −1 Payment/Vb/app1/listener/Default.aspx
  37. +5 −3 Payment/Vb/app1/listener/Default.aspx.vb
  38. +7 −0 Payment/Vb/app2/Default.aspx
  39. +1 −1 Payment/Vb/app2/Default.aspx.vb
  40. +118 −50 Payment/Vb/app2/README.txt
  41. +8 −1 Payment/Vb/app2/listener/Default.aspx
  42. +4 −3 Payment/Vb/app2/listener/Default.aspx.vb
  43. +7 −0 SMS/Csharp/app1/Default.aspx
  44. +63 −38 SMS/Csharp/app1/README.txt
  45. +7 −0 SMS/Csharp/app2/Default.aspx
  46. +8 −1 SMS/Csharp/app2/Listener.aspx
  47. +66 −44 SMS/Csharp/app2/README.txt
  48. +7 −0 SMS/Vb/app1/Default.aspx
  49. +1 −1 SMS/Vb/app1/Default.aspx.vb
  50. +64 −38 SMS/Vb/app1/README.txt
  51. +7 −0 SMS/Vb/app2/Default.aspx
  52. +1 −1 SMS/Vb/app2/Default.aspx.vb
  53. +8 −1 SMS/Vb/app2/Listener.aspx
  54. +1 −1 SMS/Vb/app2/Listener.aspx.vb
  55. +67 −44 SMS/Vb/app2/README.txt
  56. +3 −2 Speech/Csharp/app1/README.txt
  57. +1 −1 Speech/Vb/app1/Default.aspx.vb
  58. +3 −2 Speech/Vb/app1/README.txt
  59. +7 −0 TL/Csharp/app1/Default.aspx
  60. +61 −34 TL/Csharp/app1/README.txt
  61. +7 −0 TL/Vb/app1/Default.aspx
  62. +1 −1 TL/Vb/app1/Default.aspx.vb
  63. +61 −34 TL/Vb/app1/README.txt
  64. +2 −2 WAP/Csharp/app1/Default.aspx
  65. +9 −1 WAP/Csharp/app1/Default.aspx.cs
  66. +64 −38 WAP/Csharp/app1/README.txt
  67. +2 −2 WAP/Vb/app1/Default.aspx
  68. +10 −2 WAP/Vb/app1/Default.aspx.vb
  69. +64 −38 WAP/Vb/app1/README.txt
@@ -1,3 +1,10 @@
+<!--
+Licensed by AT&T under 'Software Development Kit Tools Agreement.' 2012
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION: http://developer.att.com/sdk_agreement/
+Copyright 2012 AT&T Intellectual Property. All rights reserved. http://developer.att.com
+For more information contact developer.support@att.com
+-->
+
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Default.aspx.cs" Inherits="MMS_App1" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
View
@@ -1,9 +1,21 @@
+******************************************************************************************
+* Licensed by AT&T under 'Software Development Kit Tools Agreement.' 2012
+* TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION: http://developer.att.com/sdk_agreement/
+* Copyright 2012 AT&T Intellectual Property. All rights reserved. http://developer.att.com
+* For more information contact developer.support@att.com<mailto:developer.support@att.com>
+******************************************************************************************
AT&T API Samples - MMS app 1
------------------------------
+This application allows the user to
-This file describes how to set up, configure and run the C# Applications of the AT&T HTML5 Program sample applications.
-It covers all steps required to register the application on DevConnect and, based on the generated API keys and secrets,
+ 1. Send MMS without attachement
+ 2. Send MMS with maximum 3 attachements
+ 3. Check the delivery status of the MMS
+
+This file describes how to set up, configure and run the C# Applications of the
+AT&T Platform API sample applications. It covers all steps required to register
+the application on DevConnect and, based on the generated API keys and secrets,
create and run one's own full-fledged sample applications.
1. Configuration
@@ -14,70 +26,84 @@ create and run one's own full-fledged sample applications.
1. Configuration
- Configuration consists of a few steps necessary to get an application registered on DevConnect with the proper services and
- endpoints, depending on the type of client-side application (autonomous/non-autonomous).
+ Configuration consists of a few steps necessary to get an application registered
+ on DevConnect with the proper services and endpoints, depending on the type of
+ client-side application (autonomous/non-autonomous).
- To register an application, go to https://devconnect-api.att.com/ and login with your valid username and password.
- Next, choose "My Apps" from the bar at the top of the page and click the "Setup a New Application" button.
+ To register an application, go to https://devconnect-api.att.com/ and login with
+ your valid username and password. Next, choose "My Apps" from the bar at the top
+ of the page and click the "Setup a New Application" button.
Fill in the form, in particular all fields marked as "required".
- Be careful while filling in the "OAuth Redirect URL" field. It should contain the URL that the oAuth provider will redirect
- users to when he/she successfully authenticates and authorizes your application.
+ Be careful while filling in the "OAuth Redirect URL" field. It should contain the
+ URL that the oAuth provider will redirect users to when he/she successfully
+ authenticates and authorizes your application.
+
+NOTE: You MUST select Payment in the list of services under field 'Services' in
+order to use this sample application code.
-NOTE: You MUST select MMS in the list of services under field 'Services' in order to use this sample application code.
+ Having your application registered, you will get back an important pair of data:
+ an API key and Secret key. They are necessary to get your applications working
+ with the AT&T Platform APIs.
- Having your application registered, you will get back an important pair of data: an API key and Secret key. They are
- necessary to get your applications working with the AT&T HTML5 APIs. See 'Adjusting parameters' below to learn how to use
- these keys.
+ Initially your newly registered application is restricted to the "Sandbox"
+ environment only. To move it to production, you may promote it by clicking the
+ "Promote to production" button. Notice that you will get a different API key and
+ secret, so these values in your application should be adjusted accordingly.
- Initially your newly registered application is restricted to the "Sandbox" environment only. To move it to production,
- you may promote it by clicking the "Promote to production" button. Notice that you will get a different API key and secret,
- so these values in your application should be adjusted accordingly.
+ Depending on the kind of authentication used, an application may be based on
+ either the Autonomous Client or the Web-Server Client OAuth flow (see
+ https://devconnect-api.att.com/docs/oauth20/autonomous-client-application-oauth-flow
+ or https://devconnect-api.att.com/docs/oauth20/web-server-client-application-oauth-flow
+ respectively).
- Depending on the kind of authentication used, an application may be based on either the Autonomous Client or the Web-Server
- Client OAuth flow (see https://devconnect-api.att.com/docs/oauth20/autonomous-client-application-oauth-flow or
- https://devconnect-api.att.com/docs/oauth20/web-server-client-application-oauth-flow respectively).
2. Installation
** Requirements
- To run the this sample application you need an IIS Server.
-
+ To run the examples you need an IIS Server.
-3. Parameters
+ Download the application files from the download link published in AT&T portal
+ into webdomain of your IIS server.
-
-Each sample application contains a config.web file. It holds configurable parameters described in an easy to read format. Please populate the following parameters in config.web as specified below:
-1) api_key : {set the value as per your registered application 'API key' field value}
+3. Parameters
-2) secret_key : {set the value as per your registered application 'Secret key' field value}
+Each sample application contains a web.config file. It holds configurable parameters
+described in an easy to read format. Please populate the following parameters in
+web.config as specified below:
+1) api_key : This is mandatory parameter, Set the value as per your
+ registered appliaction 'API key' field value.
-3) authorize_redirect_uri : {set the value as per your registered application 'OAuth Redirect URL' field value}
+2) secret_key : This is mandatory parameter, Set the value as per your
+ registered appliaction 'Secret key' field value.
-4) FQDN : https://api.att.com
+3) endPoint : This is mandatory parameter, Set it to the end point
+ URI of AT&T Service.
-5) scope : SMS
+4) scope : MMS (Scope of the ATT service that will be invoked by
+ the Application)
-6) short_code : {set the value as per your registered application 'short code' field value}
+5) AccessTokenFilePath : ~\\MMSApp1AccessToken.txt (This is optional parameter,
+ which points to the file path, where application
+ stores access token information. If the parameter is
+ not configured, it will take the default value as
+ ~\\MMSApp1AccessToken.txt. Give read/write access to
+ this file.)
-7) AccessTokenFilePath : {set the value to the path of the file, which application creates and stores access token }
-Note: If your application is promoted from Sandbox environment to Production environment and you decide to use production application settings, you must update parameters 1-2 as per production application details.
+Note: If your application is promoted from Sandbox environment to Production environment
+and you decide to use production application settings, you must update parameters 1-2
+as per production application details.
4. Running the application
-Suppose you copied the sample app files in your IIS server webroot/mms/app1/ folder, In order to run the sample application, type in'http://IIS_HOSTNAME/mms/app1/Default.aspx'
-
-
-
-
-
-
+Suppose you copied the sample app files in your IIS server webroot/mms/app1/ folder.
+In order to run the sample application, type in'http://IIS_HOSTNAME/mms/app1/Default.aspx'.
@@ -1,3 +1,10 @@
+<!--
+Licensed by AT&T under 'Software Development Kit Tools Agreement.' 2012
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION: http://developer.att.com/sdk_agreement/
+Copyright 2012 AT&T Intellectual Property. All rights reserved. http://developer.att.com
+For more information contact developer.support@att.com
+-->
+
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Default.aspx.cs" Inherits="MMS_App2" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
View
@@ -1,9 +1,23 @@
+******************************************************************************************
+* Licensed by AT&T under 'Software Development Kit Tools Agreement.' 2012
+* TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION: http://developer.att.com/sdk_agreement/
+* Copyright 2012 AT&T Intellectual Property. All rights reserved. http://developer.att.com
+* For more information contact developer.support@att.com<mailto:developer.support@att.com>
+******************************************************************************************
AT&T API Samples - MMS app 2
------------------------------
-This file describes how to set up, configure and run the C# Applications of the AT&T HTML5 Program sample applications.
-It covers all steps required to register the application on DevConnect and, based on the generated API keys and secrets,
+This is a server side application which also has a web interface. The application
+looks for a file called numbers.txt containing MSISDNs of desired recipients, and
+an image called coupon.jpg, and message text from a file called subject.txt, and
+then sends an MMS message with the attachment to every recipient in the list. This
+can be triggered via a command line on the server, or through the web interface,
+which then displays all the returned mmsIds or respective errors.
+
+This file describes how to set up, configure and run the C# Applications of the
+AT&T Platform API sample applications. It covers all steps required to register
+the application on DevConnect and, based on the generated API keys and secrets,
create and run one's own full-fledged sample applications.
1. Configuration
@@ -14,30 +28,38 @@ create and run one's own full-fledged sample applications.
1. Configuration
- Configuration consists of a few steps necessary to get an application registered on DevConnect with the proper services and
- endpoints, depending on the type of client-side application (autonomous/non-autonomous).
+ Configuration consists of a few steps necessary to get an application registered
+ on DevConnect with the proper services and endpoints, depending on the type of
+ client-side application (autonomous/non-autonomous).
- To register an application, go to https://devconnect-api.att.com/ and login with your valid username and password.
- Next, choose "My Apps" from the bar at the top of the page and click the "Setup a New Application" button.
+ To register an application, go to https://devconnect-api.att.com/ and login with
+ your valid username and password. Next, choose "My Apps" from the bar at the top
+ of the page and click the "Setup a New Application" button.
Fill in the form, in particular all fields marked as "required".
- Be careful while filling in the "OAuth Redirect URL" field. It should contain the URL that the oAuth provider will redirect
- users to when he/she successfully authenticates and authorizes your application.
+ Be careful while filling in the "OAuth Redirect URL" field. It should contain the
+ URL that the oAuth provider will redirect users to when he/she successfully
+ authenticates and authorizes your application.
+
+NOTE: You MUST select MMS in the list of services under field 'Services' in order
+to use this sample application code.
-NOTE: You MUST select MMS in the list of services under field 'Services' in order to use this sample application code.
+ Having your application registered, you will get back an important pair of data:
+ an API key and Secret key. They are necessary to get your applications working
+ with the AT&T Platform APIs.
- Having your application registered, you will get back an important pair of data: an API key and Secret key. They are
- necessary to get your applications working with the AT&T HTML5 APIs. See 'Adjusting parameters' below to learn how to use
- these keys.
+ Initially your newly registered application is restricted to the "Sandbox"
+ environment only. To move it to production, you may promote it by clicking the
+ "Promote to production" button. Notice that you will get a different API key and
+ secret, so these values in your application should be adjusted accordingly.
- Initially your newly registered application is restricted to the "Sandbox" environment only. To move it to production,
- you may promote it by clicking the "Promote to production" button. Notice that you will get a different API key and secret,
- so these values in your application should be adjusted accordingly.
+ Depending on the kind of authentication used, an application may be based on
+ either the Autonomous Client or the Web-Server Client OAuth flow (see
+ https://devconnect-api.att.com/docs/oauth20/autonomous-client-application-oauth-flow or
+ https://devconnect-api.att.com/docs/oauth20/web-server-client-application-oauth-flow
+ respectively).
- Depending on the kind of authentication used, an application may be based on either the Autonomous Client or the Web-Server
- Client OAuth flow (see https://devconnect-api.att.com/docs/oauth20/autonomous-client-application-oauth-flow or
- https://devconnect-api.att.com/docs/oauth20/web-server-client-application-oauth-flow respectively).
2. Installation
@@ -46,46 +68,62 @@ NOTE: You MUST select MMS in the list of services under field 'Services' in orde
To run the this sample application you need an IIS Server.
+ Download the application files from the download link published in AT&T portal
+ into webdomain of your IIS server.
-3. Parameters
-
-Each sample application contains a config.web file. It holds configurable parameters described in an easy to read format. Please populate the following parameters in config.web as specified below:
-1) api_key : {set the value as per your registered application 'API key' field value}
-
-
-2) secret_key : {set the value as per your registered application 'Secret key' field value}
+3. Parameters
+
+Each sample application contains a web.config file. It holds configurable parameters
+described in an easy to read format. Please populate the following parameters in
+web.config as specified below:
+1) api_key : This is mandatory parameter, Set the value as per your
+ registered appliaction 'API key' field value.
-3) authorize_redirect_uri : {set the value as per your registered application 'OAuth Redirect URL' field value}
+2) secret_key : This is mandatory parameter,Set the value as per your
+ registered appliaction 'Secret key' field value.
-4) FQDN : https://api.att.com
+3) endPoint : This is mandatory parameter, Set it to the end point
+ URI of AT&T Service.
-5) scope : MMS
+5) scope : MMS (Scope of the ATT service that will be invoked by the
+ Application)
-6) short_code : {set the value as per your registered application 'short code' field value}
+7) AccessTokenFilePath : ~\\MMSApp1AccessToken.txt (This is optional parameter,
+ which points to the file path, where application stores
+ access token information. If the parameter is not configured,
+ it will take the default value as ~\\MMSApp1AccessToken.txt.
+ Give read/write access to this file.)
-7) AccessTokenFilePath : {set the value to the path of the file, which application creates and stores access token }
+8) messageFilePath : coupon_info\\message.txt (This is manadatory parameter,
+ which points to the file path, from where application reads
+ the message content to be sent along with the coupon.
+ Give read/write access to this file and folder.)
-8) messageFilePath : {set the value to the path of the file, which application reads the content and sent as message text }
+9) phoneListFilePath : coupon_info\\phone.txt (This is manadatory parameter,
+ which points to the file path, from where application reads
+ the destination address for sending coupon.
+ Give read/write access to this file and folder.)
-9) phoneListFilePath : {set the value to the path of the file, which application reads the content and used as destination numbers for mms message }
+10) couponPath : coupon_info\\ (This is mandatory parameter, which will
+ point to the directory, which contains the image to be sent
+ as the coupon. Give read/write access to this folder.)
-10) couponPath : {set the value to the path of the directory, which contains the image to be sent }
+11) couponFileName : Coupon.jpg (This is mandatory parameter, which is the name
+ of the image/coupon to be sent, make sure that the image
+ exists in the "couponPath" key directory. Give read/write
+ access to this folder.)
-11) couponFileName : {set the value to the path of the image file, which will be sent as an mms messsage}
-Note: If your application is promoted from Sandbox environment to Production environment and you decide to use production application settings, you must update parameters 1-2 as per production application details.
+Note: If your application is promoted from Sandbox environment to Production environment
+and you decide to use production application settings, you must update parameters 1-2 as
+per production application details.
4. Running the application
-Suppose you copied the sample app files in your IIS server webroot/mms/app2/ folder, In order to run the sample application, type in'http://IIS_HOSTNAME/mms/app2/Default.aspx'
-
-
-
-
-
-
+Suppose you copied the sample app files in your IIS server webroot/mms/app2/ folder.
+In order to run the sample application, type in'http://IIS_HOSTNAME/mms/app2/Default.aspx'.
@@ -1,4 +1,11 @@
-<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Default.aspx.cs" Inherits="MMS_App3" %>
+<!--
+Licensed by AT&T under 'Software Development Kit Tools Agreement.' 2012
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION: http://developer.att.com/sdk_agreement/
+Copyright 2012 AT&T Intellectual Property. All rights reserved. http://developer.att.com
+For more information contact developer.support@att.com
+-->
+
+<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Default.aspx.cs" Inherits="MMS_App3" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xml:lang="en" xmlns="http://www.w3.org/1999/xhtml" lang="en">
@@ -1,4 +1,11 @@
-<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Listener.aspx.cs" Inherits="MMSApp3_Listener" %>
+<!--
+Licensed by AT&T under 'Software Development Kit Tools Agreement.' 2012
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION: http://developer.att.com/sdk_agreement/
+Copyright 2012 AT&T Intellectual Property. All rights reserved. http://developer.att.com
+For more information contact developer.support@att.com
+-->
+
+<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Listener.aspx.cs" Inherits="MMSApp3_Listener" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
Oops, something went wrong.

0 comments on commit f69cd00

Please sign in to comment.