re
am I stupid or what ...
sending wap bookmark to nokia phones - all is ok .. sending to ericsson
R520m or ericsson T68i - the message reaches the phone but no any action
follows. I suppose that ericsson phones should ask if one would like to save
the bookmark, as nokia do ..
the message is
re
according to OTA settings specification 7.0 from ericsson and nokia
dest port must be 4 (C3F4).
hmz .. c3f4 is 50164 .. shouldn't it be c34f ?
k
re
which doesn't work (the smsc returns an error). It would be
better if kannel would reply to the message with the same ton and
npi (both source and destination) as in the message received.
Curently I solve this problem by modifying smsc_smpp.c, and
changind default ton and npi values.
re
I have to disagree with you.
In GSM character set is coded as 0x00.
If your SMSC doesnt want to have encoded as 0x00 but wants to have
ISO8859-1 as input, this is something which should be taken care of in the
SMSC driver or on the SMSC itself. patching charset.c would make all SMSC
Patching charset.c is not good.
But if it affected other driver (not only SMPP),
Anybody have a clue where the right way to go? (To each driver?)
I think, we must go back to previous implementation of SMPP
driver like in 1.0.2 / 1.0.3, where smsc_smpp.c has its own
character mapping.
re
I'm going to attempt to write some sort of hack to make Kannel store
incoming SMS messages from any given SMSC into a database for the purposes
of logging and better analysis. So far I've thought that this is the best
way forward:
that't the job of application logic, not gateway. can
I wonder whether anyone out there has had this
problem, and what solution they've discovered:
When a user sends the '' character in an sms, on some
SMSCs, kannel receives '', on other it receives NULL
(as per GSM character spec). Now in the former case,
gwlib/charset.c will cause convert
I have two SMPP connections to a network. One is
primary the other a backup. I want all my messages to
go through the first, unless it is dead. By default
kannel does a sort of load balance, which is not
good... Any ideas?
enable routing to both of them, use preferred-routing to the
enable routing to both of them, use preferred-routing to the primary.
yep, that may be an option. Does that really route everything primarly
to A?
should .. as I remeber from the code - preferred routes have preference over
normal ones ..
btw, please don't send additional copy to my
Currently bearerbox and wapbox process run in super user mode. I
tried to run the bearerbox and wapbox process in user mode. It's
giving a ERROR:log file don't have permission. were are this
permission set up. please help us.
if you run them as root - the log files are created owned by root
re
If the receiver socket snaps, the receiver io_thread will go into a
reconnect anyway. However there is no need for it to set the (shared)
status variable to SMSCCONN_RECONNECTING, especially since it is not
itself privileged enough to later restore the status to SMSCCONN_ACTIVE.
well ..
I'd like to introduce a 'unified-prefix' directive on a smsc basis
that behaves the same way as the global one defines in the core group.
have implemented it a long time ago .. was a part of my big patch .. also,
actually I implemented two of them - one for incoming and another one for
re
does anyone know what CIMD parameter 69 exactly stands for? I seem to
receive it constantly from one of our operators. the parameter value seems
to include their smsc number. In the CIMD doc I have, the last is 68 .. any
pointers to some better doc?
regards,
kaido
re
I realized that every time Kannel successfuly notify my Application that
messages hadn't been delivery to SMSC (escape %d = 16) it write a new line
in store-file, so every notification of a message not sent increases the
store-file.
The actual problem is when I restart Kannel. When it
re
daily snapshot (tried only tarball) on http://www.kannel.org/ is not up to
date with cvs ..
k
forget about Java if you need a high-performance SMS gateway and take
Kannel, contribute to development if it does not fit your needs in a
specific way :)
that you say .. I remember posting 2 obvious bugfixes .. none of them appear
in cvs ..
k
[dholland@geodude download]$ cat snapshot-timestamp.txt
Snapshot build starts: Thu Aug 1 06:00:00 BST 2002
Snapshot build ends: Thu Aug 1 06:04:22 BST 2002
What do you think is missing?
uups .. my mistake .. nothing :) I had an older snapshot lying around in the
directory I downloaded the
I think I would prefer to have these combined into a single function.
gw_free now maps onto the gw_native_free or gw_check_free with macros.
We could make the macros as such that they pass the pointer to the
address space containing the pointer and make the pointer even NULL.
What do
If you haven't fixed this the Invalid source address means you
need to make sure your from= parameter is correct. If your source TON was
wrong you would get a 0x0048 or if your source NPI was wrong you would
get a
0x0049
it's not so .. TON and NPI can be 'correct' by itself, but
The principle might sound great but the practical thing is much worse.
For UK for example the prefix list is about 100 prefixes. And
furthermore you have number portability so you wont know which prefix
really belongs where because the number might now belong to another
carrier.
100
Then there should be some kind of (HTTP?) frontend to SS7 that
allows just this kind of queries. I don't think that this would
violate privacy because it only provides the same kind of
information one could previously get from looking at the MSISDN.
that would be ok. another way - I believe
Generaly speaking, I don't think you should use socket programming in
PHP for HTTP connections - PHP has a good HTTP infrastructure using the
fopen() and file() function calls. these calls will allow you to easily
that's not so easy. afaik php fopen() accepts only 200 as a valid response
re
does anybody use any smsc's which use old format smsc modules (CIMD, CIMD2,
EMI, EMI_IP, SEMA, OIS, AT)? I use CIMD2. any volunteers to convert at least
CIMD2 to new implementation? :)
kaido
Then it kinda
starts becoming unmanageable (have to walk all the smsc
connection lines to add denied/accepted logic). Soon I might turn for
custom alternative
configuration and generating kannel conf out of that using a perl script.
heh .. that's exactly the same thing I was thinking about
2002-07-05 20:51:43 [0] INFO: MAIN: Start-up done, entering mainloop
2002-07-05 20:51:43 [8] DEBUG: sms_router: time to sleep
2002-07-05 20:51:43 [8] DEBUG: sms_router: list_len = 0
2002-07-05 20:51:43 [6] PANIC: gw/smpp_pdu.def:60: smpp_pdu_pack:
Assertion
`octstr_len(p-password) 9'
contiue? why?
why? to allow other connections to come up and run ..
the password is logically longer than 8 octects, but the
SMPP spec does not accept it to put it in the appropriate PDUs. So
what should you do then? Cut the Password to 8 chars long and send the
login sequence anyway?
re
smsc_emi2.c
function int smsc_emi2_create(SMSCConn *conn, CfgGroup *cfg)
will set privdata to NULL at line 1610 (may slightly vary - have made some
changes) before goto error:, but:
error:
error(0, EMI2[%s]: Failed to create emi2 smsc connection,
octstr_get_cstr(privdata-name));
uses
re
smsc_emi2.c
function int smsc_emi2_create(SMSCConn *conn, CfgGroup *cfg)
will set privdata to NULL at line 1610 (may slightly vary - have made some
changes) before goto error:, but:
error:
error(0, EMI2[%s]: Failed to create emi2 smsc connection,
re
I'm still using kannel 1.1.4 with my own patches and modifications. However,
a number of problems seems to bew solved now with 1.1.6 so I'm thinking
about upgrade.
I've monitored the list sometimes, but not constantly, so if the question is
answered in the list - please forgive me. but, the
I noticed that the number of incoming messages (in case of EMI2) displayed
in status page is doubled up.
I use a kannel version derived from 1.1.4.
well .. the handle_operation() in gw/smsc_emi2.c updates the counter at two
places just before calling bb_smscconn_receive(). as
re
I noticed that the number of incoming messages (in case of EMI2) displayed
in status page is doubled up.
I use a kannel version derived from 1.1.4.
does anybody remember this bug being fixed or I'll go and find it out
myself?
regards,
kaido
31 matches
Mail list logo