RE: Munging the '@' (at) symbol?

Troy Kelly Tue, 25 Nov 2003 15:11:10 -0800

They are MT - Log's below - sorry I didn't include - I thought it would be a common error.

Access Log

2003-11-25 22:06:53 send-SMS request added - sender:wcsms01:+61405619420 192.168.21.43 target:+61412879366 request: 'The at symbol is here @ there it was.'

Core Log

2003-11-25 22:06:53 [6] DEBUG: SMPP[vfFSG01]: Manually forced dest addr ton = 1, dest add npi = 1
2003-11-25 22:06:53 [6] DEBUG: SMPP[vfFSG01]: Sending PDU:
2003-11-25 22:06:53 [6] DEBUG: SMPP PDU 0x1010cff0 dump:
2003-11-25 22:06:53 [6] DEBUG:   type_name: submit_sm
2003-11-25 22:06:53 [6] DEBUG:   command_id: 4 = 0x00000004
2003-11-25 22:06:53 [6] DEBUG:   command_status: 0 = 0x00000000
2003-11-25 22:06:53 [6] DEBUG:   sequence_number: 11 = 0x0000000b
2003-11-25 22:06:53 [6] DEBUG:   service_type: NULL
2003-11-25 22:06:53 [6] DEBUG:   source_addr_ton: 1 = 0x00000001
2003-11-25 22:06:53 [6] DEBUG:   source_addr_npi: 1 = 0x00000001
2003-11-25 22:06:53 [6] DEBUG:   source_addr: "61405619420"
2003-11-25 22:06:53 [6] DEBUG:   dest_addr_ton: 1 = 0x00000001
2003-11-25 22:06:53 [6] DEBUG:   dest_addr_npi: 1 = 0x00000001
2003-11-25 22:06:53 [6] DEBUG:   destination_addr: "61412879366"
2003-11-25 22:06:53 [6] DEBUG:   esm_class: 131 = 0x00000083
2003-11-25 22:06:53 [6] DEBUG:   protocol_id: 0 = 0x00000000
2003-11-25 22:06:53 [6] DEBUG:   priority_flag: 0 = 0x00000000
2003-11-25 22:06:53 [6] DEBUG:   schedule_delivery_time: NULL
2003-11-25 22:06:53 [6] DEBUG:   validity_period: NULL
2003-11-25 22:06:53 [6] DEBUG:   registered_delivery: 1 = 0x00000001
2003-11-25 22:06:53 [6] DEBUG:   replace_if_present_flag: 0 = 0x00000000
2003-11-25 22:06:53 [6] DEBUG:   data_coding: 0 = 0x00000000
2003-11-25 22:06:53 [6] DEBUG:   sm_default_msg_id: 0 = 0x00000000
2003-11-25 22:06:53 [6] DEBUG:   sm_length: 37 = 0x00000025
2003-11-25 22:06:53 [6] DEBUG:   short_message:
2003-11-25 22:06:53 [6] DEBUG:    Octet string at 0x1010cc18:
2003-11-25 22:06:53 [6] DEBUG:      len: 37
2003-11-25 22:06:53 [6] DEBUG:      size: 38
2003-11-25 22:06:53 [6] DEBUG:      immutable: 0
2003-11-25 22:06:53 [6] DEBUG:      data: 54 68 65 20 61 74 20 73 79 6d 62 6f 6c 20 69 73   The at symbol is
2003-11-25 22:06:53 [6] DEBUG:      data: 20 68 65 72 65 20 00 20 74 68 65 72 65 20 69 74    here . there it
2003-11-25 22:06:53 [6] DEBUG:      data: 20 77 61 73 2e                                     was.
2003-11-25 22:06:53 [6] DEBUG:    Octet string dump ends.
2003-11-25 22:06:53 [6] DEBUG: SMPP PDU dump ends.

From: Alan McNatty
Sent: Wed 26/11/2003 07:42
To: Troy Kelly
Cc: [EMAIL PROTECTED]
Subject: Re: Munging the '@' (at) symbol?

Hi Troy,

MO or MT? Have you run with log-level = 0 - this might help you see
where the translation is happening? 

I'm guessing it's happening to MO messages. If this is the case you may
want to experiment/read up on the alt-charset smsc group config
parameter (discussed in docs). On one link I have to set mine to
ISO-8859-1 (ie: alt-charset=ISO-8859-1).

Cheers,
Alan

On Wed, 2003-11-26 at 10:41, Troy Kelly wrote:
> Hi,
>  
> Has anybody else had a problem with Kannel eating the @ symbol?
>  
> I am using the CVS build from the 17th of November.
>  
> Regards,
> Troy

RE: Munging the '@' (at) symbol?

Reply via email to