Re: fix for timer issues

Am 09.11.2012 10:21, schrieb jolly:
> hi,
> 
> i just found an issue on timer handling with NT mode stack.
> 
> when a phone answers (call from application to phone), the child process
> for this phone will replace the master process. the timers of that
> process still have the master pid. this will cause any timer timeout to
> be ignored for that phone until release. my patch changes the pid of
> timers also when a child process is selected. additionally it is
> required to stop T312 for this instance.
> 
> i would like to test it a while. my questions are:
> 
> - should we change the pid of timers when process is selected?
> - should we stop T312 when process is selected?

I really do not know yet - I need some time to think about it.
ETSI say only if the call is in the CALL abort state, this time does
anything (release the CR).So I do not thing we need to stop it.

> 
> another minor issue: i suggest to change T305 to 1 minute, to hear
> announcement. this is what carriers seem to do.

But this is not what certifications tests are checking, the Q931 and
ETSI are stating 30 second which should be enough for announcements
in most cases and the values in dss1.h are for both NT and TE.
But on the other hand, it often makes sense to change timer value for
testing, so we should have an interface to set these as LAYER3
parameters with the ETSI values as defaults. So an PBX can change them
after it has opened the L3.
What do you think ?


> 
> regards,
> 
> andreass
> 
> 
> 
> _______________________________________________
> isdn4linux mailing list
> [email protected]
> https://www.isdn4linux.de/mailman/listinfo/isdn4linux
>