Cool I appreciate it. I've got the vaspid, vasid, url, short code, and xml schema. username and password is not required. I looked in the MM7MessageSender.. I only see the vaspid to edit.. I played with the send.bat in the standalone folder and modified the url there.. I keep getting C:\vaspsdk\samples\standalone>send [Start Thread[Thread-0,5,main] Iteration 0] APIException submitting message: username/password not supplied(ClientError:2000 ) [End Thread[Thread-0,5,main] Iteration 0] Finished 1 threads each with 1 iterations 0 iterations succeeded Messages per sec: 7.0921984
something is expecting a username/password but one's not required. Ideas? On Fri, May 16, 2008 at 12:25 PM, Rich <[EMAIL PROTECTED]> wrote: >> I just spoke with my contact.. and they mention >> >> MM7 traffic via a VASP >> >> This is all greek to me.. will an SMS Aggregator still work here? Or >> will I need to go the openwave route? >> > > Ok, I'm assuming you spoke with your contact at your SMS aggregator and this > is what they told you. That said, here are the basic definitions you will > need to remember to find your way out of acronym hell: > > SMSC - Short Message Service Center (your SMS Aggregator) > MMSC - Multimedia Message Service Center (usually provided by your > aggregator) > MM7 - This is the delivery protocol for the messages > VASP - Value Added Service Provider - you ;) > ShortCode - the (generally) 6 digit number you were given for your SMS/MMS > traffic (phone number) > > So they are saying that you send them MMS messages via MM7 ;) > > It sounds like you are in the same boat I was, so I hope the following > helps: > > The first place I started was with the Openwave SDK and its example files. > The hardest part there is configuring the correct properties; once > configured properly, you can send to your MMSC using the sample files (they > do need to be modified slightly). I strongly suggest running them from a > shell as you can see encoding for MM7 and will start to get a "feel" for the > protocol. I would suggest using the 'MM7MessageSender' as this is the most > robust example and shows many of the things you will need to work with. You > will need to alter a few parameters in the source code for it to > authenticate successfully (namely vaspid, vasid, & sourceAddress - see > below). > > There are a few details you will want to get from the MMSC in order to be > able to connect to them successfully: > > mmscUrl = the url to connect to > Username = self explanitory > Password = self explanitory > MM7 version = what version of the MM7 protocol are they using > (REL-5-MM7-1-0, REL-5-MM7-1-1, REL-5-MM7-1-2 or REL-5-MM7-1-3) > Vaspid = the VASP id provided by the aggregator, generally required for > authorizaion > Vasid = the VAS id provided by the aggregator, generally required for > authorizaion > Sender address = your short code (this was required by our MMSC to deliver > YMMV) > > Once you have these details you can use the MM7MessageSender to deliver > messages via the example applications. > > From here, your next steps are going to vary depending on the needs of your > application. We needed a high volume, scalable solution, so we created > supporting java classes that delegated to the SDK for delivery and exposed > one java 'service' class to CF to initiate the send. > > Let me know if I can be of further help. > > p.s. - It would probably save you endless hours of development if you could > find a MMSC that offered a RESTful web service for delivery so you could use > Roberts solution. > > HTH, > Rich Kroll > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;192386516;25150098;k Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:305505 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
