CUBE SIP: Trying to parse unsupported attribute at media level

[Bekzod Fakhriddinov]

I there any way to disable this message ? i have too much of it coming and because of it i don't see other messages , probably this message just filling up buffer and cleaning earlier messages . 

Thank you 

[Adarsh Chauhan]

Hi,

Please refer to: CSCuv36964

You can collect debugs (debug ccsip messages and debug voice ccapi inout) on the gateway and we can see why are these messages popping up and then make a sip profile accordingly.

Do it in the buffer or some syslog server or when you have a low call volume.

Please rate and mark correct if helpful

Regards,

Adarsh Chauhan

[Bekzod Fakhriddinov]

i attached debugs started from 9:25am till 10:25 am . I changed Ip and name of the users . I appreciate ur help . 

[Adarsh Chauhan]

Hi Bekzod,

It seems like that the following parameter are causing the problem in the SDP header of the INVITE.

a=trafficclass:conversational.audio.aq:admitted
a=trafficclass:conversational.audio.avconf.aq:admitted
a=trafficclass:conversational.video.avconf.aq:admitted

my sip profile in lab is not working for some reason. I will update you if I get it working.

You can try the following and let me know if it works:

conf  t
logging discriminator no_SIPparse msg-body drops Trying.to.parse
logging buffered discriminator no_SIPparse
logging console discriminator no_SIPparse
logging monitor discriminator no_SIPparse
exit"

Please rate and mark correct if helpful

Regards,

Adarsh Chauhan

[Bekzod Fakhriddinov]

im not getting any messages now. this discriminator looks like block every messages, even i have 

logging buffered discriminator no_SIPparse 999999

[Bekzod Fakhriddinov]

Contact: <sip:2129308935@10.132.6.13:5060;transport=tcp>;video;audio;+u.sip!devicename.ccm.cisco.com="SEP5006AB806710"   


As I remember contact field show participants of the call. So what I noticed I started to get those sip parse messages recently , and what we did recently we replaced 7965 phones with new 8845 sip phones, right after upgrade of phones. And I see on debug that trying to parse message coming in calls involved those 8845 phones. So looks like some settings on the 8845 ?? I have found trace from 7965 and trace from 8845 and attached them here. attributes they are sending different. May be You can find the cause  of the problem with you experience. Thank you

[Bekzod Fakhriddinov]

any idea  ? 

[Mohammed al Baqari]

Hi,

Yes you can exclude it from your logging. I have seen this message with video calls through cube. Use this config

logging discriminator remove_message msg-body drops Trying to parse unsupported attribute at media level
logging monitor discriminator remove_message #logging level#
logging buffer discriminator remove_message #logging level#

[Bekzod Fakhriddinov]

Thank you .

what is the logging level for that message ?  

[Mohammed al Baqari]

You can select the level which you are using in your organization. The default level is info

[Bekzod Fakhriddinov]

Debug is attached below 
Contact: <sip:2129308935@10.132.6.13:5060;transport=tcp>;video;audio;+u.sip!devicename.ccm.cisco.com="SEP5006AB806710"   


As I remember contact field show participants of the call. So what I noticed I started to get those sip parse messages recently , and what we did recently we replaced 7965 phones with new 8845 sip phones, right after upgrade of phones. And I see on debug that trying to parse message coming in calls involved those 8845 phones. So looks like some settings on the 8845 ??