I need to edit sms_emi.c field to do the ff:
1. If binfo is the right code, say 1028 (for the 1st part of the push
message), place it on the xser 0c field.
2. If binfo is some bogus code, say 1000 (for the 2nd and 3rd parts of
the push message), do not put an xser 0c field.
3. If binfo is empty
Hi,
First question while working on CPA.
For this CPA, there is a different between a MT-Push and MT-Reply, in
that if its a MT-Reply, a transaction_id need to be mapped back to the
original MO sent from the SMSC.
So the scenario is,
1. One MO comes in from SMSC, it contains a transaction ID,
Stipe,
The Base element in HTML specifies an absolute URI that acts as the base URI
for resolving relative URIs.
For example, given the following BASE declaration and A declaration:
+ADwAIQ-DOCTYPE HTML PUBLIC +ACI--//W3C//DTD HTML 4.01//EN+ACI-
+ACI-http://www.w3.org/TR/html4/strict.dtd+
Sorry, forgot to reply to the list!
Earljon Hidalgo wrote:
Thanks very much! I already fixed the problem... =)
Right now, we are having problem on the pulling of messages.. we always
get Syntax error on our bearerbox logs..
Any ideas bout this?
We have a UCP/EMI connection...
Here are the log
Stipe,
You're right. Relative URL in the page will lead to serious problem. Do you
have any solutions? Maybe we should modify the response page, tell the wap
terminal the base URI (or host) in the WML/XHTML document.
Best Regards,
Guanghua Hou
- Original Message -
From: +ACI-Stipe Tolj+AC
Stipe,
You're right. Relative URL in the page will lead to serious problem. Do you
have any solutions? Maybe we should modify the response page, tell the wap
terminal the base URI (or host) in the WML/XHTML document.
Best Regards,
Guanghua Hou
- Original Message -
From: +ACI-Stipe Tolj+AC
Stipe,
You're right. Relative URL in the page will lead to serious problem. Do you
have any solutions?
Best Regards,
Guanghua Hou
- Original Message -
From: "Stipe Tolj" <[EMAIL PROTECTED]>
To: "Rene Kluwen" <[EMAIL PROTECTED]>
Cc: "ghhou" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Th
Alan McNatty wrote:
>
> Just a question really. I've been looking at the X-Kannel headers and
> noted that if you receive an MO message from SMSC 'A' and you specify
> the message should go back via SMSC 'A' for normal short message fine.
> However if you respond with content with content that get
Rene Kluwen wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> If you mean a relative URL in the Location: header.
> Then this is something against HTTP specs. One should not use them.
> Even though almost all browsers do prepend the original http-path if you do
> send them.
nop, the
Hello All,
Just a question really. I've been looking at the X-Kannel headers and
noted that if you receive an MO message from SMSC 'A' and you specify
the message should go back via SMSC 'A' for normal short message fine.
However if you respond with content with content that gets split. The
first
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If you mean a relative URL in the Location: header.
Then this is something against HTTP specs. One should not use them.
Even though almost all browsers do prepend the original http-path if you do
send them.
Rene Kluwen
Chimit
- -Original Message-
> attached you can find patch that does following:
> 1) removes ssl_mutex
> 2) correct SSL_[read|write] operations
> 3) removes SSL_connect and SSL_accept because these
> handled by openssl
> library trasparent while SSL_[read|write] operations.
>
Did you address this issue ?
Hi List,
attached you can find patch that does following:
1) removes ssl_mutex
2) correct SSL_[read|write] operations
3) removes SSL_connect and SSL_accept because these handled by openssl
library trasparent while SSL_[read|write] operations.
I am not a openssl guru and t
Hi Slava,
no need to vote for my patch, because your approach is better.
IMO the discussion difftime vs. thread is needless, because we should
aim for scalability, and the thread-approach scales
Thus I have merged my client stuff into your thread-stuff and voila, see
the attached patch. Let
hmm, which smsc module are you using for this?
it may happens when smsc module set smsc field in Msg struct w/o to check if
it was allocated before...
On Wednesday 26 November 2003 17:07, Aarno Syvänen wrote:
> If do so, Kannel reports a leak: Allocated by dlr_find at gw/dlr.c:397.
> This is tur
If do so, Kannel reports a leak: Allocated by dlr_find at gw/dlr.c:397.
This is turning really hairy.
Aarno
On 26.11.2003, at 16:24, Alexander Malysh wrote:
On Wednesday 26 November 2003 15:45, Aarno Syvänen wrote:
A new try :(
try again ;) see bellow...
Please just skip dlr.c because dlr-core/dl
On Wednesday 26 November 2003 15:45, Aarno Syvänen wrote:
> A new try :(
try again ;) see bellow...
Please just skip dlr.c because dlr-core/dlr-mysql/dlr-internal were tested for
memleaks with valgrind ...
RCS file: /home/cvs/gateway/gw/dlr.c,v
retrieving revision 1.43
diff -u -B -b -r1.43 dlr.c
A new try :(
cvs.diff
Description: Binary data
Aarno
On 26.11.2003, at 12:32, Alexander Malysh wrote:
Hi Aarno,
would you please explain???
RCS file: /home/cvs/gateway/gw/dlr.c,v
retrieving revision 1.43
diff -u -B -b -r1.43 dlr.c
--- gw/dlr.c 15 Nov 2003 13:14:23 - 1.43
+++ gw/dlr.c 2
Hi, David.
Yes, I have thought about exactly the same:
either difftime+last_check or thread-switch.
I didn't compare the efficient of thease methods.
I'v made thread because switch occur 1 time at minute (or any configured
timeout) but difftime can occur many times in minute (unpredictable, depends
Hi Slava (and others),
yeah, you have got a point there...
But this can be avoided by using something like:
last_check = time(NULL);
while
now = time(NULL);
if ((ret == 0) || (difftime(now, last_check) >= MIN_TIME_OUT)) {
check_timeout();
last_check = time(NUL
Hi, David.
Ok. Let's suppose that we get realy high load on kannel http server.
So we get, let's say, ~5 new connection in second.
Threrefore we will check for timeouts ~5 times in second. I think it is not
efficient way.
That why I have created the thread to deal with it.
You must to choose betwe
Hi Slava,
argh, correct. An IMO easy solution is to call check_timeout even if the
recent poll did not timeout, as in:
[snip]
if ((ret = gwthread_poll(tab, n, MIN_TIME_OUT)) < 1) {
switch(ret) {
case 0: /* timeout */
break;
case -1: /* error */
Hi Aarno,
would you please explain???
RCS file: /home/cvs/gateway/gw/dlr.c,v
retrieving revision 1.43
diff -u -B -b -r1.43 dlr.c
--- gw/dlr.c15 Nov 2003 13:14:23 - 1.43
+++ gw/dlr.c26 Nov 2003 10:15:54 -
@@ -362,10 +362,11 @@
* NOTE: If typ is end status (e.g. DELIVERED) th
Hi, David.
If I understand correctly then check_timeouts() will be called only if no any
new connection to kannel http server for MIN_TIME_OUT time.
So for busy enviroment this check will be quite undeterminate and can
be not called for hours. Isn't it?
David Schmitz wrote:
Hi again,
attached i
Hi List,
I attach cvs diff for fixing kannel leaks (as tested with our mmsc).
There are new wrappers I used to find these leaks., too. And
there was one unhandled NULL pointer.
Perhaps you check & test these
cvs.diff
Description: Binary data
aarno
Understood. Appreciate your contributions to the development and the
mailing lists.
Stipe Tolj wrote:
Raditha Dissanayake wrote:
Stipe,
this sounds like a beast that everyone want's to get released from it's
cage :-) I know 'me too' posts are discouraged but can't resist this one
yep,
Raditha Dissanayake wrote:
>
> Stipe,
> this sounds like a beast that everyone want's to get released from it's
> cage :-) I know 'me too' posts are discouraged but can't resist this one
yep, seems it's a "most wanted" animal living in this little Wapme box
;)
So it's not up to me. Main holdin
Stipe,
this sounds like a beast that everyone want's to get released from it's
cage :-) I know 'me too' posts are discouraged but can't resist this one
Stipe Tolj wrote:
Rory Campbell-Lange wrote:
How can anyone help to get the mmsbox up and running?
hmmm, you can't help ;) the beast i
Hi again,
attached is the new patch for HTTP-timeouts. I have included the work of
Slava wrt. server-timeouts, but modified it such that no new thread is
needed. Another new thing is the purging of active clients upon
port-removal, as suggested by Alex.
Please, try it out and share your commen
Hi list,
I found that Kannel doesn't process socket timeout. If the WEB site
doesn't response, kannel will keep the socket for ever.
David, any comments from your side to this?
You should check David's patch that he will be posting to the list in
a couple of hours. It implements both server
Hi list,
forwarded to the list.
Stipe
mailto:[EMAIL PROTECTED]
---
Wapme Systems AG
Münsterstr. 248
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:[EMAIL PROTECTED]
http://www.wapme-systems.de
ghhou wrote:
>
> If there is comparative URL in the redirection page, then error will occurs.
> For the terminal keeps the original Host, it will send the request to the
> original web site.
sorry, seems it's too early in the morning ;) -- I didn't get the
point. Can you please re-fraze this?!
S
> I found that Kannel doesn't process socket timeout. If the WEB site
> doesn't response, kannel will keep the socket for ever.
David, any comments from your side to this?
You should check David's patch that he will be posting to the list in
a couple of hours. It implements both server and client
Rory Campbell-Lange wrote:
>
> How can anyone help to get the mmsbox up and running?
hmmm, you can't help ;) the beast is still living in a cage here at
Wapme and "waits" to be released.
The only way to get this release faster done is to consider modular
configure/make process enhancements so we
> Would you pls tell me where to get "mmsbox" software? I can't found it in
> Kannel.
it's yet not released, consider it property of Wapme at the present
time.
Stipe
mailto:[EMAIL PROTECTED]
---
Wapme Systems AG
Münsterstr. 248
404
35 matches
Mail list logo
