SMDR - Switched Syslog Servers and its not Logging anymore?

[stownsend]

We migrated out Syslog server to another IP and after I changed the SMDR IP in IP Office it is not logging any of the call Data.

I've rebooted the system a few times with no luck. I reverted back to the old IP and its not logging there either... I'm not Physically there, so no Cold Boot.

Went to Monitor and I can see that its setup with the Right info - IP and Port. I can telnet from the VMPro server to the IP/Port and see what I type in Syslog.

********** SysMonitor v9.1.1.0 build 10 [connected to 99.99.0.49 (EM_Machinery)] **********
133921mS CDR: SMDR OUTPUT '2017/10/01 23:53:14,00:00:06,0,Number@IP,I,*820,201,,0,1000001,1,T9020,Line 20.1,V9511,VM Channel 11,0,0,,,,,,,,,,,,,,99.99.0.49,1008,99.99.0.49,1010
'
133921mS CDR: Using TCP to send data to 10.1.0.11 on port 1468
138810mS CDR: SMDR OUTPUT '2017/10/01 23:53:20,00:00:00,2,,O,Number, Number,,0,1000002,0,E133,ScottTownsend,T9020,Line 20.2,0,0,,,,,,,,,,,U MT,ScottTownsend, Number@sip.com,99.99.0.49,1012,99.99.0.49,1015
'
138810mS CDR: Using TCP to send data to 10.1.0.11 on port 1468

********** SysMonitor v9.1.1.0 build 10 [connected to 99.99.0.49 (EM_Machinery)] **********
153132mS CDR: SMDR OUTPUT '2017/10/01 23:53:14,00:00: Number@IP,I,133,201,,0,1000001,0,T9020,Line 20.1,V9543,VM Channel 43,0,0,,,,,,,,,,,,,,10.1.0.40,1008,99.99.0.49,1018
'
153132mS CDR: Using TCP to send data to 10.1.0.11 on port 1468

********** SysMonitor v9.1.1.0 build 10 [connected to 99.99.0.49 (EM_Machinery)] **********

 

[intrigrant]

It needs a reboot....

 

[stownsend]

turns out that the Records were getting to the Syslog server. We get 40K Messages an hour, so its hard to see them. The records are uploaded to a SQL Server. Tough the SQL Table has a trigger on it that looks specifically for the SMDR records and ships them off to another Database. That cross Database insert failed so the local insert of the SMDR record also failed.

Fixed the Insert to allow insert of data if trigger fails, and also fixed the link to the remote database.

Thanks,

 

[HDowns]

Dummy question, but: did you open this port in a firewall on your new Syslog server?

 

[stownsend]

Yes checked the firewall, it was not the Syslog server, firewall or anything like that. It was a trigger on the Database insert that was failing and that the failure caused the record to not be inserted. the Trigger was Specifically looking for the SMDR information and only failed on those inserts. So when querying the database it was coming up with nothing. The Syslog server's log has the data, though @ 40K messages an hour, its hard to find them when I'm the only one making a call at midnight...

We added "SET XACT_ABORT OFF;" to the Trigger and even though the trigger was failing, it still inserted the record even if the trigger failed.

Thanks,