SMS-MO Problem

[Odyssey]

SMS-MO not received

Debug log of smppccm:

2016-05-05 20:38:13 ERROR    18825 Invalid Optional Parameter Value: Unknown subaddress_type_tag value 0x2b

Traceback (most recent call last):

  File "/usr/lib/python2.7/dist-packages/jasmin/vendor/smpp/twisted/protocol.py", line 195, in rawMessageReceived

    pdu = self.encoder.decode(StringIO.StringIO(message))

  File "/usr/lib/python2.7/dist-packages/jasmin/vendor/smpp/pdu/pdu_encoding.py", line 961, in decode

    self.decodeBody(file, pdu, headerParams['command_length'] - self.HEADER_LEN)

  File "/usr/lib/python2.7/dist-packages/jasmin/vendor/smpp/pdu/pdu_encoding.py", line 1001, in decodeBody

    optionalParams = self.decodeOptionalParams(pdu.optionalParams, file, bodyLength - mParamsLen)

  File "/usr/lib/python2.7/dist-packages/jasmin/vendor/smpp/pdu/pdu_encoding.py", line 1048, in decodeOptionalParams

    option = self.optionEncoder.decode(file)

  File "/usr/lib/python2.7/dist-packages/jasmin/vendor/smpp/pdu/pdu_encoding.py", line 863, in decode

    raise e

PDUParseError: Invalid Optional Parameter Value: Unknown subaddress_type_tag value 0x2b

2016-05-05 20:38:13 CRITICAL 18825 Received unparsable PDU 000000430000000500000000123c8009000101393839333437363930383738000201363937300080000000000000010001310202000d$

[Odyssey]

Bruno, whats your idea about this issue?

[Bruno C]

Seems to be a vendor-specific tag not accepted by Jasmin, the latter is tolerating such tags starting from a very recent version (i think in 0.9b2...), so what's your version ?

If it's already recent, then i'll need to see some pcap traces to check what's going through the wire.

[Odyssey]

Trying both below version facing the same result:

0.8.10

0.9.b3

pcap trace:

Short Message Peer to Peer, Command: Deliver_sm, Seq: 355500039, Len: 73

    Length: 73

    Operation: Deliver_sm (0x00000005)

    Sequence #: 355500039

    Service type: (Default)

    Type of number (originator): International (0x01)

    Numbering plan indicator (originator): ISDN (E163/E164) (0x01)

    Originator address: +XXXXXXXXXXXX

    Type of number (recipient): National (0x02)

    Numbering plan indicator (recipient): ISDN (E163/E164) (0x01)

    Recipient address: 6970

    .... ..00 = Messaging mode: Default SMSC mode (0x00)

    ..00 00.. = Message type: Default message type (0x00)

    10.. .... = GSM features: Reply path (0x02)

    Protocol id.: 0x00

    Priority level: GSM: None      ANSI-136: Bulk         IS-95: Normal (0x00)

    Scheduled delivery time: Immediate delivery

    Validity period: SMSC default validity period

    .... ..00 = Delivery receipt: No SMSC delivery receipt requested (0x00)

    .... 00.. = Message type: No recipient SME acknowledgement requested (0x00)

    ...0 .... = Intermediate notif: No intermediate notification requested (0x00)

    .... ...0 = Replace: Don't replace (0x00)

    Data coding: 0x08

        SMPP Data Coding Scheme: UCS2 (ISO/IEC-10646) (0x08)

        GSM SMS Data Coding

        0000 .... = DCS Coding Group for SMS: SMS DCS: General Data Coding indication - Uncompressed text, no message class (0x00)

        ..0. .... = DCS Text compression: Uncompressed text

        ...0 .... = DCS Class present: No message class

        .... 10.. = DCS Character set: UCS-2 (16-bit) data (0x02)

        GSM CBS Data Coding

        0000 .... = DCS Coding Group for CBS: CBS DCS: Language using the GSM 7-bit default alphabet (0x00)

        ..00 1000 = DCS CBS Message language: Portuguese (0x08)

    Predefined message: 0

    Message length: 7

    Message

    Optional parameters

        Optional parameter: source_subaddress (0x0202)

            Tag: 0x0202

            Length: 13

            Source Subaddress: 2b393839333437363930303030

Short Message Peer to Peer, Command: Deliver_sm - resp, Status: "Invalid optional parameter  value", Seq: 355500039, Len: 17

    Length: 17

    Operation: Deliver_sm - resp (0x80000005)

    Result: Invalid optional parameter  value (0x000000c4)

    Sequence #: 355500039

[Bruno C]

Give me the complete line:

 CRITICAL 18825 Received unparsable PDU ...

I'll try to reproduce the issue.

[Odyssey]

2016-05-05 20:38:13 CRITICAL 18825 Received unparsable PDU 000000430000000500000000123c8009000101393839333437363930383738000201363937300080000000000000010001310202000d$

[Bruno C]

I guess this is not a complete pdu dump since it's not getting parsed here, do you have a pcap to share ?

[Odyssey]

Dear Bruno, Any update?

On Monday, July 4, 2016 at 10:10:00 AM UTC+4:30, Odyssey wrote:

Hi Bruno,

Sorry about late response

in attached you can find pcap

Thanks

[Odyssey]

Did you see pcap?

[Bruno C]

Issue addressed in current release cycle, will be published on Monday,  August 22nd (v0.9.4), please test and confirm resolution asap.

[Odyssey]

Thanks, it works like a charm