Re: Message ID issues

Bill Brigden wrote:

> Hi,
>  
> I've noticed that one of the providers in an installation using kannel is
> giving back big message ID's - see Bill error 2 below.. The provider is
> using SMPP and using the msg id type 0x03, so hex is given in both the
> submit_sm_resp and the deliver_sm. However I'm seeing problems where the
> conversion of hex to string (with a bit of long integer mid way)... Below
> you can see output from the logs, Ive put in 2 custom errors - bill error 1
> is the tmp var (used in the dlr_add in the handle_pdu in the smpp smsc,
> after conversion), and bill error 2 is the msg structure with the message
> ie: pdu->u.submit_sm_resp.message_id, before conversion.
>  
> Has anyone ever seen this before?
> 
> 2005-11-23 14:08:11 [13972] [39] DEBUG: SMPP[*****-fixed-primary]: BILL
> ERROR1 2147483647
> 2005-11-23 14:08:11 [13972] [39] DEBUG: SMPP[*****-fixed-primary]: BILL
> ERROR2 C2F75296041985B9

ok, sofar these are "added" debuging lines, right?

can you please provide more debug log-level from the SMPP communication to review?

Stipe

mailto:stolj_{at}_wapme-group.de
-------------------------------------------------------------------
Wapme Systems AG

Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany

phone: +49.211.74845.0
fax: +49.211.74845.299

mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
-------------------------------------------------------------------