Re: SSL handshake failure on smsbox service call to various https URLs
Hi Mesbah Thanks for the reply. I'm not sure what ssl rule I should be looking at in Kannel? It works fine when I make a request to an AWS Lambda URL and other websites but not Cloudflare with a LetsEncrypt certificate. Kind regards Alex On Sat, 18 May 2024 at 12:15, Mesbahuddin Malik wrote: > check kannel ssl rule. > > regards > Mesbah > > On Fri, May 17, 2024 at 9:33 PM Alex Kinch wrote: > >> Hi all, >> >> I'm having odd problems when making an https request in an smsbox service >> (on latest compiled release from SVN and also Debian packages), I get back: >> >> 2024-05-17 15:14:25 [24] [9] ERROR: SSL write failed: OpenSSL error 1: >> error:0001:lib(0)::reason(1) >> 2024-05-17 15:14:25 [24] [9] ERROR: SSL error:0A000410:SSL >> routines::sslv3 alert handshake failure >> 2024-05-17 15:14:25 [24] [9] ERROR: SSL write failed: OpenSSL error 6: >> error:0006:lib(0)::reason(6) >> >> It seems to be affecting only certain sites, i.e. ones I have behind >> Cloudflare with an individual LetsEncrypt certificate (not a wildcard - but >> wildcard LetsEncrypt sites break too). >> >> I ran openssl s_client -connect and everything appears to be in order. >> When I set up sms-service keywords to fetch Google, or the BBC News >> website, everything works. >> >> Does anyone have any ideas what might be causing this? Running kannel in >> a docker container with debian:bookworm-slim as the base image. >> >> Thanks >> Alex >> >> >> >> >> >>
SSL handshake failure on smsbox service call to various https URLs
Hi all, I'm having odd problems when making an https request in an smsbox service (on latest compiled release from SVN and also Debian packages), I get back: 2024-05-17 15:14:25 [24] [9] ERROR: SSL write failed: OpenSSL error 1: error:0001:lib(0)::reason(1) 2024-05-17 15:14:25 [24] [9] ERROR: SSL error:0A000410:SSL routines::sslv3 alert handshake failure 2024-05-17 15:14:25 [24] [9] ERROR: SSL write failed: OpenSSL error 6: error:0006:lib(0)::reason(6) It seems to be affecting only certain sites, i.e. ones I have behind Cloudflare with an individual LetsEncrypt certificate (not a wildcard - but wildcard LetsEncrypt sites break too). I ran openssl s_client -connect and everything appears to be in order. When I set up sms-service keywords to fetch Google, or the BBC News website, everything works. Does anyone have any ideas what might be causing this? Running kannel in a docker container with debian:bookworm-slim as the base image. Thanks Alex
Re: SMPP message ID greater than 9223372036854775807 breaking DLRs
Hi Kyriacos The MySQL field type was varchar(100) so that wasn't the problem. In the end we fixed it by asking Nexmo/Vonage to change the message ID types to match (hex) and then removed msg-id-type so the conversion was no longer needed. Thanks Alex On Mon, 7 Aug 2023 at 01:04, Kyriacos/Netsmart wrote: > And your mysql table create statement. It might be that you are using a > filed type that can not hold such large numbers. Can easily be converted to > a char based storage if you don't have extreme space limit issues on the DB > side. > > On 06/08/2023 6:16 pm, Mesbahuddin Malik wrote: > > Send your Smpp Config. > > On Sun, Aug 6, 2023 at 8:26 PM Alex Kinch wrote: > >> Hi all, >> >> I've run into an issue with a certain SMS provider (Nexmo/Vonage) that is >> using message IDs greater than 9223372036854775807 (e.g. >> 6142530091694509440651642911224527237), which is in turn breaking DLR >> processing in Kannel. >> >> They use hex in submit_sm_resp and decimal in deliver_sm so I have to >> have msg-id-type=0x01 set, so it's not like I can remove it and have >> Kannel use a C literal instead. >> >> I've just tried the latest daily build and have the same issue. Using >> MySQL for DLR storage if that's relevant. >> >> Any help appreciated! >> >> Thanks >> Alex >> > > -- > Kyriacos Sakkas > Netsmart > Tel: + 357 22 452565 > Fax: + 357 22 452566 > Email: kyria...@netsmart.com.cyhttp://www.netsmart.com.cy > > Taking Business to a New Level! > > ** Confidentiality Notice: The information contained in this email > message may be privileged, confidential and protected from disclosure. > If you are not the intended recipient, any dissemination, distribution, > or copying of this email message is strictly prohibited. > If you think that you have received this email message in error, please > email the sender at supp...@netsmart.com.cy ** > >
SMPP message ID greater than 9223372036854775807 breaking DLRs
Hi all, I've run into an issue with a certain SMS provider (Nexmo/Vonage) that is using message IDs greater than 9223372036854775807 (e.g. 6142530091694509440651642911224527237), which is in turn breaking DLR processing in Kannel. They use hex in submit_sm_resp and decimal in deliver_sm so I have to have msg-id-type=0x01 set, so it's not like I can remove it and have Kannel use a C literal instead. I've just tried the latest daily build and have the same issue. Using MySQL for DLR storage if that's relevant. Any help appreciated! Thanks Alex
Re: Kannel fils to start with sqlbox configuration
I'm sure this was answered recently, however.. sqlbox-standalone config values shouldn't be in the main kannel.conf file. Move that section into it's own file (eg sqlbox.conf), make sure sqlbox is reading the right config file and bearerbox should be fine. hth, Alex On 7 Jun 2008, at 12:27, James Mutuku wrote: Hi, I compiled kannel stable release(version 1.4.1) and sqlbox- standalone. When I start bearerbox, I get the error below. what could be the problem? - error 2008-06-05 16:48:07 [8141] [0] INFO: Debug_lvl = -1, log_file = none, log_lvl = 0 2008-06-05 16:48:07 [8141] [0] ERROR: Group 'sqlbox' may not contain field 'log-level'. 2008-06-05 16:48:07 [8141] [0] ERROR: Error found on line 60 of file `/etc/kannel.conf'. 2008-06-05 16:48:07 [8141] [0] PANIC: Couldn't read configuration from `/etc/kannel.conf'. 2008-06-05 16:48:07 [8141] [0] PANIC: /usr/local/kannel/sbin/ bearerbox(gw_panic+0xe6) [0x80c4276] 2008-06-05 16:48:07 [8141] [0] PANIC: /usr/local/kannel/sbin/ bearerbox(main+0xc2d) [0x805346d] 2008-06-05 16:48:07 [8141] [0] PANIC: /lib/libc.so. 6(__libc_start_main+0xdc) [0x46d08dec] 2008-06-05 16:48:07 [8141] [0] PANIC: /usr/local/kannel/sbin/ bearerbox [0x8051b11] -end error - kannel.conf # Default kannel configuration file group = core admin-port = 13000 admin-password = root status-password = root #admin-deny-ip = *.*.*.* admin-allow-ip = 127.0.0.1, 10.2.2.13 smsbox-port = 13001 #wapbox-port = 13002 #box-deny-ip = *.*.*.* box-allow-ip = *.*.*.* wdp-interface-name = * log-file = /var/log/kannel/bearerbox.log store-file = /var/log/kannel/kannel.store log-level = 0 dlr-storage=mysql # SMSBOX SETUP group = smsbox bearerbox-host = localhost sendsms-port = 13013 sendsms-chars = 0123456789 +- global-sender = 12345 log-file = /var/log/kannel/smsbox.log log-level = 0 #access-log = access.log #white-list = #black-list = #reply-couldnotfetch = #reply-couldnotrepresent = #reply-requestfailed = #reply-emptymessage = # SENDSMS USERS SETUP group = sendsms-user username = root password = root # SQLBOX SETUP group = sqlbox id = sqlbox-db smsbox-id = smsbox #global-sender = bearerbox-host = localhost bearerbox-port = 13001 smsbox-port = 13005 smsbox-port-ssl = false sql-log-table = sent_sms sql-insert-table = send_sms log-file = /var/log/kannel/kannel-sqlbox.log log-level = 0 #white-list = #black-list = #white-list-regex = #ssl-client-certkey-file = #ssl-server-cert-file = #ssl-server-key-file = #ssl-trusted-ca-file = group = mysql-connection id = sqlbox-db host = localhost username = root password = database = delivery max-connections = 10 # DLR SETUP #mysql connection group = mysql-connection id = mydlr host = localhost username = root password = database = dlr max-connections = 10 group = dlr-db id = mydlr table=dlr field-smsc=smsc field-timestamp=ts field-destination=destination field-source=source field-service=service field-url=url field-mask=mask field-status=status field-boxc-id=boxc # SMSC Fake group = smsc smsc = fake port = 1 connect-allow-ip = 127.0.0.1 # A do-nothing service. group = sms-service keyword = nop text = You asked nothing and I did it! # SMS SERVICE black-list group = sms-service keyword = black text = You are not allowed to use this service, Go away! # SMSC SMPP group = smsc smsc = smpp host = 10.2.2.13 port = 2775 #receive-port = 2776 smsc-username = smppclient smsc-password = password system-type = address-range = # SMS SERVICE Default # there should be default always group = sms-service keyword = default text = No service specified. -end kannel.conf jmutuku.vcf
Re: reply-to address
+1 from me. On 4/19/07, Iain Dooley [EMAIL PROTECTED] wrote: hi all, i don't know about anyone else but i would prefer if the reply-to address for this list was [EMAIL PROTECTED] i accidentally send messages to the original sender quite a bit ... anyone else? cheers iain
[OT] I want to give you traffic!
I figured it's time to expand our SMSC connections, so if anyones got an SMPP server available and can fire me across a coverage list and prices, let's talk :) Also, if anyone wants high quality routes at a good price, shout too. We can only do HTTP/S at the moment, but if there's justification for putting in an SMPP server I can look at it. Maybe we should start a separate mailing list for commercial offerings? We're all in the same business here, and could probably all gain something from helping each other make a bit of money. Alex
concatenation woes
Hello, I'm trying to write a PHP script to concatenate messages to pass to Kannel. It works to the point that the message gets to the phone, but then the phone says it cannot display the message when I try to open it. Here's what I'm sending: Message 1: UDH: %05%00%03%EA%02%01 Message: This is part one Message 2: UDH: %05%00%03%EA%02%02 Message: This is part two Kannel accepts it ok, but the phone (Nokia E61) seems to be having an issue with it. Seems to be reassembling ok but won't let me display the message. Am I missing something? Alex
Re: concatenation woes
Hi Alejandro Thanks for the email, I know Kannel can split it but I wanted to take care of it in PHP to allow proper billing, logging etc. Thanks, Alex On 4/15/07, Alejandro Guerrieri [EMAIL PROTECTED] wrote: Kannel can split a long message in parts and send them with proper formatting. Check the user guide for the max-messages parameter. Hope it helps, Alejandro. On 4/15/07, Alex Kinch [EMAIL PROTECTED] wrote: Hello, I'm trying to write a PHP script to concatenate messages to pass to Kannel. It works to the point that the message gets to the phone, but then the phone says it cannot display the message when I try to open it. Here's what I'm sending: Message 1: UDH: %05%00%03%EA%02%01 Message: This is part one Message 2: UDH: %05%00%03%EA%02%02 Message: This is part two Kannel accepts it ok, but the phone (Nokia E61) seems to be having an issue with it. Seems to be reassembling ok but won't let me display the message. Am I missing something? Alex -- Alejandro Guerrieri Magicom http://www.magicom-bcn.net/ LinkedIn: http://www.linkedin.com/in/aguerrieri
Re: Strange problem with accents on MO
OK ignore me, I've just noticed it's not in the GSM 7-bit alphabet. Too much sunshine has got to my brain.. :) On 4/14/07, Alex Kinch [EMAIL PROTECTED] wrote: Doing a little testing this afternoon with accents on MO, and came across a strange problem. I'm sending the following from my Nokia E61: Test aäæåàáâãa When it appears in our database, we've got: Test aäæåà So áâãa are arriving as just a. The PDU is pasted below. Noticing the last four characters (áâãa) are showing up as just a (ASCII hex 61). Reckon its an operator problem somewhere? They use HPROMAN8 as a character set. 2007-04-14 19:37:31 [19194] [6] DEBUG: SMPP[]: Got PDU: 2007-04-14 19:37:31 [19194] [6] DEBUG: SMPP PDU 0x8557c80 dump: 2007-04-14 19:37:31 [19194] [6] DEBUG: type_name: deliver_sm 2007-04-14 19:37:31 [19194] [6] DEBUG: command_id: 5 = 0x0005 2007-04-14 19:37:31 [19194] [6] DEBUG: command_status: 0 = 0x 2007-04-14 19:37:31 [19194] [6] DEBUG: sequence_number: 18641 = 0x48d1 2007-04-14 19:37:31 [19194] [6] DEBUG: service_type: NULL 2007-04-14 19:37:31 [19194] [6] DEBUG: source_addr_ton: 1 = 0x0001 2007-04-14 19:37:31 [19194] [6] DEBUG: source_addr_npi: 1 = 0x0001 2007-04-14 19:37:31 [19194] [6] DEBUG: source_addr: 44 2007-04-14 19:37:31 [19194] [6] DEBUG: dest_addr_ton: 1 = 0x0001 2007-04-14 19:37:31 [19194] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2007-04-14 19:37:31 [19194] [6] DEBUG: destination_addr: 44 2007-04-14 19:37:31 [19194] [6] DEBUG: esm_class: 0 = 0x 2007-04-14 19:37:31 [19194] [6] DEBUG: protocol_id: 0 = 0x 2007-04-14 19:37:31 [19194] [6] DEBUG: priority_flag: 0 = 0x 2007-04-14 19:37:31 [19194] [6] DEBUG: schedule_delivery_time: NULL 2007-04-14 19:37:31 [19194] [6] DEBUG: validity_period: NULL 2007-04-14 19:37:31 [19194] [6] DEBUG: registered_delivery: 0 = 0x 2007-04-14 19:37:31 [19194] [6] DEBUG: replace_if_present_flag: 0 = 0x 2007-04-14 19:37:31 [19194] [6] DEBUG: data_coding: 0 = 0x 2007-04-14 19:37:31 [19194] [6] DEBUG: sm_default_msg_id: 0 = 0x 2007-04-14 19:37:31 [19194] [6] DEBUG: sm_length: 15 = 0x000f 2007-04-14 19:37:31 [19194] [6] DEBUG: short_message: 2007-04-14 19:37:31 [19194] [6] DEBUG:Octet string at 0x82121d0: 2007-04-14 19:37:31 [19194] [6] DEBUG: len: 15 2007-04-14 19:37:31 [19194] [6] DEBUG: size: 16 2007-04-14 19:37:31 [19194] [6] DEBUG: immutable: 0 2007-04-14 19:37:31 [19194] [6] DEBUG: data: 54 65 73 74 20 20 61 cc d7 d4 c8 61 61 61 61 Test a 2007-04-14 19:37:31 [19194] [6] DEBUG:Octet string dump ends. 2007-04-14 19:37:31 [19194] [6] DEBUG: user_message_reference: 61 = 0x003d 2007-04-14 19:37:31 [19194] [6] DEBUG: SMPP PDU dump ends.
SS7 SMSC assistance required
Hello, I know a few people on the list have done this.. if you have experience of rolling your own SS7 SMSC could you drop me a note off-list? Thanks, Alex
Re: SMSC throughput with SMPP protocol
All depends on what your provider sets as a throttle - we have SMPP connections that can quite happily handle thousands of messages a minute. It's not uncommon for a network to set an entry level limit of one or two messages a second on an SMPP connection. Alex On 1/30/07, Narendran K [EMAIL PROTECTED] wrote: what is the through put of a SMSC over SMPP?? What is the maximum, minimum, average values?? What are the factors affecting this through put?? How much does the protocol (SMPP, CIMD, SS7 etc) between SMSC and SMS-Gateway affects the through put. -- Computer Science is no more about computers than astronomy is about telescopes.
Re: Masking originating addresses
All depends on how you're sending your messages. Most decent providers will allow setting the sender number on an SMPP, HTTP, etc connection. I've never heard of a network that'll allow you to do that on a GSM modem or handset, but then again stranger things have happened.. :) Alex On 1/29/07, David Ritchie [EMAIL PROTECTED] wrote: Yes, that's right -- setting the sender number. -Original Message- From: Iain Dooley [mailto:[EMAIL PROTECTED] Sent: Tuesday, 30 January 2007 10:32 a.m. To: David Ritchie Cc: users@kannel.org Subject: Re: Masking originating addresses hi david, On Tue, 30 Jan 2007, David Ritchie wrote: Hello all -- has anybody had any success with using TPOA (or similar) to mask the originating address for MT SMS messages? do you just mean setting the sender number? cheers iain
monitoring kannel
Hello all, What does everyone else here use for monitoring their kannel boxen? I mean things like SMSCs down, queues getting too high, etc. Alex
Re: sendsms unknown command
Check your config, 13000 is by default the admin port, 13013 is where smsbox should be listening - and therefore where you should find /cgi-bin/sendsms lives. http://localhost:13013/cgi-bin/sendsms etc should work. Alex On 12/26/06, Pradnya Nimje [EMAIL PROTECTED] wrote: Hello list, I am using kannel 1.4.1 ,cygwin on windows 2000 Server, when I send sms with url ---http:\\localhost:13000\cgi-bin\sendsms? ...I get error UNKNOWN COMMAND . When I write status instead of sendsms it works fine. Can anyone suggest the resolution. Merry Christmas Happy New Year With Regards Pradnya Nimje
Re: HLR lookup for number portability
After a little delay of a few months, I'm moving forward slowly but surely with this. We now have our own internal setup to query an MSISDN for MCC/MNC, it's just a case of interfacing it to the outside world. As such a query is a two stage process, I would imagine it would go something like this: 1. Client makes request with MSISDN and return URL 2. Server posts result (as HTTP GET or POST) back to client as soon as the necessary information is received back from the remote operator. As this is such a simple thing, I don't believe it's necessary to wrap it all up in SOAP - a simple HTTP request should do. Guess the next question is how to interface it to Kannel. Also, what sort of cost would you be likely to pay for such a service - I was thinking no setup or monthly fee, and just billing for queries. Thoughts? Alex On 8/23/06, Alex Kinch [EMAIL PROTECTED] wrote: Hello, Just putting together a proposal for a new service, would there be any interest from people here for a service that will do an HLR lookup against an MSISDN and return a MCC/MNC? I know there was talk about an HLR box or plugin for Kannel, but not sure it ever went much further forward than a few emails. If anyones interested, email me off-list. ALex
Re: HLR lookup for number portability
Hi Ben, I think the protocol you use will be dependent somewhat on the average length of time for the lookup. There is more overhead in having to have 2 connection setups (1 outbound and 1 inbound) than in just the one. But it probably comes down to volumes as well, and if the calling application minds blocking for an answer. Blocking is an idea, but as you're basically doing a an SS7 query to the remote operators HLR it's possible the HLR may not respond or take a little while to respond. That's where caching comes into play. Alex
Re: HLR lookup for number portability
On 11/9/06, Ben Suffolk [EMAIL PROTECTED] wrote: Blocking is an idea, but as you're basically doing a an SS7 query to the remote operators HLR it's possible the HLR may not respond or take a little while to respond. That's where caching comes into play. Indeed. I think if you are planning on caching at your end, then you need to provide users with a way to force a live get as well, possibly making this a higher cost, or more to the point the cached one cheaper :-) Yep, that's the plan. Cache it for a predetermined amount of time, but give the client the option to force refresh of the info. The more people use it, the more likely the cache is to be up to date, and the cheaper it gets. Win-win really. Alex
Re: Re[2]: Making sure DLR's are processed by multiple SMSC Connections.
... or in a Kannel FAQ :) runs away quick in case anyone thinks I just volunteered to write one! :) On 11/6/06, Thomas Göttgens [EMAIL PROTECTED] wrote: Hello Alex, thanks, that did the trick and should be in userguide ;-) Monday, November 6, 2006, 10:23:05 PM, you wrote: AK Change the smsc-id to all be the same. I do it for 3 x SMPP links and AK it works well for DLRs.. AK On 11/6/06, Thomas Göttgens [EMAIL PROTECTED] wrote: Hello, we are maintaining 5 symmetrical links to our UCP uplink to maximize throughput. The setup is as follows: -- Best regards, Thomasmailto:[EMAIL PROTECTED]
Re: bearerbox - smsbox retry if smsbox is unavailable
Hi Ben Looking at the status you showed with them queued in smsbox, this basically means that smsbox has not returned an ack to bearerbox. It suggests to me that either sqlbox is not passing the ack back to bererbox (assuming you are connecting smsbox to sqlbox and not directly), or that smsbox is not sending it, possibly because it can't pass the message on via http and you have it set to retry? Looked just now, and it's still sitting in the queue. It's actually an ACK/ message, like this: [SMS ID] [Type] [Time] [Sender] [Receiver] [SMSC ID] [BOX ID] [UDH] [Message] [ea66c23f-bf7f-4398-a076-c883695176ff] [DLR-MO] [2006-11-02 01:04:39] [+44XX] [+44XX] [TEST] [smsbox] [] [ACK/] I will generate some MO traffic later on and see if that gets stuck too. Yes smsbox is connected to sqlbox, and sqlbox connects to bearerbox. Alex
bearerbox - smsbox retry if smsbox is unavailable
Hi, If I start everything like this: bearerbox (wait 2 seconds) sqlbox (wait 2 seconds) smsbox Then any messages that bearerbox has received via SMPP in the period while sqlbox and smsbox are starting are dumped to the store. However, the problem is these messages seem to remain in the store, and never get resubmitted to smsbox via sqlbox. It looks something like this: Box connections: smsbox:smsbox, IP 127.0.0.1 (1 queued), (on-line 0d 0h 0m 44s) *SMSBOX* smsbox:smsbox, IP 127.0.0.1 (0 queued), (on-line 0d 0h 0m 42s) *SQLBOX* As I started sqlbox first then smsbox two seconds later, it appears the message is queued at smsbox. The message that's jammed was sent around 30 minutes ago, and in the queue it says it has a BOX ID of smsbox. Any suggestions? Thanks, Alex
Re: Kannel installation problems
Hi Arun, Can I make a suggestion? Kannel 1.3.2 is now over two years old - we're now up to 1.4.1-stable. I know you don't really want to use binaries, but unless someone has kindly made some for Redhat then I think you'd be better off with compiling it from source. Hope that helps, Alex On 10/31/06, Arun Jain [EMAIL PROTECTED] wrote: Hello everybody, Even with some suggestions from community, I am still having problems in installing the kannel gateway. Am I using the wrong binary? and The binary is kannel-1.3.2-3.0.rh7.fr.i386.rpm and my system is Redhat 4.5.3 (coreutils) I do not want to install through the source. I want to install from stable binary libraries only. Importing the key gave me following errors /home/w1036/kannel!188 rpm --import RPM-GPG-KEY-freshrpms error: RPM-GPG-KEY-freshrpms: import read failed. /home/w1036/kannel!202 sudo rpm --import /usr/share/doc/fedora-release-*/RPM-GPG-KEY-fedora sudo: No match. /home/w1036/kannel My steps are as follows. 1. I checked if I have the libxml2 library. I have that. Checked. 2. I downloaded the binary kannel-1.3.2-3.0.rh7.fr.i386.rpm for my Linux machine 4.5.3 (Is this version right for my machine). 3. I installed it with the command rpm -ivh kannel-1.3.2-3.0.rh7.fr.i386.rpm it gave me a warning warning: kannel-1.3.2-3.0.rh7.fr.i386.rpm: V3 DSA signature: NOKEY, key ID e42d547b Preparing... ### [100%] package kannel-1.3.2-3.0.rh7.fr is already installed Since I have already installed it earlier the last line says that. However when I go to my /etc/init.d directory I do not find any kannel daemon or any file which is remotely connected with kannel. I fail to understand what did I do wrong. Please can someone help me guid through the process. I understand the process should not be too tough when you are installing through the packages. On 10/31/06, manas mohanty [EMAIL PROTECTED] wrote: Hi , Download gateway.zip - Source as a ZIP file. (See FAQ.) md5: 5b0a580ea9104f49c8c60e5bdadb5cd7 gateway-1.3.2.zip u can find this on below link http://kannel.org/download.shtml 1st configure kannel g/w using ./configure(--help) according ur requirement then make it.u ll get 3 binaries(bearerbox,smsbox,wapbox) at gateway-1.3.2/gw. Then u ve to configure the parameters in smskannel.conf. Then try to run the binaries . but before dat once u go through the userguide of kannel(http://kannel.org/userguide.shtml) for detail. IT'S SO SIMPLE TO BE HAPPY BUT VERY DIFICULT TO BE SIMPLE Thanks Regards, MANAS R. MOHANTY - Original Message From: Arun Jain [EMAIL PROTECTED] To: announce@kannel.org Sent: Tuesday, 31 October, 2006 2:20:32 AM Subject: Kannel installation problems Hello Group. I am working on WAP gateway installation. While installing kannel, I encountered following problems. I tried running the following command. I am working on Linux RedHat 4.5.3. (coreutils) I ran this command as root. 1. /home/arunsudo rpm --import /usr/share/doc/fedora-release-*/RPM-GPG-KEY-fedora And it came up with the following errors. sudo: No match. 2. There after I downloaded kannel-1.3.2-3.0rh7.fr.i386.rpm package and installed it with following command. It gave the following warning. /home/arun/kannelsudo rpm -ivh kannel-1.3.2-3.0.rh7.fr.i386.rpm warning: kannel-1.3.2-3.0.rh7.fr.i386.rpm: V3 DSA signature: NOKEY, key ID e42d547b Preparing... ### [100%] 1:kannel ### [100%] The final result is that I do not see any kannel daemon in init.d directory nor do I see any kannel directory, conf file or anythign connected with kannel. Could someone please guide me in through this process and point me out as to what did I do wrong. Any help will be greatly appreciated. 3. Please also tell me what changes I need to make in the conf file after I am able to install kannel. Thanks. arun ___ announce mailing list announce@kannel.org http://www.kannel.org/mailman/listinfo/announce Find out what India is talking about on - Yahoo! Answers India Send FREE SMS to your friend's mobile from Yahoo! Messenger Version 8. Get it NOW
Re: Concatenation and I-Mate JAMin' Windows Mobile phones
Hi Stipe
I've got only limited information as it's the customer testing and not
me, but from what I understand the I-Mate phone is saying 'content
cannot be displayed' when it receives a concatenated message. Leads me
to think something is up with the UDH field.
The customer took the SIM card out of the I-Mate and popped it in
another handset, and concatenation works fine from Kannel. Also seems
to work ok from other handsets to the I-Mate. Where it all seems to go
wrong is when we send a concatenated message to the network via SMPP
for delivery to the handset.
I will try and find out a little more, although I get the feeling this
might be a slow process as it's such a weird problem!
I will send the SMPP PDUs from the bearerbox box to the list later
today when I get a chance.
Alex
On 10/11/06, Stipe Tolj [EMAIL PROTECTED] wrote:
Hi Alex,
Alex Kinch wrote:
Having a problem with I-Mate JAMin' handsets not being able to
reassemble messages that have been concatenated by Kannel. Everything
looks ok, and other handsets are reassembling ok. Also sending from
another handset to this one works, and it reassembles ok too. Just
seems to be having trouble with messages sent via Kannel.
Anyone come across any issues with these handsets?
strange impact?!... I'd assume that most probably the segments are send over
different smscs? If yes, this breaks on most common handsets.
Kannel's UDH header handling regarding concat should be safe.
In case you need to investigate, I suggest to capture PDUs on a GSM modem
device, so we can confirm.
Stipe
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Concatenation and I-Mate JAMin' Windows Mobile phones
Hi, Having a problem with I-Mate JAMin' handsets not being able to reassemble messages that have been concatenated by Kannel. Everything looks ok, and other handsets are reassembling ok. Also sending from another handset to this one works, and it reassembles ok too. Just seems to be having trouble with messages sent via Kannel. Anyone come across any issues with these handsets? Thanks, Alex
Re: store messages
Can I make a suggestion? If you're not already subscribed to the kannel-devel list, get yourself hooked up and jump on the thread that's discussing this patch. With any new feature it's important to get real world feedback, so if you're having problems I'm sure the original patch creator will be able to work with you to fix it. Alex On 9/21/06, Boardmain [EMAIL PROTECTED] wrote: Some one have a easy way to store easy long messages ? I want easy do that… recive messages.. understend if it is long o sort (if is long i want to make only one big sms, not many small…) And passa all to a php script… now i have.. kannel patched with concat.diff (some time i recive sms with ½ some other no… ( message are each long…. ) i tryed do configure mysql storage… but it don't work…. :/
Re: udh record
I've used this in the past to clean up Kannels UDH into something more normal:
function cleanudh($udh) {
$udh = urlencode($udh);
$udh = str_replace(%,,$udh);
return($udh);
}
On 9/20/06, Boardmain [EMAIL PROTECTED] wrote:
Hi, why in my php script im not able to get the udh record
(udh=%u )
and i see it on the log
[udh:5:0003180303]
If i take the udh get var in php i recive an empty var (some strange char)
I think becouse it is passed as hex value ..
some one have a working php script to get correctly all param passed by
kannel and get-url ??
thanks
Samuele
Re: R: udh record
Well.. there's a patch (hopefully) about to be added to CVS that will
automatically re-join concatenated messages and then pass them in one
piece to your PHP script. It's been talked about on the kannel-devel
list, see http://www.mail-archive.com/devel@kannel.org/msg06211.html
On 9/20/06, Boardmain [EMAIL PROTECTED] wrote:
Perfect , it work...
u are able to recive crrectly long messages?
(u have a script ho take all parts into one big sms?)
-Messaggio originale-
Da: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Per conto di Alex Kinch
Inviato: mercoledì 20 settembre 2006 15.44
A: Boardmain
Cc: users@kannel.org
Oggetto: Re: udh record
I've used this in the past to clean up Kannels UDH into something more
normal:
function cleanudh($udh) {
$udh = urlencode($udh);
$udh = str_replace(%,,$udh);
return($udh);
}
On 9/20/06, Boardmain [EMAIL PROTECTED] wrote:
Hi, why in my php script im not able to get the udh record
(udh=%u )
and i see it on the log
[udh:5:0003180303]
If i take the udh get var in php i recive an empty var (some strange char)
I think becouse it is passed as hex value ..
some one have a working php script to get correctly all param passed by
kannel and get-url ??
thanks
Samuele
HLR lookup for number portability
Hello, Just putting together a proposal for a new service, would there be any interest from people here for a service that will do an HLR lookup against an MSISDN and return a MCC/MNC? I know there was talk about an HLR box or plugin for Kannel, but not sure it ever went much further forward than a few emails. If anyones interested, email me off-list. ALex
Re: Wap push sanity check
Hi Aarno
Must admit I haven't tried it yet, I've just been using PHP to
construct and send a wap push via the normal sendsms http interface.
Also tried it via sqlbox and no luck.
Will have a go with PPG and let you know how it goes..
Alex
On 8/21/06, Aarno Syvänen [EMAIL PROTECTED] wrote:
Hello,
does PPG work ?
Aarno
On 18 Aug 2006, at 23:12, Alex Kinch wrote:
Hello,
Seem to be having some problems with WAP push. The code to construct
the UDH and message is below. It used to work, but then somewhere
along the line it stopped.
Tried to both Nokia and SonyEricsson handsets, and both are ignoring
the message.
If someone could take a look and make sure my construction techniques
are right I would appreciate it.
Thanks,
Alex
$from = Sender;
$to = 44xxx;
function hex_encode( $text, $joiner='' ) {
for ($l=0; $lstrlen($text); $l++) {
$letter = substr($text, $l, 1);
$ret .= sprintf(%s%02X, $joiner, ord($letter));
}
return $ret;
}
$submittedwappushurl = urlencode(http://www.google.com;);
$submittedwappushtext = test;
// override messagebody with wappush and set udh
$messageudh = %06%05%04%0B%84%23%F0;
$messagebody =
%1B%06%01%AE%02%05%6A%00%45%C6%0C%03.hex_encode
($submittedwappushurl,'%').%00%01%03.hex_encode
($submittedwappushtext,'%').%00%01%01;
Provider doesnt want + on destination MSISDN
Hello list, I've just had an email from a provider who wants me to test their service. I tried last week and it failed on all messages I sent.. but they've said now that it's because I put a + in front of the destination MSISDN. I've always done this, and thought it was standard. Can someone be so kind to confirm whether I'm right, and removing + is a strange thing to ask? Thanks, Alex
Wap push sanity check
Hello,
Seem to be having some problems with WAP push. The code to construct
the UDH and message is below. It used to work, but then somewhere
along the line it stopped.
Tried to both Nokia and SonyEricsson handsets, and both are ignoring
the message.
If someone could take a look and make sure my construction techniques
are right I would appreciate it.
Thanks,
Alex
$from = Sender;
$to = 44xxx;
function hex_encode( $text, $joiner='' ) {
for ($l=0; $lstrlen($text); $l++) {
$letter = substr($text, $l, 1);
$ret .= sprintf(%s%02X, $joiner, ord($letter));
}
return $ret;
}
$submittedwappushurl = urlencode(http://www.google.com;);
$submittedwappushtext = test;
// override messagebody with wappush and set udh
$messageudh = %06%05%04%0B%84%23%F0;
$messagebody =
%1B%06%01%AE%02%05%6A%00%45%C6%0C%03.hex_encode($submittedwappushurl,'%').%00%01%03.hex_encode($submittedwappushtext,'%').%00%01%01;
Re: SMSC rejected login to transmit (bind failed)??
Not wishing to sound a bit blunt, but the words in the log'SMSC rejected login to transmit'Should give you a clue :)Check the login details with your provider, including system-type as it matters for some providers that you use what they give you. AlexOn 6/22/06, Raul Martinez [EMAIL PROTECTED] wrote: What does Bind failed mean? What should I do to establish connection to my SMSC?I have included by config and some debug log text.Thanks in advance?---config---group = smscsmsc = smppsmsc-id = smsc3 host = xxx.xxx.xxx.xxxport = 7501smsc-username = smsc-password = xxxsystem-type = VMAsource-addr-ton = 0dest-addr-ton = 1denied-smsc-id =smsc1;smsc2 address-range = transceiver-mode = true---eof--config--debug---2006-06-22 12:51:33 [1928] [8] DEBUG: SMPP[ite]: Sending PDU:2006-06-22 12:51:33 [1928] [8] DEBUG: SMPP PDU 0x881c410 dump: 2006-06-22 12:51:33 [1928] [8] DEBUG: type_name: bind_transceiver2006-06-22 12:51:33 [1928] [8] DEBUG: command_id: 9 = 0x00092006-06-22 12:51:33 [1928] [8] DEBUG: command_status: 0 = 0x2006-06-22 12:51:33 [1928] [8] DEBUG: sequence_number: 2 = 0x0002 2006-06-22 12:51:33 [1928] [8] DEBUG: system_id: xxx2006-06-22 12:51:33 [1928] [8] DEBUG: password: xxx2006-06-22 12:51:33 [1928] [8] DEBUG: system_type: VMA2006-06-22 12:51:33 [1928] [8] DEBUG: interface_version: 52 = 0x0034 2006-06-22 12:51:33 [1928] [8] DEBUG: addr_ton: 0 = 0x2006-06-22 12:51:33 [1928] [8] DEBUG: addr_npi: 0 = 0x2006-06-22 12:51:33 [1928] [8] DEBUG: address_range: 2006-06-22 12:51:33 [1928] [8] DEBUG: SMPP PDU dump ends. 2006-06-22 12:51:33 [1928] [8] DEBUG: Optional parameter tag (0x0210)2006-06-22 12:51:33 [1928] [8] DEBUG: Optional parameter length read as 12006-06-22 12:51:33 [1928] [8] DEBUG: SMPP[ite]: Got PDU:2006-06-22 12:51:33 [1928] [8] DEBUG: SMPP PDU 0x881c410 dump: 2006-06-22 12:51:33 [1928] [8] DEBUG: type_name: bind_transceiver_resp2006-06-22 12:51:33 [1928] [8] DEBUG: command_id: 2147483657 = 0x80092006-06-22 12:51:33 [1928] [8] DEBUG: command_status: 13 = 0x000d 2006-06-22 12:51:33 [1928] [8] DEBUG: sequence_number: 2 = 0x00022006-06-22 12:51:33 [1928] [8] DEBUG: system_id: SMPP_USSD_SERV2006-06-22 12:51:33 [1928] [8] DEBUG: sc_interface_version: 52 = 0x0034 2006-06-22 12:51:33 [1928] [8] DEBUG: SMPP PDU dump ends.2006-06-22 12:51:33 [1928] [8] ERROR: SMPP[ite]: SMSC rejected login totransmit, code 0x000d (Bind Failed).2006-06-22 12:51:33 [1928] [8] ERROR: SMPP[ite]: I/O error or other error. Re-connecting.2006-06-22 12:51:33 [1928] [8] ERROR: SMPP[ite]: Couldn't connect to SMS center(retrying in 10 seconds).---eof--debug---
Re: SMPP 3.4 Optional params
There was an Mblox patch floating around a while back that might be a good starting point for these custom parameters. Perhaps its a good time to do something a bit more permanent to the SMPP driver and the rest of Kannel so it supports the addition of carrier-specific 'optional' parameters? There's one thing following standards to the exact letter, but another having to deal with some of these weird and wonderful aggregators/carriers out in the real world! Just my 1p worth.. On 6/5/06, Mi Reflejo [EMAIL PROTECTED] wrote: If you look closer into Simplewire_SMPP_ShortCodes.pdf, optionalparameters are included only in MT or MO messages (submit_sm and deliver_sm).You just need to take care sending interface_version v3.4 in bind operation.Nonetheless, kannel (as much as i know) doesn't handle optionalparameters in deliver_sm/submit_sm. So, maybe you want to take a look into the sources and make some modifications for your needs.If you need some help with that, just tell me.Regards,Martín Conte.On 6/5/06, Leonard [EMAIL PROTECTED] wrote: Firstly,There are optional paramters to SMPP 3.4. - Please review the specification, or look here: http://www.alvento.com/productos/sms/smpp/smpp34.pdf section 5.3 Optional parameter are required to set carrier and billing info mation for messagin into the USA where the aggregator does not supply NP lookups. (or they cost extra). What needs to be achieved can be found here: http://www.simplewire.com/downloads/files/Simplewire_SMPP_ShortCodes.pdf - Original Message - From: Mi Reflejo [EMAIL PROTECTED] To: Leonard [EMAIL PROTECTED] Cc: users@kannel.org Sent: Monday, June 05, 2006 5:59 PM Subject: Re: SMPP 3.4 Optional params There are no optional parameters in bind operations. (Maybe you are talking about system_type?) Kannel follows strictly SMPP specs. If you need to add any parameter which isn't in specs you should look to other way or take a look into sources by yourself :). Otherwise, if SimpleWire follows SMPP specs, kannel will help you. Regards, Martín Conte. On 6/5/06, Leonard [EMAIL PROTECTED] wrote: Hi All, I need to set optional params on a SMPP 3.4 Bind, specifically for a bind to SimpleWire. These optional params set carrier, billing and other requirements. Is there anyway to do this with Kannel, or will I have to use their XML interface? Regards Leonard
Re: dlr
If you send via sqlbox doing an insert into the database, it *should* use dlr-url. However, I don't think that bit is written yet :) You will probably also see problems with DLRs getting stuck in the kannel store as sqlbox does not 'ack' them to bearerbox. Alex On 5/12/06, Roman Yeryomin [EMAIL PROTECTED] wrote: Hi all,but what about when sending from database with sqlbox (simply inserting indatabase)? dlr_url should also work, right?but it seems that kannel doesn't fetch my ulencoded dlr_url defined indatabase (mysql)i'm stuck...does anyone know where could be the problem?i'm using kannel 1.4 with mysql 4.1RomanOn Friday 12 May 2006 17:31, Heru Tjatur wrote:: Hi Wayne, I set it in dlr-url when sending messages vi cgi-bin/sendsms. So, each time I send message, I put dlr-url containing my custom ID. Something like this: dlr-url="" href="http://127.0.0.1/smspapp/dlr.php?msgID=[mycustomID]dlrstatus=%">http://127.0.0.1/smspapp/dlr.php?msgID=[mycustomID]dlrstatus=% d[other parameter] Don't forget to url-encode your dlr-url when sending the mesaage via cgi-bin/sendsms? Hope it give you a hint ... --tjatur On Fri, 2006-05-12 at 13:40 +0800, Wayne Khan wrote: Hi Heru, How do you send the custom id to the smsc and get it back? I've tried the various kannel escape codes (%a, %b) but they don't seem to work. I'm doing some auditing function so there's a need to tie in the report with the sms... please help! Thanks! Heru Tjatur wrote: dear Issam, Here what I do to get the dlr in Kannel. Hope it could give you a light how to implement it for your needs. (1) I set up a url that will capture delivery status of the messages sent by kannel, base on a custom ID for the message (I defined that ID for each message sent). (2) When sending the message to the user, through cgi-bin/sendsms?, a drl-url containing custom ID is added with proper dlr-mask value. (3) That way, each incomming dlr will bring custom ID that will used to update my table regarding the delivery status of the message. (http://www.kannel.org/download/1.4.0/userguide-1.4.0/userguide.html#AE N3749) Hope this could help you... --tjatur On Thu, 2006-05-11 at 12:15 issam wrote: hello I use dlr-url parameter. when I send a message with kannel I attribute a unique ID to this message and Kannel give it another ID when he send it for delivery (----). I want to correspond in my base this ID and my ID to resend the message if he fail after validity period expiration. How can I do this big thanks for help - Original Message - From: Heru Tjatur [EMAIL PROTECTED] To: users@kannel.org Sent: Thursday, May 11, 2006 4:22 AM Subject: Re: dlr Dear issam, On Wed, 2006-05-10 at 13:47 +0100, issam wrote: Hello when I send a message with Kannel, he return a message like accepted for delivery but not the id used in dlr message. if I send 2 messages and I receive one dlr how can I know if this dlr is for first message or 2nd message. You could use set dlr-url parameter when sending the message. Each dlr message coming, it will its trigger dlr-url. So, you will know which message's dlr is comming. Hope it could help you.. --tjatur
Re: sqlbox, smsbox-route and dlr rerouting help!
Hi Anselmo, Yes I did get your email, sorry I meant to reply with some more in depth information but got sidetracked on other things. The problem I see is: 1. Insert message into sqlbox send_sms table 2. sqlbox picks it up, passes it to bearerbox 3. bearerbox passes it via smpp to carrier All fine so far, but then the problems come.. 4. dlr comes in to bearerbox via smpp 5. some dlrs get passed to sqlbox, but after a time (around 50-100 dlrs) it all jams up. kannel's store includes the 50-100 dlrs plus any further messages - also there are lots of 'ACK/' messages in the kannel store. The dlr never reaches the URL specified. I'll message you off-list to see what further information I can provide. Thanks, Alex On 5/12/06, Mi Reflejo [EMAIL PROTECTED] wrote: I'm reopening that issue. I dont know if you got the mail that i sendyou on 5/7.Hi Alex, i was doing a couple of tests. At First, every time that the smsbox got a delivery report the logssaid INFO: Starting to service ACK/. (it means that smsbox istrying to route the dlr as an MO). And sent_sms table had something like : | 147| MO | 1010 | 1157494777 | | ACK/ |()i did a checkout and then everything was fine.Please try a checkout, if it doesn't work please send me more debug logs and what are you doing exactly (The INSERT statment, for example)and i'll try to reproduce your error.Regards,AnselmoOn 5/7/06, Mi Reflejo [EMAIL PROTECTED] wrote: Hi Alex, i was doing a couple of tests. At First, every time that the smsbox got a delivery report the logs said INFO: Starting to service ACK/. (it means that smsbox is trying to route the dlr as an MO). And sent_sms table had something like : | 147| MO | 1010 | 1157494777 | | ACK/ | () i did a checkout and then everything was fine. Please try a checkout, if it doesn't work please send me more debug logs and what are you doing exactly (The INSERT statment, for example) and i'll try to reproduce your error. Regards, Anselmo
Re: sqlbox, smsbox-route and dlr rerouting help!
It's a long story to explain why (especially since we don't use Euros here in the UK), but I have just under €100 in cash sitting on my desk waiting to bribe someone to fix this problem :) Any takers? I'm stuck without delivery reporting at the moment and it's not good :( On 5/3/06, Rene Kluwen [EMAIL PROTECTED] wrote: I think what happening is: MO traffic is routed to your smsbox (through sqlbox). DLR's are routed to sqlbox and end there. Rene Kluwen Chimit -Original Message-From: Alex Kinch [mailto:[EMAIL PROTECTED] ] Sent: dinsdag 2 mei 2006 23:17To: Rene KluwenCc: users@kannel.orgSubject: Re: sqlbox, smsbox-route and dlr rerouting help! 1. Ok, understood. 2. I am seeing messages in the store file with the content of 'ACK/' - although they look like normal DLR messages (with source, recipient, smsc, etc). Are these just DLRs or something else? Sorry if that's a really stupid question, it's been a long day :) Guess the question is how quick can we work together to fix sqlbox to ACK? I can live without DLR for a while as it's not difficult to parse the sqlbox database to do DLR stuff. One thing that is strange, it's only DLRs that remain in the store file. Normal MO traffic gets through to sqlbox ok. Is it because by the fact that smsbox is receiving MO traffic that the ACKing is being carried out, but because DLRs aren't going through it's not happening for those? Alex On 5/2/06, Rene Kluwen [EMAIL PROTECTED] wrote: 1. Yes, it differs if you send messages via smsbox or sqlbox 2. I think they changed behaviour bearerbox to require an ACK at the moment that delayed writing was introduced (if I am not mistaken). Rene Kluwen Chimit -Original Message-From: Alex Kinch [mailto: [EMAIL PROTECTED]]Sent: dinsdag 2 mei 2006 21:20To: Rene KluwenCc: users@kannel.org Subject: Re: sqlbox, smsbox-route and dlr rerouting help! Sorry, my misunderstanding! But I seem to remember being able to run sqlbox on a previous build of Kannel (quite a while back) without any problems. But then I was sending messages via smsbox, not sqlbox. Alex On 5/2/06, Rene Kluwen [EMAIL PROTECTED] wrote: Sorry... let me correct this... I do know what is going wrong... sqlbox doesn't do message ack-ing nor DLR requests... It is a missing feature... So only the messages are acked that are being relayed through smsbox. Rene Kluwen Chimit -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Alex KinchSent: dinsdag 2 mei 2006 19:26 To: users@kannel.orgSubject: sqlbox, smsbox-route and dlr rerouting help! Hi, Hopefully someone can solve this mystery for me. I'm using sqlbox compiled into cvs-20060424, using MySQL 4.1.18. Incoming messages weren't being routed into sqlbox, so I added: group = smsbox-routesmsbox-id = smsboxsmsc-ids = (smsc1);(smsc2) (smsc1) and (smsc2) being the names of some SMPP connections. Everything is fine now, however when delivery reports come back in some of them go into sqlbox but appear not to be ack'd by sqlbox - or for some other reason remain in the Kannel store. Anything between 50-200 DLRs makeit to sqlbox before it seems to hit a limit and no more come in to the table. None of the DLR entries in sqlbox seem to go any further so the DLR URL is not called either. I do notice throughout the log the following entries for both(smsc1) and (smsc2) as well: INFO: DLR rerouting for smsc id (smsc1) disabled I have been speaking to Rene (Kluwen) and working through this issue with him, but neither of us are really too sure what is going wrong. Maybe Stipe or someone could advise me if these problems may be caused by something to do with lack of DLR rerouting, and if so, how do I enable the rerouting? Kannel.conf is below. Thanks in advance! Alex -- group = coreadmin-port = 13000wapbox-port = 13002admin-port-ssl = nosmsbox-port = 13001admin-password = *REMOVED*status-password = *REMOVED*admin-deny-ip = *REMOVED*admin-allow-ip = *REMOVED* log-file = /home/kannel/logs/kannel.loglog-level = 0box-deny-ip = *REMOVED*box-allow-ip = *REMOVED*unified-prefix = +44,0044,44,0store-file = /home/kannel/logs/kannel.store dlr-storage = mysqlwdp-interface-name = * # SQL BOX CONFIG group = mysql-connectionid = dlr-dbhost = localhostusername = *REMOVED*password = *REMOVED*database = *REMOVED*max-connections = 5 group = mysql-connectionid = sqlbox-dbhost = localhostusername = *REMOVED*password = *REMOVED*database = *REMOVED*max-connections = 10 group = dlr-dbid = dlr-dbtable = dlrfield-smsc = smscfield-timestamp = tsfield-destination = destinationfield-source = sourcefield-service = servicefield-url = "">field-mask = mask field-status = statusfield-boxc-id = boxc # SQL BOX CONFIG group = sqlbox# id corresponds to id in group = mysql-connection.# this is analogous to id in group = dlr-dbid = sqlbox-db# smsbox-id indicates the box where SQL-injected messages appear to be coming fr smsbox-id = sqlbox# bearerbox ho
Re: DLR : why I got this log on smsclogfile?
It's because you have received a delivery report that doesn't match up to anything in Kannel's DLR table. Try sending a message, noting down the message id that Kannel logs to the DLR table, then see what DLR it is looking for when the report comes back. It's possible that you'll need to use the msg-id-typeoption in your SMPP configuration. Alex On 5/5/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: 2006-05-05 16:53:05 [4326] [7] DEBUG: DLR[internal]: Looking for DLRsmsc=my_route, ts=9093560, dst=393386776419, type=1 2006-05-05 16:53:05 [4326] [7] WARNING: DLR[internal]: DLR forDST393386776419not found.2006-05-05 16:53:05 [4326] [7] ERROR: SMPP[my_route]: got DLR but could notfindmessage or was not interested in it id9093560 dstsergio, type1 Was NOT interested?? Who?? I hope not me, i'm trying to get them from a lot oftime!Could anybody explain how to fix this?Thank you!
Re: DLR : why I got this log on smsclogfile?
Hello, I've connected to Logica SMSCs without a problem. Use: msg-id-type = 0x01 which will make Kannel expect the submit_sm_resp in hex and the deliver_sm in decimal. Alex On 5/5/06, Ilija Cutura google [EMAIL PROTECTED] wrote: Hi All, Does anyone have expirience with DLR handling using Logica SMSC simulator? Just to get a common understanding. This, what is in Kannel context called DLR, is actually Delivery Notification according to SMPP 3.4 spec. Real DLR actually comes in the message body at the end of delivery. Am I correct ? So, when using Logica SMSC simulator there are different numbers being reported as message ID refering to the same message:. 1) After sending the message there comes Submit Response with mesage ID X (for example). This message ID is being taken by Kannel and written into DLR database together with other data. 2) Than comes Delivery notification with status 8 (this is what is meant by DLR in Kannel vocabulary, if I understood well). Problem is that this notification contains Message ID (lets say Y) which looks completely different from the message ID obtained in step 1 (Y X). I have no clue how to relate these two numbers, although I am 100% sure they refer to the same message. 3) At the end comes Real DLR having all those data in the message body which are given in the appendix of SMPP 3.4 specs. Among those data there is again that number X given as message ID (the same as the one from the Submit response). QUESTIONS: Q1- Is my understanding that Kannel DLR database actualy deals with Delivery Notifications and not Real DLRs, as described in SMPP 3.4 spec, correct ? Q2- did anyone managed the succesfull usage of Kannel DLR database when testing with Logica SMSC simulator Q3 - do you allways have the situation in Real Life (for those who are using the life network systems) that the Delivery Notification Contains Message ID exactly appropriate to the one obtained in Sumbit Response when sending original message ? Q4 - Could msg-id-typeparameter be helpfull to test with Logica SMSC as well ? Q5 - is there any way of automatic handling of real DLRs with Kannel, and not only notifications ? Q6 - is message ID the only parameter that could be used for matching Delivery Notifications in Kannel DLR database, or something else could be used as well ? Thanks, Ilija - Original Message - From: Alex Kinch To: [EMAIL PROTECTED] Cc: users@kannel.org Sent: Friday, May 05, 2006 5:06 PM Subject: Re: DLR : why I got this log on smsclogfile? It's because you have received a delivery report that doesn't match up to anything in Kannel's DLR table. Try sending a message, noting down the message id that Kannel logs to the DLR table, then see what DLR it is looking for when the report comes back. It's possible that you'll need to use the msg-id-typeoption in your SMPP configuration. Alex On 5/5/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: 2006-05-05 16:53:05 [4326] [7] DEBUG: DLR[internal]: Looking for DLRsmsc=my_route, ts=9093560, dst=393386776419, type=1 2006-05-05 16:53:05 [4326] [7] WARNING: DLR[internal]: DLR forDST393386776419not found.2006-05-05 16:53:05 [4326] [7] ERROR: SMPP[my_route]: got DLR but could notfindmessage or was not interested in it id9093560 dstsergio, type1 Was NOT interested?? Who?? I hope not me, i'm trying to get them from a lot oftime!Could anybody explain how to fix this?Thank you!
sqlbox, smsbox-route and dlr rerouting help!
Hi, Hopefully someone can solve this mystery for me. I'm using sqlbox compiled into cvs-20060424, using MySQL 4.1.18. Incoming messages weren't being routed into sqlbox, so I added: group = smsbox-routesmsbox-id = smsboxsmsc-ids = (smsc1);(smsc2) (smsc1) and (smsc2) being the names of some SMPP connections. Everything is fine now, however when delivery reports come back in some of them go into sqlbox but appear not to be ack'd by sqlbox - or for some other reason remain in the Kannel store. Anything between 50-200 DLRs makeit to sqlbox before it seems to hit a limit and no more come in to the table. None of the DLR entries in sqlbox seem to go any further so the DLR URL is not called either. I do notice throughout the log the following entries for both(smsc1) and (smsc2) as well: INFO: DLR rerouting for smsc id (smsc1) disabled I have been speaking to Rene (Kluwen) and working through this issue with him, but neither of us are really too sure what is going wrong. Maybe Stipe or someone could advise me if these problems may be caused by something to do with lack of DLR rerouting, and if so, how do I enable the rerouting? Kannel.conf is below. Thanks in advance! Alex -- group = coreadmin-port = 13000wapbox-port = 13002admin-port-ssl = nosmsbox-port = 13001admin-password = *REMOVED*status-password = *REMOVED*admin-deny-ip = *REMOVED*admin-allow-ip = *REMOVED* log-file = /home/kannel/logs/kannel.loglog-level = 0box-deny-ip = *REMOVED*box-allow-ip = *REMOVED*unified-prefix = +44,0044,44,0store-file = /home/kannel/logs/kannel.store dlr-storage = mysqlwdp-interface-name = * # SQL BOX CONFIG group = mysql-connectionid = dlr-dbhost = localhostusername = *REMOVED*password = *REMOVED*database = *REMOVED*max-connections = 5 group = mysql-connectionid = sqlbox-dbhost = localhostusername = *REMOVED*password = *REMOVED*database = *REMOVED*max-connections = 10 group = dlr-dbid = dlr-dbtable = dlrfield-smsc = smscfield-timestamp = tsfield-destination = destinationfield-source = sourcefield-service = servicefield-url = "">field-mask = mask field-status = statusfield-boxc-id = boxc # SQL BOX CONFIG group = sqlbox# id corresponds to id in group = mysql-connection.# this is analogous to id in group = dlr-dbid = sqlbox-db# smsbox-id indicates the box where SQL-injected messages appear to be coming fr smsbox-id = sqlbox# bearerbox host to connect tobearerbox-host = localhost# smsbox port to be listening onsmsbox-port = 13005smsbox-port-ssl = false# sql-log-table is the table used to log all sent messages sql-log-table = sent_sms# sql-insert-table is the table that is monitored for new messages to sendsql-insert-table = send_sms# global sender: If no sender is specified in sql-insert-table then this# value is used. global-sender = 06121log-file = /home/kannel/logs/sqlbox.loglog-level = 0ssl-client-certkey-file = ssl-server-cert-file = ssl-server-key-file = ssl-trusted-ca-file = # SMSC CONNECTIONS group = smscsmsc = smppsmsc-id = (smsc1)allowed-smsc-id = (smsc1);(smsc1)_01host = *REMOVED*port = *REMOVED*transceiver-mode = truesystem-type = *REMOVED*interface-version = 33smsc-username = *REMOVED* smsc-password = *REMOVED*source-addr-autodetect = truedest-addr-ton = 1dest-addr-npi = 1msg-id-type = 0x01alt-charset = HPROMAN8 group = smscsmsc = smppsmsc-id = (smsc2)allowed-smsc-id = (smsc2)host = *REMOVED*port = *REMOVED*interface-version = 34transceiver-mode = truesystem-type = *REMOVED*smsc-username = *REMOVED* smsc-password = *REMOVED*source-addr-ton = 0source-addr-npi = 0msg-id-type = 0x01 group = smscsmsc = smppsmsc-id = (smsc2)allowed-smsc-id = (smsc2)host = *REMOVED*port = *REMOVED*interface-version = 34transceiver-mode = truesystem-type = *REMOVED*smsc-username = *REMOVED* smsc-password = *REMOVED*source-addr-ton = 0source-addr-npi = 0msg-id-type = 0x01 # SMSBOX SETUP group = smsboxbearerbox-host = localhost# the following is a sqlbox extension!!bearerbox-is-sqlbox = truesmsbox-id = smsboxsendsms-port = 13013sendsms-port-ssl = no#sendsms-chars = 0123456789 +- log-file = /home/kannel/logs/smsbox.logaccess-log = /home/kannel/logs/smsbox_access.loglog-level = 0 # SEND-SMS USERS group = sendsms-userusername = *REMOVED*password = *REMOVED*user-deny-ip = *REMOVED*user-allow-ip = *REMOVED* # SERVICES group = sms-servicekeyword = defaultget-url = "">catch-all = truemax-messages = 0accepted-smsc = *REMOVED* group = sms-servicekeyword = stopget-url = "">max-messages = 0accepted-smsc = *REMOVED* group = sms-servicekeyword = defaultget-url = "">catch-all = truemax-messages = 0accepted-smsc = (smsc2) group = smsbox-routesmsbox-id = smsboxsmsc-ids = (smsc1);(smsc2)
Re: sqlbox, smsbox-route and dlr rerouting help!
Sorry, my misunderstanding! But I seem to remember being able to run sqlbox on a previous build of Kannel (quite a while back) without any problems. But then I was sending messages via smsbox, not sqlbox. Alex On 5/2/06, Rene Kluwen [EMAIL PROTECTED] wrote: Sorry... let me correct this... I do know what is going wrong... sqlbox doesn't do message ack-ing nor DLR requests... It is a missing feature... So only the messages are acked that are being relayed through smsbox. Rene Kluwen Chimit -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Alex KinchSent: dinsdag 2 mei 2006 19:26 To: users@kannel.orgSubject: sqlbox, smsbox-route and dlr rerouting help! Hi, Hopefully someone can solve this mystery for me. I'm using sqlbox compiled into cvs-20060424, using MySQL 4.1.18. Incoming messages weren't being routed into sqlbox, so I added: group = smsbox-routesmsbox-id = smsboxsmsc-ids = (smsc1);(smsc2) (smsc1) and (smsc2) being the names of some SMPP connections. Everything is fine now, however when delivery reports come back in some of them go into sqlbox but appear not to be ack'd by sqlbox - or for some other reason remain in the Kannel store. Anything between 50-200 DLRs makeit to sqlbox before it seems to hit a limit and no more come in to the table. None of the DLR entries in sqlbox seem to go any further so the DLR URL is not called either. I do notice throughout the log the following entries for both(smsc1) and (smsc2) as well: INFO: DLR rerouting for smsc id (smsc1) disabled I have been speaking to Rene (Kluwen) and working through this issue with him, but neither of us are really too sure what is going wrong. Maybe Stipe or someone could advise me if these problems may be caused by something to do with lack of DLR rerouting, and if so, how do I enable the rerouting? Kannel.conf is below. Thanks in advance! Alex -- group = coreadmin-port = 13000wapbox-port = 13002admin-port-ssl = nosmsbox-port = 13001admin-password = *REMOVED*status-password = *REMOVED*admin-deny-ip = *REMOVED*admin-allow-ip = *REMOVED* log-file = /home/kannel/logs/kannel.loglog-level = 0box-deny-ip = *REMOVED*box-allow-ip = *REMOVED*unified-prefix = +44,0044,44,0store-file = /home/kannel/logs/kannel.store dlr-storage = mysqlwdp-interface-name = * # SQL BOX CONFIG group = mysql-connectionid = dlr-dbhost = localhostusername = *REMOVED*password = *REMOVED*database = *REMOVED*max-connections = 5 group = mysql-connectionid = sqlbox-dbhost = localhostusername = *REMOVED*password = *REMOVED*database = *REMOVED*max-connections = 10 group = dlr-dbid = dlr-dbtable = dlrfield-smsc = smscfield-timestamp = tsfield-destination = destinationfield-source = sourcefield-service = servicefield-url = "">field-mask = mask field-status = statusfield-boxc-id = boxc # SQL BOX CONFIG group = sqlbox# id corresponds to id in group = mysql-connection.# this is analogous to id in group = dlr-dbid = sqlbox-db# smsbox-id indicates the box where SQL-injected messages appear to be coming fr smsbox-id = sqlbox# bearerbox host to connect tobearerbox-host = localhost# smsbox port to be listening onsmsbox-port = 13005smsbox-port-ssl = false# sql-log-table is the table used to log all sent messages sql-log-table = sent_sms# sql-insert-table is the table that is monitored for new messages to sendsql-insert-table = send_sms# global sender: If no sender is specified in sql-insert-table then this# value is used. global-sender = 06121log-file = /home/kannel/logs/sqlbox.loglog-level = 0ssl-client-certkey-file = ssl-server-cert-file = ssl-server-key-file = ssl-trusted-ca-file = # SMSC CONNECTIONS group = smscsmsc = smppsmsc-id = (smsc1)allowed-smsc-id = (smsc1);(smsc1)_01host = *REMOVED*port = *REMOVED*transceiver-mode = truesystem-type = *REMOVED*interface-version = 33smsc-username = *REMOVED* smsc-password = *REMOVED*source-addr-autodetect = truedest-addr-ton = 1dest-addr-npi = 1msg-id-type = 0x01alt-charset = HPROMAN8 group = smscsmsc = smppsmsc-id = (smsc2)allowed-smsc-id = (smsc2)host = *REMOVED*port = *REMOVED*interface-version = 34transceiver-mode = truesystem-type = *REMOVED*smsc-username = *REMOVED* smsc-password = *REMOVED*source-addr-ton = 0source-addr-npi = 0msg-id-type = 0x01 group = smscsmsc = smppsmsc-id = (smsc2)allowed-smsc-id = (smsc2)host = *REMOVED*port = *REMOVED*interface-version = 34transceiver-mode = truesystem-type = *REMOVED*smsc-username = *REMOVED* smsc-password = *REMOVED*source-addr-ton = 0source-addr-npi = 0msg-id-type = 0x01 # SMSBOX SETUP group = smsboxbearerbox-host = localhost# the following is a sqlbox extension!!bearerbox-is-sqlbox = truesmsbox-id = smsboxsendsms-port = 13013sendsms-port-ssl = no#sendsms-chars = 0123456789 +- log-file = /home/kannel/logs/smsbox.logaccess-log = /home/kannel/logs/smsbox_access.loglog-level = 0 # SEND-SMS USERS group = sendsms-userusername = *REMOVED*password = *REMOVED*user-deny-ip = *REMOVED*user-allow-ip = *REMOVED* # SERVICES group
Re: sqlbox, smsbox-route and dlr rerouting help!
1. Ok, understood. 2. I am seeing messages in the store file with the content of 'ACK/' - although they look like normal DLR messages (with source, recipient, smsc, etc). Are these just DLRs or something else? Sorry if that's a really stupid question, it's been a long day :) Guess the question is how quick can we work together to fix sqlbox to ACK? I can live without DLR for a while as it's not difficult to parse the sqlbox database to do DLR stuff. One thing that is strange, it's only DLRs that remain in the store file. Normal MO traffic gets through to sqlbox ok. Is it because by the fact that smsbox is receiving MO traffic that the ACKing is being carried out, but because DLRs aren't going through it's not happening for those? Alex On 5/2/06, Rene Kluwen [EMAIL PROTECTED] wrote: 1. Yes, it differs if you send messages via smsbox or sqlbox 2. I think they changed behaviour bearerbox to require an ACK at the moment that delayed writing was introduced (if I am not mistaken). Rene Kluwen Chimit -Original Message-From: Alex Kinch [mailto: [EMAIL PROTECTED]]Sent: dinsdag 2 mei 2006 21:20To: Rene KluwenCc: users@kannel.org Subject: Re: sqlbox, smsbox-route and dlr rerouting help! Sorry, my misunderstanding! But I seem to remember being able to run sqlbox on a previous build of Kannel (quite a while back) without any problems. But then I was sending messages via smsbox, not sqlbox. Alex On 5/2/06, Rene Kluwen [EMAIL PROTECTED] wrote: Sorry... let me correct this... I do know what is going wrong... sqlbox doesn't do message ack-ing nor DLR requests... It is a missing feature... So only the messages are acked that are being relayed through smsbox. Rene Kluwen Chimit -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Alex KinchSent: dinsdag 2 mei 2006 19:26 To: users@kannel.orgSubject: sqlbox, smsbox-route and dlr rerouting help! Hi, Hopefully someone can solve this mystery for me. I'm using sqlbox compiled into cvs-20060424, using MySQL 4.1.18. Incoming messages weren't being routed into sqlbox, so I added: group = smsbox-routesmsbox-id = smsboxsmsc-ids = (smsc1);(smsc2) (smsc1) and (smsc2) being the names of some SMPP connections. Everything is fine now, however when delivery reports come back in some of them go into sqlbox but appear not to be ack'd by sqlbox - or for some other reason remain in the Kannel store. Anything between 50-200 DLRs makeit to sqlbox before it seems to hit a limit and no more come in to the table. None of the DLR entries in sqlbox seem to go any further so the DLR URL is not called either. I do notice throughout the log the following entries for both(smsc1) and (smsc2) as well: INFO: DLR rerouting for smsc id (smsc1) disabled I have been speaking to Rene (Kluwen) and working through this issue with him, but neither of us are really too sure what is going wrong. Maybe Stipe or someone could advise me if these problems may be caused by something to do with lack of DLR rerouting, and if so, how do I enable the rerouting? Kannel.conf is below. Thanks in advance! Alex -- group = coreadmin-port = 13000wapbox-port = 13002admin-port-ssl = nosmsbox-port = 13001admin-password = *REMOVED*status-password = *REMOVED*admin-deny-ip = *REMOVED*admin-allow-ip = *REMOVED* log-file = /home/kannel/logs/kannel.loglog-level = 0box-deny-ip = *REMOVED*box-allow-ip = *REMOVED*unified-prefix = +44,0044,44,0store-file = /home/kannel/logs/kannel.store dlr-storage = mysqlwdp-interface-name = * # SQL BOX CONFIG group = mysql-connectionid = dlr-dbhost = localhostusername = *REMOVED*password = *REMOVED*database = *REMOVED*max-connections = 5 group = mysql-connectionid = sqlbox-dbhost = localhostusername = *REMOVED*password = *REMOVED*database = *REMOVED*max-connections = 10 group = dlr-dbid = dlr-dbtable = dlrfield-smsc = smscfield-timestamp = tsfield-destination = destinationfield-source = sourcefield-service = servicefield-url = "">field-mask = mask field-status = statusfield-boxc-id = boxc # SQL BOX CONFIG group = sqlbox# id corresponds to id in group = mysql-connection.# this is analogous to id in group = dlr-dbid = sqlbox-db# smsbox-id indicates the box where SQL-injected messages appear to be coming fr smsbox-id = sqlbox# bearerbox host to connect tobearerbox-host = localhost# smsbox port to be listening onsmsbox-port = 13005smsbox-port-ssl = false# sql-log-table is the table used to log all sent messages sql-log-table = sent_sms# sql-insert-table is the table that is monitored for new messages to sendsql-insert-table = send_sms# global sender: If no sender is specified in sql-insert-table then this# value is used. global-sender = 06121log-file = /home/kannel/logs/sqlbox.loglog-level = 0ssl-client-certkey-file = ssl-server-cert-file = ssl-server-key-file = ssl-trusted-ca-file = # SMSC CONNECTIONS group = smscsmsc = smppsmsc-id = (smsc1)allowed-smsc-id = (smsc1);(smsc1)_01host = *REMOVED*po
Re: compatibility
Maybe 'will Kannel support Nokia 6230i, 6600 or 3650 phones' :) On 11/3/05, Julien Buratto [EMAIL PROTECTED] wrote: Teo wrote: Hi at all! Support Kannel the mobile phone Nokia 6230i or Nokia 6600 or 3650? Thanks! MatteoWhat do U mean ? It's a strange question...J
Re: Front End for Kannel
I know Rene Kluwen has been working on a sqlbox project for Kannel that should do what you want, although can't remember how far he got. We've done some testing on our side and it seems to work, but you'd be best to ask him yourself. Or wait until he reads this message on the list and he'll reply :-) Alex - Original Message - From: Rory Campbell-Lange [EMAIL PROTECTED] To: Mikko Kiesil? [EMAIL PROTECTED] Cc: Kannel Users [EMAIL PROTECTED] Sent: Wednesday, March 31, 2004 2:41 PM Subject: Re: Front End for Kannel I've suggested a persistent database store in the past, with the idea that DLR reports could be reported against objects in the database in a simple way. Postgresql, with its support for triggers and custom functions (and BSD license) is a good choice. However this would make Kannel dependant on a database package, which isn't really required. I have a rather crude system which is a version of this system, where messages aimed at and coming out of Kannel are stored in a database. A looping perl script passes the SMS to Kannel or passes an SMS to a receiving url. I think there might be something like this in the contrib directory already. Anyhow, I call this smshub, and I can share if anyone is interested. Rory On 31/03/04, Mikko Kiesil? ([EMAIL PROTECTED]) wrote: Kannel also storing/dumbing the SMS in store-file. If that part is modified to store in such a manner so that the clients can access it. -- Rory Campbell-Lange [EMAIL PROTECTED] www.campbell-lange.net
HLR lookup
Hi gang, Can't remember who it was, but someone on here said they could do HLR lookups on UK MSISDNs to find out what network they're on. Got a customer who wants to do about 1m lookupsa month. Replies off-list please! Thanks Alex
Re: SMS TCP/IP
Hi Richard, From experience you have to be doing quite a large amount of traffic per month before you can get a direct IP connection to a networks SMSC. Some also will charge you lots of money in setup and monthly access, so you have to weigh up the options. Understand what you mean about competing with yourself, but I think there's a big enough market out there without necessarily running into the providers suggested. Don't forget, in some places you've also got the actual mobile networks themselves competing in the same marketplace. For instance, the minimum cost of delivering a message to a UK network directly is 3p plus whatever markup the operator/aggregator adds on. You're then up against the operators themselves undercutting you by offering 3p texts to their own customers. Alex - Original Message - From: Richard Bottoms [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, February 26, 2004 9:35 PM Subject: Re: SMS TCP/IP www.smsgui.com www.bulksms.com www.smsxchange.com look for sms gateways on google Appreciate the referral, but what I am trying to do is get past these guys to go directly to the SMS Center which presumably is provided by ATT, or Cingular or some other telcom. As I understand how Kannel works, I don't need a provider like bulksms.com to send my mesaages. Instead I can plug directly into the network Gateway itself or use a GSM equipped phone/modem. If I go through a provider I am competeing with myself and paying their markup. r.b.
[off-topic] OTA SIM update
Hi gang, Hopefully someone can enlighten me on this one. What exactly can be changed byan over-the-air SIM update? Would it be possible for a non-GSM network operator (eg spammers!) to send SIM updates? Had a few emails from people today saying they'd got SIM updates from Orange, and when they called Orange they said they hadn't sent any updates out, and they themselves had received a heap of people calling about strange SIM updates. Thanks, Alex
Re: Specifying a number when sending SMS
John, I understand you're on a tight budget, but there are providers out there that'll give you the ability to set your own "from" number on a SMPP connection - and won't charge you any rental or setup for the service (you obviously have to pay for the texts!). Not a recommendation as such, but have you looked at someone like Clickatell (http://www.clickatell.com)? Alex - Original Message - From: Nicholas Calugar To: 'John Vincent Mombay' Cc: [EMAIL PROTECTED] Sent: Tuesday, February 10, 2004 1:06 AM Subject: RE: Specifying a number when sending SMS Will this application be available to a closed group (i.e. colleagues, students, etc) or to an open group? If the former is the case, you can train your users never to reply to the message. Most mobile devices can pick a number from the body of the message, and either place a call or send a text message to it. Nicholas Calugar 619-546-9803 866-404-2428 Chatter 3577 4th Ave. San Diego, CA 92103 www.2chatter.com -Original Message-From: John Vincent Mombay [mailto:[EMAIL PROTECTED] Sent: Monday, February 09, 2004 4:35 PMTo: [EMAIL PROTECTED]Subject: RE: Specifying a number when sending SMS First thank you all for that insight. So does anyone have an idea how I can overcome this? Im on a tight budget and cant simply afford to use any other methods but by using a real mobile phone for this. -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nicholas CalugarSent: Tuesday, February 10, 2004 1:45 AMTo: [EMAIL PROTECTED]Subject: RE: Specifying a number when sending SMS I also havent heard of a GSM Modem allowing the spoofing of the FROM phone number. Think about the havoc that would ensue if you could send an SMS from your phone but it looked like it was coming from another persons phone number. I understand that your use is legitimate but it is simply the only way they could implement the GSM network. You probably can do this if you used some sort of provider for sending SMS. Nicholas Calugar 619-546-9803 866-404-2428 Chatter 3577 4th Ave. San Diego, CA 92103 www.2chatter.com -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Navjot SinghSent: Monday, February 09, 2004 2:49 AMTo: [EMAIL PROTECTED]Subject: RE: Specifying a number when sending SMS hope you mean setting FROM value. Well, that depends upon the SMSC. In my experience, most of the SMSC don't allow. HTH Navjot Singh -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of John Vincent MombaySent: Monday, February 09, 2004 1:26 PMTo: [EMAIL PROTECTED]Subject: Specifying a number when sending SMS Hi guys, Can anyone give me an idea if it is possible to specify a number when sending out an SMS via the http command? Id like to do this since whenever people send SMS messages from the browser they cant possibly receive any replies from their mobile phones. I set up kannnel with a virtual SMSC using a sony ericsson t68i. It works well, though I needed to specify the number which I have readily available on a database that is retrieve based on who is logged in and sending it. Hope you can help me on this. Regards, JV
Re: DLR problems....
Dave, Add msg-id-type = 0x01 to the smsc group where you've got your MBlox connections, and it should do the trick. Alex - Original Message - From: Dave Holmes [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, January 30, 2004 12:28 PM Subject: DLR problems Guys, Hopefully you may be able to help me with something I have been tearing my hair out about all morning, I have compiled, configured and installed Kannel on one of our servers, hooked it up to our SMSC and been able to send SMS messages using the HTTP interface No problems so far :) I can't however seem to get the delivery notifications to work properly, I have run the bearer box in debug mode, which shows the message going through and the DLR being created with my URL. The SMSC then sends the delivery reports for ACKED and DELIVERED It would appear that Kannel unpacks the PDU no problem but then fails to find the DLR within the internal storage, and does not make the callback to my URL Has anybody got any suggestions where to start looking ! Thanks in advance Dave Holmes 2004-01-30 11:46:52 [7] DEBUG: boxc_receiver: sms received 2004-01-30 11:46:52 [5] DEBUG: SMPP[SMPP:smpp1.mblox.com:3200/3200:EurSoftDev:]: Sending PDU: 2004-01-30 11:46:52 [5] DEBUG: SMPP PDU 0x80d10b0 dump: 2004-01-30 11:46:52 [5] DEBUG: type_name: submit_sm 2004-01-30 11:46:52 [5] DEBUG: command_id: 4 = 0x0004 2004-01-30 11:46:52 [5] DEBUG: command_status: 0 = 0x 2004-01-30 11:46:52 [5] DEBUG: sequence_number: 5 = 0x0005 2004-01-30 11:46:52 [5] DEBUG: service_type: NULL 2004-01-30 11:46:52 [5] DEBUG: source_addr_ton: 2 = 0x0002 2004-01-30 11:46:52 [5] DEBUG: source_addr_npi: 1 = 0x0001 2004-01-30 11:46:52 [5] DEBUG: source_addr: 13013 2004-01-30 11:46:52 [5] DEBUG: dest_addr_ton: 2 = 0x0002 2004-01-30 11:46:52 [5] DEBUG: dest_addr_npi: 1 = 0x0001 2004-01-30 11:46:52 [5] DEBUG: destination_addr: 447966013309 2004-01-30 11:46:52 [5] DEBUG: esm_class: 3 = 0x0003 2004-01-30 11:46:52 [5] DEBUG: protocol_id: 0 = 0x 2004-01-30 11:46:52 [5] DEBUG: priority_flag: 0 = 0x 2004-01-30 11:46:52 [5] DEBUG: schedule_delivery_time: NULL 2004-01-30 11:46:52 [5] DEBUG: validity_period: NULL 2004-01-30 11:46:52 [5] DEBUG: registered_delivery: 1 = 0x0001 2004-01-30 11:46:52 [5] DEBUG: replace_if_present_flag: 0 = 0x 2004-01-30 11:46:52 [5] DEBUG: data_coding: 0 = 0x 2004-01-30 11:46:52 [5] DEBUG: sm_default_msg_id: 0 = 0x 2004-01-30 11:46:52 [5] DEBUG: sm_length: 0 = 0x 2004-01-30 11:46:52 [5] DEBUG: short_message: this is anther test 2004-01-30 11:46:52 [5] DEBUG: SMPP PDU dump ends. 2004-01-30 11:46:52 [5] DEBUG: SMPP[SMPP:smpp1.mblox.com:3200/3200:EurSoftDev:]: Got PDU: 2004-01-30 11:46:52 [5] DEBUG: SMPP PDU 0x80d10b0 dump: 2004-01-30 11:46:52 [5] DEBUG: type_name: submit_sm_resp 2004-01-30 11:46:52 [5] DEBUG: command_id: 2147483652 = 0x8004 2004-01-30 11:46:52 [5] DEBUG: command_status: 0 = 0x 2004-01-30 11:46:52 [5] DEBUG: sequence_number: 5 = 0x0005 2004-01-30 11:46:52 [5] DEBUG: message_id: 0026e9ece 2004-01-30 11:46:52 [5] DEBUG: SMPP PDU dump ends. 2004-01-30 11:46:52 [5] DEBUG: Adding DLR smsc=SMPP:smpp1.mblox.com:3200/3200:EurSoftDev:, ts=0026e9ece, src=13013, dst=447966013309, mask=31 2004-01-30 11:46:52 [5] DEBUG: Looking for DLR smsc=SMPP:smpp1.mblox.com:3200/3200:EurSoftDev:, ts=0026e9ece, dst=447966013309, type=12 2004-01-30 11:46:52 [5] DEBUG: created DLR message for URL http://smsrelay.e-msg.co.uk/testing.php?callbacktype= 2004-01-30 11:46:52 [5] INFO: dlr not destroyed, still waiting for other delivery report 2004-01-30 11:46:52 [8] DEBUG: boxc_sender: sent message to 127.0.0.1 2004-01-30 11:46:52 [7] DEBUG: boxc_receiver: got ack 2004-01-30 11:46:52 [5] DEBUG: SMPP[SMPP:smpp1.mblox.com:3200/3200:EurSoftDev:]: Got PDU: 2004-01-30 11:46:52 [5] DEBUG: SMPP PDU 0x80d1cf8 dump: 2004-01-30 11:46:52 [5] DEBUG: type_name: deliver_sm 2004-01-30 11:46:52 [5] DEBUG: command_id: 5 = 0x0005 2004-01-30 11:46:52 [5] DEBUG: command_status: 0 = 0x 2004-01-30 11:46:52 [5] DEBUG: sequence_number: 1 = 0x0001 2004-01-30 11:46:52 [5] DEBUG: service_type: NULL 2004-01-30 11:46:52 [5] DEBUG: source_addr_ton: 0 = 0x 2004-01-30 11:46:52 [5] DEBUG: source_addr_npi: 0 = 0x 2004-01-30 11:46:52 [5] DEBUG: source_addr: 447966013309 2004-01-30 11:46:52 [5] DEBUG: dest_addr_ton: 0 = 0x 2004-01-30 11:46:52 [5] DEBUG: dest_addr_npi: 0 = 0x 2004-01-30 11:46:52 [5] DEBUG: destination_addr: NULL 2004-01-30 11:46:52 [5] DEBUG: esm_class: 4 = 0x0004 2004-01-30 11:46:52 [5] DEBUG: protocol_id: 0 = 0x 2004-01-30 11:46:52 [5] DEBUG: priority_flag: 0 = 0x 2004-01-30 11:46:52 [5] DEBUG: schedule_delivery_time: NULL 2004-01-30 11:46:52 [5] DEBUG:
Re: SQLBOX [Was Re: Feature request:storingincoming/outgoingmessagesin database]
Hi Rene I think Stipe was working on something before Christmas, but some nasty non-C-programming car thiefs stole his laptop. Still haven't had any other offers, so you're welcome to take up the offer. Of course comments from Stipe, Alex, everyone else would be appreciated :-) Alex - Original Message - From: Rene Kluwen To: [EMAIL PROTECTED] Org Sent: Saturday, January 17, 2004 10:49 PM Subject: FW: SQLBOX [Was Re: Feature request:storingincoming/outgoingmessagesin database] Sorry, forgot to reply to the list... I thought this so-called "SQLBOX" was already being developed? And waiting for release in the same manner as the SMPP-BOX? Or am I wrong here? Any case, if I am wrong, I am about ready to pick up the offer on rentacoder. Rene Kluwen Chimit -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Alex KinchSent: vrijdag 16 januari 2004 23:52To: [EMAIL PROTECTED]Subject: Re: SQLBOX [Was Re: Feature request: storingincoming/outgoingmessagesin database] Hi, I put an offer on rentacoder.com for someone to do this - unfortunately the only response was from a programmer who had quite a low rating (to say the least!). The plan was to get it developed, do a bit of testing then pass it back to anyone on the list who'd want to test it - then finally get it committed into CVS at some point in the future. The bidding is still ongoing on rentacoder - it closes on Jan 28th. Alex - Original Message - From: Renaat Dumon To: [EMAIL PROTECTED] Sent: Friday, January 16, 2004 8:22 PM Subject: RE: SQLBOX [Was Re: Feature request: storing incoming/outgoingmessagesin database] This is a feature (storing MO/MT messages in a database) is also something I've been looking for for quite a while now. I kept monitoring Kannel after some requests of other users for this, however up until now, I've not seen this feature request been picked up by one of the devs.. I suppose we're just waiting for somebody to consider this a calling :-o I would do it if it hadn't been a while since I seriously programmed though, maybe with some help from other people interested ? .. Pak, the way you described your application is exactly what I've had in mind for a project of mine too: i.e. poll an "outbound" table for messages to be sent. Or maybe even work with triggers (like oracle has for instance). And vice versa for the MO messages obviously. This would also great to do some accounting real easy, a couple of queries and you're done.. Kind regards, Renaat From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pak BeiSent: Monday, January 12, 2004 09:25To: [EMAIL PROTECTED]Subject: SQLBOX [Was Re: Feature request: storing incoming/outgoing messagesin database] Dear All, What is the status of "own smsbox" called sqlbox ?Why don't you list it to TODO list ? Regards. From: Stipe Tolj Subject: Re: Feature request: storing incoming/outgoing messages in database Date: Wed, 29 Oct 2003 04:20:38 -0800 Right now I'm using kannel towards Telenor (Norwegian telco running Logica CMG SMSC) and it works fine (when you remember to specify interface-version=33, that part took some time to figure out :-P). Actually the only part of kannel I use is the smpp parsing/sending, "forwarding" of the message to a URL, and sending a message through the SMPP SMSC. In this context I'm wondering if the following extensions have been thought of: 1. Store incoming messages into a sdb supported database (like you do with dlr's) ? 2. Have a thread in smsbox that checks a table in a database for messages that are to be sent to a smsbox compatible protocol. I had(?!) (yes *had*) an sqlbox implementation that did this withmysql. Actually it took my 1 week of coding and I lost it, because mylaptop has been taken away by some rude people that had to break intomy car. ;(( I have to check if I can find it on one of our other local machinehere arround. The basic idea was to use pre-processor magic from gw/msg-decl.h andwrap the structure of a SMS message into table attributes. Then I had a poll'ing thread that checked in a configurable ammount ofsec if there are new messages in the "outgoing" table and passed it(as a
Re: SQLBOX [Was Re: Feature request: storingincoming/outgoingmessagesin database]
PS: http://www.rentacoder.com/RentACoder/misc/BidRequests/ShowBidRequest.asp?lngBidRequestId=114460if anyone wants to take up the offer :-) - Original Message - From: Alex Kinch To: [EMAIL PROTECTED] Sent: Friday, January 16, 2004 10:52 PM Subject: Re: SQLBOX [Was Re: Feature request: storingincoming/outgoingmessagesin database] Hi, I put an offer on rentacoder.com for someone to do this - unfortunately the only response was from a programmer who had quite a low rating (to say the least!). The plan was to get it developed, do a bit of testing then pass it back to anyone on the list who'd want to test it - then finally get it committed into CVS at some point in the future. The bidding is still ongoing on rentacoder - it closes on Jan 28th. Alex - Original Message - From: Renaat Dumon To: [EMAIL PROTECTED] Sent: Friday, January 16, 2004 8:22 PM Subject: RE: SQLBOX [Was Re: Feature request: storing incoming/outgoingmessagesin database] This is a feature (storing MO/MT messages in a database) is also something I've been looking for for quite a while now. I kept monitoring Kannel after some requests of other users for this, however up until now, I've not seen this feature request been picked up by one of the devs.. I suppose we're just waiting for somebody to consider this a calling :-o I would do it if it hadn't been a while since I seriously programmed though, maybe with some help from other people interested ? .. Pak, the way you described your application is exactly what I've had in mind for a project of mine too: i.e. poll an "outbound" table for messages to be sent. Or maybe even work with triggers (like oracle has for instance). And vice versa for the MO messages obviously. This would also great to do some accounting real easy, a couple of queries and you're done.. Kind regards, Renaat From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pak BeiSent: Monday, January 12, 2004 09:25To: [EMAIL PROTECTED]Subject: SQLBOX [Was Re: Feature request: storing incoming/outgoing messagesin database] Dear All, What is the status of "own smsbox" called sqlbox ?Why don't you list it to TODO list ? Regards. From: Stipe Tolj Subject: Re: Feature request: storing incoming/outgoing messages in database Date: Wed, 29 Oct 2003 04:20:38 -0800 Right now I'm using kannel towards Telenor (Norwegian telco running Logica CMG SMSC) and it works fine (when you remember to specify interface-version=33, that part took some time to figure out :-P). Actually the only part of kannel I use is the smpp parsing/sending, "forwarding" of the message to a URL, and sending a message through the SMPP SMSC. In this context I'm wondering if the following extensions have been thought of: 1. Store incoming messages into a sdb supported database (like you do with dlr's) ? 2. Have a thread in smsbox that checks a table in a database for messages that are to be sent to a smsbox compatible protocol. I had(?!) (yes *had*) an sqlbox implementation that did this withmysql. Actually it took my 1 week of coding and I lost it, because mylaptop has been taken away by some rude people that had to break intomy car. ;(( I have to check if I can find it on one of our other local machinehere arround. The basic idea was to use pre-processor magic from gw/msg-decl.h andwrap the structure of a SMS message into table attributes. Then I had a poll'ing thread that checked in a configurable ammount ofsec if there are new messages in the "outgoing" table and passed it(as a smsbox connection) to bearerbox. Same for MO messages, passedeverything into an other table for external applications to poll them. So, the idea has been there and even the implementation. But don'tconsider doing this inside smsbox itself. Write an "own smsbox" calledsqlbox for this. Stipe Yahoo! Personals- New people, new possibilities. FREE for a limited time!
Re: Munging the '@' (at) symbol?
Troy, We had the same problem on a particular provider - it wasn't just @ that was disappearing, but also pound signs, and other random symbols. Talk to the people who you connect to, and ask them what character set they support. We fixed ours by setting the charset to HP Roman 8 - but it differs between providers. Alex - Original Message - From: Alan McNatty To: Troy Kelly Cc: [EMAIL PROTECTED] Sent: Tuesday, November 25, 2003 9:42 PM Subject: Re: Munging the '@' (at) symbol? Hi Troy,MO or MT? Have you run with log-level = 0 - this might help you seewhere the translation is happening? I'm guessing it's happening to MO messages. If this is the case you maywant to experiment/read up on the alt-charset smsc group configparameter (discussed in docs). On one link I have to set mine toISO-8859-1 (ie: alt-charset=ISO-8859-1).Cheers,AlanOn Wed, 2003-11-26 at 10:41, Troy Kelly wrote: Hi, Has anybody else had a problem with Kannel eating the @ symbol? I am using the CVS build from the 17th of November. Regards, Troy
Re: sms-service
Title: Message I'm sure you can do this. Let me get my brain in gear later and I'll reply to this email. Alex - Original Message - From: Jens von Bülow To: Alex Kinch ; [EMAIL PROTECTED] ; [EMAIL PROTECTED] Sent: Friday, November 14, 2003 4:25 AM Subject: RE: sms-service Hi, Nice, but what about routing all SMS's to a specific number to a single URL? Can one do that? How would you do it? I look forward to your responses. Thanks Regards Jens -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alex KinchSent: 14 November 2003 01:18To: [EMAIL PROTECTED]; [EMAIL PROTECTED]Subject: Re: sms-service Hi Alex, We're doing that on Kannel cvs-20031112 for nine different smsc's, works fine: group = sms-servicekeyword = defaultget-url = ""http://yoururl/page.asp?from=%pto=%Pkeyword=%kbody=%rmccmnc=%Bsmscid=%ifullbody=%a">http://yoururl/page.asp?from=%pto=%Pkeyword=%kbody=%rmccmnc=%Bsmscid=%ifullbody=%a"catch-all = truemax-messages = 0accepted-smsc = SMSC1;SMSC2;SMSC3;SMSC4; Don't think you'll get %B unless you're up to date with a CVS build from the last couple of weeks - we use it to pass the originators MCC MNC which we get from some SMSCs in the SMPP service-type field. Alex - Original Message - From: Alexandre BARBEITOS To: [EMAIL PROTECTED] Sent: Thursday, November 13, 2003 7:56 PM Subject: sms-service Hello,Is it possible to redirect all inbound SMS from an operator without keyword andwithout reliable receiver number.Can I use keyword "default" with acceped-smsc with multiple smsc.Thanks for your help,Alex
Messages stuck in store
Hi, Seen a couple of instances in the last few days when messages have got "stuck" in the store - at a guess due to the relevent SMPP connection being temporarily unavailable at the time they were submitted via smsbox. Is there a way to set bearerbox up to attempt to resend store messages at a regular interval? Alex
Connecting to operator MMSCs in the UK
Hi gang, Slightly off-topic, but is anyone here connecting to a UK operator's MMSC with a direct IP connection of some sort? Orange have advised that they are testing a product that'll allow this, but it won't be available until sometime in the first half of next year. Haven't spoken to O2 etc yet, but thought I'd ask before hammering the phone :-) Alex
Re: Connecting to operator MMSCs in the UK
Edd, I'm pretty certain anyone who's got the actual docs will be under NDA, so won't be officially allowed to send them to you. However, I believe there are some similarities between T-Mobile and the O2 Broker service. Alex Judd (on this list) is someone who might be able to add some more to this. For SMS, O2 themselves are SMPP, O2 Online (theirownreseller, or "broker" as they like to call it)seem to likeSOAP, Orange are SMPP and Vodafone, as Steve mentionedearlier, used to only doSEMA2000/X.25 - but according to their website they can do SMPP now as well. Most of the operators that offer SMPP will insist on a IP Sec tunnel if you're running over the internet. If you're also doing premium services with them, as far as I know they all requireyou to doSMPPvia aleased line IP connection to one of their SMS centres. The requirement isn't necessarily technical, it's more of a barrier to entry to weed out the non-serious players. As for MMS, it's all a little vague at the moment :-) Alex - Original Message - From: Edd Dawson To: [EMAIL PROTECTED] Sent: Wednesday, October 22, 2003 8:03 PM Subject: Re: Connecting to operator MMSCs in the UK does anyone have any links to docs about SOAP interfaces provided by theuk mobile companies? "Alex Kinch" [EMAIL PROTECTED] 10/22/03 6:30 PM Hi SteveHold on two secs though, SOAP, Sema X.25 and SMPP? I thought MMSinterconnects was all about the MM7 etc? Or am I just showing my lackof knowledge of this? :-)Alex - Original Message - From: Steve Kennedy To: [EMAIL PROTECTED] Sent: Wednesday, October 22, 2003 6:15 PM Subject: Re: Connecting to operator MMSCs in the UK On Wed, Oct 22, 2003 at 06:07:58PM +0100, Alex Kinch wrote: Slightly off-topic, but is anyone here connecting to a UK operator'sMMSC with a direct IP connection of some sort? Orange have advised that theyare testing a product that'll allow this, but it won't be available untilsometime in the first half of next year. Haven't spoken to O2 etc yet, but thoughtI'd ask before hammering the phone :-) O2 Online allow access via "The Internet", using a proprietry SOAP protocol. T-Mobile I think do (I know someone who set-up theirfirewall stuff, so I think you have to VPN it). Voodoofone generally used to use SEMA2000/X.25 but I think they mayhave introduced an IP connection service using SMPP (or were going to). Steve -- NetTek Ltd Phone/Fax +44-(0)20 7483 2455 SMS steve-pager (at) gbnet.net [body] gpg 1024D/468952DB 2001-09-19This email has been scanned for all viruses by the MessageLabs EmailSecurity System. For more information on a proactive email securityservice working around the clock, around the globe, visithttp://www.messagelabs.com
SMPP peer naming conventions
Wondered what sort of naming convention other people on this list with lots of SMPP connections use? Was thinking: [CarrierName(4)][IsoCountryCode(2)][ConnectionNo(2)][ConnectionType(2)] Eg O2 UK, connection #2, premium rate would be: O2GB02PR Thoughts, recommendations etc welcome! Alex
Re: DLR problems with Hex vs Decimal message IDs
Actually, it's more than one SMSC - I've just got out my calculator and done some hex-dec conversions and found it's happening quite a lot now that I've turned on DLR support. Alex - Original Message - From: Alex Kinch To: [EMAIL PROTECTED] Sent: Friday, October 17, 2003 4:40 PM Subject: DLR problems with Hex vs Decimal message IDs Hi, One of our SMSCs isreturning message IDs in the submit_sm_respin hex - eg B29282 - but the DLRs are coming back in decimal - eg 0011702914. This is causing problems with Kannel with the MySQL queries on the DLR database, as it can't find the related message. Any quick fixes I can make? Alex
Re: DLR problems with Hex vs Decimal message IDs
Ok, another brain dead day. Off to go hang my head in shame after RTFM :-) msg-id-typenumber - Optional, specifies which number base the SMSC is using for the message ID numbers in the corresponding submit_sm_resp and deliver_sm PDUs. Alex - Original Message - From: Alex Kinch To: [EMAIL PROTECTED] Sent: Friday, October 17, 2003 4:42 PM Subject: Re: DLR problems with Hex vs Decimal message IDs Actually, it's more than one SMSC - I've just got out my calculator and done some hex-dec conversions and found it's happening quite a lot now that I've turned on DLR support. Alex - Original Message - From: Alex Kinch To: [EMAIL PROTECTED] Sent: Friday, October 17, 2003 4:40 PM Subject: DLR problems with Hex vs Decimal message IDs Hi, One of our SMSCs is returning message IDs in the submit_sm_resp in hex - eg B29282 - but the DLRs are coming back in decimal - eg 0011702914. This is causing problems with Kannel with the MySQL queries on the DLR database, as it can't find the related message. Any quick fixes I can make? Alex
Cannot find SMSCConn
OK I know this is a stupid question, and I should reallyknow the answer, but here goes. I've got multiple SMSCs configured, and when I receive a message on one, smsbox tries to reply and fails with: WARNING: Cannot find SMSCConn for message to +44xx, rejected. There's somethingreally obvious I'veforgotten to do in my config file, can remind me? Thanks, Alex
EMI2 SMSC - does this look rigiht?
Hi list, We've just configured our first EMI2 SMSC, however messages sent to it via the HTTP interface on smsbox don't seem to be getting through. Does this look right (from the debug log)? 2003-09-22 22:15:19 [14] DEBUG: EMI2[]: emi2 sending packet: 00/00116/O/51/447764xx/14201AED76B3D168B8DA0D/3//74686973206973206120746573745039/192003-09-22 22:15:19 [14] DEBUG: EMI2[]: Got packet from the mainsocket2003-09-22 22:15:19 [14] DEBUG: EMI2[]: emi2 parsing packet: 00/00041/R/51/A//447764xx:13205528/EB Still trying to find someone at the provider that can confirm whether these messages are being processed properly at their end, however in the meantime I figured it'd be good to make sure it's all ok our end. Thanks, Alex
[OT] Bulk SMS prices to UK networks
Hi, Apologies for the [OT] message, but I need to put approx 20k messages a month (and growing steadily)to UK destinations. Any suggestions off-list please. Thanks, Alex
