[cisco-voip] FXO hang due to connectivity loss?

[Ki Wi]

The team reported that when there's an minor WAN outage, the FXO ports will
not get disconnect by itself even disconnect tone is defined and working
fine normally.

Regardless it is calling or called party hang up, I'm expecting the voice
gateway to put the FXO port to on-hook status whenever the predefined
disconnected tone is detected.

If there's no definite answer, might need to open a TAC case to conclude
this.


On Thu, Dec 14, 2017 at 1:41 AM, Norton, Mike <mikenorton at pwsd76.ab.ca>
wrote:

> Are you sure that the gateway is properly detecting the tone and hanging
> up when connectivity *is* working? FXO disconnect is terribly hit-and-miss
> even at the best of times. Disconnect supervision on FXO is more of a
> best-effort attempt than an actual thing.
>
> If the disconnect signal is properly interpreted by the gateway then like
> you I would expect the gateway to end that leg of the call regardless of
> SIP reachability. But I consider that a pretty big if!
>
> -mn
>
> *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] *On Behalf
> Of *Ki Wi
> *Sent:* December 13, 2017 12:34 AM
> *To:* cisco-voip at puck.nether.net
> *Subject:* [cisco-voip] FXO hang due to connectivity loss?
>
>
>
> Hi Folks,
>
> If the voice gateway is defined with disconnect tone/ cadence,etc. Should
> a loss of connectivity (SIP signaling between VG and CUCM) cause the FXO
> port not to hang up ?
>
>
>
> To me , SIP is peer to peer signaling. It should not affect the voice
> gateway decision for going on-hook when a disconnect tone is detected even
> there is a loss of connectivity to CUCM.
> --
>
> Regards,
>
> Ki Wi
>



-- 
Regards,
Ki Wi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20171215/2415af47/attachment.html>