| Integration of NowMMS with nokia MMSC |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through April 12, 2010 ⬆ |
◄ ► |
| Author | Message | |||
| josgeorge New member Username: Jos Post Number: 4 Registered: 08-2009 |
Hi , Is it possible to use Now-mms tool to directly connect to nokia mmsc to retreive mms useing EAif interface ie MO-AT senario . if it possible what all are the configurations i must do from now mms side Thanks Jos | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1819 Registered: 08-2008 |
Hi Jos, Yes. To retrieve MMS messages from a Nokia MMSC using EAIF, this is what you must configure on the NowSMS side. Define a new account under "MMSC VASP". The "Account Name" and "Password" will be part of a URL that you give to your provider. Most of the other settings can be left at their defaults. For "MMSC Routing", initially you will want to set this to "Receive to MMS-IN Directory". This means that NowSMS is going to process messages that come in via this connection and save them to the MMS-IN directory when they are received. Once you see that is working, you can go back in and configure a different way for these messages to be processed, depending on how you plan to process them. You need to tell your operator the IP address or host name of your NowSMS server, because they need to configure their MMSC to deliver messages to you. Both EAIF and MM7 work differently than what you might be used to with SMPP in SMS environments. With both EAIF and MM7 the operator must initiate a connection to your server in order to deliver MMS messages. You need to give your operator a URL that they use for delivering MMS messages to your system. This URL will be of the following format: http://ip.address:port/eaif/account=password ip.address is the IP address of your NowSMS system. Port number is the HTTP port configured for the MMSC component of NowSMS. account and password are the details for the "MMSC VASP" account that you created earlier. Once you are receiving MMS messages, you can refer to the following link for some additional options on how to process received MMS messages: http://www.nowsms.com/documentation/ProductDocumentation/2_way_mms_support.htm A PHP script interface for processing received MMS messages is described here: http://www.nowsms.com/download/php2waymms.pdf -- Des NowSMS Support | |||
| josgeorge New member Username: Jos Post Number: 5 Registered: 08-2009 |
Hi Des , Actually i tried the same as you instructed but still i am got able to retrive mms from nokia Plese find the logs main: preferred sender = +1111,jos MoveMMSCUsersFiles: Thread started MMSCMigrateUserDBThread: Thread started MoveMMSCUsersFiles: Thread ended ThreadListenForConnections: Thread started ThreadListenSMTPIn: Thread started MMSCMigrateUserDBThread: Thread ended ThreadListenForConnections: Now MMSC server started on port number 40030 ThreadListenSMTPIn: Now MMSC SMTP server started on port number 25 main: Now SMS/MMS Gateway v2010.02.09 service started. Using web port 40030. U sing SMTP port 25. ThreadListenPOP3In: Thread started ThreadRouteSMTPOut: Thread started ThreadRouteSMTPOut: Thread started ThreadRouteSMTPIn: Thread started ThreadRouteSMTPOut: MMSCOUT ThreadRouteSMTPOut: MMSCACK ThreadStartVASPQ: Thread started ThreadProcessIPNotifyQ: Thread started ThreadRecombineSARMessages: Thread started main: 58 Days remaining in trial version ThreadProcessVASPQ: Thread started ThreadProcessVASPQ: C:\Program Files\NowSMS\VASPOUT\jos\VASP.INI InternalProcessConnection: Thread started ThreadProcessConnection: Processing connection from 10.142.202.219... ThreadProcessConnection: C:\Program Files\NowSMS\MMSCDATA\eaif/jos=jos.INI ThreadProcessConnection: File not found ThreadProcessConnection: C:\Program Files\NowSMS\MMSCDATA\eaif/jos=jos ThreadProcessConnection: HTTP/1.1 404 Not Found Content-Length: 0 Connection: Keep-Alive 2010-02-20 20:47:50,MMSRETRIEVE,10.142.202.219,,,eaif/jos=jos,FAILED | |||
| josgeorge New member Username: Jos Post Number: 6 Registered: 08-2009 |
HI Des, I had tried configuring now mms tool with Nokia MMSC and found its not working when i am giving restart to EAIF process in MMSC side i can see following threads in nowmms tool where 10.71.4.37 hreadProcessConnection: Processing connection from 10.71.4.37... hreadProcessConnection: Processing Complete nternalProcessConnection: Thread ended i tried sending AT mms to a short code +1111 but its not going i can see in mmsc database in waiting fetch status configurations i had done from mmsc side is 1)ip address of nowmms 2)http port number in given in MMSC page of Now mms tool 3)url= /eaif this is when i am giveing in nowmms tool MMSC vASP page ip of my mms as Account Name and other options keep as default or url=/eaif/jos=jos when i am giveing VASPID and password option as jos . 4) Also in MMSC EAIF configuration page i have provision to define VASPID and VAS ID i had tried defineing jos here as VASPID and also tried with out defineing VASPID all the tries where unscuccessful While during all the tesing i kept receive to MMS-IN directory in VASP account in now mms tool Can you please suggest accordingly Thanks jos | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1826 Registered: 08-2008 |
Hi Jos, It looks like someone is trying to issue an HTTP GET request for /EAIF/jos=jos That will result in a file not found error response. If an EAIF message were being posted by the MMSC it would be an HTTP POST request. I am also confused, because the MMSCDEBUG.LOG should show a hex dump of the inbound request. However, I do not see that in your log extract above. Is there other data in the MMSCDEBUG.LOG that shows what data is being received? It should appear right after "ThreadProcessConnection: Processing connection from 10.142.202.219..." Also, just FYI ... VASPID and VASID parameters will be ignored. -- Des NowSMS Support | |||
| josgeorge New member Username: Jos Post Number: 7 Registered: 08-2009 |
Actually its was my inferance on sunday ... i had posted you my inferance after that can you please check that Posted on Monday, February 22, 2010 - 08:23 am: | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1833 Registered: 08-2008 |
Sorry if I confused you. I still want to see the MMSCDEBUG.LOG, which should show a hex dump of the inbound request. URL /EAIF/jos=jos is correct. VASPID and VASID parameters will be ignored. The error that you see in MMSCDEBUG.LOG with file not found "EAIF/jos=jos" is because someone is sending an HTTP GET request. EAIF uses HTTP POST. I don't think any request from the MMSC is ever going to NowSMS. But I want to see more details from the MMSCDEBUG.LOG to understand what this mysterious "GET" request is. My guess at this point is that the MMSC does not know to route any MMS messages to you. Are you sure the MMSC is configured to route messages for that short code to this route? -- Des NowSMS Support | |||
| josgeorge New member Username: Jos Post Number: 8 Registered: 08-2009 |
Hi Des Thank you very much for your support Now i am able to receive MMS . Problem was i did not define routeing in kernal file of nokia mmsc . Once its defined message starts flowing to the tool Warm Regards Jos  | |||
