| Sender Address overriding |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through October 31, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| MedSalimALI Frequent Contributor Username: Salim Post Number: 121 Registered: 04-2005 |
Hey !!! I have problem with the sender address. CAn anyone tell him how to override the default sender address which can be mentioned in the nowsms?? } | |||
| msalim Frequent Contributor Username: Salim Post Number: 124 Registered: 04-2005 |
Hello Bryce, Nice to contact you again, we have been in Holiday and I wish you spend yours fine... We migrated our NowSMS gateway by upgrading the license into 2007 version... I am connected into a new operator MMSC who gave me some MM7 settings which I use my guessing matching as below: Clause Parameter Value 2.1 Service Name: ISYS MMS Services 2.2 Enterprise Code: 1004 2.3 VAS Code: 100400 2.4 Service Code : 100 2.5 Access Number: 10040 2.9 SP Access Auth Account ( If required by Clause 2.8 ): sysmms 2.10 SP Access Auth Password ( If required by Clause 2.8 ): s1y2s3 2.11 MMSC Access Auth Mode: 1-Auth IP Address only 2.12 MMSC Access Auth Account For me I translated it as below: [VASP] Protocol=MM7 Server=http://195.229.243.170:81/vas VASPID=10040 VASID=100400 ServiceCode=100 mm7SubmitReq=Yes UserName=sysmms Password=s1y2s3 UseDial=No The problem, am sending MMS, simple text, nowSMS log showing OK, but the Operator receipient don't receive any thing? can please give me some clouds on such matter as usual? -09-03 12:44:46,MMSIN-DeliveryReport,,SMS:localsystem,100,VASP:etisalat,1A3EC63F.mms,55 2007-09-03 12:44:46,MMSIN-DeliveryReport,,SMS:localsystem,100,VASP:etisalat,E466453E.mms,55 2007-09-03 12:44:49,MMSOUT-DeliveryReport,VASP:etisalat,100,+971508114633/TYPE=PLMN,OK,1A3E C63F.MMS,771 2007-09-03 12:44:50,MMSOUT-DeliveryReport,VASP:etisalat,100,00971508114633/TYPE=PLMN,OK,E46 6453E.MMS,77 Salim | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7438 Registered: 10-2002 |
Hi Salim, How you override the "Default Sender Address" depends on how you are submitting messages (HTTP, SMPP, MM7??). If "Allow Sender Address Override" is checked, then it is possible to override the sender address ... at least as far as what NowSMS transmits over the connection (the provider might have their own restrictions). So I would need more detail to answer that. Regarding the other question .... it sounds like we are getting some sort of delivery report back from the provider, but we can't figure out what to do with it, so we are routing it back to them. I think we would need to see an MMSCDEBUG.LOG to figure out what is actually going on. -bn | |||
| msalim Frequent Contributor Username: Salim Post Number: 125 Registered: 04-2005 |
hello Bryce, I was spent more than 5 nights and fortunately I got solve the problem... What I have done Bryce, as i sent in the email, the Soap-env was not present on the header, I remove the mmsc.exe and place another one which was bigger, after submitting, I found it present exactly as I was guessing... Hooray i got a phone call from UAE Operator that the MMS was reeived.. here is the header we are passing and the MMSC accept it: <?xml version="1.0" encoding="UTF-8"?> <soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"><soap-env:Header><mm7:TransactionID xmlns:mm7="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-0" soap-env:mustUnderstand="1">20070910183450-77F89AD9@192.168.0.17</mm7:TransactionID></soap-env:Header><soap-env:Body><SubmitRsp xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-0"><MM7Version>6.3.0</MM7Version><Status><StatusCode>1000</StatusCode><StatusText >Sending succeeded.</StatusText></Status><MessageID>091019442797100101424</MessageID></Su bmitRsp></soap-env:Body></soap-env:Envelope> 18:34:54:515 [7] ThreadProcessVASPQ: mm7 - got MessageID I send all kind now, pic, video, audio without problem... I was even call Lisa, and she was informed me to have forward to you the email... but I was trying to guess and it solved... now still in Bahrain, I am trying to do similar and come back to you again... Salim | |||
| Tusajigwe Isaga New member Username: Isyu1979 Post Number: 1 Registered: 09-2007 |
Dear sir/madam I am using your software in trial version,i would like to know if your software can interface with c language because i wrote a programm in c to read a text file which i saved on LOCAL DISK on my PC,basically the text file contain this informations from isyu1979@yahoo.com To bmazigo@yahoo.com Hi can we meet tommorrow Tusa. What i want is to use NOW SMS software which i nstalled on my PC to receive this text file which I have created,i.e to receive this file in now sms Software,because if i will manage to see this file,i would like to send an SMS E-mail alert message which will be in the form of text message by using your software to the e-mail owner i.e bmazigo@yahoo.com from the example above. So at the end i will send the following message YOU HAVE 1 E-MAIL FROM isyu1979@yahoo.com to the mobile number of bmazigo,just to inform that he has got e-mail.Is that posssibe? Also i would like to know how the text file can be received in now sms software? thanks Regards Tusa | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7452 Registered: 10-2002 |
Hi Salim, I was confused by the messages that Lisa fowarded me. Whether "soap-env:" or "env:" is used as the prefix should not matter. There is a statement in the XML that specifies what the actual prefix is. <XXXXXXXX:Envelope xmlns:XXXXXXXX="http://schemas.xmlsoap.org/soap/envelope/"> In the above statement, it indicates that if "XXXXXXXX:" is used as a prefix, then we are using an XML element defined in the schema "http://schemas.xmlsoap.org/soap/envelope/". It is the "xmlns:XXXXXXXX=" part of the statement that defines which prefix is used. So, whether the prefix is "soap-env:" or "env:" should not make any difference, as long as it is defined properly in the XML. NowSMS uses the "env:" prefix, because this is the prefix that is used in all of the examples in the actual MM7 specification (3GPP TS 23.140). However, we have observed that there is at least one brain-dead MMSC that will not accept messages unless "soap-env:" is used as the prefix. There is a configuration parameter that can be put into VASPOUT\accountname\VASP.INI, under the [VASP] header, FirstHop=Yes ... this setting will make some subtle changes to the XML so that "soap-env:" is used as a prefix instead. Perhaps this is the problem that you have encountered? -bn | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7453 Registered: 10-2002 |
Hi Tusa, The API for NowSMS is HTTP based (you can also enable SMTP in NowSMS so that it can accept e-mail messages that it forwards to SMS, but this is less flexible and can be more difficult to configure). From a C program, you would make a URL request to the NowSMS server. (As NowSMS is running on the same machine as your program, you would connect to NowSMS on the 127.0.0.1 loopback address.) The following link shows the basic URL format for sending a text message: http://www.nowsms.com/documentation/ProductDocumentation/sending_messages/sendin g_text_messages.htm From a C program, you just need to find a C example for making a URL request, and change the URL to a URL for connecting to the NowSMS server. Unfortunately, I don't have any C examples ... but I do have a simple command line example that might help you. The following link has a Windows JScript: http://www.nowsms.com/support/bulletins/tb-nowsms-008.htm Save the Windows JScript file to your computer ... edit the username and password in the example script (or create an "SMS Users" account in NowSMS with a username and password of "test" as that is what the example uses) ... and then you have a simple command line program for sending an SMS which you could easily spawn from your C program. -bn | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7454 Registered: 10-2002 |
Hi Tusa, The API for NowSMS is HTTP based (you can also enable SMTP in NowSMS so that it can accept e-mail messages that it forwards to SMS, but this is less flexible and can be more difficult to configure). From a C program, you would make a URL request to the NowSMS server. (As NowSMS is running on the same machine as your program, you would connect to NowSMS on the 127.0.0.1 loopback address.) The following link shows the basic URL format for sending a text message: http://www.nowsms.com/documentation/ProductDocumentation/sending_messages/sendin g_text_messages.htm From a C program, you just need to find a C example for making a URL request, and change the URL to a URL for connecting to the NowSMS server. Unfortunately, I don't have any C examples ... but I do have a simple command line example that might help you. The following link has a Windows JScript: http://www.nowsms.com/support/bulletins/tb-nowsms-008.htm Save the Windows JScript file to your computer ... edit the username and password in the example script (or create an "SMS Users" account in NowSMS with a username and password of "test" as that is what the example uses) ... and then you have a simple command line program for sending an SMS which you could easily spawn from your C program. -bn | |||
| msalim Frequent Contributor Username: Salim Post Number: 127 Registered: 04-2005 |
Hi Bryce, You are totally right, but the matter is I try the Firsthope settings which we used in Bahrain with and also it doesn't work with UAE operator... I think I will send you the MMSC.EXE I used and I got solve the matter... Me I was wondering to solve the header "soap-env"... after solving it was cleared by MMSCDEBUG.LOG that the VASPID was missing on the Error sent back "Authority Failed" I use the same Username as VASPID, the MMS delivered successfully... Honestly Bryce, I am now courious binding another MM7 with Fastlink in Jordan with another one for Zain Bahrain... because of the only license we have I would need to run 4 MM7 accounts in one NowSMS, and I tested the sender addresses to be the only identifier... Can I used comma between a list of Sender address in case on the URL I use a different MMSFrom, or NowSMS will not support such settings? Regarding the above way of Email2SMS, we have a client who want to use an email forwarder base solution: whenver an email sent to a specific email ID, nowSMS should receive an alert and notify as SMS to the User to have revceived the SMS, can we enable a receiving email and send the email as SMS? can we also send email to MMS? because the MMS to email is supporting on the Peer2Peer sending... Please advice, and sorry because whenever I catch you I don't want to leave you.... Salim | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7462 Registered: 10-2002 |
Hi Salim, Ok ... send the MMSC.EXE. I do not understand why the version would make a difference. Are you sure the version of MMSC.EXE made it work, or was it the setting of the VASPID parameter that made it work?
I don't think the comma list of sender addresses will work (it does for SMSC connections, but I do not think it will for MMSC). However, there is another solution for MMSC connections. With MMSC connections, because you are using the HTTP protocol, which is only connected when you are transmitting a message, it is not a problem to define multiple copies of the same MMSC connection, but defined with different sender addresses. Use all of the other same parameters, but change the sender address in the copies of the definition. (Sometimes when you use a different sender address, the operator wants you to use a different VASPID or VASID setting, so you may need to find out about this.)
Yes. SMS or MMS. I think I gave some good explanation about this yesterday here: http://support.nowsms.com/discus/messages/1/22525.html So that may help answer some questions. -bn | |||
| ashot shabazian New member Username: Tyrebusters Post Number: 8 Registered: 03-2004 |
.....the comma list of sender addresses will work (it does for SMSC connections.... How about wildcards or regexp for message routing upstream in SMSC (SMPP connection) definitions, based on Source Address. Alphanumeric/numeric for example, with leading or tailing combinations, etc. Sorry for posting off-topic, but this seems to be a practical important feature we haven't seen in commercial SMPP platforms.. | |||
