Hello All ,
i want to bring this matter to the discussion , i Hope it will Help .
In a similare call flow (not strict , its applies on all the call flows with CCM/PRI controlled by MGCP existance)
PSTN-->MGCP PRI-->CUCM-->IP Phone (SCCP)
and you facing issue that When PSTN hang up the call, internal IP phone does not hang up by the meaning : the call remain established until the ip phone hang up the call or the T306 timer Kick in , here is the explination of this behaviour :
=======================
in the deb isdn you usually see this ISDN messages exhange (example) :
13:57:22.561 Q.931 0x002D SETUP RX <-- 89.13.198.7 13:57:22.599 Q.931 0x802D CALL_PROC TX --> 89.13.198.7 13:57:22.599 Q.931 0x802D ALERTING TX --> 89.13.198.7 13:57:24.598 Q.931 0x802D CONNECT TX --> 89.13.198.7 13:57:24.701 Q.931 0x002D CONNECT_ACK RX <-- 89.13.198.7 13:57:34.833 Q.931 0x002D DISCONNECT RX <-- 89.13.198.7 13:57:53.056 Q.931 0x802D RELEASE TX --> 89.13.198.7 13:57:53.142 Q.931 0x002D RELEASE_COMP RX <-- 89.13.198.7
so from the debugs it looks like the CCM didnt send the RELEASE immediatly so all the attention turn to
be on the CCM side and you start thinking that this is a CCM defect or so .
if you took deeper look to the disconnect message body , and if you see PI in the Disconnect message body
13:40:12.694 Q.931 0x006C DISCONNECT RX <-- 89.13.198.7 Cause i = 0x8090 - Normal call clearing Progress Ind i = 0x8288 - In-band info or appropriate now available
#the root cause of this issue is that the MGCP protocol doesnt handle/convert the disconnect with PI and this
is the natural of this prtocol so in the CCM traces you will the CCM transperent to the disconnect message
and the call will only Tear down if the ip phone simply hang up the call or the T306 Kick in.
