Jarrod Hermer wrote:
While running Kannel 1.3.1 in Cygwin the following error message was
printed to screen by the bearerbox:
7 [unknown (0x74C)] bearerbox 1960 pthread_cond::Signal: Released too
many threads - 1 now 1 originally
Any ideas what might have caused this and what the
On Friday 04 April 2003 11:56, Stipe Tolj wrote:
Alexander Malysh wrote:
Hi Stipe, All,
On Friday 04 April 2003 11:32, Stipe Tolj wrote:
Nope,
I'm getting message:
INFO: NOTE: sender and receiver same number 520, ignoring!
it's comming from smsbox...
and this is a
Citando Stipe Tolj [EMAIL PROTECTED]:
PS: This reminds me that we could mo-recode it to utf-8 instead of iso,
with a
parameter ;)
Kannels internal charset is ISO (latin1).
mo-recode-charset = utf-8 ? ;)
it's a simple patch. Just carry this string to mo-recode function and give it to
Hi list,
I have patched gw/smsc/smsc_http.c to fix a couple of issues,
including:
* bearerbox crash if smsc is shutdown and /status is called
* don't 'fail' messages if the connection could not be established to
HTTP SMSC, instead re-queue and respect 'reconnect-delay' for a
sleeping period.
On 2003-04-04 at 10:27:14 [+0200], you wrote:
the DLR storage is completely internal to Kannel and is not supposed from
the outside.
it is used to track internally messages kannel has sent to SMSC's. The
DLR url is a callback mechanism to tell your application the status of
the message.
Hi,
How phone to know the application type? So SMSC should transfer some smpp
headers to phone and the header value is written by Kannel. Now I think the
header is service_type and its value is WAP. But kannel sets this value
as NULL.
According to what you mean, phone will know the message is
Guanghua Hou wrote:
How phone to know the application type? So SMSC should transfer some smpp
headers to phone and the header value is written by Kannel. Now I think the
header is service_type and its value is WAP. But kannel sets this value
as NULL.
According to what you mean, phone will
There is two way to define the application type (push case)
a) the port, client port specified for push
b) X-WAP-Application-Id header, telling is the application wlm.ua or
mms.ua
In pull, it is the phone that starts the things, so it is more like how
server knows
that this is wap (phone knows
Hi,
According to what you said, 'service_type' setting is optional.If it's null,
phone shall also recogonize WAP application.
Best Regards,
Guanghua Hou
Guanghua Hou wrote:
How phone to know the application type? So SMSC should transfer some
smpp
headers to phone and the header value is
According to what you said, 'service_type' setting is optional.If it's null,
phone shall also recogonize WAP application.
yes, it will recognize either via the UDH header port or the token
that has been encoded within the UDH header while using PPG's push
capabilities and setthing the
On Freitag, April 4, 2003, at 11:56 Uhr, Stipe Tolj wrote:
Alexander Malysh wrote:
Hi Stipe, All,
On Friday 04 April 2003 11:32, Stipe Tolj wrote:
Nope,
I'm getting message:
INFO: NOTE: sender and receiver same number 520>, ignoring!
it's comming from smsbox...
and this is a bug (imho).
On Freitag, April 4, 2003, at 12:10 Uhr, Guanghua Hou wrote:
Hi,
According to what you said, 'service_type' setting is optional.If it's null,
phone shall also recogonize WAP application.
the phone wont get this information anyway. Application Type is a SMPP specific tag which doesn't go into
12 matches
Mail list logo
