Hi Stipe and Alex Apologies, I should have really looked through the message in more detail :-)
Looking at the SMPP 3.4 docs, a ton value of 0x01 is "international". Should it therefore be 0x101 (Alphanumeric) if there's a "+" prefix? I've spoken to the provider, and I seem to be the only customer out of around 500 SMPP connections that's noticed this :-) I've provided them with my Kannel debug logs and told them to go fix it! Thanks for the patch Alex, I'll give it a try in a minute. Alex ----- Original Message ----- From: "Stipe Tolj" <[EMAIL PROTECTED]> To: "Alexander Malysh" <[EMAIL PROTECTED]> Cc: "Alex Kinch" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Thursday, October 16, 2003 11:32 PM Subject: Re: SMPP broken in cvs-20031016? > Alexander Malysh wrote: > > > > have you notice a command status in deliver_sm_resp? it's 0x0a == Invalid > > source address. And see source address in deliver_sm: '+' in front which is > > not allowed. > > > > So you should try to contact telco and tell them that smsc is broken. > > And second: please try attached patch that just implements a workaround for > > this mess ;) > > yep, Alex is right here. Haven't checked the PDU that pedantically as > he did ;) > > The source_addr_ton specifies 0x01 which means no prefixing at all. > And the + prefix is hance *not* protocoll conform. > > Alex, to put this vendor on a "black list", which one is it? > > Stipe > > [EMAIL PROTECTED] > ------------------------------------------------------------------- > Wapme Systems AG > > Vogelsanger Weg 80 > 40470 D�sseldorf > > Tel: +49-211-74845-0 > Fax: +49-211-74845-299 > > E-Mail: [EMAIL PROTECTED] > Internet: http://www.wapme-systems.de > ------------------------------------------------------------------- > wapme.net - wherever you are > > >
