Navigacija
Lista poslednjih: 16, 32, 64, 128 poruka.

M payments problem???

[es] :: XML :: M payments problem???

[ Pregleda: 2674 | Odgovora: 0 ] > FB > Twit

Postavi temu Odgovori

Autor

Pretraga teme: Traži
Markiranje Štampanje RSS

vialli
Beograd

Član broj: 2548
Poruke: 31
..njuel-bg.customer.sbb.co.yu.



Profil

icon M payments problem???07.07.2006. u 09:15 - pre 193 meseci
Ne znam da li je ovo pravi forum ali....
Da li neko ima iskustava sa M-payments? Jedna firma mi nudi usluge placanja sadrzaja preko sms-a, ali zbog zauzetosti resursa ne mogu da mi naprave skriptu koja ce da odradi posao. Tako da se svelo na to da se sam snadjem. Dobio sam instrukcije, a posto se ne razumem u tematiku nisam bas razumeo sta i kako treba da uradim.

2.2. HTTP Interface

This type of content delivery is used when MO messages (SMS messages that were
sent by mobile service user to "FIRMA" service) are forwarded to customer.
Standard HTTP protocol is used as a means of transportation.

There are two cases when HTTP type of content delivery is used:
2.2.1. Single message delivery – each MO message received from end
users is forwarded to customer
2.2.2. Aggregated data delivery – only aggregated data on MO messages
is forwarded to customer (e.g. results of SMS voting)


2.2.1. Single message delivery
This type of content delivery is used when customer wants to keep part of the
service logic on his side. This type of delivery enables customer to use connections
to many countries transparently by using one simple interface towards "FIRMA".
In this way, customer doesn’t have to deal with details of interconnection problems.
Instead, he can focus on delivering quality service operation to his users.

There are three communication conducts used:

1) MO delivery with predefined response to end user
"FIRMA" service forwards MO message to customer via HTTP request
(POST or GET) and customer acknowledges message reception with
standard HTTP 200 OK response. "firma" servcie sends predefined
answer to end user. Response text is fuly configurable by customer.



2) MO/MT delivery
"FIRMA" forwards MO message to customer via HTTP request
(POST or GET) and customer returns MT message via HTTP response.
This MT message is forwarded to end users mobile phone.


This type of content delivery uses HTTP-POST or HTTP-GET request-response
mechanism to communicate with customer.

Standard MO message parameters for HTTP interface are:

Parameter Mandatory Description
number Yes End user number
text Yes Message text received from end user. If requiered,
"FIRMA" can modify received text prioir to
sending to customers application (e.g. remove
keyword from message)
messageid Yes Unique message id

Standard MT message parameters for HTTP interface are:

Parameter Mandatory Description
number Yes End user number
text Yes Message text
messageid Yes Unique message id (samo value as received in MO
message)
service No Used if two or more diferent services connect to
same interface script.
These parameters are standard but not mandatory. "FIRMA" and customer can set
an agreement on which parameters wil be used. If requiered, aditional parameters
can be used.

Here is an example of HTTP-POST request sending the MO message “Helo” from
"FIRMA" to customer:

POST /cgi/post HTTP/1.1 ?
User-Agent: "FIRMA"/1.2 ?
Host: 323.157.223.102 ?
Content-Type: application/x-www-form-urlencoded ?
Connection: close ?
Content-Length: 34 ?
username=abc&password=cba&text=Hello&number=0041791231234&provid
er=2281! ?
Here is an example of HTTP-GET request sending the MO message “Helo” from
"FIRMA" to customer:

GET /smsc/IncomingHTTP.asp?
username=abc&password=cba&number=0041791231234&text=Hello&provid
er=22801 HTTP/1.1 ?
User-Agent: "FIRMA"/1.2 ?
Host: 323.157.223.102 ?
Connection: close ?

In either case (HTTP-POST or HTTP-GET), customer responds either with standard
HTTP response (“200 OK”) or with a generated HTML page. If customer script
returns just one parameter (e.g. “OK” as notification that MO message sent by
"FIRMA" is accepted – MO delivery) it is best to put it out on the page. However,
"FIRMA" also supports multiple return values with delimiter that can be agreed
with customer. Usualy delimiter is “&” symbol. "FIRMA" parses response and uses
data received in response. E.g. when sending MT message back (MT delivery):

number=0041791231234&text=Wellcome




Da li moze neko da mi pomogne?

Unapred zahvalan,
vialli
 
Odgovor na temu

[es] :: XML :: M payments problem???

[ Pregleda: 2674 | Odgovora: 0 ] > FB > Twit

Postavi temu Odgovori

Navigacija
Lista poslednjih: 16, 32, 64, 128 poruka.