problem with unicode?
Hello! Recently my kannel 1.2.0 box receive the cyrillic unicode message and pass strange urlencoded parameter (text) into sms-service (see web server log). Any ideas? Thanks a lot. [kannel.log] 2002-07-17 17:42:56 [8] DEBUG: AT2[PHMTS]: -- 07910759679901F0240B919720713370F8207071712494210C041F04400 438043204350442 2002-07-17 17:42:56 [8] DEBUG: AT2[PHMTS]: Numeric sender (international) +79021733070 2002-07-17 17:42:56 [8] DEBUG: AT2[PHMTS]: -- AT+CNMA^M 2002-07-17 17:42:56 [13] DEBUG: boxc_sender: sent message to 127.0.0.1 2002-07-17 17:42:56 [12] DEBUG: boxc_receiver: got ack 2002-07-17 17:42:56 [1] DEBUG: Dumping 0 messages and 0 acks to store [access.log] 2002-07-17 17:42:56 Receive SMS [SMSC:PHMTS] [SVC:] [ACT:] [from: +79021733070] [to:+79165904505] [flags:0:3:0:0:0] [msg:12:041F04400438043204350442] [udh:0:] [smsbox_access.log] 2002-07-17 17:42:56 SMS HTTP-request sender:+79021733070 request: 'mail gaksenov Sent' url: 'http://127.0.0.1/ cgi-bin/sms2mail?to=gaksenovfrom=%2B79021733070text =%04%1F%04%40%048%042%045%04B' reply: 200 ' successful ' [web server log] 127.0.0.1 - - [17/Jul/2002:17:42:56 +0400] GET /cgi-bin/sms2mail?to=gaksenovfrom=%2B79021733070text =%04%1F%04%40%048%042%045%04B HTTP/1.1 200 5 Kannel 1.2.0 with best wishes German Aksenov phone: (095)258-7258 ext. 7836
Kannel deb and rpm
I've setup links for deb and rpm packages for 1.2.0 Please test them and bug-report to devel or to my email. rpm file is alienized from debian, so I don't know if it is ok.
Re: Phone as MMSC 3/3
David White wrote: Both sender and recipient must either use the same MMSURL, or the MMSC operators must agree to relay messages between each other. This makes it unlikely that an on-phone MMSC would work as desired. yeah, officials from Nokia HQ Helsinki has signalled to me that they are enforcing operators to inter-connect their MMSC installation for this reason. And they do inter-operability testing with other MMSC vendors to ensure there is no business breaking effect. I suppose we agree all that the more operators are inter-connected, the more MMS will be send and hence revenues generated. So it's an intrinsic interest of any operator to have as much inter-connects as possible, at least as long payoff is not dominating costs in this trade-off situation. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
RE:Re: Phone as MMSC 2/3
-
Re: kannel download ..
www.kannel.org - download stable release points to 1.2.0 development release points to 1.1.6 .. so, what's the current development snapshot? still 1.1.6 ? yep. There have been some patches incorporated after 1.2.0 and there will be some following in the next 2 weeks I guess, so I'd like to expect a new development release in 2-3 weeks. BTW, you can allways download a cvs-snaphot tarball package on a daily basis via the same download page. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: AW: AW: Phone as MMSC
What we need is a reverse wapbox. something that listens for http and send wsp packets. This way I could point opie-konqueror to use pawbox (reverse wap) as a proxy and have a wml browser. konqueror supports wml. Something like fakewap, but with a http proxy listener hmmm, I didn't get the point. *clueless_scrumble* Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Phone as MMSC
Yes. You have a regular wap configuration plus one mms-url, wich contains the mmsc server's url. You just need to use your usual connection and point to your favorite mms-url. But I thing operators will block MMS traffic to other mmsc-urls. Why? Because they need to know how to charge for a MMS, and they can only charge if the MMS is processed by their own MMSC. I have seen Vodafone in D2 (which offer MMS since some time) do not use their regular WAP gateway for the proxying, but do use an dedicated one. So we could blast operators MMS revenue fantasies, if someone would put up a free MMSC with an public adressable mms-url, right? Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
RE:Re: Phone as MMSC 1/3
I'm afraid it's not that simple. A real weakness of MMS is that an operator has the choice between an interoperable service, where the WAP gateway may access any MMS store, and a secure service, where there is only one allowed store, and MM's are relayed over MM4. Operators prefer the latter. cont'd
RE:Re: Phone as MMSC 3/3
Both sender and recipient must either use the same MMSURL, or the MMSC operators must agree to relay messages between each other. This makes it unlikely that an on-phone MMSC would work as desired. Sorry about the number of mails, BTW; the T68i mail client is rather limited. David WHITE
Nokia 3510 wap problem
Title: Message Hi, I'm using quite new Kannel cvs version as wap gateway. With the Nokia 3510, when trying most wap sites, and the "Tone services" from the menu, I get the error message "File too large to be loaded". No problems with other phones like Ericsson T39... wapbox.log looks like this: 2002-07-18 13:43:31 [8] INFO: WSP: Fetched http://wap.aftonbladet.se (text/html, charset='') 2002-07-18 13:43:31 [8] INFO: WSP: Got status 413 2002-07-18 13:43:31 [8] WARNING: WSP: Content type text/html not supported by client, deleting body. Is the problem in the phone (seems weird since Nokias own services doesn't work) ? Or is it something that can be done in the gateway? /Peter Lofman
Kannel as SMSC
Hello! I'm new to Kannel and would like to know if its possible to use Kannel as a real SMSC. Which means, that Kannel accepts UCP Connections(with login.. like any SMSC Kannel would normally connect to) and can then accept SMS via this connection and route those SMS to another SMSC. Like the HTTP incoming interface but with UCP. I haven't found anything in the docs. So maybe someone has allready implemented something like that? I think you only need to change the login method from creating a connection to listening for a connection and change the auth acordingly. or? Thanks for any Help Stefan Haubold YOC AG Dircksenstr. 47 10178 Berlin / Germany Tel: +49-30 72 61 62-411 Fax: +49-30 72 61 62-222 mail to: [EMAIL PROTECTED] visit us at: www.yoc.de / www.yoc-ag.de
OTA Truncation?
Hi - I posted a message here last week regarding bad OTA. I now have more info. Using the CVS from yesterday it looks like the PDU is getting truncated. Can anyone confirm this please or see what I'm doing wrong? Here is the XML I'm sending: ?xml version=1.0? !DOCTYPE CHARACTERISTIC-LIST SYSTEM file://gw/settings.dtd CHARACTERISTIC-LIST CHARACTERISTIC TYPE=ADDRESS PARM NAME=BEARER VALUE=GSM/CSD/ PARM NAME=PROXY VALUE=123.34.6.7/ PARM NAME=CSD_DIALSTRING VALUE=+45/ PARM NAME=PPP_AUTHTYPE VALUE=PAP/ /CHARACTERISTIC CHARACTERISTIC TYPE=URL VALUE= http://wap.dk / CHARACTERISTIC TYPE=NAME PARM NAME=NAME VALUE=ABC/ /CHARACTERISTIC CHARACTERISTIC TYPE=BOOKMARK PARM NAME=NAME VALUE=Wap/ PARM NAME=URL VALUE= http://wap.dk / /CHARACTERISTIC /CHARACTERISTIC-LIST Here is the bearerbox log (which looks ok): 2002-07-18 14:48:29 [3] INFO: smsbox: Got HTTP request /cgi-bin/sendota from 127.0.0.1 2002-07-18 14:48:29 [3] INFO: sendsms used by foo 2002-07-18 14:48:29 [3] DEBUG: OTA service with XML document 2002-07-18 14:48:29 [3] DEBUG: Octet string at 0x100cea98: 2002-07-18 14:48:29 [3] DEBUG: len: 158 2002-07-18 14:48:29 [3] DEBUG: size: 159 2002-07-18 14:48:29 [3] DEBUG: immutable: 0 2002-07-18 14:48:29 [3] DEBUG: data: 01 06 2c 1f 2a 61 70 70 ..,.*app 2002-07-18 14:48:29 [3] DEBUG: data: 6c 69 63 61 74 69 6f 6e lication 2002-07-18 14:48:29 [3] DEBUG: data: 2f 78 2d 77 61 70 2d 70 /x-wap-p 2002-07-18 14:48:29 [3] DEBUG: data: 72 6f 76 2e 62 72 6f 77 rov.brow 2002-07-18 14:48:29 [3] DEBUG: data: 73 65 72 2d 73 65 74 74 ser-sett 2002-07-18 14:48:29 [3] DEBUG: data: 69 6e 67 73 00 81 ea 01 ings 2002-07-18 14:48:29 [3] DEBUG: data: 01 6a 00 45 c6 06 01 87 .j.E 2002-07-18 14:48:29 [3] DEBUG: data: 12 45 01 87 13 11 03 31 .E.1 2002-07-18 14:48:29 [3] DEBUG: data: 32 33 2e 33 34 2e 36 2e 23.34.6. 2002-07-18 14:48:29 [3] DEBUG: data: 37 00 01 87 21 11 03 2b 7...!..+ 2002-07-18 14:48:29 [3] DEBUG: data: 34 35 00 01 87 22 70 01 45...p. 2002-07-18 14:48:29 [3] DEBUG: data: 01 86 07 11 03 20 68 74 . ht 2002-07-18 14:48:29 [3] DEBUG: data: 74 70 3a 2f 2f 77 61 70 tp://wap 2002-07-18 14:48:29 [3] DEBUG: data: 2e 64 6b 20 00 01 c6 08 .dk 2002-07-18 14:48:29 [3] DEBUG: data: 01 87 15 11 03 41 42 43 .ABC 2002-07-18 14:48:29 [3] DEBUG: data: 00 01 01 c6 7f 01 87 15 2002-07-18 14:48:29 [3] DEBUG: data: 11 03 57 61 70 00 01 87 ..Wap... 2002-07-18 14:48:29 [3] DEBUG: data: 17 11 03 20 68 74 74 70 ... http 2002-07-18 14:48:29 [3] DEBUG: data: 3a 2f 2f 77 61 70 2e 64 ://wap.d 2002-07-18 14:48:29 [3] DEBUG: data: 6b 20 00 01 01 01 k 2002-07-18 14:48:29 [3] DEBUG: Octet string dump ends. 2002-07-18 14:48:29 [3] INFO: /cgi-bin/sendota: XML request for target +44777xx x 2002-07-18 14:48:29 [3] DEBUG: Octet string at 0x100cea98: 2002-07-18 14:48:29 [3] DEBUG: len: 158 2002-07-18 14:48:29 [3] DEBUG: size: 159 2002-07-18 14:48:29 [3] DEBUG: immutable: 0 2002-07-18 14:48:29 [3] DEBUG: data: 01 06 2c 1f 2a 61 70 70 ..,.*app 2002-07-18 14:48:29 [3] DEBUG: data: 6c 69 63 61 74 69 6f 6e lication 2002-07-18 14:48:29 [3] DEBUG: data: 2f 78 2d 77 61 70 2d 70 /x-wap-p 2002-07-18 14:48:29 [3] DEBUG: data: 72 6f 76 2e 62 72 6f 77 rov.brow 2002-07-18 14:48:29 [3] DEBUG: data: 73 65 72 2d 73 65 74 74 ser-sett 2002-07-18 14:48:29 [3] DEBUG: data: 69 6e 67 73 00 81 ea 01 ings 2002-07-18 14:48:29 [3] DEBUG: data: 01 6a 00 45 c6 06 01 87 .j.E 2002-07-18 14:48:29 [3] DEBUG: data: 12 45 01 87 13 11 03 31 .E.1 2002-07-18 14:48:29 [3] DEBUG: data: 32 33 2e 33 34 2e 36 2e 23.34.6. 2002-07-18 14:48:29 [3] DEBUG: data: 37 00 01 87 21 11 03 2b 7...!..+ 2002-07-18 14:48:29 [3] DEBUG: data: 34 35 00 01 87 22 70 01 45...p. 2002-07-18 14:48:29 [3] DEBUG: data: 01 86 07 11 03 20 68 74 . ht 2002-07-18 14:48:29 [3] DEBUG: data: 74 70 3a 2f 2f 77 61 70 tp://wap 2002-07-18 14:48:29 [3] DEBUG: data: 2e 64 6b 20 00 01 c6 08 .dk 2002-07-18 14:48:29 [3] DEBUG: data: 01 87 15 11 03 41 42 43 .ABC 2002-07-18 14:48:29 [3] DEBUG: data: 00 01 01 c6 7f 01 87 15 2002-07-18 14:48:29 [3] DEBUG: data: 11 03 57 61 70 00 01 87 ..Wap... 2002-07-18 14:48:29 [3] DEBUG: data: 17 11 03 20 68 74 74 70 ... http 2002-07-18 14:48:29 [3] DEBUG: data: 3a 2f 2f 77 61 70 2e 64 ://wap.d 2002-07-18 14:48:29 [3] DEBUG: data: 6b 20 00 01 01 01 k 2002-07-18 14:48:29 [3] DEBUG: Octet string dump ends. 2002-07-18 14:48:29 [3] INFO: /cgi-bin/sendota default +447779xx 2002-07-18 14:48:29 [3] DEBUG: message length 158, sending 1 messages 2002-07-18 14:48:29 [3] DEBUG: Status: 202 Answer: Sent. Here is the smsbox log: 2002-07-18 14:48:29 [7] DEBUG: boxc_receiver: sms received 2002-07-18 14:48:30 [5] DEBUG: AT2[COM4]: international starting with + (+447779 x) 2002-07-18 14:48:30 [5] DEBUG: AT2[COM4]:
Sending MMS with kannel ...
Hi, I've just subscribed this mailing-list, so, what I have to ask could be in previous posts. I want to send MMS from Kannel to compliant MMS phones. I have a look to MMS specifications, so it seems there are 2 ways: a) M-send.request: sending MMS to MMSC Relay/server b) M-notification.ind: sending directly MMS to phone What's the best way? Is b) way correct? Case a) I suppose I must have a link to operator MMSC ... how can I use/configure kannel to communicate with operator MMSC ? Is this way for mobile users only or can I use kannel to communicate with operator MMSC? Case b) Are there any interoperability problems? I have found an example here: http://www.mail-archive.com/users@kannel.3glab.org/msg00972.html Is that correct? Does it work? Are there any mms-related news from may 7, 2002? A bit confused ... Enzo
Re: AW: AW: Phone as MMSC
On Thu, 2002-07-18 at 13:03, Stipe Tolj wrote: What we need is a reverse wapbox. something that listens for http and send wsp packets. This way I could point opie-konqueror to use pawbox (reverse wap) as a proxy and have a wml browser. konqueror supports wml. Something like fakewap, but with a http proxy listener hmmm, I didn't get the point. *clueless_scrumble* I have free gprs wap access but have to pay for data gprs ;) Anyway, a client like that could be useful to debug the gateway, that's why I've referred to fakewap. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Phone as MMSC
On Thu, 2002-07-18 at 13:06, Stipe Tolj wrote: Yes. You have a regular wap configuration plus one mms-url, wich contains the mmsc server's url. You just need to use your usual connection and point to your favorite mms-url. But I thing operators will block MMS traffic to other mmsc-urls. Why? Because they need to know how to charge for a MMS, and they can only charge if the MMS is processed by their own MMSC. I have seen Vodafone in D2 (which offer MMS since some time) do not use their regular WAP gateway for the proxying, but do use an dedicated one. So we could blast operators MMS revenue fantasies, if someone would put up a free MMSC with an public adressable mms-url, right? Yep. Just do your http-mms application and enable sar and mms notify in kannel and we'll have a mmsc. If we do content adaptation, like converting the incoming email with a 1024x768 png to a 101x80 gif when ericsson t68 accesses the mmsc, or wav to amr, and we'll have something much better that Ericsson :P Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [FYI] patch commited for 'allowed-receiver-prefix' insms-service groups
On Mon, 2002-07-15 at 13:24, Stipe Tolj wrote: I just commited a patch that allows to allow, deny routing of inbound messages based on the receiver numbers and their prefixes. This is very usefull if you have several shortcut numbers and want to allow only certain of them (let's say those that are related to premium sms traffic) to access a sms-service with a keyword. I think, and this has been discussed AFAIK some time ago, we should think about a message routing facility based on receiver numbers. Currently we do basicaly only route according to given keywords, hence the contents of the message. We'd like to route messages to specific URLTranslation based on receiver-numbers too. Any comments, objections?! Hei, there's already the allowed-prefix and denied-prefix on sms-services group, I've done that a long time ago. I'm using it like: group = sms-service keyword = xpto allowed-prefix = 91 text = Hello vodafone group = sms-service keyword = xpto allowed-prefix = 93;96 text = Hello others Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: R: Siemens M35
On Thu, 2002-07-11 at 13:29, Stefano Baronio wrote: Stefano Baronio wrote: For whoever may be interested I got a Siemens M35i mobile phone (M20 family I think) working with kannel 1.2. Jus add an init-string in the modems group init-string = AT+CNMI=1,2,0,0,1 Sorry, forgot to specify that: 1- at2 driver used. 2- speed must be set to 19200 Stefano Baronio could you send me the ATI result or the modems.conf group ?
kannel 1.2.0 and SMPP v3.3
Does anybody know what SMSC returned error code 0x000a in response to submit_sm means, using kannel 1.2.0 and connecting to a SMPP SMSC v3.3 in transmitter mode. BR Arnar
Re: Sending MMS with kannel ...
Enzo dell'Aquila kirjoittaa torstaina, 18. heinäkuuta 2002, kello 17:44:Hi, I've just subscribed this mailing-list, so, what I have to ask could be in previous posts. I want to send MMS from Kannel to compliant MMS phones. I have a look to MMS specifications, so it seems there are 2 ways: a) M-send.request: sending MMS to MMSC Relay/server b) M-notification.ind: sending directly MMS to phone What's the best way? Is b) way correct? B) is OK. Case a) I suppose I must have a link to operator MMSC ... how can I use/configure kannel to communicate with operator MMSC ? Is this way for mobile users only or can I use kannel to communicate with operator MMSC? MMSCs does the communicating to the other MMSCs. But protocols are SMTP and IMAP. But does operators let you in, is another matter. Case b) Are there any interoperability problems? No, because all phones must understand notification, otherwise they do not fetch the message from the center. I have found an example here: http://www.mail-archive.com/users@kannel.3glab.org/msg00972.html This should work (have tested it). A
Re: OTA Truncation?
Aarno Syvänen kirjoittaa perjantaina, 19. heinäkuuta 2002, kello 08:06:[EMAIL PROTECTED] kirjoittaa torstaina, 18. heinäkuuta 2002, kello 17:20:Hi - I posted a message here last week regarding bad OTA. I now have more info. Using the CVS from yesterday it looks like the PDU is getting truncated. Can anyone confirm this please or see what I'm doing wrong? 2002-07-18 14:48:29 [3] DEBUG: message length 158, sending 1 messages 2002-07-18 14:48:29 [3] DEBUG: Status: 202 Answer: Sent. Sending 158 binary octets in one message is certainly wrong, the message should be segmented. This looks to me like the message is just cut off after the Wap string!!! If all octets does not fit in one message, and there are no segmentation, leftover octets are cut. System is Cygwin, sending with Ericsson R320 as SMSC using AT2, reciever is T68i. Anyone please!!! (I'm quite new to this so please don't assume I can see the obvious ;-)) Perhaps you can correct the segmentation ? This should not be too much work, the code is already available, you must just call it. A
