Is SMS Replace if Present (RIP) supported in v5.51c | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 15, 2006 ⬆ |
◄ ► |
Author | Message | |||
Anne Hughes New member Username: Annehughes Post Number: 1 Registered: 03-2004 |
Up to now we have used NowSMS to receive MMS messages from our messaging application so we can test OTA - very successfully! We have a request for NowSMS to receive SMS messages from an application so we can evaluate SMS RIP. Before I go any further I need help with the following : • Firstly we want to use the SMSC to test SMS Replace if Present (RIP), can you verify if this is supported? Other questions we need answered are: • The messaging protocol used to submit messages (such as SMPP, CIMD, or UCP). NB. SMPP will be fine for us. • Is the port on which it accepts connections the same as defined in smsgw.ini ? (We have SMPPPort=7777 ) • Message segmentation and encoding requirements (if any) - Does the SMSC perform segmentation on long messages? Should the SME Gateway perform segmentation before the message gets to the SMSC? If so, what kind of segmentation should the SME Gateway do? - Is the network GSM or ANSI-based? (I assume GSM based since we are using a GSM modem to send SMS) • Connection timeout periods Any help much appreciated, Anne | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6132 Registered: 10-2002 |
Hi Anne, I assume by "replace if present", you're referring to the "replacement type" values. You can actually access those settings through the web interface. See "This SMS Will Self-Destruct" referenced in the following newsletter: http://www.nowsms.com/newsletter/20060202.htm
You can submit to NowSMS using either SMPP or HTTP. The SMPP port is configured on the "Web" page of the configuration dialog, and this is the port on which SMPP protocol connections will be accepted. (Logins for SMPP are defined under "SMS Users".) Note: When submitting via SMPP, replacement type values are set via the protocol_id value (which corresponds to the GSM PID field). Because of the terminology that you used above, you might be thinking that you should use the SMPP replace_if_present_flag value ... but that setting is only intended to replace an existing message if it is still on the SMSC, not if it is already delivered. (NowSMS does not support the replace_if_present_flag ... you cannot replace a message that is still in NowSMS outbound message queue.)
It is not necessary for the submitting client to perform segmentation, NowSMS will do it. There may be some issues with v5.51c properly supporting SMPP TLV parameters for segmentation. (You should update to v5.51k, a free update at http://www.nowsms.com/download/latestpatch.zip ... or the paid upgrade, NowSMS 2006.)
I assume that you're referring to character set. You can use either, but you should explicitly set the data_coding value to indicate which character set you are using. (I believe we assume GSM if data_coding is left at default.)
In v5.51, I believe there is none. In NowSMS 2006, the default is 60 seconds, meaning that if the connection is idle, you should send an enquire_link at least every 60 seconds to indicate that the client is still alive. (This is good practice anyway.) There is a configuration setting in NowSMS 2006 to alter or disable this timeout. -bn | |||
Anne Hughes New member Username: Annehughes Post Number: 2 Registered: 03-2004 |
Hi Bryce, Many thanks for the comprehensive reply - it answered all our queries. We wanted to test end-2-end using a SMSC that supports RIP - so you've saved us a lot of time. Regards, Anne |