Push Proxy Gateway uses http smsc in a special way. A HTTP SMSC generates following HTTP get request when it receives a sendmessage event: http://hostname:port/path?user=foo&password=bar&to=number&text=%02%06%17%ae %92localhost%3a8080%00%af%80&8d%cf%b4%80%02%05j%00e%c6%0c%03wap.iobox.fi %00%11%031%40wiral.com%00%07%0a%c3%07%19%99%06%25%15%23%15%10%c3 %04+%02%060%01%03Want+to+test+the+fetch%3f%00%01%01&udh=%06%05%04%0b %84%23%f0 Here text contains the unicode version of a tokenised SI document. If a sendsms service listens at this URL and is capable to understand it, it will send a WAP conforming SI to the phone specified by to. It is up to http server to understand escaped unicode text; they usually do. This is actually usefull, because this makes possible to build a PPG on the top of existing sendsms services. Of course PPG should work with other SMSCs.
Aarno
