Looks right. Look in your bearerbox.log for this:
2005-04-18 01:00:18 [20764] [15] DEBUG: Optional parameter tag (0x1402) 2005-04-18 01:00:18 [20764] [15] DEBUG: Optional parameter length read as 5 2005-04-18 01:00:18 [20764] [15] DEBUG: SMPP[xxxxxxxxx]: Got PDU: 2005-04-18 01:00:18 [20764] [15] DEBUG: SMPP PDU 0xae204d88 dump: 2005-04-18 01:00:18 [20764] [15] DEBUG: type_name: deliver_sm 2005-04-18 01:00:18 [20764] [15] DEBUG: command_id: 5 = 0x00000005 2005-04-18 01:00:18 [20764] [15] DEBUG: command_status: 0 = 0x00000000 2005-04-18 01:00:18 [20764] [15] DEBUG: sequence_number: 231 = 0x000000e7 2005-04-18 01:00:18 [20764] [15] DEBUG: service_type: "1060" 2005-04-18 01:00:18 [20764] [15] DEBUG: source_addr_ton: 0 = 0x00000000 2005-04-18 01:00:18 [20764] [15] DEBUG: source_addr_npi: 0 = 0x00000000 2005-04-18 01:00:18 [20764] [15] DEBUG: source_addr: "xxxxxxxxxx" 2005-04-18 01:00:18 [20764] [15] DEBUG: dest_addr_ton: 0 = 0x00000000 2005-04-18 01:00:18 [20764] [15] DEBUG: dest_addr_npi: 0 = 0x00000000 2005-04-18 01:00:18 [20764] [15] DEBUG: destination_addr: "xxxxx" 2005-04-18 01:00:18 [20764] [15] DEBUG: esm_class: 0 = 0x00000000 2005-04-18 01:00:18 [20764] [15] DEBUG: protocol_id: 0 = 0x00000000 2005-04-18 01:00:18 [20764] [15] DEBUG: priority_flag: 0 = 0x00000000 2005-04-18 01:00:18 [20764] [15] DEBUG: schedule_delivery_time: NULL 2005-04-18 01:00:18 [20764] [15] DEBUG: validity_period: NULL 2005-04-18 01:00:18 [20764] [15] DEBUG: registered_delivery: 0 = 0x00000000 2005-04-18 01:00:18 [20764] [15] DEBUG: replace_if_present_flag: 0 = 0x00000000 2005-04-18 01:00:18 [20764] [15] DEBUG: data_coding: 0 = 0x00000000 2005-04-18 01:00:18 [20764] [15] DEBUG: sm_default_msg_id: 0 = 0x00000000 2005-04-18 01:00:18 [20764] [15] DEBUG: sm_length: 3 = 0x00000003 2005-04-18 01:00:18 [20764] [15] DEBUG: short_message: "xxx" 2005-04-18 01:00:18 [20764] [15] DEBUG: mblox_operator: "31004" 2005-04-18 01:00:18 [20764] [15] DEBUG: SMPP PDU dump ends.
If you don't, then your patches didn't work. If you do, then your get-url isn't getting called, or that line-wrap you've got is messing things up.
Also, make sure the patches you got were for the right version of kannel...
Beckman
On Mon, 18 Apr 2005, Derek Barber wrote:
Hello,
I've successfully configured kannel to work with Mblox and I can send and receive SMS messages successfully.
However, I've run into a problem with receiving the operator code from the incoming SMS messages. Mblox has configured our account to work with over 5 different operators, each one with a 5 digit code. In order to successfully reply to an incoming SMS message I need to get the operator code from the incoming message and set that as the operator in the outgoing message.
I have set up an sms-service group to handle all incoming SMS messages and I am trying to get kannel to pass the operator code to the script as a GET variable. It is my understanding from the MBlox kannel patch that %o should contain the operator code. Here is the relevant portion of my kannel config:
group = sms-service keyword = default get-url = "http://abcd.pl?raw=%a&sender=%p&operator=%o&billing=% O&service_name=%n&billing_info=%B" max-messages = 3 concatenation = true
Does any know if I am missing something here, or if I am able to get the operator code in this way? Or does anyone know a better way to do it?
Many thanks, Derek
--------------------------------------------------------------------------- Peter Beckman Internet Guy [EMAIL PROTECTED] http://www.purplecow.com/ ---------------------------------------------------------------------------
