Naming SMSC Connections

Naming SMSC Connections SearchSearch
Author Message
John Roth
New member
Username: Ispeakgeek

Post Number: 6
Registered: 08-2006
Posted on Thursday, January 18, 2007 - 03:15 pm:   

Hello!

I'm wondering if it's possible to include a descriptive name for an SMSC connection. Many of our connections are by IP address, which can lead to some confusion when editing settings. Can we give the connections a descriptive name that will show up in the listing on the SMSC tab?

I know that when we have multiple connections to the same SMSC, NowSMS appends the '#' character and an index number. Can I safely presume that NowSMS ignores anything after the # sign when making the connection? Could we put in something like '127.0.0.1#SomeName' for a single connection and '192.0.0.1#SomeName 01' & '192.0.0.1#SomeName 02' for multiple connections?

Thanks!

John
Malcolm - Now Support
Moderator
Username: Malcolm

Post Number: 114
Registered: 12-2006
Posted on Monday, January 22, 2007 - 09:52 pm:   

Hi John,

The issue of putting descriptive names in this list is one that we have had a number of internal discussions about, but at the end of the discussion there has always been other issues that were more pressing.

The idea that you have suggested about putting the text after the "#" character is very interesting. However, my experience suggests that NowSMS will only ignore text after the "#" if it is all numeric. If there are any non-numeric characters, then NowSMS tries to use it as part of the host name.

I'm going to do some investigation to see if maybe a simple change would allow "#" to be used as a generic comment marker. If the "#" character is not allowed in a DNS host name (I think that is the case), then this would probably be an easy change.

--
Malcolm
Now Wireless Support
John Roth
New member
Username: Ispeakgeek

Post Number: 7
Registered: 08-2006
Posted on Wednesday, January 24, 2007 - 11:33 am:   

Hi Malcolm,

To be honest, if it were me, I'd simply add a new ini setting called Description and revise the code that populates the SMSC connections list to display the description and the server host name (e.g. "Vodafone (127.0.0.1#1:0000)").

That way you don't risk affecting any other sections of code (yours or client customization code) that read the ini.

Just a thought anyways...

John