SMPP privacy_indicator

[Konstantin Vayner-2]

Hi list,

One of the smscs (smpp) we are connected to sends a privacy_indicator field in deliver_sm.
And the operator in question wants our application to behave differently depending on the indicator value.
I can see the privacy_indicator in pdu dump in the log, but how can i get this info into my sms-service ?
Looked through the manual and i cant find any option to do so... Either i am missing something or kannel doesnt disclose that info?
It would be good to be able to get all parts (fields) of the message pdu that kannel extracted in general

Also,  i'd like to be able push this privacy indicator back when sending submit_sm. Is this possible?

Regards,
  Konstantin

[Alejandro Guerrieri]

Maybe it's a TLV? Can you paste your pdu dump?

Regards,

Alejandro

On Tue, Nov 10, 2009 at 5:15 PM, Konstantin Vayner <poncha@...> wrote:

Hi list,

One of the smscs (smpp) we are connected to sends a privacy_indicator field in deliver_sm.
And the operator in question wants our application to behave differently depending on the indicator value.
I can see the privacy_indicator in pdu dump in the log, but how can i get this info into my sms-service ?
Looked through the manual and i cant find any option to do so... Either i am missing something or kannel doesnt disclose that info?
It would be good to be able to get all parts (fields) of the message pdu that kannel extracted in general

Also,  i'd like to be able push this privacy indicator back when sending submit_sm. Is this possible?

Regards,
  Konstantin

[Konstantin Vayner-2]

yes, i think this might be tlv
attached you can see dump of two messages, one without privacy_indicator and one with
the second one had "Optional parameter tag (0x0201)" line in debug before pdu dump

On Tue, Nov 10, 2009 at 6:20 PM, Alejandro Guerrieri <alejandro.guerrieri@...> wrote:

Maybe it's a TLV? Can you paste your pdu dump?

Regards,

Alejandro

On Tue, Nov 10, 2009 at 5:15 PM, Konstantin Vayner <poncha@...> wrote:

Hi list,

One of the smscs (smpp) we are connected to sends a privacy_indicator field in deliver_sm.
And the operator in question wants our application to behave differently depending on the indicator value.
I can see the privacy_indicator in pdu dump in the log, but how can i get this info into my sms-service ?
Looked through the manual and i cant find any option to do so... Either i am missing something or kannel doesnt disclose that info?
It would be good to be able to get all parts (fields) of the message pdu that kannel extracted in general

Also,  i'd like to be able push this privacy indicator back when sending submit_sm. Is this possible?

Regards,
  Konstantin

2009-11-10 18:17:54 [6013] [7] DEBUG: SMPP[smsc_mo]: Got PDU:
2009-11-10 18:17:54 [6013] [7] DEBUG: SMPP PDU 0x7f0180d9e4d0 dump:
2009-11-10 18:17:54 [6013] [7] DEBUG:   type_name: deliver_sm
2009-11-10 18:17:54 [6013] [7] DEBUG:   command_id: 5 = 0x00000005
2009-11-10 18:17:54 [6013] [7] DEBUG:   command_status: 0 = 0x00000000
2009-11-10 18:17:54 [6013] [7] DEBUG:   sequence_number: 1339407 = 0x0014700f
2009-11-10 18:17:54 [6013] [7] DEBUG:   service_type: NULL
2009-11-10 18:17:54 [6013] [7] DEBUG:   source_addr_ton: 1 = 0x00000001
2009-11-10 18:17:54 [6013] [7] DEBUG:   source_addr_npi: 1 = 0x00000001
2009-11-10 18:17:54 [6013] [7] DEBUG:   source_addr: "048654321"
2009-11-10 18:17:54 [6013] [7] DEBUG:   dest_addr_ton: 1 = 0x00000001
2009-11-10 18:17:54 [6013] [7] DEBUG:   dest_addr_npi: 1 = 0x00000001
2009-11-10 18:17:54 [6013] [7] DEBUG:   destination_addr: "0523213231"
2009-11-10 18:17:54 [6013] [7] DEBUG:   esm_class: 0 = 0x00000000
2009-11-10 18:17:54 [6013] [7] DEBUG:   protocol_id: 0 = 0x00000000
2009-11-10 18:17:54 [6013] [7] DEBUG:   priority_flag: 0 = 0x00000000
2009-11-10 18:17:54 [6013] [7] DEBUG:   schedule_delivery_time: NULL
2009-11-10 18:17:54 [6013] [7] DEBUG:   validity_period: NULL
2009-11-10 18:17:54 [6013] [7] DEBUG:   registered_delivery: 0 = 0x00000000
2009-11-10 18:17:54 [6013] [7] DEBUG:   replace_if_present_flag: 0 = 0x00000000
2009-11-10 18:17:54 [6013] [7] DEBUG:   data_coding: 8 = 0x00000008
2009-11-10 18:17:54 [6013] [7] DEBUG:   sm_default_msg_id: 0 = 0x00000000
2009-11-10 18:17:54 [6013] [7] DEBUG:   sm_length: 84 = 0x00000054
2009-11-10 18:17:54 [6013] [7] DEBUG:   short_message:
2009-11-10 18:17:54 [6013] [7] DEBUG:    Octet string at 0x7f0180d6b8b0:
2009-11-10 18:17:54 [6013] [7] DEBUG:      len:  84
2009-11-10 18:17:54 [6013] [7] DEBUG:      size: 85
2009-11-10 18:17:54 [6013] [7] DEBUG:      immutable: 0
2009-11-10 18:17:54 [6013] [7] DEBUG:      data: 05 d0 05 d6 05 e2 05 e7 05 d4 00 20 05 de 05 e9   ........... ....
2009-11-10 18:17:54 [6013] [7] DEBUG:      data: 05 e8 05 d3 00 20 00 20 00 20 00 20 00 20 00 20   ..... . . . . .
2009-11-10 18:17:54 [6013] [7] DEBUG:      data: 00 0d 05 d4 05 e4 05 e2 05 dc 05 d4 00 20 00 2d   ............. .-
2009-11-10 18:17:54 [6013] [7] DEBUG:      data: 00 20 05 e1 05 e9 05 d4 00 20 00 20 00 20 00 20   . ....... . . .
2009-11-10 18:17:54 [6013] [7] DEBUG:      data: 00 20 00 0d 00 31 00 38 00 3a 00 30 00 38 00 0d   . ...1.8.:.0.8..
2009-11-10 18:17:54 [6013] [7] DEBUG:      data: 00 31 00 30                                       .1.0
2009-11-10 18:17:54 [6013] [7] DEBUG:    Octet string dump ends.
2009-11-10 18:17:54 [6013] [7] DEBUG: SMPP PDU dump ends.
2009-11-10 18:17:54 [6013] [7] DEBUG: SMPP[smsc_mo]: Sending PDU:
2009-11-10 18:17:54 [6013] [7] DEBUG: SMPP PDU 0x7f0180d8fa10 dump:
2009-11-10 18:17:54 [6013] [7] DEBUG:   type_name: deliver_sm_resp
2009-11-10 18:17:54 [6013] [7] DEBUG:   command_id: 2147483653 = 0x80000005
2009-11-10 18:17:54 [6013] [7] DEBUG:   command_status: 0 = 0x00000000
2009-11-10 18:17:54 [6013] [7] DEBUG:   sequence_number: 1339407 = 0x0014700f
2009-11-10 18:17:54 [6013] [7] DEBUG:   message_id: NULL
2009-11-10 18:17:54 [6013] [7] DEBUG: SMPP PDU dump ends.


2009-11-10 18:17:54 [6013] [7] DEBUG: Optional parameter tag (0x0201)
2009-11-10 18:17:54 [6013] [7] DEBUG: Optional parameter length read as 1
2009-11-10 18:17:54 [6013] [7] DEBUG: SMPP[smsc_mo]: Got PDU:
2009-11-10 18:17:54 [6013] [7] DEBUG: SMPP PDU 0x7f0180d9e4d0 dump:
2009-11-10 18:17:54 [6013] [7] DEBUG:   type_name: deliver_sm
2009-11-10 18:17:54 [6013] [7] DEBUG:   command_id: 5 = 0x00000005
2009-11-10 18:17:54 [6013] [7] DEBUG:   command_status: 0 = 0x00000000
2009-11-10 18:17:54 [6013] [7] DEBUG:   sequence_number: 1339408 = 0x00147010
2009-11-10 18:17:54 [6013] [7] DEBUG:   service_type: NULL
2009-11-10 18:17:54 [6013] [7] DEBUG:   source_addr_ton: 1 = 0x00000001
2009-11-10 18:17:54 [6013] [7] DEBUG:   source_addr_npi: 1 = 0x00000001
2009-11-10 18:17:54 [6013] [7] DEBUG:   source_addr: "048765432"
2009-11-10 18:17:54 [6013] [7] DEBUG:   dest_addr_ton: 1 = 0x00000001
2009-11-10 18:17:54 [6013] [7] DEBUG:   dest_addr_npi: 1 = 0x00000001
2009-11-10 18:17:54 [6013] [7] DEBUG:   destination_addr: "0521234567"
2009-11-10 18:17:54 [6013] [7] DEBUG:   esm_class: 0 = 0x00000000
2009-11-10 18:17:54 [6013] [7] DEBUG:   protocol_id: 0 = 0x00000000
2009-11-10 18:17:54 [6013] [7] DEBUG:   priority_flag: 0 = 0x00000000
2009-11-10 18:17:54 [6013] [7] DEBUG:   schedule_delivery_time: NULL
2009-11-10 18:17:54 [6013] [7] DEBUG:   validity_period: NULL
2009-11-10 18:17:54 [6013] [7] DEBUG:   registered_delivery: 0 = 0x00000000
2009-11-10 18:17:54 [6013] [7] DEBUG:   replace_if_present_flag: 0 = 0x00000000
2009-11-10 18:17:54 [6013] [7] DEBUG:   data_coding: 5 = 0x00000005
2009-11-10 18:17:54 [6013] [7] DEBUG:   sm_default_msg_id: 0 = 0x00000000
2009-11-10 18:17:54 [6013] [7] DEBUG:   sm_length: 30 = 0x0000001e
2009-11-10 18:17:54 [6013] [7] DEBUG:   short_message:
2009-11-10 18:17:54 [6013] [7] DEBUG:    Octet string at 0x7f0180d947f0:
2009-11-10 18:17:54 [6013] [7] DEBUG:      len:  30
2009-11-10 18:17:54 [6013] [7] DEBUG:      size: 31
2009-11-10 18:17:54 [6013] [7] DEBUG:      immutable: 0
2009-11-10 18:17:54 [6013] [7] DEBUG:      data: e0 f0 e0 20 f0 e8 ec e9 20 f8 e5 e3 e9 20 e3 e7   ... .... .... ..
2009-11-10 18:17:54 [6013] [7] DEBUG:      data: e5 f4 20 e3 e9 e2 e9 20 ec f2 e9 f0 e3 f7         .. .... ......
2009-11-10 18:17:54 [6013] [7] DEBUG:    Octet string dump ends.
2009-11-10 18:17:54 [6013] [7] DEBUG:   privacy_indicator: 3 = 0x00000003
2009-11-10 18:17:54 [6013] [7] DEBUG: SMPP PDU dump ends.
2009-11-10 18:17:54 [6013] [7] DEBUG: SMPP[smsc_mo]: Sending PDU:
2009-11-10 18:17:54 [6013] [7] DEBUG: SMPP PDU 0x7f0180d8fa10 dump:
2009-11-10 18:17:54 [6013] [7] DEBUG:   type_name: deliver_sm_resp
2009-11-10 18:17:54 [6013] [7] DEBUG:   command_id: 2147483653 = 0x80000005
2009-11-10 18:17:54 [6013] [7] DEBUG:   command_status: 0 = 0x00000000
2009-11-10 18:17:54 [6013] [7] DEBUG:   sequence_number: 1339408 = 0x00147010
2009-11-10 18:17:54 [6013] [7] DEBUG:   message_id: NULL
2009-11-10 18:17:54 [6013] [7] DEBUG: SMPP PDU dump ends.

[Alejandro Guerrieri]

Then you should be able to get it by using the meta-data functionality then.

You need a more or less recent CVS, though, 1.4.3 and earlier won't cut it.

Regards,

Alejandro

On Tue, Nov 10, 2009 at 5:40 PM, Konstantin Vayner <poncha@...> wrote:

yes, i think this might be tlv
attached you can see dump of two messages, one without privacy_indicator and one with
the second one had "Optional parameter tag (0x0201)" line in debug before pdu dump

On Tue, Nov 10, 2009 at 6:20 PM, Alejandro Guerrieri <alejandro.guerrieri@...> wrote:

Maybe it's a TLV? Can you paste your pdu dump?

Regards,

Alejandro

On Tue, Nov 10, 2009 at 5:15 PM, Konstantin Vayner <poncha@...> wrote:

Hi list,

One of the smscs (smpp) we are connected to sends a privacy_indicator field in deliver_sm.
And the operator in question wants our application to behave differently depending on the indicator value.
I can see the privacy_indicator in pdu dump in the log, but how can i get this info into my sms-service ?
Looked through the manual and i cant find any option to do so... Either i am missing something or kannel doesnt disclose that info?
It would be good to be able to get all parts (fields) of the message pdu that kannel extracted in general

Also,  i'd like to be able push this privacy indicator back when sending submit_sm. Is this possible?

Regards,
  Konstantin

[Alejandro Guerrieri]

CVS is as stable as 1.4.3 (or more, many bugs were fixed since 1.4.3), you can safely use it on production.

Regards,

Alejandro

On Tue, Nov 10, 2009 at 5:50 PM, Konstantin Vayner <konstantin@...> wrote:

Do you know if there are plans to roll out a stable release any time soon?
I need to use this feature (and i'd also like to see the advanced http administration stuff including per-smsc config reload and new smsc addition etc) in a production system inside telco... i'm not sure if running cvs would be stable enough let alone getting permission to run such a version from the telco it guys ;)

Regards,
  Konstantin

On Tue, Nov 10, 2009 at 6:44 PM, Alejandro Guerrieri <alejandro.guerrieri@...> wrote:

Then you should be able to get it by using the meta-data functionality then.

You need a more or less recent CVS, though, 1.4.3 and earlier won't cut it.

Regards,

Alejandro

On Tue, Nov 10, 2009 at 5:40 PM, Konstantin Vayner <poncha@...> wrote:

yes, i think this might be tlv
attached you can see dump of two messages, one without privacy_indicator and one with
the second one had "Optional parameter tag (0x0201)" line in debug before pdu dump

On Tue, Nov 10, 2009 at 6:20 PM, Alejandro Guerrieri <alejandro.guerrieri@...> wrote:

Maybe it's a TLV? Can you paste your pdu dump?

Regards,

Alejandro

On Tue, Nov 10, 2009 at 5:15 PM, Konstantin Vayner <poncha@...> wrote:

Hi list,

One of the smscs (smpp) we are connected to sends a privacy_indicator field in deliver_sm.
And the operator in question wants our application to behave differently depending on the indicator value.
I can see the privacy_indicator in pdu dump in the log, but how can i get this info into my sms-service ?
Looked through the manual and i cant find any option to do so... Either i am missing something or kannel doesnt disclose that info?
It would be good to be able to get all parts (fields) of the message pdu that kannel extracted in general

Also,  i'd like to be able push this privacy indicator back when sending submit_sm. Is this possible?

Regards,
  Konstantin