Patch to turn off CRTSCTS
We have an old Ericsson GM12 with a custom-made serial cable that does
not have the control signals wired. When running Kannel 1.2.0, no
communications occurs. Turning off hardware flow control helps.
Attached is a patch against Kannel 1.2.0 that add an extra directive to
the modems group (disable-crtscts). Might help some people.
Regards,
Eric Yeo
Only in gateway-1.2.0-ttey/doc/alligata: alligata.tex
Only in gateway-1.2.0-ttey/doc/alligata: alligata.tmp
diff -r -c gateway-1.2.0/gw/smsc_at2.c gateway-1.2.0-ttey/gw/smsc_at2.c
*** gateway-1.2.0/gw/smsc_at2.c Tue May 14 09:57:36 2002
--- gateway-1.2.0-ttey/gw/smsc_at2.c Fri Jul 12 15:01:54 2002
***
*** 82,87
--- 82,91
tios.c_cflag |= CRTSCTS; /* enable hardware flow control */
tios.c_cc[VSUSP] = 0; /* otherwhise we can not send CTRL Z */
+ if (privdata->modem->disable_crtscts) {
+ tios.c_cflag &= ~CRTSCTS; /* disable hardware flow control */
+ }
+
/*
if ( ModemTypes[privdata->modemid].enable_parity )
tios.c_cflag ^= PARODD;
***
*** 2033,2038
--- 2037,2044
modem->speed = 9600;
cfg_get_integer(&modem->speed, grp, octstr_imm("speed"));
+ cfg_get_bool(&modem->disable_crtscts, grp, octstr_imm("disable-crtscts"));
+
cfg_get_bool(&modem->need_sleep, grp, octstr_imm("need-sleep"));
modem->enable_hwhs = cfg_get(grp, octstr_imm("enable-hwhs"));
diff -r -c gateway-1.2.0/gw/smsc_at2.h gateway-1.2.0-ttey/gw/smsc_at2.h
*** gateway-1.2.0/gw/smsc_at2.h Thu Apr 11 12:46:42 2002
--- gateway-1.2.0-ttey/gw/smsc_at2.h Fri Jul 12 14:50:30 2002
***
*** 54,59
--- 54,60
int broken;
Octstr *message_storage;
int enable_mms;
+ int disable_crtscts;
} ModemDef;
typedef struct PrivAT2data {
diff -r -c gateway-1.2.0/gwlib/cfg.def gateway-1.2.0-ttey/gwlib/cfg.def
*** gateway-1.2.0/gwlib/cfg.def Tue Jun 25 20:32:06 2002
--- gateway-1.2.0-ttey/gwlib/cfg.def Fri Jul 12 14:52:50 2002
***
*** 326,331
--- 326,332
OCTSTR(init-string)
OCTSTR(speed)
OCTSTR(enable-hwhs)
+ OCTSTR(disable-crtscts)
OCTSTR(need-sleep)
OCTSTR(no-pin)
OCTSTR(no-smsc)
Re: AW: patch
I can comment more on how Hong Kong does Ported Numbers support. As Andreas stated, all the routing is done through SS7..but not the queries. Each operator (mobile [MNO] and fixed-line [FTN]) keeps track of which phone numbers are under their jurisdiction. They then forward the information to all the other operators every 12 hours. This info is incorporated into their backup databse and then pushed out to their production database. As a result, queries are done on the local database, eliminating the load on the SS7 network. The OFfice of Telecommication Authority (OFTA) stipulated that the Ported Numbers database must be available to each operator. But there's no requirement to provide this information to non-operators. In addition, each operator claims their number database is their intellectual property. As a result, it's next to impossible to acquire the complete database unless: (1) your a licensed local operator (2) you have a number database of your own that you can share Operators do not sell the database to anyone. But, they will let you query their backup database for a FEE ($0.05 HKD per query was my cheapest quote). Some of the operators provide an SS7 query service (fast but usually only available to the international long distance [IDD] operators) and/or HTTP queries (slow and no guarantee of minimal response time). All the operators ban resale of the information queried from their database. For IDD operators that can't gain query access from a cheaper local operator with a number database, they are forced to get the service from the very expensive registry kept by PCCW (formerly Hong Kong Telecom). I would not be surprised if other countries implement the same senario. My advice would be to get VERY friendly with operator providing you with your access to their SMSC. They must have access to the Ported Numbers database for the SMS's destination country. Be ready to pay a fee and don't forget to cache your queries. See ya... d.c. **>From: Andreas Fink <[EMAIL PROTECTED]> **>Subject: Re: AW: patch **>Date: Thu, 11 Jul 2002 14:10:50 +0200 **> **>>Andreas Fink wrote: **>>> **>>> This is country specific. One possibility is to look up all network's **>>> HLR record to find which one responds to that number but its kinda **>>> tricky and only useful if done from a SMSC level (SS7). **>> **>>which is currently not possible for most of us Kannel production users **>>here, right?! **> **> **>Right. Without SS7 access, you wont be able to do it. **>If there's enough demand for this we could offer that as a service to **>the Kannel community. **> **> **>>I have read something about a law regulation at least for the german **>>"Regulierungsbeh?rde", but I don't remember if they suggested **>>something like an open MSISDN <-> Carrier query server. **> **>what I've seen from a case in Hongkong, they always do it in SS7 **>because mobile switches rely on those number lookup features. However **>the source of the information is always coming from some centralized **>/ decentralized synchronized database which all the carriers share in **>some way. Of course the people who have access directly to that **>database can use it this way without SS7 but then again, its country **>specific while the SS7 solution is not. **> **>-- **> **>Andreas Fink **>Fink-Consulting **> **>-- **>Tel: +41-61-6932730 Fax: +41-61-6932729 Mobile: +41-79-2457333 **>Address: A. Fink, Schwarzwaldallee 16, 4058 Basel, Switzerland **>E-Mail: [EMAIL PROTECTED] Homepage: http://www.finkconsulting.com **>-- **>Something urgent? Try http://www.smsrelay.com/ Nickname afink **>
RE: originating address (ID:023)
Hi, the SMSC I use also supports the 23 option (via cimd2 interface). If you look trough the source code of the cimd2 interface (gateway/gw/smsc_cimd2.c), you can see that Kannel doesn't support this option at all. Best regards, Christophe Pannon GSM > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of Rolf Froysa > Sent: Thursday, July 11, 2002 12:38 PM > To: Oded Arbel > Cc: [EMAIL PROTECTED] > Subject: Re: originating address (ID:023) > > > I`ve tried various configurations: > > unified-prefix = "02" > sender-prefix = "03" > global-sender = "04" > faked-sender = "05" > > I`ve tried to set the from/sender field using the http based smssend. > > It looks like kannel ignores it when sending to the smsc. > > Here is a trace from one of the smsc`s where you can see a > complete message with field 23 set. And a kannel message > without field 23: > > Printified Data received: > [@@03:227@021:4792444342@030:0@056:38@023:02@033:smsmessage > with field 23 (not kannel) Printified Data received: > [@03:005@021:4745257287@056:0@033:smsmessage > without field 23 (kannel) > > Is there any way to enable this kind of trace or debugging > within kannel? > > Vennlig hilsen > > Rolf Frøysa > > > Oded Arbel wrote: > > > > Rolf Frøysa wrote: > > > > >I`ve setup kannel for demonstration and it seems to work > great. The > > >only thing is that I would like to change the originating address > > >based on the sms-service. Is this possible? In Norway, the smsc > > >providers are using the originating address (field 23) for billing > > >codes. > > > > > >Sincerly > > > > > >Rolf Frøysa > > > > > > > > > > > I don't think you can do this based on the sms-service (or > maybe you > > can > > - check forced-sender and global-sender in the userguide- I don't > > remember whether those pertain to sms-service), but in your > application > > you can set the "from" X-Kannel header to set the sender in > the returned > > MT, or the sender paremeter in the send-sms call for a push MT. > > > > -- > > Oded Arbel > > m-Wise mobile solutions > > > >
Re: originating address (ID:023)
I`ve tried various configurations: unified-prefix = "02" sender-prefix = "03" global-sender = "04" faked-sender = "05" I`ve tried to set the from/sender field using the http based smssend. It looks like kannel ignores it when sending to the smsc. Here is a trace from one of the smsc`s where you can see a complete message with field 23 set. And a kannel message without field 23: Printified Data received: [@@03:227@021:4792444342@030:0@056:38@023:02@033:smsmessage with field 23 (not kannel) Printified Data received: [@03:005@021:4745257287@056:0@033:smsmessage without field 23 (kannel) Is there any way to enable this kind of trace or debugging within kannel? Vennlig hilsen Rolf Frøysa Oded Arbel wrote: > > Rolf Frøysa wrote: > > >I`ve setup kannel for demonstration and it seems to work great. The only > >thing is that I would like to change the originating address based on > >the sms-service. Is this possible? In Norway, the smsc providers are > >using the originating address (field 23) for billing codes. > > > >Sincerly > > > >Rolf Frøysa > > > > > > > I don't think you can do this based on the sms-service (or maybe you can > - check forced-sender and global-sender in the userguide- I don't > remember whether those pertain to sms-service), but in your application > you can set the "from" X-Kannel header to set the sender in the returned > MT, or the sender paremeter in the send-sms call for a push MT. > > -- > Oded Arbel > m-Wise mobile solutions
Re: Send SMS Problem
Tampier Thomas wrote: >Hi list > >my kannel is unstabke in terms of send sms from php srcipts.. my scripts >are called by a sms-service from kannel and i use "echo" to reply to the >SMS-Devices... My problem is, that each time i try to send a sms i get an >ERROR -> and sometimes the SMS is sent, sometimes not. I use a Siemens >TC35 as SMS center. i use cvs-20020618 version of kannel. >does anybody know whats the problem? > >thx in advance >T > >2002-07-10 21:51:44 [5] DEBUG: AT2[/dev/ttyS0]: <-- +CMT: ,23 >2002-07-10 21:51:44 [5] DEBUG: AT2[/dev/ttyS0]: <-- >069134660405F1040C9134663419289620700112544348044AB55A0D >2002-07-10 21:51:44 [5] DEBUG: AT2[/dev/ttyS0]: >Numeric sender (international) <+436643918269> >2002-07-10 21:51:44 [5] DEBUG: AT2[/dev/ttyS0]: --> AT+CNMA^M >2002-07-10 21:51:44 [8] DEBUG: boxc_sender: sent message to <127.0.0.1> >2002-07-10 21:51:44 [7] DEBUG: boxc_receiver: got ack >2002-07-10 21:51:44 [7] DEBUG: boxc_receiver: sms received >2002-07-10 21:51:44 [5] DEBUG: AT2[/dev/ttyS0]: <-- OK >2002-07-10 21:51:44 [5] DEBUG: AT2[/dev/ttyS0]: international starting with + >(+436643918269) >2002-07-10 21:51:44 [5] DEBUG: AT2[/dev/ttyS0]: TP-Validity-Period: 24.0 hours >2002-07-10 21:51:44 [5] DEBUG: AT2[/dev/ttyS0]: --> AT+CMGS=38^M >2002-07-10 21:51:44 [5] DEBUG: AT2[/dev/ttyS0]: <-- > >2002-07-10 21:51:44 [5] DEBUG: AT2[/dev/ttyS0]: send command status: 1 >2002-07-10 21:51:44 [5] DEBUG: AT2[/dev/ttyS0]: --> >0011000C91346634192896A71BC2349D5E06C9CBE7F49C2E4F97E56537689A2E83E6E9311A >2002-07-10 21:51:44 [5] DEBUG: AT2[/dev/ttyS0]: --> ^Z >2002-07-10 21:51:45 [5] DEBUG: AT2[/dev/ttyS0]: <-- > >2002-07-10 21:51:45 [5] DEBUG: AT2[/dev/ttyS0]: <-- ERROR >2002-07-10 21:51:45 [5] DEBUG: AT2[/dev/ttyS0]: send command status: -1 >2002-07-10 21:51:45 [5] DEBUG: AT2[/dev/ttyS0]: --> AT+CMGS=38^M >2002-07-10 21:51:45 [5] DEBUG: AT2[/dev/ttyS0]: <-- > >2002-07-10 21:51:45 [5] DEBUG: AT2[/dev/ttyS0]: send command status: 1 >2002-07-10 21:51:45 [5] DEBUG: AT2[/dev/ttyS0]: --> >0011000C91346634192896A71BC2349D5E06C9CBE7F49C2E4F97E56537689A2E83E6E9311A >2002-07-10 21:51:45 [5] DEBUG: AT2[/dev/ttyS0]: --> ^Z >2002-07-10 21:51:48 [5] DEBUG: AT2[/dev/ttyS0]: <-- > >2002-07-10 21:51:48 [5] DEBUG: AT2[/dev/ttyS0]: <-- +CMGS: 140 >2002-07-10 21:51:48 [5] DEBUG: AT2[/dev/ttyS0]: <-- OK >2002-07-10 21:51:48 [5] DEBUG: AT2[/dev/ttyS0]: send command status: 0 > >__ > > > > > This looks ok - the message was sent successfuly, eventually. what happens is that when you deliver an MT to the AT2 module, it attempts to send it to the modem. sometime, for various reasons, the modem will reject the MT, in which case the driver will try again until it either succeeds or fails 3 times. in the logs here you can see a message that was tried once, failed, tried again and sent successfuly the second time. -- Oded Arbel m-Wise mobile solutions
Re: originating address (ID:023)
Rolf Frøysa wrote: >I`ve setup kannel for demonstration and it seems to work great. The only >thing is that I would like to change the originating address based on >the sms-service. Is this possible? In Norway, the smsc providers are >using the originating address (field 23) for billing codes. > >Sincerly > >Rolf Frøysa > > > I don't think you can do this based on the sms-service (or maybe you can - check forced-sender and global-sender in the userguide- I don't remember whether those pertain to sms-service), but in your application you can set the "from" X-Kannel header to set the sender in the returned MT, or the sender paremeter in the send-sms call for a push MT. -- Oded Arbel m-Wise mobile solutions
Re: symbol @ problem
Mauricio Ramos wrote:
I find out that I have problems with "@" when it's been sent with 7bits
encoding (coding=1) then I need to translate to "¡" to sent as 7bits.
When I sent "@" with 8bits encoding (coding=2), the "@" displays correctly
on mobile phone for Logica's SMSC but not for CMG's SMSC. I suspect this is
due to wrong SMSC's configuration.
Is this a clue?
Regards.
-Original Message-
From: Oded Arbel [mailto:[EMAIL PROTECTED]]
Sent: quarta-feira, 10 de julho de 2002 15:17
To: Aarno Syvänen
Cc: Otgo; [EMAIL PROTECTED]
Subject: Re: symbol @ problem
Aarno Syvänen wrote:
Otgo kirjoittaa keskiviikkona, 3. heinäkuuta 2002, kello 04:10:I am
going to use kannel with Comverse iSMSC connecting via its SMPP EI. I
am testing it to decide to use or to don't use. It works OK. I can send
short messages and also I could send some binanry messages. But when
I send
message to the mobile from kannel using http push way then message is
truncated by symbol @. If I see smsbox.log it looks OK. symbol @ is
in. In
bearerbox log also it doesn't give any error but there is no message
body so
I don't know about content from bearerbox log file. But when I see iSMSC
debug file the symbol @ is changed to symbol 0x00 however it is not
actually
truncated. There are remaining part of message is in the message body
following the 0x00 symbol.
This is because in GSM character set @ is 0x00. So SMPP driver uses c
strings
after GSM conversion. Fix would be to use octstrs instead. I cannot do
this myself,
however, because I do not have a connection to an EMI center.
Aarno
This is not a problem with the Kannel drivers, but a problem with the
SMSC itself. we encountered same problem with SMPP connection to
BTCellnet - the SMPP driver sends the message OK, but the SMSC itself
truncates the message. this is usually due to faulty encoding handling
in the SMSC (although the Kannel SMPP driver uses the SMPPv3.3 coding
format and not the SMPPv3.4 coding format - which is diffrent - but as
the v3.4 is backwards compatible it shouln't be a problem).
--
Oded Arbel
m-Wise mobile solutions
Yes - that is definetly an SMSC problem . try to send sqaure brackets ('['
']') as 7 bit and see what happens - if you get '<' '>' instead then
your SMSC is broken - it ignores the data_coding fields and uses some sort
of latin encoding instead of GSM 03.38. I've noticed that some SMSCs are
broken that way.
--
Oded Arbel
m-Wise mobile solutions
Re: Trouble sending dollar symbol ($) in SMS
Joel Hockey wrote: I'm using at. -Original Message- From: Oded Arbel [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 11, 2002 4:50 AM To: Joel Hockey Cc: '[EMAIL PROTECTED]' Subject: Re: Trouble sending dollar symbol ($) in SMS Joel Hockey wrote: Hi, I am using Kannel 1.1.4 on win2k with a wavecom gsm modem. I am having trouble sending the dollar symbol ($), (ASCII character 0x24) in an sms message to a mobile phone. When I use fakesmsc, I see the '$' fine. When I send an sms to a nokia phone, the phone complains that the message is corrupted and will not display it. When I send it to a siemens phone, the $ is displayed as '¤' (ASCII char 0xa4). I have tried using the 'alt-charset = 1' option but this doesn't make any difference. Does anyone have any suggestions? Thanks, Joel I did not have this problem - are you using AT2 or AT ? -- Oded Arbel m-Wise mobile solutions Please use AT2. AT is deprecated and should not be used (it will probably be kicked of Kannel in the near future). -- Oded Arbel m-Wise mobile solutions
Re: Doubts regarding status numbers
Mauricio Ramos wrote: >Hello All, > >I have some limitation to read the source code so I please ask you some >questions (at the end): > >---cutted from status.html--- >SMS: received 343 (0 queued), sent 31 (0 queued), store size 312 >SMS: inbound 0.63 msg/sec, outbound 0.06 msg/sec >DLR: 0 queued, using internal storage > >SMSC connections: >CARRIER1 SMPP:xxx.xxx.xxx.xxx:/:xx:xx (online 547s, rcvd 45, >sent 0, failed 0, queued 0 msgs) >CARRIER2 SMPP:yyy.yyy.yyy.yyy:y/y:yyy:yy (online 547s, rcvd >298, sent 31, failed 0, queued 0 msgs) >- > >Who is actually receiving in status.html? Kannel or SMSC? > Kannel. >What does "store size" mean? > When a message is received it is stored in stateful storage on disk, called "message store". when a message is succesfuly delivered to the SMSC, or rejected by it, it is then removed from the store. this value is the number of messages in the store file. >What does "DLR queued" mean? > How many delivery reports are still being waited on. >Waht does "failed" mean? > > Message that failed to be sent ? -- Oded Arbel m-Wise mobile solutions
Weird chars..
Hi! Every no and then, (very seldom) we receive strange chars from Tele2 in Sweden (connecting using SMPP). For this campaign, three SMS out of 1000 000 has became like this: 2002-07-11 10:07:33 Receive SMS [SMSC:tele2] [SVC:] [ACT:] [from:46704146118] [tj×çé5è=FølÈe:¨¬ù¹Éç·ÄÎ×a2Æ>³¡ä2æd/ÓAê:Hæ>»Ö] [udh:0:]»Aì²½,w¹¡UzØ Any ideas ? Is the problem at the SMSC side ? /S - Stefan Cars CTO Globalwire Communications Phone: +46 18 10 79 50 Mobile(UK): +44 788 061 36 69 Mobile(SE): +46 708 44 36 00
kannel 1.2.0 rpm
I built an RPM on redhat 7.2 (enigma) if anybody cares. Could we publish it on the website (it might need some cleanup and checking, I'm not an RPM expert, but at least it works. ;) ). No documentation, FYI. === Andrea Trasatti BWARE TECHNOLOGIES via San Gregorio, 3 - 20124 Milan - Italy http://www.bware.it Tel. +39 02 2779181 Fax +39 02 27791828 Cell. +39 335 7866749
RE: Trouble sending dollar symbol ($) in SMS
I'm using at. > -Original Message- > From: Oded Arbel [mailto:[EMAIL PROTECTED]] > Sent: Thursday, July 11, 2002 4:50 AM > To: Joel Hockey > Cc: '[EMAIL PROTECTED]' > Subject: Re: Trouble sending dollar symbol ($) in SMS > > > Joel Hockey wrote: > > >Hi, > > > >I am using Kannel 1.1.4 on win2k with a wavecom gsm modem. > I am having > >trouble sending the dollar symbol ($), (ASCII character > 0x24) in an sms > >message to a mobile phone. > > > >When I use fakesmsc, I see the '$' fine. > > > >When I send an sms to a nokia phone, the phone complains > that the message is > >corrupted and will not display it. > > > >When I send it to a siemens phone, the $ is displayed as '¤' > (ASCII char > >0xa4). > > > >I have tried using the 'alt-charset = 1' option but this > doesn't make any > >difference. > > > >Does anyone have any suggestions? > > > >Thanks, > > > >Joel > > > > > > > I did not have this problem - are you using AT2 or AT ? > > -- > Oded Arbel > m-Wise mobile solutions > > >
Re: webmin kannel module needed
Hi, I have an old version of the webmin kannel module (from november 2000, but I think that is the last version). It works with kannel 1.0.3 ! You can find it at the following URL : http://jerome.ramette.free.fr/webmin Bye, Jérôme. On Tue, Jul 09, 2002 at 02:15:38PM +0200, Lukas wrote: > Hi, > > If someone has webmin kannel module for administrating SMS messages, please > send a copy to me. > > I can't find it anywhere, link to the author`s page is blind. > > I would really apprieciate sending it to me, or putting somewhere on ftp.. > > Thank you in advance, > Bye! Lukas > > >
Re: originating address (ID:023)
On Wednesday 10 July 2002 20:49, Rolf Frøysa wrote: > I`ve setup kannel for demonstration and it seems to work great. The only > thing is that I would like to change the originating address based on > the sms-service. Is this possible? In Norway, the smsc providers are > using the originating address (field 23) for billing codes. You could do it in Kannel, but the operators will still use your shortcode. Arne -- Arne K. Haaje | T: 69 92 04 90 Bregneveien 9 | F: 69 92 04 91 1825 Tomter | M: 92 88 44 66
