The document provides documentation on using the SMS Gateway Interface to send and receive SMS messages. It describes sending SMS messages using HTTP POST with XML, including simple and advanced examples. It also covers sending multiple requests, the response XML format, and code samples for C#, PHP and VB. Additional topics covered include sending SMS using web services, parameters, message length, delivery notifications, receiving SMS, SMS tools, and managing contacts and groups.
The document provides instructions for using an SMS gateway interface to send SMS messages via HTTP POST requests. It describes:
1) How to structure the XML request with elements for user credentials, message content, recipient phone numbers, and optional settings like the sender ID, delivery notifications URLs, and a scheduled send time.
2) Examples of simple and advanced XML requests with explanations of the elements.
3) How to send multiple requests in one call by enclosing them in an InforuRoot element.
4) The structure of the XML response and meaning of possible status codes.
5) Code samples for sending requests in C#, PHP, and VB.NET with instructions on encoding and escaping the XML
The document provides documentation on using the SMS Gateway Interface to send and receive SMS messages. It describes sending SMS messages using HTTP POST with XML, including simple and advanced examples. It also covers sending multiple requests, the response XML format, and code samples for C#, PHP and VB.NET. Additional sections describe using a web service interface, sending SMS with parameters, message character limits, delivery notifications, receiving SMS, SMS tools, and managing contacts and groups.
The document describes an SMS gateway interface that allows sending SMS messages via HTTP POST requests. Key points:
- Clients can send SMS messages by making HTTP POST requests to a URL, passing an XML payload with the message details, recipient numbers, authentication credentials, and other optional parameters.
- The XML payload allows specifying a single message, multiple messages by using an "InforuRoot" element, and various optional settings like delivery notifications, custom IDs, and future delivery times.
- The response returns status codes to indicate success or reason for failure, number of recipients, and is repeated for each request if multiple were sent.
- Examples are given for the XML payload structure and HTTP requests in different
The document provides instructions and code samples for sending SMS messages using the Inforu SMS Gateway API in 3 sentences:
It describes the HTTP POST interface for sending SMS messages with XML requests, including simple and advanced XML examples and describes the response XML structure. Code samples are provided in C#, PHP, and VB for sending SMS messages by constructing an XML request and posting it to the API URL. The document also covers additional features like sending messages at a later time, delivery notifications, and receiving SMS.
API למפתחים לערוץ SMS במערכת InforUMobileinforumobile
This document provides instructions and examples for using the Inforu SMS Gateway Interface to send SMS messages programmatically. It describes:
- Sending SMS using a simple or advanced HTTP POST request with an XML payload.
- XML structures for specifying sender/recipient details, message content, and optional parameters like delivery notifications or scheduled sending times.
- Code samples for HTTP POST requests to the SMS gateway in C#, PHP, and VB.
- Additional SMS gateway APIs and features like receiving SMS, checking quotas/blocking numbers, and deleting future messages.
Web service api - InfoSMS By InforUMobileinforumobile
The document describes a web service interface for sending SMS messages through InforuMobile. It provides details on the functions, parameters, and response codes for the SendSms and SendSmsDetailed functions. Microsoft .NET and other platforms can access this interface by adding a reference to the SendMessage.asmx URL and web service. The functions allow sending SMS messages by specifying parameters for user credentials, phone numbers, message text, send time/date and more.
This document provides documentation on the SMS gateway interface for InforUMobile Ltd. It describes several methods for sending SMS messages programmatically, including an HTTP POST interface using an XML request, a web service interface, and examples of code for C#, PHP, and VB. It also covers additional SMS tools and functions for managing contacts and groups.
This document describes an API for sending SMS messages via HTTP requests. It provides examples of XML structures for simple, advanced, and multiple requests. It also covers response XML, code samples for HTTP post in C#, PHP and VB, and additional parameters like delivery notifications, message character limits, and tools for checking quotas and blocking numbers.
The document provides instructions for using an SMS gateway interface to send SMS messages via HTTP POST requests. It describes:
1) How to structure the XML request with elements for user credentials, message content, recipient phone numbers, and optional settings like the sender ID, delivery notifications URLs, and a scheduled send time.
2) Examples of simple and advanced XML requests with explanations of the elements.
3) How to send multiple requests in one call by enclosing them in an InforuRoot element.
4) The structure of the XML response and meaning of possible status codes.
5) Code samples for sending requests in C#, PHP, and VB.NET with instructions on encoding and escaping the XML
The document provides documentation on using the SMS Gateway Interface to send and receive SMS messages. It describes sending SMS messages using HTTP POST with XML, including simple and advanced examples. It also covers sending multiple requests, the response XML format, and code samples for C#, PHP and VB.NET. Additional sections describe using a web service interface, sending SMS with parameters, message character limits, delivery notifications, receiving SMS, SMS tools, and managing contacts and groups.
The document describes an SMS gateway interface that allows sending SMS messages via HTTP POST requests. Key points:
- Clients can send SMS messages by making HTTP POST requests to a URL, passing an XML payload with the message details, recipient numbers, authentication credentials, and other optional parameters.
- The XML payload allows specifying a single message, multiple messages by using an "InforuRoot" element, and various optional settings like delivery notifications, custom IDs, and future delivery times.
- The response returns status codes to indicate success or reason for failure, number of recipients, and is repeated for each request if multiple were sent.
- Examples are given for the XML payload structure and HTTP requests in different
The document provides instructions and code samples for sending SMS messages using the Inforu SMS Gateway API in 3 sentences:
It describes the HTTP POST interface for sending SMS messages with XML requests, including simple and advanced XML examples and describes the response XML structure. Code samples are provided in C#, PHP, and VB for sending SMS messages by constructing an XML request and posting it to the API URL. The document also covers additional features like sending messages at a later time, delivery notifications, and receiving SMS.
API למפתחים לערוץ SMS במערכת InforUMobileinforumobile
This document provides instructions and examples for using the Inforu SMS Gateway Interface to send SMS messages programmatically. It describes:
- Sending SMS using a simple or advanced HTTP POST request with an XML payload.
- XML structures for specifying sender/recipient details, message content, and optional parameters like delivery notifications or scheduled sending times.
- Code samples for HTTP POST requests to the SMS gateway in C#, PHP, and VB.
- Additional SMS gateway APIs and features like receiving SMS, checking quotas/blocking numbers, and deleting future messages.
Web service api - InfoSMS By InforUMobileinforumobile
The document describes a web service interface for sending SMS messages through InforuMobile. It provides details on the functions, parameters, and response codes for the SendSms and SendSmsDetailed functions. Microsoft .NET and other platforms can access this interface by adding a reference to the SendMessage.asmx URL and web service. The functions allow sending SMS messages by specifying parameters for user credentials, phone numbers, message text, send time/date and more.
This document provides documentation on the SMS gateway interface for InforUMobile Ltd. It describes several methods for sending SMS messages programmatically, including an HTTP POST interface using an XML request, a web service interface, and examples of code for C#, PHP, and VB. It also covers additional SMS tools and functions for managing contacts and groups.
This document describes an API for sending SMS messages via HTTP requests. It provides examples of XML structures for simple, advanced, and multiple requests. It also covers response XML, code samples for HTTP post in C#, PHP and VB, and additional parameters like delivery notifications, message character limits, and tools for checking quotas and blocking numbers.
The document describes an API for sending SMS messages through HTTP requests. It provides examples of XML structures for simple, advanced, and multiple requests. It also covers response XML, code samples for HTTP post in C#, PHP and VB, and additional parameters like delivery notifications, message character limits, and tools for checking quotas and blocking numbers.
This document provides information and code samples for using the InforUMobile SMS gateway API. It describes how to send SMS messages using HTTP POST with XML requests, including simple and advanced XML examples. It also covers sending multiple requests, response XML formats, and optional features like delivery notifications, receiving SMS, and API tools. Code samples are provided for C#, PHP, and VB for sending SMS via HTTP POST.
This document provides instructions for using the InforUMobile SMS gateway API. It describes sending SMS messages via HTTP POST with XML, including examples in C#, PHP, and VB. It also covers additional parameters, sending multiple requests, response XML, and receiving delivery notifications. Finally, it discusses an alternative of sending SMS using a web service interface with examples in C#.
The Wireless Messaging API (WMA) allows applications to send and receive messages on mobile devices through protocols like SMS, MMS, and CBS. It defines classes like MessageConnection for composing, sending, and receiving messages, and different message types including text, binary, and multipart messages. The document discusses the WMA classes and permissions, message types, example code, and future directions for the next chapter on MIDP deployment.
The document provides information about using an HTTP API to send SMS messages through the Muthofun reseller platform. It describes the HTTP protocol basics, parameters required for SMS submission requests, examples of different types of SMS submissions (single, multiple recipients, future delivery, etc.), and error codes. It also describes how to check credit balance and view pricing/coverage details using the HTTP API.
The document provides an overview of WhatsApp's end-to-end encryption system. It describes how encryption keys are generated and exchanged between clients to establish encrypted messaging sessions. It explains how message keys are derived to encrypt individual messages sent within a session using protocols that provide forward secrecy. It also covers how media attachments and group messages are encrypted within the system.
This document provides information about an SMS gateway API, including how to send SMS messages using HTTP POST requests or a web service interface. It describes the XML structure for simple and advanced requests, how to send multiple requests, and the response XML structure. It also covers additional features like delivery notifications, receiving SMS, tools for deleting messages and checking quotas/blocks. Code samples are provided for C#, PHP, and VB for sending SMS using the HTTP POST method.
The document provides information about interfaces for controlling and customizing the SMS engine of the Inforu system. It describes the HTTP POST/GET interface format for sending SMS messages programmatically. Examples are given in C#, Visual Basic, and PHP to illustrate making requests to the SMS API endpoint. The response indicates the number of messages sent or an error code. Limits for maximum message lengths per cellular provider in Israel are also listed.
The document provides information about connecting to and using the RouteMobile Messaging Platform SMPP gateway. It describes the required connection parameters, supported message submission types and responses, character sets and data coding, long messages, delivery reports, and supported originator and destination address types. It also includes tables listing the supported SMPP error codes and delivery report status codes.
The document provides an overview of Short Message Service (SMS) technology, including how SMS works, common SMS protocols like SMPP, and some open source SMS gateway software. It describes the basic concepts of SMS such as SMSCs, intra-operator and inter-operator SMS messages, and introduces SMPP as an open protocol for exchanging SMS data between applications and SMSCs. Popular open source SMS gateway software like Kannel and Tambur Messaging Gateway are also mentioned.
The document provides information about the HTTP API for sending SMS through SMSGlobal. It describes how to send SMS requests via HTTP/HTTPS, including required parameters, response formats, delivery receipt notifications via email or HTTP postback, message scheduling, and supported features such as custom sender IDs and international text support. Examples are given of HTTP requests and responses.
This document provides documentation on the HTTP API for sending SMS messages through SMSGlobal. It describes how to send SMS, check balances, and receive delivery receipts via HTTP requests and responses. Key features include custom sender IDs, delivery receipts by email or HTTP callback, international support, and scheduling messages to be sent later.
Interconnection form in the SMS business - explainedDaniela Jovic
What is an 헶헻혁헲헿헰헼헻헻헲헰혁헶헼헻 헳헼헿헺? Why do SMS suppliers need this type of document? Learn how to understand and work with this data!
It usually contains information about the technical details of both
SMS providers - acting as a supplier and/or customer. It consists
of data such as: the protocol used, IP addresses, binds and SMS features. It can also contain data regarding VPN or IPsec tunnels, etc.
This document provides instructions for sending SMS messages using the SMSGATEWAYHUB SMS gateway via HTTP API. It details the required parameters for authentication and sending single, bulk, scheduled, and group messages. It also describes how to check delivery reports and balances. Various error codes are listed to help troubleshoot any issues.
This document proposes a presentation on using a common mediation port in TTCN-3 to execute scripts from test cases. A mediation port is defined that accepts messages containing a script name and parameters. A TRI connects this port to a mediation server hosting scripts in languages like Shell and Perl. Test cases can call scripts by sending messages to the port. This allows tasks like controlling non-SUT devices and databases through scripts without recompiling test suites. Benefits include reduced compilation times when changes are needed and the ability to develop new interfaces quickly by moving functionality to reusable scripts.
Important tips on Router and SMTP mail routingjayeshpar2006
This document provides tips on router and SMTP mail routing in Lotus Domino. It discusses 21 tips covering topics like ignoring location document email addresses, hiding SMTP details, setting message size restrictions, using authentication for SMTP relays, and setting mail routing priorities. The tips are presented by various IBM ICS support engineers and SWAT team members and include references to IBM support documents for additional details.
SMSCountry is a leading bulk SMS messaging service provider established in 2003 in India. It provides comprehensive messaging solutions through its core messaging platform, including push, pull, and two-way messaging. It has tools like an MS Excel plugin and API that allow users to send bulk SMS easily from Excel or their own applications. SMSCountry has a large client base and has received several awards and recognition for its innovative technologies and solutions.
SMSCountry is a leading bulk SMS messaging service provider established in 2003 in India. It provides comprehensive messaging solutions through its core messaging platform, including push, pull, and two-way messaging. It has tools like an MS Excel plugin and API that allow users to send bulk SMS easily from Excel or their own applications. SMSCountry has a large client base and has received several awards and recognition for its innovative technologies and solutions.
With 2 Way SMS Messaging Service by Route Mobile brands can manage inbound campaigns with auto-response, validate service messages, accelerate customer retention & loyalty.
IntelliSMS - Telco Grade, SMS Gateway and Technology Provider Peter Humphries
Intelli Messaging Services (IntelliSMS) is one of Australia's leading SMS Gateway and messaging technology providers.
IntelliSMS provides the infrastructure for Software Developers, Enterprise IT development teams to integrate SMS into their systems.
With clients in Enterprise using our notifications systems such as Powercor and Woolworths and Big Box retailers using our marketing and compliance solutions, IntelliSMS is the only one to turn to if you want to deliver the right message at the right time.
Find out more by visiting https://www.intellisms.com.au
This document provides an overview of WebSphere MQ Administration training notes. It discusses key concepts in message-oriented middleware including messaging, queuing, MQSeries, and the Message Queue Interface. It also describes common MQ objects like queue managers, queues, channels, and messages. The document outlines how applications use MQ calls to connect to queue managers and put and get messages from queues.
We wish to introduce to you our Bulk SMS portal that is like no other you have ever come across. We can boast about it because we are very sure. It can be yours for free, without a single charge. What is more, it can be customized as your own site on your domain name and you can resell to others if you wish.
Please use the following details to login to a demo account set up for you.
URL: http://sms.bytessms.net
Username: democlient19
Password: demo
The document describes an API for sending SMS messages through HTTP requests. It provides examples of XML structures for simple, advanced, and multiple requests. It also covers response XML, code samples for HTTP post in C#, PHP and VB, and additional parameters like delivery notifications, message character limits, and tools for checking quotas and blocking numbers.
This document provides information and code samples for using the InforUMobile SMS gateway API. It describes how to send SMS messages using HTTP POST with XML requests, including simple and advanced XML examples. It also covers sending multiple requests, response XML formats, and optional features like delivery notifications, receiving SMS, and API tools. Code samples are provided for C#, PHP, and VB for sending SMS via HTTP POST.
This document provides instructions for using the InforUMobile SMS gateway API. It describes sending SMS messages via HTTP POST with XML, including examples in C#, PHP, and VB. It also covers additional parameters, sending multiple requests, response XML, and receiving delivery notifications. Finally, it discusses an alternative of sending SMS using a web service interface with examples in C#.
The Wireless Messaging API (WMA) allows applications to send and receive messages on mobile devices through protocols like SMS, MMS, and CBS. It defines classes like MessageConnection for composing, sending, and receiving messages, and different message types including text, binary, and multipart messages. The document discusses the WMA classes and permissions, message types, example code, and future directions for the next chapter on MIDP deployment.
The document provides information about using an HTTP API to send SMS messages through the Muthofun reseller platform. It describes the HTTP protocol basics, parameters required for SMS submission requests, examples of different types of SMS submissions (single, multiple recipients, future delivery, etc.), and error codes. It also describes how to check credit balance and view pricing/coverage details using the HTTP API.
The document provides an overview of WhatsApp's end-to-end encryption system. It describes how encryption keys are generated and exchanged between clients to establish encrypted messaging sessions. It explains how message keys are derived to encrypt individual messages sent within a session using protocols that provide forward secrecy. It also covers how media attachments and group messages are encrypted within the system.
This document provides information about an SMS gateway API, including how to send SMS messages using HTTP POST requests or a web service interface. It describes the XML structure for simple and advanced requests, how to send multiple requests, and the response XML structure. It also covers additional features like delivery notifications, receiving SMS, tools for deleting messages and checking quotas/blocks. Code samples are provided for C#, PHP, and VB for sending SMS using the HTTP POST method.
The document provides information about interfaces for controlling and customizing the SMS engine of the Inforu system. It describes the HTTP POST/GET interface format for sending SMS messages programmatically. Examples are given in C#, Visual Basic, and PHP to illustrate making requests to the SMS API endpoint. The response indicates the number of messages sent or an error code. Limits for maximum message lengths per cellular provider in Israel are also listed.
The document provides information about connecting to and using the RouteMobile Messaging Platform SMPP gateway. It describes the required connection parameters, supported message submission types and responses, character sets and data coding, long messages, delivery reports, and supported originator and destination address types. It also includes tables listing the supported SMPP error codes and delivery report status codes.
The document provides an overview of Short Message Service (SMS) technology, including how SMS works, common SMS protocols like SMPP, and some open source SMS gateway software. It describes the basic concepts of SMS such as SMSCs, intra-operator and inter-operator SMS messages, and introduces SMPP as an open protocol for exchanging SMS data between applications and SMSCs. Popular open source SMS gateway software like Kannel and Tambur Messaging Gateway are also mentioned.
The document provides information about the HTTP API for sending SMS through SMSGlobal. It describes how to send SMS requests via HTTP/HTTPS, including required parameters, response formats, delivery receipt notifications via email or HTTP postback, message scheduling, and supported features such as custom sender IDs and international text support. Examples are given of HTTP requests and responses.
This document provides documentation on the HTTP API for sending SMS messages through SMSGlobal. It describes how to send SMS, check balances, and receive delivery receipts via HTTP requests and responses. Key features include custom sender IDs, delivery receipts by email or HTTP callback, international support, and scheduling messages to be sent later.
Interconnection form in the SMS business - explainedDaniela Jovic
What is an 헶헻혁헲헿헰헼헻헻헲헰혁헶헼헻 헳헼헿헺? Why do SMS suppliers need this type of document? Learn how to understand and work with this data!
It usually contains information about the technical details of both
SMS providers - acting as a supplier and/or customer. It consists
of data such as: the protocol used, IP addresses, binds and SMS features. It can also contain data regarding VPN or IPsec tunnels, etc.
This document provides instructions for sending SMS messages using the SMSGATEWAYHUB SMS gateway via HTTP API. It details the required parameters for authentication and sending single, bulk, scheduled, and group messages. It also describes how to check delivery reports and balances. Various error codes are listed to help troubleshoot any issues.
This document proposes a presentation on using a common mediation port in TTCN-3 to execute scripts from test cases. A mediation port is defined that accepts messages containing a script name and parameters. A TRI connects this port to a mediation server hosting scripts in languages like Shell and Perl. Test cases can call scripts by sending messages to the port. This allows tasks like controlling non-SUT devices and databases through scripts without recompiling test suites. Benefits include reduced compilation times when changes are needed and the ability to develop new interfaces quickly by moving functionality to reusable scripts.
Important tips on Router and SMTP mail routingjayeshpar2006
This document provides tips on router and SMTP mail routing in Lotus Domino. It discusses 21 tips covering topics like ignoring location document email addresses, hiding SMTP details, setting message size restrictions, using authentication for SMTP relays, and setting mail routing priorities. The tips are presented by various IBM ICS support engineers and SWAT team members and include references to IBM support documents for additional details.
SMSCountry is a leading bulk SMS messaging service provider established in 2003 in India. It provides comprehensive messaging solutions through its core messaging platform, including push, pull, and two-way messaging. It has tools like an MS Excel plugin and API that allow users to send bulk SMS easily from Excel or their own applications. SMSCountry has a large client base and has received several awards and recognition for its innovative technologies and solutions.
SMSCountry is a leading bulk SMS messaging service provider established in 2003 in India. It provides comprehensive messaging solutions through its core messaging platform, including push, pull, and two-way messaging. It has tools like an MS Excel plugin and API that allow users to send bulk SMS easily from Excel or their own applications. SMSCountry has a large client base and has received several awards and recognition for its innovative technologies and solutions.
With 2 Way SMS Messaging Service by Route Mobile brands can manage inbound campaigns with auto-response, validate service messages, accelerate customer retention & loyalty.
IntelliSMS - Telco Grade, SMS Gateway and Technology Provider Peter Humphries
Intelli Messaging Services (IntelliSMS) is one of Australia's leading SMS Gateway and messaging technology providers.
IntelliSMS provides the infrastructure for Software Developers, Enterprise IT development teams to integrate SMS into their systems.
With clients in Enterprise using our notifications systems such as Powercor and Woolworths and Big Box retailers using our marketing and compliance solutions, IntelliSMS is the only one to turn to if you want to deliver the right message at the right time.
Find out more by visiting https://www.intellisms.com.au
This document provides an overview of WebSphere MQ Administration training notes. It discusses key concepts in message-oriented middleware including messaging, queuing, MQSeries, and the Message Queue Interface. It also describes common MQ objects like queue managers, queues, channels, and messages. The document outlines how applications use MQ calls to connect to queue managers and put and get messages from queues.
We wish to introduce to you our Bulk SMS portal that is like no other you have ever come across. We can boast about it because we are very sure. It can be yours for free, without a single charge. What is more, it can be customized as your own site on your domain name and you can resell to others if you wish.
Please use the following details to login to a demo account set up for you.
URL: http://sms.bytessms.net
Username: democlient19
Password: demo
SMS Gateway Center API Documentation. Learn how to send SMS in PHP and Java code using SMS Gateway Center API. Log on http://www.smsgatewaycenter.com/updates/http-sms-api-documentation/ for more info
Each MQ Connection resource has a shared connection pool that is used by multiple business and proxy services to connect to the same queue manager. The connection pool maintains unused connections and destroys them after a default interval of 1800 seconds. When throttling is enabled for a business service, it allows restricting the maximum concurrency and specifying the throttling queue size and message expiration time.
This document provides an overview of the architecture and components of the Islamic SIM Card Application Server (ISCAS). The key components include a Linux OS, PostgreSQL or MySQL database, Apache Tomcat web server, and multiple Islamic SIM Card application boxes (ISCBOX) which handle request processing. The components are modular and can be distributed across physical or virtual servers for scalability. User requests from mobile phones are processed by first passing through the SMSC to the Tomcat server and then delegated to an available ISCBOX for execution. The document discusses sample configurations, licensing, and management of the system components.
SMS is a text messaging system that allows short text messages to be sent between mobile phones. It was introduced in 1991 in Europe and supports sending text, images, sound, and animation. SMS uses a store-and-forward mechanism that allows messages to be sent to phones that are offline. It has become widely used for personal and business communication as well as applications like voting and stock quotes.
The document is a user guide for the InforUMobile platform. It provides instructions on creating an account, logging in, sending SMS texts, creating and managing landing pages, registration forms, surveys, contacts, and other features. Key sections include how to create an account, top up account credits to send SMS, compose and send SMS messages, include personalized content or links in messages, and view detailed reports on message delivery status. It also outlines how to build mobile-optimized landing pages and forms using drag-and-drop elements, customize styles and settings, and view submission reports.
This document provides a user guide for the InforUMobile platform. It includes 12 chapters that describe how to create an account, log in, top up account credits for sending SMS, send SMS texts and manage reports. It also covers how to create and manage landing pages, registration forms, surveys, contacts and comply with GDPR. Chapters also discuss the API and help/support. The guide provides step-by-step instructions on using the various features in a concise and easy to understand manner.
The document is a user guide for the InforUMobile platform. It provides instructions on creating an account, logging in, sending SMS texts, creating and managing landing pages, registration forms, surveys, and contacts. It also covers account top up, reports, GDPR, the API, and help/support. The guide contains step-by-step explanations of the platform's key features to help new users get started effectively utilizing the mobile messaging and content creation tools.
The document is a user guide for the InforUMobile platform. It provides instructions on how to create an account, log in, top up account credits to send SMS texts, and send SMS messages. It also covers how to create and manage landing pages, registration forms, surveys, contacts, and includes chapters on GDPR and the API.
The document provides a user guide for the InforUMobile platform. It includes chapters on creating an account, logging in, account top up, sending SMS texts, creating and managing landing pages, registration forms, surveys, managing contacts, GDPR, API, and help/support. The guide provides step-by-step instructions on how to use the various features of the platform.
The document is a user guide for the InforUMobile SMS marketing platform. It provides instructions on creating an account, logging in, purchasing SMS credits, and sending SMS texts. It also covers creating and managing landing pages, registration forms, surveys, contacts, and account settings.
This document provides a user guide for the InforUMobile platform. It covers how to create an account, log in, top up account credits to send SMS texts, send SMS messages, and create and manage landing pages, registration forms, surveys, contacts, and account settings. Key features covered include composing SMS texts, selecting recipients, scheduling delivery times, including personalized content and links, and viewing detailed reports on message delivery and engagement. The guide also reviews how to build mobile-optimized landing pages using drag-and-drop elements, templates, and separate settings for mobile and desktop versions.
This document is a user guide for InforUMobile's SMS marketing platform. It covers topics such as creating an account, logging in, purchasing SMS credits, sending SMS texts, creating and managing landing pages, registration forms, surveys, contacts, and more. The guide provides step-by-step instructions on how to use the various features in 3 chapters or less per section. It also includes contact information for customer support.
The document is a user guide for the InforUMobile platform. It provides instructions on how to create an account, log in, top up account credits to send SMS texts, and send SMS messages. It also covers how to create and manage landing pages, registration forms, surveys, contacts, and account settings.
The document is a user guide for the InforUMobile SMS marketing platform. It provides instructions on how to create an account, log in, top up account credits to send SMS messages, and send SMS texts. It also covers how to create and manage landing pages, registration forms, surveys, contacts, and account settings.
The document provides a user guide for the InforUMobile platform. It includes chapters on creating an account, logging in, account top up, sending SMS texts, creating and managing landing pages, registration forms, surveys, managing contacts, GDPR, API, and help/support. The guide describes how to perform tasks in the platform such as creating an account, logging in, purchasing SMS credits, composing and sending SMS messages, creating forms and surveys, and managing contacts and account settings.
This document provides a user guide for the InforUMobile platform. It includes chapters on creating an account, logging in, account top up, sending SMS texts, creating and managing landing pages, registration forms, surveys, contacts, GDPR, API, and help/support. The guide explains how to perform essential tasks within the platform such as creating an account, purchasing SMS credits, sending SMS messages to contacts, and creating/managing forms, surveys and landing pages.
The document is a user guide for the InforUMobile SMS marketing platform. It provides instructions on how to create an account, log in, top up account credits to send SMS messages, and send SMS texts. It also covers how to create and manage landing pages, registration forms, surveys, contacts, and account settings.
This document provides a user guide for InforUMobile's mobile marketing platform. It includes 9 chapters that describe how to use the platform's key features:
1. Creating an account and logging in
2. Topping up SMS credits
3. Sending SMS texts and viewing reports
4. Creating and managing landing pages, registration forms, and surveys
5. Importing and managing contacts
6. Getting help and support
Each chapter provides step-by-step instructions on how to perform tasks in a clear and organized manner. Screenshots are included to illustrate the user interfaces. The guide aims to educate users on all aspects of the platform so they can fully utilize its mobile marketing capabilities.
This document provides a user guide for the InforUMobile platform. It outlines how to create an account, log in, top up account credits to send SMS texts, and send SMS texts. It also covers how to create and manage landing pages, registration forms, surveys, contacts, and get help/support. Each chapter provides step-by-step instructions and screenshots to explain the features and functionality of the mobile messaging platform.
Prediction of Electrical Energy Efficiency Using Information on Consumer's Ac...PriyankaKilaniya
Energy efficiency has been important since the latter part of the last century. The main object of this survey is to determine the energy efficiency knowledge among consumers. Two separate districts in Bangladesh are selected to conduct the survey on households and showrooms about the energy and seller also. The survey uses the data to find some regression equations from which it is easy to predict energy efficiency knowledge. The data is analyzed and calculated based on five important criteria. The initial target was to find some factors that help predict a person's energy efficiency knowledge. From the survey, it is found that the energy efficiency awareness among the people of our country is very low. Relationships between household energy use behaviors are estimated using a unique dataset of about 40 households and 20 showrooms in Bangladesh's Chapainawabganj and Bagerhat districts. Knowledge of energy consumption and energy efficiency technology options is found to be associated with household use of energy conservation practices. Household characteristics also influence household energy use behavior. Younger household cohorts are more likely to adopt energy-efficient technologies and energy conservation practices and place primary importance on energy saving for environmental reasons. Education also influences attitudes toward energy conservation in Bangladesh. Low-education households indicate they primarily save electricity for the environment while high-education households indicate they are motivated by environmental concerns.
Height and depth gauge linear metrology.pdfq30122000
Height gauges may also be used to measure the height of an object by using the underside of the scriber as the datum. The datum may be permanently fixed or the height gauge may have provision to adjust the scale, this is done by sliding the scale vertically along the body of the height gauge by turning a fine feed screw at the top of the gauge; then with the scriber set to the same level as the base, the scale can be matched to it. This adjustment allows different scribers or probes to be used, as well as adjusting for any errors in a damaged or resharpened probe.
Home security is of paramount importance in today's world, where we rely more on technology, home
security is crucial. Using technology to make homes safer and easier to control from anywhere is
important. Home security is important for the occupant’s safety. In this paper, we came up with a low cost,
AI based model home security system. The system has a user-friendly interface, allowing users to start
model training and face detection with simple keyboard commands. Our goal is to introduce an innovative
home security system using facial recognition technology. Unlike traditional systems, this system trains
and saves images of friends and family members. The system scans this folder to recognize familiar faces
and provides real-time monitoring. If an unfamiliar face is detected, it promptly sends an email alert,
ensuring a proactive response to potential security threats.
Blood finder application project report (1).pdfKamal Acharya
Blood Finder is an emergency time app where a user can search for the blood banks as
well as the registered blood donors around Mumbai. This application also provide an
opportunity for the user of this application to become a registered donor for this user have
to enroll for the donor request from the application itself. If the admin wish to make user
a registered donor, with some of the formalities with the organization it can be done.
Specialization of this application is that the user will not have to register on sign-in for
searching the blood banks and blood donors it can be just done by installing the
application to the mobile.
The purpose of making this application is to save the user’s time for searching blood of
needed blood group during the time of the emergency.
This is an android application developed in Java and XML with the connectivity of
SQLite database. This application will provide most of basic functionality required for an
emergency time application. All the details of Blood banks and Blood donors are stored
in the database i.e. SQLite.
This application allowed the user to get all the information regarding blood banks and
blood donors such as Name, Number, Address, Blood Group, rather than searching it on
the different websites and wasting the precious time. This application is effective and
user friendly.
Discover the latest insights on Data Driven Maintenance with our comprehensive webinar presentation. Learn about traditional maintenance challenges, the right approach to utilizing data, and the benefits of adopting a Data Driven Maintenance strategy. Explore real-world examples, industry best practices, and innovative solutions like FMECA and the D3M model. This presentation, led by expert Jules Oudmans, is essential for asset owners looking to optimize their maintenance processes and leverage digital technologies for improved efficiency and performance. Download now to stay ahead in the evolving maintenance landscape.
Tools & Techniques for Commissioning and Maintaining PV Systems W-Animations ...Transcat
Join us for this solutions-based webinar on the tools and techniques for commissioning and maintaining PV Systems. In this session, we'll review the process of building and maintaining a solar array, starting with installation and commissioning, then reviewing operations and maintenance of the system. This course will review insulation resistance testing, I-V curve testing, earth-bond continuity, ground resistance testing, performance tests, visual inspections, ground and arc fault testing procedures, and power quality analysis.
Fluke Solar Application Specialist Will White is presenting on this engaging topic:
Will has worked in the renewable energy industry since 2005, first as an installer for a small east coast solar integrator before adding sales, design, and project management to his skillset. In 2022, Will joined Fluke as a solar application specialist, where he supports their renewable energy testing equipment like IV-curve tracers, electrical meters, and thermal imaging cameras. Experienced in wind power, solar thermal, energy storage, and all scales of PV, Will has primarily focused on residential and small commercial systems. He is passionate about implementing high-quality, code-compliant installation techniques.
Software Engineering and Project Management - Software Testing + Agile Method...Prakhyath Rai
Software Testing: A Strategic Approach to Software Testing, Strategic Issues, Test Strategies for Conventional Software, Test Strategies for Object -Oriented Software, Validation Testing, System Testing, The Art of Debugging.
Agile Methodology: Before Agile – Waterfall, Agile Development.
Accident detection system project report.pdfKamal Acharya
The Rapid growth of technology and infrastructure has made our lives easier. The
advent of technology has also increased the traffic hazards and the road accidents take place
frequently which causes huge loss of life and property because of the poor emergency facilities.
Many lives could have been saved if emergency service could get accident information and
reach in time. Our project will provide an optimum solution to this draw back. A piezo electric
sensor can be used as a crash or rollover detector of the vehicle during and after a crash. With
signals from a piezo electric sensor, a severe accident can be recognized. According to this
project when a vehicle meets with an accident immediately piezo electric sensor will detect the
signal or if a car rolls over. Then with the help of GSM module and GPS module, the location
will be sent to the emergency contact. Then after conforming the location necessary action will
be taken. If the person meets with a small accident or if there is no serious threat to anyone’s
life, then the alert message can be terminated by the driver by a switch provided in order to
avoid wasting the valuable time of the medical rescue team.
Use PyCharm for remote debugging of WSL on a Windo cf5c162d672e4e58b4dde5d797...shadow0702a
This document serves as a comprehensive step-by-step guide on how to effectively use PyCharm for remote debugging of the Windows Subsystem for Linux (WSL) on a local Windows machine. It meticulously outlines several critical steps in the process, starting with the crucial task of enabling permissions, followed by the installation and configuration of WSL.
The guide then proceeds to explain how to set up the SSH service within the WSL environment, an integral part of the process. Alongside this, it also provides detailed instructions on how to modify the inbound rules of the Windows firewall to facilitate the process, ensuring that there are no connectivity issues that could potentially hinder the debugging process.
The document further emphasizes on the importance of checking the connection between the Windows and WSL environments, providing instructions on how to ensure that the connection is optimal and ready for remote debugging.
It also offers an in-depth guide on how to configure the WSL interpreter and files within the PyCharm environment. This is essential for ensuring that the debugging process is set up correctly and that the program can be run effectively within the WSL terminal.
Additionally, the document provides guidance on how to set up breakpoints for debugging, a fundamental aspect of the debugging process which allows the developer to stop the execution of their code at certain points and inspect their program at those stages.
Finally, the document concludes by providing a link to a reference blog. This blog offers additional information and guidance on configuring the remote Python interpreter in PyCharm, providing the reader with a well-rounded understanding of the process.
Supermarket Management System Project Report.pdfKamal Acharya
Supermarket management is a stand-alone J2EE using Eclipse Juno program.
This project contains all the necessary required information about maintaining
the supermarket billing system.
The core idea of this project to minimize the paper work and centralize the
data. Here all the communication is taken in secure manner. That is, in this
application the information will be stored in client itself. For further security the
data base is stored in the back-end oracle and so no intruders can access it.
1. Version 4.9
בע"מ ומפעלים מערכות שמיר
.ת.ד2097ציונה נס74120.טל9415550-03פקס9514736-03www.inforu.co.il
SMS Gateway Interface
SMS Interface.......................................................................................................................................1
Send SMS using http post Interface .....................................................................................................1
Simple XML example ......................................................................................................................1
Advanced XML Example.................................................................................................................2
Send Multiple Requests....................................................................................................................3
Response XML.................................................................................................................................4
HTTP Post code sample ...................................................................................................................5
C# example...................................................................................................................................5
PHP example................................................................................................................................7
VB Example.................................................................................................................................8
Send SMS Using Web Service Interface............................................................................................10
C# example.................................................................................................................................11
Send SMS Using Parameters..............................................................................................................12
Example for a UTF8 request:.........................................................................................................12
Message character length ...................................................................................................................13
Delivery Notification..........................................................................................................................13
Option 1(PUSH).............................................................................................................................13
Option 2 (PULL) ............................................................................................................................14
Receiving SMS (optional)..................................................................................................................16
Option 1(PUSH).............................................................................................................................16
Option 2 (PULL) ............................................................................................................................17
SMS Tools..........................................................................................................................................19
Delete Future Messages .................................................................................................................19
Remaining SMS Quota...................................................................................................................20
Phone Number block check............................................................................................................21
Blocking Phone Numbers...............................................................................................................22
Contacts & Groups Management .......................................................................................................23
Create or Update contact................................................................................................................23
Example simple..........................................................................................................................23
Response.....................................................................................................................................23
Example Advanced ....................................................................................................................24
Check Status Token........................................................................................................................26
Response.....................................................................................................................................26
2. Version 4.9
בע"מ ומפעלים מערכות שמיר
.ת.ד2097ציונה נס74120.טל9415550-03פקס9514736-03www.inforu.co.il
-1-
SMS Interface
Send SMS using http post Interface
Client should perform Http Post request to this URL.
The encoding should be UTF-8.
http://uapi.inforu.co.il/SendMessageXml.ashx?InforuXML={xml}
Secure interface
For a secure interface use:
https://uapi.inforu.co.il/SendMessageXml.ashx?InforuXML={xml}
Simple XML example
<Inforu>
<User>
<Username>MyUsername</Username>
<Password>MyPassword</Password>
</User>
<Content Type="sms">
<Message>This is a test SMS Message</Message>
</Content>
<Recipients>
<PhoneNumber>0501111111;0502222222</PhoneNumber>
</Recipients>
<Settings>
<Sender>0501111111</Sender>
</Settings>
</Inforu>
Explanation of XML structure:
UserName – Username of the account that was supplied by InforUMobile
Password – Password of the account
Message – SMS message that needs to be sent
PhoneNumber – The recipients' phone list. Can be multiple recipients separated by a
semicolon ";"
Sender – The ID that will be displayed in the recipient's phone as the sender.
3. Version 4.9
בע"מ ומפעלים מערכות שמיר
.ת.ד2097ציונה נס74120.טל9415550-03פקס9514736-03www.inforu.co.il
-2-
Advanced XML Example
<Inforu>
<User>
<Username>MyUserName</Username>
<Password>MyPassword</Password>
</User>
<Content Type="sms">
<Message>This is a test SMS Message</Message>
</Content>
<Recipients>
<PhoneNumber>0501111111;0502222222</PhoneNumber>
<GroupNumber>5</GroupNumber>
</Recipients>
<Settings>
<Sender>MyCompany</Sender>
<CustomerMessageID>112233</CustomerMessageID>
<CustomerParameter>AffId4</CustomerParameter>
<MessageInterval>0</MessageInterval>
<TimeToSend>12/05/2013 12:23</TimeToSend>
<DelayInSeconds>60</DelayInSeconds>
<DeliveryNotificationUrl>http://mysite.co.il/Notif.aspx</DeliveryNotificationUrl>
<MaxSegments>0</MaxSegments>
<Priority>0</Priority>
</Settings>
</Inforu>
Explanation of XML structure (All the following parameters are optional):
Sender – The "Sender" field is restricted to a maximum of 11 Latin characters (Consecutive
characters, no spaces) or 14 digits (no characters). You can also write an asterisk (*) at the beginning
of the identifier.
GroupNumber – Use this parameter in order to send messages to a group according to
the group number defined in the web site. To send a message to multiple groups please use a
semicolon ";".
CustomerMessageID – Message ID on the client application. When confirmation on delivery is sent
back to the client, the message ID is also sent for synchronization.
CustomerParameter – Parameter set by the client that can be seen in the reports, later.
Can be used to mark each message by activity segmentation, for example.
Priority – In order to prioritize your messages, you can use the priority tag, when 0 means normal
priority, -1 high priority (used only for a single message), and then 1,2 and so on. The higher the value,
the lower the priority.
MessageInterval - Sending messages with number of seconds interval between them.
The value 0 means non-interval.
DeliveryNotificationUrl – Needed in order to send a confirmation on delivery to the client.
The system will perform HTTP post to this URL with notification information.
MaxSegments – When sending long messages, this parameter allows the client to set the
maximum number of segments per message. Value 0 means unlimited segments.
TimeToSend – Date and time on which the messages will be sent.
Please use the following format: dd/mm/yyyy hh:mm. If left blank, the message will be sent
immediately.
DelayInSeconds – Number of seconds of delay from receiving the request in the system and up to
sending the message (use this parameter as long as the TimeToSend parameter is not in use).
4. Version 4.9
בע"מ ומפעלים מערכות שמיר
.ת.ד2097ציונה נס74120.טל9415550-03פקס9514736-03www.inforu.co.il
-3-
Send Multiple Requests
In order to send requests using different wordings, use InforuRoot – It is recommended to send up to 100
packages per request.
<InforuRoot>
<Inforu>
<User>
<Username>MyUsername</Username>
<Password>MyPassword</Password>
</User>
<Content Type="sms">
<Message>This is the first SMS message</Message>
</Content>
<Recipients>
<PhoneNumber>0501111111;0502222222</PhoneNumber>
</Recipients>
<Settings>
<Sender>0501111111</Sender>
</Settings>
</Inforu>
<Inforu>
<User>
<Username>MyUsername</Username>
<Password>MyPassword</Password>
</User>
<Content Type="sms">
<Message>This is the second SMS message</Message>
</Content>
<Recipients>
<PhoneNumber>054-6669999</PhoneNumber>
</Recipients>
<Settings>
<Sender>Company</Sender>
</Settings>
</Inforu>
</InforuRoot>
5. Version 4.9
בע"מ ומפעלים מערכות שמיר
.ת.ד2097ציונה נס74120.טל9415550-03פקס9514736-03www.inforu.co.il
-4-
Response XML
Explanation of Response, XML structure:
<Result>
<Status>1</Status >
<Description>Message accepted successfully</ Description>
<NumberOfRecipients>1</ NumberOfRecipients>
</Result>
(In case of using Inforuroot, the above response will repeat itself as many times as there are requests
which you have inputted into the InforuRoot(
1. Status:
1 = OK
-1 = Failed
-2 = Bad user name or password
-6 = RecipientsDataNotExists
-9 = MessageTextNotExists
-11 = IllegalXML
-13 = UserQuotaExceeded
-14 = ProjectQuotaExceeded
-15 = CustomerQuotaExceeded
-16 = WrongDateTime
-17 = WrongNumberParameter
-18 = No valid recipients
-20 = InvalidSenderNumber
-21 = InvalidSenderName,
-22 = UserBlocked
-26 = UserAuthenticationError
-28 = NetworkTypeNotSupported
-29 = NotAllNetworkTypesSupported
-90 = InvalidSenderIdentification
2. Description – Status interpretation.
3. NumberOfRecipients - Phone numbers that the message has been sent to.
6. Version 4.9
בע"מ ומפעלים מערכות שמיר
.ת.ד2097ציונה נס74120.טל9415550-03פקס9514736-03www.inforu.co.il
-5-
HTTP Post code sample
C# example
//set password, user name, message text, semder name and number
string userName = "UserName";
string password = "UserPassword";
string messageText = System.Security.SecurityElement.Escape("Message text");
string sender = "MySender";
//set phone numbers
string phonesList = "0503333333;0503333334;0503333335;0503333336;0503333337";
//set additional parameters
string timeToSend = "21/12/2017 15:30";
// create XML
StringBuilder sbXml = new StringBuilder();
sbXml.Append("<Inforu>");
sbXml.Append("<User>");
sbXml.Append("<Username>" + userName + "</Username>");
sbXml.Append("<Password>" + password + "</Password>");
sbXml.Append("</User>");
sbXml.Append("<Content Type="sms">");
sbXml.Append("<Message>" + messageText + "</Message>");
sbXml.Append("</Content>");
sbXml.Append("<Recipients>");
sbXml.Append("<PhoneNumber>" + phonesList + "</PhoneNumber>");
sbXml.Append("</Recipients>");
sbXml.Append("<Settings>");
sbXml.Append("<Sender>" + sender+ "</Sender>");
sbXml.Append("<MessageInterval>" + messageInterval + "</MessageInterval>");
sbXml.Append("<TimeToSend>" + timeToSend + "</TimeToSend>");
sbXml.Append("</Settings>");
sbXml.Append("</Inforu >");
string strXML = HttpUtility.UrlEncode(sbXml.ToString(), System.Text.Encoding.UTF8);
string result = PostDataToURL("http://uapi.inforu.co.il/SendMessageXml.ashx", "InforuXML=" + strXML);
static string PostDataToURL(string szUrl, string szData)
{
//Setup the web request
string szResult = string.Empty;
WebRequest Request = WebRequest.Create(szUrl);
Request.Timeout = 30000;
Request.Method = "POST";
Request.ContentType = "application/x-www-form-urlencoded";
//Set the POST data in a buffer
byte[] PostBuffer;
try
7. Version 4.9
בע"מ ומפעלים מערכות שמיר
.ת.ד2097ציונה נס74120.טל9415550-03פקס9514736-03www.inforu.co.il
-6-
{
// replacing " " with "+" according to Http post RPC
szData = szData.Replace(" ", "+");
//Specify the length of the buffer
PostBuffer = Encoding.UTF8.GetBytes(szData);
Request.ContentLength = PostBuffer.Length;
//Open up a request stream
Stream RequestStream = Request.GetRequestStream();
//Write the POST data
RequestStream.Write(PostBuffer, 0, PostBuffer.Length);
//Close the stream
RequestStream.Close();
//Create the Response object
WebResponse Response;
Response = Request.GetResponse();
//Create the reader for the response
StreamReader sr = new StreamReader(Response.GetResponseStream(), Encoding.UTF8);
//Read the response
szResult = sr.ReadToEnd();
//Close the reader, and response
sr.Close();
Response.Close();
return szResult;
}
catch (Exception e)
{
return szResult;
}
}
Using Dot Net Programming:
Message text must be escaped with System.Security.SecurityElement.Escape.
XML must be encoded by HttpUtility.UrlEncode(xml, .Text.Encoding.UTF8)
9. Version 4.9
בע"מ ומפעלים מערכות שמיר
.ת.ד2097ציונה נס74120.טל9415550-03פקס9514736-03www.inforu.co.il
-8-
VB Example
//Important: need to add reference to System.Web.dll
'set password, user name, message text, semder name and number
Dim userName As String = "UserName"
Dim password As String = "UserPassword"
Dim messageText As String = System.Security.SecurityElement.Escape("Message text")
Dim sender As String = "MySender"
Dim messageInterval As Integer = 0
'set phone numbers
Dim phonesList As String = "0503333333;0503333334;0503333335;0503333336;0503333337"
'set additional parameters
Dim timeToSend As String = "21/12/2017 15:30"
' create XML
Dim sbXml As New Text.StringBuilder()
sbXml.Append("<Inforu>")
sbXml.Append("<User>")
sbXml.Append("<Username>" & userName & "</Username>")
sbXml.Append("<Password>" & password & "</Password>")
sbXml.Append("</User>")
sbXml.Append("<Content Type=""sms"">")
sbXml.Append("<Message>" & messageText & "</Message>")
sbXml.Append("</Content>")
sbXml.Append("<Recipients>")
sbXml.Append("<PhoneNumber>" & phonesList & "</PhoneNumber>")
sbXml.Append("</Recipients>")
sbXml.Append("<Settings>")
sbXml.Append("<Sender>" & sender & "</Sender>")
sbXml.Append("<MessageInterval>" & messageInterval & "</MessageInterval>")
sbXml.Append("<TimeToSend>" & timeToSend & "</TimeToSend>")
sbXml.Append("</Settings>")
sbXml.Append("</Inforu >")
Dim strXML As String = System.Web.HttpUtility.UrlEncode(sbXml.ToString(),
System.Text.Encoding.UTF8)
Dim result As String = PostDataToURL("http://uapi.inforu.co.il/SendMessageXml.ashx", "InforuXML=" &
strXML)
Private Function PostDataToURL(ByVal szUrl As String, ByVal szData As String) As String
'Setup the web request
Dim szResult As String = String.Empty
Dim Request As Net.HttpWebRequest
Request = CType(System.Net.WebRequest.Create(szUrl), System.Net.HttpWebRequest)
Request.Timeout = 30000
Request.Method = "POST"
Request.ContentType = "application/x-www-form-urlencoded"
'Set the POST data in a buffer
Dim PostBuffer As Byte()
10. Version 4.9
בע"מ ומפעלים מערכות שמיר
.ת.ד2097ציונה נס74120.טל9415550-03פקס9514736-03www.inforu.co.il
-9-
Try
' replacing " " with "+" according to Http post RPC
szData = szData.Replace(" ", "+")
'Specify the length of the buffer
PostBuffer = System.Text.Encoding.UTF8.GetBytes(szData)
Request.ContentLength = PostBuffer.Length
'Open up a request stream
Dim RequestStream As IO.Stream = Request.GetRequestStream()
'Write the POST data
RequestStream.Write(PostBuffer, 0, PostBuffer.Length)
'Close the stream
RequestStream.Close()
'Create the Response object
Dim Response As Net.HttpWebResponse
Response = CType(Request.GetResponse(), System.Net.HttpWebResponse)
'Create the reader for the response
Dim sr As New IO.StreamReader(Response.GetResponseStream(),
System.Text.Encoding.UTF8)
'Read the response
szResult = sr.ReadToEnd()
'Close the reader, and response
sr.Close()
Response.Close()
Return (szResult)
Catch e As Exception
Return (szResult)
End Try
End Function
11. Version 4.9
בע"מ ומפעלים מערכות שמיר
.ת.ד2097ציונה נס74120.טל9415550-03פקס9514736-03www.inforu.co.il
-10-
Send SMS Using Web Service Interface
Description
Web service interface is mainly used for .Net applications although Java developers can use it too.
Microsoft .Net framework has a built-in support for calling web services, so for anyone who uses .Net it
is highly recommended to use this interface. This interface allows the user to control and customize
every aspect of the InforuMobile SMS engine.
Format
Microsoft .Net users should add a reference to this URL:
http://uapi.inforu.co.il/SendMessage.asmx
Java / Delphi / Magic users should use this URL:
http://uapi.inforu.co.il/SendMessage.asmx?wsdl
The web interface implements 2 functions:
SendSms – Sending SMS with minimum parameters
SendSmsDetailed – Sending SMS with additional parameters
Function Parameters Explanation
There are 2 functions for sending SMS messages.
Here is an explanation of the parameters from the function SendSmsDetailed:
UserName - Username of the account that was supplied by InforUMobile
Password - Password of the account.
Message – SMS message that needs to be sent.
MessagePelephone – Not in use (Use double quotation marks).
MessageCellcom – Not in use (Use double quotation marks).
MessageOrange – Not in use (Use double quotation marks).
MessageMirs - Not in use (Use double quotation marks).
Recipients – The recipients' phone list. Can be multiple recipients separated by a ";"
CustomerParameter - Parameter set by the client that can be seen in the reports, later.
Can be used to mark each message by activity segmentation, for example.
CustomerMessageID - Message ID on the client application. When confirmation on delivery is
sent back to the client, the message ID is also sent for synchronization.
MessageInterval - Sending messages with number of seconds interval between them.
The value 0 means non-interval.
TimeToSend – Date and time on which the messages will be sent. Please use the following
format: dd/mm/yyyy hh:mm. If left blank, the message will be sent immediately.
SenderName – The name that will be displayed on the recipient's device, is restricted to a
maximum of 11 Latin characters (Consecutive characters without spaces).
SenderNumber – Not in use. (Use 0000)
MaxSegments – When sending long messages, this parameter allows the client to set the
maximum number of segments per message. Value 0 means unlimited segments.
12. Version 4.9
בע"מ ומפעלים מערכות שמיר
.ת.ד2097ציונה נס74120.טל9415550-03פקס9514736-03www.inforu.co.il
-11-
C# example
static void Main(string[] args)
{
WS_SendSMS.SendMessageSoapClient SendSMS = new WS_SendSMS.SendMessageSoapClient();
String Result = SendSMS.SendSmsDetailed("MyUserName","MyPassword","Test using
WS","","", "","","0529999999","","",0,new
DateTime(1900,01,01,00,00,00),"MyCompany","0000", 0);
Console.WriteLine(Result);
Console.ReadLine();
}
Successful response example
<Result>
<Status>1</Status>
<Description>Message accepted successfully</Description>
<NumberOfRecipients>1</NumberOfRecipients>
</Result>
Unsuccessful response example
<Result>
<Status>-2</Status>
<Description>Error: Bad user name or password</Description>
<NumberOfRecipients>0</NumberOfRecipients>
</Result>
Response status explanations
1. Status:
1 = OK
-1 = Failed
-2 = Bad user name or password
-6 = RecipientsDataNotExists
-9 = MessageTextNotExists
-11 = IllegalXML
-13 = UserQuotaExceeded
-14 = ProjectQuotaExceeded
-15 = CustomerQuotaExceeded
-16 = WrongDateTime
-17 = WrongNumberParameter
-18 = No valid recipients
-20 = InvalidSenderNumber
-21 = InvalidSenderName,
-22 = UserBlocked
-26 = UserAuthenticationError
-28 = NetworkTypeNotSupported
-90 = InvalidSenderIdentification
2. Description – Status interpretation.
3. NumberOfRecipients - Phone numbers that the message has been sent to.
13. Version 4.9
בע"מ ומפעלים מערכות שמיר
.ת.ד2097ציונה נס74120.טל9415550-03פקס9514736-03www.inforu.co.il
-12-
Send SMS Using Parameters
Description
In order to send messages through the use of chaining parameters, this is a brief explanation of
implementing the code properly.
Format
For UTF8 encoding, use the following URL:
http://uapi.inforu.co.il/inforufrontend/WebInterface/SendMessageByNumber.aspx
For WIN1255 encoding, use the following URL:
http://uapi.inforu.co.il/InforuFrontEnd/EngineInterface/SendMessageByNumber.aspx
Parameters required for the reference:
UserName
Password
SenderCellNumber
CellNumber
MessageString
Example for a UTF8 request:
http://uapi.inforu.co.il/inforufrontend/WebInterface/SendMessageByNumber.aspx?UserName=myusern
ame&Password=100301&SenderCellNumber=Mysender&CellNumber=052000000;0542152743&Mess
ageString=Hello
Parameters: Explanation of Functions
UserName - Username of the account that was supplied by InforUMobile
Password - Password of the account
SenderCellNumber – The "SenderCellNumber" field is restricted to a maximum of 11 Latin
characters (Consecutive characters with no spaces) or up to 14 digits (and no characters).
You can also write an asterisk (*) at the beginning of the identifier.
CellNumber – Recipient's phone list. Multiple recipients may be added when separated by a
semicolon ";"
MessageString – SMS message that needs to be sent.
Response
The response of your requests be a number
1 = OK
Other statuses, see page 4.
14. Version 4.9
בע"מ ומפעלים מערכות שמיר
.ת.ד2097ציונה נס74120.טל9415550-03פקס9514736-03www.inforu.co.il
-13-
Message character length
hereated information can be founddUp
Delivery Notification
There are two options for Notifications:
1. Push - We appeal to your URL real time.
2. Pull - You turn to us for pulling your notifications
Option 1(PUSH)
The client can receive confirmation on delivery on each message sent. When sending the message the
client should use the CustomerMessageID and the DeliveryNotificationUrl parameters. The system
performs an HTTP Post request to this URL regarding any message.
The parameters for the request are:
PhoneNumber – The number of the recipient.
Network – The network of the recipient.
Status – The status of the message.
(2) – Delivered.
(-2) – Not delivered.
(-4) – Blocked by InforuMobile.
StatusDescription – If not delivered, contains the reason.
ProjectId – The project ID Below describes the user who sent the message.
CustomerMessageId – The client message ID.
CustomerParam – The client parameter.
SenderNumber – The ID of the sender who sent the message.
SegmentsNumber – The amount of segments in the message (See "Message character length").
OriginalMessage – The content of the sent message.
NotificationDate – Time of receiving the notification from the cellular operator.
Delivery Notification Example
URL: http://www.clientURL.co.il/demo.aspx
With parameters:
PhoneNumber=0527777888&Network=052&Status=2&StatusDescription=Delivered&ProjectId=10838&
CustomerMessageId=652&CustomerParam=&id=&SenderNumber=4234324&BillingCodeId=1&Price=0
.00&SegmentsNumber=2&ActionType=Content&OriginalMessage=test 1&NotificationDate=08/01/2017
10:12:07&RetriesNumber=0
15. Version 4.9
בע"מ ומפעלים מערכות שמיר
.ת.ד2097ציונה נס74120.טל9415550-03פקס9514736-03www.inforu.co.il
-14-
Option 2 (PULL)
In order to pull notifications you need to enter the following address under the DeliveryNotificationUrl
tag. http://uapi.inforu.co.il/InsertNotificationsToPullQueue.ashx
NOTE: Once pulled, the notification entries are removed from our system queue.
Web Service Address:
http://uapi.inforu.co.il/ClientServices.asmx
Function name: PullClientDLR
Parameters: Explanation of Functions
UserName – Username of the account that was supplied by InforUMobile
Password – Password of the account
batchSize – The amount of notifications you wish to pull
Response XML
After you issue the request, an answer is returned in XML format:
<ClientNotification>
<Status>OK</Status>
<BatchSize>2</BatchSize>
<Messages>
<Message>
<Type>Notification </Type>
<PhoneNumber>0529999999</PhoneNumber>
<Network>052</Network>
<Status>2</Status>
<StatusDescription>Delivered</StatusDescription>
<CustomerMessageId>1234</CustomerMessageId>
<CustomerParam>A60</CustomerParam>
<SenderNumber>1315</SenderNumber>
<SegmentsNumber>1</SegmentsNumber>
<NotificationDate>29/11/2016 14:16:25</NotificationDate>
<SentMessage>test</SentMessage>
</Message>
<Message>
<Type>Notification </Type>
<PhoneNumber>0546668887</PhoneNumber>
<Network>054</Network>
<Status>-2</Status>
<StatusDescription>Expired</StatusDescription>
<CustomerMessageId>1238</CustomerMessageId>
<CustomerParam>F321</CustomerParam>
<SenderNumber>1315</SenderNumber>
<SegmentsNumber>1</SegmentsNumber>
<NotificationDate>29/11/2016 14:16:25</NotificationDate>
<SentMessage>test</SentMessage>
</Message>
</Messages>
</ClientNotification>
16. Version 4.9
בע"מ ומפעלים מערכות שמיר
.ת.ד2097ציונה נס74120.טל9415550-03פקס9514736-03www.inforu.co.il
-15-
If the system queue is empty, the response will look like so:
<ClientNotification>
<Status>OK</Status>
<BatchSize>0</BatchSize>
</ClientNotification>
An explanation of the return parameters:
Status (of the request) – Describes whether the request succeeded or not. The list of possible statuses
can be found below.
BatchSize – The number of notifications transferred.
Type – Will always contain the word 'Notification'.
PhoneNumber – The phone number for which the notification was received.
Network – The destination network
Status (of the message) – Possible values: 2 (received), -2 (not received), -4 (blocked).
StatusDescription – Given reason in case of message not received.
CustomerMessageID – Message identity parameter which is transferred during the time the message
is sent. This is helpful when matching notifications received with messages sent.
CustomerParam – An additional, optional parameter for message identity.
SenderNumber – Phone number of the sender defined in the sent message.
SegmentsNumber – The number of segments sent.
NotificationDate – Time of receiving the notification from the cellular operator.
SentMessage - The content of the sent message.
List of Possible Statuses
OK
Failed
BadUserNameOrPassword
17. Version 4.9
בע"מ ומפעלים מערכות שמיר
.ת.ד2097ציונה נס74120.טל9415550-03פקס9514736-03www.inforu.co.il
-16-
Receiving SMS (optional)
Option 1(PUSH)
When a user sends an SMS from his cell phone, the system will perform an HTTP Post Request to the
client's predefined URL (via customer support). The client receives the XML in the “IncomingXML”
parameter, encoded in UTF-8.
Receiving SMS Example
http://ClientWebApp.co.il/GetSMS.aspx?IncomingXML=
<IncomingData>
<PhoneNumber>0509999111</PhoneNumber>
<Keyword>Yes</Keyword>
<Message> Yes I am interested </Message>
<Network>054</Network>
<ShortCode>039444666</ShortCode>
<CustomerID>17</CustomerID>
<ProjectID>456</ProjectID>
<ApplicationID>33321</ApplicationID>
</IncomingData>
Your site needs to answer:
<Inforu>OK</Inforu>
An explanation of the return parameters:
PhoneNumber – The phone number of the message.
Keyword – First word in the message.
Message – The message incoming message.
Network – The source network.
ShortCode – Phone number to which the incoming message was sent.
CustomerID – Customer ID in our system.
ProjectID – Project ID in our system.
ApplicationID – Application ID in our system.
18. Version 4.9
בע"מ ומפעלים מערכות שמיר
.ת.ד2097ציונה נס74120.טל9415550-03פקס9514736-03www.inforu.co.il
-17-
Option 2 (PULL)
Purpose of the service: Pulling incoming messages which were received from the operators are
waiting in the DB under PULL instead of PUSH. In order to activate this option, refer to the support
department which will enable it for you.
NOTE: Once pulled, the MO entries are removed from our system queue.
Format
Microsoft .Net users should add reference to this URL:
http://uapi.inforu.co.il/ClientServices.asmx
Java / Delphi / Magic users should use this URL:
http://uapi.inforu.co.il/ClientServices.asmx?wsdl
The function name is PullClientMO.
Parameters: Explanation of Functions
UserName – Username of the account that was supplied by InforUMobile
Password – Password of the account
batchSize – The amount of MO you wish to pull
Response:
After you issue the request, an answer is returned in XML format:
<ClientNotification>
<Status>OK</Status>
<BatchSize>2</BatchSize>
<Messages>
<Message>
<Type>MoMessage</Type>
<PhoneNumber>0521111111</PhoneNumber>
<Network>052</Network>
<Status></Status>
<StatusDescription></StatusDescription>
<CustomerMessageId></CustomerMessageId>
<CustomerParam></CustomerParam>
<SenderNumber>1315</SenderNumber>
<SegmentsNumber></SegmentsNumber>
<NotificationDate>29/12/2017 13:10:25</NotificationDate>
<SentMessage>test</SentMessage>
</Message>
<Message>
<Type>MoMessage</Type>
<PhoneNumber>0548889999</PhoneNumber>
<Network>054</Network>
<Status></Status>
<StatusDescription></StatusDescription>
<CustomerMessageId></CustomerMessageId>
<CustomerParam></CustomerParam>
19. Version 4.9
בע"מ ומפעלים מערכות שמיר
.ת.ד2097ציונה נס74120.טל9415550-03פקס9514736-03www.inforu.co.il
-18-
<SenderNumber>0000</SenderNumber>
<SegmentsNumber></SegmentsNumber>
<NotificationDate>29/12/2017 14:16:26</NotificationDate>
<SentMessage>test 222</SentMessage>
</Message>
</Messages>
</ClientNotification>
If the system queue is empty, the response will look like so:
<ClientNotification>
<Status>OK</Status>
<BatchSize>0</BatchSize>
</ClientNotification>
An explanation of the return parameters:
Status (of the request) – Describes whether the request succeeded or not. The list of possible statuses
can be found below.
BatchSize – The number of MO transferred.
Type – Will always contain the word 'MoMessage'.
PhoneNumber – The number that sent the incoming message.
Network – The source network.
Status – Not in use.
StatusDescription – Not in use.
CustomerMessageID – Not in use.
CustomerParam – Not in use.
SenderNumber – Phone number to which the incoming message was sent.
SegmentsNumber – Not in use.
NotificationDate – Time of receiving the MO from the cellular operator.
SentMessage – The content of the message which was received by the respondent.
List of Possible Statuses
OK
Failed
BadUserNameOrPassword
20. Version 4.9
בע"מ ומפעלים מערכות שמיר
.ת.ד2097ציונה נס74120.טל9415550-03פקס9514736-03www.inforu.co.il
-19-
SMS Tools
Delete Future Messages
You can delete future sent messages programmatically using a WebService.
In order to delete these messages, one must input any data in the CustomerMessageID and
CustomerParam parameters at the time in which the message was originally sent.
Format
Microsoft .Net users should add reference to this URL:
http://uapi.inforu.co.il/ClientServices.asmx
Java / Delphi / Magic users should use this URL:
http://uapi.inforu.co.il/ClientServices.asmx?wsdl
Function name: DeleteFutureMessage.
Parameters: Explanation of Functions
UserName – Username of the account that was supplied by InforUMobile
Password – Password of the account
PhoneNumber – Number to which the message was sent
CustomerMessageId – ID sent in sending the message
CustomerParam – Parameter sent in sending the message
Response:
<ClientNotification>
<Status>OK</Status>
<BatchSize>1</BatchSize>
</ClientNotification>
List of Possible Statuses
Status
o OK – Success
o Failed – The request failed
BatchSize – Number of future messages deleted.
Notes
Deletion will be available only for singular messages sent, and not group messages sent.
If data was not inputted in the CustomerParam and CustomerMessageID parameters , the request
will fail.
21. Version 4.9
בע"מ ומפעלים מערכות שמיר
.ת.ד2097ציונה נס74120.טל9415550-03פקס9514736-03www.inforu.co.il
-20-
Remaining SMS Quota
A function that returns the amount of SMS messages remaining in the user account.
Format
Microsoft .Net users should add reference to this URL:
http://uapi.inforu.co.il/WebTools.asmx
Java / Delphi / Magic users should use this URL:
http://uapi.inforu.co.il/WebTools.asmx?wsdl
Function name: GetUserQuota
URL GET or POST:
http://uapi.inforu.co.il/WebTools/GetUserQuota.ashx
Parameters:
UserName – Username of the account that was supplied by InforUMobile.
Password – Password of the account.
An example of a request in HTTP Get:
http://uapi.inforu.co.il/WebTools/GetUserQuota.ashx?userName=XXX&password=XXX
Response:
<Result>
<Status>1</Status>
<Data>9955.00</Data>
</Result>
List of Possible Statuses
-26 - Error User ID, Data empty
1- OK, Data Contains the Quota
22. Version 4.9
בע"מ ומפעלים מערכות שמיר
.ת.ד2097ציונה נס74120.טל9415550-03פקס9514736-03www.inforu.co.il
-21-
Phone Number block check
The function checks if a certain phone number is blocked for receiving SMS.
Format
Microsoft .Net users should add reference to this URL:
http://uapi.inforu.co.il/WebTools.asmx
Java / Delphi / Magic users should use this URL:
http://uapi.inforu.co.il/WebTools.asmx?wsdl
Function name: CheckIfNumberBlocked
URL GET or POST:
http://uapi.inforu.co.il/WebTools/CheckIfNumberBlocked.ashx
Parameters:
UserName – Username of the account that was supplied by InforUMobile.
Password – Password of the account.
PhoneNumber – Phone number (string)
PrepaidAmount – Not in use. (Use 0 always)
An example of a request in HTTP Get:
http://uapi.inforu.co.il/WebTools/CheckIfNumberBlocked.ashx?userName=XXX&password=XXX&phon
eNumber=0529999999&prepaidAmount=0
Response:
After you issue the request, an answer is returned in XML format:
<Result>
<Status>1</Status>
<Data></Data>
</Result>
List of Possible Statuses
-26 - Error User ID, Data empty
-44- No permission to access, Data empty
-49- Phone number is blocked, Data empty
1 - Phone number is open, Data empty
23. Version 4.9
בע"מ ומפעלים מערכות שמיר
.ת.ד2097ציונה נס74120.טל9415550-03פקס9514736-03www.inforu.co.il
-22-
Blocking Phone Numbers
Blocking numbers from receiving messages programmatically using WebService or POST.
Format
Microsoft .Net users should add reference to this URL:
http://uapi.inforu.co.il/WebTools.asmx
Java / Delphi / Magic users should use this URL:
http://uapi.inforu.co.il/WebTools.asmx?wsdl
Function name: BlockPhoneNumbers
URL GET or POST:
http://uapi.inforu.co.il/WebTools/BlockNumbersMT.ashx
Parameters:
UserName – Username of the account that was supplied by InforUMobile.
Password – Password of the account.
PhonesList – The list of numbers to be blocked. Separate using semicolon (;).
An example of a request in HTTP Get:
http://uapi.inforu.co.il/WebTools/BlockNumbersMT.ashx?
UserName=david&Password=123456&PhonesList=0549999999;0556325698
Response:
After you issue the request, an answer is returned in XML format:
<Result>
<Status>1</Status>
</Result>
List of Possible Statuses
1 – Success
-26 – User identitiy failed
-33 – No correct phone numbers were found
24. Version 4.9
בע"מ ומפעלים מערכות שמיר
.ת.ד2097ציונה נס74120.טל9415550-03פקס9514736-03www.inforu.co.il
-23-
Contacts & Groups Management
Create or Update contact
This function create or update contacts. The key for update is email or phone or both.
If you create 5 contacts or less, the response will be synchronic and final, else the response contain
RequestToken ,You can check back later what the result of your request was.
https://capi.inforu.co.il/api/Contact/Update?json=
Example simple
{
"User": {
"Username": " USER ",
"Token": " TOKEN "
},
"Data": {
"Contacts": [
{
"FirstName": "David",
"LastName": "Cohen",
"PhoneNumber": "0589995551",
"Email": "Cohen@test.com"
},
{
"PhoneNumber": "0589995552"
}
]
}
}
Response
{
"StatusId": 1,
"StatusDescription": "Success",
"DetailDescription": "",
"FunctionName": "api/Contact/Update",
"RequestToken": "",
"Records": 2,
"ReturnData": null
}
Status:
1 = OK
-1 = Failed
26. Version 4.9
בע"מ ומפעלים מערכות שמיר
.ת.ד2097ציונה נס74120.טל9415550-03פקס9514736-03www.inforu.co.il
-25-
Explanation of parameters:
UserName – Username of the account that was supplied by InforUMobile
Token – Token of the account
Contacts – Email or PhoneNumber are mandatory all other fields are optional.
o ContactRefId - Optional - a unique id of the contact in the calling system
o GenderId - 1=Male , 2 = Female
o FirebaseToken – use for send notifications to google devices and apple,
if you send only FirebaseToken without Email or PhoneNumber, you should also send
ContactRefId.
o Platform – "ANDROID" / "IOS", If you use FirebaseToken you should also send
Platform.
27. Version 4.9
בע"מ ומפעלים מערכות שמיר
.ת.ד2097ציונה נס74120.טל9415550-03פקס9514736-03www.inforu.co.il
-26-
Check Status Token
This function checks the final response for your request (if you create more than 5 contacts)
https://capi.inforu.co.il/api/Contact/CheckJobStatusByToken?json=
{
"User": {
"Username": " USER ",
"Token": " TOKEN "
},
"Data": {
"RequestToken": "ljfkdsfds"
}
}
Response
{
"StatusId": 1,
"StatusDescription": "Success",
"DetailDescription": "",
"FunctionName": "api/Contact/CheckJobStatusByToken",
"RequestToken": "",
"Records": 2,
"ReturnData": null
}
1. Status:
1 = OK
-1 = Failed
-4 = RequestToken not found
-5 = Job in progress
2. StatusDescription – Status interpretation.
3. DetailDescription – Detail Description.
4. RequestToken – Not in use.
5. FunctionName – The name of the function you To which turned
6. Records – Number of contacts created or updated
7. ReturnData – Not in use.