Hi Bobby
You can have and individual log for each smsc by just adding a
log-file=path/to/file/mylog and log-level to each smsc configuration.
Regards
Alvaro
|-----------------------------------------------------------------------------------------------------------------|
Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier
celular y Nextel
en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS
y GPRS online
Visitenos en www.perusms.com
On Tue, Jul 14, 2015 at 3:15 PM, Bobby Richardson <
bobby.richard...@jasper.com> wrote:
> Here is the log and line numbers:
>
>
>
> 01: 2015-04-16 18:12:25 [20014] [6] DEBUG: SMPP[SMSC1_ATT_RSS]: UDH length
> read as 3
>
> 02: 2015-04-16 18:12:25 [20014] [6] DEBUG: SMPP[SMSC1_ATT_RSS]: Sending
> PDU:
>
> 03: 2015-04-16 18:12:25 [20014] [6] DEBUG: SMPP PDU 0x1d3d7a80 dump:
>
> 04: 2015-04-16 18:12:25 [20014] [6] DEBUG: type_name: deliver_sm_resp
>
> 05: 2015-04-16 18:12:25 [20014] [6] DEBUG: command_id: 2147483653 =
> 0x80000005
>
> 06: 2015-04-16 18:12:25 [20014] [6] DEBUG: command_status: 0 = 0x00000000
>
> 07: 2015-04-16 18:12:25 [20014] [6] DEBUG: sequence_number: 9014 =
> 0x00002336
>
> 08: 2015-04-16 18:12:25 [20014] [6] DEBUG: message_id: NULL
>
> 09: 2015-04-16 18:12:25 [20014] [10] DEBUG: send_msg: sending msg to box:
> <127.0.0.1>
>
> 10: 2015-04-16 18:12:25 [20014] [7] DEBUG: Optional parameter tag (0x0427)
>
> 11: 2015-04-16 18:12:25 [20014] [7] DEBUG: Optional parameter length read
> as 1
>
> 12: 2015-04-16 18:12:25 [20014] [7] DEBUG: Optional parameter tag (0x001e)
>
> 13: 2015-04-16 18:12:25 [20014] [7] DEBUG: Optional parameter length read
> as 11
>
> 14: 2015-04-16 18:12:25 [20014] [7] DEBUG: SMPP[SMSC2_ATT_RSS]: Got PDU:
>
> 15: 2015-04-16 18:12:25 [20014] [10] DEBUG: boxc_sender: sent message to
> <127.0.0.1>
>
> 16: 2015-04-16 18:12:25 [20014] [6] DEBUG: SMPP PDU dump ends.
>
> 17:
>
> 18: 2015-04-16 18:12:25 [20014] [7] DEBUG: SMPP PDU 0x1d438e90 dump:
>
> 19: 2015-04-16 18:12:25 [20014] [7] DEBUG: type_name: deliver_sm
>
> 20: 2015-04-16 18:12:25 [20014] [7] DEBUG: command_id: 5 = 0x00000005
>
> 21: 2015-04-16 18:12:25 [20014] [7] DEBUG: command_status: 0 = 0x00000000
>
> 22: 2015-04-16 18:12:25 [20014] [7] DEBUG: sequence_number: 9004 =
> 0x0000232c
>
> 23: 2015-04-16 18:12:25 [20014] [7] DEBUG: service_type: NULL
>
> 24: 2015-04-16 18:12:25 [20014] [7] DEBUG: source_addr_ton: 1 =
> 0x00000001
>
>
>
> [image: cid:image001.png@01CF5A5E.181E0540]
>
> *Bobby Richardson*
>
> Manager - SIM Engineering
>
> O 650.810.8196 | M 310.894.0100
>
>
>
> *From:* users [mailto:users-boun...@kannel.org] *On Behalf Of *Bobby
> Richardson
> *Sent:* Tuesday, July 14, 2015 1:11 PM
> *To:* users@kannel.org
> *Subject:* Multiple SMPP objects overlapping
> *Importance:* High
>
>
>
> Hello:
>
>
>
> My organization uses Kannel logs everyday and is experiencing a technical
> challenge recently.
>
> For this issue, I searched through kannel.org and unfortunately could not
> find any helpful solution.
>
>
>
> From attached, you may see 2 SMPP objects (first one is a complete one;
> lines between 1 and 16 and the second one is just a partial) with 2
> different connection names (ie. SMPP[SMSC1_ATT_RSS] and
> SMPP[SMSC2_ATT_RSS]) .
>
>
>
> Before the second SMPP object starts, I expected “SMPP PDU dump ends.”
> first and then “SMPP[SMSC2_ATT_RSS]: Got PDU:”. “SMPP[SMSC2_ATT_RSS]:
> Got PDU:” was placed in line 14 before the first SMPP object ends.
>
> Is this normal sequence? In many cases, I have seen “SMPP PDU dump ends.”
> as an indication of end of a SMPP. And then after this, another SMPP may
> start with “SMPP[SMSC2_ATT_RSS]: Got PDU:”.
>
>
>
> Do you have any suggestion for how to let Kannel log records one SMPP
> object at a time without getting mixed?
>
> Is there any specific parameter in the Configuration file to control this
> case?
>
>
>
> Thank you.
> Bobby
>
>
>
> [image: cid:image001.png@01CF5A5E.181E0540]
>
> *Bobby Richardson*
>
> Manager - SIM Engineering
>
> O 650.810.8196 | M 310.894.0100
>
>
>
