[cisco-voip] Missed DISCONNECT

[Fedorov, Konstantin]

Hi,

How I understand you main concern about
Why after receiving disconnect my router doesn't send release message ,
correct ??  But on the whole, call completes successfully, correct ??

I think that you must not worry about this, this is called two-way
disconnect, both parties must hang-up.



-----------------------
Sincerely Yours,
Konstantin Fedorov

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Andre Beck
Sent: Tuesday, November 14, 2006 2:57 PM
To: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Missed DISCONNECT

Re,

On Tue, Nov 14, 2006 at 01:05:05PM +0200, Andrius Kislas wrote:
> try
> 
> voice-port 2/0:15
>  disc_pi_off

I'm not sure whether this is actually what I want. First, if there is
a progress indication (which might include some voice announcement by
the carrier or interworking gateways) I'd like the user to be able to
hear it instead of forcibly tearing down the call. Second, the docs
state that

   The disc_pi_off voice-port command is valid only if the disconnect
   with PI is received on the inbound call leg.

which doesn't apply to my case, where it is received on the outbound
call leg. The docs may however be wrong here, as the following text
doesn't make sense and explains the case vice versa.

The problem I'm seeing is IMO not due to the PI but due to a facility
IE the router cannot interpret - probably erroneously, as I cannot
really imagine a carrier would send defective IEs. The IOS in
question is 12.3(11)T2 for several reasons (mainly H.323 Gatekeeper).
The user never gets any message that the call disconnected until the
relevant timer runs out, neither inband tones nor any feedback on
the display.

I'll have a try on disc_pi_off in a test window, though, as it might
help against the cases where the remote user hangs up at the end of
a call and the local user gets a busy instead of a hangup, so they
have to hang up explicitely at the phone. Annoying when you are using
a headset instead of a handset. I've just retested this and it happens
only when I call the remote, but not when the remote originated the
call to me. Sounds as if the docs really got it the wrong way around.
Or it is due to the AOCE charge facility IE that is only present in
the DISCONNECT when it was an outgoing call. Seems I've to further
debug this...

Thanks,
Andre.
-- 
                  The _S_anta _C_laus _O_peration
  or "how to turn a complete illusion into a neverending money source"

-> Andre Beck    +++ ABP-RIPE +++    IBH Prof. Dr. Horn GmbH, Dresden <-
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip