Hello,   we have an issue with "clear ip mroute A.B.C.D” command (tested on NX-OS  7.3.3.N1.1 and  7.3.2.N1.1 ). After specific (s,g) group is cleared, it doesn't appear again. Only after "clear ip mroute *" command, that (s,g) entry appearing again in mrib. It is NX-OS bug or not? Because in classical IOS "clear ip mroute A.B.C.D" works great.   Example output (real IP adresses is changed):   NX3# sh ip mroute 233.x.x.x IP Multicast Routing Table for VRF "default" (a.b.c.d/32, 233.x.x.x/32), uptime: 00:00:59, ip pim    Incoming interface: Vlan817, RPF nbr: c.d.e.f   Outgoing interface list: (count: 0) NX3# clear ip mroute   233.x.x.x NX3# sh ip mroute   233.x.x.x IP Multicast Routing Table for VRF "default" Group not found NX3# clear ip mroute *   NX3# sh ip mroute 233 .x.x.x IP Multicast Routing Table for VRF "default" ( a.b.c.d/32, 233.x.x.x/32), uptime: 00:00:04, ip pim    Incoming interface: Vlan817, RPF nbr:  c.d.e.f   Outgoing interface list: (count: 0)     Thank you in advance. ... View more

Hello, mine question is, why there are no support for 'Set_G729_annexb: No' for SPA series gateways. That is SPA gateway violates RFC 3555 (dating back to 2003) in its G729 codec naming. Snippet from RFC:    MIME subtype name: G729    Required parameters: None    Optional parameters:         ptime, maxptime         annexb: indicates that Annex B, voice activity detection, is         used or preferred.  Permissible values are "yes" and "no"         (without the quotes); "yes" is implied if this parameter is         omitted. That is by not providing this optional attribute, G729 is considered Annex B. And accoring RFC theres no such mime name as G729a. Even more, i dont think that rtpmap attribute is of any use for codec G729 as it is only in 8khz. As i understand other cisco equipment follows this RFC requirement also as SPA IP Phones do. Is there a change that this option will be added to SPA gateways? This would really help with G729 interoperability. best regards, Antanas Masevicius ... View more