| Wireless messaging API SMS port |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through January 23, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Loke Peng Fai New member Username: Rwalker Post Number: 1 Registered: 10-2006 |
My applicationis is using SMPP to communicate with NowSMS 5.5.1. I have a problem using sms port as specified in http://www-106.ibm.com/developerworks/java/library/wi-p2pmsg/ In the old archeive (2004), a similar problem is raised and Bryce said future NowSMS may support SMPP 'destination port'. How about v5.5.1? Will NowSMS v5.5.1 convert the SMPP 'destination port' to proper format in UDH header? If not, what can I do assuming I can only use SMPP to interface with NowSMS and not web interface? Is my understanding listed below correct?: set 'ems_class" to "0x40" set encoding = 8 append "0x06050462226222" (3.5 bytes) infront of the message text, where 0x6222 is the source/destination port Is the setting/work around above generic and can be applied when interacting with a real SMSC? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6691 Registered: 10-2002 |
Hi, I don't know for certain about NowSMS v5.51 behaviour in this regard. But I do know that NowSMS 2006 supports TLV parameters for source and destination port on connections from SMPP clients. So you would just set the SMPP TLV destination port parameter, and you could encode your text as you would sending a regular text message. The alternative way (if the TLV parameter for destination port is not supported) would be as you describe ... but here are some considerations: data_coding would only be 8 if the message text is in Unicode format. If the message text is not in Unicode format, then you can encounter some confusion. When UDH is present, most versions of NowSMS expect any non-Unicode text to be packed into 7-bit format. (NowSMS 2006 expects non-Unicode text to be in normal 8-bit text format when UDH is present, but it will attempt to auto-detect situations where the text has been packed into 7-bit format.) Is any of this generic for interacting with a real SMSC? Well ... when NowSMS connects to an SMPP SMSC, we have a variety of different configuration settings to control whether or not we use TLV ... whether or not text is packed when UDH is present. Basically, the SMPP specfication is too ambiguous, so in the real world, some of these different options have been implemented differently by different providers. Our experience is that using the UDH in front of the message text (with text in standard 8-bit format) is most widely supported. You may want to try the v5.51k patch for NowSMS, which can be downloaded at http://www.nowsms.com/download/latestpatch.zip. NowSMS 2006, of course, is the download available from the "Free Trial Version" link on the web site. -bn | |||
| Wu Jiong Hui New member Username: Jionghui Post Number: 1 Registered: 11-2006 |
Hi Bryce, Do you know how to set SMPP TLV destination port parameter in NowSMS? Shall I edit SMSGW.INI? Is there any user guide for this configuration? Best Regards, Jionghui | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6784 Registered: 10-2002 |
Hi Jionghui, When you define an SMPP connection in NowSMS, there is an "Advanced Settings" button. One of the configuration options is "Use TLV parameters for port numbers and segmentation". When this option is checked, NowSMS uses the TLV paramters for source/destination port and segmentation, instead of generating the GSM UDH (user data header). -bn | |||
