Daniele Orlandi schrieb:
On Saturday 11 March 2006 11:55, Florian Trück wrote:
Maybe I missed something, but the HANGUP_INDICATION State of the network
will not last for about 30 or 40 seconds.
It is called DISCONNECT_INDICATION status and it will last for T306/T305
seconds (30 seconds) if the local party does not hang up before.
I have no detail info on that part of isdn protocol but i don't think
that any device in the network needs about that much time
to say how long the call lasted and what its costs were.
The timer says what the maximum time to send and receive the in-band
indications is. The network could, of course, end the in-band message by
sending a RELEASE, but usually the network sends the busy tone for as long as
T306 lasts.
So maybe to think of a timeout period where the device has time to respond
or not. Maybe 2sec is enough. Then simply close that channel.
Uhm... no... the correct way is to handle the DISCONNECT indication (thru the
AST_CONTROL_DISCONNECT frame) and hangup. app_voicemail should hangup,
because it is not interested in recording the disconnect indication tones.
Bye,
OK, i know this is not fin what I'm asking now.
but could it be possible to implement a config flag where i can control
if I want this feature or not?
I know it is according to the standards to wait for special data. But I
definitely do not want to do
this. I have no reason for this. So the most simple way to get a (in my
viewpoint) working visdn
is to implement this config flag or to supply a patch where I can
disable this feature in my source.
Bye,
Flo
_______________________________________________
Visdn-hackers mailing list
[email protected]
https://mailman.uli.it/mailman/listinfo/visdn-hackers
