| Wap push SI ID |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through December 01, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Anonymous |
I remember somewhere saying if we send a wap push with the si id it will always override older wap push msg of the same si id how can we input it for url submission? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2306 Registered: 10-2002 |
That is correct. When you submit a WAP PUSH SI message, there can be an ID associated with it. Later, you can submit another push with the same ID, and (if the phone supports this properly) the content of the new push will replace the existing one. It is also possible to send a push referencing an ID, along with a "signal-action" of "delete", which deletes an existing push. Usually if an SI ID is not supplied, the phone will use the URL of the push as the SI ID. (But if you require this behaviour, it is best to set it explicitly.) Some time ago, we added parameters to our web interface for WAP Push, so that you could set this id, or use other signal-actions, such as delete. Unfortunately, the parameters were only documented in the readme file. The following variables can be used when sending a WAP Push Service Indication (SI) message: WAPURL - URL to be included in the push. Text - Text message associated with the push. WAPSIID - "ID" for the service indication message. (Note: Specs recommend including your domain name in the ID to avoid conflicts with other applications, e.g., id@yourdomain.com. Or you can specify a URL.) WAPSIACTION - "Signal Action" for the push, with possible values of "signal-none", "signal-low", "signal-medium", "signal-high", and "delete". WAPSIEXPIRES - Set the "si-expires" attribute for the push, which specifies when the push expires. Requires that the date be input in the format: YYYY-MM-DDThh:mm:ssZ (where "T" and "Z" are literal characters). WAPSICREATED - Set the "created" attribute for the push, which is useful when sending out replacement pushes with the same ID as a previous push. This attribute allows the receiving device to know that the date/time of a replacement push is later than an earlier received push. (If the date/time of a replacement push is before that of an earlier received push, the existing push should not be replaced.) Requires that the date be input in the format: YYYY-MM-DDThh:mm:ssZ (where "T" and "Z" are literal characters). For WAP Service Load (SL) pushes, the following parameters can be specified: WAPURL - URL to be included in the push. WAPSLACTION - "Action" associated with the push, with possible values of "execute-high", "execute-low" and "cache". | |||
| Anonymous |
what does the high low in wap signal action is for? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2378 Registered: 10-2002 |
The signal actions are phone dependent. The idea is that the phone might use different methods to signal the user. A "low" signal might mean that there is no audible notification. A "high" signal might zap the phone's owner with an electrical current.  The idea is that the phone might produce a more noticeable alert for a higher priority message. Think of the signal-action's as representing priority. What the phone does based upon the signal-action is all phone dependent ... and FWIW, I don't think that many phones actually implement different signal actions. | |||
| Beemabi Husaina New member Username: Beemabi Post Number: 13 Registered: 05-2004 |
Hai Bryce, The parameters that you have mentioned for SI push,should these be added along with your suggested MMSWAPPush Program with that WAPPush parameter set to 'Yes'? Regards, A.H.K.Beemabi Husaina | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3052 Registered: 10-2002 |
That's a good idea. There's a lot of more pressing features in the development queue at present, but I'll see if we can get this on the future enhancements list. | |||
| Beemabi Husaina New member Username: Beemabi Post Number: 14 Registered: 05-2004 |
Hai Bryce, I got the SI push program successfully done with the parameters you suggested by adding the parameters along with the MMS Push parameters.But I am not able to get SL Push properly.As per the specification, the SL message must start loading the URI mentioned in the WAPURL parameter as soon as it reaches the mobile.But it is not getting done like that when i send a SL message to the mobile phone.Can you spot out the reason and help me out in this matter. Regards, A.H.K.Beemabi Husaina | |||
| Beemabi Husaina New member Username: Beemabi Post Number: 15 Registered: 05-2004 |
Hai Bryce, One more clarification added up to the above query.SL message gets submitted like a SI message.It is seen clearly from the SMSOUT log file where the data is encoded as say, 2004-07-19 11:15:16,40FB5348.req,10.145.3.103,9840410504,OK -- Nokia 7600 (USB) #3,Binary=1;DCS=4;UDH=0605040B8423F0;Data=410601AE02056A00 45 C60C037761702E6D756C74696D61702E636F6D0001034269736D696C000101 The 45 (shown separately above) in the data specifies the SI content.But actually this data was caught in the NowSMS "SMSOUT.log" file when i tried sending a SL message.For SL message the code must be 85 and not 45.This shows clearly that SL is taken up for SI message.How to change the mode?Is there any way to edit the log file for SL message directly or any other parameter to be added? Regards, A.H.K.Beemabi Husaina | |||
| Beemabi Husaina New member Username: Beemabi Post Number: 16 Registered: 05-2004 |
Hai Bryce, One more clarification added up to the above query.SL message gets submitted like a SI message.It is seen clearly from the SMSOUT log file where the data is encoded as say, 2004-07-19 11:15:16,40FB5348.req,10.145.3.103,9840410504,OK -- Nokia 7600 (USB) #3,Binary=1;DCS=4;UDH=0605040B8423F0;Data=410601AE02056A00 45 C60C037761702E6D756C74696D61702E636F6D0001034269736D696C000101 The 45 (shown separately above) in the data specifies the SI content.But actually this data was caught in the NowSMS "SMSOUT.log" file when i tried sending a SL message.For SL message the code must be 85 and not 45.This shows clearly that SL is taken up for SI message.How to change the mode?Is there any way to edit the log file for SL message directly or any other parameter to be added? Regards, A.H.K.Beemabi Husaina | |||
| Beemabi Husaina New member Username: Beemabi Post Number: 18 Registered: 05-2004 |
Hai Bryce, I am awaiting your reply for the above queries. Regards, A.H.K.Beemabi Husaina | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3129 Registered: 10-2002 |
Hi Beemabi, Sorry, I am running a bit behind on some replies. The "45" code is not specific to SI or SL. However, I can see from your example that the content type code in the push message is "AE", and that does indicate that it is an SI message. An SL message would have B0 instead. How exactly are you submitting this push message? Are you doing it from our web interface, or via a URL request? I just tried an SL push from our web interface, and it seems to work correctly. Try that ... If you are generating your own URL request, be sure that the URL request includes the parameter WAPSL=1. -bn | |||
| Beemabi Husaina New member Username: Beemabi Post Number: 19 Registered: 05-2004 |
Hai Bryce, Actually i had developed a java code with the parameters you had mentioned earlier say, WAPSIID,WAPSIACTION,WAPSIEXPIRES,WAPSICREATED, MMSFrom,MMSSub,MMSWAPPush,for SI message and the parameter WAPSLACTION, MMSFrom,MMSSub,MMSWAPPush set for SL message. The Code for SI with parameters works fine ,while for SL, message reaches the mobile ,but as an SI message.The parameters mentioned above were specified in your previous mails. Are the parameters for SL correct or am i supposed to include anything in addition. Regards, A.H.K.Beemabi Husaina | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3359 Registered: 10-2002 |
Hi Beemabi, Did you include WAPSL=1 as a parameter, in addition to the WAPSLACTION setting? The reason I ask is because when WAPURL is present in a URL request, NowSMS defaults to sending an SI, unless it sees WAPSL=1 in the request. -bn | |||
| Beemabi Husaina New member Username: Beemabi Post Number: 20 Registered: 05-2004 |
Hai Bryce, I had got the SL messaging code successfully once adding the WAPSL parameter.Thanks.My next proceeding is to convert the code to send SI / SL message to a simulator instead of a mobile.If so,in the destination phone number details, what am i supposed to give.With the same NowSMS setup is it possible to send SI/SL message to a simulator installed in a PC. One more query.Are there any ideas in the future release of NowSMS to perform Cache Operation too? If so , I would be pleased to know it. Regards, A.H.K.Beemabi Husaina | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3374 Registered: 10-2002 |
Hi Beemabi, If you specify an IP address instead of a phone number (in the phone number parameter), it will send the push over IP (this option is only valid for sending a WAP Push SI, SL, or MMS notification). We do have support for cache operation in v5.51, as an "XML Settings Document" ... so you post the XML for the cache operation under the menu option for XML Settings. Unfortunately, there is no option for routing any of these XML settings to an IP address instead of via SMS. But one thing you can do, is write an HTTP SMSC handler. So that we call your script every time we have an SMS to send. If your script can accept the SMS message and route it into your simulator, that is a possibility. -bn | |||
| Beemabi Husaina New member Username: Beemabi Post Number: 21 Registered: 05-2004 |
Hai Bryce, I tried sending Push messages over IP to a simulator.But I find no response from simulator.The simulator closes if already opened.There is no log for data in SMSOUT.log file of NowSMS.So I am unable to decide if data reached the simulator or not.Can you please help me out in this matter. Regards, A.H.K.Beemabi Husaina | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3397 Registered: 10-2002 |
When you send a WAP Push (SI or SL), or an MMS notification, to an IP address, it only gets logged in the SMSWEB-yyyymmdd.LOG file. It never makes it to the SMSOUT log, basically because we do it real time as the message is submitted. Most emulators don't listen for WAP push over IP. See the following thread for details about using NETSTAT to determine if the emulator you are using is even listening: http://support.nowsms.com/discus/messages/1/3652.html | |||
