Work around bug in HLR sending invalid CamelCapabilityHandling=0

This commit is contained in:
Harald Welte 2011-02-10 14:30:19 +01:00
parent 2e4004150b
commit 8fe3132736
1 changed files with 2 additions and 1 deletions

View File

@ -1691,7 +1691,8 @@ DefaultCallHandling ::= ENUMERATED {
-- reception of values in range 2-31 shall be treated as "continueCall"
-- reception of values greater than 31 shall be treated as "releaseCall"
CamelCapabilityHandling ::= INTEGER(1..16)
-- The Specification says 1..16, however some implementations are broken and send 0 !!! - laforge
CamelCapabilityHandling ::= INTEGER(0..16)
-- value 1 = CAMEL phase 1,
-- value 2 = CAMEL phase 2,
-- value 3 = CAMEL Phase 3,