Hi,
On 11.3.2004, at 13:40, Stipe Tolj wrote:
Joachim Breitner schrieb:
Take a look at fakewap.c in the Kannel src tree. It's a good place
to start for a WAP client. It lacks certain features (SAR, WTLS) but
its better than starting from scratch.
fakewap.c seems to use hardcoded WSP and and WTP
Vjacheslav Chekushin schrieb:
Hi, Stipe.
Cookies wsp packing/unpacking is the secondary problem.
The primary problem for me now is Encoding-Version support.
In wsp_headers.c Version-Encodning handled in some places, but not handled in
another impotent places. This is for example parameter
Hello,
Follow up:
After I tried to run with following patch wapbox crashed with different
backtrace.
Both patch and gdb backtrace at the end of e-mail. No ideas why the crash
happened?
Mindaugas
#0 0x08080117 in wap_event_assert (event=0x0) at wap_events.c:222
No locals.
#1
Hi, Stipe.
Stipe Tolj wrote:
Vjacheslav Chekushin schrieb:
Hi, Stipe.
Cookies wsp packing/unpacking is the secondary problem.
The primary problem for me now is Encoding-Version support.
In wsp_headers.c Version-Encodning handled in some places, but not handled in
another impotent places. This is
As library level, it should not indeed to be too hard:
a) Add class 2 transaction WTP state initiator state table (class 1
there already)
b) WSP client state table
c) Push client. There is already some code for this, but you must add
the logic
to handle incoming messages
GUI is another
sorry my english is not good :)
I want to implement the OTA_HTTP using kannel push gateway.
In the TO tcp connection procedure , the push gateway can listen on the port :
a port specified in SIR (if present) to wait the terminal's connection.
when i send a PO PUSH message to the terminal ,which
sorry my english is not good :)
I want to implement the OTA_HTTP using kannel push gateway.
In the TO tcp connection procedure , the push gateway can listen on the port
:
a port specified in SIR (if present) to wait the terminal's connection.
when i send a PO PUSH message to the terminal ,which
Paul Bagyenda schrieb:
Attached are some diffs to implement OMA-style sending of OTA settings.
Refer to OMA-WAP-ProvCont-v1_1-20021112-C (at
http://www.openmobilealliance.org/tech/docs/) for details on how this
works.
The changes include all (most) the HMAC computation stuff required for
Yes, idea of stress testing MMSC with real WAP client stack sounds
indeed sellable, but in this case MMS client is required, too. This is
however just one interface, mmsc has many of them.
Aarno
On 12.3.2004, at 12:41, Stipe Tolj wrote:
As library level, it should not indeed to be too hard:
a)
Basically most of the changes were made to ota_compiler.[ch].
Here, if the compiler detects the OMA provisioning ID in the XML
document (see ora_compiler.c:423 in the file), it passes a
flag to each of the callees that tells them to expect OMA-style
settings. I had to change some of the
So wapbox log at debug level (level 0), with configured Kannel
--with-defaults=debug would be useful.
Aarno
On 12.3.2004, at 16:20, Mindaugas Riauba wrote:
I would check first is wap_appl.c answers routed properly
when no ppg is defined.
I'm posting all those backtraces in hope that someone
11 matches
Mail list logo
