S and L timers set to 0
Alexander Agranovsky <[email protected]>
| Newsgroups | gmane.ietf.megaco |
|---|---|
| Message-ID | <[email protected]> |
Hi All,
I have a question about the settings of S and L timers in H.248.1.
According to 7.1.14.2, if T timer value is set to 0, it means that the timer is cancelled and MG will wait infinitely for the
first digit.
However, there is no word about valid behaviour with S or L timers set to 0.
There are 4 possible options:
a. MG should wait infinitely in cases where S or L timer would usually be applied.
b. MG should not wait at all in cases where S or L timer would usually be applied
c. MG would use default values for S and L timers
d. Values of 0 are invalid for S and L timers - it should not be possible to provision these values, and Digit Map received from MGC which specifies these values should be rejected with appropriate Error Code ( 401? ).
Option a. will prevent any ambiguous match to be achieved.
Option b. will cause MG to send early partial matches ( especially problematic if L is set to 0 - first digit will always be reported as a partial match).
Therefore, only options c. and d. seem to be feasible.
A.2 and B.2 describe the format of the Digit Map parameter and mention that the range for T, S and L is between 1 and 99 seconds, but that's clearly not true about T timer, so I am not sure whether it should be taken as a normative.
Regards,
Alex.
---------------------------------
Support the World Aids Awareness campaign this month with Yahoo! for Good
_______________________________________________
Megaco mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/megaco