SMS Settings - Sender field is not saved > CELCAT Discussion Forum

Unanswered Active Topics

Forums Search

Forums > Using Timetabler Applications > Administrator

Subject: SMS Settings - Sender field is not saved

Prev Next

You are not authorized to post a reply.

Author

Messages

Graham Crawford User is Offline

Posts:6

11 May 2009 6:36 AM
I'm trying to setup SMS Notification Alerts in conjuction with the SAT supervisor alerts. In the SMS settings dialog box (selected from the Settings -> Communications tab) I'm setting the Sender field to be the mobile phone number of my account and I can send a test SMS message just fine with the Test button. But when I close down the Administrator application and restart it, the field is blank and subsequent tests fail (until I enter the phone number in the field again.) Does anyone have this working ?

--- Graham

Support

Posts:77

12 May 2009 10:44 AM
Hi Graham, We have had a look at this and it appears to be a bug which I have reported to development. To allow this to work, you will need to populate the following table manually CT_CONFIG You need to then make the change to sms_originator (Sender) ms_signature - if you use this. This will then save the changes directly to the database. Sorry for the inconvienence caused Regards CELCAT Technical

Graham Crawford User is Offline

Posts:6

14 May 2009 5:55 AM
I've now updated the CT_CONFIG database table with our details which are displayed below. sms_provider: 5006 sms_user_id: D29... sms_password: 923... sms_originator: 61429776214 sms_account: sms_signature: Now, when the notification service fires the following message can be seen in the log file. 14/05/2009 1:39:46 PM SMS Error - Invalid account details Initially the sms_account field was displayed as NULL in the database, I tried resetting this to an empty string ("") but either way the same message was seen in the log file. When the Test dialog box is used from the Administrator application is used the account field is greyed out and the SMS message is sent sucessfully. Any ideas what the account field has to be set to to enable the auto notifications to work ?

--- Graham

Antony

Posts:21

14 May 2009 9:23 AM
The GUI is generic - being used to send SMS to various supported providers - so if a field is grayed out in the GUI it simply means it's not applicable to the chosen provider. So in your case (withthe Telstra provider) the sms_account column should remain NULL. The "Invalid account details" error is a response from your SMS provider and seems to indicate that the user id and password are not correctly specified. Please bear in mind that the sms_user_id and sms_password fields are encrypted in the database so you can't just enter the values there - they must be entered in the Administrator SMS form so they are correctly encrypted Rgds Antony

Graham Crawford User is Offline

Posts:6

15 May 2009 4:24 AM
The GUI is generic - being used to send SMS to various supported providers - so if a field is grayed out in the GUI it simply means it's not applicable to the chosen provider. So in your case (withthe Telstra provider) the sms_account column should remain NULL. The "Invalid account details" error is a response from your SMS provider and seems to indicate that the user id and password are not correctly specified. Please bear in mind that the sms_user_id and sms_password fields are encrypted in the database so you can't just enter the values there - they must be entered in the Administrator SMS form so they are correctly encrypted Yes, thats right, the sms_user_id and sms_password are entered through the GUI and stored as encrypted strings in the database, in my previous post you can see the first part of each of these encrypted ascii strings. I didn't include the full string for brevity and security reasons. I know that these are correct as the GUI works correctly sending an SMS message through our provider (see above.) Also all HTTP requests from our browsers and servers are channeled through a proxy server which logs them. This is useful as communications can be traced with these log entries, for example, when I use the Celcat SMS GUI to send a test message the following log entry appears. 1242188907.854 780 192.168.1.4 TCP_MISS/200 537 POST http://apac.soprano.com.au/cgphttp/servlet/sendmsg? - DIRECT/128.121.252.113 text/plain When the Celcat notification service fires up and I see the "Invalid account details" message in the Celcat log, but no such log messages (as shown above) can be seen in the proxy log. Thus I assume no communication between Celcat and the SMS provider and that the error lies within Celcat. Can you confirm that the notification service uses exaclty the same method to contact the SMS Provider as the SMS GUI screen ? I can then track the rest of the sending process through the SMS providers tools and utilities.OK, that's great, the Celcat SMS GUI works just fine, the SMS message is sent, received and all is well (except for the bug noted above!)

--- Graham

Graham Crawford User is Offline

Posts:6

15 May 2009 4:33 AM
Hhhmn, the first part of that last post went missing, it should have read ....The GUI is generic - being used to send SMS to various supported providers - so if a field is grayed out in the GUI it simply means it's not applicable to the chosen provider. So in your case (withthe Telstra provider) the sms_account column should remain NULL. OK, that's great, the field is greyed out, the database field is NULL, and the Celcat SMS GUI Test Button works fine, the SMS Message is sent, received and all is well (except for the bug noted at the very top of this forum.)

--- Graham

Antony

Posts:21

15 May 2009 9:10 AM
Graham Good - sounds like all works ok now except for the bug raised at top of thread (but the wrok-round is you have to enter the sender value manually in the CT_CONFIG table). Rgds Antony

You are not authorized to post a reply.

Forums > Using Timetabler Applications > Administrator > SMS Settings - Sender field is not saved

ActiveForums 3.7