| Question of creating destination address field |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through April 11, 2011 ⬆ |
◄ ► |
| Author | Message | |||||
| Johnny New member Username: Johny Post Number: 16 Registered: 02-2009 |
Hi… I run Now sms v2010.12.21 and many people use it. We have some request to you. We’d like to change the destination address as they like. Currently, When we send sms in the now sms, destination address is fix. So We request creating destination address field in the Send Binary Message. In the destination address field created, Users enter destination address values they want. For example, Currently destination address 0c91280192991141 0c - Length 91 – TON/NPI 28 - 821029991114 01 92 99 11 41 the other destination address values we want 04D01100 04 - Length D0 – TON/NPI 11 – DATA 1 00 – DATA 2 We want to enter the other destination address values instead of fix destination address. Thanks  | |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2906 Registered: 08-2008 |
Hi Johnny, The destination address is who the message is being sent to. That is specified in the "Phone Number" field. I'm guessing that you must not be referring to the destination address, but maybe the source address? However, your example seems to be encoded as SMS PDU fields that would be used when sending via a modem. And you cannot set a source address when submitting an SMS PDU via a modem. So I don't understand what you are asking for. Can you please clarify? -- Des NowSMS Support | |||||
| Johnny New member Username: Johny Post Number: 17 Registered: 02-2009 |
The destination address is who the message is being sent to. That is specified in the "Phone Number" field. --> I run now sms in the lab and many developers use now sms.. they want to set destination address values directly they want. I'm guessing that you must not be referring to the destination address, but maybe the source address? However, your example seems to be encoded as SMS PDU fields that would be used when sending via a modem. And you cannot set a source address when submitting an SMS PDU via a modem. -->These are PDU files and send a message via now sms web page. OK, source address can be not sent. So that it is possible, I request creating destination address field in the Send Binary Message. And in the new field, I want to set destination address value they want. | |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2911 Registered: 08-2008 |
Johnny, I'm sorry, but I still do not understand. The destination address is who the message is being sent to. That is specified in the "Phone Number" field. -- Des NowSMS Support | |||||
| Johnny New member Username: Johny Post Number: 18 Registered: 02-2009 |
Dear Sir... I summarize our request. Please refer to the attached files and consider it Thanks...
| |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2935 Registered: 08-2008 |
Hi Johnny, Ok ... you appear to be referring to the source (also known as "originator" or "sender") address. What type of SMSC connection are you using? From the attachment, you appear to be using a GSM modem. It is NOT possible to set the source address when sending messages via a GSM modem. This explanation might help you understand why. Your attachment makes reference to the SMS-DELIVER PDU. Notice that the SMS-DELIVER PDU contains the TP-Originating-Address field, which is the address that you want to change ... the address of the sender/originator of this message. The SMS-DELIVER PDU does NOT contain a TP-Destination-Address field. It is implied that the entity that has received this PDU is the destination address. Similarly, when NowSMS sends a message using a GSM modem, it uses the SMS-SUBMIT TPDU. The SMS-SUBMIT TPDU contains a TP-Destination-Address field (who should receive the message), but it does NOT contain a TP-Originating-Address. The terminal (modem or phone) is not allowed to specify the TP-Originating-Address. The TP-Originating-Address that appears in the resulting SMS-DELIVER TPDU is inserted by the SMSC that processes the message. If you use a different type of SMSC connection (such as SMPP), it is possible to specify the originator/sender/source address. This address is encoded in SMPP submit PDU format, and the SMSC that processes the message converts it to SMS-DELIVER TPDU. NowSMS does support alphanumeric sender addresses in SMPP environments. The originator/sender address is specified in the "Default Sender Address" field where the SMPP connection is defined in NowSMS. It is also possible to override this sender address in individual message submissions (it is very simple to edit the NowSMS web form to add a parameter named "Sender"). I hope this helps answer your question. I wish we could do what you ask, but a GSM modem does not allow the originator/sender/source address to be specified. -- Des NowSMS Support | |||||
| Johnny New member Username: Johny Post Number: 19 Registered: 02-2009 |
Thank you for your support. I use SMPP environment. So I add the parameter named “Sender” as follow ------------------------------------------------- <tr style='mso-yfti-irow:2'> <td width=236 valign=top style='width:176.95pt;border:solid #669999 1.0pt; border-top:none;mso-border-top-alt:solid #669999 .5pt;mso-border-alt:solid #669999 .5pt; padding:0in 5.4pt 0in 5.4pt'> <p class=MsoNormal>Origination Number:</p> </td> <td width=504 valign=top style='width:377.95pt;border-top:none;border-left: none;border-bottom:solid #669999 1.0pt;border-right:solid #669999 1.0pt; mso-border-top-alt:solid #669999 .5pt;mso-border-left-alt:solid #669999 .5pt; mso-border-alt:solid #669999 .5pt;padding:0in 5.4pt 0in 5.4pt'> <p class=MsoNormal><INPUT TYPE="TEXT" SIZE="43" NAME="Sender"></p> </td> </tr> ------------------------------------------------- I entered binary data “”04D01100” in the added field and I sent a message. However I didn’t receive it. So I check Q folder. In the Q folder message was stored. This is information of SMS ------------------------------------------- [SMS] SubmittedBy=127.0.0.1 Sender=04D01100 Data= Binary=1 PhoneNumber=22114576 [ErrorDetail] RetryCount=2 LastRetryTime=20110223150750 LastErrorInfo=ERROR: Timeout waiting for response from server or lost connection -- SMPP – 2xx.2xx.2xx.2xx:6xxx ------------------------------------------------ When I entered decimal number such as 22115678, I received the message. And sender address is changed. What’s the problem? SMPP or Now SMS?  | |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2939 Registered: 08-2008 |
04D01100 is a format that you would use in a raw SMS PDU (if it were technically possible). If I'm decoding it correctly, it is specifying an alphanumeric sender address of the _ (underscore) character. In an SMPP environment, you would specify a sender address of this underscore character. NowSMS would see that it is not a numeric sender address, and it would set the source_ton field to indicate an alphanumeric sender address. If you enter 04D01100 as the sender address, NowSMS will submit that string as an alphanumeric sender address. Since that is failing, perhaps your SMPP server does not allow alphanumeric sender values? If you try different sender addresses for sending normal text messages, do they also have problems if you use a non-numeric sender? The SMPP server might not allow it. -- Des NowSMS Support | |||||
| Johnny New member Username: Johny Post Number: 20 Registered: 02-2009 |
Thank you for your support. I also want to set TON, NPI and send the messge as follow. TON – D (hexa) NPI – 0 Is it possible or not? What are Bind TON,NPI?  | |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2988 Registered: 08-2008 |
Hi Johnny, According to the SMPP 3.4 specification, a TON value of 0x0D is a reserved value. I suspect you actually want to use a value of 5, which is the SMPP addr_ton to indicate an alphanumeric address. In this case, there is no need to set any TON values in the NowSMS configuration. By default, if the sender address is not numeric, NowSMS will use a TON value of 5 ... if the TON configurations are left at their default settings. Bind TON and NPI are values sent in the SMPP bind request only. (In the bind SMPP PDUs, they are defined simply as addr_ton and addr_npi. They are most relevant only if the address_range parameter is being used, but I have seen some SMPP providers that require particular values for no apparent reason.) If you specify a value for any of these TON or NPI parameters in NowSMS advanced settings, NowSMS will use these settings for all messages. (Well, source and destination apply to all messages ... bind is for the bind request only.) If you want to specify a TON of 0x0D, you need to enter it into the NowSMS configuration as a decimal number 13. Beware, however, that a TON of 0x0D is a reserved value in SMPP. I'm also confused because in ETSI GSM 03.40, type-of-number is a 3 bit number, which means that 0x0D is too big to be used as a type-of-number in an actual over the air SMS as well. So let's go back to your raw SMS PDU. In it, you wanted to use a TON/NPI value of 0xD0. Let's look at ETSI GSM 03.40 to see how these values are encoded:  0xD0 = 1101 0000 The high bit is always 1. The next 3 bits (101) are the TON ... or 5. The low 4 bits (0000) are the NPI ... or 0. This leads me back to what I thought you were referring to ... alphanumeric TON, which is 5. If the sender address is an non-numeric string (i.e., alphanumeric), NowSMS automatically uses a source_addr_ton value of 5 and a source_addr_npi value of 0. (Automatic when the TON and NPI settings in the configuration are left at their defaults.) In a raw SMS PDU, those values (TON=5, NPI=0) would be encoded together by the SMSC as 0xD0. If the text that you enter as the "Sender" value is non-numeric, and the NowSMS TON and NPI settings are left at their default, NowSMS should encode the message the way you want it to be encoded when submitting via SMPP. What do you see after the message leaves the SMSC? Maybe the SMPP server or SMSC is not equipped to handle alphanumeric sender? More on how NowSMS chooses default TON/NPI here: http://www.nowsms.com/ton-and-npi-settings-for-smpp-and-ucpemi -- Des NowSMS Support | |||||
| Johnny New member Username: Johny Post Number: 21 Registered: 02-2009 |
Dear sir. I'd like to enter TON&NPI value I want in the "Send binary message" such as "Origination Number" When I set TON/NPI in the SMPP Advanced Configuration Options, All message is applied. In the send binary message form, I want to edit TOM/NPI value, and send them. could you creat TON&NPI field in the "Send binary message?" After creating TON&NPI field, can I receive them to the ME? | |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2998 Registered: 08-2008 |
I'm sorry, you cannot set the TON and NPI explicitly in a message submission. As I have mentioned above, if you leave NowSMS configured to use the default TON and NPI values, the TON and NPI will adjust automatically based upon the "Sender" value. As you have shown in a screen capture earlier in this thread, it is possible to add the "Sender" value when submitting a message. NowSMS will choose the TON and NPI based upon the sender value. If the sender is alphanumeric (or non-numeric), NowSMS will automatically choose a TON value of 5. As I mention in the previous post, SMPP TON value 5, with NPI value 0 ... when the SMPP server creates the raw SMS PDU, it should encode TON=5 and NPI = 0 as 0xD0. (The previous post includes a diagram from ETSI GSM 03.40 that shows how the TON and NPI values get packed together in a raw SMS PDU.) What I am trying to say is that you should be able to accomplish what you want by including the sender address in the message submission. The TON value that you are trying to use (0x0D) is invalid because TON is defined in the SMS specification as only a 3 bit value. -- Des NowSMS Support | |||||
