Re: (no subject)

2002-11-11 Thread Andrea Trasatti
Are you sure the page is ok and reachable? Sometimes devices with openwave 
browsers, when the homepage times out go to openwave's homepage.

Which device are you using?

On 30 Oct 2002 at 21:20, Sherly Scott wrote:

 
 Hi all!!
 
 I’m using kannel 1.2. I want that my cellphone load this page as default: 
http://192.24.xxx.xx/test/test.asp;
 
 So, I'm setting the map-url = http://192.24.xxx.xx/test/test.asp; and device-home = 
http://192.24.xxx.xx/test/test.asp;, is that ok?.
 
 The problem is that my cellphone doesn’t open this page as default, it always opens 
the  http://www.openwave.com/wml/opwv. I don’t know why it opens the openwave when 
I’m seting the device home as test.asp in the kannel.conf, should I have to set 
another variable or maybe I need to do another 
change? 
 
 Is my kannel.conf right?
 
 Please, could anybody help me? What can I do?
 
 This is my kannel.conf:
 
 group = core 
 
 admin-port = 13000
 
 admin-password = bar
 
 admin-deny-ip = *.*.*.*
 
 admin-allow-ip = 127.0.0.1
 
 wapbox-port = 13002
 
 wdp-interface-name = *
 
 log-file = /var/log/kannel/bearerbox.log
 
 box-deny-ip = *.*.*.*
 
 box-allow-ip = 127.0.0.1
 
 group = wapbox
 
 bearerbox-host = localhost
 
  map-url = http://192.24.xxx.xx/test/test.asp; 
 
 device-home = http://192.24.xxx.xx/test/test.asp; 
 
  log-file = /var/log/kannel/wapbox.log
 
 Please help me!
 
 Thanks a lot in advance to everyone!
 
 Sherly
 
 
 -
 Yahoo! Messenger
 Nueva versión: Webcam, voz, y mucho más ¡Gratis!






RE: (no subject)

2002-10-20 Thread Wilf \(Neil Wilkinson\)
AFAIK, SMTP is not used by SMSCs themselves, but is often used by people
providing SMS Gateways.  (In a previous life, I built an SMTP interface to
an existing SMS gateway to make it more accessible for clients that didnt
have much(any) technical nouse.)

That may be why you have heard of it - writing a simple script that reacts
to a mail arriving to a certain account (sendmail can provide this i
believe) and makes a HTTP transaction with Kannel would do the trick.

But as Oded says, SMTP has a heavy pay-load and the client would have to be
sent a seperate message for success/failure (and if they are sending
thousands of emails, it would be complicated to tarry up the status with the
original sms as they would have to parse the emails that are returned).


Wilf

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:users-admin;kannel.3glab.org]On Behalf Of Oded Arbel
 Sent: Sunday, 20 October 2002 5:30 PM
 To: Blesson Paul; [EMAIL PROTECTED]
 Subject: RE: (no subject)




  -Original Message-
  From: Blesson Paul [mailto:blessonpaul;softhome.net]

  In some documentation, we found that, many
  commercial SMSC's work with
  SMTP protocol. Why there is no support for SMTP in Kannel

 I'm not aware of any SMSC that supports SMTP, or at least - no
 SMSC that supports SMTP and not one of the other protocols that
 Kannel can use to deliver SMs. please note that SMTP is not a
 good protocol to deliver SMs with, as it is designed and
 optimised for large data transfer (heck - SMTP handshake alone is
 longer then most SMs). since an SMTP connection is
 unidirectional, to set up a proper system for SMTP messaging the
 network provider and content provider both need to set up lots of
 globally accesiable records which are not directly related to SM.
 As a result, it was never a requirment for Kannel to have an SMTP
 driver for SM delivery, and if your provider offers you an option
 to use a protocol other then SMTP, you better take that offer.

 OTOH, MMS messaging does have provisions for SMTP messaging, and
 due to the large size of most MMs, and the complicated nature of
 the MM* protocols, using SMTP for connections to MMSC is a good idea.

 --
 Oded Arbel
 m-Wise mobile solutions
 [EMAIL PROTECTED]

 +972-9-9581711 (116)
 +972-67-340014

 ::..
 We promise according to our hopes, and perform according to our fears.






Re: (no subject)

2002-10-07 Thread Kwok Peng Tuck

The kannel user guide doesn't say anything about the system-id in the 
smpp section.
I think the password is test, but you should really double check with 
your provider.
Doesn't hurt to try the password 'test' first :) .


Cipher Strength wrote:


 While trying to connect through SMPP . I got the follwoing error.


 2002-10-07 12:08:23 [0] INFO: Debug_lvl = 1, log_file = none, 
 log_lvl = 0
 2002-10-07 12:08:23 [0] WARNING: DLR: using default 'internal' for 
 storage type.
 2002-10-07 12:08:23 [0] INFO: Added logfile `/gdev116/core.log' with 
 level `0'.
 2002-10-07 12:08:23 [0] INFO: 
 2002-10-07 12:08:23 [0] INFO: Kannel bearerbox II version 1.2.0 starting
 2002-10-07 12:08:23 [0] INFO: Started access logfile 
 `/gstab12/coreaccess.log'.
 2002-10-07 12:08:23 [0] INFO: SSL not supported, no SSL initialization 
 done.
 2002-10-07 12:08:23 [0] INFO: MAIN: Start-up done, entering mainloop
 2002-10-07 12:08:23 [5] ERROR: 
 SMPP[SMPP:192.168.1.1:5005/5005:test:VMA]: SMSC rejected login to 
 transmit, code 0x000d.
 2002-10-07 12:08:23 [6] ERROR: 
 SMPP[SMPP:192.168.1.1:5005/5005:test:VMA]: SMSC rejected login to 
 receive, code 0x000d.


 I got the following information from my operator

 IP_ADDRESS = 192.168.1.1
 PORT = 5005
 SYSTEM_ID = test
 SYSTEM_TYPE = test

 I have configured the follwoing entries in conf file.

 group = smsc
 smsc = smpp
 host = 192.168.1.1
 smsc-username = test
 smsc-password = 
 port = 5005
 receive-port = 5005
 system-type = VMA
 address-range = 

 from the user guide what i understand is, system-id is username  but i 
 have no password . kindly help me
 Regards
 CIPHER


 _
 Chat with friends online, try MSN Messenger: http://messenger.msn.com









RE: (no subject)

2002-09-05 Thread Oded Arbel

It's not a problem - simply a misconfiguration. what modems are you using ?

Alternativly - you can implement support for +CMTI notifications into the AT2 module 
:-) . a patch to do that was already submitted once upon a time to the list, but it 
wasn't clean enough and the author never pursued that after the sim-buffering patch 
went it. with the sim-buffering architecture it shouldn't be hard to implement.

--
Oded Arbel
m-Wise mobile solutions
[EMAIL PROTECTED]

+972-9-9581711 (116)
+972-67-340014

::..
buddha nature
aliens worship
twinkle little star



 -Original Message-
 From: Avner Sternheim [mailto:[EMAIL PROTECTED]]
 Sent: Thursday, September 05, 2002 4:39 PM
 To: Oded Arbel; Avner Sternheim; [EMAIL PROTECTED]
 Cc: [EMAIL PROTECTED]
 Subject: RE: (no subject)
 
 
 but it depends on the messages I'm sending, from one type of 
 mobile I get
 messages and from another I dont 
 can you recommend on another modem which doesn't have this 
 sort of problems
 ?
 
 -Original Message-
 From: Oded Arbel [mailto:[EMAIL PROTECTED]]
 Sent: Thursday, September 05, 2002 3:36 PM
 To: Avner Sternheim; [EMAIL PROTECTED]
 Cc: [EMAIL PROTECTED]
 Subject: RE: (no subject)
 
 
 
 
  -Original Message-
  From: Avner Sternheim [mailto:[EMAIL PROTECTED]]
 
  I'm using kannel stable version 1.2
 
  On an incoming messages it says the following in the bearerbox-log: 
   DEBUG: AT2[/dev/ttyS1]: -- +CMTI: SM,3 
  Can anyone tell me, why Kannel doesn't fetch the message  ?? 
 
 Your modem is set to store messages in to SIM memory instead 
 of forwarding
 the SM directly to Kannel. Currently kannel does not support 
 notifications
 of submition to SIM memory. you can either fix your init 
 string to issue the
 correct CNMI setting to cause the modem to delivery the SMs 
 directly to the
 TE (Kannel) or enable sim-buffering on the modem. please consult the
 demonstration configuration files in the doc directory on how 
 to do both. 
 
 --
 Oded Arbel
 m-Wise mobile solutions
 [EMAIL PROTECTED]
 
 +972-9-9581711 (116)
 +972-67-340014
 
 ::..
 Microsoft should switch to the vacuum cleaner business where 
 people actually
 want products that suck.
 




RE: (no subject)

2002-05-06 Thread Oded Arbel

You have to set smsc-id for each one (different for each one) and then
send to sendsms the id of the smsc you want to use as one of the
parameters (the key is 'smsc' of course). you also need to setup
'access-lists' with preffered-smsc-id, allowed-smsc-id and
denied-smsc-id, other wise Kannel will route randomly between the SMSCs.

--
Oded Arbel
m-Wise Inc.
[EMAIL PROTECTED]
(972)-67-340014
(972)-9-9581711 (ext: 116)

::..
Anyone who considers arithmetical methods of producing random digits
is, of course, in a state of sin.
-- John von Neumann


 -Original Message-
 From: Florian Schlums [mailto:[EMAIL PROTECTED]]
 Sent: Sunday, May 05, 2002 11:25 PM
 To: [EMAIL PROTECTED]
 Subject: (no subject)
 
 
 I have two different smsc.
 How do I select the smsc I want to use?
 Each smsc is defined like this:
 #
 group = smsc
 smsc = at (or anything else)
 




Re: (no subject)

2002-01-09 Thread David Holland

On Tue, Jan 08, 2002 at 08:50:01AM -, Andy Goodwin wrote:
 SUBSCRIBE [EMAIL PROTECTED]

To subscribe to this list, either:

1. visit http://kannel.3glab.org/mailman/listinfo/users
  or
2. send mail to [EMAIL PROTECTED] with Subject: subscribe

This has been a public service announcement.

Dave
-- 
David Holland   =*=   Systems Manager   =*=   tel: +44 01223 478900
http://www.3glab.com/   =*= 3G Lab, UK  =*=   fax: +44 01223 478901




Re: (no subject)

2002-01-06 Thread Stipe Tolj

Off-topic:

First of all I would like to suggest to use a more related subject
line for mails. (no subject) is often mis-noticed by developers. So
if you want some fast help, make sure your subject line keeps the
folks in charge interested :)

Ok, not for the core:

 I installed Kannel 1.1.4 (Cygwin 1.1.x) on Win2000. I used the conf file from RedHat 
7.1, but it did not work. So I changed device for AT from /dev/ttyS0 to COM1, it 
started working. Strangely, its giving following error after I make /cgi-bin/status 
request.

/cgi-bin/status !??!?!

Do you mean http://hostname:port/status?... for the status
page?!
There is no URI mapped to an function for /cgi-bin/status.

 2003-01-05 07:42:10 [2] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'.
 2003-01-05 07:42:10 [3] DEBUG: HTTP: Resetting HTTPClient for `127.0.0.1'.
 2003-01-05 07:42:47 [3] DEBUG: HTTP: Resetting HTTPClient for `127.0.0.1'.
 2003-01-05 07:42:56 [3] DEBUG: HTTP: Resetting HTTPClient for `127.0.0.1'.
 2003-01-05 07:43:43 [8] INFO: Connection closed by the box 127.0.0.1
 2003-01-05 07:43:56 [1] ERROR: Error reading from fd 29:
 2003-01-05 07:43:56 [1] ERROR: System error 104: Connection reset by peer
 2003-01-05 07:43:56 [1] ERROR: Error reading from fd 29:
 2003-01-05 07:43:56 [1] ERROR: System errfor 104: Connection reset by peer
 2003-01-05 07:43:56 [1] DEBUG: HTTP: Destroying HTTPClient area 0x1002ad48.
 2003-01-05 07:43:56 [1] DEBUG: HTTP: Destroying HTTPClient for `127.0.0.1'.

This means your HTTP connections go away. What HTTP client (browser)
are you using for this?!

I have seen these on Cygwin too, without any considerable effect to
the functionality of Kannel.

 My kannel.conf reads
 
 group = core
 admin-port = 13000
 smsbox-port = 13001
 admin-password = shridhar
 admin-allow-ip = *.*.*.*
 log-file = kannel.log
 log-level = 0
 box-allow-ip = *.*.*.*
 access-log = access.log
 
 # SMSC CONNECTIONS
 
 group = smsc
 smsc = at
 smsc-id = nokia
 modemtype = nokiaphone
 device = COM1

In the Cygwin world the serial COM devices are 

  /dev/com1
  /dev/com2
  etc.

So please use them for the device directive.

 Any suggestion for the error. And I want to know, does anybody in group using Cygwin 
port of kannel for production environment and how stable it is, as compared to Linux 
version. Thanks in advance.

I'm developing all major changes on Cygwin 1.3.x for Kannel and test
it there too. So any changes made to CVS from my side are tested on
Cygwin, Linux, Solaris.

Unfortunatly I can't give any guess about the production stability,
due that we run a Linux and a Solaris machine for high-load
production. But there is a Cygwin machine running recent Kannel cvs in
idle mode, which means without heay load and is stable.

Andrea Viscovich [EMAIL PROTECTED] runs a Win2000 machine running
Cygwin 1.x with several modems attached and seems to be happy enought.

Stipe

[EMAIL PROTECTED]
---
Wapme Systems AG

Münsterstr. 248
40470 Düsseldorf

Tel: +49-211-74845-0
Fax: +49-211-74845-299

E-Mail: [EMAIL PROTECTED]
Internet: http://www.wapme-systems.de
---
wapme.net - wherever you are