| Send MMS via Agilent 8960 |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through July 28, 2014 ⬆ |
◄ ► |
| Author | Message | |||
| Julien Reynaud New member Username: Julien_r Post Number: 1 Registered: 12-2013 |
Hello  I have an android phone connected to an Agilent 8960 with HTTP Web input interface enabled. Phone is registered to network and PDP Context active. I configured MMSC user on NowSMS (MMSC Tab) Then use this user/password + NowSMS address and port (8080) as APN on phone. I configured SMSC Connection (SMSC tab) to dialog with the Agilent via HTTP Interface: Left all by default and http connection look ok. (Also define this route by default for a specific phone number) I send a MMS sending request via a PC connected on same network and the "JAR" method. From jar to NowSMS it should be OK because receive Response Code->OK (In addition on log SMSOUT log the SMS should be well sent via good route, and on MMSC logs look ok because same id than JAR feedback.) But the MMS is never received on the phone. Anyone has an idea ?  | |||
| Julien Reynaud New member Username: Julien_r Post Number: 2 Registered: 12-2013 |
Hello, If found what I miss here: http://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_sms_http_mt.html Then the template used for Agilent 8960: Text: /sms/send/?PhoneNumber=@@PhoneNumber@@&TEXT=@@Text@@&SENDER=@@Sender@@ Binary: /sms/send/?PhoneNumber=@@PhoneNumber@@&DATA=@@Data@@&UDH=@@UDH@@&PID=@@PID@@&DCS =@@DCSdecimal@@&SENDER=@@Sender@@ (Does not include TEXT on binary otherwise Agilent will say "TEXT parameter out of range" and for DCS need decimal value) When sending SMS/MMS with Now SMS web interface its OK. We look for the Web Interface -> MMSC request then we are able to fix what is missing on the jar sample. (Look on SMSDEBUG.log) | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8076 Registered: 10-2002 |
Hi, Agilent posted some info on their expected templates here: http://support.nowsms.com/discus/messages/1/5614.html What you have is close ... they ignore the PhoneNumber= parameter, but NowSMS requires it in the template, so that is ok. I expect your template will work, just change @@PID@@ to @@PIDdecimal@@ for better accuracy (MMS messages do not use PID, so this is not required for MMS to work). I believe there are more complex requirements if you are using a CDMA2000/3GPP2 environment. -bn | |||
| Julien Reynaud New member Username: Julien_r Post Number: 3 Registered: 12-2013 |
Thank you for these useful information. We "now"  are able to send MMS through Agilent 8960 from Now SMS web interface AND our jar but we update our jar to send the missing parameters on the request to SMSC. As: (as the sample) PhoneNumber= &MMSFrom= &MMSSubject= &MMSText= &MMSFile= Added: &MMSBCC=No &MMSDeliveryReport=No &MMSReadReport=No &MMSPriority=Normal &MMSMessageClass=Personal &MMSForwardLock=No &DRMRestrict=No &Submit=Submit& <- for this one I would want to know the purpose of this parameter ? Optional: &DRMRestrictTextXML= &DRMConstraintCount= &DRMConstraintStart= &DRMConstraintEnd= &DRMConstraintInterval= &MMSHEADERS= In addition we have to install the latest version (as trial but we have old install license), is it possible to transfer the license from the old version to the latest one ? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4778 Registered: 08-2008 |
Hi Julien, It is best to talk with our sales department about licensing issues. In particular, if the old license is an Agilent OEM, there may be restrictions. The office is closed for the weekend now, but contact info can be found here: http://www.nowsms.com/contact
The server does not use this parameter. The web form may have a submit button, but that is for the convenience of creating the form and serves no practical purpose. -- Des NowSMS Support | |||
