Bryce,, I need your help in 2-way

Bryce,, I need your help in 2-way SearchSearch
Author Message
ahmed r
New member
Username: Ahmader

Post Number: 4
Registered: 04-2004
Posted on Wednesday, May 19, 2004 - 08:48 pm:   

Hello Bryce,
As you suggested before about the WTIA issue we ware talking about .. i moved to another subject and really i think it interested one too. Please i need your help badly.

first let me tell you what im doing, I've one SMPP connection the bind type TRX, which is so hardly i got NowSMS bind in TRX mood, and i still dont know how i did it

this SMPP connection is routed to me by an SP, which will handel more than one country operator. I got rid of my application for SMPP and now i started to use NowSMS for many reason. my applications will be based on 2-Way SMS. I'll receive an MO from the user and i'll process the message to my scripts and then push the MT again to the user.
thats simple what im doing... my problems stand on :
1- the TRX mood whats that and how can i make sure i can do it again. is it (TR) or there is diffrent and how can i bind on (tx-rx) !!

2- you know as i said before about multi countries it means i need to send back the messages from the same Address i received this message. i kept the senderAddress empty ... but what happend its sending back the MT with an empty address.. i've one guy tracing my connection and thats how i could know that issue .. cause the message not deleivring.. so how can i replay from the same sourceAddress.

Thats would be for now .. Please if you can help me fast i'll be so thankful.
ahmed r
New member
Username: Ahmader

Post Number: 5
Registered: 04-2004
Posted on Thursday, May 20, 2004 - 06:55 pm:   

Hello Bryce,
I've got this solve ... i need to know how to check the Binary message which come to me from the user to pass it to my script ... i'm using (@@FULLSMS@@) and its passing something like this %D8%B3 ... i need the UCS which im getting (100%) in the SMS_IN file as (0633) ...
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2653
Registered: 10-2002
Posted on Tuesday, May 25, 2004 - 06:33 pm:   

Hi Ahmed,

What you are receiving "%D8%B3..." is the message in UTF-8 encoding.

UTF-8 encoding is a standard for transmitting Unicode data using 8 bit characters. So depending on what environment you are working in, there is hopefully a function to convert UTF-8 into the character set that you prefer to work with.

There is also a configuration option that you can use to tell NowSMS to use a character set other than UTF-8 for transmitting text to a 2-way command. Edit SMSGW.INI, and under the [SMSGW] section header, add ReceiveSMSCharset=xxxxx, where xxxx is a valid character set name (such as iso-8859-1 for the standard Western European character set, iso-8859-6 for Arabic, big5 or gb2312 for different Chinese encodings).

Unfortunately, there is no an option to send it in UCS2.

-bn
ahmed r
New member
Username: Ahmader

Post Number: 6
Registered: 04-2004
Posted on Friday, May 28, 2004 - 03:54 pm:   

Hey BN,

Thanks allot man i donno what to do with out you in this forum and with this great application, I fixed the pervious issue im having, by both ways you suggested.
1- by converting the UTF-8 to a valid charset, which is by the way took me hours to find it out with ASP/IIS4/WIN2K for others to be able to do it use this code in the top of your ASP page:
<%@ language="vbscript" codepage=65001 %>
<% Response.CharSet = "UTF-8" %>
and then use the function : ascw() to get the ascii code for the char. hope im helpful engouh.
2- its easy no need to commet.

ok BN on more issue : (you know i never stop)
My operator's SMPP connection allow me to send 5 MT per second. so when i use the DList option to push bulk MT i get this in the logs:

xxxxxxxxx123,OK -- SMPP - xxx.xxx.xxx.xxx:xxxx,Binary=1;DCS=8;Data=062C
xxxxxxxxx124,OK -- SMPP - xxx.xxx.xxx.xxx:xxxx,Binary=1;DCS=8;Data=062C
xxxxxxxxx125,OK -- SMPP - xxx.xxx.xxx.xxx:xxxx,Binary=1;DCS=8;Data=062C
xxxxxxxxx126,OK -- SMPP - xxx.xxx.xxx.xxx:xxxx,Binary=1;DCS=8;Data=062C
xxxxxxxxx127,OK -- SMPP - xxx.xxx.xxx.xxx:xxxx,Binary=1;DCS=8;Data=062C
xxxxxxxxx128,Retry Pending - ERROR: Timeout waiting for response from server or lost connection -- SMPP - xxx.xxx.xxx.xxx:xxxx
xxxxxxxxx128,OK -- SMPP - xxx.xxx.xxx.xxx:xxxx,Binary=1;DCS=8;Data=062C
xxxxxxxxx129,OK -- SMPP - xxx.xxx.xxx.xxx:xxxx,Binary=1;DCS=8;Data=062C
xxxxxxxxx131,OK -- SMPP - xxx.xxx.xxx.xxx:xxxx,Binary=1;DCS=8;Data=062C
xxxxxxxxx132,OK -- SMPP - xxx.xxx.xxx.xxx:xxxx,Binary=1;DCS=8;Data=062C
xxxxxxxxx133,OK -- SMPP - xxx.xxx.xxx.xxx:xxxx,Binary=1;DCS=8;Data=062C
xxxxxxxxx134,Retry Pending - ERROR: Timeout waiting for response from server or lost connection -- SMPP - xxx.xxx.xxx.xxx:xxxx
xxxxxxxxx134,OK -- SMPP - xxx.xxx.xxx.xxx:xxxx,Binary=1;DCS=8;Data=062C

so its sending the pending MT again, but can i specify the number of MT per second ?
thanks man and regards.
ahmed r
New member
Username: Ahmader

Post Number: 8
Registered: 04-2004
Posted on Thursday, June 03, 2004 - 03:51 pm:   

Hello Bn,

waitting for your answer, and couple of issues,
1- Can i get any uniqe id for the MO message, so while proccess it my application wont proccess it twice in case any pendding problem.

2- While getting an MO the MSISDN (@@SENDER@@) it is include a + sgin how can i remove it.. anywise i did remove it from the application but its everywhere :-(

3- When i send a campgine for lets say 2500 users it take from me around 10 mins as per the pervious thread (5 MT/SEC) so while browsing the Discussion Board i found away to add multi connection for the same SMPP the (ETC/HOSTS) things.. so it works with me fine now i added 3 connections two only for sending and one for sending/receiving so now im sending around 15 MT/sec WoOoOoW but the thing is still pendding messages so my issue i need to send the bulk via one smpp and the requests be immeditly fire out with out waiting for the q to finish
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2681
Registered: 10-2002
Posted on Friday, June 04, 2004 - 05:47 pm:   

Hi Ahmed,

Apologies for the delay in getting back to you. I had to take some time off, and my tech support backup had so much extra work that he couldn't get out to this discussion forum on a regular basis.

On the 5 messages per second issue, I asssume you're working with a trial version.

The trial version is limited to 30 messages per minute. However, our throttling for this condition was only on a per minute basis. We would try to submit as many messages as we could, as fast as we could, until we hit that limit of the 30 messages within a single minute.

But that doesn't work so well with many SMSC connections which limit the number of messages submitted per second, and don't handle this gracefully. (Terminating the connection, as shown in your log is definitely not graceful handling.)

So I suspect you're running a version prior to v5.50. If so, update to v5.50. In it, if the NowSMS license is less than or equal to 1 message per second, we make sure that we don't send more than 1 message per second. (With the 30 messages per minute limit, you'll see approximately 1 message per second for 30 seconds, then a 30 second pause.)

On the newer issues ...

1. Hmm. I'm trying to think if there is something that we could add here. I suppose we could add a "@@MESSAGEID@@" replaceable parameter. However, this would be our id, and not the id from the SMSC, so it would not catch if the SMSC was resending a message for some reason. (But this would help situations where NowSMS doesn't like the response back from your script, and it keeps retrying a message.)

2. We pass along the value the way that it comes in to us from the SMSC. And if it the SMSC says it is in international format, then we put in the plus. I'd be hesitant to make any changes in this area, and hopefully you can handle this in your scripts.

3. Specify a different sender address for one or more of the connections. When you submit messages that you want to route only those connections, include a "Sender=" parameter that matches the "Default Sender Address" that is configured for that SMSC connection.

When NowSMS sees a sender address associated with a message submission, it looks for an SMSC definition with a matching sender address. If it finds at least one match, then the message will only be routed through an SMSC with a matching sender address.

-bn
ahmed r
New member
Username: Ahmader

Post Number: 9
Registered: 04-2004
Posted on Friday, June 04, 2004 - 06:40 pm:   

Thanks Bn,

Your really helping allot,

first my NowSMS is v5.50 ant not trail. how can i know how many sms/sec for outgoing ?

"@@MESSAGEID@@" is not working with me, is it a new parameter your talking about or its already there ?

and about sender id, in my case all 3 smpp connections are using the same sender id and i cant leave it blank. any suggestion ?

Thanks again man and hope ot hear from you soon, as i replayed after your replay with 10 min
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2717
Registered: 10-2002
Posted on Monday, June 07, 2004 - 08:27 pm:   

Ahmed,

Please e-mail me (nowsms@now.co.uk) with your serial number information, and I will advise.

@@MESSAGEID@@ is a parameter that we are adding to address this issue. I can send you a beta update that adds this parameter if you send me an e-mail with the above information.

On the other issue, unfortunately, if the sender is the same on all of the connections, we don't have a way for handling this. It is an issue that we are trying to address in a future version, but we do not yet have a solution.

-bn
cjegadees
Unregistered guest
Posted on Tuesday, July 06, 2004 - 09:33 am:   

hi
i want to connect my ASP application with nowsms gateway. Please explain how can i do this?

i am new to this nowsms. explain both gateway side and application side

if anyone knows please mail me
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2996
Registered: 10-2002
Posted on Wednesday, July 07, 2004 - 08:52 pm:   

For submitting a mesasge to NowSMS, you basically issue an HTTP request.

I'm not as familiar with this process using ASP as with HTTP, but there are some links that might help you in the following thread:

http://support.nowsms.com/discus/messages/1/252.html

Basically, you issue HTTP requests from within your script to trigger messages to be sent:

http://www.nowsms.com/documentation/ProductDocumentation/sending_messages/sendin g_text_messages.htm
http://www.nowsms.com/documentation/ProductDocumentation/sending_messages/url_pa rameters_for_sending_messages.htm

For receiving SMS, here is a real simple example with an ASP script:

http://support.nowsms.com/discus/messages/1/4420.html