Sender Address - Only 10 Characters?

Sender Address - Only 10 Characters? SearchSearch
Author Message
Dhiraj Mirchandaney
New member
Username: Dhirajm

Post Number: 1
Registered: 05-2004
Posted on Sunday, May 23, 2004 - 12:45 pm:   

Hi!

Ive got multiple users configured for the Web Interface using the "SMS Users" tab and checking the "Enable Web Login" option. I am able to dynamically send the "sender address" for these users by configuring it in the "Forced Sender Address" option. Now the issue is that it allows only 10 characters.

Whereas at the global setting level (SMSC Tab) it allows 11 characters.

Is there a way to send 11 characters in the sender address when configured using the "SMS Users" tab?

Help.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2641
Registered: 10-2002
Posted on Tuesday, May 25, 2004 - 03:28 pm:   

Hi Dhiraj,

The 10 character limit is definitely incorrect.

I have sent an update for NowSMS v5.50 that increases the limit on the "forced sender address" applied to "SMS Users" accounts to the e-mail address in your discussion board profile.

If you do not receive this message, please e-mail nowsms@now.co.uk from an alternate e-mail address, reference this problem, and I will resend.

-bn
Dhiraj Mirchandaney
New member
Username: Dhirajm

Post Number: 2
Registered: 05-2004
Posted on Sunday, May 30, 2004 - 05:42 am:   

Hi Bryce,
I have upgraded the NowSMS installation to v 5.5 and applied the patch you sent. Now I keep getting this error : ERROR: ESME already in bound state (see attached file).

Please help!ERROR: ESME already in bound state
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2708
Registered: 10-2002
Posted on Monday, June 07, 2004 - 07:51 pm:   

Hi Dhiram,

Apologies for the delay getting back to you. Hopefully you were able to restore your previous version.

However, I don't see why updating would trigger this error.

This error is coming back from the SMSC, it is saying that you can't login because you are already logged in.

Perhaps there is some sort of timeout involved in disconnecting the previous session???