| Different MMS-IN directory for each VASP account?? |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through October 19, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Scott Grimmett New member Username: Scottgr Post Number: 1 Registered: 03-2007 |
A few years ago there was a post where someone was asking to put messages received from each VASP Account into a different directory rather than putting all messages in the MMS-IN directory. The response was that you would consider it for a future version. Was this feature added to v2006? Thanks | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7047 Registered: 10-2002 |
Hi Scott, No. We have added a variety of other options, but not that. I've just done a quick look, and it looks like the implementation would be quite simple ... if we did an INI file entry where when it was enabled, each VASP (or modem) got their own subdirectory under MMS-IN. Would that be sufficient for what you are looking for? -bn | |||
| Scott Grimmett New member Username: Scottgr Post Number: 2 Registered: 03-2007 |
Bryce, Last night I was looking through the discussion board and found a feature that is already in NOW that will address my need without creating seperate directories. I found the ReceiveMMSCallback=xxxxxx property in the SMSGW.INI file. I can use this property to send the message to any directory and and more. I can use this property to start an application which can read the header file and based on the information in the header do any processing I need to the message. The nice thing about this property is that I only need to create one VASP account. The one issue I am having is that when the VASP account Allow Sender Address Override is checked, the sender address does not come through. I only get the VASP Sender Address. My work around is to just dial a different phone number for each user and look for the TO address rather than the FROM address. Is there something I may be doing wrong that doesn't allow the sender address to pass through? Thanks, Scott | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7064 Registered: 10-2002 |
Hi Scott, How are the VASP messages being submitted? Is it possible that they are not setting a sender address property? If they are mobile phones, then this would be the case, because the phone expects the MMSC to insert its phone number as the sender (and how the MMSC determines this phone number is outside the scope of the MMS definition itself, the MMSC needs to use other network components). In this case, what you would need to do is define separate VASP accounts for each client, and use the "Force Sender Address" property to apply a sender address. If what I'm describing doesn't match your configuration, then please explain your setup in some more detail so that I can understand how the VASPs are submitting messages. -bn | |||
| Scott Grimmett New member Username: Scottgr Post Number: 3 Registered: 03-2007 |
Hello Bryce, The message is being sent from a phone through an MMSC to NOW. The MMSC is suppose to be inserting a sender address to the URL message. Each phone goes through its own MMSC so I have defined a different sender address in each MMSC. It may be that the MMSCs are not adding the address properly or not at all. Is there a log file in NOW that would show me what NOW is receiving? Thanks, Scott | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7077 Registered: 10-2002 |
Hi Scott, Let's look at the MMSCDEBUG.LOG. (Enable it via the checkbox on the "Serial #" tab.) But since the configuration can be a bit complicated, let me also make some suggestions of settings that you should verify. It sounds like the phone clients are submitting message using VASP accounts, instead of standard user accounts. (This is a good approach when you want the phones to always submit directly to an application.) In this case, the URL on the phone would include /mm1/account=password, where "account" is an account defined in the "MMSC VASP" list. Because the phone does not specify a sender address when it submits, you want to fill in an appropriate sender value for the "VASP Sender Address" field. (I would also recommend UNchecking "Allow Sender Address Override" ... although this setting should not be a factor.) If instead, the phones were submitting via standard "MMSC Users" accounts, the sender phone number would be specified in the "Phone Number" parameter of the account definition. The submission URL would be /user=password ... where "User" is either the "Phone Number" or "Alias" paremter for the "MMSC Users" definition. In your case, it sounds like you are just routing the messages to MMS-IN, but if you were routing them to an MM7 connection, for example ... the "MMSC Routing" definition would need to have "Allow Sender Address Override" checked. Otherwise the "Default Sender Address" (which might be blank) would always be applied for messages routed via that connection. If reviewing these settings doesn't resolve your issue, let's take a look at the MMSCDEBUG.LOG which shows a message being submitted. -bn | |||
| Scott Grimmett New member Username: Scottgr Post Number: 4 Registered: 03-2007 |
Hello Bryce, All of my phone clients are submitting messages using a VASP account. Every phone is configured with the same VASP account and the URL includes /mm1/aaa=ddd. I have one VASP account in NOW which routes all messages to the MMS-IN directory. Once the message is saved in the MMS-IN directory, I use the ReceiveMMSCallback to read the header file and determine which phone sent the message. I want to use the FROM field in the header file to determine which phone sent the message. Since I am using only one VASP account, I need to check Allow Sender Address Override so that I can get the sender address that came from the phone. Since all phones have the same username and password, each phone message is routed through a different SMSC. The SMSC adds a unique Sender=xx to the URL from the phone. Here is an example of what the SMSC adds: PhoneNumber=@@NUMBER@@&Data=@@DATA@@&UDH=@@UDH@@&PID=@@PIDHEX@@&DCS=@@DCSHEX@@&S ender=xx&Binary=1. After passing through the SMSC, each phone URL has a different Sender address. Each SMSC is connected to NOW and routes the URL to NOW VASP account. I want NOW to pass that Sender address from the SMSC to the FROM address in the header file. I could then read the header and determine which phone sent the message. It is necessary for me to keep all the phones configured the same so I can not define a unique username and password for each phone. Thanks, Scott | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7092 Registered: 10-2002 |
Hi Scott, The problem is that the sending phone doesn't specify a sender address. It would seem logical that it does...but unfortunately it does not. The way that the MMSC determines the phone number of the sender is actually outside of the scope of MMS protocol. Basically there are only 2 ways for the MMSC to determine this sender address: 1.) Based upon the submission URL 2.) Via trusted components of the operator network Unless you are a mobile operator, #2 isn't feasible. You can see how we do this in a mobile operator environment in the description at http://www.nowsms.com/support/bulletins/tb-nowsms-002.htm. Basically the MMSC expects to receive the sender MSISDN via an HTTP header. This HTTP header is usually generated by the WAP proxy ... if this WAP proxy is ours, then we receive the MSISDN info via a RADIUS accounting feed from the access server (GGSN). (Basically you're not going to get this RADIUS accounting feed unless you have your own APN.) That said, a few mobile operators do send the MSISDN info in an HTTP header ... but most don't for privacy reasons. (The MMSCDEBUG.LOG will show you the raw HTTP POST submission coming in from the client.) So that leaves us with identification based upon the submission URL. -bn | |||
