Hakan Lager wrote:
Hi,
As you can see the last part of the URL (.38) is missing in the GET request from the Symbian But it seems to still exist in the MMS notification sent by kannel, so my guess is that your Symbian of any reason misinterpret the notification, perhaps it thinks that the URL
is too long (try a shorter mbubi host name) .
I checked the PDU in PDUspy and it is not correct. But I think you have fixed it manually showhow, correct? / Hakan

2008/1/22, Andrew B <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>:

       I am sending MMS messages from a WM6 phone to a Symbian phone,
    and I
    get the following error when I send some MMS messages:
    The phone retrieves the message and displays the following:
    Message not found

    Here are the (what I feel are) relevant log messages:

    2008-01-22 07:25:39 [11092] [25] DEBUG: Parsing URL
    
`http://localhost:13013/cgi-bin/sendsms?_dummy=x&username=foo&password=bar&text=%01%06%03%BE%AF%84%8C%82%98-
    
qf4709.1.x92.38%00%8D%90%89%18%80208.54.94.40%2FTYPE%3DIPv4%00%96Mmmmm...+Yummy%00%8A%80%8E%02t%87%88%05%81%03%01Q%5B%83http%3A%2F%2Fgentoo1.**************%3A8191%2Fqf4709.1.x92.38%402%2Fwx42%00&to=703xxxxxxx&udh=%06%05%04%0B%84%23%F0
    ':


    2008-01-22 07:25:59 [11089] [5] DEBUG: Octet string dump ends.
    2008-01-22 07:25:59 [11089] [4] DEBUG: Fetcher got
    http://nds1.nds.nokia.com/uaprof/NE62-1r100.xml
    <http://nds1.nds.nokia.com/uaprof/NE62-1r100.xml>
    2008-01-22 07:25:59 [11089] [4] ERROR: MMS Fetch interface: failed to
    find envelope/data qf4709.1.x92. for request url (/qf4709.1.x92.) from
    209.183.32.20 <http://209.183.32.20> (e=not found)!
    2008-01-22 07:25:59 [11089] [4] DEBUG: WSP: Mapping `text/plain', WSP
    1.2 to 0x0003.
    2008-01-22 07:25:59 [11089] [4] DEBUG:  $$$$$$ fetch message [fail]
    replying with [type=m-retrieve-conf,content_len=105]:

    and on the kannel side:
    2008-01-22 07:40:40 [10866] [6] DEBUG: AT2[/dev/ttyUSB0]:
    TP-Validity-Period: 24.0 hours
    2008-01-22 07:40:40 [10866] [6] DEBUG: AT2[/dev/ttyUSB0]: -->
    AT+CMGS=153^M
    2008-01-22 07:40:40 [10866] [6] DEBUG: AT2[/dev/ttyUSB0]: <-- >
    2008-01-22 07:40:40 [10866] [6] DEBUG: AT2[/dev/ttyUSB0]: send command
    status: 1
    2008-01-22 07:40:40 [10866] [6] DEBUG: AT2[/dev/ttyUSB0]: -->
    
'0051000a8107535081280004a78c0605040b8423f0030603beaf848c82982d7166343730392e312e7839322e3338008d908918803230382e35342e39342e34302f545950453d4950763400964d6d6d6d6d2e2e2e59756d6d79008a808e02748788058103014dd783687474703a2f2f67656e746f6f312e585858585858585858582e5858583a383139312f7166343730392e312e7839322e33'

    2008-01-22 07:40:44 [10866] [6] DEBUG: AT2[/dev/ttyUSB0]: --> ^Z
    2008-01-22 07:40:48 [10866] [6] DEBUG: AT2[/dev/ttyUSB0]: <-- >
    2008-01-22 07:40:48 [10866] [6] DEBUG: AT2[/dev/ttyUSB0]: <--
    +CMGS: 222
    2008-01-22 07:40:48 [10866] [6] DEBUG: AT2[/dev/ttyUSB0]: <-- OK
    2008-01-22 07:40:48 [10866] [6] DEBUG: AT2[/dev/ttyUSB0]: send command
    status: 0

    ^^^The PDU has been sanitized...

    and here is the /var/spool/mbuni/mm1 directory
    [EMAIL PROTECTED] /var/spool/mbuni/mm1 $ ls
    0  1  2  3  4  5  6  7  8  9  a  b  c  d  df4709.1.x92.38  e  f  g  h
    i  j  k  l  m  n  o  p  q  qf4709.1.x92.38  r  s  t  u  v  w  x  y  z


    Also, if I send a simple MMS (one of the built in ones on WM6, the
    Boing! Happy birthday one) it works just fine...

    Thanks in advance for any help!
    _______________________________________________
    Users mailing list
    [email protected] <mailto:[email protected]>
    http://lists.mbuni.org/mailman/listinfo/users


I shortened the FQDN to just the IP address of the server, and that seemed to work (it still truncated some characters, but it sent enough through that the nokia was able to retrieve the message. I guess I'm wondering, how come mbuni didn't just generate a concatenated SMS if it couldn't fit everything in a single PDU?

Thanks!

_______________________________________________
Users mailing list
[email protected]
http://lists.mbuni.org/mailman/listinfo/users

Reply via email to