| PID on operatorlogos |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 15, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Anonymous |
Is is right that the PID should contain the countrycode. Is this nescesarry? I send out using AA and that is not Denmark, but still it works. | |||
| Bryce Norwood - NowSMS Support |
No. The PID is pretty much irrelevant when sending operator logos. The country code (and network code) is included in the operator logo message data itself, but not in the PID. There are actually very few really good uses for the PID. You didn't ask about it, but since we are talking about PIDs, and since I have a habit of getting off subject from time to time, I'll mention one very good use of the PID. If you specify a PID value between 41 and 47 (inclusive), this means that if an existing message exists from the same sender address, with the same PID value, then the new message should replace the existing message. There are a variety of good uses for this PID setting. It is quite useful to help ensure that you don't overload someone's SMS inbox if you are sending them regular alerts where only the most recent message is relevant. One of the best examples is a quiz type of application ... where you want to have a dialog with a user in a sequence of messages. Let's say you start by sending out an SMS message that asks the user a question. The user replies back via SMS ... and you send back another question (or another response). You can use one of the replace message type PIDs on the message, so that new messages automatically overwrite any existing messages. This way you're not filling up the user's SMS inbox (so many people don't delete their messages right away) ... and you can help prevent the possibility of a user going back to an earlier message in the dialog that is no longer in the current context. Unfortunately, you can't do this via the simple web form that we have for sending a message, you have to do it with a direct URL request. If you want to try it (obviously the exact behaviour varies by phone), you can try this: http://gateway.ip:port/?PhoneNumber=xxxxx&PID=41&text=message+1 Wait for your phone to receive the message with the text "message 1". Read this message if you like, but don't delete this message. Now issue another URL request: http://gateway.ip:port/?PhoneNumber=xxxxx&PID=41&text=message+2 The message with the text "message 1" should now be gone from the phone, and replaced with "message 2". This is a nice feature to be used for some applications. In fact, I might go ahead and edit our "send text message" HTML form to include radio buttons for setting a replacement message type so that more people can be aware that this is possible. -bn | |||
| Bryce Norwood - NowSMS Support |
Continuing a bit off-topic ... the replacement message type PIDs (41 thru 47 inclusive) are good for SMS messages. But they won't do any good for MMS messages, where there is no similar functionality. There is a similar type of functionality for WAP push SI (service indication) messages. If you set the "SI ID", then a new push with the same "SI ID" will replace an existing push ... at least that is how it is supposed to work in the spec, not all phones handle it 100% correct. You can also use the "Signal Action" = "Delete" against an "SI ID" to delete a previously issued push ... again, if the phone supports this. -bn | |||
