Application-Specific Megaco Error Codes
It has been bothering me for quite a while that we have no guidelines for the numbering of error codes, so they could be all over the map. For example, I created codes in the NAS packages starting with 100, simply because this was the first example of package-documented error codes. Since these codes were not yet registered with IANA, it may not be too late to enforce the following convention, following the precedent set by H.,248 Annex M.1:
Proposal: application-specific error codes are assigned consecutive values starting at 600.
Following on this proposal, I am changing the NAS error codes to 613-616 from 100-103.
Comments?
Tom Taylor taylor@nortelnetworks.com Ph. +1 613 736 0961 (ESN 396 1490)
Hello Tom,
Sounds OK to me. How do you see that this will be documented? At the IANA site?
Regards, Christian
Tom-PT Taylor wrote:
It has been bothering me for quite a while that we have no guidelines for the numbering of error codes, so they could be all over the map. For example, I created codes in the NAS packages starting with 100, simply because this was the first example of package-documented error codes. Since these codes were not yet registered with IANA, it may not be too late to enforce the following convention, following the precedent set by H.,248 Annex M.1:
Proposal: application-specific error codes are assigned consecutive values starting at 600.
Following on this proposal, I am changing the NAS error codes to 613-616 from 100-103.
Comments?
Tom Taylor taylor@nortelnetworks.com Ph. +1 613 736 0961 (ESN 396 1490)
Dear experts,
I'd like to check my interpretation of the format of the BearerCaps IE for a Setup message for call-independent signalling connections. Per H.225.0 7.2.2.1: "If this information element appears in a Setup message for a call-independent signalling connection as defined in Recommendation H.450.1, the coding shall follow 7.2/H.450.1."
Normally this IE will have octets 3, 4, and 5, and if multirate, also octet 4.1, for length of either 5 or 6 octets. But for the signalling only connection, 7.2/H.450.1 states: "...the coding defined in Q.931 shall apply for octets 1 to 2 and bit 8 of octets 3 to 4. Information transfer capability, Transfer mode and Information transfer rate shall be encoded as indicated and no other octets shall be included." So for this case we have only octets 1 to 4, with a length therefore of 4 octets. Taking this with the bit 8 coding from Q.931, it appears that for the signalling case the BearerCaps IE should contain octets 3 and 4 with values:
3: 0xA8 4: 0x80
Does this seem correct?
-- best regards, miner --------------------------------------+------------------------ Miner Gleason, Software Engineer | | | mgleason@cisco.com | :|: :|: 7025 Kit Creek Road, P.O. Box 14987 | :|||||: :|||||: Research Triangle Park, NC 27709-4987 | .:|||||||:.:|||||||:. 919-392-8752 fax: 919-392-7065 | c i s c o S y s t e m s
participants (3)
-
Christian Groves -
Miner Gleason -
Tom-PT Taylor