Re: SMPP 3.4 C-Octet String Termination

2003-02-26 Thread Andreas Fink
On Mittwoch, Februar 26, 2003, at 03:52 Uhr, Alex Judd wrote: We're working with a SMPP 3.4 server that validly (according to the 3.4 specs) terminates the C-Octet Strings it sends us with a NULL character. This currently isn't handled directly by Kannel and ends up as an extra character on the

Re: SMPP 3.4 C-Octet String Termination

2003-02-26 Thread Stipe Tolj
Alex Judd wrote: We're working with a SMPP 3.4 server that validly (according to the 3.4 specs) terminates the C-Octet Strings it sends us with a NULL character. This currently isn't handled directly by Kannel and ends up as an extra character on the message content. For example a message

Re: SMPP 3.4 C-Octet String Termination

2003-02-26 Thread Stipe Tolj
I think kannel should respect the length. So a single octstr_trim(packet,len) should do the trick I guess. if you guys consider it a bug in Kannel, then pass the information you have to the bug tracking system. Stipe [EMAIL PROTECTED]

Re: SMPP 3.4 C-Octet String Termination

2003-02-26 Thread Alexander Malysh
Hi, this is not the kannel problem! Your smsc sned wrong pdu: please look smpp v.3.4 issue 1.2 site 61... short_message field is Octet-String and not C-Octet-String. Your smsc is just buggy ;) Am Mittwoch, 26. Februar 2003 16:00 schrieb Stipe Tolj: Alex Judd wrote: We're working with a SMPP

Re: SMPP 3.4 C-Octet String Termination

2003-02-26 Thread Stipe Tolj
Alexander Malysh wrote: this is not the kannel problem! Your smsc sned wrong pdu: please look smpp v.3.4 issue 1.2 site 61... short_message field is Octet-String and not C-Octet-String. Your smsc is just buggy ;) if that's the case, Alex, could you ask which explicit SMSC it is? So we can

Re: SMPP 3.4 C-Octet String Termination

2003-02-26 Thread Alexander Malysh
it can't be C-Octet-String at all ;) Just think that '@' in GSM 03.38 is 0x00 ;) Am Mittwoch, 26. Februar 2003 16:10 schrieb Stipe Tolj: Alexander Malysh wrote: this is not the kannel problem! Your smsc sned wrong pdu: please look smpp v.3.4 issue 1.2 site 61... short_message field is

Re: SMPP 3.4 C-Octet String Termination

2003-02-26 Thread Stipe Tolj
Alexander Malysh wrote: it can't be C-Octet-String at all ;) Just think that '@' in GSM 03.38 is 0x00 ;) so it's a pat situation?! Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel:

Re: SMPP 3.4 C-Octet String Termination

2003-02-26 Thread Alex Judd
, 2003 3:16 PM Subject: Re: SMPP 3.4 C-Octet String Termination it can't be C-Octet-String at all ;) Just think that '@' in GSM 03.38 is 0x00 ;) Am Mittwoch, 26. Februar 2003 16:10 schrieb Stipe Tolj: Alexander Malysh wrote: this is not the kannel problem! Your smsc sned wrong pdu: please

Re: SMPP 3.4 C-Octet String Termination

2003-02-26 Thread Alex Judd
Ahh.. I think Alexander is right DELIVER_SM specifies that short_message is a Var 0 - 254 size octets Then specified earleir in the spec. is that Var 0 - 254 is an Octet String, not a C-Octet String Octet Strings are not Null terminated. Looks like Mobay's gateway is buggy. I'll try and

Re: SMPP 3.4 C-Octet String Termination

2003-02-26 Thread Alexander Malysh
]; [EMAIL PROTECTED] Sent: Wednesday, February 26, 2003 3:16 PM Subject: Re: SMPP 3.4 C-Octet String Termination it can't be C-Octet-String at all ;) Just think that '@' in GSM 03.38 is 0x00 ;) Am Mittwoch, 26. Februar 2003 16:10 schrieb Stipe Tolj: Alexander Malysh wrote

Re: SMPP 3.4 C-Octet String Termination

2003-02-26 Thread Alan McNatty
Alex, Have experienced SMSC that did this. In our case it was configurable on SMSC - eventually it was turned off. It may be worth seeing if you can do the same (given the SMSC's adding it). Cheers, Alan On Thu, 2003-02-27 at 03:52, Alex Judd wrote: We're working with a SMPP 3.4 server that