SMS sending problem

SMS sending problem SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through July 14, 2004 » SMS sending problem « Previous || Next »
Author Message
DEEP
Unregistered guest
Posted on Monday, June 28, 2004 - 04:29 pm:   

Hi,

I have downlowded and tested NowSMS with Clickatell service by Http integration, and found a single diference in sending sms trought NowSMS and directly from Clickatell web interface.

If i send a unicode string with over 70 Character using NowSMS web interface (wich tells me that will send 2 SMS) i will be charged by clickatell 2 credits (as for 2 SMS), But if i use the same string and send the SMS by the web interface provided by Clickatell services i will be charged only one credit.

Can you please explain what im doing wrong, is it possible to configure NowSMS to not break the message in to 2 SMS.

Example of the string im using contains characters like € â ã ç & #, and both arrive correctly on the GSM phone as one message, but from Nowsms costs me 2 SMS and from clickatell only one.

Can you help on this?

Best regards,
NDL
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2930
Registered: 10-2002
Posted on Monday, June 28, 2004 - 06:22 pm:   

Hi NDL,

It sounds like Clickatell might not realise that they are offering a bargain.

Are you connecting NowSMS to Clickatell using SMPP or HTTP?

There is an option in the HTTP setup, where you can check "Send Long Messages without Segmentation". This means that we don't do the segmenting of the message, and pass all of the data in one request (letting the service provider perform the segmentation).

-bn
DEEP
Unregistered guest
Posted on Tuesday, June 29, 2004 - 10:18 am:   

Hi Bryce,

We are using Http integration to clickatell, this are the strings we are using:

URL for text:"/http/sendmsg?api_id=xxxxxx&user=@@UserName@@&password=@@Password@@&to=@@P honeNumber@@&text=@@Text@@&from=@@Sender@@"

URL for Binary: "/http/sendmsg?api_id=xxxxxx&user=@@UserName@@&password=@@Password@@&to=@@PhoneN umber@@&udh=@@UDH@@&text=@@Text@@&from=@@Sender@@&unicode=1"

I have checked the option "send long messages without segmentation" and no messages are delivered from the nowsms gateway to clickatell!!!

Is something wrong with the string?

Apreciate you help, thank you Bryce
Regards,
NDL
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2939
Registered: 10-2002
Posted on Tuesday, June 29, 2004 - 07:57 pm:   

NDL,

Oops. It looks like that feature is not working like it supposed to.

Give me a day or two to investigate this more fully.

-bn
DEEP
Unregistered guest
Posted on Friday, July 02, 2004 - 11:28 am:   

Hi Bryce,

Any news on the "send long messages without segmentation" situation?

Best regards
NDL
DEEP
Unregistered guest
Posted on Monday, July 05, 2004 - 02:30 pm:   

Hi Bryce,

Sorry to bother again, but we need to test the segmentation feature to make some internal options, do you have any news?

Best regards
NDL
DEEP
Unregistered guest
Posted on Tuesday, July 06, 2004 - 02:34 pm:   

Hi again,

Any news on the segmentation issue Bryce.

Sorry, but i have confirmed several times that sending the same string with euro and other portuguese character from clickatell interface only uses 1 sms for more than 70 characters, but using the same string with nowsms costs 2 sms and there for whebn delivered to clickatell trought http connection it costs 2 sms.

Please help, we are at a stand and need a quick solution

best Regards
NDL
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2978
Registered: 10-2002
Posted on Wednesday, July 07, 2004 - 02:54 pm:   

Hi NDL,

It has taken us awhile to work through this issue, but the "Send long messages without segmentation" issue has been fixed.

There is an update that can be downloaded at the following URL:

http://www.nowsms.com/download/nowsms550c.zip

I have not tried this against Clickatell, so please advise how it works for you.

-bn
DEEP
Unregistered guest
Posted on Wednesday, July 07, 2004 - 09:18 pm:   

Hi Bryce,

I have downloaded and tested the new release but even with the options send without segmentation it costs me 2 sms to send the string with nowsms.

Is it possible to send the message without breaking it in to 2 SMS when using unicode string over 70 characteres?


If i send this string "teste com € e com mais o simbolo ç e mais â emais à e mais % até fazer mais de 70 caracteres." with 93 caracteres directly from clickatell http interface... it costs me 1 credit (1 SMS).

If i use the same string and send the message from NowSMS connected to clickatell by Http integration it costs me 2 credits (as in 2 SMS).

But both messages arrive at the mobile phone as one message.

Im sending messages to Portugal mobile network, do you think its possible to do something about this?

I would apreciate it very mutch.

Best Regards
NDL

DEEP
Unregistered guest
Posted on Thursday, July 08, 2004 - 07:46 pm:   

Bryce,

Im so desperate....

regards,
NDL
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 3019
Registered: 10-2002
Posted on Friday, July 09, 2004 - 06:39 pm:   

Hi NDL,

I don't think Clickatell realises what is occurring. At the end of the day, that message would need to go out over the network as 2 messages (to preserve characters "ç" and "â" which are only available with Unicode encoding).

The "Send Long Messages without Segmentation" setting in NowSMS is working correctly. I see that when I enable this setting, we send it out to the SMSC in a single request. But I suspect that Clickatell sees that this requires 2 messages, whereas their parsing engine doesn't realise that when that particular message is submitted as text, it also requires 2 messages (and they just charge you for 1).

I see we are sending it out as a Unicode binary string. I've been thinking for awhile that we could use support for a separate Unicode URL template when connecting to an HTTP based SMSC.

But I'm not sure that would help you.

What encoding are you using when you submit the above text directly via HTTP? Are you putting the special characters directly in the URL, or are you encoding them in some way?

I'll see if there's something that we can do ... but I also expect that once Clickatell realises this bug, they'll probably be fixing it shortly as well.

-bn

Login Login / Register Logout Logout Search Last 30 Days Topics Topics