| Send port directed SMS |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through January 23, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Junqing Xie New member Username: Pwd Post Number: 1 Registered: 01-2007 |
I am using NowSMS 2006 (v.2006.03.09) with aircard 860 to send SMSes. And now there is a requirement to send port directed SMS, i.e., send the SMS to an application running on cell phone, which is listening on a specific port. The interface between the sending program and NowSMS is SMPP. How can I do such sending? Is it enough to just set the optional parameters 'destination_port' and 'source_port' in SubmitSM request? | |||
| Malcolm - Now Support Moderator Username: Malcolm Post Number: 85 Registered: 12-2006 |
Yes, you can use the optional TLV parametersf or source_port and dest_port in the SMPP message submission. -- Malcolm Now Wireless Support | |||
| Junqing Xie New member Username: Pwd Post Number: 2 Registered: 01-2007 |
Malcolm, Thanks for the reply! :-) My further question is that when NowSMS 2006 receives the SubmitSM request with source_port and dest_port, it will create a UDH with the ports automatically and send the SMS as a binary SMS through aircard to the cell phone. Is my understanding correct? If that is correct, when the text message body is too large, will NowSMS split it into multiple port directed SMS to the cell phone? Or NowSMS just send the first portion of the message body with the maximum size allowed in one SMS (except for the UDH size)? Thanks, Junqing | |||
| Malcolm - Now Support Moderator Username: Malcolm Post Number: 96 Registered: 12-2006 |
Hi Junqing,
Yes.
My tests suggest that NowSMS does not handle this scenario correctly, and the result is the sending of a corrupt message. It will work properly if you segment the message, and use the sar_msg_ref_num, sar_total_segments, and sar_segment_seqnum parameters. In this scenario, you would have to keep your message text to less than 152 characters for a single part message, and for multipart messages, no more than 145 characters per segment to allow for UDH overhead. That said, the problem is very similar to the one described in the following thread: http://support.nowsms.com/discus/messages/1/19585.html And I have not yet had a chance to test this scenario with that update. (I ran these tests earlier today before getting my hands on this update, and have not had time to retest with the update yet.) This update did fix a similar encoding problem for a long text message with UDH submitted via the web interface, so it may also fix this for similar messages submitted via SMPP. -- Malcolm Now Wireless Support | |||
