SV: TC-35 Startup
Hi Thomas, I have similar problems and mine comes down to two issues. First the /dev/ttyS0 have root.tty as owner, so the user you are trying with need to have the right premissions. I overcome this (at this moment, because its only a test box) by running kannel as root. I tried this morning to reboot the box and the start kannel, but got the log as you write here, I started minicom and tried to isue some at commands directly to the phone modem and it responde like it should. After closing down minicom I had no problem starting kannel. So the modem might be in a strangs state that kannel can not get it out of (I guess its a bug). regards Steffen -Oprindelig meddelelse- Fra: Tampier Thomas [mailto:[EMAIL PROTECTED]] Sendt: 19. juni 2002 00:43 Til: [EMAIL PROTECTED] Emne: TC-35 Startup Hi list, i have troubles starting my Siemens TC35. Every time i try to start the bearerbox i get this log (i tried all possible configurations in kannel.conf, its always the same) --> any ideas? thx for your help Thomas 2002-06-19 00:38:30 [5] INFO: AT2[/dev/ttyS0]: speed set to 19200 2002-06-19 00:38:30 [5] DEBUG: AT2[/dev/ttyS0]: --> ^M 2002-06-19 00:38:32 [5] DEBUG: AT2[/dev/ttyS0]: --> AT^M 2002-06-19 00:38:36 [5] DEBUG: AT2[/dev/ttyS0]: --> AT^M 2002-06-19 00:38:40 [5] DEBUG: AT2[/dev/ttyS0]: -->AT^M 2002-06-19 00:38:44 [5] INFO: AT2[/dev/ttyS0]: closing device 2002-06-19 00:38:44 [5] INFO: AT2[/dev/ttyS0]: opening device 2002-06-19 00:38:44 [5] DEBUG: AT2[/dev/ttyS0]: device opened 2002-06-19 00:38:44 [5] INFO: AT2[/dev/ttyS0]: speed set to 9600 2002-06-19 00:38:44 [5] DEBUG: AT2[/dev/ttyS0]: --> ^M 2002-06-19 00:38:46 [5] DEBUG: AT2[/dev/ttyS0]: --> AT^M 2002-06-19 00:38:50 [5] DEBUG: AT2[/dev/ttyS0]: --> AT^M 2002-06-19 00:38:54 [5] DEBUG: AT2[/dev/ttyS0]: --> AT^M 2002-06-19 00:38:58 [5] INFO: AT2[/dev/ttyS0]: closing device 2002-06-19 00:38:58 [5] INFO: AT2[/dev/ttyS0]: cannot detect speed 2002-06-19 00:38:58 [5] DEBUG: Thread 5 (gw/smsc_at2.c:at2_device_thread) terminates.
Re: MMS and Kannel
Hello there Diogo, long time no see :-) There are efforts to put kannel PPG and wap gateway to interact with MMSC, althoug i suppose is under [alpha] development (maybe you can give a hand here ;) ) You can find answers to your questions in devel mailing list archive: http://www.mail-archive.com/cgi-bin/htsearch?method=and&format=short&config=devel_kannel_3glab_org&restrict=&exclude=&words=MMS http://www.mail-archive.com/devel@kannel.3glab.org/ http://www.mail-archive.com/users@kannel.3glab.org/ stay k00l /valter On Mon, 2002-06-17 at 17:58, [EMAIL PROTECTED] wrote: > Hi > > Is it possible to send MMS messages with Kannel? I've worked with Kannel > before, and i would like to know if it supports MMS and how can i use it > (i haven't found any post with that subject). > > Thank you > > Diogo Calvário
TC-35 Startup
Hi list, i have troubles starting my Siemens TC35. Every time i try to start the bearerbox i get this log (i tried all possible configurations in kannel.conf, its always the same) --> any ideas? thx for your help Thomas 2002-06-19 00:38:30 [5] INFO: AT2[/dev/ttyS0]: speed set to 19200 2002-06-19 00:38:30 [5] DEBUG: AT2[/dev/ttyS0]: --> ^M 2002-06-19 00:38:32 [5] DEBUG: AT2[/dev/ttyS0]: --> AT^M 2002-06-19 00:38:36 [5] DEBUG: AT2[/dev/ttyS0]: --> AT^M 2002-06-19 00:38:40 [5] DEBUG: AT2[/dev/ttyS0]: -->AT^M 2002-06-19 00:38:44 [5] INFO: AT2[/dev/ttyS0]: closing device 2002-06-19 00:38:44 [5] INFO: AT2[/dev/ttyS0]: opening device 2002-06-19 00:38:44 [5] DEBUG: AT2[/dev/ttyS0]: device opened 2002-06-19 00:38:44 [5] INFO: AT2[/dev/ttyS0]: speed set to 9600 2002-06-19 00:38:44 [5] DEBUG: AT2[/dev/ttyS0]: --> ^M 2002-06-19 00:38:46 [5] DEBUG: AT2[/dev/ttyS0]: --> AT^M 2002-06-19 00:38:50 [5] DEBUG: AT2[/dev/ttyS0]: --> AT^M 2002-06-19 00:38:54 [5] DEBUG: AT2[/dev/ttyS0]: --> AT^M 2002-06-19 00:38:58 [5] INFO: AT2[/dev/ttyS0]: closing device 2002-06-19 00:38:58 [5] INFO: AT2[/dev/ttyS0]: cannot detect speed 2002-06-19 00:38:58 [5] DEBUG: Thread 5 (gw/smsc_at2.c:at2_device_thread) terminates.
RE: sms.coding choice in smsbox (SMPP smsc)
This shouldn't work (nor should it have worked in 1.1.4 - if it did then that was a bug) as in addition to hard setting (in a non comaptible way) the coding type for a PDU, you must make sure your message is formatted according to the chosen character set - which currently it isn't as messages delivered are formatted either for 8 bit, 7 bit or unicode. As an ugly hack, you can hardcode the data_coding pdu parameter, then send messages to the smsbox, using send-sms, in the target character set but don't set the charset parameter, and set coding to 2. this way Kannel will not transcode the message and it will be delivered as is to the driver. -- Oded Arbel m-Wise Mobile Solutions [EMAIL PROTECTED] Mobile: +972-67-340014 Tel: +972-9-9581711 (ext: 116) ::.. How much wood could a woodchuck chuck if a woodchuck could chuck wood? > -Original Message- > From: Arne K. Haaje [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, June 18, 2002 3:03 PM > To: [EMAIL PROTECTED] > Subject: Re: sms.coding choice in smsbox (SMPP smsc) > > > On Tuesday 18 June 2002 14:40, Oded Arbel wrote: > > SMPP v3.4 support many character set delivery types but > SMPP v3.3 doesn't, > > and the way the SMPP driver in kannel is written, it > supports only the v3.3 > > style of character coding which limits us to GSM 03.38 > (7bit), iso-8859-1 > > (8bit) or UCS-2 (unicode). Changing the SMPP implementation > to support the > > v3.4 supported charsets is on my todo list, but it wouldn't > help any as > > Kannel does not currently have an infrastructure to support arbitary > > chracter sets (or just anything besides the 3 coding styles). > > > > Currently to send anything other the ISO-8859-1 on SMPP you > need to either > > deliver everything in unicode (UCS-2) or to hack the driver > to support your > > specific charset. > > In 1.1.4 you could put > > pdu->u.submit_sm.data_coding = 0xf5; > > in smsc_smpp.c > > I am no C guru, but I tried putting this in the version from > the latest > snapshot (which has changed a bit..). It does'nt seem to > work, as I get no > messages through. > > Any ideas on where I should hardcode the driver to use 0xf5 > as the coding? > > Regards, > > Arne > -- > > Arne K. Haaje | T: 69 92 04 90 > Bregneveien 9 | F: 69 92 04 91 > 1625 Tomter | M: 92 88 44 66 > > > >
Tariff tag of outgoing SMS
Sorry all, I changed subject. "Re: Using Service Description in CIMD2" Unfortunately haven´t I work with Kannel so I have no clue where to look. If someone point me in the right direction, I probably could enable tariff taging of SMS, delivered over CIMD2 protocol. Has anyone added some logic to enable billing on outgoing SMS from Kannel? How did you do it? If not, how do you perform billing? problems: I will probably need support for Tafiff tag over SMPP (3.4) also, a general solution would be nice. Thou I haven´t found anyway tariff tag i SMPP :) Thanks! Tobias Shridhar Raju wrote: > If u r familiar with C & kannel architecture, then u can change/add code of > kannel to suit ur requirement. The tariff class parametrer can be added in > CIMD packet using cgi parameter of sendsms of smsbox. I did it for something > else, and its working fine for me. > > Shridhar Raju > > - Original Message - > From: "Tobias Höglund" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, June 18, 2002 12:52 PM > Subject: Using Service Description in CIMD2 > > > >>Hi all. >> >>To enable billing of a SMS reciever I want to set the Tariff class tag(64) >>and maybe Service Description(65) in CIMD2 to a given value. >> >>1: Can I do this with Kannel, specify the tariff tag on a outgoing SMS? >>Cant find anything in the documents, nore maillists. :( >> >>2: Can I use HTTP sendsms also to set tariff tag? If not, any suggestions >> on how to do this? >> >> >>Regards Tobias >> > > >
Re: sms.coding choice in smsbox (SMPP smsc)
On Tuesday 18 June 2002 14:40, Oded Arbel wrote: > SMPP v3.4 support many character set delivery types but SMPP v3.3 doesn't, > and the way the SMPP driver in kannel is written, it supports only the v3.3 > style of character coding which limits us to GSM 03.38 (7bit), iso-8859-1 > (8bit) or UCS-2 (unicode). Changing the SMPP implementation to support the > v3.4 supported charsets is on my todo list, but it wouldn't help any as > Kannel does not currently have an infrastructure to support arbitary > chracter sets (or just anything besides the 3 coding styles). > > Currently to send anything other the ISO-8859-1 on SMPP you need to either > deliver everything in unicode (UCS-2) or to hack the driver to support your > specific charset. In 1.1.4 you could put pdu->u.submit_sm.data_coding = 0xf5; in smsc_smpp.c I am no C guru, but I tried putting this in the version from the latest snapshot (which has changed a bit..). It does'nt seem to work, as I get no messages through. Any ideas on where I should hardcode the driver to use 0xf5 as the coding? Regards, Arne -- Arne K. Haaje | T: 69 92 04 90 Bregneveien 9 | F: 69 92 04 91 1625 Tomter | M: 92 88 44 66
RE: sms.coding choice in smsbox (SMPP smsc)
SMPP v3.4 support many character set delivery types but SMPP v3.3 doesn't, and the way the SMPP driver in kannel is written, it supports only the v3.3 style of character coding which limits us to GSM 03.38 (7bit), iso-8859-1 (8bit) or UCS-2 (unicode). Changing the SMPP implementation to support the v3.4 supported charsets is on my todo list, but it wouldn't help any as Kannel does not currently have an infrastructure to support arbitary chracter sets (or just anything besides the 3 coding styles). Currently to send anything other the ISO-8859-1 on SMPP you need to either deliver everything in unicode (UCS-2) or to hack the driver to support your specific charset. -- Oded Arbel m-Wise Mobile Solutions [EMAIL PROTECTED] Mobile: +972-67-340014 Tel: +972-9-9581711 (ext: 116) ::.. Ask five economists and you'll get five different explanations (six if one went to Harvard). > -Original Message- > From: Arne K. Haaje [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, June 18, 2002 1:41 PM > To: [EMAIL PROTECTED] > Subject: Re: sms.coding choice in smsbox (SMPP smsc) > > > On Tuesday 18 June 2002 13:17, Oded Arbel wrote: > > coding is set per message, in the send-sms call. if unset, > it is set to > > undef by default. > > How do I set this for the Spanish Operator Vodafone/Airtel in > the latest > version? I think they need the coding 0xf5, but I see no way > to specify this. > > Regards, > > Arne > >
Re: MMS and Kannel
Hello there Diogo, long time no see :-) There are efforts to put kannel PPG and wap gateway to interact with MMSC, althoug i suppose is under [alpha] development (maybe you can give a hand here ;) ) You can find answers to your questions in devel mailing list archive: http://www.mail-archive.com/cgi-bin/htsearch?method=and&format=short&config=devel_kannel_3glab_org&restrict=&exclude=&words=MMS http://www.mail-archive.com/devel@kannel.3glab.org/ http://www.mail-archive.com/users@kannel.3glab.org/ stay k00l /valter On Mon, 2002-06-17 at 17:58, [EMAIL PROTECTED] wrote: > Hi > > Is it possible to send MMS messages with Kannel? I've worked with Kannel > before, and i would like to know if it supports MMS and how can i use it > (i haven't found any post with that subject). > > Thank you > > Diogo Calvário
RE: Siemens M20 stops receiving sms
Setting the keepalive did not help... I have now tried the setup with ericsson t39 and that is working perfectly. If I receive many messages, will the phone get full?? /Peter Lofman > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of Bruno > David Rodrigues > Sent: den 17 juni 2002 14:28 > To: Andrea Trasatti > Cc: [EMAIL PROTECTED] > Subject: RE: Siemens M20 stops receiving sms > > > On Mon, 2002-06-17 at 09:19, Andrea Trasatti wrote: > > Hello, > > are you sure it's a problem with Kannel and not with the M20? > > > > How often do you get SMS messages on it? We have *2* M20 here and we > > experienced a similar problem VERY often. It seems like if > the phone doesn't receive > > SMS messages for a while and the server resets it, the > phone will just go in some > > limbo state. It looks like it's alive, but whatever you try > to do, it fails. It doesn't receive > > messages anymore and if you try to send any, it will give > you a network error, as if > > the cell had rejected the message or something. Turn the > phone off and back on and > > it'll restart working. > > I did have that problem too. M20 stopped receiving messages. > I don't send anything through it. > > Try to add keepalive: > keepalive = 60 > keepalive-cmd = "AT+CBC;+CSQ" > > Then watch the values > > --> AT+CBC;+CSQ^M > <-- +CBC: 1,100 > <-- +CSQ: 16,0 > > CBC= on power, 100 batery > CSQ= signal 16 (see 3gpp-27007 or 27005) >
Re: sms.coding choice in smsbox (SMPP smsc)
On Tuesday 18 June 2002 13:17, Oded Arbel wrote: > coding is set per message, in the send-sms call. if unset, it is set to > undef by default. How do I set this for the Spanish Operator Vodafone/Airtel in the latest version? I think they need the coding 0xf5, but I see no way to specify this. Regards, Arne
Re: Using Service Description in CIMD2
If u r familiar with C & kannel architecture, then u can change/add code of kannel to suit ur requirement. The tariff class parametrer can be added in CIMD packet using cgi parameter of sendsms of smsbox. I did it for something else, and its working fine for me. Shridhar Raju - Original Message - From: "Tobias Höglund" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, June 18, 2002 12:52 PM Subject: Using Service Description in CIMD2 > Hi all. > > To enable billing of a SMS reciever I want to set the Tariff class tag(64) > and maybe Service Description(65) in CIMD2 to a given value. > > 1: Can I do this with Kannel, specify the tariff tag on a outgoing SMS? > Cant find anything in the documents, nore maillists. :( > > 2: Can I use HTTP sendsms also to set tariff tag? If not, any suggestions >on how to do this? > > > Regards Tobias >
RE: sms.coding choice in smsbox (SMPP smsc)
coding is set per message, in the send-sms call. if unset, it is set to undef by default. -- Oded Arbel m-Wise Mobile Solutions [EMAIL PROTECTED] Mobile: +972-67-340014 Tel: +972-9-9581711 (ext: 116) ::.. "Even the AI hated [my book]?" "The AI _loved_ it. That's when we knew for sure that _people_ were going to hate it." -- Dan Simmons, "Hyperion" > -Original Message- > From: yuryx [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, June 18, 2002 1:20 PM > To: [EMAIL PROTECTED] > Subject: sms.coding choice in smsbox (SMPP smsc) > > > Hi all! > Can anyone help me with choice sms.coding parameter in msg > (I'm just use > SMPP smsc) > May be set this parameter in smsboxkannel.conf (if that possible)? > I use kannel-1.1.6 version > > Thanx. > Yury. > > > >
sms.coding choice in smsbox (SMPP smsc)
Hi all! Can anyone help me with choice sms.coding parameter in msg (I'm just use SMPP smsc) May be set this parameter in smsboxkannel.conf (if that possible)? I use kannel-1.1.6 version Thanx. Yury.
RE: Date incoherence for MO
The date Kannel is reporting, is the time stamp received in the message itself. this time stamp is usually generated by the SMSC from which the message originated, and it may not be (it usually isn't) the same time as the time that Kannel received the message. some time it may not even be in the same time zone. If Kannel can convert the time stamp, reliably, to the local time zone, it does so. else it reports it as it sees it. many protocols do not define a method for detecting the original time zone, and many implementations of protocols that do define such a method are broken, hence that time stamp will usually not be very useful to you, as it only means what the originating SMSC thinks the delivery time is. -- Oded Arbel m-Wise Mobile Solutions [EMAIL PROTECTED] Mobile: +972-67-340014 Tel: +972-9-9581711 (ext: 116) ::.. Q: How many Microsoft technicians does it take to change a light bulb? A: Three. Two holding the ladder, and one to screw the bulb into the faucet. > -Original Message- > From: Michael Tung [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, June 18, 2002 8:58 AM > To: [EMAIL PROTECTED] > Subject: Date incoherence for MO > > > Dear all, > > > I previously mentioned that the date and time (%t) for > MO is following GMT standard. I think I am wrong, as > when I'm looking at my database I see that its incoherent : > > Actual Date MO Received : 6/14/2002 10:17:34 AM > Kannel Reported : 7/14/2002 2:03:57 AM > > Actual Date MO Received : 6/18/2002 1:29:20 AM > Kannel Reported : 7/2/2002 1:36:37 AM > > Does anyone have an idea of what's going on? > I'm using Redhat 7.0 and Kannel 1.1.6 (not CSV) > > > -- > Michael Tung @ Work > [Product Manager] > [EMAIL PROTECTED] > > mobileExec (M) Sdn Bhd (557748-X) > 4th Floor, Wisma RA > 12 Jalan Dang Wangi > 50100 Kuala Lumpur > Malaysia > > Mob: +60 (13) 351 1100 > Tel: +60 (3) 2693 5001 > Fax: +60 (3) 2693 5007 > Help Desk: +60 (3) 2691 7001 > > Get ahead, go mobile at www.mobileExec.net > Visit our e-community for executives at www.asianExec.com > -- > > > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.370 / Virus Database: 205 - Release Date: 6/5/2002 > > >
RE: SMPP configuration
If not, then they should. -- Oded Arbel m-Wise Mobile Solutions [EMAIL PROTECTED] Mobile: +972-67-340014 Tel: +972-9-9581711 (ext: 116) ::.. "You fall out of your mother's womb, you crawl across open country under fire, and drop into your grave." --Quentin Crisp > -Original Message- > From: Mauricio Ramos [mailto:[EMAIL PROTECTED]] > Sent: Monday, June 17, 2002 11:39 PM > To: Oded Arbel; [EMAIL PROTECTED] > Subject: RE: SMPP configuration > > > > Interesting, I also need this. > > For curiosity, this new feature and other new ones are being > documented in > userguide? > > -Original Message- > From: Oded Arbel [mailto:[EMAIL PROTECTED]] > Sent: quinta-feira, 6 de junho de 2002 06:23 > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: RE: SMPP configuration > > > Latest CVS version of kannel support the setting of TON and > NPI for SMPP > using the folowing configuration options in the smsc group : > source-addr-ton > source-addr-npi > dest-addr-ton > dest-addr-npi > > -- > Oded Arbel > m-Wise Inc. > [EMAIL PROTECTED] > (972)-67-340014 > (972)-9-9581711 (ext: 116) > > ::.. > X windows: > THE user interference management system. > > > > -Original Message- > > From: world2web [Matthias Fraccaro] [mailto:[EMAIL PROTECTED]] > > Sent: Wednesday, June 05, 2002 9:42 PM > > To: [EMAIL PROTECTED] > > Subject: SMPP configuration > > Importance: High > > > > > > Hello, > > > > where can I define the parameters below: > > > > TON=1, NPI=1, ADDR="999 Sender:999 > > TON=0,NPI=9, ADDR="999" sender in international format > > TON=5,NPI=1, ADDR="XXX" Sender:XXX alphanumeric originator > > > > > > Best regards > > Matthias Fraccaro > > > > > > >
Need help : Modify SEMA OIS 2000 protocol
Dear all, I need some help as the SMSC I need to be connecting to has perverted the OIS 2000 protocol slightly. The only difference is when a connection is first established, it requires an authentication (username/password) to be sent. After that the OIS 2000 standard is the same. Could somebody help me to point out exactly which class file I should be looking at? I have been looking but it looks like a jungle in there. -- Michael Tung @ Work [Product Manager] [EMAIL PROTECTED] mobileExec (M) Sdn Bhd (557748-X) 4th Floor, Wisma RA 12 Jalan Dang Wangi 50100 Kuala Lumpur Malaysia Mob: +60 (13) 351 1100 Tel: +60 (3) 2693 5001 Fax: +60 (3) 2693 5007 Help Desk: +60 (3) 2691 7001 Get ahead, go mobile at www.mobileExec.net Visit our e-community for executives at www.asianExec.com -- --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.370 / Virus Database: 205 - Release Date: 6/5/2002
