I have two questions for those patches:
 
- I've commented out receive-port from the conf file but the bearerbox didn't start complaining about a missing parameter
- I've added keepalive = 1 to the conf file and set the debugging level to 0. I was expecting to see UCP 31 messages every minute in the logs but there are no such log entrys. Is that normal?
 
thanks,
Ozkan Erener
VeriPark - www.veripark.com
-----Original Message-----
From: Bruno David Simões Rodrigues [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 18, 2001 11:27 PM
To: [EMAIL PROTECTED]
Subject: [Patch] EMI2 Keepalive patch

Hi.
 
I've sent the emi2 keepalive patch to the CVS.
 
I have more code in here. I have to clean the code, cut it in pieces and write documentation before sending to CVS.
 
Between what I have working, what I'm coding now and what I (my company) need, there will be these patches:
 
. Keepalive for emi2 (again)
    I think it's fundamental for everyone that uses "our-port"
. Optional "receive-port" for emi2
    When using one connection and keepalive, you don't need receive-port
. Flash re-written to support unicode and others
    Flash is incompatible with other DCS values
. Unicode extention (text=xxxxyyyy)
    DCS=unicode and pass directly the hex text to the message (concatenation
code included)
. Message Waiting Indicator for emi2 and AT (and possibly others, if
wanted and I get some time for it)
    With "how many messages" and text
. Username limits
    for each sendsms-user, control if it can use udh, flash, mwi and unicode
fields. Sometimes you want a user to only send text.
    The same syntax for sms-service (additional to accept-x-kannel-headers)
. Some php4 scripts to contrib
    Encode Nokia Smart Messaging, OTA Wap config and bookmarks, Wap Push SMS
(still to test: I want a nokia 6310!)
    Decoding of binary messages received (example: when receiving a binary
sms of type bookmark, decodes it and send only the name and url to some server)
. Validity and defered time
 
(not in any particular order)
 
 
regards,
--
Bruno Rodrigues

Reply via email to