telephone A-----FXS----3600----WAN----2600----FXS----telephone B
3600's ios is 12.0.3T3,2600's ios is 12.0.4T.
when side A is calling side B, and side A hangs up later,side B can't not hang up and continue to ring until you shut down the FXS interface on the 2600.
I'm not sure whether we can resolve it by upgrading ios?or is there any other ways?
If the FXS card change to FXO card in the topology above,we met another problem.For example,side A called side B,and the session established.After side A close the session,side B can't hang up until you shut down the FXO interfaceIs.
Is there still an inherent problem with FXO interfaces running loo start, because of no disconnect supervision?Is there any new ways to resolve this?
The problem you stated about 3600 with FXS calling 2600 with FXS, and Side A calling Side B, and Side B not hanging up, can be a bug possibly related to hung ports, and we need more info to determine exactly which bug. However, the IOS versions of 12.0T that you mentioned are rather old in terms of voip and it is highly likely that you ran into some VIC hang port problem that we had. This is solved in later IOS.
Regarding your second question of FXS calling FXO side , the only inherent problem is in a condition where:
FXS calls FXO
FXO side does not answer
FXS side hangs up
FXO side continues to ring
If this is the problem you have, this is the FXO disconnect problem, and workarounds are explained in the doc below:
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...