Problem connection with SMMP over TCP/IP connection to SMSC

Problem connection with SMMP over TCP/IP connection to SMSC SearchSearch
Author Message
iwansuryaputra
Posted on Wednesday, July 23, 2003 - 05:46 pm:   

Hi All

I need help about SMPP connection to SMSC , After i input Host IP address, Port , User name and Password assign by operator I got this windows message : "Unable to logging to SMPP server with specified parameters. ERROR : Bind Failed

Please help me , Thank you

Best Regards
Iwan
Bryce Norwood - NowSMS Support
Posted on Thursday, July 24, 2003 - 01:17 pm:   

Hi Iwan,

This means that the SMPP server rejected the username and password that you supplied. (It was able to connect to the server, but it received an SMPP response that rejected the login.)

Make sure that you are using the correct username and password.

If there are IP address restrictions on your account, make sure that you are authorised to login from the PC that is running the NowSMS gateway.

You could try changing the SMPP version, and see if that makes a difference.

For some SMSCs, you may want to try setting the "System Type" field to "VMA".

Unfortunately, if neither of these works either, you'd have to check with your service provider to determine why they are rejecting the connection.

-bn
Iwan Suryaputra
Posted on Friday, July 25, 2003 - 06:26 am:   

Dear : Bryce

Thank you for the support, i manage to connect smpp to smsc now.
But now i cannot sent the message from web interface , when i take a look at the event log :
Warning SMS can not be sent to 08557875758, ERROR invalid destination address NPI
How to solve this problem ?
The operator also give me the virtual smsc number , where i must input this parameter?

Thank you the help.

Rgds
Iwan S
Anonymous
Posted on Friday, July 25, 2003 - 08:11 am:   

Where do i input these parameters:
Ton=1 npi=1 destination npi=1 dest npi=1 source ton=0 source npi=1
Anonymous
Posted on Friday, July 25, 2003 - 11:54 pm:   

There are some fields which we can configure in other SMPP products. I cannot find in NowSMS version yet.. Still looking..

SMPPS.AddressTON = 1
SMPPS.AddressNPI=0

Message.SourceAddressTON = SMPPS.AddressTON
Message.SourceAddressNPI = SMPPS.AddressNPI
Message.DestAddressTON = SMPPS.AddressTON
Message.DestAddressNPI = SMPPS.AddressNPI
Bryce Norwood - NowSMS Support
Posted on Monday, July 28, 2003 - 09:17 pm:   

Hi Iwan,

Sorry for the delay getting back to you.

We set the TON to "1" or "0" depending on whether or not the corresponding address is in international format.

If the sender or recipient address starts with "+", then TON is set to "1" (and the "+" stripped off before submitting to the SMSC).

NPI is always set to "1". However, we did have a bug in the original v4.20 release where the NPI was set to "0" by default.

Most systems, if they care about NPI at all want it set to "1".

There is a fixed version of v4.20 available for download at the link http://www.nowsms.com/download/nowsms420a.exe. You can download that file and install over your existing copy, and I suspect that will resolve your problems.

In the v5.0 release (which is still in beta), we have made the TON and NPI configurable. In the SMSGW.INI file, under an [SMPP] section header in the file, the following parameters are supported:

SourceNPI=
SourceTON=
DestNPI=
DestTON=

I contend that aside from this bug in our v4.20 release, there's usually not a need to manually set any of these settings.

Information about (and a link to the download of) the v5.0 beta can be found at http://www.nowsms.com/beta5.

-bn
Iwan Suryaputra
Posted on Friday, August 01, 2003 - 01:25 pm:   

Hi Bryce

Thank your support .We successfully connetted to SMSC.
Today i encounter another problem with sending the ringtones , our ringtones binary more then 280 byte ( characters ) mean it should be sent in 2 part . How to make it otomatically send a long binary in 2 part or more ?
Thank you for the support .

Best Regards
Iwan Sp
Bryce Norwood - NowSMS Support
Posted on Friday, August 01, 2003 - 04:28 pm:   

Hi Iwan,

How are you submitting the ring tone?

If you submit a binary to us that is longer than 140 bytes, we automatically add the appopriate concatenation headers. (Of course, you can also do it yourself if you want.)

What is the data that you are submitting, and how are you submitting it to NowSMS?

-bn
iwan suryaputra
Posted on Saturday, August 02, 2003 - 09:15 am:   

Hi Bryce

This is the binary i sent :
0B0504158100000003350201024A3A5D2161194CB4C4DC041F491ED5966166156136156248D16462 92B4211511A188A48D14622B22C491A28E452468B2312AC493A2C9C526284227284224E8B2D12CC4 93A2CAC524E8B2712AC491A2C8C52568422A2AC491A28AC4D312468A331491A28D45645892B451C8 A4C50844E50844AD14722B22C495A28E452568A30B05041581000000033502021138C49AA28D448D 0844B3125A8A31134C496A28CC525A8A35138C498A2C8C54468422568422931451C8AC8B12628A39

my ringtones binary always in this format if the sent in 2 part , we submit the header .And we submit to SMSNow using the web interface ,Send Binary Message , Ringtones . Any other way to sent this ringtones etc instead of using webinterface ?

Please help .

Rgds
Iwan Sp

Please help
Bryce Norwood - NowSMS Support
Posted on Sunday, August 03, 2003 - 03:33 pm:   

Iwan,

The problem here is that you have two distinct messages combined together with the headers intermixed with the data.

At the start of the data, 0B0504158100000003350201 is the user data header (UDH) for the first message.

Later in the data, I see, 0B0504158100000003350202, which I expect is the user data header for the second message.

You can't intermix the message in this way. If you have the headers created for submitting the ring tone as two messages, you have to submit it as two messages.

There are two ways that you could submit this message data.

1.) Submit the message as two individual messages. I've noted the break point between the two messages above. When you submit a binary message to NowSMS, you have to separate the UDH field from the data. So, for the first message, you would specify 0B0504158100000003350201 as the UDH, and all of the data up to the next header would be the binary data for that first message.

2.) Let NowSMS perform the message segmentation. Change the UDH to 06050415810000, and for the message data, specify all of the actual ring tone data ... which would mean all of the data except for the parts that I identified as headers, or:

0B0504158100000003350201024A3A5D2161194CB4C4DC041F491ED5966166156136156248D16462 92B4211511A188A48D14622B22C491A28E452468B2312AC493A2C9C526284227284224E8B2D12CC4 93A2CAC524E8B2712AC491A2C8C52568422A2AC491A28AC4D312468A331491A28D45645892B451C8 A4C50844E50844AD14722B22C495A28E452568A30B05041581000000033502021138C49AA28D448D 0844B3125A8A31134C496A28CC525A8A35138C498A2C8C54468422568422931451C8AC8B12628A39

(I crossed out the part of your original data that is headers, and not actual data.)

-bn
Iwan Suryaputra
Posted on Monday, August 04, 2003 - 11:59 am:   

Dear : Bryce

Okay we manage to sent the ringtones , now we encounter another problem to sent the picture message, since the binary is more then 2083 charaters. and we can not submit that long character via url .
Please give us guide how to sent the picture message ( nokia ) .

Best Regards
Iwan Sp
Bryce Norwood - NowSMS Support
Posted on Tuesday, August 05, 2003 - 02:07 pm:   

Hi Iwan,

I think we dealt with this one via e-mail. Apparently the 2083 character limit is related to a PHP redirect limit on the URL length.

We were able to shorten the URL by removing some unnecessary parameters. (When submitting a Nokia ring tone, for example, our web form submits some variables that are not actually used by the server ... they are used only by the JavaScript. Only the "Data", "UDH", "PID", and "DCS" parameters are really relevant ... the variable names that start with "Nokia" are used only by the JavaScript ... and are ignored by the server.)

-bn