How should i set now sms to ...? | Search |
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 06, 2005 ⬆ |
◄ ► |
Author | Message | ||||
Anonymous |
hi I've designed a vasp and test it to send files to nowsms and there is no problem and i recieve succees message with code 1000 but i'm confused how to set nowsms , i mean in account part, i have a .jar file(this is my vasp)and how should i send my file or message to mobile number which i have entered it's number in html dialoge of my project, any help, regards:akram | ||||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3721 Registered: 10-2002 |
Putting the VASP aside for now ... Are you able to send SMS or MMS messages from the NowSMS web interface? What are your external SMS and/or MMS connections? | ||||
Anonymous |
hi i can send MMS and SMS from web menu and there is no problem with it, but in vasp when i set MMSC Routing message to standard MMSE delivery i can recieve the succees in Debug but nothing would be sent to mobile , should i set it to send by MM1 or ...,and when i set it to E_mail address i can recieved it after restarting my pc and the problem is reading from socket, any help, thkx. | ||||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3739 Registered: 10-2002 |
In that case, a debug log would help, so that we can see exactly what you are submitting. Edit MMSC.INI, and under the [MMSC] header, add Debug=Yes. Then restart the MMSC service. Repeat your VASP submission. Post the MMSCDEBUG.LOG as an attachment to a reply here. -bn | ||||
Anonymous |
hi this is my debug: hreadProcessConnection: Processing Complete 09:58:26:374 [7] ThreadProcessConnection: Processing connection from 1.1.1.108... 09:58:26:405 [7] ThreadProcessConnection: Packet Length is 2153 bytes 09:58:26:405 [7] ThreadProcessConnection: 50 4F 53 54 20 2F 6D 6D 37 31 36 35 30 34 38 30 POST /mm71650480 09:58:26:405 [7] ThreadProcessConnection: 38 30 30 30 3D 64 65 76 65 6C 6F 70 65 72 20 48 8000=developer H 09:58:26:405 [7] ThreadProcessConnection: 54 54 50 2F 31 2E 30 0D 0A 53 4F 41 50 41 63 74 TTP/1.0 SOAPAct 09:58:26:405 [7] ThreadProcessConnection: 69 6F 6E 3A 20 22 22 0D 0A 43 6F 6E 74 65 6E 74 ion: "" Content 09:58:26:405 [7] ThreadProcessConnection: 2D 4C 65 6E 67 74 68 3A 20 31 39 38 39 0D 0A 43 -Length: 1989 C 09:58:26:405 [7] ThreadProcessConnection: 6F 6E 74 65 6E 74 2D 54 79 70 65 3A 20 6D 75 6C ontent-Type: mul 09:58:26:405 [7] ThreadProcessConnection: 74 69 70 61 72 74 2F 72 65 6C 61 74 65 64 3B 20 tipart/related; 09:58:26:405 [7] ThreadProcessConnection: 0D 0A 09 62 6F 75 6E 64 61 72 79 3D 22 2D 2D 2D boundary="--- 09:58:26:405 [7] ThreadProcessConnection: 2D 3D 5F 50 61 72 74 5F 32 5F 37 35 37 32 30 38 -=_Part_2_757208 09:58:26:405 [7] ThreadProcessConnection: 31 2E 31 31 30 30 33 32 37 32 39 38 35 35 39 22 1.1100327298559" 09:58:26:405 [7] ThreadProcessConnection: 0D 0A 0D 0A 2D 2D 2D 2D 2D 2D 3D 5F 50 61 72 74 ------=_Part 09:58:26:405 [7] ThreadProcessConnection: 5F 32 5F 37 35 37 32 30 38 31 2E 31 31 30 30 33 _2_7572081.11003 09:58:26:405 [7] ThreadProcessConnection: 32 37 32 39 38 35 35 39 0D 0A 43 6F 6E 74 65 6E 27298559 Conten 09:58:26:405 [7] ThreadProcessConnection: 74 2D 54 79 70 65 3A 20 74 65 78 74 2F 78 6D 6C t-Type: text/xml 09:58:26:405 [7] ThreadProcessConnection: 3B 20 63 68 61 72 73 65 74 3D 75 73 2D 61 73 63 ; charset=us-asc 09:58:26:405 [7] ThreadProcessConnection: 69 69 0D 0A 43 6F 6E 74 65 6E 74 2D 54 72 61 6E ii Content-Tran 09:58:26:405 [7] ThreadProcessConnection: 73 66 65 72 2D 45 6E 63 6F 64 69 6E 67 3A 20 37 sfer-Encoding: 7 09:58:26:405 [7] ThreadProcessConnection: 62 69 74 0D 0A 0D 0A 3C 3F 78 6D 6C 20 76 65 72 bit <?xml ver 09:58:26:405 [7] ThreadProcessConnection: 73 69 6F 6E 3D 27 31 2E 30 27 20 3F 3E 3C 65 6E sion='1.0' ?><en 09:58:26:405 [7] ThreadProcessConnection: 76 3A 45 6E 76 65 6C 6F 70 65 20 78 6D 6C 6E 73 v:Envelope xmlns 09:58:26:405 [7] ThreadProcessConnection: 3A 65 6E 76 3D 22 68 74 74 70 3A 2F 2F 73 63 68 :env="http://sch 09:58:26:405 [7] ThreadProcessConnection: 65 6D 61 73 2E 78 6D 6C 73 6F 61 70 2E 6F 72 67 emas.xmlsoap.org 09:58:26:405 [7] ThreadProcessConnection: 2F 73 6F 61 70 2F 65 6E 76 65 6C 6F 70 65 2F 22 /soap/envelope/" 09:58:26:405 [7] ThreadProcessConnection: 3E 3C 65 6E 76 3A 48 65 61 64 65 72 3E 3C 6D 6D ><env:Header><mm 09:58:26:405 [7] ThreadProcessConnection: 37 3A 54 72 61 6E 73 61 63 74 69 6F 6E 49 44 20 7:TransactionID 09:58:26:405 [7] ThreadProcessConnection: 78 6D 6C 6E 73 3A 6D 6D 37 3D 22 68 74 74 70 3A xmlns:mm7="http: 09:58:26:405 [7] ThreadProcessConnection: 2F 2F 77 77 77 2E 33 67 70 70 2E 6F 72 67 2F 66 //www.3gpp.org/f 09:58:26:405 [7] ThreadProcessConnection: 74 70 2F 53 70 65 63 73 2F 61 72 63 68 69 76 65 tp/Specs/archive 09:58:26:405 [7] ThreadProcessConnection: 2F 32 33 5F 73 65 72 69 65 73 2F 32 33 2E 31 34 /23_series/23.14 09:58:26:405 [7] ThreadProcessConnection: 30 2F 73 63 68 65 6D 61 2F 52 45 4C 2D 35 2D 4D 0/schema/REL-5-M 09:58:26:405 [7] ThreadProcessConnection: 4D 37 2D 31 2D 33 22 3E 39 39 38 62 30 38 3A 31 M7-1-3">998b08:1 09:58:26:405 [7] ThreadProcessConnection: 30 30 33 30 37 32 65 35 61 63 3A 2D 37 66 66 64 003072e5ac:-7ffd 09:58:26:405 [7] ThreadProcessConnection: 7A 6A 61 6C 69 6C 69 2F 31 2E 31 2E 31 2E 31 30 zjalili/1.1.1.10 09:58:26:405 [7] ThreadProcessConnection: 38 3C 2F 6D 6D 37 3A 54 72 61 6E 73 61 63 74 69 8</mm7:Transacti 09:58:26:405 [7] ThreadProcessConnection: 6F 6E 49 44 3E 3C 2F 65 6E 76 3A 48 65 61 64 65 onID></env:Heade 09:58:26:405 [7] ThreadProcessConnection: 72 3E 3C 65 6E 76 3A 42 6F 64 79 3E 3C 53 75 62 r><env:Body><Sub 09:58:26:405 [7] ThreadProcessConnection: 6D 69 74 52 65 71 20 78 6D 6C 6E 73 3D 22 68 74 mitReq xmlns="ht 09:58:26:405 [7] ThreadProcessConnection: 74 70 3A 2F 2F 77 77 77 2E 33 67 70 70 2E 6F 72 tp://www.3gpp.or 09:58:26:405 [7] ThreadProcessConnection: 67 2F 66 74 70 2F 53 70 65 63 73 2F 61 72 63 68 g/ftp/Specs/arch 09:58:26:405 [7] ThreadProcessConnection: 69 76 65 2F 32 33 5F 73 65 72 69 65 73 2F 32 33 ive/23_series/23 09:58:26:405 [7] ThreadProcessConnection: 2E 31 34 30 2F 73 63 68 65 6D 61 2F 52 45 4C 2D .140/schema/REL- 09:58:26:405 [7] ThreadProcessConnection: 35 2D 4D 4D 37 2D 31 2D 33 22 3E 3C 4D 4D 37 56 5-MM7-1-3"><MM7V 09:58:26:405 [7] ThreadProcessConnection: 65 72 73 69 6F 6E 3E 35 2E 33 2E 30 3C 2F 4D 4D ersion>5.3.0</MM 09:58:26:421 [7] ThreadProcessConnection: 37 56 65 72 73 69 6F 6E 3E 3C 53 65 6E 64 65 72 7Version><Sender 09:58:26:421 [7] ThreadProcessConnection: 49 64 65 6E 74 69 66 69 63 61 74 69 6F 6E 3E 3C Identification>< 09:58:26:421 [7] ThreadProcessConnection: 56 41 53 50 49 44 3E 6D 79 20 69 64 3C 2F 56 41 VASPID>my id</VA 09:58:26:421 [7] ThreadProcessConnection: 53 50 49 44 3E 3C 53 65 6E 64 65 72 41 64 64 72 SPID><SenderAddr 09:58:26:421 [7] ThreadProcessConnection: 65 73 73 3E 3C 4E 75 6D 62 65 72 3E 31 36 35 30 ess><Number>1650 09:58:26:421 [7] ThreadProcessConnection: 34 38 30 38 30 30 30 3C 2F 4E 75 6D 62 65 72 3E 4808000</Number> 09:58:26:421 [7] ThreadProcessConnection: 3C 2F 53 65 6E 64 65 72 41 64 64 72 65 73 73 3E </SenderAddress> 09:58:26:421 [7] ThreadProcessConnection: 3C 2F 53 65 6E 64 65 72 49 64 65 6E 74 69 66 69 </SenderIdentifi 09:58:26:421 [7] ThreadProcessConnection: 63 61 74 69 6F 6E 3E 3C 52 65 63 69 70 69 65 6E cation><Recipien 09:58:26:421 [7] ThreadProcessConnection: 74 73 3E 3C 54 6F 3E 3C 53 68 6F 72 74 43 6F 64 ts><To><ShortCod 09:58:26:421 [7] ThreadProcessConnection: 65 3E 2B 39 38 39 31 32 32 30 36 35 37 30 39 3C e>+989122065709< 09:58:26:421 [7] ThreadProcessConnection: 2F 53 68 6F 72 74 43 6F 64 65 3E 3C 2F 54 6F 3E /ShortCode></To> 09:58:26:421 [7] ThreadProcessConnection: 3C 2F 52 65 63 69 70 69 65 6E 74 73 3E 3C 53 65 </Recipients><Se 09:58:26:421 [7] ThreadProcessConnection: 72 76 69 63 65 43 6F 64 65 3E 31 3C 2F 53 65 72 rviceCode>1</Ser 09:58:26:421 [7] ThreadProcessConnection: 76 69 63 65 43 6F 64 65 3E 3C 4D 65 73 73 61 67 viceCode><Messag 09:58:26:421 [7] ThreadProcessConnection: 65 43 6C 61 73 73 3E 50 65 72 73 6F 6E 61 6C 3C eClass>Personal< 09:58:26:421 [7] ThreadProcessConnection: 2F 4D 65 73 73 61 67 65 43 6C 61 73 73 3E 3C 44 /MessageClass><D 09:58:26:421 [7] ThreadProcessConnection: 65 6C 69 76 65 72 79 52 65 70 6F 72 74 3E 66 61 eliveryReport>fa 09:58:26:421 [7] ThreadProcessConnection: 6C 73 65 3C 2F 44 65 6C 69 76 65 72 79 52 65 70 lse</DeliveryRep 09:58:26:421 [7] ThreadProcessConnection: 6F 72 74 3E 3C 52 65 61 64 52 65 70 6C 79 3E 66 ort><ReadReply>f 09:58:26:421 [7] ThreadProcessConnection: 61 6C 73 65 3C 2F 52 65 61 64 52 65 70 6C 79 3E alse</ReadReply> 09:58:26:421 [7] ThreadProcessConnection: 3C 50 72 69 6F 72 69 74 79 3E 4C 6F 77 3C 2F 50 <Priority>Low</P 09:58:26:421 [7] ThreadProcessConnection: 72 69 6F 72 69 74 79 3E 3C 53 75 62 6A 65 63 74 riority><Subject 09:58:26:436 [7] ThreadProcessConnection: 3E 61 20 74 65 73 74 3C 2F 53 75 62 6A 65 63 74 >a test</Subject 09:58:26:436 [7] ThreadProcessConnection: 3E 3C 43 68 61 72 67 65 64 50 61 72 74 79 3E 53 ><ChargedParty>S 09:58:26:436 [7] ThreadProcessConnection: 65 6E 64 65 72 3C 2F 43 68 61 72 67 65 64 50 61 ender</ChargedPa 09:58:26:436 [7] ThreadProcessConnection: 72 74 79 3E 3C 43 6F 6E 74 65 6E 74 20 68 72 65 rty><Content hre 09:58:26:436 [7] ThreadProcessConnection: 66 3D 22 63 69 64 3A 67 65 6E 65 72 69 63 5F 63 f="cid:generic_c 09:58:26:436 [7] ThreadProcessConnection: 6F 6E 74 65 6E 74 5F 69 64 22 20 2F 3E 3C 2F 53 ontent_id" /></S 09:58:26:436 [7] ThreadProcessConnection: 75 62 6D 69 74 52 65 71 3E 3C 2F 65 6E 76 3A 42 ubmitReq></env:B 09:58:26:436 [7] ThreadProcessConnection: 6F 64 79 3E 3C 2F 65 6E 76 3A 45 6E 76 65 6C 6F ody></env:Envelo 09:58:26:436 [7] ThreadProcessConnection: 70 65 3E 0D 0A 2D 2D 2D 2D 2D 2D 3D 5F 50 61 72 pe> ------=_Par 09:58:26:436 [7] ThreadProcessConnection: 74 5F 32 5F 37 35 37 32 30 38 31 2E 31 31 30 30 t_2_7572081.1100 09:58:26:436 [7] ThreadProcessConnection: 33 32 37 32 39 38 35 35 39 0D 0A 43 6F 6E 74 65 327298559 Conte 09:58:26:436 [7] ThreadProcessConnection: 6E 74 2D 54 79 70 65 3A 20 6D 75 6C 74 69 70 61 nt-Type: multipa 09:58:26:436 [7] ThreadProcessConnection: 72 74 2F 72 65 6C 61 74 65 64 3B 20 0D 0A 09 62 rt/related; b 09:58:26:436 [7] ThreadProcessConnection: 6F 75 6E 64 61 72 79 3D 22 2D 2D 2D 2D 3D 5F 50 oundary="----=_P 09:58:26:436 [7] ThreadProcessConnection: 61 72 74 5F 33 5F 32 35 35 36 34 37 39 37 2E 31 art_3_25564797.1 09:58:26:436 [7] ThreadProcessConnection: 31 30 30 33 32 37 32 39 38 35 35 39 22 3B 0D 0A 100327298559"; 09:58:26:436 [7] ThreadProcessConnection: 09 73 74 61 72 74 3D 22 3C 6D 6D 73 2E 73 6D 69 start="<mms.smi 09:58:26:436 [7] ThreadProcessConnection: 6C 3E 22 3B 0D 0A 09 74 79 70 65 3D 22 61 70 70 l>"; type="app 09:58:26:436 [7] ThreadProcessConnection: 6C 69 63 61 74 69 6F 6E 2F 73 6D 69 6C 22 0D 0A lication/smil" 09:58:26:436 [7] ThreadProcessConnection: 43 6F 6E 74 65 6E 74 2D 49 44 3A 20 3C 67 65 6E Content-ID: <gen 09:58:26:436 [7] ThreadProcessConnection: 65 72 69 63 5F 63 6F 6E 74 65 6E 74 5F 69 64 3E eric_content_id> 09:58:26:436 [7] ThreadProcessConnection: 0D 0A 0D 0A 2D 2D 2D 2D 2D 2D 3D 5F 50 61 72 74 ------=_Part 09:58:26:436 [7] ThreadProcessConnection: 5F 33 5F 32 35 35 36 34 37 39 37 2E 31 31 30 30 _3_25564797.1100 09:58:26:436 [7] ThreadProcessConnection: 33 32 37 32 39 38 35 35 39 0D 0A 43 6F 6E 74 65 327298559 Conte 09:58:26:436 [7] ThreadProcessConnection: 6E 74 2D 54 79 70 65 3A 20 74 65 78 74 2F 70 6C nt-Type: text/pl 09:58:26:436 [7] ThreadProcessConnection: 61 69 6E 3B 20 6E 61 6D 65 3D 74 65 73 74 31 2E ain; name=test1. 09:58:26:436 [7] ThreadProcessConnection: 74 78 74 3B 20 63 68 61 72 73 65 74 3D 75 73 2D txt; charset=us- 09:58:26:436 [7] ThreadProcessConnection: 61 73 63 69 69 0D 0A 43 6F 6E 74 65 6E 74 2D 54 ascii Content-T 09:58:26:436 [7] ThreadProcessConnection: 72 61 6E 73 66 65 72 2D 45 6E 63 6F 64 69 6E 67 ransfer-Encoding 09:58:26:436 [7] ThreadProcessConnection: 3A 20 37 62 69 74 0D 0A 43 6F 6E 74 65 6E 74 2D : 7bit Content- 09:58:26:436 [7] ThreadProcessConnection: 44 69 73 70 6F 73 69 74 69 6F 6E 3A 20 61 74 74 Disposition: att 09:58:26:436 [7] ThreadProcessConnection: 61 63 68 6D 65 6E 74 3B 20 66 69 6C 65 6E 61 6D achment; filenam 09:58:26:436 [7] ThreadProcessConnection: 65 3D 74 65 73 74 31 2E 74 78 74 0D 0A 43 6F 6E e=test1.txt Con 09:58:26:436 [7] ThreadProcessConnection: 74 65 6E 74 2D 49 44 3A 20 3C 74 65 73 74 31 2E tent-ID: <test1. 09:58:26:436 [7] ThreadProcessConnection: 74 78 74 3E 0D 0A 0D 0A 74 68 69 73 20 69 73 20 txt> this is 09:58:26:436 [7] ThreadProcessConnection: 61 20 74 65 78 74 20 63 6F 6E 74 65 6E 74 20 66 a text content f 09:58:26:436 [7] ThreadProcessConnection: 69 6C 65 20 77 68 69 63 68 20 68 61 73 20 6A 75 ile which has ju 09:58:26:436 [7] ThreadProcessConnection: 73 74 20 6F 6E 65 20 6C 69 6E 65 0A 0D 0A 2D 2D st one line -- 09:58:26:436 [7] ThreadProcessConnection: 2D 2D 2D 2D 3D 5F 50 61 72 74 5F 33 5F 32 35 35 ----=_Part_3_255 09:58:26:436 [7] ThreadProcessConnection: 36 34 37 39 37 2E 31 31 30 30 33 32 37 32 39 38 64797.1100327298 09:58:26:436 [7] ThreadProcessConnection: 35 35 39 0D 0A 43 6F 6E 74 65 6E 74 2D 54 79 70 559 Content-Typ 09:58:26:436 [7] ThreadProcessConnection: 65 3A 20 61 70 70 6C 69 63 61 74 69 6F 6E 2F 73 e: application/s 09:58:26:436 [7] ThreadProcessConnection: 6D 69 6C 0D 0A 43 6F 6E 74 65 6E 74 2D 54 72 61 mil Content-Tra 09:58:26:436 [7] ThreadProcessConnection: 6E 73 66 65 72 2D 45 6E 63 6F 64 69 6E 67 3A 20 nsfer-Encoding: 09:58:26:436 [7] ThreadProcessConnection: 37 62 69 74 0D 0A 43 6F 6E 74 65 6E 74 2D 49 44 7bit Content-ID 09:58:26:436 [7] ThreadProcessConnection: 3A 20 3C 6D 6D 73 2E 73 6D 69 6C 3E 0D 0A 0D 0A : <mms.smil> 09:58:26:436 [7] ThreadProcessConnection: 3C 3F 78 6D 6C 20 76 65 72 73 69 6F 6E 3D 22 31 <?xml version="1 09:58:26:436 [7] ThreadProcessConnection: 2E 30 22 20 65 6E 63 6F 64 69 6E 67 3D 22 55 54 .0" encoding="UT 09:58:26:436 [7] ThreadProcessConnection: 46 2D 38 22 3F 3E 0A 3C 73 6D 69 6C 3E 3C 68 65 F-8"?> <smil><he 09:58:26:436 [7] ThreadProcessConnection: 61 64 3E 3C 6C 61 79 6F 75 74 3E 3C 72 6F 6F 74 ad><layout><root 09:58:26:436 [7] ThreadProcessConnection: 2D 6C 61 79 6F 75 74 20 77 69 64 74 68 3D 22 31 -layout width="1 09:58:26:436 [7] ThreadProcessConnection: 32 2E 30 22 20 68 65 69 67 68 74 3D 22 31 32 2E 2.0" height="12. 09:58:26:436 [7] ThreadProcessConnection: 30 22 2F 3E 3C 72 65 67 69 6F 6E 20 69 64 3D 22 0"/><region id=" 09:58:26:436 [7] ThreadProcessConnection: 54 65 78 74 22 20 74 6F 70 3D 22 35 30 25 22 20 Text" top="50%" 09:58:26:436 [7] ThreadProcessConnection: 6C 65 66 74 3D 22 30 22 20 68 65 69 67 68 74 3D left="0" height= 09:58:26:436 [7] ThreadProcessConnection: 22 35 30 25 22 20 77 69 64 74 68 3D 22 31 30 30 "50%" width="100 09:58:26:436 [7] ThreadProcessConnection: 25 22 20 66 69 74 3D 22 68 69 64 64 65 6E 22 2F %" fit="hidden"/ 09:58:26:436 [7] ThreadProcessConnection: 3E 3C 2F 6C 61 79 6F 75 74 3E 3C 2F 68 65 61 64 ></layout></head 09:58:26:436 [7] ThreadProcessConnection: 3E 3C 62 6F 64 79 3E 3C 70 61 72 20 64 75 72 3D ><body><par dur= 09:58:26:436 [7] ThreadProcessConnection: 22 31 32 6D 73 22 3E 3C 74 65 78 74 20 73 72 63 "12ms"><text src 09:58:26:436 [7] ThreadProcessConnection: 3D 22 63 69 64 3A 74 65 73 74 31 2E 74 78 74 22 ="cid:test1.txt" 09:58:26:436 [7] ThreadProcessConnection: 20 72 65 67 69 6F 6E 3D 22 54 65 78 74 22 2F 3E region="Text"/> 09:58:26:436 [7] ThreadProcessConnection: 3C 2F 70 61 72 3E 3C 2F 62 6F 64 79 3E 3C 2F 73 </par></body></s 09:58:26:436 [7] ThreadProcessConnection: 6D 69 6C 3E 0D 0A 2D 2D 2D 2D 2D 2D 3D 5F 50 61 mil> ------=_Pa 09:58:26:436 [7] ThreadProcessConnection: 72 74 5F 33 5F 32 35 35 36 34 37 39 37 2E 31 31 rt_3_25564797.11 09:58:26:436 [7] ThreadProcessConnection: 30 30 33 32 37 32 39 38 35 35 39 2D 2D 0D 0A 0D 00327298559-- 09:58:26:436 [7] ThreadProcessConnection: 0A 2D 2D 2D 2D 2D 2D 3D 5F 50 61 72 74 5F 32 5F ------=_Part_2_ 09:58:26:436 [7] ThreadProcessConnection: 37 35 37 32 30 38 31 2E 31 31 30 30 33 32 37 32 7572081.11003272 09:58:26:436 [7] ThreadProcessConnection: 39 38 35 35 39 2D 2D 0D 0A 98559-- 09:58:26:546 [7] DeliverMMSMessage: Found Phone Recip 09:58:26:577 [7] mm7 Recip: TO: +989122065709/TYPE=PLMN 09:58:26:577 [7] ProcessMM7Request: HTTP/1.0 200 OK Content-Length: 709 Content-Type: text/xml Connection: close 09:58:26:577 [7] ProcessMM7Request: <?xml version='1.0' ?> <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> <env:Header> <mm7:TransactionID xmlns:mm7="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-M M7-1-2" env:mustUnderstand="1"> 998b08:1003072e5ac:-7ffdzjalili/1.1.1.108 </mm7:TransactionID> </env:Header> <env:Body> <SubmitRsp xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1 -2"> <MM7Version>5.3.0</MM7Version> <Status> <StatusCode>1000</StatusCode> <StatusText>Success</StatusText> </Status> <MessageID>20041113/09/93E67249@1.1.1.94</MessageID> </SubmitRsp> </env:Body> </env:Envelope> 09:58:26:577 [7] ThreadProcessConnection: Processing Complete regards:akram | ||||
Anonymous |
hi this is that file
| ||||
Anonymous |
hi why nobody help me? | ||||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3761 Registered: 10-2002 |
Unfortunately, there's not really enough detail in that debug log. I can only see that the message was accepted, but I can't see how it is being routed. Well, actually, the fact that it says "found phone recip" suggests that NowSMS is going to act as an MMSC and perform direct delivery of the MMS message. So the SMSOUT-yyyymmdd.LOG should show one or two messages being sent out after this message is submitted ... that would be the MMS notification for the message. Assuming that you are sending in both cases to the same phone number, it doesn't make any sense that sending an MMS would work from the web interface of NowSMS, but not from an MM7 submission. The MMSC-yyyymmdd.LOG should show a record of your message being submitted via MM7. Does it show an MMSRETRIEVE entry in the log following the message submission? (I'm wondering if the phone is getting the notification, but not understanding something about the message content. SonyEricsson phones are great for troubleshooting because they will tell you that they received a notification, even if they cannot understand or access the MMS message. But Nokia phones hide all of this from you.) Basically, I'm curious what you can see different in the SMSOUT-yyyymmdd.LOG and MMSC-yyyymmdd.LOG files between when you send the MMS message through the web interface and when you send it via an MM7 message submission. -bn | ||||
akram New member Username: Akram Post Number: 2 Registered: 08-2004 |
Hi Bryce thkx for your help,i try it. let me now what should i do if i want to send a request to vas from mobile phone? regards | ||||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3782 Registered: 10-2002 |
Define one or more fictional phone numbers for the VASP, and then under the "MMSC Routing" definition, put the phone number(s) into the "Route messages to this account for recipient phone number(s)" field. If you want to use short codes, NowSMS defaults to 4 or less digits for short codes. And in some conditions, longer short codes can get mangled unless you edit MMSC.INI, and under the [MMSC] header add: ShortCodeMaxLength=5 (You can choose another number other than 5, but that seems to be the value that most people are using ... and actually the one that we should change to be our default setting.) -bn | ||||
akram New member Username: Akram Post Number: 3 Registered: 08-2004 |
hi what is the role of "Content href"? regards | ||||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3818 Registered: 10-2002 |
Hi akram, For more information on the MM7 elements, I'd refer you to the 3GPP specification. http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/ has an archive of the different releases of the spec. But basically, it is a pointer to the "content-id:" of the MIME object that contains the content of the MMS message. (Usually that object is a multipart/related object.) Note that our MMSC ignores this field and assumes that the MIME object that follows the MM7 XML contains the content of the MMS message. -bn |