On Thu, Feb 20, 2003 at 06:55:21PM +0100, Alexander Malysh wrote:
here is trivial SMPP generic_nack fix.
generic_nack command id is 0x8000 instead of 0x
Please apply ...
Thanks, you are right. I checked the SMPP spec and I've committed that
patch to CVS.
Cheers,
Dave
--
:: David
This isn't Kannel's decision to make; this is data set by the
end user's
telephone, which may have requirements neither you nor I are
(or could
be) aware of. The analogy to a case-insensitive filesystem
namespace is
quite fitting if you think about it carefully.
I did look at
Thanks, I just applied it and I have the following log (see below).
I have 2 questions:
- Why is there 2 enquire link, is there one for the transmitter and one
for the receiver?
- The sequence number of the generic_nack seems to refer to the bind
transmitter and bind_receiver. Is it the case? If
Raphael Bellec [EMAIL PROTECTED] wrote:
2003-02-21 11:28:48 [5] DEBUG: command_id: 2147483648 = 0x8000
2003-02-21 11:28:48 [5] DEBUG: command_status: 4 = 0x0004
A generic nack with a status of 4 = Incorrect bind status for the given
command. It would appear that the SMSC hasn't
Hi,
please apply attached patch and try again...
For all: SMPP v3.4 spec allow sequence number in the range from 0x0001 to
0x7FFF
And we send 0x0 , that is wrong and SMSC do right job!
I have sent similar patch for a while but .
Am Freitag, 21. Februar 2003 13:29 schrieb Raphael
On Fri, Feb 21, 2003 at 02:06:12PM +0100, Alexander Malysh wrote:
For all: SMPP v3.4 spec allow sequence number in the range from 0x0001 to
0x7FFF
And we send 0x0 , that is wrong and SMSC do right job!
Looks plausible to me... +1
I guess most other SMSC's are lax about accepting a
I applied it and the first sequence number is '1'... but I still have
the same error.
I will contact Comverse with these informations, I keep you informed.
Thanks.
Raphaël.
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
De la part de Alexander Malysh
Envoyé :
Yep of course +1, this is something I already submitted on Sep 06 2002, and
was accepted. See
http://www.kannel.3glab.org/cgi-bin/viewcvs.cgi/gateway/gw/smsc/smsc_smpp.c.
diff?r1=1.9r2=1.10
http://www.kannel.3glab.org/cgi-bin/viewcvs.cgi/gateway/ChangeLog.diff?r1=1.
1950r2=1.1951
It seems
On Fri, Feb 21, 2003 at 04:45:53PM +0100, Angel Fradejas wrote:
It seems someone rolled it back :-(
Oops. I think Stipe took it out in revision 1.12... Stipe, was that
deliberate?
Dave
--
:: David Holland :: Systems Manager :: 3G Lab :: +44 01223 478900 ::
Hi All,
has anybody configuration kannel in order to use DLR with Siemens TC35
like SMSC?
Angelo
signature.asc
Description: PGP signature
On Freitag, Februar 21, 2003, at 07:07 Uhr, Andy Elacion, Jr. wrote:
Is it possible for kannel to accept and reply in chinese? If your can
you give me a hint on how to do it or point me to a readme/howto on how
am I going to implement it.
Thank you very much in advance,
Andy
for chinese
Citando Paul Keogh [EMAIL PROTECTED]:
This isn't Kannel's decision to make; this is data set by the
end user's
telephone, which may have requirements neither you nor I are
(or could
be) aware of. The analogy to a case-insensitive filesystem
namespace is
quite fitting if
12 matches
Mail list logo
