Re: Fw: Kannel & Wap Configuration

[Jacob Eiler]

If you already have a working smsc connection that supports binary sms,
you can call sendsms with something like

from=1234&to=12345&udh=%06%05%04%0B%84%23%F0&text=%01%06%01%ae%02%05%04%
00%45%c6%0c%03%77%77%77%2e%67%6f%6f%67%6c%65%2e%63%6f%6d%00%01%03%67%6f%
6f%67%6c%65%00%01%01

(wap push to google.com)

/Jacob


On Fri, 2010-10-08 at 14:13 +0200, Innocent Muchedzi wrote:
> Does anyone knows how to configure kannel to be able to send send WAP
> messages
>  
>  
> Innocent Muchedzi
> Creative Directory
> Syldah Media
> Ipelo House, Plot 103, Unit 4 Gaborone International Commerce Park
> Gaborone
>  
> Tele/Fax: 3105907
> Cell: 71806864/73114818
> www.syldah.com
> www.mobitecworld.com

-- 
Apide ApS
Jacob Eiler
t: 2374 0486
e: jacob.ei...@apide.com
w: apide.com

Re: Unicode Character Count

[Jacob Eiler]

Hi James, 

the message data in the log is written in hex.

A single sms can contain 140 octets, when sending unicode (UCS2) each
character requires two octets, so you have 70 characters per message.

/Jacob

On Thu, 2010-12-16 at 19:47 +0700, JAmes wrote:
> Hi,
> 
> When sending a unicode sms, the character count is about 500-520
> characters.
> 
> When looking in the kannel-access log file, its showing like this:
> 
> [msg:956:0051004E00650074 . (lots more after this)
> 
> Is this binary encoding?
> 
> Also, how come its showing as 956 characters? How many segments is
> this ? (to determine total message cost)
> 
> Regards,
> J

-- 
Apide ApS
Jacob Eiler
t: 2374 0486
e: jacob.ei...@apide.com
w: apide.com

Number of parts sent in access log

[Jacob Eiler]

Hi.

When sending concatenated messages, I need to know the number of parts
sent. It there any way to obtain this information and possibly log it in
the bearerbox access log?

/Jacob

-- 
Apide ApS
Jacob Eiler
t: 2374 0486
e: jacob.ei...@apide.com
w: apide.com

Re: Number of parts sent in access log

[Jacob Eiler]

Hi Mads,

thank you for the feedback.

My version of Kannel (1.4.3) does not include the number of parts in the
reply from smsbox. At any rate it is my understanding that this number
may or may not be correct depending on the configuration of the smsc
(specifically max-sms-octets) actually used by the bearerbox to send the
message.

Anybody have an idea on how to extract the information from the
bearerbox - short of adding an extra field to the message structure.

/Jacob

On Thu, 2011-01-06 at 14:08 +0100, "Mads N. Vestergaard – CoolSMS A/S"
wrote:
> Hi Jacob,
> 
> When sending the messages over HTTP GET, the kannel server will reply "Sent." 
> or in case it is a multipart message "Sent. Message splits: 2"
> 
> I hope this can help you further, even tough it is not the bearerbox log.
> 
> Mads  
>   
>     
> 
> Den 06/01/2011 kl. 13.51 skrev Jacob Eiler:
> 
> > Hi.
> > 
> > When sending concatenated messages, I need to know the number of parts
> > sent. It there any way to obtain this information and possibly log it in
> > the bearerbox access log?
> > 
> > /Jacob
> > 
> > -- 
> > Apide ApS
> > Jacob Eiler
> > t: 2374 0486
> > e: jacob.ei...@apide.com
> > w: apide.com
> > 
> > 
> > 

-- 
Apide ApS
Jacob Eiler
t: 2374 0486
e: jacob.ei...@apide.com
w: apide.com

Re: Deferred for mobile connected Kannel

[Jacob Eiler]

 AT+CSMS=1^M
> 2011-01-26 14:21:07 [28822] [6] DEBUG: AT2[mysmsc]: <-- +CSMS: 1,1,1
> 2011-01-26 14:21:07 [28822] [6] DEBUG: AT2[mysmsc]: <-- OK
> 2011-01-26 14:21:07 [28822] [6] DEBUG: AT2[mysmsc]: --> AT
> +CNMI=3,2,0,1,1^M
> 2011-01-26 14:21:07 [28822] [6] DEBUG: AT2[mysmsc]: <-- OK
> 2011-01-26 14:21:07 [28822] [6] INFO: AT2[mysmsc]: AT SMSC
> successfully opened.
> 
> 
> Log file for SMSBox:
> 
> 
> 2011-01-26 14:21:06 [28831] [0] INFO: Added logfile
> `/var/log/kannel/smsbox.log' with level `0'.
> 2011-01-26 14:21:06 [28831] [0] INFO: Service global sender set as '0'
> 2011-01-26 14:21:06 [28831] [0] INFO: Logging accesses to
> '/var/log/kannel/smsboxAccess.log'.
> 2011-01-26 14:21:06 [28831] [0] INFO: Started access logfile
> `/var/log/kannel/smsboxAccess.log'.
> 2011-01-26 14:21:06 [28831] [0] INFO: HTTP: Opening server at port
> 13013.
> 2011-01-26 14:21:06 [28831] [1] DEBUG: Thread 1 (gwlib/fdset.c:poller)
> maps to pid 28831.
> 2011-01-26 14:21:06 [28831] [0] DEBUG: Started thread 1
> (gwlib/fdset.c:poller)
> 2011-01-26 14:21:06 [28831] [2] DEBUG: Thread 2
> (gwlib/http.c:server_thread) maps to pid 28831.
> 2011-01-26 14:21:06 [28831] [0] DEBUG: Started thread 2
> (gwlib/http.c:server_thread)
> 2011-01-26 14:21:06 [28831] [0] INFO: Set up send sms service at port
> 13013
> 2011-01-26 14:21:06 [28831] [0] DEBUG: Started thread 3
> (gw/smsbox.c:sendsms_thread)
> 2011-01-26 14:21:06 [28831] [3] DEBUG: Thread 3
> (gw/smsbox.c:sendsms_thread) maps to pid 28831.
> 2011-01-26 14:21:06 [28831] [0] DEBUG:
> --
> 2011-01-26 14:21:06 [28831] [0] DEBUG: Kannel smsbox version 1.4.3
> starting
> 2011-01-26 14:21:06 [28831] [0] DEBUG:   dumping group (sendsms-user):
> 2011-01-26 14:21:06 [28831] [0] DEBUG:  = 
> 2011-01-26 14:21:06 [28831] [0] DEBUG:  = <10>
> 2011-01-26 14:21:06 [28831] [0] DEBUG:  = 
> 2011-01-26 14:21:06 [28831] [0] DEBUG:  = 
> 2011-01-26 14:21:06 [28831] [0] DEBUG:  = 
> 2011-01-26 14:21:06 [28831] [0] DEBUG: Started thread 4
> (gw/smsbox.c:obey_request_thread)
> 2011-01-26 14:21:06 [28831] [4] DEBUG: Thread 4
> (gw/smsbox.c:obey_request_thread) maps to pid 28831.
> 2011-01-26 14:21:06 [28831] [0] DEBUG: Started thread 5
> (gw/smsbox.c:url_result_thread)
> 2011-01-26 14:21:06 [28831] [5] DEBUG: Thread 5
> (gw/smsbox.c:url_result_thread) maps to pid 28831.
> 2011-01-26 14:21:06 [28831] [0] DEBUG: Started thread 6
> (gw/smsbox.c:http_queue_thread)
> 2011-01-26 14:21:06 [28831] [6] DEBUG: Thread 6
> (gw/smsbox.c:http_queue_thread) maps to pid 28831.
> 2011-01-26 14:21:06 [28831] [0] INFO: Connected to bearerbox at
> 127.0.0.1 port 13005.
> 2011-01-26 14:21:06 [28831] [7] DEBUG: Thread 7
> (gw/heartbeat.c:heartbeat_thread) maps to pid 28831.
> 2011-01-26 14:21:06 [28831] [0] DEBUG: Started thread 7
> (gw/heartbeat.c:heartbeat_thread)
> 
> 
> 
> 
> My conf file:
> 
> 
> 
> 
> #-
> # CORE
> #
> # There is only one core group and it sets all basic settings
> # of the bearerbox (and system). You should take extra notes on
> # configuration variables like 'store-file' (or 'store-dir'),
> # 'admin-allow-ip' and 'access.log'
> 
> 
> group = core
> admin-port = 13000
> smsbox-port = 13005
> admin-password = 
> log-file = "/var/log/kannel/bearerbox.log"
> log-level = 0
> box-deny-ip = "*.*.*.*"
> box-allow-ip = "127.0.0.1"
> access-log = "/var/log/kannel/access.log"
> sms-combine-concatenated-mo = true
> sms-combine-concatenated-mo-timeout = "1800"
> dlr-storage = internal
> sms-resend-retry = 10
> sms-resend-freq = 2
> 
> 
> 
> 
> group = smsc
> smsc = at
> smsc-id = mysmsc
> modemtype = siemensmc35i
> device = /dev/ttyS0
> speed = 115200
> pin = 
> 
> 
> group = modems
> id = siemensmc35i
> name = siemensmc35i
> detect-string = "SIEMENS"
> detect-string2 = "MC35"
> #Messages are held on the GSM modem
> init-string = "AT+CNMI=3,2,0,1,1"
> enable-hwhs="AT\\Q3"
> 
> 
> 
> 
> #For some strange reason I need this in the configuration
> #file to support inbound large text messages
> group = smsbox-route
> smsbox-id = mysmsbox
> smsc-id = mysmsc
> 
> 
> 
> 
> group = smsbox
> smsbox-id = mysmsbox
> bearerbox-host = 127.0.0.1
> global-sender = 0
> mo-recode = true
> sendsms-port = 13013
> sendsms-chars = "0123456789 +-"
> log-file = "/var/log/kannel/smsbox.log"
> log-level = 0
> access-log = "/var/log/kannel/smsboxAccess.log"
> 
> 
> #-
> # SEND-SMS USERS
> #
> # These users are used when Kannel smsbox sendsms interface is used to
> # send PUSH sms messages, i.e. calling URL like
> #
> http://kannel.machine:13013/cgi-bin/sendsms?username=tester&password=foobar...
> 
> 
> group = sendsms-user
> username = X
> password = 
> concatenation = true
> max-messages= 10
> 
> 
> #-
> # SERVICES
> #
> # These are 'responses' to sms PULL messages, i.e. messages arriving
> from
> # handsets. The response is based on message content. Only one
> sms-service is
> # applied, using the first one to match.
> 
> 
> group = sms-service
> name = receiveMessages
> keyword = default
> max-messages = 0
> concatenation = true
> get-url = http://localhost:8080/receiveSMS?sender=%p&text=%a&udh=%u
> #omit-empty=true
> #accept-x-kannel-headers=true
> 
> 
> 
> 

-- 
Apide ApS
Jacob Eiler
t: 2374 0486
e: jacob.ei...@apide.com
w: apide.com

Re: replacing WAP Push on mobile phone

[Jacob Eiler]

You should be able to produce the same result if you encode your wap
push by hand and send via sendsms specifying text (user data), udh and
binary encoding.

I know my operation uses the pid replace functionality when sending out
notifications from their voice mail system. However I suspect that
support for this depends on the handset receiving the message.

/Jacob

On Tue, 2011-02-15 at 13:19 +0100, Latitude Berlin wrote:
> I was able to replace the reached SMS on the phone using pid.
> 
> 2011/2/14 Nikos Balkanas 
> You cannot replace an SMS once it has reached the mobile. You
> just send a new one. You could replace an SMS at the SMSc,
> before reaching the mobile, but kannel doesn't support that
> issue.
> 
> BR,
> Nikos
> - Original Message - From: Latitude Berlin
> To: users
> Sent: Monday, February 14, 2011 4:39 PM
> Subject: replacing WAP Push on mobile phone
> 
> 
> 
> 
> Hi Everyone,
> 
> How can I replace a WAP Push message sent via Kannel on a
> mobile phone?
> I can do this for plain SMS by using 'pid' in the HTTP send
> request.
> 
> Regards. 
> 
> 

Re: call records / billing info

[Jacob Eiler]

Even using sqlbox each "message" is just a single record. The actual
message may have been split into several sms messages when sent by the
bearerbox. In most cases the operator will charge you per sms sent, so
some analysis of the access log or sqlbox table data is still required.

If you want to do this correct, you should take the following factors
into account:
- message data coding scheme (GSM 03.38, UCS2, 8 bit data)
- message data/text
- message headers (as set by sender or inserted by bearerbox when
splitting the message)
- max. octets per message as set on the smsc-connection used to sent the
message (default is 140 octets).

If you know C try looking at sms_split(...) in gw/sms.c, it splits
messages into parts, but the information is not recorded in any logs.

/Jacob


On Fri, 2011-02-25 at 06:53 +0500, ha...@aeon.pk wrote:
> Use sqlbox.
> 
> On Wed, Feb 23, 2011 at 11:43 PM, Sanjay Bhandari
>  wrote:
> Just want to confirm my understanding about call records in
> Kannel. It seems to me that one would have to parse the logs
> to extract the accounting / billing info / call records. Are
> there other ways to get to this information, which are, maybe,
> easier to use?
> 
> Thanks for your help.
>     
> Sanjay
> 
> 

-- 
Jacob Eiler
Apide ApS
e: jacob.ei...@apide.com
t: +45 2374 0486
w: apide.com

RE: Error in Kannel

[Jacob Eiler]

Hi Ghassen,

the error message is pretty generic - every part of Kannel uses octstr,
so without some additional information it is going to be pretty hard to
help you.

You need to include information about the specific version of Kannel,
your configuration and other relevant information about the system you
are running Kannel on.

/Jacob

On Mon, 2011-02-28 at 15:34 +0100, GHASSEN BEZZINE wrote:
> Any Answer !!!
> 
>  
> 
>  
> 
>
> __
> De :users-boun...@kannel.org [mailto:users-boun...@kannel.org] De la
> part de GHASSEN BEZZINE
> Envoyé : mercredi 23 février 2011 09:08
> À : users@kannel.org
> Objet : Error in Kannel
> 
> 
>  
> 
> Hello Users of Kannel,
> 
>  
> 
> I am getting an Error message that brings my gateway suspended, did
> any one got this error before :
> 
>  
> 
> 2011-02-17 07:51:10 [11704] [6] PANIC: gwlib/octstr.c:2502:
> seems_valid_real: Assertion `ostr->data[ostr->len] == '\0'' failed.
> (Called from gwlib/octstr.c:872:octstr_compare.)
> 
>  
> 
>  
> 
> Regards
> 
> 

-- 
Jacob Eiler
Apide ApS
e: jacob.ei...@apide.com
t: +45 2374 0486
w: apide.com

Re: Re : How to change Phone Number to Name when getting SMS on phone screen

[Jacob Eiler]

Hi Kidi,

what exactly are you setting in the from field? It may be that you  
are using invalid characters or the text is too long.


I believe there is a limit of 11 characters when using alphanumeric  
origination. Also only a subset of GSM 03.38 is supported.


/Jacob


Den 23/03/2011 kl. 9.32 skrev Kidi Kidi:

I have replaced the "From Field" by a name and sent a SMPP message  
to my phone, but i didn't get any

 message. But if the "From Field" is my shortcode i do get my message.
So i think hamza are right by saying you can only use it if it is  
allowed by your telco operator over

 the account allotted to you.
Is there a way to do it without my telco operator support?

From: "ha...@aeon.pk" 
To: Richard Crawshaw 
Sent:  22 March 2011 14:33
Subject:  Re: How to change Phone Number to Name when getting SMS  
on phone screen


Also, you can only use it if it is allowed by your telco operator  
over the account allotted to you.


On Tue, Mar 22, 2011 at 8:56 PM, Richard Crawshaw  
wrote:

Take a look at the Running SMS Gateway section of the user guide.


You can specify the from field for each message, this can be a  
number or it can be text.  (The from field is also called the MASK  
field.)  It can also be specified in different parts of Kannel  
configuration file depending on how you have Kannel configured.



Richard


From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On  
Behalf Of Kidi Kidi

Sent: 22 March 2011 14:33
To: users@kannel.org
Subject: How to change Phone Number to Name when getting SMS on  
phone screen



Great Thanks hamza,


I don't understand, could you give me more explanation please?


De : "ha...@aeon.pk" 
À : Kidi Kidi 
Cc : users@kannel.org
Envoyé le : Mar 22 mars 2011, 14h 07min 21s
Objet : Re: How to change Phone Number to Name when getting SMS on  
phone screen


Use MASK field while sending SMS from application.

On Tue, Mar 22, 2011 at 6:52 PM, Kidi Kidi  wrote:

Hi all,


When i get a SMS on my phone i see the FROM number, but i want to  
change this number to alphabetical value. For exemple i want that  
if i send a SMS to somebody, this person must see the name of my  
school instead of my phone number. I know that it's possible, but  
kannel can do that?

Re: Kannel+opensmppbox+sqlbox

[Jacob Eiler]

  
  
Hi Henrik,

yes, sqlbox should be placed between bearerbox and smsbox. 

For example configure the bearerbox with smsbox-port 11001, then
configure sqlbox with bearerbox-port=11001 and smsbox-port=11002,
and finally configure the smsbox with bearerbox-port=11002.

I have no experience with opensmpp, so I don't know how that fits
into the equation.

/Jacob


Den 30-03-2011 13:44, Henrik Månsson skrev:

  
  
  
  
  
Hi all,
 
I
have installed and have a running Kannel installation with
Opensmppbox. I use MySQL for DLR, but I would like to add
sqlbox to have the send_sms stored in Mysql, so I can see
how many and which servers has send sms to who. 
 
I
can’t figure out if this is the way sqlbox works?
 
SMPPclient
=> smsbox => sqlbox => bearerbox => receiver
 
And
who is connecting to how in kannel?
 
Med venlig hilsen / Best regards

  

Henrik Månsson
Kompetencekonsulent 


Mobil: +45 3078 1298 
  henrik.maans...@atea.dk
  

  Atea
  A/S

Lautrupvang 6 
2750 Ballerup 
DANMARK
Telefon / Phone: +45 7025 2550
Telefax: +45 7025 2575
  www.atea.dk
  
  

Atea er Danmarks førende leverandør af it-infrastruktur. Med
de mest kompetente og højest certificerede medarbejdere
bistår vi vores kunder med specialistkompetencer, produkter,
services og løsninger. I Danmark beskæftiger Atea mere end
1400 medarbejdere, og har en stærk lokal tilstedeværelse med
8 afdelinger fordelt over hele landet. Som en del af Atea
koncernen er vi repræsenteret i hele Norden og Baltikum.
Atea koncernen er noteret på Oslo Børs.
  
  

    
    
    -- 
Jacob Eiler
Apide ApS
e: jacob.ei...@apide.com
t: +45 2374 0486
w: apide.com

  

Re: Kannel+opensmppbox+sqlbox

[Jacob Eiler]

Den 31-03-2011 11:56, Henrik Månsson skrev:


I have another problem with Danish characters. When I submit a sms 
with Danish characters, then dansh letters are not shown in the 
received sms.


Is there a workaround to this issue?



You need to clarify - is the message submitted by a client to the 
opensmpp server or smsbox or is it received from the smsc?


--
Jacob Eiler
Apide ApS
e: jacob.ei...@apide.com
t: +45 2374 0486
w: apide.com

Re: using Parlay X with Kannel

[Jacob Eiler]

To my knowledge Kannel does not include an smsc driver for Parlay X, so
you may need to implement your own.

/Jacob

-- 
Jacob Eiler
Apide ApS
e: jacob.ei...@apide.com
t: +45 2374 0486
w: apide.com



On Mon, 2011-04-18 at 04:51 -0700, write2...@live.com wrote: 
Dear All,
> 
> I am facing an issue when connecting with SMSC using Parlay X in
Kannel.
> 
> Can anyone provide me with some help how to connect with SMSC using
Parlay X
> 2.1
> 
> I am totally lost here
> 
> Looking forward to your response.
> 

Re: What happens to MO if kannel is stopped

[Jacob Eiler]

Hi Harbhag,

What happens to the mo sms depends on the operator smsc/platform. The
operator may store the sms and attempt to deliver it later, they may
discard it or - in some cases - your gateway must pull the message from
the operator.

What protocol are you using?

/Jacob

On Mon, 2011-06-27 at 19:43 +0530, Harbhag Singh Sohal wrote:
> yes I can confirm that get-url is not getting triggered even though
> SMS is received.
> 
> On Mon, Jun 27, 2011 at 7:37 PM, Harbhag Singh Sohal
>  wrote:
> > And what are chances that MO gets rejected by SMSC ?
> > And when the MO is received after kannel is up again, will it run get-url ?
> > bcoz I think its not running get-url
> >
> > On Mon, Jun 27, 2011 at 7:33 PM, ha...@aeon.pk  wrote:
> >> It will get stored in the SMSC, to be delivered to you kannel whenever it
> >> gets up.
> >>
> >> On Mon, Jun 27, 2011 at 6:53 PM, Harbhag Singh Sohal
> >>  wrote:
> >>>
> >>> Suppose I have bearerbox,smsbox and sqlbox stopped and someone sends
> >>> me SMS, where this MO will go ? What will happen to it ?
> >>>
> >>> --
> >>> Regards
> >>> Harbhag Singh Sohal
> >>> www.harbhag.wordpress.com
> >>>
> >>
> >>
> >
> >
> >
> > --
> > Regards
> > Harbhag Singh Sohal
> > www.harbhag.wordpress.com
> >
> 
> 
> 

-- 
Jacob Eiler
Apide ApS
e: jacob.ei...@apide.com
t: +45 2374 0486
w: apide.com

Re: Is there a way to force a sender in sendsms-user group?

[Jacob Eiler]

  
  
There is a "forced-sender" setting for
  sendsms-user.
  
  /Jacob
  
  On 2012-07-06 09:36, Tshimanga Minkoka wrote:


  Dears,

What I want to achieve is to force and use a kind of forced-sender in sendsms-user group, in order for smsbox to always ignore the supplied sender (by the from parameter in the HTTP request) in the HTTP request to replace it by the forced-sender.

I was not able to find something clearly related in the user guide.

The only thread I found in mailing list ("Senders/from white-list" on 09 Nov 2009) that somehow discusses the problem is quite old and does not come to a final conclusion. Being old, maybe some patches have already been merged in the latest versions.

Any help or suggestion will be appreciated.

Best regards,

Tshimanga



Tshimanga Minkoka
Manager VAS  & Data Systems
Billing & IT Group
Desk   : +243815560341 ext 0583
Mobile: +243814443113
http://www.vodacom.cd/
https://twitter.com/#!/Vodacomcongo http://www.facebook.com/VodacomRDC
This e-mail is classified C2 - Vodacom Restricted - Information to be used inside Vodacom but it may be shared with authorised partners.
Ce courriel est classifie C2 – Vodacom Restreint. Ce sont des informations dont la divulgation non autorisée, en particulier en dehors de l'organisation, serait inappropriée et inopportune









-- 
  
  
  
    
  
Jacob Eiler
Apide ApS
  e: jacob.ei...@apide.com
  t: +45 23740486
  w: apide.com



  

  
  

  

Re: Is there a way to force a sender in sendsms-user group?

[Jacob Eiler]

  
  
Sorry, it a 'faked-sender', but I
  believe it has higher priority than the 'from' specified in the
  HTTP request.
  
  I believe the priority is
  
  faked-sender
  from variable
  default-sender
  global-sender
  
  /Jacob
  
  On 2012-07-06 09:48, Jacob Eiler wrote:


  
  There is a "forced-sender" setting
for sendsms-user.

/Jacob

On 2012-07-06 09:36, Tshimanga Minkoka wrote:
  
  
Dears,

What I want to achieve is to force and use a kind of forced-sender in sendsms-user group, in order for smsbox to always ignore the supplied sender (by the from parameter in the HTTP request) in the HTTP request to replace it by the forced-sender.

I was not able to find something clearly related in the user guide.

The only thread I found in mailing list ("Senders/from white-list" on 09 Nov 2009) that somehow discusses the problem is quite old and does not come to a final conclusion. Being old, maybe some patches have already been merged in the latest versions.

Any help or suggestion will be appreciated.

Best regards,

Tshimanga



Tshimanga Minkoka
Manager VAS  & Data Systems
Billing & IT Group
Desk   : +243815560341 ext 0583
Mobile: +243814443113
http://www.vodacom.cd/
https://twitter.com/#!/Vodacomcongo http://www.facebook.com/VodacomRDC
This e-mail is classified C2 - Vodacom Restricted - Information to be used inside Vodacom but it may be shared with authorised partners.
Ce courriel est classifie C2 – Vodacom Restreint. Ce sont des informations dont la divulgation non autorisée, en particulier en dehors de l'organisation, serait inappropriée et inopportune






  
  
  
  -- 

    
    
  

  Jacob Eiler
  Apide ApS
e: jacob.ei...@apide.com
t: +45 23740486
w: apide.com
  
  
  

  


  



-- 
  
  
  

  
Jacob Eiler
Apide ApS
  e: jacob.ei...@apide.com
  t: +45 23740486
  w: apide.com



  

  
  

  

Re: Kannel HTTP GET works, but HTTP POST fails

[Jacob Eiler]

Hi Kasper.

The content type should not be set to text/xml. It depends on the type of
OTA that you want to send:
text/vnd.wap.connectivity-xml
application/x-wap-prov.browser-bookmarks
application/x-wap-prov.browser-settings

The documentation is a little lacking, so have a look in gw/smsbox.c

Jacob


[image: apide.png]

Jacob Eiler

e: ja...@apide.com

t: +45 2374 0486

w: apide.com


On Tue, Jan 23, 2018 at 3:01 PM, Kasper Nielsen  wrote:

> Tried
>
> request({
> url: 'http://127.0.0.1:13002/cgi-bin/sendota',
> method: 'POST',
> headers : {
> 'content-type': 'text/xml',
> 'X-Kannel-Username': 'foo',
> 'X-Kannel-Password': 'bar',
> 'X-Kannel-To': '1324422133',
> 'X-Kannel-From': '12023455750'
> },
> body: xml
> }, function (error, response, body) {
> console.log('error:', error); // Print the error if one occurred
> console.log('statusCode:', response && response.statusCode); // Print
> the response status code if a response was received
> console.log('body:', body); // Print the HTML for the Google homepage.
> });
>
> Now I'm getting body: Unsupported content-type, rejected
> but text/xml should be supported...
>
> On Tue, Jan 23, 2018 at 2:40 PM, Kasper Nielsen 
> wrote:
>
>> Just testing if this mailinglist is active, has anyone received my
>> questions?
>>
>> On Tue, Jan 23, 2018 at 2:01 PM, Kasper Nielsen 
>> wrote:
>>
>>> Seems - after a lot of Googling - that the Kannel SMS gateway actually
>>> doesn't support HTTP POST for sending SMSes, which is a limit to the size
>>> of SMSes being sent :(
>>>
>>> On Tue, Jan 23, 2018 at 1:35 PM, Kasper Nielsen 
>>> wrote:
>>>
>>>> Looked through the contrib-examples and all examples actually uses the
>>>> HTTP GET method to send SMS, which may fail on large SMSes.
>>>>
>>>> On Tue, Jan 23, 2018 at 12:19 PM, Kasper Nielsen 
>>>> wrote:
>>>>
>>>>> ...and tried old school XML:
>>>>>
>>>>> var xml = ' \
>>>>> \
>>>>> \
>>>>>   \
>>>>> 11021034235\
>>>>> 11076034723\
>>>>> Hello\
>>>>> \
>>>>>   foo\
>>>>>   foo\
>>>>>   bar\
>>>>>   bar\
>>>>> \
>>>>>   \
>>>>> \
>>>>> ';
>>>>>
>>>>> var options = {
>>>>>   method: 'POST',
>>>>>   uri: 'http://127.0.0.1:13002/cgi-bin/sendsms',
>>>>>   body: xml,
>>>>>   headers: {'content-type': 'text/xml'}
>>>>> };
>>>>>
>>>>>  but getting:  body: 'Authorization failed for sendsms' } }
>>>>>
>>>>>
>>>>> On Tue, Jan 23, 2018 at 11:58 AM, Kasper Nielsen 
>>>>> wrote:
>>>>>
>>>>>> Also able to get:  body: 'Invalid content-type' } }
>>>>>> But the content-type is correct http form:
>>>>>> application/x-www-form-urlencoded.
>>>>>>
>>>>>> On Tue, Jan 23, 2018 at 11:57 AM, Kasper Nielsen >>>>> > wrote:
>>>>>>
>>>>>>> ...and the docs doesn't seem to tell anything about this.
>>>>>>>
>>>>>>> On Tue, Jan 23, 2018 at 11:36 AM, Kasper Nielsen <
>>>>>>> kasp.n...@gmail.com> wrote:
>>>>>>>
>>>>>>>> This is my NodeJS (request-promise) for sending SMS via HTTP GET:
>>>>>>>>
>>>>>>>> var options = {
>>>>>>>> method: 'GET',
>>>>>>>> uri: 'http://127.0.0.1:13002/cgi-bin/sendsms',
>>>>>>>> qs: {
>>>>>>>> username: 'foo',
>>>>>>>> password: 'bar',
>>>>>>>> to: '127883327304',
>>>>>>>> from: '12488331359 <(248)%20833-1359>',
>>>>>>>> text: 'Hi
>>>>>>>> }
>>>>>>>> };
>>>>>>>>
>>>>>>>> This works, but changing to HTTP POST fails.
>>>>>>>>
>>>>>>>> var options = {
>>>>>>>> method: 'POST',
>>>>>>>> uri: 'http://127.0.0.1:13002/cgi-bin/sendsms',
>>>>>>>> form: {
>>>>>>>> username: 'foo',
>>>>>>>> password: 'bar',
>>>>>>>> to: '127883327304',
>>>>>>>> from: '12488331359 <(248)%20833-1359>',
>>>>>>>> text: 'Hi
>>>>>>>> }
>>>>>>>> };
>>>>>>>>
>>>>>>>> Getting  body: 'Authorization failed for sendsms' } }
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>

Re: Re: Deliver_sm

[Jacob Eiler]

Yes. They also come in the form of deliver_sm, but you must include
dlr-mask and dlr-url in your request to sendsms.

/eiler

On 30/08/2010 14:17 "dafodil"  wrote:

> i should be also able to get delivery report when i m sending from
> HTTP/kannel.
> 
> elthox wrote:
> > 
> > You will see deliver_sm PDU-s whenever you send back from your
> > mobile
> > toward application.
> > 
> > On Mon, Aug 30, 2010 at 1:14 PM, dafodil 
> > wrote:
> > > 
> > > Hi List,
> > > i habe bit confusion in my case.I see submit_sm and submit_sm_resp
> > > in the
> > > log but not deliver_sm.
> > > Can it be a problem with my configuration or carrier has not
> > > enabled
> > > it.How
> > > ever my message is successfully delivered to the destination
> > > mobile.i m
> > > using HTTP post to send message and dlr type default(internal)
> > > 
> > > Br
> > > daf
> > > 
> > > --
> > > View this message in context:
> > > 
> > > Sent from the Kannel - User mailing list archive at Nabble.com.
> > > 
> > > 
> > > 
> > 
> > 
> > 

Re: Re: Deliver_sm

[Jacob Eiler]

UG: SMPP[B]: Got PDU:
> 2010-08-31 08:36:49 [23468] [7] DEBUG: SMPP PDU 0x4a5b7c0 dump:
> 2010-08-31 08:36:49 [23468] [7] DEBUG:   type_name: enquire_link_resp
> 2010-08-31 08:36:49 [23468] [7] DEBUG:   command_id: 2147483669 = 0x8015
> 2010-08-31 08:36:49 [23468] [7] DEBUG:   command_status: 0 = 0x
> 2010-08-31 08:36:49 [23468] [7] DEBUG:   sequence_number: 7 = 0x0007
> 2010-08-31 08:36:49 [23468] [7] DEBUG: SMPP PDU dump ends.
> 2010-08-31 08:37:19 [23468] [8] DEBUG: SMPP[C]: Sending enquire link:
> 2010-08-31 08:37:19 [23468] [8] DEBUG: SMPP PDU 0x4a8ac00 dump:
> 2010-08-31 08:37:19 [23468] [8] DEBUG:   type_name: enquire_link
> 2010-08-31 08:37:19 [23468] [8] DEBUG:   command_id: 21 = 0x0015
> 2010-08-31 08:37:19 [23468] [8] DEBUG:   command_status: 0 = 0x
> 2010-08-31 08:37:19 [23468] [8] DEBUG:   sequence_number: 7 = 0x0007
> 2010-08-31 08:37:19 [23468] [8] DEBUG: SMPP PDU dump ends.
> 2010-08-31 08:37:19 [23468] [8] DEBUG: SMPP[C]: Got PDU:
> 2010-08-31 08:37:19 [23468] [8] DEBUG: SMPP PDU 0x4a5b7c0 dump:
> 2010-08-31 08:37:19 [23468] [8] DEBUG:   type_name: enquire_link_resp
> 2010-08-31 08:37:19 [23468] [8] DEBUG:   command_id: 2147483669 = 0x8015
> 2010-08-31 08:37:19 [23468] [8] DEBUG:   command_status: 0 = 0x
> 2010-08-31 08:37:19 [23468] [8] DEBUG:   sequence_number: 7 = 0x0007
> 2010-08-31 08:37:19 [23468] [8] DEBUG: SMPP PDU dump ends.
> 2010-08-31 08:37:19 [23468] [7] DEBUG: SMPP[B]: Sending enquire link:
> 2010-08-31 08:37:19 [23468] [7] DEBUG: SMPP PDU 0x4a8ac00 dump:
> 2010-08-31 08:37:19 [23468] [7] DEBUG:   type_name: enquire_link
> 2010-08-31 08:37:19 [23468] [7] DEBUG:   command_id: 21 = 0x0015
> 2010-08-31 08:37:19 [23468] [7] DEBUG:   command_status: 0 = 0x
> 2010-08-31 08:37:19 [23468] [7] DEBUG:   sequence_number: 8 = 0x0008
> 2010-08-31 08:37:19 [23468] [7] DEBUG: SMPP PDU dump ends.
> 2010-08-31 08:37:19 [23468] [7] DEBUG: SMPP[B]: Got PDU:
> 2010-08-31 08:37:19 [23468] [7] DEBUG: SMPP PDU 0x4a5b7c0 dump:
> 2010-08-31 08:37:19 [23468] [7] DEBUG:   type_name: enquire_link_resp
> 2010-08-31 08:37:19 [23468] [7] DEBUG:   command_id: 2147483669 = 0x8015
> 2010-08-31 08:37:19 [23468] [7] DEBUG:   command_status: 0 = 0x
> 2010-08-31 08:37:19 [23468] [7] DEBUG:   sequence_number: 8 = 0x0008
> 2010-08-31 08:37:19 [23468] [7] DEBUG: SMPP PDU dump ends.
> 2010-08-31 08:37:27 [23468] [2] DEBUG: HTTP: Creating HTTPClient for
> `127.0.0.1'.
> 2010-08-31 08:37:27 [23468] [2] DEBUG: HTTP: Created HTTPClient area
> 0x2c000a90.
> 2010-08-31 08:37:27 [23468] [3] DEBUG: HTTP: Resetting HTTPClient for
> `127.0.0.1'.
> 2010-08-31 08:37:27 [23468] [1] DEBUG: HTTP: Destroying HTTPClient area
> 0x2c000a90.
> 2010-08-31 08:37:27 [23468] [1] DEBUG: HTTP: Destroying HTTPClient for
> `127.0.0.1'.
> 2010-08-31 08:37:49 [23468] [8] DEBUG: SMPP[C]: Sending enquire link:
> 2010-08-31 08:37:49 [23468] [8] DEBUG: SMPP PDU 0x4a8ac00 dump:
> 2010-08-31 08:37:49 [23468] [8] DEBUG:   type_name: enquire_link
> 2010-08-31 08:37:49 [23468] [8] DEBUG:   command_id: 21 = 0x0015
> 2010-08-31 08:37:49 [23468] [8] DEBUG:   command_status: 0 = 0x
> 2010-08-31 08:37:49 [23468] [8] DEBUG:   sequence_number: 8 = 0x0008
> 2010-08-31 08:37:49 [23468] [8] DEBUG: SMPP PDU dump ends.
> 2010-08-31 08:37:49 [23468] [8] DEBUG: SMPP[C]: Got PDU:
> 2010-08-31 08:37:49 [23468] [8] DEBUG: SMPP PDU 0x4a5b7c0 dump:
> 2010-08-31 08:37:49 [23468] [8] DEBUG:   type_name: enquire_link_resp
> 2010-08-31 08:37:49 [23468] [8] DEBUG:   command_id: 2147483669 = 0x8015
> 2010-08-31 08:37:49 [23468] [8] DEBUG:   command_status: 0 = 0x
> 2010-08-31 08:37:49 [23468] [8] DEBUG:   sequence_number: 8 = 0x0008
> 2010-08-31 08:37:49 [23468] [8] DEBUG: SMPP PDU dump ends.
> 2010-08-31 08:37:49 [23468] [7] DEBUG: SMPP[B]: Sending enquire link:
> 2010-08-31 08:37:49 [23468] [7] DEBUG: SMPP PDU 0x4a8ac00 dump:
> 2010-08-31 08:37:49 [23468] [7] DEBUG:   type_name: enquire_link
> 2010-08-31 08:37:49 [23468] [7] DEBUG:   command_id: 21 = 0x0015
> 2010-08-31 08:37:49 [23468] [7] DEBUG:   command_status: 0 = 0x
> 2010-08-31 08:37:49 [23468] [7] DEBUG:   sequence_number: 9 = 0x0009
> 2010-08-31 08:37:49 [23468] [7] DEBUG: SMPP PDU dump ends.
> 2010-08-31 08:37:50 [23468] [7] DEBUG: SMPP[B]: Got PDU:
> 2010-08-31 08:37:50 [23468] [7] DEBUG: SMPP PDU 0x4a5b7c0 dump:
> 2010-08-31 08:37:50 [23468] [7] DEBUG:   type_name: enquire_link_resp
> 2010-08-31 08:37:50 [23468] [7] DEBUG:   command_id: 2147483669 = 0x8015
> 2010-08-31 08:37:50 [23468] [7] DEBUG:   command_status: 0 = 0x
> 2010-08-31 08:37:50 [23468] [7] DEBUG:   sequence_number: 9 = 0x0009
> 2010-08-31 08:37:50 [23468] [7] DEBUG: SMPP PDU dump ends.
> 
> 
> Jacob Eiler wrote:
> > 
> > Yes. They also come in the form of deliver_sm, but you must include
> > dlr-mask and dlr-url in your request to sendsms.
> > 
> > /eiler
> > 
> > On 30/08/2010 14:17 "dafodil"  wrote:
> > 
> >> i should be also able to get delivery report when i m sending from
> >> HTTP/kannel.
> >> 
> >> elthox wrote:
> >> > 
> >> > You will see deliver_sm PDU-s whenever you send back from your
> >> > mobile
> >> > toward application.
> >> > 
> >> > On Mon, Aug 30, 2010 at 1:14 PM, dafodil 
> >> > wrote:
> >> > > 
> >> > > Hi List,
> >> > > i habe bit confusion in my case.I see submit_sm and submit_sm_resp
> >> > > in the
> >> > > log but not deliver_sm.
> >> > > Can it be a problem with my configuration or carrier has not
> >> > > enabled
> >> > > it.How
> >> > > ever my message is successfully delivered to the destination
> >> > > mobile.i m
> >> > > using HTTP post to send message and dlr type default(internal)
> >> > > 
> >> > > Br
> >> > > daf
> >> > > 
> >> > > --
> >> > > View this message in context:
> >> > > <http://old.nabble.com/Deliver_sm-tp29571489p29571489.html>
> >> > > Sent from the Kannel - User mailing list archive at Nabble.com.
> >> > > 
> >> > > 
> >> > > 
> >> > 
> >> > 
> >> > 
> > 
> 

-- 
Apide ApS
Jacob Eiler
t: 2374 0486
e: jacob.ei...@apide.com
w: apide.com

Re: Deliver_sm

[Jacob Eiler]

Hi Daf.

OK. So you receive deliver_sm on the connection, just not delivery 
reports for previously sent messages. Then I suspect that the issue is 
with the smsc..


/Jacob

dafodil skrev:

Hi Jacob,
Thanks for the reply.Yes message is delivered to terminal.I tested with my
own number ad it works fine.

Br
Daf



Jacob Eiler wrote:
  

Hi Daf.

Everything looks just fine to me - you connect as transceiver and have
the 'registered delivery' flag set on the submit_sm.

Do you know if the message is delivered to the terminal? How about
receive sms messages from the smsc - does that work?

/Jacob

On Tue, 2010-08-31 at 00:51 -0700, dafodil wrote:


Hi jacob,
 have almost done evry thing but with no success.Pls see bellow.I have
also
attached log and all info.I have been struggling since days for
this.Message
gets successfully delivered but i dont get the dlr.

Br
Daf

$dlrurl = "http://smpp.X.com/dl.php?dlr=%d";;
$durl = urlencode($dlrurl);
$result =
curl_init("http://$kannelHost:$kannelPort/cgi-bin/sendsms?dlr=1&dlr-mask=31&dlr-url=$durl&username=$userName&password=$userPassword&from=$from&to=$to&text=$msg&coding=2&charset=iso-8859-7";);


Kannel.conf
# SMSC SMPP
group = smsc
smsc = smpp
smsc-id = B
host = .x.com
port = 
transceiver-mode = yes
alt-charset = "ISO-8859-1"
msg-id-type=0x01
system-type = ""
address-range = ""
max-pending-submits = 10
smsc-username = "xxx"
smsc-password = ""
connect-allow-ip = "*.*.*.*"

# SMSC HTTP
group = smsc
smsc = http
msg-id-type=0x01
smsc-id = D
system-type = kannel
smsc-username = tester
smsc-password = foobar
port = 13015
connect-allow-ip = "*.*.*.*"
send-url = "http://www.x.com:13015/cgi-bin/sendsms";

bearerbox.log


2010-08-31 08:34:19 [23468] [0] INFO: DLR rerouting for smsc id  
disabled.
2010-08-31 08:34:19 [23468] [0] INFO: DLR rerouting for smsc id 
disabled.

2010-08-31 08:34:19 [23468] [0] INFO: DLR rerouting for smsc id 
disabled.
2010-08-31 08:34:19 [23468] [0] INFO: DLR rerouting for smsc id 
disabled.
2010-08-31 08:34:19 [23468] [8] DEBUG: Thread 8
(gw/smsc/smsc_smpp.c:io_thread) maps to pid 23468.
2010-08-31 08:34:19 [23468] [0] INFO: HTTP: Opening server at port 13015.
2010-08-31 08:34:19 [23468] [0] DEBUG: Started thread 9
(gw/smsc/smsc_http.c:httpsmsc_receiver)
2010-08-31 08:34:19 [23468] [0] DEBUG: Started thread 10
(gw/smsc/smsc_http.c:httpsmsc_send_cb)
2010-08-31 08:34:19 [23468] [0] INFO: HTTP[D]: Initiated and ready
2010-08-31 08:34:19 [23468] [0] DEBUG: Started thread 11
(gw/bb_smscconn.c:sms_router)
2010-08-31 08:34:19 [23468] [0] DEBUG: starting UDP sender/receiver
module
2010-08-31 08:34:19 [23468] [0] INFO: Adding interface *
2010-08-31 08:34:19 [23468] [0] DEBUG: udpc_create: Bound to UDP
<0.0.0.0:9200>
2010-08-31 08:34:19 [23468] [0] DEBUG: Started thread 12
(gw/bb_udp.c:udp_receiver)
2010-08-31 08:34:19 [23468] [0] DEBUG: Started thread 13
(gw/bb_udp.c:udp_sender)
2010-08-31 08:34:19 [23468] [9] DEBUG: Thread 9
(gw/smsc/smsc_http.c:httpsmsc_receiver) maps to pid 23468.
2010-08-31 08:34:19 [23468] [0] DEBUG: udpc_create: Bound to UDP
<0.0.0.0:9201>
2010-08-31 08:34:19 [23468] [0] DEBUG: Started thread 14
(gw/bb_udp.c:udp_receiver)
2010-08-31 08:34:19 [23468] [0] DEBUG: Started thread 15
(gw/bb_udp.c:udp_sender)
2010-08-31 08:34:19 [23468] [0] DEBUG: starting wapbox connection module
2010-08-31 08:34:19 [23468] [0] DEBUG: Started thread 16
(gw/bb_boxc.c:wdp_to_wapboxes)
2010-08-31 08:34:19 [23468] [0] DEBUG: Started thread 17
(gw/bb_boxc.c:wapboxc_run)
2010-08-31 08:34:19 [23468] [17] DEBUG: Thread 17
(gw/bb_boxc.c:wapboxc_run)
maps to pid 23468.
2010-08-31 08:34:19 [23468] [0] DEBUG: starting WDP router
2010-08-31 08:34:19 [23468] [7] DEBUG: Thread 7
(gw/smsc/smsc_smpp.c:io_thread) maps to pid 23468.
2010-08-31 08:34:19 [23468] [0] DEBUG: Started thread 18
(gw/bearerbox.c:wdp_router)
2010-08-31 08:34:19 [23468] [0] INFO:

2010-08-31 08:34:19 [23468] [0] INFO: Kannel bearerbox II version 1.4.3
starting
2010-08-31 08:34:19 [23468] [10] DEBUG: Thread 10
(gw/smsc/smsc_http.c:httpsmsc_send_cb) maps to pid 23468.
2010-08-31 08:34:19 [23468] [18] DEBUG: Thread 18
(gw/bearerbox.c:wdp_router) maps to pid 23468.
2010-08-31 08:34:19 [23468] [16] DEBUG: Thread 16
(gw/bb_boxc.c:wdp_to_wapboxes) maps to pid 23468.
2010-08-31 08:34:19 [23468] [13] DEBUG: Thread 13
(gw/bb_udp.c:udp_sender)
maps to pid 23468.
2010-08-31 08:34:19 [23468] [0] INFO: Loading store file
`/var/log/kannel/kannel.store'
2010-08-31 08:34:19 [23468] [15] DEBUG: Thread 15
(gw/bb_udp.c:udp_sender)
maps to pid 23468.
2010-08-31 08:34:19 [23468] [14] DEBUG: Thread 14
(gw/bb_udp.c:udp_receiver)
maps to pid 23468.
2010-08-31 08:34:19 [23468] [0] INFO: Store-file size 0, starting to
unpack
2010-08-31 08:34:19 [23468] [12] DEBUG: Thread 12
(gw/bb_udp

Re: long message sent problem

[Jacob Eiler]

Hi Levon.

Some more information is needed. Can you post you configuration?

/Jacob

On 02/09/2010 21:00  wrote:

> 
> Hi,
> 
> 
> 
> My name is Levon, I represent Paradox company in Armenia. We are using
> your Kannel software. We have a problem with it now. When we sent
> message with simbols more then 160 figures are changing to some kind
> of hieroglyphs and messages are being sent with hieroglyphs. The
> problem is connected with multimessage sending. Please help us to
> solve this problem.
> 
> 
> 
> Regards,
> 
> Levon Harutyunyan.

Binfo on long messages

[Jacob Eiler]

Hi Kannel users.

When sending long messages with binfo attached, the binfo value is
attached to each message fragment. I wonder if binfo should not be
handled in the same way as dlr (which is only set on the first message
fragment).


/Jacob

GSM Modem

[Jacob Eiler]

Hi all.

I am planning to use Kannel with a GSM modem to send SMS notifications
from an application, i.e use a GSM modem as SMSC with Kannel.

I would like to know what kind of experiences you have with different
modems - for example the Siemens TC35.

/eiler


-- 
Jacob Eiler - Senior Consultant
[EMAIL PROTECTED] - +45 2374 0486
Unzet ApS - www.unzet.com

Re: mysql-dlr storage problem

[Jacob Eiler]

Hi James

It is only the query parameter values part that should be encoded:

http://192.168.111.151:8085/Kannel_Test/Recieve_dlr?message=%25a×tamp=%25tetc

Jacob Eiler
Apide ApS
e: jacob.ei...@apide.com
t: +45 2374 0486
w: apide.com


Den 11/06/2013 kl. 08.26 skrev testn4n1 :

Hi,

Hi tried the following insert query with the encoded url:

INSERT INTO send_sms (momt, sender, receiver, msgdata, sms_type, dlr_mask,
dlr_url, boxc_id) VALUES ('MT', '1234', '919067184864', 'Abbe russsh',
2, 31,
'http%3A%2F%2F192.168.111.151%3A8085%2FKannel_Test%2FReceive_dlr%3Fmessage%3D%25a%26timestamp%3D%25t%26sender%3D%25p%26receiver%3D%25P%26smsc_id%3D%25i%26dlr_value%3D%25d%26msg_id%3D%25F%26sendsms_user%3D%25n',
'box1');


Kannel gives the following error:

ERROR: URL

doesn't start with `http://' nor `https://'


Regards,
James

On 10 June 2013 19:27, spameden  wrote:

> check page 91 of the guide (Table 6-9. Parameters (Escape Codes))
>
>
> 2013/6/10 testn4n1 
>
>> Hi,
>>
>> I read the user-guide. It says about url encoding in the MO Messages
>> section. but it does not specify what are the key and values for the
>> parameters. i.e. which are the common parameters we need to pass in the
>> dlr-url.
>> Only an example is given like this:
>>
>> http://localhost/myscript?...&meta-data=%D&;...
>>
>> can you please tell me which are the other parameters and their values?
>> also, it specifies %D as value for the meta-data key. Is it something
>> that kannel replaces %D with some other value and then calls the specified
>> url? if yes, then what are the other such values for the keys?
>>
>> Regards,
>> James
>>
>>
>> On 10 June 2013 18:23, spameden  wrote:
>>
>>> Yes, you need to:
>>>
>>> 1) URLENCODE URL before inserting into database
>>> 2) pass parameters into URL, i.e.
>>>
>>> example:
>>> http%3A%2F%2F192.168.111.151%3A8085%2FKannel_Test%2FReceive_dlr%3Fsmsc-id%3D%25i%22%22
>>>
>>> Once again, read user-guide.
>>>
>>>
>>> 2013/6/10 testn4n1 
>>>
>>>> ok...the url i provided gets called the second i insert data into the
>>>> send_sms table but no parameters are passed. i printed all the request
>>>> parameters but got nothing.
>>>>
>>>>
>>>> On 10 June 2013 17:58, spameden  wrote:
>>>>
>>>>> To achieve this you need to put smsbox in between of the sqlbox and
>>>>> bearerbox or enforce smsbox id into boxc_id field, i.e.:
>>>>>
>>>>> INSERT INTO send_sms (momt, sender, receiver, msgdata, sms_type,
>>>>> dlr_mask, dlr_url, boxc_id) VALUES ('MT', '1234', '919067184864', 'Abbe
>>>>> russsh', 2, 31, '
>>>>> http://192.168.111.151:8085/Kannel_Test/Receive_dlr', 'smsbox_id');
>>>>>
>>>>>
>>>>>
>>>>> 2013/6/10 testn4n1 
>>>>>
>>>>>> i am trying to send sms by inserting data into send_sms table and
>>>>>> want to process dlrs with script using dlr_url. So, i have changed the
>>>>>> configuration to the following but i cannot receive anything in my
>>>>>> application:
>>>>>>
>>>>>>
>>>>>> group = sendsms-user
>>>>>> username = tester
>>>>>> password = foobar
>>>>>> forced-smsc = smpp-nexmo
>>>>>> name = users
>>>>>> dlr-url = http://192.168.111.151:8085/Kannel_Test/Receive_dlr
>>>>>>
>>>>>> #user-deny-ip = "*.*.*.*"
>>>>>> user-allow-ip = "*.*.*.*"
>>>>>> max-messages = 3
>>>>>> concatenation = 1
>>>>>> omit-empty = 1
>>>>>>
>>>>>>
>>>>>> I am executing the following query for inserting the data:
>>>>>>
>>>>>> INSERT INTO send_sms (momt, sender, receiver, msgdata, sms_type,
>>>>>> dlr_mask, dlr_url) VALUES ('MT', '1234', '919067184864', 'Abbe 
>>>>>> russsh',
>>>>>> 2, 31, 'http://192.168.111.151:8085/Kannel_Test/Receive_dlr');
>>>>>>
>>>>>> The dlr is not routed to my specified url. Can you please tell me
>>>>>> what is wrong here?
>>>>>>
>>>>>> Re

Re: What does these numbers mean in SMSC logs ?

[Jacob Eiler]

They are process and thread identifiers. For example the bearerbox process
starts multiple threads, one for routing, one for communication with the
smsbox etc. Normally each smsc will also start at least one thread, some
like the http-based drivers starts multiple threads as well.

BR
  Jacob


On Thu, Jun 27, 2013 at 1:37 PM, Hamid R. Hashmi wrote:

> What are these numbers /[9446] [6]/ for ???
>
>
> 2013-06-27 10:39:42 *[9446] [6]* DEBUG: SMPP PDU 0x7f8364000a50 dump:
>
> 2013-06-27 10:39:42 *[9446] [6]* DEBUG: type_name: enquire_link
>
> 2013-06-27 10:39:42* [9446] [6]* DEBUG: command_id: 21 = 0x0015
>
> 2013-06-27 10:39:42 *[9446] [6]* DEBUG: command_id: 21 = 0x0015
>
> 2013-06-27 10:39:42 *[9446] [6*] DEBUG: command_status: 0 = 0x
>
> 2013-06-27 10:39:42 *[9446] [7]* DEBUG: SMPP[mvoip]: Got PDU:
>
> 2013-06-27 10:39:42 *[9446] [6]* DEBUG: sequence_number: 519338176 =
> 0x1ef478c0
>
> 2013-06-27 10:39:42* [9446] [6] *DEBUG: SMPP PDU dump ends.
>
>
>
> --
> View this message in context:
> http://kannel.6189.n7.nabble.com/What-does-these-numbers-mean-in-SMSC-logs-tp28510.html
> Sent from the Kannel - User mailing list archive at Nabble.com.
>
>


-- 

*Jacob Eiler*
*t:* +45 2374 0486
*e:* jacob.ei...@apide.com
*w:* apide.com