Hi!

First a question...

I got a carrier, where messages are billed by MO, and I need to bill some by MT
They told me to use the SMPP billing parameter, which I guess is "binfo", right?

They sent me an e-mail with this:

Meaning:

Value:

Parameter tag

0x060B

Length

0x0007

Billing format tag

0x80



is it ok, is it the binfo parameter?

Then, they asked me first to try send a message putting "001100010001" as value for this parameter, but when I do so, the system_type gets changed to this value, thus giving an error  :(


This is what I'm doing to send it:

http://xxx.xxx.xxx.xxx:XXX/cgi-bin/sendsms?user=myUser&pass=myPass&smsc=mySMSC&from=1010&to=1234567890&text=test&binfo=001100010001

And this shows up on the logs:

2006-11-02 13:37:50 [22983] [12] DEBUG: SMPP[mySMSC]: Got PDU:
2006-11-02 13:37:50 [22983] [12] DEBUG: SMPP PDU 0x81d7450 dump:
2006-11-02 13:37:50 [22983] [12] DEBUG:   type_name: enquire_link_resp
2006-11-02 13:37:50 [22983] [12] DEBUG:   command_id: 2147483669 = 0x80000015
2006-11-02 13:37:50 [22983] [12] DEBUG:   command_status: 0 = 0x00000000
2006-11-02 13:37:50 [22983] [12] DEBUG:   sequence_number: 626 = 0x00000272
2006-11-02 13:37:50 [22983] [12] DEBUG: SMPP PDU dump ends.
2006-11-02 13:38:03 [22983] [12] DEBUG: SMPP[mySMSC]: Manually forced source addr ton = 1, source add npi = 1
2006-11-02 13:38:03 [22983] [12] DEBUG: SMPP[mySMSC]: Manually forced dest addr ton = 1, dest add npi = 1
2006-11-02 13:38:03 [22983] [12] DEBUG: SMPP[mySMSC]: Sending PDU:
2006-11-02 13:38:03 [22983] [12] DEBUG: SMPP PDU 0x81d7450 dump:
2006-11-02 13:38:03 [22983] [12] DEBUG:   type_name: submit_sm
2006-11-02 13:38:03 [22983] [12] DEBUG:   command_id: 4 = 0x00000004
2006-11-02 13:38:03 [22983] [12] DEBUG:   command_status: 0 = 0x00000000
2006-11-02 13:38:03 [22983] [12] DEBUG:   sequence_number: 627 = 0x00000273
2006-11-02 13:38:03 [22983] [12] DEBUG:   service_type: "001100010001"
2006-11-02 13:38:03 [22983] [12] DEBUG:   source_addr_ton: 1 = 0x00000001
2006-11-02 13:38:03 [22983] [12] DEBUG:   source_addr_npi: 1 = 0x00000001
2006-11-02 13:38:03 [22983] [12] DEBUG:   source_addr: "1010"
2006-11-02 13:38:03 [22983] [12] DEBUG:   dest_addr_ton: 1 = 0x00000001
2006-11-02 13:38:03 [22983] [12] DEBUG:   dest_addr_npi: 1 = 0x00000001
2006-11-02 13:38:03 [22983] [12] DEBUG:   destination_addr: "1234567890"
2006-11-02 13:38:03 [22983] [12] DEBUG:   esm_class: 3 = 0x00000003
2006-11-02 13:38:03 [22983] [12] DEBUG:   protocol_id: 0 = 0x00000000
2006-11-02 13:38:03 [22983] [12] DEBUG:   priority_flag: 0 = 0x00000000
2006-11-02 13:38:03 [22983] [12] DEBUG:   schedule_delivery_time: NULL
2006-11-02 13:38:03 [22983] [12] DEBUG:   validity_period: NULL
2006-11-02 13:38:03 [22983] [12] DEBUG:   registered_delivery: 0 = 0x00000000
2006-11-02 13:38:03 [22983] [12] DEBUG:   replace_if_present_flag: 0 = 0x00000000
2006-11-02 13:38:03 [22983] [12] DEBUG:   data_coding: 0 = 0x00000000
2006-11-02 13:38:03 [22983] [12] DEBUG:   sm_default_msg_id: 0 = 0x00000000
2006-11-02 13:38:03 [22983] [12] DEBUG:   sm_length: 17 = 0x00000011
2006-11-02 13:38:03 [22983] [12] DEBUG:   short_message: "test"
2006-11-02 13:38:03 [22983] [12] DEBUG: SMPP PDU dump ends.
2006-11-02 13:38:03 [22983] [12] WARNING: SMPP: PDU element <service_type> too long (length is 12, should be 5)


Why is this happening??  :(
I'm using Kannel 1.4.0

I got a 1.4.1 running also, but can not change this connection right now to test with 1.4.1

Thanks in advance,

Juan

Reply via email to