| TIME STAMP Field or settings with NowSMS 5.51k |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 15, 2006 ⬆ |
◄ ► |
| Author | Message | ||||
| MedSalimALI Frequent Contributor Username: Salim Post Number: 59 Registered: 04-2005 |
Hello Bryce and All Members, I am facing one problem with MM7 settings for sending MMS through a mobile operator. I got the log from his MMSC and it showed that I am submitting MMS without TIME STAMP field parameter. I was reading on Thread from Bryce that, it makes me understand that NowSMS is taking GMT by default to send MMS. So What I need, is there a way to setup this Field as TIME STAMP, or Changing the TIME STAMP from GMT to GMT+3 (Mobile Operator TIME STAMP)will solve the Problem? Both ways which right Now I am guessing, I don't find any way to do it. is there any update of MMSC can help me with my NowSMS 5.51k version. Really who will show me the way, will help me alot and I will share with him more again, for sure. Regards, Salim | ||||
| MedSalimALI Frequent Contributor Username: Salim Post Number: 63 Registered: 04-2005 |
Hi Bryce, I understand that the Mobile operator MMSC is waiting from my MMS submission the TIME STAMP parameter as GMT+3 so how can I setup it as you have seen it on my other Post thread and you told me that my Guess is fine. remember that I am using 5.51k version. Regards, Salim | ||||
| MedSalimALI Frequent Contributor Username: Salim Post Number: 67 Registered: 04-2005 |
Hi Bryce, Do you think so, that I have to uninstall 5.51k and install an 5.50 old version for the TIME STAMP, I am really need your opinion Bryce. I read alot on the Forum I found one place but it was for an old version, and again for the 2006 release one, but you know that we are using 5.51k for most of the stability we have on it. Regards, Salim | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6069 Registered: 10-2002 |
Hi Salim, Your question puzzles me, because if you are submitting an MMS message to the mobile operator via MM7, we do not include a timestamp field of any sort. The field is defined as optional in the MM7 specs. If there is no timestamp field, then the MMSC that receives the MM7 submission should just add one automatically. So if the operator is seeing a time that is 3 hours off, this suggests that there is a time problem in their system. -bn | ||||
| MedSalimALI Frequent Contributor Username: Salim Post Number: 68 Registered: 04-2005 |
Hi Bryce, You know this is among the problems we are facing, dealing with many mobile operators which most of them don't know exactly what they are doing. Even they are telling me to include a TIME STAMP field, and I was trying to find a way to edit it. I asked them, and they don't care because they are on GMT+3 like us, but It seems that they are new on the MMS services or a new MMSC suplier. So bryce, We cannot process sending MMS as GMT+3 from our NowSMS? I read some where in the forum, you was giving a solution MMSC update link which was providing a GMT+3 instead of GMT the default, but my Problem was that it was an old version 5.50. Regards, salim | ||||
| MedSalimALI Frequent Contributor Username: Salim Post Number: 69 Registered: 04-2005 |
Hi Bryce, Please, Can you take a look on the below log I got from their MMSC? xml version="1.0" encoding="utf-8"?> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header><mm7:TransactionID SOAP-ENV:mustUnderstand="1" xmlns:mm7="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0">C7A45640-temp@192.168.0.3</mm7:TransactionID></SOAP-ENV:Header><SOAP-ENV:Body><DeliveryReportRsp xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0"><MM7Version>5.3.0</MM7Version><Status><StatusCode>2007</StatusCode><StatusText>missing mandatory field 'Date'</StatusText></Status></DeliveryReportRsp></SOAP-ENV:Body></SOAP-ENV:Envelope> They send me Email that I have to include the Time Stamp inside my XML request, how can we do that? they send me an XML template (Which I am suspecting that is a SMIL sample which the submission MMS content was defined, can I try it?), I attached it if you can give advice, by the way I will try it. Regards, Salim
| ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6105 Registered: 10-2002 |
Hi Salim, I'm confused. The response from the MMSC is a "DeliveryReportRsp" ... which means that your system sent them a delivery report (and they are acknowledging it). What I don't understand is why your system would be sending them a delivery report. NowSMS can send delivery reports over an MM7 connection (and it does include a "TimeStamp" field in those reports). And I guess what is happening is that someone has sent a message to your VASP requesting a delivery report. If NowSMS is configured to save received MMS messages to the MMS-IN directory, then beginning in v5.51i, if the sender requested a delivery report, it will generate one back. If you want to disable delivery reports, then you can edit VASPOUT/accountname/VASP.INI (for the outbound connection), and add DisableDeliveryReport=Yes under the [VASP] header). And actually, I do see the problem. The REL5 MM7 1.0 thru 1.3 use a "Date" element instead of a "Timestamp" element in delivery reports. Actually, it's more insane than that ... REL5 MM7 1.0 thru 1.3 use a "Date" element ... REL5 MM7 1.4 uses a "Timestamp" element ... REL5 MM7 1.5 goes back to a "Date" element! REL6 MM7 1.0 uses a "Date" element ... REL6 MM7 1.1 uses a "Timestamp" element ... REL6 MM7 1.2 goes back to the "Date" element. No wonder there is so much confusion. We will apply the above adaptations to send the correct "Date" or "Timestamp" header depending on which schema is in use. However, it is not likely that we will update v5.5x for this change, the change will likely only be applied to NowSMS 2006. My advice to resolve the issue is to disable delivery reports, as I detailed above. I don't believe this issue has any relation to the timestamp issues that you have discussed above. (Regading the issues above, any timestamp issues related to v5.50 have nothing to do with what you are talking about. We could experiment with a setting to include a timestamp when submitting MMS messages via MM7 ... but only for NowSMS 2006 ... we are only going back and applying critical patches for v5.5x users.) -bn | ||||
| MedSalimALI Frequent Contributor Username: Salim Post Number: 70 Registered: 04-2005 |
Hi Bryce, Thank you very much for your effort and comment. I am working now on your suggestion and advice, I will give details for what I have found as result. Mainly the setup you give above, I will follow, because Myself I didn't face any similer problem here in Kuwait or another mobile Operatory yet. Regards, Salim | ||||
| MedSalimALI Frequent Contributor Username: Salim Post Number: 71 Registered: 04-2005 |
Hi Bryce, I am facing this problem and I never face similar before. can you give me another suggestion, because I have done the delivery report disabled and still I am not able to send MMS correctly I am getting failed. please see below: [VASP] DisableDeliveryReport=Yes Protocol=MM7 Server=http://82.114.178.4:3128/mm7/mms ServiceCode=8045 SenderAddress=8045 ForceSenderAddress=Yes UseDial=No mm7SubmitReq=Yes VASID=isysts MM7Version=5.4.0 MM7Schema=http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-1 VASPID=isysts.com this is my MMSCIN/OUt log: 11:28:16,MMSIN,127.0.0.1,isysts,+967733111247,VASP:isysts,8B2216DF.mms,134 2006-06-26 11:28:20,MMSOUT,VASP:isysts,isysts/TYPE=PLMN,+967733111247,FAILED,8B2216DF.MMS,1341 I am attaching to you the MMSCDEBUG, and please give any suggestion. Regards, Salim
| ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6122 Registered: 10-2002 |
Hi Salim, The MMS provider is returning the following error: <Status> <StatusCode>4007</StatusCode> <StatusText>User unknown</StatusText> </Status> What is not clear from the error message is whether the MMSC does not know the recipient of the message, or who you are as the sender. The MM7 specification defines error 4007 as "Service denied", with a further explanation of "The client does not have permission or funds to perform the requested operation." So this makes me think that the MMSC does not like your account, or the account information that you have supplied. Either it does not like your VASPID, VASID, ServiceCode or SenderAddress ... or the provider has not configured proper access for your account. -bn | ||||
Sub MMS Sample
MMSCDEBUG
