SPA525G syslog is too verbose

Unanswered Question
Sep 28th, 2010

Setting up the syslog server you begin to get a lot of information coming through.  The debug server is blank and the debug level is set to 0.


I keep getting messages like:


Sep 28 15:29:29 10.1.5.27 [4]CC:NewCallState 9/8

Sep 28 15:29:29 10.1.5.27 

Sep 28 15:29:59 10.1.5.27 [4]CC:NewCallState 13/9

Sep 28 15:29:59 10.1.5.27 

Sep 28 15:30:21 10.1.5.27 [4]CC:NewCallState 0/13

Sep 28 15:30:21 10.1.5.27 


Sep 28 15:09:40 10.1.5.24 SCCP:TFTP From 100010a:69/SEP68EFBD28E8CE.cnf.xml

Sep 28 15:09:44 10.1.5.12 [0]Reg Addr Change(0) 0:0->a010050:5060

Sep 28 15:09:45 10.1.5.22 [0]Reg Addr Change(0) 0:0->a010050:5060

Sep 28 15:09:47 10.1.5.34 [0]Reg Addr Change(0) 0:0->a010050:5060

Sep 28 15:09:53 10.1.5.70 SCCP:TFTP From 100010a:69/XMLDefault525G.cnf.xml

Sep 28 15:09:53 10.1.5.18 SCCP:TFTP From 100010a:69/XMLDefault525G.cnf.xml

Sep 28 15:10:00 10.1.5.24 SCCP:TFTP From 100010a:69/XMLDefault525G.cnf.xml

Sep 28 15:10:13 10.1.5.70 SCCP:TFTP From 100010a:69/XMLDefault.cnf.xml

Sep 28 15:10:13 10.1.5.18 SCCP:TFTP From 100010a:69/XMLDefault.cnf.xml

Sep 28 15:10:20 10.1.5.24 SCCP:TFTP From 100010a:69/XMLDefault.cnf.xml

Sep 28 15:10:33 10.1.5.70 SpcpDetect:ServerIp=0 ncm=0

Sep 28 15:10:33 10.1.5.70 Wifi profile { order <2> key<2> name:cisco-voice ssid:cisco-voice security:1 }

Sep 28 15:10:33 10.1.5.18 SpcpDetect:ServerIp=0 ncm=0

Sep 28 15:10:33 10.1.5.18 Wifi profile { order <2> key<2> name:cisco-voice ssid:cisco-voice security:1 }

Sep 28 15:10:40 10.1.5.24 SpcpDetect:ServerIp=0 ncm=0

Sep 28 15:10:40 10.1.5.24 Wifi profile { order <2> key<2> name:cisco-voice ssid:cisco-voice security:1 }

When all I am looking for is messages like what I get from the SPA962's ( the SPA962's behave as expected with just the syslog server entered ).
Sep 28 15:19:14 10.1.5.12 SPA-962  -- Requesting resync tftp://10.1.0.80:69/spa962.cfg
Sep 28 15:19:14 10.1.5.12 SPA-962  -- Successful resync tftp://10.1.0.80:69/spa962.cfg
I have checked all the Line's and all SIP Debug is set to none.  Am I missing something in regards to the SPA525G or is this a software defect?
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
nseto Wed, 09/29/2010 - 11:21

This is normal.  syslog generally shows a bit more than debug, even when debug level at 0, you'll see something.  It looks like 'auto detect sccp' is set to yes based on what I can see.

rcanavan Wed, 09/29/2010 - 11:29

The SPA962 phones only send the provisioning elements to the syslog server.  This is really all we want to get so that we can ensure that our devices are getting their provisioning, etc.


I really don't need to see when people are making calls, etc.  And even if I set the debug server only, it still gives me the same amount of data.

nseto Wed, 09/29/2010 - 11:33

The log is showing SCCP and WiFi info.  The 962 doesn't have those features.

Check that 'auto detect sccp' is turned off and see if that gets rid of the sccp messages shown in the log.

rcanavan Wed, 09/29/2010 - 11:45

Even with that parameter set to No, it is still pushing stuff like this to the syslog server:



Sep 29 14:39:38 10.1.5.65 [0]CC:NewCallState 8/6

Sep 29 14:39:38 10.1.5.65 

Sep 29 14:39:38 10.1.5.65 ++++ called number = *452850

Sep 29 14:39:38 10.1.5.65 [0]CC:NewCallState 13/8

Sep 29 14:39:38 10.1.5.65 

Sep 29 14:39:41 10.1.5.65 [0]CC:NewCallState 15/13

Sep 29 14:39:41 10.1.5.65 

Sep 29 14:39:41 10.1.5.65 [1]CC:NewCallState 8/6

Sep 29 14:39:41 10.1.5.65 

Sep 29 14:39:42 10.1.5.65 ++++ called number = *452850

Sep 29 14:39:42 10.1.5.65 [0]CC:NewCallState 14/15

Sep 29 14:39:42 10.1.5.65 

Sep 29 14:39:42 10.1.5.65 [1]CC:NewCallState 13/8

Sep 29 14:39:42 10.1.5.65 

Sep 29 14:39:44 10.1.5.65 ## goes to idle: 5 0

Sep 29 14:39:44 10.1.5.65 [0]CC:NewCallState 0/14

Sep 29 14:39:44 10.1.5.65 

Sep 29 14:39:45 10.1.5.65 [1]CC:NewCallState 11/13

rcanavan Wed, 09/29/2010 - 13:45

I should also note that it is also sending out a line like this:

>>>>PRV decrpt profile len=512 pwd=ourPassword


We want the provisioning syslog to be sent, but this is certainly way too much information.  This looks to be debugging grade info which is not required for basic logging of phone activities during the provisioning process.

Actions

This Discussion

Related Content