Source_subaddress | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through June 21, 2007 ⬆ |
◄ ► |
Author | Message | |||
tim 1980 New member Username: Tim1980 Post Number: 1 Registered: 01-2007 |
Hi, I connected to Sfone SMSC, they want us to set the Optional parameter source_subaddress, how could i configure NOWSMS for that? Thanks, | |||
Malcolm - Now Support Moderator Username: Malcolm Post Number: 156 Registered: 12-2006 |
Hi, You would need to use the "SMPPOptions" settings to enable additional parameters. The following thread talks about doing this for an optional parameter called "user_message_reference" ... but it should still be helpful: http://support.nowsms.com/discus/messages/1/13585.html For the "source_subaddress" parameter, you would use the following setting: [SMPPOptions] source_subaddress=202,String --- Malcolm Now Wireless Support | |||
tim 1980 New member Username: Tim1980 Post Number: 2 Registered: 01-2007 |
Thanks Malcolm. But SMSC wants us to put source_subaddress with the value 0202 000C A03834393538393030383836. The 3834393538393030383836 is a dest number. I tried but couldn't put the value like this. Can you help me? Thanks for your supports. | |||
Malcolm - Now Support Moderator Username: Malcolm Post Number: 158 Registered: 12-2006 |
Hi Tim, The trick would appear to be getting the "A0" part of the string in place. The "0202" and "000C" would get generated automatically. ("0202" being the code for source_subaddress" and "000C" being the length of the field.) If you were submitting to NowSMS via the web interface, and you had the [SMPPOptions] section set in your SMSGW.INI file, then you could append the following to an HTTP request: &SMPPOption_source_subaddress=%A084958900886 When you submit via URL, %xx is the syntax that is used to specify a hex character value. So I used %A0 at the start of the string. For the rest of the string, "38" is the hex code for the ASCII character 8, so I expressed the remaining characters using standard ASCII. Alternatively, if you wanted to submit using the hex encoding, you could append this to the URL: &SMPPOption_source_subaddress=%A0%38%34%39%35%38%39%30%30%38%38%36 Does the SMSC always want the destination address for the phone number to be encoded in this source_subaddress field? If so, then we could look at adding a special configuration setting to do this automatically. It's an unusual requirement, but we've done similar things to meet unusual requirements in the past. -- Malcolm Now Wireless Support |