unsubscribe;
unsubscribe;
sendota problems
Hello, I want to configure synchronization for Nokia 6070 mobile phone. My program generates this XML provisioning document: ?xml version=1.0? !DOCTYPE wap-provisioningdoc PUBLIC -//WAPFORUM//DTD PROV 1.0//EN http://www.wapforum.org/DTD/prov.dtd; wap-provisioningdoc characteristic type=BOOTSTRAP parm name=NAME value=SKLADDEVEL/ /characteristic characteristic type=APPLICATION parm name=APPID value=w5/ parm name=TO-NAPID value=INTERNET / parm name=NAME value=SKLADDEVEL/ parm name=ADDR value=http://megalogika.stp.lt/funambol/ds/ characteristic type=RESOURCE parm name=URI value=card/ parm name=NAME value=Contacts DB/ parm name=AACCEPT value=text/x-vcard/ /characteristic characteristic type=RESOURCE parm name=URI value=cal/ parm name=NAME value=Calendar/ parm name=AACCEPT value=text/x-vcalendar/ /characteristic characteristic type=RESOURCE parm name=URI value=notes/ parm name=NAME value=Notes/ parm name=AACCEPT value=text/plain/ /characteristic characteristic type=APPAUTH parm name=AAUTHNAME value=funUsrVe/ parm name=AAUTHSECRET value=funPassVe/ /characteristic /characteristic /wap-provisioningdoc When i send it via Kannel's /sendota, via this request: /cgi-bin/sendota?password=##username=##type=oma-settingssec=USERPINpin=1234to=%2B37069953201text=%3C%3Fxml+version%3D%221.0%22%3F%3E%0A%3C%21DOCTYPE+wap-provisioningdoc+PUBLIC+%22-%2F%2FWAPFORUM%2F%2FDTD+PROV+1.0%2F%2FEN%22%0A%22http%3A%2F%2Fwww.wapforum.org%2FDTD%2Fprov.dtd%22%3E%0A%3Cwap-provisioningdoc%3E%0A%3Ccharacteristic+type%3D%22BOOTSTRAP%22%3E%0A%3Cparm+name%3D%22NAME%22+value%3D%22SKLADDEVEL%22%2F%3E%0A%3C%2Fcharacteristic%3E%0A%3Ccharacteristic+type%3D%22APPLICATION%22%3E%0A%3Cparm+name%3D%22APPID%22+value%3D%22w5%22%2F%3E%0A%3Cparm+name%3D%22TO-NAPID%22+value%3D%22INTERNET%22+%2F%3E%0A%3Cparm+name%3D%22NAME%22+value%3D%22SKLADDEVEL%22%2F%3E%0A%3Cparm+name%3D%22ADDR%22+value%3D%22http%3A%2F%2Fmegalogika.stp.lt%2Ffunambol%2Fds%22%2F%3E%0A%3Ccharacteristic+type%3D%22RESOURCE%22%3E%0A%3Cparm+name%3D%22URI%22+value%3D%22card%22%2F%3E%0A%3Cparm+name%3D%22NAME%22+value%3D%22Contacts+DB%22%2F%3E%0A%3Cparm+name%3D%22AACCEPT%22+value%3D%22text%2Fx-vcard%22%2F%3E%0A%3C%2Fcharacteristic%3E%0A%3Ccharacteristic+type%3D%22RESOURCE%22%3E%0A%3Cparm+name%3D%22URI%22+value%3D%22cal%22%2F%3E%0A%3Cparm+name%3D%22NAME%22+value%3D%22Calendar%22%2F%3E%0A%3Cparm+name%3D%22AACCEPT%22+value%3D%22text%2Fx-vcalendar%22%2F%3E%0A%3C%2Fcharacteristic%3E%0A%3Ccharacteristic+type%3D%22RESOURCE%22%3E%0A%3Cparm+name%3D%22URI%22+value%3D%22notes%22%2F%3E%0A%3Cparm+name%3D%22NAME%22+value%3D%22Notes%22%2F%3E%0A%3Cparm+name%3D%22AACCEPT%22+value%3D%22text%2Fplain%22%2F%3E%0A%3C%2Fcharacteristic%3E%0A%3Ccharacteristic+type%3D%22APPAUTH%22%3E%0A%3Cparm+name%3D%22AAUTHNAME%22+value%3D%22funUsrVe%22%2F%3E%0A%3Cparm+name%3D%22AAUTHSECRET%22+value%3D%22funPassVe%22%2F%3E%0A%3C%2Fcharacteristic%3E%0A%3C%2Fcharacteristic%3E%0A%3C%2Fwap-provisioningdoc%3E it generates a single sms message: 0051000B9173x0xxFx0004A7870605040B840B8401062F1F2DB69181923738424536353833373946364436324435394544374431323831443536454141423541343346353500030B6A0045C65003424F4F5453545241518705034E414D45000603534B4C414556454C000101C650034150504C49434154494F4E0001870503415050494400060377350001870503544F which is successfully delivered to the handset which then claims that it is 'Unable to save settings. Setttings discarded.' I tried this via GET request and POST request as well (not XML post, though, because I could not find anything concerning OMA CP in the examples provided in Kannel user guide). Meanwhile, NowSMS generates 3 messages: 0051000B917xx0xxFx0004A78C0B05040B8423F305030105062F1F2DB69181924144304542424539423642323245443636433746433236353435373437433036373243394243454300030B6A0C54657374310074657374310045C6560187070683000101C600015501873606037735000187220603494E5445524E45540001870706830001870001340603687474703A2F2F6D 0051000B9173x0xxFx004A77D0B05040B8423F305030320444200018700012E0603746578742F782D7663616C656E646172000101C600015901873A06032E2F6E6F7465730001870706034E6F74657320444200018700012E0603746578742F706C61696E000101C6000157018731068306018700013206830601010101 0051000B9173x0xxFx0004A78C0B05040B8423F30503026567616C6F67696B612E7374702E6C742F66756E616D626F6C2F64730001C600015901873A06032E2F636F6E7461637473000187070603436F6E746163747320444200018700012E0603746578742F782D7663617264000101C600015901873A06032E2F63616C656E64617200018707060343616C656E646172 which are successfully delivered to the phone and recognized by it as a valid and working synchronization settings. Funnily enough, these three messages are routed via the same kannel. Therefore my questions are: * is Kannel wrongly transforming my request into OMA settings provisioning message? * if so, is it because of my error or because of a bug in Kannel? any other advice? -- Tomas Verbaitis Verbaitis ** http://megalogika.lt
Re: Omitting the generation of delivery reports
Hi, Did you mean this? if (DLR_IS_SUCCESS_OR_FAIL http://doxygen.kannel.org/d1/d5d/dlr_8h.html#a13(msg-sms.dlr_mask)) 00918 pdu http://doxygen.kannel.org/df/de6/wsp__session_8c.html#a182a79-u http://doxygen.kannel.org/da/d81/structSMPP__PDU.html#o15.submit_sm.registered_delivery = 1; Inside the SMPP_PDU http://doxygen.kannel.org/da/d81/structSMPP__PDU.html* msg_to_pdu http://doxygen.kannel.org/de/dfe/smsc__smpp_8c.html#a23function In we change this kannel should be recompiled again.is there any other way? Regards Elton On Sun, Mar 15, 2009 at 7:55 PM, Falko Ziemann fal...@gmail.com wrote: Hi, this is a protocol issue. SMPP for example has only the switch registered_delivery where you can (de-)activate all DLRs. It is not possible to activate on some kinds of DLR. Kannel has no control about this. But kannel should not forward certain DLRs to the DLR-URL if you're not interessted in them. Regards Falko Am 15.03.2009 um 17:52 schrieb Elton Hoxha: Hi all, I know this subject has been asked a lot, but my concern is something else. I have played with dlr-mask pretty much and it is working very well. In some cases I dont want to exhaust the database of SMSC creating useless delivery statuses for bulk SMS. Making my dlr-mask=10 didnt change anything. It is supposed that this value concerns only to submit and failure. This is what I need, only the acknowledment that sms has been submitted. But the SMSC is creating the delivery status as well, pending in the queue and making retries. Why the mask is behaving the same with different values? Thanks Elton
problem with sendsms POST method
hi, kannel is working fine. Now I need to change the request type to POST (from an own written sendsms script). My application receives the error code (curl) 22 == the request has been rejected from the kannel server.. I do the same request via url (browser) with a special character in the message (which is the reason why I want to change from GET to POST) does somebody have an idea? xox bea -- Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss für nur 17,95 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a
Re: problem with sendsms POST method
On Mon, Mar 16, 2009 at 5:10 PM, Beatrice Tamburrino beatrice.tamburr...@gmx.ch wrote: hi, kannel is working fine. Now I need to change the request type to POST (from an own written sendsms script). My application receives the error code (curl) 22 == the request has been rejected from the kannel server.. check what's the http error code. curl_getinfo(CURL_HANDLE, CURLINFO_HTTP_CODE) If kannel rejects the http post request it could be malformed request. Can you send us what are you trying to send via the post request. I do the same request via url (browser) with a special character in the message (which is the reason why I want to change from GET to POST) What's that special character that can not be send via get request. maybe there is a way to url encode that character. BR, Jovan
