Re: callback_num

I solve the problem.....

the method is right, but i need to change 3030 with the callback_num 
specs by the smpp.

If anyone want this option, fell free to contact me

Thanks

Rafael Ugolini wrote:

> Sorry about the idle time.......
>
> I added in line 742,
>
> 742    pdu->u.submit_sm.callback_num = octstr_create("3030");
>
> in the smsc_smpp.c this
>
> and here is the DEBUG level of the PDU
>
> 2005-04-22 16:18:22 [1244] [7] DEBUG:   type_name: submit_sm
> 2005-04-22 16:18:22 [1244] [7] DEBUG:   command_id: 4 = 0x00000004
> 2005-04-22 16:18:22 [1244] [7] DEBUG:   command_status: 0 = 0x00000000
> 2005-04-22 16:18:22 [1244] [7] DEBUG:   sequence_number: 2 = 0x00000002
> 2005-04-22 16:18:22 [1244] [7] DEBUG:   service_type: NULL
> 2005-04-22 16:18:22 [1244] [7] DEBUG:   source_addr_ton: 2 = 0x00000002
> 2005-04-22 16:18:22 [1244] [7] DEBUG:   source_addr_npi: 1 = 0x00000001
> 2005-04-22 16:18:22 [1244] [7] DEBUG:   source_addr: "3032"
> 2005-04-22 16:18:22 [1244] [7] DEBUG:   dest_addr_ton: 2 = 0x00000002
> 2005-04-22 16:18:22 [1244] [7] DEBUG:   dest_addr_npi: 1 = 0x00000001
> 2005-04-22 16:18:22 [1244] [7] DEBUG:   destination_addr: "1197653221"
> 2005-04-22 16:18:22 [1244] [7] DEBUG:   esm_class: 3 = 0x00000003
> 2005-04-22 16:18:22 [1244] [7] DEBUG:   protocol_id: 0 = 0x00000000
> 2005-04-22 16:18:22 [1244] [7] DEBUG:   priority_flag: 0 = 0x00000000
> 2005-04-22 16:18:22 [1244] [7] DEBUG:   schedule_delivery_time: NULL
> 2005-04-22 16:18:22 [1244] [7] DEBUG:   validity_period: NULL
> 2005-04-22 16:18:22 [1244] [7] DEBUG:   registered_delivery: 0 = 
> 0x00000000
> 2005-04-22 16:18:22 [1244] [7] DEBUG:   replace_if_present_flag: 0 = 
> 0x00000000
> 2005-04-22 16:18:22 [1244] [7] DEBUG:   data_coding: 0 = 0x00000000
> 2005-04-22 16:18:22 [1244] [7] DEBUG:   sm_default_msg_id: 0 = 0x00000000
> 2005-04-22 16:18:22 [1244] [7] DEBUG:   sm_length: 2 = 0x00000002
> 2005-04-22 16:18:22 [1244] [7] DEBUG:   short_message: "Oi"
> 2005-04-22 16:18:22 [1244] [7] DEBUG:   callback_num: "3030"
> 2005-04-22 16:18:22 [1244] [7] DEBUG: SMPP PDU dump ends.
> 2005-04-22 16:18:22 [1244] [7] DEBUG: SMPP[VIVO_TESTE]: Got PDU:
> 2005-04-22 16:18:22 [1244] [7] DEBUG: SMPP PDU 0x819da60 dump:
> 2005-04-22 16:18:22 [1244] [7] DEBUG:   type_name: submit_sm_resp
> 2005-04-22 16:18:22 [1244] [7] DEBUG:   command_id: 2147483652 = 
> 0x80000004
> 2005-04-22 16:18:22 [1244] [7] DEBUG:   command_status: 0 = 0x00000000
> 2005-04-22 16:18:22 [1244] [7] DEBUG:   sequence_number: 2 = 0x00000002
> 2005-04-22 16:18:22 [1244] [7] DEBUG:   message_id: "077739AC"
> 2005-04-22 16:18:22 [1244] [7] DEBUG: SMPP PDU dump ends.
>
>
> Seens like okay, but its not working, i belive the error is when SMSC 
> opens the PDU.
> Dunno....
>
> Thanks
>
>
> Stipe Tolj wrote:
>
>> Rafael Ugolini wrote:
>>
>>> i tried this too, but no sucess
>>>
>>> and i even tried
>>>
>>> line 354 pdu->u.deliver_sm.callback_num = octstr_create("3030");
>>>
>>> Any help will be very cool, im without clues.
>>
>>
>>
>> can you please provide us a debug-level bearerbox.log to review the 
>> SMPP PDUs between Kannel and the SMPP server?!
>>
>> Stipe
>>
>> mailto:stolj_{at}_wapme.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/
>> -------------------------------------------------------------------
>
>
>
>