Nit on new callcapacity field
Can anyone explain the mysterious maximum value used for all of the call capacity fields added to H.225.0 version 4? They are all defined as INTEGER (1..429467295). At first glance, it appeared to be 4G (which is BIG!), but after a while, it revealed itself to be something totally different (429M, still a fair sized H323 endpoint). I'd like this to be fixed. (I find it an unreasonable limitation on my Annex L endpoint ;)
Dave W.
Dave,
Good catch - obviously a digit is missing, so I'll fix this in the next draft. And of course we don't want to place unreasonable limits on SETs!
Rich -- Dave Walker wrote:
Can anyone explain the mysterious maximum value used for all of the call capacity fields added to H.225.0 version 4? They are all defined as INTEGER (1..429467295). At first glance, it appeared to be 4G (which is BIG!), but after a while, it revealed itself to be something totally different (429M, still a fair sized H323 endpoint). I'd like this to be fixed. (I find it an unreasonable limitation on my Annex L endpoint ;)
Dave W.
-- -------------------------------------------------------------------- Richard K. Bowen Cisco Systems, Inc. rkbowen@cisco.com Research Triangle Park, NC --------------------------------------------------------------------
participants (2)
-
Dave Walker -
Rich Bowen