I have a 2801 gateway with 4 port FXS/DID card and about once a week, a voice port will get stuck in S_SETUP_REQ_PROC VTSP state and we need to go in and shut/no shutdown the port to clear it. Resetting the MGCP Endpoint in Call Manager also clears the issue.
We were originally on 12.4(11)T2 IOS and I found a bug with this issue, and it said it is fixed in 12.4(11)T4 so we upgraded to current 12.4(15)T which was 12.4(15)T6 at the time, but then we had a seperate FAX issue so used 12.4(11)T4 which has bug fix for this. After 1-2 weeks of being on that, we are having this problem again.
Just wondering if anyone has seen this with the FXS port getting stuck like this. We need to use MGCP as this port is shared with IP Phones and goes to a overhead bell so when the phone rings, the overhead bell rings at same time.
Below is capture of show voice-port trace from before we cleared the port of being stuck.
Call Manager version is 6.0.1-2000-4
MMD-2801-1#show voice trace 0/0/0
0/0/0 State Transitions: timestamp (state, event) -> (state, event) ...
I've seen it happen in SCCP (I don't use MGCP) and the fix was in 12.4.15T5 I think.It seemed that the gateway and callmanager got out of sync under heavy traffic loads(congested WAN link). The site finally upgraded their WAN at around the same time as we upgraded IOS. I don't know which fixed the issue,
With SCCP/skinny, the ports don't appear to be hanging up and getting stuck anymore, but when a user picks up the call on their IP Phone the FXS port on gateway is in S_SETUP state until they hang up the call on the IP Phone. The extension is a shared line across 3-4 phones and the FXS for over head bell and when they pick up call on IP Phone the FXS port should go idle (it does with MGCP) but with sccp it is staying active (bells stop ringing after IP Phone user answers call) but then other calls the site gets when someone is on phone don't ring the overhead bell until no one is using the extension again.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.