| SMSOUT Logs show unassigned LocalUser |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through April 16, 2015 ⬆ |
◄ ► |
| Author | Message | |||
| Lee Eidson New member Username: Leidson Post Number: 4 Registered: 04-2014 |
Hi We're using SMPP binds to several SMSC's, with a number of LocalUsers doing both MO and MT traffic. In our SMSOUT logs, there are entries routed to a particular LocalUser whose status history shows no traffic for several years and who I can't find configured to receive any traffic - not set on any SMPP bind under "Route SMS to Local User" and nothing under "Recipient address(es) to route to this user". Is there some other place that I'm overlooking? Here are the entries for one message from both SMSOUT and SMSIN. Names have been changed to protect the innocent... 2014-07-25 16:40:15,5F40963C.req,,xxxxxxxx,OK -- LocalUser:yyytest,SubmitUser=SMPP - 123.123.123.123:1234;Sender=1234567890;Text="53D27B1A,1,-5,24,0,17F15673" Cleaned SMSIN log entry: 2014-07-25 16:40:15,1234567890,SMPP - 123.123.123.123:1234,Text="53D27B1A,1,-5,24,0,17F15673";SMSCRouteName=XXX SMPP - 123.123.123.123:1234;Recip=xxxxxxxx | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4961 Registered: 08-2008 |
Hi Lee, I'd look at the SMSGW.INI, [Inbound SMS Routing] section. Maybe there is a rogue entry there. Other than that, maybe some test code in an accounting callback that has been forgotten? -- Des NowSMS Support | |||
| Lee Eidson New member Username: Leidson Post Number: 5 Registered: 04-2014 |
Hi Des There's an entry in the SMSGW.INI file that explains the routing. I guess the question now is why this doesn't show up in the interface. Is there a reason it's missing from the LocalUser's form? Thanks! | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4962 Registered: 08-2008 |
Hi Lee, Anything you can tell us about this would be helpful. Since you edited the file directly, if you put the entry back in SMSGW.INI, does that recreate the problem? Scan the hard drive for additional copies of SMSGW.INI. We have seen issues where security configurations led to the config program seeing a different version of this file than the service. (A quick way to check this is to right-click "Run as Admin" to launch the config program and check if it sees the correct settings.) -- Des NowSMS Support | |||
| Lee Eidson New member Username: Leidson Post Number: 6 Registered: 04-2014 |
Hi Des For now, I just updated the LocalUser to match what was in the SMSGW.INI file. I've never edited the file manually, though it's possible someone else before me did. There is only one smsgw.ini file on the server. | |||
