Re: Signaling MIB - Draft 3 - Last Call - pktcSigDevCodecTable (Issue1)
"David De Reu" <[email protected]>
| Newsgroups | gmane.ietf.ipcdn |
|---|---|
| Message-ID | <[email protected]> |
Another advantage of having multiple indexing in the pktcSigDevCodecTable (i.e. being able to obtain all possible codec combinations from the MTA), is the added value when you are debugging/troubleshooting. Suppose you find out that an MTA refuses to create a given connection and you want to know why. The response code in the NCS error response, and the optional comment string, are not always very clear on the exact reason for the failure. In this case, you can maybe use the pktcSigDevCodecTable for troubleshooting. Having the full list of codec combinations available can be interesting here. In contrast, the current definition provides very little extra information above having just a list of supported codecs. Will the maximum number of codec sessions as it is defined now not always equal the number of ports the MTA has? _____________________________________________________ David De Reu tComLabs Stapelplein 70/004 9000 Ghent Belgium Tel: +32 9 269 22 91 Fax: +32 9 329 31 74 www.tComLabs.com _____________________________________________________