Sending sms using spesific port

Sending sms using spesific port SearchSearch
Author Message
Rusdy Heriyanto
New member
Username: Rusdy

Post Number: 1
Registered: 01-2007
Posted on Friday, January 12, 2007 - 05:41 am:   

Dear friends,

I'm interested to replace my own sms gateway with nowSMS.

Is there any issue if I send sms to a spesific port?

Currently I use spesific port to avoid sending sms to the normal sms inbox since it can be read by my application (installed on mobile phone) only.

Thank in advance.

Rgds
Malcolm - Now Support
Moderator
Username: Malcolm

Post Number: 102
Registered: 12-2006
Posted on Friday, January 12, 2007 - 06:48 pm:   

Are you using SMPP or HTTP?

If you are using SMPP, you can use the optional TLV parameters for source_port and/or dest_port.

If you are using HTTP, you need to include the corresponding UDH (user data header), which is 060504xxxxyyyy where xxxx is the source port and yyyy is the destination port. (In your HTTP submission URL, include "&UDH=060504xxxxyyyy" in the URL. For testing purposes, use the "Send Binary Other" web form, insert the UDH into the appropriate field, and in the "Binary Data" field put in your normal text ... NowSMS will detect that it is text rather than a binary hex string.)

--
Malcolm
Now Wireless Support
eragon
New member
Username: Eragon

Post Number: 5
Registered: 12-2006
Posted on Monday, February 26, 2007 - 11:19 am:   

Pls, I have tried this by setting the clicking the "Use TLV for port number and segmentation" and I sent an ordinary text message but it never came to my application that is listening, it went straight to my inbox.

Pls, can u help out, I am uconnect thru NowSMS to my GSM operator's SMPP server. I have tried to send to a port thru phone modem usin NowSMS and the application received it.
eragon
New member
Username: Eragon

Post Number: 6
Registered: 12-2006
Posted on Monday, February 26, 2007 - 03:26 pm:   

I am conencted to my GSM operators SMPP connection. How do I use the optional TLV parameters for source_port and/or dest_port?

How can I achieve this.

I will like to send using the http://nowsmsgateway:8800/**************

Pls help.

Rgds
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6958
Registered: 10-2002
Posted on Wednesday, March 07, 2007 - 10:07 pm:   

Hi,

Malcolm's suggestion above was not to check the "Use TLV for port number and segmentation" setting in the SMPP connection. That setting controls how NowSMS will signal the SMSC that a message should be sent to a particular port number. By default, NowSMS uses GSM UDH. This setting tells NowSMS to use SMPP TLV parameters instead.


quote:

Pls, I have tried this by setting the clicking the "Use TLV for port number and segmentation" and I sent an ordinary text message but it never came to my application that is listening, it went straight to my inbox.




If you send an ordinary text message, NowSMS has no way of knowing that you intended for it to be sent to a specific port address.


quote:

I am uconnect thru NowSMS to my GSM operator's SMPP server. I have tried to send to a port thru phone modem usin NowSMS and the application received it.




Ok ... if it works ok sending via a modem, then I assume that you are submitting the message to NowSMS including a UDH parameter for the port addressing, right?

The same technique should work if you are using an SMPP connection.

However, some SMPP servers may expect to see UDH ... and some may expect to see the "dest_port" setting in the optional TLV parameters. There is also an issue that if UDH is used, some SMPP servers may expect the text of the message to be 7-bit encoded, others may expect 8-bit encoding.

So here are the different "Advanced Settings" that you should try (be sure at all times to include the port addressing when you submit the message to NowSMS, just like you do when submitting to NowSMS for going out the modem):

1.) Check "Use TLV parameters for port numbers and segmentation".

What happens? Does the message go to the regular inbox? Is the message in the inbox garbled or plain text?

2.) UNcheck "Use TLV parameters for port nubmers and segmentation".
UNcheck "Encode long text messages with 7-bit packed encoding".

What happens? Does the message go to the regular inbox? Is the message in the inbox garbled or plain text?

3.) UNcheck "Use TLV parameters for port nubmers and segmentation".
Check "Encode long text messages with 7-bit packed encoding".

What happens? Does the message go to the regular inbox? Is the message in the inbox garbled or plain text?


---

Assuming that in all cases, the message goes to your inbox instead of to your application ... (and regardless of whether the text is garbled or not) ... then it is likely that we need advice from your SMPP provider on how they support destination port addressing.

The only two techniques that we are aware of is the use of GSM UDH parameters, or the use of the dest_port optional TLV parameter. (It is also possible that your provider needs to set

-bn