Bug report or a feature request

Bug report or a feature request SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through March 09, 2004 » Bug report or a feature request « Previous || Next »
Author Message
Anonymous
 
Posted on Thursday, February 26, 2004 - 03:42 pm:   

Hi Bryce,

I have made the following observation:
While testing the NowSMS I noticed a corruption in my SMPP connections. After tracing, I figured out the reason.
First I would like to describe what I did to trigger this behaviour.
When creating an SMPP connection, I used 192.168.1.9 port 7000 for example. I added all the account details.
The I tried adding a new smpp connection to same machine but with different account details. So, I used 192.168.1.9 port 7000 for the second connection.
This causes NowSMS to delete the previously defined connection and gets replaced by the new connection.

I managed to get around this problem by editting the SMSGW.INI manually and adding the second connection manually. To differentiate between the connections, I had to use 192.168.1.009 for the server connection, thus making the name unique.

It works this way, as long as you dont try to edit the connection from NowSMS UI.

Just liked to inform you on the issue.

Yours,
Hadi
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 1999
Registered: 10-2002
Posted on Tuesday, March 09, 2004 - 04:19 pm:   

Hi Hadi,

Apologies for the delay getting back to you.

Yes, this is a known issue. Your work-around is a good idea, but leading zeros in IP addresses can sometimes cause problems (because Windows thinks a leading 0 means that the number is in octal/base-8 format).

The work-around that we usually recommend is to use a HOSTS file, as described in the following thread:

http://support.nowsms.com/discus/messages/485/791.html

I wish we had a solution other than this work-around, but any other type of fix would require a change in our INI file format, and we're concerned that we don't want to introduce potential incompatibilities in an updated release. So we've been recommending this work-around.

-bn

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