Hi, sipCommonStatusCodeMethod is an index for that table. The idea was that to track status code responses on a per method basis (i.e. track 200 responses to INVITE, independently from 200 from BYE, OPTIONS, etc.).
You are correct though that the text in the subsequent table entry objects does not state that the number of responses in/out are on a per method basis. I think they should be. I cc: Kevin for a confirmation on this. If folks agree that this correction is needed, I will log an errata. Hope this helps. Jean-Francois. [EMAIL PROTECTED] > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:sip- > [EMAIL PROTECTED] On Behalf Of Nithin N > Sent: Thursday, June 19, 2008 12:49 AM > To: [email protected] > Subject: [Sip-implementors] SIP MIBs in RFC 4780 > > Hi All, > > I have a question on SIP MIBs described in RFC 4780. > > sipCommonStatusCodeTable has sipCommonStatusCodeMethod as an object > with uniquely identifies > a conceptual row. But the definitions of rest of the MIB objects in > the table does not specify any relation > with sipCommonStatusCodeMethod. For e.g. sipCommonStatusCodeIns > object reflects the total number > of response messages received by the SIP entity with the status > code > value contained in the > sipCommonStatusCodeValue. So what is the significance of having > sipCommonStatusCodeMethod in the > sipCommonStatusCodeTable? > > Can you please tell, how sipCommonStatusCodeMethod can be related > to > other MIB objects of sipCommonStatusCodeTable.? > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
