| Problems receiving MMS through an operator MMSC |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through December 01, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Anonymous |
Hi, I'm running Aircard 750 and NowSMS 5.50. The setup is connected to an operator MMSC through the operator's WAP GW. (WAPGW configured as the Aircard GPRS APN) I have no problems sending MMS from NowSMS to a normal MMS capable handset. Also, I can send MMS from a normal handset to my NowSMS+GPRS setup. I use a PHP script (the one posted here) to send the messages from the command line. However, what seems to be a problem is sending and receiving the same message with NowSMS and the GPRS connection using the operator MMSC. I'm basically just trying to send myself messages. I figure the WAP URL might be a problem... Below is a capture of SMSDEBUG when receiving a WAP push to start the WAP download. However, the URL fails to link to any MMS. If I'm sending an MMS from a handset to the NowSMS+GPRS setup the URL is slightly different and works OK. 12:57:56:735 [4] ThreadProcessInboundSMS: Processing 413D6EEA.in... 12:57:56:735 [4] ThreadProcessInboundSMS: Processing WAP Push Message 12:57:56:735 [4] ThreadProcessInboundSMS: Processing MMS message 12:57:56:735 [4] ThreadProcessInboundSMS: MMS Content-location: http://mms.xxxx.xxx:1234/20040907/12/E05C9E3E.MMS?id=%2b123505512500 12:57:58:137 [3] ThreadProcessInboundMMS: Processing 413D6EEB.Q... 12:57:58:147 [3] ThreadProcessInboundMMS: Before WSPRasDial - Network: Local Area Connection 2 12:58:00:210 [3] ThreadProcessInboundMMS: After WSPRasDial - OK 12:58:00:951 [3] ThreadProcessInboundMMS: GET http://mms.xxxx.xxx:1234/20040907/12/E05C9E3E.MMS?id=%2b123505512500 HTTP/1.0 Accept: application/vnd.wap.mms-message 12:58:05:457 [3] ThreadProcessInboundMMS: Packet Length is 157 bytes 12:58:05:457 [3] ThreadProcessInboundMMS: HTTP/1.0 200 Ok 12:58:05:457 [3] ThreadProcessInboundMMS: Content-type: a 12:58:05:457 [3] ThreadProcessInboundMMS: pplication/vnd.w 12:58:05:457 [3] ThreadProcessInboundMMS: ap.mms-message 12:58:05:457 [3] ThreadProcessInboundMMS: Content-length: 12:58:05:457 [3] ThreadProcessInboundMMS: 71 A= , 12:58:05:457 [3] ThreadProcessInboundMMS: +123505512500/T 12:58:05:457 [3] ThreadProcessInboundMMS: YPE=PLMN 12:58:05:457 [3] ThreadProcessInboundMMS: permanent-mess 12:58:05:457 [3] ThreadProcessInboundMMS: age-not-found 12:58:05:457 [3] ThreadProcessInboundMMS: mm1 - got http ok response 12:58:05:457 [3] ParseInboundMMS: body part #1 Content-type = text/plain 12:58:05:457 [3] ThreadProcessInboundMMS: POST http://mms.xxxx.xxx:1234 HTTP/1.0 Content-length: 18 Content-type: application/vnd.wap.mms-message Accept: application/vnd.wap.mms-message Any idea how to solve this? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3490 Registered: 10-2002 |
I think I'd need to see your log files to understand this. Those URLs look like the format generated by NowSMS as the MMSC ... but we would never return an MMS message that says "permanent-message-not-found". I'd be interested in seeing the complete set of SMSDEBUG.LOG, MMSCDEBUG.LOG and MMSWAPDEBUG.LOG files. (In v5.51, these are enabled by checking the appropriate boxes on the "Serial #" page of the configuration dialog.) | |||
