| MMS - 'From' address in m-send-req |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 28, 2006 ⬆ |
◄ ► |
| Author | Message | |||||
| Ian Mac New member Username: Imcgraw Post Number: 8 Registered: 01-2006 |
Hi there, We are currently trying to make use of NowSMS MMSC functionality which we hope to recommend to our customers to use with our BTS/MSC platform. We have a modded SIM in a GPRS test phone which we know can connect to a local host and retrieve a web page. The mod was simply to add the phone's provisioned MSISDN number to it's "Own Numbers" SIM record. We have set up NowSMS on a PC on our network along with our BTS/MSC and test phone. We have also set up Ethereal to monitor the MMS protocol data to/from the phone. At the moment if we attempt to send an MMS message (text based) to NowSMS, Ethereal displays the incoming m-send-req PDU from the phone. The returned m-send-conf from NowSMS contains error code 'Sending address unresolved'. We can see that the m-send-req PDU contains 'From: <insert address>' i.e. there is no From address being supplied. For this reason is there anyway we can use NowSMS without having to set up a validated MMS user for every provisioned subscriber on our network? Thanks, Ian. | |||||
| Ian Mac New member Username: Imcgraw Post Number: 9 Registered: 01-2006 |
Hi please find attached the debug from a MMS plain text send. The log does not contain any indication that the message failed - Ethereal would suggest otherwise.
| |||||
| Ian Mac New member Username: Imcgraw Post Number: 10 Registered: 01-2006 |
MMSC log yeilds :- 2006-03-27 13:29:02,MMSIN,192.168.2.240,,,User Not Defined,FAILED The handset MMSC URL is set to :- http://192.168.1.203:80/2410=password NowSMS has the follow user setup:- Phone Number: 2410 Alias: 2410 Password: password | |||||
| Ian Mac New member Username: Imcgraw Post Number: 11 Registered: 01-2006 |
Update: | |||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5735 Registered: 10-2002 |
Hi Ian, Sorry for the delay. What you are seeing is normal. Well, sort of. Let me explain. When an MMS client sends a message, there is nowhere in the MMS protocol for the client to authenticate (or otherwise identify itself) to the MMSC. Basically it is expected that the MMSC will somehow use other network elements to identify the client. There are two ways that we can facilitate this identification. 1.) Manually provision user accounts on the MMSC, and use a unique MMSC URL on the handset to allow the handset to identify itself to the MMSC. This is basically the process that you describe above. You define an account in the "MMSC Users" list, and then you append /username=password to the MMSC URL. Based upon the debug log and Ethereal log that you attached above, the client is not appending this information to its MMSC URL. I'd suggest double checking the configuration on the phone. (Note that in some versions of NowSMS, if there was only one user defined in the "MMSC Users" list, we would still return an error even if the user was identified properly in the MMSC URL. I believe this problem has long since been fixed, but this is one of those problems which didn't occur in every configuration and was very difficult for us to identify, so I mention it just in case there are still configurations where the problem remains. In this case, the solution was to define more than 1 user in the "MMSC Users" list. I do not believe you are experiencing this problem at present.) 2.) Obviously, the above is not practical for a mobile operator configuration. So for a mobile operator configuration, the MMSC needs to have a way of identifying the user automatically. The way that we do this is described in the following document: http://www.nowsms.com/support/bulletins/tb-nowsms-002.htm The short of it is that the MMSC expects another network element to insert an HTTP header that identifies the device. The MMSC parses identification information from this header. This HTTP header is normally inserted by a proxy rather than by the MMSC itself, because the proxy provides this same service for other applications that require user identification. Our NowWAP proxy receives user identification from the network via RADIUS accounting. More details can be found in the above referenced link. -bn | |||||
| Ian Mac New member Username: Imcgraw Post Number: 12 Registered: 01-2006 |
Hi Bryce, thanks for the information (spot on as usual). Yes I found I was setting up the phone incorrectly, once I appended the alias and password to the URL of the MMSC then things sprang into life. I have some DCS issues still to sort out with the MMS indication on our SMSC but I expect it will all work well once that is done. Best regards, Ian. | |||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5756 Registered: 10-2002 |
Hi Ian, The most common DCS issue is that we default to using F5, with is a GSM specific value. You can configure us to use 4 (generic binary) instead by editing SMSGW.INI, and under the [SMSGW] header, adding BinaryDCS=4. (We also automatically use 4 when WDP Adaptation is enabled for CDMA environments.) -bn | |||||
| Ian Mac New member Username: Imcgraw Post Number: 13 Registered: 01-2006 |
Thanks for that, 0xF5 is the one we default to too so we'll stick with that for now. I am sure CDMA will not be too far off though. I can therefore confirm that NowSMS works well with Zynetix equipment. We already recommend NowSMS to our customers for SMPP, so can now extend this to MMS too. | |||||
MMS LOG
