Hello Aarno, thks for help-me,
I implemented this change and wapbox not stopped, this part is ok now.
now sending the push for mobile phone, the phone does not understand it and
will not rescue the MMS according to the logs of the push SMSC is delivered
to the mobile device.
it allows me to paste the trace, I promise to be the last time ... :)
maybe you can give me a hint, I tried everything but the handset will not
retrieve the message after receiving the push
tks
Rafael
Short Message Peer to Peer, Command: Submit_sm, Seq: 135, Len: 147
Length: 147
Operation: Submit_sm (0x00000004)
Sequence #: 135
Service type: WAP
Type of number (originator): International (0x01)
Numbering plan indicator (originator): ISDN (E163/E164) (0x01)
Originator address: 900101
Type of number (recipient): International (0x01)
Numbering plan indicator (recipient): ISDN (E163/E164) (0x01)
Recipient address: 55349992XXXX
.... ..11 = Messaging mode: Store and forward mode (0x03)
..00 00.. = Message type: Default message type (0x00)
01.. .... = GSM features: UDHI indicator (0x01)
Protocol id.: 0x00
Priority level: GSM: None ANSI-136: Bulk IS-95: Normal
(0x00)
Scheduled delivery time: Immediate delivery
Validity period: Jul 27, 2012 18:54:37.000000000 BRT
.... ..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: 0x04
SMPP Data Coding Scheme: Octet unspecified (8-bit binary) (0x04)
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
.... 01.. = DCS Character set: 8-bit data (0x01)
GSM CBS Data Coding
0000 .... = DCS Coding Group for CBS: CBS DCS: Language using the
GSM 7-bit default alphabet (0x00)
..00 0100 = DCS CBS Message language: Spanish (0x04)
Predefined message: 0
Message length: 77
Message
GSM Short Message Service User Data
UDH Length: 11
IE Id: SMS - Application port addressing scheme, 16 bit address
(0x05): source port 9200, destination port 2948
Destination port: 2948
Source port: 9200
IE Id: SMS - Concatenated short messages, 8-bit reference number
(0x00): message 22, part 2 of 2
Message identifier: 22
Message parts: 2
Message part number: 2
[Short Message fragments (193 bytes): #61(128), #63(65)]
[Frame: 61, payload: 0-127 (128 bytes)]
[Frame: 63, payload: 128-192 (65 bytes)]
[Reassembled Short Message length: 193]
Wireless Session Protocol, Method: Push (0x06), Content-Type:
application/vnd.wap.mms-message
Transaction ID: 0x16
PDU Type: Push (0x06)
Headers Length: 37
Content-Type: application/vnd.wap.mms-message
Headers
Content-Length: 153
Encoding-Version: 1.3
MMS Message Encapsulation, Type: Unknown type 97
X-Mms-Message-Type: Unknown (0x61)
p-Application-Id: 4\r\n\r\n\214\202\2300120000015605120726155614001:
\215\220\203http://172.xx.x.xx/was/0120000015605120726155614001
X-Mms-Expiry: 172777.000000000 seconds
From: +55349992XXXX/TYPE=PLMN
X-Mms-Message-Class: Personal (0x80)
X-Mms-Message-Size: 248146
POST /ppg HTTP/1.0
Content-Length: 836
Host: 172.29.7.35:9080
Content-Type: multipart/related; boundary=asdlfkjiurwghasf;
type="application/xml"
--asdlfkjiurwghasf
Content-Type:application/xml
<?xml version="1.0" ?>
<!DOCTYPE pap PUBLIC "-//WAPFORUM//DTD PAP 1.0//EN" "
http://www.wapforum.org/DTD/pap_1.0.dtd">
<pap>
.<push-message progress-notes-requested="false" ppg-notify-requested-to="
http://172.XX.X.XXX/was" push-id="000120000015605120726155614001">
..<address address-value="WAPPUSH=+55349992XXXX/[email protected]
"></address>
..<quality-of-service bearer-required="true" bearer="SMS"
network-required="true" network="GSM" delivery-method="unconfirmed"
priority="medium"></quality-of-service>
.</push-message>
</pap>
--asdlfkjiurwghasf
X-Wap-Application-Id: 4
Content-Type: application/vnd.wap.mms-message
...0120000015605120726155614001....
http://172.xx.x.xx/was/0120000015605120726155614001...........+55349992XXXX/TYPE=PLMN.......R
--asdlfkjiurwghasf--HTTP/1.0 202 Accepted
Server: Kannel/svn-r4977M
Date: Thu, 26 Jul 2012 18:54:37 GMT
Content-Length: 416
Content-Type: application/xml
<?xml version="1.0"?><!DOCTYPE pap PUBLIC "-//WAPFORUM//DTD PAP 1.0//EN" "
http://www.wapforum.org/DTD/pap_1.0.dtd"><pap><push-response
push-id="000120000015605120726155614001" sender-name="wapsrv.localdomain;
WAP/1.3 (Kannel/svn-r4977M)" reply-time="2012-07-26T18:54:37Z"
sender-address="/ppg"><response-result code ="1001" desc="The request has
been accepted for processing"></response-result></push-response></pap>
2012/7/26 Aarno Syvänen <[email protected]>
>
> Hi,
> can you add function call wap_event_accept_or_create(element_name, e); at
> the start of the function set_attribute_value in file
> gw/wap_push_pap_compiler.c, line 1287
>
> Aarno
>
> On 26.07.2012, at 16:46, Rafael Aquino wrote:
>
> Hello Andreas, thks for help-me,
>
> I found one thing,
>
> when the parameter of pap "progress-notes-requested" at the beginning of
> this wapbox the tag is killed when he is at the end of the tag or not there
> is wapbox is alive and sends the wappush.
>
> huawei as MMSC sends the "progress-notes-requested" at the beginning of
> the tag I removed a sentence "IF" File "wap_push_pap_compiler.c"
>
> 1293 if (octstr_compare (element_name, octstr_imm ("push-message")) ==
> 0) {
> 1294 if (octstr_compare (attr_name, Octstr_imm 1295 ("progress-notes-
> requested")) == 0)
> 1296 (** e). U.Push_Message.progress_notes_requested =
> 1297 (ret = parse_requirement (attr_value))> = 0? ret 0;
>
> and then the wapbox not die again
>
> but even so, the phone does not understand the message and will not get
> MMS.
>
> do not know if there's something about this but in the MMSE is malformed
> packet wireshark seconds:
>
> Wireless Session Protocol, Method: Push (0x06), Content-Type:
> application/vnd.wap.mms-message
> Transaction ID: 0x14
> PDU Type: Push (0x06)
> Headers Length: 73
> Content-Type: application/vnd.wap.mms-message
> Headers
> X-Wap-Application-Id: x-wap-application:mms.ua
> Content-Transfer-Encoding: binary
> Content-Length: 330
> Encoding-Version: 1.3
> MMS Message Encapsulation, Type: Unknown type 45
> X-Mms-Message-Type: Unknown (0x2d)
> [Malformed Packet: MMSE]
> [Expert Info (Error/Malformed): Malformed Packet (Exception occurred)]
> [Message: Malformed Packet (Exception occurred)]
> [Severity level: Error]
> [Group: Malformed]
>
>
> sorry for my terrible inglish.
>
> best regards,
>
> Rafael Aquino
>
>
>
>
>
>
> 2012/7/26 Andreas Fink <[email protected]>
>
>> try running it in the debugger and produce a backtrace if possible. If
>> the wapbox is killed its most likely a bug.
>> Furthermore, there is no PANIC text in the trace below. Check the
>> logfiles for more info (run with log-level=0)
>> It should probably say where it crashes.
>>
>> On 25.07.2012, at 20:14, Rafael Aquino wrote:
>>
>> hello All,
>>
>> i have a problem using the kannel PPG with huawei MMSC sending mmsc wap
>> push, can you hellp me?
>>
>> 2012-07-25 14:53:01 [25836] [12] DEBUG: HTTP: Creating HTTPClient for
>> `172.XX.X.XX'.
>> 2012-07-25 14:53:01 [25836] [12] DEBUG: HTTP: Created HTTPClient area
>> 0xa5eb3d0.
>> 2012-07-25 14:53:01 [25836] [15] INFO: PPG: Accept request </ppg> from
>> <172.XX.X.XX>
>> 2012-07-25 14:53:01 [25836] [15] DEBUG: PPG: http_read_thread: pap
>> multipart accepted
>> 2012-07-25 14:53:01 [25836] [15] PANIC: /usr/bin/wapbox [0x475d3f]
>> 2012-07-25 14:53:01 [25836] [15] PANIC: /lib64/libpthread.so.0
>> [0x3ba780ebe0]
>> 2012-07-25 14:53:01 [25836] [15] PANIC: /usr/bin/wapbox [0x425360]
>> 2012-07-25 14:53:01 [25836] [15] PANIC: /usr/bin/wapbox [0x424ff2]
>> 2012-07-25 14:53:01 [25836] [15] PANIC: /usr/bin/wapbox [0x424fd1]
>> 2012-07-25 14:53:01 [25836] [15] PANIC: /usr/bin/wapbox(pap_compile+0x88)
>> [0x425678]
>> 2012-07-25 14:53:01 [25836] [15] PANIC: /usr/bin/wapbox [0x41bdf0]
>> 2012-07-25 14:53:01 [25836] [15] PANIC: /usr/bin/wapbox [0x461235]
>> 2012-07-25 14:53:01 [25836] [15] PANIC: /lib64/libpthread.so.0
>> [0x3ba780677d]
>> 2012-07-25 14:53:01 [25836] [15] PANIC: /lib64/libc.so.6(clone+0x6d)
>> [0x3ba70d49ad]
>>
>> the wapbox is killed by PPG request from MMSC
>>
>>
>> <?xml
>> version="1.0"
>> ?>
>> <!DOCTYPE pap PUBLIC "-//WAPFORUM//DTD PAP 1.0//EN" "
>> http://www.wapforum.org/DTD/pap_1.0.dtd">
>> <pap>
>> <push-message
>> progress-notes-requested="false"
>> ppg-notify-requested-to="http://172.XX.X.XXX/was"
>> push-id="000120000015559120725145436001">
>> <address
>> address-value="
>> WAPPUSH=+5534XXXXXXXX/[email protected]">
>> </address>
>> <quality-of-service
>> bearer-required="true"
>> bearer="SMS"
>> network-required="true"
>> network="GSM"
>> delivery-method="unconfirmed"
>> priority="medium">
>> </quality-of-service>
>> </push-message>
>> </pap>
>>
>>
>>
>>
>> my last config:
>>
>>
>> group = core
>> admin-port = 13000
>> wapbox-port = 13002
>> smsbox-port = 13003
>> admin-password = XXXX
>> status-password = YYYY
>> wdp-interface-name = "*"
>> log-file = "/var/log/kannel/bearerbox.log"
>> log-level = 0
>> box-deny-ip = "*.*.*.*"
>> box-allow-ip = "127.0.0.1"
>> access-log = "/var/log/kannel/access.log"
>> store-type = file
>> store-location = "/var/log/kannel/sms-store.dta"
>>
>>
>> group = wapbox
>> bearerbox-host = 127.0.0.1
>> log-file = "/var/log/kannel/wapbox.log"
>> log-level = 0
>> syslog-level = none
>> access-log = "/var/log/kannel/wapaccess.log"
>>
>>
>> group = radius-acct
>> our-port = 1813
>> secret-nas = 1212
>> remote-host = 127.0.0.1
>> remote-port = 1646
>> secret-radius = 1212
>>
>> group = smsbox
>> bearerbox-host = 127.0.0.1
>> sendsms-port = 13013
>> log-file = "/var/log/kannel/smsbox.log"
>> log-level = 0
>> access-log = "/var/log/kannel/smsaccess.log"
>> sendsms-url = /cgi-bin/sendsms
>> mo-recode = true
>>
>> group = ppg
>> ppg-url = /ppg
>> ppg-port = 9080
>> concurrent-pushes = 100
>> default-smsc = fo
>> users=1024
>> global-sender ="+5534XXXXXX"
>> service-name = PPG0
>> trusted-pi = true
>> ppg-allow-ip = "*.*.*.*"
>>
>> group = smsc
>> smsc = smpp
>> smsc-id = fo
>> no-sender = true
>> no-coding = true
>> transceiver-mode = yes
>> smsc-username = XXXX
>> smsc-password = XXXXXX
>> system-type = "WAP"
>> service-type = "WAP"
>> host = 172.29.7.10
>> port = 5019
>> dest-addr-ton = 1
>> dest-addr-npi = 1
>> bind-addr-ton = 1
>> bind-addr-npi = 1
>> #msg-id-type = "0x00"
>> receive-port = ""
>> my-number = "+5534XXXXXX"
>>
>>
>>
>> please help me...
>>
>>
>> Rafael Aquino
>>
>>
>>
>
>