| User_message_reference |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through October 31, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Hugo Cabrera New member Username: Hcabrerah Post Number: 1 Registered: 06-2007 |
How can i configure that, all ESME messages to SMSC (submit_sm) should include user_message_reference, a sequencial number between 0000 and FFFF, not initializing with the same number to avoid two messages with the same value | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7176 Registered: 10-2002 |
Hi, We do not have any support for doing that. It could be added as an option with relative ease ... but I would want to understand better why this is needed for your configuration before I put the request into the development queue. -bn | |||
| Hugo Cabrera New member Username: Hcabrerah Post Number: 2 Registered: 06-2007 |
I suppose that the objective is a messages control that was sent from the ESME to the SMSC for billing information. i read post that especifes this cofiguration [SMPPOptions] user_message_reference=204,Integer,2 With this setting present is enough or it has another objective | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7192 Registered: 10-2002 |
Hi Hugo, When you put that setting in the SMSGW.INI, it allows you to specify a user_message_reference value when you submit a message to NowSMS ... and includes this parameter when the message is submitted to an SMPP server. But it doesn't automatically generate a value for this parameter. Basically, include "&SMPPOption_user_message_reference=#####" in the URL request when submitting the message in order to specify a value. In this case, the ##### value for this parameter would be decimal, so you would could specify a value between 0 and 65535 here. -bn | |||
| Hugo Cabrera New member Username: Hcabrerah Post Number: 3 Registered: 06-2007 |
Hi Bryce, then, this option could be added : include user_message_reference, a sequencial number between 0000 and FFFF, not initializing with the same number to avoid two messages with the same value | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7208 Registered: 10-2002 |
Hi Hugo, Hmm...the only problem that I see with adding this is ... wouldn't you want to have some way of knowing what user_message_reference value is assigned to each message? If we just assigned a new value on each message submission, it wouldn't necessarily mean anything to you. So it would be relatively easy to do ... but as you wouldn't see these values logged anywhere (only transmitted via SMPP), I'm just not sure that we've actually accomplished anything. That's why I'm asking questions ... I want to make sure that before we actually commit any development time to it, that the end result will actually accomplish something worthwhile. Is the reason you are asking for this "because this is what the SMS service provider we are connecting to requires" ... then that's an ok answer, just let me know. My main concern is that if we implement it the easy way, I'd want to be sure it actually met your needs. -bn | |||
| Hugo Cabrera New member Username: Hcabrerah Post Number: 4 Registered: 06-2007 |
Hi Bryce, it´s a requirement of the SMSC service provider (Movistar - Peru) that the ESME sends user_message_reference: a sequencial number between 0000 and FFFF, not initializing with the same number to avoid two messages with the same value it is an item of the contract. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7215 Registered: 10-2002 |
Hi Hugo, Ok ... now I understand clearly. Let me take this back to development, hopefully this will not take too long to implement. -bn | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7262 Registered: 10-2002 |
Hugo, I've uploaded an update that has a configuration setting which allows this user_message_reference to be assigned automatically. Initially it will start at 0 ... and increment from there. Eventually it will reach 0xFFFF (65535), and then it will go back to 0. There is no way to avoid two messages with the same value if you send more than 65536 messages, because this parameter only allows 65536 different values. It will remember the last used value between connections, so when the connection is reinitialised, it will not start over at 0 each time. The update can be downloaded at http://www.nowsms.com/download/nowsms2007.zip. To enable this feature, you need to manually edit SMSGW.INI, and under the [SMPP - host:port] section for your provider, add GenerateUserMessageReference=Yes. -bn | |||
| Hugo Cabrera New member Username: Hcabrerah Post Number: 5 Registered: 06-2007 |
Hi Bryce, thank you for the update... today I begin the test connection with my service provider they especify me than i have this billing configuration: MO --DEFAULT-- 0,00 MT Free 0,00 MT --DEFAULT-- 0,99 How and where i configure this especification in nowsms? thanks | |||
| Hugo Cabrera New member Username: Hcabrerah Post Number: 6 Registered: 06-2007 |
Hi bryce, continuing the previous post; can i specify MT indicating free or default? my service provider indicate me that i should be especify the service_type (to know if the MT is free or default) please help me | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7337 Registered: 10-2002 |
Hi Hugo, I do not understand what parameters they expect you to configure for this:
MO means mobile originating (SMS sending from the mobile). MT means mobile terminating (SMS being received by the mobile). In other words, there is not an MO or MT parameter value that you can set. So I assume that they are asking you to set a particular parameter to specify a value, but I don't know what parameter they want you to set. Some SMS providers use custom parameters that have to be defined in the [SMPPOptions] section of SMSGW.INI. Some SMS providers use the service_type parameter. Basically, you need to get more detail before I can offer any advice. -bn | |||
| Hugo Cabrera New member Username: Hcabrerah Post Number: 7 Registered: 06-2007 |
Hi Bryce, my question is about service_type configuration per message. this post is similar http://support.nowsms.com/discus/messages/1/3619.ht ml How and where i configure service_type per message in nowsms? | |||
| Malcolm - Now Support Moderator Username: Malcolm Post Number: 206 Registered: 12-2006 |
The SMPP service_type parameter can be set on a per message basis by including "&ServiceType=XXX" in the URL submission. | |||
