maemo.org - Talk - View Single Post - [FIX] fMMS - MMS on the N900, cannot receive

shubell	2016-11-18 , 13:08
Posts: 64 \| Thanked: 84 times \| Joined on Oct 2012	#67

It works. I can get the full header now. Even tho there are still some errors. The question is if something is now broken because of those 3 lines.

Code:

MMS 9200 2948 dbus.Array([dbus.Byte(97), dbus.Byte(112), dbus.Byte(112), dbus.Byte(108), dbus.Byte(105), dbus.Byte(99), dbus.Byte(97), dbus.Byte(116), dbus.Byte(105), dbus.Byte(111), dbus.Byte(110), dbus.Byte(47), dbus.Byte(118), dbus.Byte(110), dbus.Byte(100), dbus.Byte(46), dbus.Byte(119), dbus.Byte(97), dbus.Byte(112), dbus.Byte(46), dbus.Byte(109), dbus.Byte(109), dbus.Byte(115), dbus.Byte(45), dbus.Byte(109), dbus.Byte(101), dbus.Byte(115), dbus.Byte(115), dbus.Byte(97), dbus.Byte(103), dbus.Byte(101), dbus.Byte(0), dbus.Byte(175), dbus.Byte(132)], signature=dbus.Signature('y')) dbus.Array([dbus.Byte(140), dbus.Byte(130), dbus.Byte(152), dbus.Byte(49), dbus.Byte(53), dbus.Byte(52), dbus.Byte(67), dbus.Byte(51), dbus.Byte(56), dbus.Byte(56), dbus.Byte(54), dbus.Byte(0), dbus.Byte(141), dbus.Byte(145), dbus.Byte(138), dbus.Byte(128), dbus.Byte(142), dbus.Byte(2), dbus.Byte(6), dbus.Byte(172), dbus.Byte(136), dbus.Byte(5), dbus.Byte(129), dbus.Byte(3), dbus.Byte(3), dbus.Byte(244), dbus.Byte(128), dbus.Byte(131), dbus.Byte(104), dbus.Byte(116), dbus.Byte(116), dbus.Byte(112), dbus.Byte(58), dbus.Byte(47), dbus.Byte(47), dbus.Byte(109), dbus.Byte(109), dbus.Byte(115), dbus.Byte(46), dbus.Byte(116), dbus.Byte(101), dbus.Byte(108), dbus.Byte(101), dbus.Byte(107), dbus.Byte(111), dbus.Byte(109), dbus.Byte(46), dbus.Byte(115), dbus.Byte(105), dbus.Byte(47), dbus.Byte(76), dbus.Byte(74), dbus.Byte(47), dbus.Byte(47), dbus.Byte(49), dbus.Byte(53), dbus.Byte(52), dbus.Byte(67), dbus.Byte(51), dbus.Byte(56), dbus.Byte(56), dbus.Byte(54), dbus.Byte(0), dbus.Byte(137), dbus.Byte(24), dbus.Byte(128), dbus.Byte(43), dbus.Byte(51), dbus.Byte(56), dbus.Byte(54), dbus.Byte(52), dbus.Byte(49), dbus.Byte(55), dbus.Byte(52), dbus.Byte(50), dbus.Byte(49), dbus.Byte(56), dbus.Byte(54), dbus.Byte(47), dbus.Byte(84), dbus.Byte(89), dbus.Byte(80), dbus.Byte(69), dbus.Byte(61), dbus.Byte(80), dbus.Byte(76), dbus.Byte(77), dbus.Byte(78), dbus.Byte(0), dbus.Byte(150), dbus.Byte(6), dbus.Byte(234), dbus.Byte(116), dbus.Byte(101), dbus.Byte(115), dbus.Byte(116), dbus.Byte(0)], signature=dbus.Signature('y')) 
Message-Type: m-notification-ind 
Transaction-Id: 154C3886 
MMS-Version: 1.1 
Message-Class: Personal 
Message-Size: 1708 
Expiry: 259200 
Content-Location: http://mms.telekom.si/LJ//154C3886 
From: +38641666999/TYPE=PLMN 
Subject: test 
() 
Subject: t 
Traceback (most recent call last): 
File "/usr/lib/python2.5/logging/handlers.py", line 73, in emit 
if self.shouldRollover(record): 
File "/usr/lib/python2.5/logging/handlers.py", line 146, in shouldRollover 
msg = "%s\n" % self.format(record) 
File "/usr/lib/python2.5/logging/__init__.py", line 630, in format 
return fmt.format(record) 
File "/usr/lib/python2.5/logging/__init__.py", line 418, in format 
record.message = record.getMessage() 
File "/usr/lib/python2.5/logging/__init__.py", line 288, in getMessage 
msg = msg % self.args 
TypeError: not all arguments converted during string formatting 
+ id -u 
+ [ 29999 != 0 ] 
+ exec sudo /opt/fmms/fmms_magic START gprs0 10.206.128.9 mms.telekom.si mms.telekom.si 213.229.249.161 213.229.249.40

btw is it normal that you receive the mms notification after the mms has been downloaded not after the push sms?

Code:

2016-11-18 14:00:35,702 fmms.__main__: Incoming SMS Push!
2016-11-18 14:00:35,748 fmms.__main__: SRC: MMS:9200
2016-11-18 14:00:35,750 fmms.__main__: DST: 2948
2016-11-18 14:00:35,754 fmms.__main__: decoding...
2016-11-18 14:00:35,814 fmms.controller: content-location: http://mms.telekom.si/LJ//154D3AF6
2016-11-18 14:00:35,826 fmms.controller: transid: 154D3AF6
2016-11-18 14:00:35,828 fmms.controller: Sender: +38641742186/TYPE=PLMN
2016-11-18 14:00:35,954 fmms.controller: saved binary push: <open file '/home/user/.fmms/push/154D3AF6', mode 'wb' at 0x41780140>
2016-11-18 14:00:36,201 fmms.contacts: loaded contacthandler in 0.15 s
2016-11-18 14:00:36,632 fmms.__main__: saving...
2016-11-18 14:00:36,661 fmms.dbhandler: inserted row as: 626
2016-11-18 14:00:37,274 fmms.__main__: fetching mms...
2016-11-18 14:00:37,367 fmms.connectors: i acquired lock (2653)
2016-11-18 14:00:37,377 fmms.connectors: RUNNING IN UGLYHACK MODE
2016-11-18 14:00:37,440 fmms.connectors: UglyHackHandler UP!
APN: Mms.mobitel.si user: mobitel pass: internet proxyip: 213.229.249.40 mmsc1: mms.telekom.si mmsc2: mms.telekom.si
2016-11-18 14:04:39,781 fmms.connectors: fmms_magic retcode: 0
2016-11-18 14:04:39,784 fmms.__main__: getting file: http://mms.telekom.si/LJ//154D3AF6
2016-11-18 14:04:39,920 fmms.__main__: sending notify...
2016-11-18 14:04:39,923 fmms.__main__: using custom mms
2016-11-18 14:04:39,949 fmms.__main__: connecting via proxy 213.229.249.40:8080
2016-11-18 14:04:39,952 fmms.__main__: mmschost: http://mms.telekom.si
2016-11-18 14:04:41,172 fmms.__main__: MMSC STATUS: 200 OK
2016-11-18 14:04:41,177 fmms.__main__: MMSC RESPONDED: {}
2016-11-18 14:04:41,180 fmms.__main__: m-notifyresp-ind: (200, 'OK', {}, True)
2016-11-18 14:04:41,183 fmms.__main__: notifyresp sent
2016-11-18 14:04:41,187 fmms.__main__: connecting with proxy 213.229.249.40:8080
2016-11-18 14:04:41,203 fmms.__main__: trying url: http://mms.telekom.si/LJ//154D3AF6
2016-11-18 14:04:45,972 fmms.__main__: mmsc info: content-length: 2020^M
content-type: application/vnd.wap.mms-message^M
date: Fri, 18 Nov 2016 14:04:45 +0100^M
Connection: close^M

2016-11-18 14:04:46,028 fmms.controller: saved binary mms <open file '/home/user/.fmms/mms/154D3AF6/message', mode 'wb' at 0x417fa920>
2016-11-18 14:04:46,031 fmms.__main__: fetched http://mms.telekom.si/LJ//154D3AF6 and wrote to file
2016-11-18 14:04:46,148 fmms.__main__: sending ack...
2016-11-18 14:04:46,152 fmms.__main__: using custom mms
2016-11-18 14:04:46,183 fmms.__main__: connecting via proxy 213.229.249.40:8080
2016-11-18 14:04:46,185 fmms.__main__: mmschost: http://mms.telekom.si
2016-11-18 14:04:47,010 fmms.__main__: MMSC STATUS: 200 OK
2016-11-18 14:04:47,014 fmms.__main__: MMSC RESPONDED: {}
2016-11-18 14:04:47,017 fmms.__main__: m-acknowledge-ind: (200, 'OK', {}, True)
2016-11-18 14:04:47,020 fmms.__main__: ack sent
2016-11-18 14:04:47,025 fmms.connectors: UglyHackHandler running disconnect
2016-11-18 14:04:47,305 fmms.connectors: disconnecting connection. rx: 3230 tx: 5013
2016-11-18 14:04:47,314 fmms.connectors: UglyHackHandler running disconnect
2016-11-18 14:04:47,539 fmms.connectors: disconnecting connection. rx: 3334 tx: 5065
2016-11-18 14:04:47,547 fmms.__main__: decoding mms... path: /home/user/.fmms/mms/154D3AF6
2016-11-18 14:04:47,549 fmms.controller: decode_binary_mms running: /home/user/.fmms/mms/154D3AF6
2016-11-18 14:04:47,887 fmms.controller: returning message!
2016-11-18 14:04:47,890 fmms.__main__: storing mms...
2016-11-18 14:04:47,938 fmms.dbhandler: inserted row as: 644
2016-11-18 14:04:48,355 fmms.dbhandler: inserting attachment: smil.smil
2016-11-18 14:04:48,403 fmms.dbhandler: inserting attachment: text_0.txt
2016-11-18 14:04:48,442 fmms.dbhandler: inserting attachment: unnamed.png
2016-11-18 14:04:48,482 fmms.dbhandler: inserting description: test2
2016-11-18 14:04:48,521 fmms.__main__: notifying mms...
2016-11-18 14:04:48,842 fmms.__main__: done, returning!

Quote & Reply |

The Following User Says Thank You to shubell For This Useful Post:
Ilew