| How to? |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through January 23, 2007 ⬆ |
◄ ► |
| Author | Message | ||||
| Guy Vachtel New member Username: Vachtel Post Number: 3 Registered: 07-2006 |
Hi I am new in the WAP push world and i am trying to send server initiation message to my SyncML H/S client using Now.SMS. Could you please add guideline (Step-By-Step) how to send WAP PUSH PAP message via NowSMS? I am trying to send Server alert notification to the handset so the h/s will start automatically the syncML with my sync4j server i read the thread here but i couldn't find the step by step instruction. i looked at the following link as well: http://support.nowsms.com/discus/messages/485/3293. html and can understand what should be done - which other tool / terminal should i use Please advise | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6284 Registered: 10-2002 |
Hi Guy, We get asked similar questions from time to time, but I'm at a disadvantage because I don't fully understand the SyncML protocol. What is the data that you want to send in your notification push? Is it similar to the data referenced in the following thread: http://support.nowsms.com/discus/messages/485/9072.html We don't have a WBXML converter for that type of data (although we could add one relatively easily). So without a WBXML converter, you would need to include the WBXML data in your HTTP PAP POST. (The format of the POST is shown in the link I referenced above.) Like I said, I don't have a full working knowledge of the SyncML protocol, so I'm not sure what the SyncML data is that you would be trying to send. So if it is not like the data referenced in the above thread, can you give me a pointer in the specs to the type of data that you want to send? If it is like the data referenced in the example, do you already have the WBXML conversion? If so, does the above link help in understanding how you would post this data using PAP? -bn | ||||
| Guy Vachtel New member Username: Vachtel Post Number: 4 Registered: 07-2006 |
Assuming i need to send the following XML page what should i do?how can i convert it to the right binary, which port should i POST it <?xml version="1.0" encoding="UTF-8"?> <SyncML xmlns='SYNCML:SYNCML1.1'> <SyncHdr> <VerDTD>1.1</VerDTD> <VerProto>SyncML/1.1</VerProto> <SessionID>1</SessionID> <MsgID>1</MsgID> <Target> <LocURI>IMEI:111111111111111</LocURI> </Target> <Source> <LocURI>http://hostaddressofserver</LocURI> </Source> <Meta> <MaxMsgSize xmlns='syncml:metinf'>10000</MaxMsgSize> </Meta> </SyncHdr> <SyncBody> <Alert> <CmdID>1</CmdID> <Data>206</Data> <Item> <Target> <LocURI>./Contacts</LocURI> </Target> <Source> <LocURI>./Contacts</LocURI> </Source> <Meta> <Type xmlns='syncml:metinf'>text/x-vcard</Type> </Meta> </Item> </Alert> <Final/> </SyncBody> </SyncML> Thanks for your support Guy | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6292 Registered: 10-2002 |
Guy, That looks like the exact same XML from the other thread. In that thread, there is an attachment with a supposed WBXML conversion of the data. The PAP HTTP POST gets directed to whatever port NowSMS is configured to use as its "web interface" port on the "Web" page of the configuration dialog. By default, it is 8800. The binary data needs to go into the PAP document as raw binary data. I could look at doing some tests and experiments from our end at performing the XML to WBXML conversion, as I am curious to learn how this process works. But it is probably going to be a couple of weeks before I can do this. -bn | ||||
| Guy Vachtel New member Username: Vachtel Post Number: 5 Registered: 07-2006 |
Ok, thanks for your reply i'll wait for your update | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6428 Registered: 10-2002 |
Guy, For you or anyone else that is interested in this ... we've implemented some support for sending this XML format from the "Send XML Settings" page. However, we can't really test it, because I believe we would need to have SyncML setup on a phone in order to try. There is a NowSMS 2006 update available for download at http://www.nowsms.com/download/20060824.zip. You can give it a try. It might work, but then again, we might not have all of the encoding just right since we can't test it. Perhaps someone that is interested in testing this capability could provision an account on a SyncML server that we could connect to over the internet for testing. -bn | ||||
| Guy Vachtel New member Username: Vachtel Post Number: 6 Registered: 07-2006 |
I tried to send the message using the new interface, and nothing received on my phone (i can see that 2 messages generated under the "Q" folder and then they sent) please advise Guy | ||||
| Guy Vachtel New member Username: Vachtel Post Number: 7 Registered: 07-2006 |
attached the loggers from the NowSMS
| ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6466 Registered: 10-2002 |
It's hard for me to provide any definitive answer ... because I'm not 100% sure that the message example that you provided above is the correct type of content to be included in this type of notification. That's why I suggested that maybe someone could provide us with an account on a SyncML server that we could connect to over the internet for testing. Then we could take a closer look at a typical protocol exchange, and perhaps better understand the type of message that should be sent out. That said ... when I look at your log ... I see one definite problem ... the SyncML message is being sent to the phone number of the modem. So when you send it out, it is being received back in by the modem ... | ||||
| Guy Vachtel New member Username: Vachtel Post Number: 8 Registered: 07-2006 |
How should i prevent the modem to get the message back? | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6564 Registered: 10-2002 |
Hi, Maybe I'm confused, but you would want to send the message to a phone number other than the one associated with the modem itself. That said, normally most phones when acting as a modem, will not forward any WAP push messages over the GSM modem interface ... the WAP push messages stay on the phone. But in this case, we're clearly receiving it over the GSM modem interface. You could try unchecking the "Receive SMS Messages" under the properties of the modem in the NowSMS SMSC list. This will stop NowSMS from polling the modem for new received messages. -bn | ||||
| Guy Vachtel New member Username: Vachtel Post Number: 9 Registered: 07-2006 |
hi I unchecked it and it's works, i managed to send it to the phone but the phone didn't recognized it as i expecxted: as Sync alert message, no indication and no error log on the phone :-( do you know abouty any phone simulator that i can use to recieve the message and to validate it? | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6609 Registered: 10-2002 |
Hi again Guy, I'm at a disadvantage because I don't have a working SyncML server. I spent 4 hours today trying to install Funambol (Sync4J), and I could not get it to accept SyncML sessions from a mobile device. I'm probably just missing something simple ... but judging from the proxy logs, it looks like I didn't have the correct server URL. (The old Sync4J manual says that it is host:8080/sync4j/sync ... but that didn't work. And the new Funambol manual omits the section that talks about connections from mobile devices. I guessed maybe it changed to host:8080/funambol/sync ... but no.) I'd be happy to look into this in more detail, but as I suggested earlier, I believe that I need someone to provide us with an account on a SyncML server that we could connect to over the internet for testing. Then we could take a closer look at a typical protocol exchange, and perhaps better understand what information might be missing. Looking at your example above, I don't know if the issue might just be that you need to be using valid values for the source and target URIs. If you can provide a SyncML account that I can connect to over the internet, then I'd like to take a closer look at the protocol exchange. (If you don't want to supply these account details here, then please e-mail them to nowsms@now.co.uk with "Attention: Bryce" in the subject line of the message.) -bn | ||||
| Guy Vachtel New member Username: Vachtel Post Number: 10 Registered: 07-2006 |
Not sure you need the sync server for the test, what i would like to see is a simple scenario: after sending the PAP message from the nowSMS to the handset to see that there is a request from the handset to the "syncML server" (doesn't matter for me if the sync succeed, only to see that the message arrived correctly from the PPG to the handset and trigger the syncML application on the handset to send request to any destination | ||||
| Guy Vachtel New member Username: Vachtel Post Number: 11 Registered: 07-2006 |
BTW - as for the sync4j configuration: you typed it correctly, check your configuration file at: C:\Program Files\Sync4j 2.3\server\config\Sync4j.xml for the following parameter: <void property="serverURI"> <string>http://xx.xxx.xx.xx:8080/sync4j/sync</string> </void> Instead of the xx put your internet IP (make sure the IP & the port are not blocked by your firewall). Make sure you entered the same address in your phone / sync application. | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6699 Registered: 10-2002 |
Hi Guy, I'd really prefer connecting to someone else's server that is already working. It looks like you have Sync4j v2.3, and it looks like that has been replaced by Funambol v3.0. And although I haven't spent much time on it, I just can't figure out the URL for connecting to the server. (It's not a firewall issue, I can trace the connection, and I get a "404 not found" error at the HTTP level.) I understand what you are saying ... that you are looking for a simple scenario. The issue is that the PAP message that you are generating is being sent to the phone, and we are generating the proper headers to get the push message routed to the SyncML client on the phone. However ... just because the message makes it to the client doesn't mean that the client will act on it. We've seen this with other WAP push protocols as well. If the receiving client doesn't understand the content, or it is "out of context", then the client that receives the push might decide to ignore it. I'm guessing that context might matter. For example, are the Source and Target LocURI values set correctly? Is the SessionID value important? What I'd like to do is have one of my phones connect to a SyncML server, where I can trace a simple sync session. I would then try different variations on the push message to make sure that the content of the push message contains values that are in the proper context for the existing communication between client and server. I just don't want to become an expert in configuring a SyncML server in the process. -bn | ||||
