additions... to SRS
Vishal, For us to properly synchronize the following we need the adjacent tables to be synchronized contacts > email list email table(*.edb) contacts > email list email table(*.edb) contacts > email list email table(*.edb)
Re: GPRS and SSL
Yes Sure, I will report my experiences after I've tested that, meanwhile I am waiting for report from others, any body? Regards, Joel - Original Message - From: "Navjot Singh" <[EMAIL PROTECTED]> To: "Julyanto Sutandang" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Monday, February 23, 2004 1:02 PM Subject: RE: GPRS and SSL > sorry to say but i never tested wtls with kannel wapbox. but you ca share > your experiences rather problems :-) > > >-Original Message- > >From: Julyanto Sutandang [mailto:[EMAIL PROTECTED] > >Sent: Friday, February 20, 2004 4:40 PM > >To: Navjot Singh > >Cc: [EMAIL PROTECTED] > >Subject: Re: GPRS and SSL > > > > > >Dear All, > > > >I just wondering how's the status of implementation of WTLS in the WAP > >Gateway? is it already stable? or there's some trick and tip to use that? > > > >I have read some docs but didn't get any satisfied information regarding > >that. > > > >Is there Any one who has implemented WAP 1.2.x with WTLS through GPRS ? > > > >Please share your success story here, me and may be some folks > >here would be > >very appreciated > > > >Thank you, > > > >Joel > >- Original Message - > >From: "Navjot Singh" <[EMAIL PROTECTED]> > >To: "Robert Tomohamat" <[EMAIL PROTECTED]>; > ><[EMAIL PROTECTED]> > >Sent: Friday, February 13, 2004 6:32 PM > >Subject: RE: GPRS and SSL > > > > > >> hi robert, > >> > >> what's the port number that you have set for secure connection oriented > >port > >> in your kannel conf? should be 9203 by default. > >> if it is open, your telnet to that port should work. > >> > >> i have never used it myself so can't help you much. may be someone else > >can > >> guide? however, if you are able to make it happen, pls let me > >know i would > >> also like to run a test bed myself. > >> > >> regards > >> Navjot Singh > >> > >> >-Original Message- > >> >From: Robert Tomohamat [mailto:[EMAIL PROTECTED] > >> >Sent: Friday, February 13, 2004 2:31 PM > >> >To: Navjot Singh > >> >Subject: Re: GPRS and SSL > >> > > >> > > >> >Dear Navjot, > >> > > >> >Thank you for your answer. I set the security setting in my phone > >> >to on, but > >> >now the connection fails with the following error message: > >> > > >> >Communication error, secure connection failed > >> > > >> >Do you have any idea how to solve this? > >> > > >> >Kind regards, > >> >Robert Tomohamat > >> > > >> > > >> >- Original Message - > >> >From: "Navjot Singh" <[EMAIL PROTECTED]> > >> >To: "Robert Tomohamat" <[EMAIL PROTECTED]>; > >> ><[EMAIL PROTECTED]> > >> >Sent: Friday, February 13, 2004 6:30 AM > >> >Subject: RE: GPRS and SSL > >> > > >> > > >> >> if you have compiled your kannel with openssl then kannel > >> >already supports > >> >> TLS for you. In you cell phone service setting, you can set connection > >as > >> >> secure and kanell will do that for you. > >> >> > >> >> never done anything with live GPRS cnxns though > >> > > >> > > >> > >> > >> > > > > > > >
Re: not sending sms (nokia 6310 virtual SMSC)
After some more testing on the phone, I found out that it is cactus! The search continues for a working mobile phone. Phillip Lucs >> Hi to the group, >> >> I am not able to send SMSs yet. I have read through the archives and >> user-guide and have constructed a suitable configuration file. >> >> I built kannel from source. >> >> I am using a Nokia 6310 as a virtual SMSC. >> >> The configuration file is: >> >> group = core >> admin-port = 13000 >> smsbox-port = 13001 >> admin-password = phillip >> log-file = "/var/log/kannel/phil_bearerbox.log" >> log-level = 0 >> access-log = "/var/log/kannel/phil_bearer-access.log" >> box-allow-ip = "127.0.0.1" >> >> group = modems >> id = nokiaphone >> name = "Nokia Phone" >> detect-string = "nokia" >> speed = 9600 >> >> group = smsc >> smsc = at2 >> smsc-id = nok6310 >> speed = 9600 >> modemtype = nokiaphone >> device = /dev/ttyS0 >> connect-allow-ip = "127.0.0.1" >> sms-center = "+61411990001" >> >> group = smsbox >> bearerbox-host = localhost >> sendsms-port = 13013 >> log-file = "/var/log/kannel/phil_smsbox.log" >> log-level = 0 >> access-log = "/var/log/kannel/phil_sms-access.log" >> >> group = sendsms-user >> username = phillip >> password = phillip >> max-messages = 10 >> concatenation = true >> >> group = sms-service >> keyword = nop >> text = "You asked nothing and I did it!" >> catch-all = true >> >> group = sms-service >> keyword = default >> text = "No service specified" >> >> group = sms-service >> keyword = www >> get-url = "http://%S"; >> group = sms-service >> keyword = complex >> get-url = "http://host/service?sender=%p&text=%r"; >> accept-x-kannel-headers = true >> max-messages = 3 >> concatenation = true >> >> I'm started kannel from the command line. >> >> bearerbox -v 0 /etc/kannel/kannel.conf >> >> where kannel.conf is the configuration file. >> >> The output i am getting when starting the bearerbox is: >> >> 2004-02-24 02:13:57 [0] INFO: Debug_lvl = 0, log_file = , log_lvl >> = >> 0 >> 2004-02-24 02:13:57 [0] WARNING: DLR: using default 'internal' for >> storage >> type. >> 2004-02-24 02:13:57 [0] DEBUG: Kannel bearerbox version `1.2.1'. >> System Linux, release 2.2.20-idepci, version #1 Sat Apr 20 12:45:19 EST >> 2002, machine i686. >> Hostname fenris.valhalla.com, IP 192.168.1.2. >> Libxml version 20419. >> Using native malloc. >> >> 2004-02-24 02:13:57 [0] INFO: Added logfile >> `/var/log/kannel/phil_bearerbox.log' with level `0'. >> 2004-02-24 02:13:57 [0] INFO: Started access logfile >> `/var/log/kannel/phil_bearer-access.log'. >> 2004-02-24 02:13:57 [0] INFO: SSL not supported, no SSL initialization >> done. >> 2004-02-24 02:13:57 [0] DEBUG: HTTP: Opening server at port 13000. >> 2004-02-24 02:13:57 [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller) >> 2004-02-24 02:13:57 [0] DEBUG: Started thread 2 >> (gwlib/http.c:server_thread) >> 2004-02-24 02:13:57 [0] DEBUG: Started thread 3 >> (gw/bb_http.c:httpadmin_run) >> 2004-02-24 02:13:57 [0] DEBUG: starting smsbox connection module >> 2004-02-24 02:13:57 [0] DEBUG: Started thread 4 >> (gw/bb_boxc.c:smsboxc_run) >> 2004-02-24 02:13:57 [0] INFO: AT2[nok6310]: configuration shows >> modemtype >> >> 2004-02-24 02:13:57 [0] DEBUG: AT2[nok6310]: Reading modem definitions >> from >> 2004-02-24 02:13:57 [0] DEBUG: AT2[nok6310]: Found <1> modems in config >> 2004-02-24 02:13:57 [0] INFO: AT2[nok6310]: read modem definition for >> >> 2004-02-24 02:13:57 [0] DEBUG: Started thread 5 >> (gw/smsc/smsc_at2.c:at2_device_thread) >> 2004-02-24 02:13:57 [0] DEBUG: Started thread 6 >> (gw/bb_smscconn.c:sms_router) >> 2004-02-24 02:13:57 [0] INFO: >> 2004-02-24 02:13:57 [0] INFO: Kannel bearerbox II version 1.2.1 starting >> 2004-02-24 02:13:57 [0] INFO: MAIN: Start-up done, entering mainloop >> 2004-02-24 02:13:57 [0] DEBUG: AT2[nok6310]: start called >> 2004-02-24 02:13:57 [5] INFO: AT2[nok6310]: opening device >> 2004-02-24 02:13:57 [5] DEBUG: AT2[nok6310]: device opened >> 2004-02-24 02:13:57 [6] DEBUG: sms_router: time to sleep >> 2004-02-24 02:13:57 [6] DEBUG: sms_router: list_len = 0 >> 2004-02-24 02:13:58 [5] DEBUG: AT2[nok6310]: device opened >> 2004-02-24 02:13:58 [5] INFO: AT2[nok6310]: init device >> 2004-02-24 02:13:58 [5] INFO: AT2[nok6310]: speed set to 9600 >> 2004-02-24 02:13:58 [5] DEBUG: AT2[nok6310]: --> AT^M >> >> I find this worrying that execution of the bearerbox command ends here. >> There is only one AT^M command, should there be more communication >> between >> the 6310 and kannel? >> >> I get the following when i try to send an sms through my browser using >> the >> following command >> http://smsbox.host.name:13001/cgi-bin/sendsms?username=phillip&password=phillip&to=0404042346&text=Hello+world >> >> 2004-02-24 02:16:32 [4] DEBUG: Started thread 7 (gw/bb_boxc.c:function) >> 2004-02-24 02:16:32 [7] INFO: Client connected from <192.168.1.30> >> 2004-02-24 02:16:32 [7] DEBUG: Started thread 8 >> (gw/bb_boxc.c:boxc_sender) >> >> However, the br
[off-topic] OTA SIM update
Hi gang, Hopefully someone can enlighten me on this one. What exactly can be changed by an 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: Decoding MMS PDUs
Bill Brigden wrote: > If you have a look for: > > WAP-203-WSP-2504-a.pdf > WAP-209-MMSEncapsulation-20020105-a.pdf And put aside a week to stare at the WAP specs until your eyes drop out. They don't make this stuff trivial to understand, but its quite logical once you've got it sussed. -- Ian Cass
Kannel CIMD2 tariff support.
Hi, I'm interested in knowing does Kannel 1.3.1 support CIMD2 tariff properly?, since with earlier kannels there was a problem with tariff, because at least we have a need to send different tariffs with MT messages, I'm running a patched version of kannel cvs, which supports tariff, but I'm in need of upgrading kannel and can't do that without tariff support so..If it does support it, how to specify different tariffs? Thx in advance Pete
RE: Decoding MMS PDUs
Are you just meaning the binary mms file - or the binary mms notification? If you have a look for: WAP-203-WSP-2504-a.pdf WAP-209-MMSEncapsulation-20020105-a.pdf (There may be newer versions of them, I haven't checked) Also, a nokia document: How to Create MMS Services_v3_21.pdf ..has some nice pictures and a graphical explanation of things.. Bill. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: 23 February 2004 11:52 To: [EMAIL PROTECTED] Subject: Decoding MMS PDUs Hi, I've been trying to encode/decode PDU's for sending an MMS message over a WAP channel, and in the process trying to understand exactly how the specification for the binary layout of the encoded PDU works. Basically, I can parse all of the headers and the body of the message, but I cannot find a reference which descibes exactly how a text MIME messages with a SMIL and multiple data bodyparts is encoded into the binary PDU. Specifically, I cannot find any reference to how the binary PDU indicates the end of the header fields, the number/content-type of bodyparts, etc. If anyone could point me to a useful discussion, worked example, or specification for this, I would be grateful. Regard, Vin
RE: Decoding MMS PDUs
> > If anyone could point me to a useful discussion, worked > example, or specification for this, I would be grateful. > Look at the WSP multipart encoding specification.
Decoding MMS PDUs
Hi, I've been trying to encode/decode PDU's for sending an MMS message over a WAP channel, and in the process trying to understand exactly how the specification for the binary layout of the encoded PDU works. Basically, I can parse all of the headers and the body of the message, but I cannot find a reference which descibes exactly how a text MIME messages with a SMIL and multiple data bodyparts is encoded into the binary PDU. Specifically, I cannot find any reference to how the binary PDU indicates the end of the header fields, the number/content-type of bodyparts, etc. If anyone could point me to a useful discussion, worked example, or specification for this, I would be grateful. Regard, Vin
