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.9&r2=1.10 http://www.kannel.3glab.org/cgi-bin/viewcvs.cgi/gateway/ChangeLog.diff?r1=1. 1950&r2=1.1951 It seems someone rolled it back :-( Angel Fradejas Mediafusion Espana, S.A. [EMAIL PROTECTED] www.mediafusion.es Tel. +34 91 252 32 00 Fax +34 91 572 27 08 -----Mensaje original----- De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]En nombre de David Holland Enviado el: viernes 21 de febrero de 2003 14:19 Para: Alexander Malysh CC: Raphael Bellec; [EMAIL PROTECTED] Asunto: Re: [PATCH] Re: RE : SMPP 3.3 trouble 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 0x00000001 to 0x7FFFFFFF > 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 zero sequence number or this problem would have been fixed by now. Dave -- :: David Holland :: Systems Manager :: 3G Lab :: +44 01223 478900 :: "Disney does mediated experiences better than anyone. If they understood what OSes are ... they could crush Microsoft in a year or two." -- NS
