We're having a strange issue with our locations configured with FXO ports only where they eventually stop working. Incoming calls get one ring and then dial tone. Outgoing calls work fine. When issue show voice calls, each port diplays something like this:
0/2/1 - - - vpm level 1 state = FXOLS_ONHOOK
vpm level 0 state = S_UP
calling number , calling name unavailable, calling time 12/17 16:11
running the ccm-manager command I see the latest MGCP failover / switchback occured yesterday evening when I assume everything stopped working.
I can reset the gateway and nothing happens. The only way to resolve this issue is to physically restart / reload the router.
Is there any other way?
I'm running 12.4(6)T5-SP-SERV-CRYPTO on all 13 locations. Only the 4 locations without a PRI are having this issue.
There is a distinct possibily that you are running into a known issue given the version that you are currently running.
It is assumed that the other gateways with FXO ports exhibit the same symptoms following a fallback to SRST and then re-registered with CallManager?
In such cirmstances have you tried restarting the MGCP app rather than reloading the gateway? Initiate a 'no mgcp' then 'mgcp'.
I have experienced various issues with MGCP, FXO and SRST under 12.4(9)T, symptoms similiar to those you described. In most cases you could hear alerting on the pstn call leg, however there was no ringing on the phone, this was directly after the gateway re-registered. Given the time constraints it was difficult to troubleshoot and raise a Tac case. It was far easier to configure the gateway for H323, after which there were no issues after fallback.
I will take a look and see if there are any known issues similar to what you have described.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
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...