asked on weird error on my CISCO2911/K9 voice gateway ...
Anyone know why my log buffer in my functioning voice gateway 2911 is full of this message and how I can stop it? debug is not turned on....:
SIP: Trying to parse unsupported attribute at media level
I see a bug report at https://quickview.cloudapps.cisco.com/quickview/bug/CSCuv36964 but they have no advice for how to stop it from constantly filling up my log buffer .... does anyone know how to make this irritating message stop? Is there any way to determine exactly what the "unsupported attribute" message might be that triggers this or where it is coming from? If someone has an old test sending out something repeatedly, am I going to have to sniff packets all day to find it?
SIP: Trying to parse unsupported attribute at media level
I see a bug report at https://quickview.cloudapps.cisco.com/quickview/bug/CSCuv36964 but they have no advice for how to stop it from constantly filling up my log buffer .... does anyone know how to make this irritating message stop? Is there any way to determine exactly what the "unsupported attribute" message might be that triggers this or where it is coming from? If someone has an old test sending out something repeatedly, am I going to have to sniff packets all day to find it?
Voice Over IP
Last Comment
Jane Updegraff
ASKER
All I want to achieve is to not have this event filling up my log buffer. I can't keep logs of any "real" activity when one of these messages is logged every five or ten minutes. I guess I can increase the buffer size. Or replace this aging device....
You said:
....that's what i thought you would say. *sigh*
According to what I've read in the community, this message can't be turned off. And although I may be able to figure out what's triggering the log entry, if it is something normal that actually belongs in the traffic then I'm out of luck, it seems.
But thanks for confirming ....
You said:
here is little you can do to stop an external source from sending this packet your way.
....that's what i thought you would say. *sigh*
According to what I've read in the community, this message can't be turned off. And although I may be able to figure out what's triggering the log entry, if it is something normal that actually belongs in the traffic then I'm out of luck, it seems.
But thanks for confirming ....
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
As you suggest I would rather know where they are coming from and stop the message from being created to begin with, rather than have to filter my syslog. Thanks for the ideas. :-)
ASKER
Thanks for the ideas!
Given the info, what are you hoping to achieve?
First thing, as noted, identify the source of the packet. If external to your provider......
There is little you can do to stop an external source from sending this packet your way.