| Don't receive the originator number phone in #B Terminal |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 09, 2011 ⬆ |
◄ ► |
| Author | Message | |||||
| Fernando Nahuel Marti New member Username: Fmarti Post Number: 1 Registered: 05-2011 |
Hi, In the MMS receiving, the originator phone number is received on the platform but , in the #B terminal, it is replaced by the name of the VASP Acount. The connection between MMSC (different operators) is through SMTP (MM4) protocol. I see this link: “http://www.nowsms.com/cgi-bin/discus/discus.cgi?pg=prev&topic=485&page=41553” but I do not have similar connection because in our network we do not have GPRS Modem’s. Below, I send you the logs of the platform: [MMSC.INI] WebPort=80 SMTPPort=25 RelayHost= HostName=172.31.31.131 DomainName=mms.nuestro.com.ar SMTPRequireAuth=No EnableDeliveryNotification=No ConvertImages=Yes ConvertScaleToScreen=Yes SMSEMail=No SMSDomainName= SMSPerEMail=1 NotifyRetryDelay=15 DataRetainDays=1 Debug=Yes [Outbound MMS Routing] Fecosur=+542255570484,2255570484 Personal I=+541131089895,1131089895 Log file: 2011-05-16 18:26:20,MMSIN,172.31.31.25,VASP:172.31.31.25,+542255570485,20110516/18/BCFD472E ,SAR-+542255570485-aa-2-1.req,221240 2011-05-16 18:26:20,MMSIN,172.31.31.25,VASP:172.31.31.25,+542255570485,20110516/18/BCFD472E ,SAR-+542255570485-aa-2-2.req,221240 2011-05-16 18:27:10,MMSRETRIEVE,172.21.8.7,VASP:172.31.31.25,+542255570485,20110516/18/BCFD 472E.MMS,OK,221196 [SMS] SubmittedBy= SubmitUser=localsystem-mmsc PhoneNumber=+542255570485 Data=2F32303131303531372F31322F30463342433430422E4D4D533F69643D25326235343232353 535373034383500 UDH=0B05040B8423F00003500202 pid=00 dcs=F5 Binary=1 [MMSCDEBUG.INI] 10:55:23:984 [337] ThreadProcessConnection: Packet Length is 600 bytes 10:55:23:984 [337] ThreadProcessConnection: 47 45 54 20 2F 32 30 31 31 30 35 31 33 2F 31 30 GET /20110513/10 10:55:23:984 [337] ThreadProcessConnection: 2F 36 38 44 41 44 35 46 30 2E 4D 4D 53 3F 69 64 /68DAD5F0.MMS?id 10:55:23:984 [337] ThreadProcessConnection: 3D 25 32 62 35 34 32 32 35 35 35 37 30 34 38 35 =%2b542255570485 10:55:23:984 [337] ThreadProcessConnection: 20 48 54 54 50 2F 31 2E 30 0D 0A 43 6F 6E 6E 65 HTTP/1.0 Conne 10:55:23:984 [337] ThreadProcessConnection: 63 74 69 6F 6E 3A 20 4B 65 65 70 2D 41 6C 69 76 ction: Keep-Aliv 10:55:23:984 [337] ThreadProcessConnection: 65 0D 0A 55 73 65 72 2D 41 67 65 6E 74 3A 20 4E e User-Agent: N 10:55:23:984 [337] ThreadProcessConnection: 6F 6B 69 61 35 38 30 30 64 2D 31 62 2F 35 31 2E okia5800d-1b/51. 10:55:23:984 [337] ThreadProcessConnection: 32 2E 30 30 37 3B 20 53 65 72 69 65 73 36 30 2F 2.007; Series60/ 10:55:23:984 [337] ThreadProcessConnection: 35 2E 30 20 50 72 6F 66 69 6C 65 20 4D 49 44 50 5.0 Profile MIDP 10:55:23:984 [337] ThreadProcessConnection: 32 2E 31 20 43 6F 6E 66 69 67 75 72 61 74 69 6F 2.1 Configuratio 10:55:23:984 [337] ThreadProcessConnection: 6E 2F 43 4C 44 43 2D 31 2E 31 20 33 67 70 70 2D n/CLDC-1.1 3gpp- 10:55:23:984 [337] ThreadProcessConnection: 67 62 61 0D 0A 48 6F 73 74 3A 20 31 37 32 2E 32 gba Host: 172.2 10:55:23:984 [337] ThreadProcessConnection: 35 2E 37 2E 31 39 31 0D 0A 41 63 63 65 70 74 3A 5.7.191 Accept: 10:55:23:984 [337] ThreadProcessConnection: 20 2A 2F 2A 2C 20 61 70 70 6C 69 63 61 74 69 6F */*, applicatio 10:55:23:984 [337] ThreadProcessConnection: 6E 2F 76 6E 64 2E 77 61 70 2E 6D 6D 73 2D 6D 65 n/vnd.wap.mms-me 10:55:23:984 [337] ThreadProcessConnection: 73 73 61 67 65 2C 20 61 70 70 6C 69 63 61 74 69 ssage, applicati 10:55:23:984 [337] ThreadProcessConnection: 6F 6E 2F 76 6E 64 2E 77 61 70 2E 73 69 63 0D 0A on/vnd.wap.sic 10:55:23:984 [337] ThreadProcessConnection: 41 63 63 65 70 74 2D 43 68 61 72 73 65 74 3A 20 Accept-Charset: 10:55:23:984 [337] ThreadProcessConnection: 75 74 66 2D 38 0D 0A 41 63 63 65 70 74 2D 4C 61 utf-8 Accept-La 10:55:23:984 [337] ThreadProcessConnection: 6E 67 75 61 67 65 3A 20 65 6E 0D 0A 78 2D 77 61 nguage: en x-wa 10:55:23:984 [337] ThreadProcessConnection: 70 2D 70 72 6F 66 69 6C 65 3A 20 22 68 74 74 70 p-profile: "http 10:55:23:984 [337] ThreadProcessConnection: 3A 2F 2F 6E 64 73 31 2E 6E 64 73 2E 6E 6F 6B 69 ://nds1.nds.noki 10:55:23:984 [337] ThreadProcessConnection: 61 2E 63 6F 6D 2F 75 61 70 72 6F 66 2F 4E 6F 6B a.com/uaprof/Nok 10:55:23:984 [337] ThreadProcessConnection: 69 61 35 38 30 30 64 2D 31 72 31 30 30 2D 33 47 ia5800d-1r100-3G 10:55:23:984 [337] ThreadProcessConnection: 2E 78 6D 6C 20 22 0D 0A 56 69 61 3A 20 69 6E 66 .xml " Via: inf 10:55:23:984 [337] ThreadProcessConnection: 6F 58 20 57 41 50 20 47 61 74 65 77 61 79 20 56 oX WAP Gateway V 10:55:23:984 [337] ThreadProcessConnection: 33 30 30 52 30 30 31 2C 20 48 75 61 77 65 69 20 300R001, Huawei 10:55:23:984 [337] ThreadProcessConnection: 54 65 63 68 6E 6F 6C 6F 67 69 65 73 0D 0A 58 2D Technologies X- 10:55:23:984 [337] ThreadProcessConnection: 4D 53 49 53 44 4E 3A 20 35 34 32 32 35 35 35 37 MSISDN: 54225557 10:55:23:984 [337] ThreadProcessConnection: 30 34 38 34 0D 0A 78 2D 66 6F 72 77 61 72 64 65 0484 x-forwarde 10:55:23:984 [337] ThreadProcessConnection: 64 2D 66 6F 72 3A 20 31 37 32 2E 32 35 2E 31 39 d-for: 172.25.19 10:55:23:984 [337] ThreadProcessConnection: 35 2E 31 30 0D 0A 78 2D 73 6F 75 72 63 65 2D 69 5.10 x-source-i 10:55:23:984 [337] ThreadProcessConnection: 64 3A 20 67 67 73 6E 5F 62 61 0D 0A 58 2D 4E 6F d: ggsn_ba X-No 10:55:23:984 [337] ThreadProcessConnection: 6B 69 61 2D 4D 75 73 69 63 53 68 6F 70 2D 56 65 kia-MusicShop-Ve 10:55:23:984 [337] ThreadProcessConnection: 72 73 69 6F 6E 3A 20 31 31 2E 31 30 31 34 2E 31 rsion: 11.1014.1 10:55:23:984 [337] ThreadProcessConnection: 35 0D 0A 58 2D 4E 6F 6B 69 61 2D 4D 75 73 69 63 5 X-Nokia-Music 10:55:23:984 [337] ThreadProcessConnection: 53 68 6F 70 2D 42 65 61 72 65 72 3A 20 47 50 52 Shop-Bearer: GPR 10:55:23:984 [337] ThreadProcessConnection: 53 2F 33 47 0D 0A 0D 0A S/3G 10:55:23:984 [337] ThreadProcessConnection: C:\PROGRA~1\NowSMS\MMSCDATA\20110513/10/68DAD5F0.INI 10:55:23:984 [337] ThreadProcessConnection: got recipient match 10:55:23:984 [337] GetLocalUaProfFile: Profile: 10:55:23:984 [337] GetLocalUaProfFile: http://nds1.nds.nokia.com/uaprof/Nokia5800d-1r100-3G.xml 10:55:23:984 [337] RetrieveURL: Retrieving http://nds1.nds.nokia.com/uaprof/Nokia5800d-1r100-3G.xml 10:55:23:984 [337] RetrieveURL: Looking up nds1.nds.nokia.com 10:55:23:984 [337] RetrieveURL: Lookup failed for nds1.nds.nokia.com 10:55:23:984 [337] ThreadProcessConnection: Sending C:\PROGRA~1\NowSMS\MMSCDATA\20110513/10/68DAD5F0.MMS 10:55:23:984 [337] ThreadProcessConnection: HTTP/1.0 200 OK 10:55:23:984 [337] ThreadProcessConnection: Content-Type: application/vnd.wap.mms-message 10:55:23:984 [337] ThreadProcessConnection: Connection: close 10:55:23:984 [337] ThreadProcessConnection: Content-Length: 11425 10:55:23:984 [337] SendMMSFileSetVersion: 1.0 10:55:24:000 [337] ThreadProcessConnection: Processing Complete 10:55:24:000 [337] InternalProcessConnection: Thread ended [MSCDATA] [Message] Sender=VASP:172.31.31.25 Subject=tapa-almafuerte DeliveryNotification=Yes OriginalMessageID=13205050202@mms.personal.com.ar [Recipient Status] +542255570485=Delivered [Recipient MMS Version] +542255570485=1.0 [NotifyID] +542255570485=210 [NotifyPDU] +542255570485=D206226170706C69636174696F6E2F766E642E7761702E6D6D732D6D6573736167 6500AF848C82983543373033353944008D90891B80564153503A3137322E32352E372E372F545950 453D504C4D4E0096746170612D616C6D61667565727465008A808E022CA6880680044DD5134F8368 7474703A2F2F3137322E32352E372E3139312F32303131303531372F31302F35433730333539442E 4D4D533F69643D25326235343232353535373034383500 [NotifySubmitUser] +542255570485=VASP:172.31.31.25 [UndeliveredScan] Scanned=Yes Regards, Fernando | |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3190 Registered: 08-2008 |
Hi Fernando, The following link might help you more as it describes an MM4 interconnection setup: http://www.nowsms.com/mmsc-mm4-interconnection-basics I think I know your problem. Look at the "MMSC VASP" account definition. What you describe will happen if the following settings are defined: "VASP Sender Address" is blank. "Allow Sender Address Override" is NOT checked. You want to change "Allow Sender Address Override" to be checked. -- Des NowSMS Support | |||||
| Fernando Nahuel Marti New member Username: Fmarti Post Number: 2 Registered: 05-2011 |
Hi, "Allow Sender Address Override" is checked and the "VASP Sender Address" has the IP of the server: 172.31.31.25. After the change, in the #B terminal, the MMS is received with the field "From": "172313125" (is the server IP without point) | |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3202 Registered: 08-2008 |
Hi Fernando, I need to see details of the actual MM4 transaction in order to understand this. It sounds like the "From:" field is missing in the MM4 message that is being received. -- Des NowSMS Support | |||||
| Fernando Nahuel Marti New member Username: Fmarti Post Number: 3 Registered: 05-2011 |
Hi I send some information previously in the firt post. What do you need? Any file in special? For Example: MMSCDEBUG.LOG or SMPPDEBUG.LOG. | |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3227 Registered: 08-2008 |
Hi, I specifically need to see the SMTP transaction data that shows the data that is being received via the MM4 connection. (MM4 is an SMTP based protocol, so there will be headers like MAIL FROM:, RCPT TO:, DATA.) This would be logged in MMSCDEBUG.LOG ... or you can use a packet sniffer like WireShark to intercept the data being received on the SMTP port. It would also help to know what version of the NowSMS MMSC you are running. And, for the sake of quickly resolving the problem, other information that would be helpful is the configuration details for the "MMSC VASP" account (either a screen capture of the configuration dialog, or VASPIN\accountname\VASP.INI). As there may be details that need to remain confidential, you can send this information to nowsms@nowsms.com with Attention: Des in the subject line. Please also post a reply here to let me know if any files are sent via e-mail so that I can know to check for them. -- Des NowSMS Support | |||||
| Fernando Nahuel Marti New member Username: Fmarti Post Number: 4 Registered: 05-2011 |
Hi, The version is: v2008.10.22. Attached files>
Regards. | |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3232 Registered: 08-2008 |
Hi Fernando, We have identified the problem. The "From:" header in the MM4/SMTP message is using a horizontal tab character as a field delimiter, which is not expected, and is causing the sender address to be considered invalid. This is unusual. However, according to the SMTP specifications, the horizontal tab character is legal as a delimiter. I have asked our engineering team to prepare an update ASAP to fix this problem. -- Des NowSMS Support | |||||
| Fernando Nahuel Marti New member Username: Fmarti Post Number: 5 Registered: 05-2011 |
Ok. Really thanks. I wait the upgrade. Regards | |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3234 Registered: 08-2008 |
Hi Fernando, We've posted an update at the following link which will address the issue with missing originator address triggered by tab delimiters in the MM4/SMTP From header: http://www.nowsms.com/download/nowsms20110606.zip The ZIP file contains an installer that will perform a full install of the updated version. -- Des NowSMS Support | |||||
| Fernando Nahuel Marti New member Username: Fmarti Post Number: 6 Registered: 05-2011 |
Hi, The problem is fixed. Really thanks!!! Reguards | |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3250 Registered: 08-2008 |
Hi Fernando, A follow-up. A potentially severe problem was discovered in the 2011.06.06 version that I told you to update to. Please update to the 2011.06.08 version at http://www.nowsms.com/download/nowsms20110608.zip -- Des NowSMS Support | |||||
MMSCDEBUG.LOG
VASP.INI
