| Mm7/,,User Not Defined,FAILED |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 07, 2009 ⬆ |
◄ ► |
| Author | Message | ||||
| Dina Zahed New member Username: Novemberbreeze Post Number: 1 Registered: 06-2009 |
Hi, I have setup up a VASP account (mm7) for a mobile operator to forward the received MMS on a specific shortcode to the NowSMS MMS-IN directory. The operator's MMSC vendor is Nokia, and we are using mm7 not EAIF. The post url configured on their side is http://myIP:myPort/mm7 The MMSCDebug file shows that a message is being posted but at the end of the thread the following is written: 20:31:16:531 [11] ThreadProcessConnection: no find alias for mm7 Also the MMSC 2009-06-25 Log File, states the following: 15:24:58,MMSIN,Operator's IP Address,mm7/,,User Not Defined,FAILED I do not know why mm7/ is appearing in the log, and why User not defined. In the VASP tab, the Account Name is the Operator's IP, and i am not using a password. I have tried leaving the VASP sender address empty, and i also filled it once with the shortcode number and another time with the Operator's IP. But nothing is working. The mobile handset receives a delivery receipt but there is nothing in the MMS-In folder. Am i doing something wrong, or is the operator configuring something wrong on his end? | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 948 Registered: 08-2008 |
Hi Dina, Based upon that log information, they are not sending you MM7 content. Although "/mm7" is in the URL, if NowSMS sees the content type "application/vnd.wap.mms-message", it tries to process it as an MM1 or EAIF request. You might want to enable the MMSCDEBUG.LOG to see the raw transaction information ... and this may tell us some more information as well. But I think it is going to show us that they are trying to post to you using the EAIF protocol. -- Des NowSMS Support | ||||
| Dina Zahed New member Username: Novemberbreeze Post Number: 2 Registered: 06-2009 |
Hi Des, I have attached the MMSCDEBUG.LOG
I did notice in it application/vnd.wap.mms-message But its strange, because the operator told me that they were posting using MM7, but maybe because its a Nokia MMSC something is going wrong at their end. Appreciate your feedback. | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 949 Registered: 08-2008 |
Hi Dina, Yes, it's definitely not MM7. It's an MM1 format message. If the operator doesn't know how to change it to MM7 format, just have them change the URL to http://myIP:myPort/eaif, and you should be ok. -- Des NowSMS Support | ||||
| Dina Zahed New member Username: Novemberbreeze Post Number: 3 Registered: 06-2009 |
Hi Des, Thank you very much Des, hope it works. Would you happen to know where i can find Nokia MMSC configuration information/documentation? Because the operator tells me that Nokia's MMSC supports MM7 in a weird way (it converts internally from EAIF to MM7). | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 950 Registered: 08-2008 |
There's a document called "External Application Developer's Guide" that Nokia publishes. I've downloaded it from forum.nokia.com in the past. There is a section that talks about parameters that can be configured on the operator side, but it doesn't go into much detail on them. One of the settings is protocol ... MM7 or EAIF. Unfortunately, it doesn't tell you where the parameters are configured. (Well, I'm looking at the 3.1 version of the document, and maybe the 3.2 version has more details.) -- Des | ||||
| Dina Zahed New member Username: Novemberbreeze Post Number: 4 Registered: 06-2009 |
Hello Des, Well we converted to EAIF, and i am still getting the same issue. 2009-06-26 20:47:50,MMSIN,62.241.155.46,User3266,,User Not Defined,FAILED Attached is the Debug Log.
I also noticed in the Debug Log the following: 1- The post url is http://myIP:myPort/EAIF/username=password 2- It seems the MMS is being sent twice or something. Appreciate your kind help. | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 953 Registered: 08-2008 |
Hi Dina, That is a strange POST. Previously, it was coming in to: http://217.52.75.115:2007/mm7 Not it is coming in to: /217.52.75.115:2007/eaif/user=pass The problem seems to be a missing "http://" prefix ... so "/217.52.75.115:2007" is getting treated as part of the URL. (It's also strange, because normally we don't see "http://host:port" at all ... but it's ok.) As a result, we're parsing the user information as a local MMSC users instead of as a VASP because we don't see the "/eaif" in the beginning of the URL. So I think they've got a typo in there somewhere. I don't know what configuration options they have on the operator side. But reading the Nokia document, I think I understand the problem. They can configure the following fields: host address port number URI The URI would normally be the URL without the host address and port number. In this case, it should be: /eaif/user=pass We also will allow the URI to be of a format the includes the host address and port number like this: http://217.52.75.115:2007/eaif/user=pass You're getting closer! -- Des NowSMS Support | ||||
| Dina Zahed New member Username: Novemberbreeze Post Number: 5 Registered: 06-2009 |
Hello, We fixed the issue.Thank you very much. But now i only see in MMSC-Log files the following: 2009-06-26 21:38:15,MMSIN-DeliveryReport,,SMS:localsystem,+20127497452,20090626/21/BAD1210E ,85555ECD.req,121 Shouldn't there be something else besides the DeliveryReport? | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 956 Registered: 08-2008 |
Hi Dina, I might not know enough about your usage scenario to answer this. But let me think about this. There are so many different ways to configure things. When messages go into the MMS-IN directory, they don't actually get written to the log files, just to the directory. (That is something that we should change.) The delivery report handling is also something that we should change. Your system is sending it out via SMS. But technically it should be going back out via MM7 (or EAIF). NowSMS is going to route the delivery report the same way that it would route any other delivery report, either using the internal MMSC functionality, or via an outbound "MMSC Routing" definition. And, actually we should have an option to suppress the delivery report from being sent out at all. I'm going to put in a quick change request on that, as it was not that long ago that we added the functionality to generate a delivery report in this scenario, and that is not always desirable! -- Des NowSMS Support | ||||
MMSC Debug Log
