| NowSMS and Quios |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through October 19, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Never Better New member Username: Waleedshahin Post Number: 3 Registered: 11-2004 |
Hello, I would like to know if NowSMS compatible with Quios SMSC. Quios SMSC supports SMPP and it needs to set the SMPP attributes to special values, Can we support modifying ALL values to send SMS messages. I know that NowSMS supports most of them, but does it all of them with their values. Example see below: service_type => 0, source_addr => '14155556666', source_addr_ton => 0, source_addr_npi => 0, destination_addr => '14155556666', dest_addr_ton => 0, dest_addr_npi => 0, esm_class => 0x00, protocol_id => 0x00, priority_flag => 0x00, schedule_delivery_time => '', validity_period => '', registered_delivery => 0x10, replace_if_present_flag => 0x00, data_coding => 0xf1, sm_default_msg_id => 0x00, short_message => 'test message', sm_length => 12 More information, http://www.quios.com/docs/SMPP_interface_1.0_tech_spec.pdf Kind Regards, | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7157 Registered: 10-2002 |
Hi, I don't have any specific information on that SMSC, but based upon the specification that you've included, it's pretty basic stuff. The only things that look unusual are: registered_delivery => 0x10 That value indicates that you are requesting intermediate message delivery notifications, but not final delivery notification. Similarly, the examples in their documentation for having delivery notification on or off are weird values. According to the specs, generally you would set this value to 1 if you want a delivery receipt for when the message is delivered or fails. And you would set this value to 2 if you want a delivery receipt only in the case of failure. 0 means no receipt is requested, and that is the default. We do have ways of setting the above two values. Normally, if you were submitting via HTTP, you would include "&ReceiptRequested=Yes" to set this value to 1. The HTTP interface does not support a parameter to set the value to 2. However, it is possible to configure a particular SMPP interface to always use a value of 1 or 2. Under the [SMPP - host:port] section of SMSGW.INI, you can set DefaultDelReceipt=Yes for 1, or DefaultNonDelReceipt=Yes for 2. Requesting the intermediate delivery notifications generally doesn't add any value, other than maybe letting you know that the SMSC is still trying. But basically, there is no guarantee when the SMSC will generate one of these intermediate notifications. So I have a hard time seeing the value. I can't imagine that this provider requires that you use a value of 0x10. If necessary, it'd be easy for us to add a configuration option to allow this ... but at this time, I just don't see the need. data_coding = 0xF1 is also unusual. Basically, it just means that you are setting the GSM message class of the message to 1 (mobile equipment specific). If submitting via HTTP, to set this parameter, you must include "&DCS=F1" in the URL. There is no way to force this value as a default. -bn | |||
