| Problem when using HTTP Post/Get to Gateway |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 06, 2005 ⬆ |
◄ ► |
| Author | Message | |||||
| nguyen the vinh New member Username: Vinhnguyen Post Number: 1 Registered: 02-2005 |
Hello, After configurating MMSC (without SMSC), I try to receive the MMS message by using HTTP Get, http://127.0.0.1:8080/?PhoneNumber=%2B447778001210&MMSFrom=%2B447778001210&MMSSubject=vinhtest&MMSText= vinhtest&MMSFile=http://127.0.0.1/Next.gif But I didn't see any mms message int MMS-IN directory, and the MMSDebug log is Please help me to solve this problem, Thanks a lot :-)
P/S: By the way, I didn't see folder VASPQ after installing and configuring Now SMS/MMS. Do I need anything else? | |||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4035 Registered: 10-2002 |
Hi, Do you mean that you are trying to send (not receive) an MMS message? Based upon your log, I think this is what you are trying to do. The HTTP request format that you are using needs to go through the SMS gateway (which will then interface with the MMSC to send the message). So you need to have the SMS gateway service active, and you need to post to that service's HTTP port instead of the MMSC HTTP port. That said, there still may be some confusion. If you submit a message in this way, it will NOT arrive in the MMS-IN directory. The MMS-IN directory contains received messages, but you are using an interface that is used for sending messages. The VASPQ directory is created automatically when it is needed. It is used when there are "MMSC Routing" connections defined, and NowSMS has a message that it needs to route via one of these connections. -bn | |||||
| nguyen the vinh New member Username: Vinhnguyen Post Number: 2 Registered: 02-2005 |
Hi, Thanks for your quick reply. Sorry for my late reply because I took some vacations for the Lunar New year. My mobile account cannot use MMS service, so how can I test receive function? How can simulate this situation? I think I can post message to the gateway with ip 127.0.0.1:8080, for example. Please show me the way. Thanks a lot. Regards, | |||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4065 Registered: 10-2002 |
I'm not sure how you could do this. Perhaps you could define an MMSC VASP account that routes all received messages to the "MMS-IN Directory". Then define an "MMSC Routing" definition that is a loopback connection of MM7 back to the VASP account (e.g., http://127.0.0.1:8080/mm7/vasp=password where "vasp" is the account named defined under "MMSC VASP"). It's a bit of an odd configuration, but that might do some of what you want. -bn | |||||
| nguyen the vinh New member Username: Vinhnguyen Post Number: 3 Registered: 02-2005 |
Hi, Thanks for your responses. I tried as you told many times, there was a good thing: the MMSCDebug.log didn't generate any errors anymore. But in the MMS-IN directory, I didn't see any mms messages. Here are steps done: 1. I configured MMSCVASP account, with name "vasp", password is "password", vasp sender address "84908496175", mmsc routing type is "Receive in MMS-IN directory". 2. In the MMSC Outbound Routing tab, I configured account name "loopback", sender address "84908496175", route message type is MM7, server address is "http://127.0.0.1:8080/mm7/vasp=password" (loopback address), login name = vasp, password=password, connection type is "To MMSC (use submitReq)" (and others, I also tried). In the Routing Rule, I selected default route is "loopback" (outbound routing named above). That's all. I used web interface to submit the mms message. Here is debug log:
Besides, In the MMSCData folder, with .ini file has just been created together with mms message, I saw the status [Recipient Status] 84908496175=Pending I don't know what it means. Did I do anything wrong with steps above. Pls, help me. Thanks a lot, -vn | |||||
| Karim Ibrahim Mohamed Unregistered guest |
Dear All, i tried to using NowSMS gateway to send my requests via MM7 to submitted it. for example the following request: http://kimo:kimo@213.178.229.90:8080/mm7?PhoneNumber=%2B96393607701&MMSFile=http ://213.178.229.90:8080/Image/Test.gif where 'kimo' is the account name and password for MMSC VASP configuration and '8080' is the http port in MMSC dialoge. be sure that i have configured my MMSC routing to the MM7 server, after all i have received a return web page error as following: <?xml version="1.0" ?> - <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> - <env:Header> <mm7:TransactionID xmlns:mm7="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-M M7-1-2" env:mustUnderstand="1">unknown</mm7:TransactionID> </env:Header> - <env:Body> - <RSErrorRsp xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1 -2"> <MM7Version>5.3.0</MM7Version> - <Status> <StatusCode>4003</StatusCode> <StatusText>Unsupported Operation</StatusText> <Details>HTTP GET not supported on MM7 interface</Details> </Status> </RSErrorRsp> </env:Body> </env:Envelope> please check the matter and give me then your opinion. Thanks in advance. | |||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4279 Registered: 10-2002 |
In the above example, you're mixing interfaces. When you specify "/mm7" in the URL request, this indicates that you are submitting a message in MM7 format. However, your submission is not in MM7 format ... it is in the NowSMS proprietary URL format, except that you've added "/mm7" to it for some reason. Take the "/mm7" out of the URL request. And change the port to be the "port number for web interface" instead of the MMSC port number. Of course, before issuing any of these types of direct URL requests, I would suggest that you confirm that the MMS sending is working properly by submitting messages through the web menu interface. -bn | |||||
| Karim Ibrahim Mohamed Unregistered guest |
Dear All, In the first i must thanks any one answer my questions. regarding my first question and your answer, my task here that i want use the NowSMS Gateway to submite any MMS message i send to it by routing this request(MMS message)to MMSC with MM7 protocol so that i mention '/MM7' in my request as i reads the manwal for the NowSMS Gateway, Now i think that i have wrong understanding for the request formula that i will use and i need your help to do this and very thanks for replaying me. | |||||
| Eng.Karim Ibrahim Mohamed Unregistered guest |
Dear all, i hope you fine and with good health, please i need your help and please any support answer me. as i asked before, i was tried to send MMS message from my NowSMS gateway machine to MMSC server(MM7) to be submitted there and my HTTP request examples as following: http://kimsh:kimo@213.178.229.90:8800?PhoneNumber=%2B96393607701&MMSFile=http://213.178.229.90:8080/Tones/1000.mid http://kimsh:kimo@213.178.229.90:8800?PhoneNumber=%2B96393607701&MMSFile=http://213.178.229.90:8080/Image/1982.gif where 'Kimsh' is SMS User Account in the NowSMS gateway and 'kimo' is the password for it, '213.178.229.90' is the Ip of my NowSMS gateway machine, '8800' is the port number in the web dialog and '8080' is the port number in the MMSC dialog. After posting this request in the internet explorer the return page is 'Message submitted' but there's nothing has been received there in the the MMSC(MM7) server so i need you tell me what can i do again and if there's missing or wrong thing in my request, Also please find the attached files 'MMSCDEBUG.LOG' and 'MMSC-20050509.LOG' which returned after sending my request. please replay me as fast as you can. Best Regards, Eng.Karim Ibrahim Mohamed.
| |||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4490 Registered: 10-2002 |
Hi, We are attempting to submit the message via MM7 to the server that you have specified: http://172.20.5.3/mm7/mm7tomms.sh However, we are not getting any response back from that server. I can see that the server accepts the HTTP connection. But when we perform the post of the MM7 data, the server drops the connection after about 10 seconds. There is no error code returned. I would expect at least some sort of HTTP formatted reply ... or more helpful would be if it actually returned some MM7 XML in the response. At this point, I think you have to ask your provider what errors they are seeing in their logs. -bn | |||||
MMSCDEBUG.LOG
