| HELP: Connection to Cingular MMS DOWN! |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through October 19, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Claeton New member Username: Claeton Post Number: 5 Registered: 09-2005 |
I have been successfully sending test messages through a Sony-Ericsson z500a for a long time. Suddenly, the NOWSMS gateway is no longer able to connect to Cingular. Data I have so far: 1) SMS sending via NOWSMS is OK. 2) MMS send/recv using the handset (not through NOWSMS) is working fine. 3) NOWSMS MMSC Routing "Test Connection" makes the phone initiate a WAP connection, but NOWSMS reports that it cannot connect to the gateway. 4) I took the settings from the MMSC Route in NOWSMS and created a new profile with them in the phone and was able to send/recv MMS messages using the phone. It just seems that sending from NOWSMS is somehow broken, but nothing has been touch in NOWSMS isn weeks. What else could be wrong? | |||
| Claeton New member Username: Claeton Post Number: 6 Registered: 09-2005 |
One possibility is that Cingular is screening connections based on the useragent or profile, but I don't see reports of that from anyone else. Here's the debug output from MMSWAPDEBUG.LOG: 6:35:18:115 InitTAPI: Performing TAPI initialisation 16:35:30:042 GetCIDForAPN: Sony Ericsson Z500 Serial Modem #2 16:35:30:042 GetCIDForAPN: wap.cingular 16:35:30:042 InitTAPI: Returning cached TAPI session information 16:35:36:011 GetCIDForAPN: AT+CGDCONT=? 16:35:36:081 GetCIDForAPN: +CGDCONT: (1-10),("IP"),,,(0-1),(0-1) +CGDCONT: (1-10),("IPV6"),,,(0-1),(0-1) OK 16:35:36:081 GetCIDForAPN: minCID = 1, maxCID = 10 16:35:36:081 GetCIDForAPN: AT+CGDCONT? 16:35:36:191 GetCIDForAPN: +CGDCONT: 1,"IP","wap.cingular","0.0.0.0",0,0 +CGDCONT: 2,"IP","wap.cingular","0.0.0.0",0,0 OK 16:35:36:191 GetCIDForAPN: Found CID=1 for APN wap.cingular 16:35:36:191 WSPRasDial: Before RasDial NowSMS - Sony Ericsson Z500 Serial Modem #2 16:35:45:655 WSPRasDial: RasDial connected to NowSMS - Sony Ericsson Z500 Serial Modem #2 16:35:45:675 WSPAddRoute: Routing 66.209.11.61 via 10.20.35.31 16:35:45:905 WSPConnect: Sending 44 byte request to 66.209.11.61 16:35:45:905 WSPConnect: Packet Length is 44 bytes 16:35:45:905 WSPConnect: 0A 00 01 12 01 10 0A 1A 04 80 8F F8 00 04 81 8F 16:35:45:905 WSPConnect: F8 00 A9 4E 6F 77 20 53 4D 53 2F 4D 4D 53 20 47 Now SMS/MMS G 16:35:45:905 WSPConnect: 61 74 65 77 61 79 20 76 35 2E 30 00 ateway v5.0 16:35:55:920 WSPConnect: Sending 44 byte request to 66.209.11.61 16:35:55:920 WSPConnect: Packet Length is 44 bytes 16:35:55:920 WSPConnect: 0B 00 01 12 01 10 0A 1A 04 80 8F F8 00 04 81 8F 16:35:55:920 WSPConnect: F8 00 A9 4E 6F 77 20 53 4D 53 2F 4D 4D 53 20 47 Now SMS/MMS G 16:35:55:920 WSPConnect: 61 74 65 77 61 79 20 76 35 2E 30 00 ateway v5.0 16:36:06:335 WSPConnect: Received 13 byte response from 66.209.11.61 16:36:06:335 WSPConnect: Packet Length is 13 bytes 16:36:06:335 WSPConnect: 12 80 01 03 40 C4 00 C0 32 AC 10 1A 0F @ 2 16:36:06:375 WSPConnect: Sending 44 byte request to 66.209.11.61 16:36:06:375 WSPConnect: Packet Length is 44 bytes 16:36:06:375 WSPConnect: 0A 00 01 12 01 10 0A 1A 04 80 8F F8 00 04 81 8F 16:36:06:375 WSPConnect: F8 00 A9 4E 6F 77 20 53 4D 53 2F 4D 4D 53 20 47 Now SMS/MMS G 16:36:06:375 WSPConnect: 61 74 65 77 61 79 20 76 35 2E 30 00 ateway v5.0 16:36:16:389 WSPConnect: Sending 44 byte request to 66.209.11.61 16:36:16:389 WSPConnect: Packet Length is 44 bytes 16:36:16:389 WSPConnect: 0B 00 01 12 01 10 0A 1A 04 80 8F F8 00 04 81 8F 16:36:16:389 WSPConnect: F8 00 A9 4E 6F 77 20 53 4D 53 2F 4D 4D 53 20 47 Now SMS/MMS G 16:36:16:389 WSPConnect: 61 74 65 77 61 79 20 76 35 2E 30 00 ateway v5.0 16:36:26:404 WSPConnect: Sending 44 byte request to 66.209.11.61 16:36:26:404 WSPConnect: Packet Length is 44 bytes 16:36:26:404 WSPConnect: 0B 00 01 12 01 10 0A 1A 04 80 8F F8 00 04 81 8F 16:36:26:404 WSPConnect: F8 00 A9 4E 6F 77 20 53 4D 53 2F 4D 4D 53 20 47 Now SMS/MMS G 16:36:26:404 WSPConnect: 61 74 65 77 61 79 20 76 35 2E 30 00 ateway v5.0 16:36:36:418 WSPConnect: Sending 44 byte request to 66.209.11.61 16:36:36:418 WSPConnect: Packet Length is 44 bytes 16:36:36:418 WSPConnect: 0B 00 01 12 01 10 0A 1A 04 80 8F F8 00 04 81 8F 16:36:36:418 WSPConnect: F8 00 A9 4E 6F 77 20 53 4D 53 2F 4D 4D 53 20 47 Now SMS/MMS G 16:36:36:418 WSPConnect: 61 74 65 77 61 79 20 76 35 2E 30 00 ateway v5.0 16:36:46:432 WSPConnect: Sending 44 byte request to 66.209.11.61 16:36:46:432 WSPConnect: Packet Length is 44 bytes 16:36:46:432 WSPConnect: 0B 00 01 12 01 10 0A 1A 04 80 8F F8 00 04 81 8F 16:36:46:432 WSPConnect: F8 00 A9 4E 6F 77 20 53 4D 53 2F 4D 4D 53 20 47 Now SMS/MMS G 16:36:46:432 WSPConnect: 61 74 65 77 61 79 20 76 35 2E 30 00 ateway v5.0 16:36:56:447 WSPRasDial: Unable to connect to WAP gateway at 66.209.11.61 16:36:56:447 WSPRasHangUp: NowSMS - Sony Ericsson Z500 Serial Modem #2 | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7063 Registered: 10-2002 |
Strange. I do have an old report from someone who was using another model of a SonyEricsson mobile phone, and the phone became confused about access point definitions. The problem was resolved by deleting all data account definitions through the phone user interface. You could also try going into HyperTerminal, and issuing the following commands: AT+CGDCONT=1 AT+CGDCONT=2 This will remove the current APN definitions, and require NowSMS to recreate what it needs. | |||
| Claeton New member Username: Claeton Post Number: 7 Registered: 09-2005 |
Bryce - Thanks for your reply. I got pulled off this evaluation for a while, but am picking it up again. So, if I use the AT+CGDCONT= commands, the GSM modem will delete the APN defs in the phone. Then NowSMS will recreate new defs in the phone from the MMS profile I give it? Will I be able to see those defs from the phone's UI? - Claeton | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7138 Registered: 10-2002 |
Sorry for the delay in response Claeton ... in the phone UI for SonyEricsson phones, these definitions often show up under "Data Accounts". So another idea is to delete those "Data Accounts" via the phone UI. -bn | |||
| Claeton New member Username: Claeton Post Number: 8 Registered: 09-2005 |
Bryce, I found a couple of posts with the exact same behavior as shown in the debug log. The root cause was some problem with a networking windows API call returning an unexpected response that tripped up NOWSMS. The patched mmswap.dll fixed the problem. This has been one of those back-burner evaluation projects that just keeps getting pushed off. Before going further, we'll upgrade to the lastest version on a clean machine. Thanks for your help. Regards, Claeton | |||
