|
|
Posted by Jerry Stuckle on 03/08/07 04:24
Justin wrote:
> Dear Jerry,
> There's a API provided to us by the provider, with the parameters
> required and process of sending. So the situation is like this. In
> order to prevent ppl from abusing the use of mobile contents(spam,
> unnecessary charges to mobile users), the local telcos strictly
> required us(content provider) to follow their registration process. A
> specific keyword must be provided to indicate the registration
> process. Assuming REG ABC is my keyword for the registration. Now i
> want my subscribers to send in "REG ABC NAME ID AGE LOCATION". the
> string will be one of the parameter i receive(lets put it as SMS). So
> the parameters will be the mobile numbers, time, date, sms and so on.
> The thing is the provider only take REG ABC into consideration, so
> any numbers which send in a text msg to their server with the prefix
> REG ABC will be routed to us(will call my php page). And i need to
> repy -1 to acknowledge the receipts. Then the whole process is done.
> But the thing is some of my subscribers leave out some important info
> such as age, location etc (which is important to me but not the
> provider) thats why i wanna send a msg to them ask them to provide the
> additional info. (that is when the problem occurs). As the provider
> only recognize REG ABC and -1 as a whole process, they dun care
> whether the subscribers send in full msg or not. my side will have to
> do the verification ourselves. That's why when i receive a msg with
> incomplete info, i need to send them the msg, and this process is done
> by using another method in the API.
> I tried setting up a cron job or running the page with browser,
> everything works well, the extra msg will be sent out. but when use
> mobile phone to register, the page doesnt refresh/redirect. So they
> only receive the standard msg from the provider. The standard msg is a
> must as it's the requirements from the telcos. So i need to reply -1
> first then only proceed with my own verification.
>
> It's really nice meeting you here and thanx for being so helpful.
>
> Regards,
> Justin
>
Hi, Justin,
Yes, it might work with a browser. But in the cell phone registration
process they aren't communicating with you - they're communicating with
their cell provider. And therein lies the problem.
When you respond, you're responding to the cellular provider. And you
can only send what they understand. Since you've indicated the only
thing they understand is a -1, that's all you can send. Anything else
will be kicked out by them.
When you test with the browser you don't have that intermediate step
(the cellular provider) so of course it works.
The only thing you can do is talk to the provider to see if there is an
extended interface you can use.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================
Navigation:
[Reply to this message]
|