| How can I configure NOW SMS to do both : Receive mms in MMS-IN dire... |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 06, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| Deepesh Aggarwal New member Username: Deepesha Post Number: 1 Registered: 02-2005 |
Hi Bryce, I have few queries about NOW SMS. Q. Is there any way to configure the directory to receive mms? From MMSC VASP account looks like it is fixed as MMS-IN. Q. Is there any way to configure NOW SMS in such a manner that I can receive the MMS in MMS-IN directory as well as perform standard MMS delivery? Seems that we can configure only one at a time. Well the reason why I am asking for such configurations is that for my application I need to get an MMS Notification from NOW SMS and as well as I need the decomposed MMS ( smil , image, audio..) to verify them. If I configure it for "statdard MMS delivery" then I would be able to get .mms file from MMSCDATA but I also need smil,image and other components files the way I get in MMS-IN directory.(I hope I have not confused you..) Or do you know some command base utility like MMSCOMP which can decompose .mms message in to its components.? I would appreciate a quick response. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4274 Registered: 10-2002 |
Hi Deepesh, 1.) If you configure the directory setting in the "2-way" tab then that should apply. 2.) Hmm ... I'm not sure that this would work, but here's my idea ... Send your messages to two recipients. Configure the VASP that you are submitting through for standard MMS delivery. (Or connect through a regular "MMSC Users" account, unless there is a reason you need to use a VASP.) One recipient that you would send to would be a standard MMS recipient with a real phone number. But the other would be a virtual phone number, something like 999999999, which you would intercept. To perform this interception, configure an "MMSC Routing" definition. Make sure to enable "Allow Sender Address Override". "Route messages to..." should include a mask to catch your virtual phone number, such as "9999*,+9999*". I'd suggest using EAIF as the protocol ... and you're going to connect to a VASP account on your own server. So the server address would be "127.0.0.1:mmscport/eaif", and specify the login name and password for the VASP (or include them in the URL). Define the "MMSC VASP" account, and configure it to route received messages to the MMS-IN directory. I haven't tried this approach myself, but I don't see why it would not work ... -bn | |||
| Deepesh Aggarwal New member Username: Deepesha Post Number: 2 Registered: 02-2005 |
Hi Bryce, Thanks for your response. 1.) Is there any way to figure out the unique name of the directory NOW SMS creates to receive a particular MMS Message assuming I know the time stamp a MMS has been submitted to NOW SMS through MM1 interface ?( I know its too much to ask for...) 2.) Well Bryce, I cannot impose that restriction of sending it to two recipients as it is coming directly from mobile through MM1 interface. Do we have any other choice in this regard..? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4360 Registered: 10-2002 |
1.) No. I suppose you might be able to find it from the log file, which has a timestamp, but I'm not certain. 2.) Hmm ... I can't think of any solution. But it would be relatively easy for us to add an Auto-BCC option, and then you could route the copy through the path that I mention above. We've been asked for this before because of lawful interception requirements in many countries, but we've been somewhat reluctant. If you think that would solve your problem, send an e-mail to nowsms@now.co.uk put "Attention: Bryce" in the subject line, and I'll see what we can do. -bn | |||
