| MMS inbound not working |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 28, 2006 ⬆ |
◄ ► |
| Author | Message | ||||
| Rick May New member Username: Rickmay Post Number: 1 Registered: 06-2006 |
Bryce: I need a debug option to get you more information. I searched all these threads and am not sure how to get you a debug copy. I can send SMS in and out using a MultiTech GSM GPRS modem, but not MMS. I think I have read everything. Here is my configuration: Microsoft Windows Server 2003 Standard Edition Service Pack 1 Microsoft SharePoint Server 2007 is installed NowSMS v2006.03.09 MultiTech GSM GPRS wireless Modem model MTCBA-G-F2 Attached at COM 02 Email from NowSMS is received and sent from Microsoft (Office) Outlook 2007 Test phone is a Cingular 8125 PDA Camera Cell Phone MMS Settings for Cingular MMS Server URL: mmsc.cingular.com/ WAP Gateway IP: 66.209.11.61 GPRS APN: wap.cingular Login Name: WAP@CINGULARGPRS 1. Placed the modem SIM card in the Cingular 8125 and sent a picture to our Razr – no problem. Returned the modem SIM card to the modem. 2. Sent an MMS from Outlook email to the phone number of my Cingular 8125; ATTACHING a 7KB GIF picture. a. Cell Phone Note “Unable to receive your message(s). Your message notification(s) will remain in the Inbox.” 3. Sent an MMS from Outlook email to the phone number of my Cingular 8125; with the picture pasted as part of the email content. a. Cell Phone Note “Unable to receive your message(s). Your message notification(s) will remain in the Inbox.” 4. Sent a TEXT message from Outlook email. Message received in MMS Inbox in the 8125 cell phone. 5. Sent a TEXT message from the 8125 cell phone to server / NowSMS. Outlook received email text message. 6. Sent an MMS message from a Cingular GSM Razr to the server / modem / NowSMS. Nothing received. I think I have read all the non-MMS transmission communications here - and still no MMS activity. Thanks for your help Rick | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6087 Registered: 10-2002 |
Hi Rick, I've moved this message into a separate thread, because I didn't think it was related to the issues being discussed in the thread that it was originally posted to (http://support.nowsms.com/discus/messages/485/13110.html). If you're working with someone who is posting in that thread, I'm sorry ... it just seemed like the issues being discussed were different, so I didn't want to get them confused. Let's focus on sending MMS first. It sounds like what is going on is that NowSMS is acting like an MMSC in sending out the MMS notifications instead of routing the MMS messages out to the operator MMSC via the GPRS modem. Go to the "MMSC Routing" page, and add a route for the GPRS modem. "Account name" and "Account description" are names that are only used internally by NowSMS, so these can be whatever you like. Leave "Default Sender Address" blank ... and "Allow Sender Address Override" UNchecked. Go ahead and leave "Route messages to this ..." blank, as we'll go back to the previous screen and make this route the default. "Route Messages to VASP via" should be "MM1". Press "Lookup Operator Settings" to load the settings for Cingular (your stetings above look correct, except that you also need Password: CINGULAR1). Set "Network Connection:" to point to your modem. Then press "Test Connection" to verify that the GPRS/WAP part of the settings are correct. (If you are going to have multiple e-mail users sending out to MMS, also check "Embed Original Sender in Subject Header"). Press "OK" ... then when you are back on the "MMSC Routing" page, make that newly defined route your default outbound route. Restart the MMSC service (I think you will be prompted to do this automatically). Then try sending again. On the receiving end, I assume that you defined the "MMS Settings" when defining the modem in the "SMSC" list. Did you include Password: CINGULAR1 in these settings? If it's not a password issue, let's take a look at the debug logs to troubleshoot that. On the "Serial #" page of the configuration dialog, go ahead and enable all of the debug logs. Repeat the sending and receiving attempts with those debug logs enabled ... then ZIP them up and post in reply here, or e-mail to nowsms@now.co.uk with "Attention: Bryce" in the subject line, referencing this thread. -bn | ||||
| Rick May New member Username: Rickmay Post Number: 2 Registered: 06-2006 |
Bryce: Thank you very much. I think we have been pointed to a problem, but not sure how to fix. I think we created this in our long hours of trying EVERYTHING prior to communicating with you. First, we are using CINGULAR1 as the password. Second, we set up MMSC Routing as requested. Test Connection returned a first message of "modem is not responding to GPRS commands, testing will continue". Followed by " Connection Failed, RAS error 692, hdw failure or modem connected to another device" With this information, we went to SMSC / Properties / MMS Settings / Test Connection. We received the exact RAS error. We see an error - and cannot fix. The SMSC tab has a connection labeled "COM1". Our modem should be COM2. When we try to add another connection here, we cannot. We took a quick check - Windows device manager - found the modem description under Modems. Properties shows COM2. Applied all three debug logs. Rick | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6096 Registered: 10-2002 |
Rick, Remove "COM1" from the "SMSC" list. Add the named Multitech modem driver instead. I think this will resolve the immediate conflict. -bn | ||||
| Rick May New member Username: Rickmay Post Number: 3 Registered: 06-2006 |
Bryce: We deleted the COM1 connection. Restarted to make sure it was clear. Selected ADD, selecting GSM Modem or Phone, selecting our named modem, then Test and Add modem. "Unable to access modem at COM2 -Error 5 - access is denied. Another application is already using this device" So, we have another ghost of our past mistakes. We will look. And , will do SMS and MMS messages to place data in the debug files. Thanks, Rick | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6101 Registered: 10-2002 |
Rick, Is the modem actually on COM2? Before, the SMS messages were actually being sent with NowSMS configured to use the modem on COM1, right? If you put COM1 back, can you send SMS messages again? I'm wondering if the underlying problem is that the modem driver is configured for COM2 but should be on COM1? The error code that you are getting suggests that another application has the modem open. Those can be difficult problems to sort out, because I'm not aware of any programs that can tell you which application that is running on the PC has the port open. -bn | ||||
| Rick May New member Username: Rickmay Post Number: 4 Registered: 06-2006 |
Bryce: Great. We will go that direction. Windows Task Manager shows no other activity. So, big possibility that modem is actually on COM1 and driver configured on COM2. Rick | ||||
| Rick May New member Username: Rickmay Post Number: 5 Registered: 06-2006 |
Bryce: We spent a lot of time testing to make sure modem is on COM1. Still cannot get any message through.
At this time, we cannot send anything in or out. We are too close to this and may be making mistakes. We have been careful to make sure all descriptions are COM1. We uninstalled everything and used a modem tester which gave us good information on COM1. I hope you can untangle us. We tried to send out 2 messages at 7:31 and 1 text in from a cell at 7:41. Rick | ||||
| Rick May New member Username: Rickmay Post Number: 6 Registered: 06-2006 |
Bryce: Continuing.. We spent time trying to evaluate the modem - which is new. We used Modemtest from PassMark. Modemtest with NowSMS running, test says COM1 in use. We turn off NowSMS, modem test says COM1 in use. We power down server, power back on, run modem test immediately, COM1 shows good modem readings. We wait a few minutes, modem test shows COM1 busy?? System shows no other software running. Still trying to see what this suggests. Still looking for other ways to test modem. Been through all NowSMS setting, feel good, but not 100% sure. Rick | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6103 Registered: 10-2002 |
Hi Rick, I'm not really sure what to suggest at this point. It sounds like something is grabbing the modem, a service process, or some other software that is loaded by startup. I've had problems in the past with Nokia PC Suite doing this. Make sure that NowSMS is not configured not to run as a service (so that it is not NowSMS conflicting with itself ... normally this doesn't happen unless you are accessing the PC via Remote Desktop, are you?). Then, without NowSMS running as a service (uncheck "Run as a service" on "Service" page of config), I'd suggest confirming the observations that you have about the modem initially being ok immediately after bootup, but then several minutes becoming inaccessible. Confirm it once just testing the modem with NowSMS. (Assuming you are testing the named modem driver from within NowSMS, try adding the COM port directly ... does it also report an error. If it does not return an error, let me know, but do not leave the COM port definition in the SMSC list.) Then reboot, and confirm it just testing the modem through the Windows Control Panel ... Phone & Modem Options ... Diagnostics .... Query Modem. If the problem occurs without ever running NowSMS .... then ... hmm ... there must be some other application that grabs the port after startup. Try closing any tray icons (bottom right corner of screen) .... look at the Services list in the Administrative section, and try shutting down some non-core services ... retesting for modem accessibility each time you shut something down to try to determine what the conflict is. -bn | ||||
zip of log files
