William Bell Fri, 03/26/2010 - 12:15
User Badges:
  • Purple, 4500 points or more


I had an issue like this over a year or so ago.  The tactical fix to the current state is to restart the stcapp application on the router.

conf t

no stcapp


This isn't guaranteed to fix the state the ports are in.  You may also have to reload the router.

In my case the root cause of the issue was two fold.  One, I was running into a couple of software defects:

/* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin;}


Externally found moderate defect: Duplicate (D)

VG224 issues fast busy tone on going offhook


Internally found moderate defect: Resolved (R) No dialtone on VG224 endpoint when more than one line configured


Internally found minor defect: Assigned (A)

VG224 Endpoints may lose dialtone after Immediate Switchover

Second, I did not have all VG224 ports configured on the CUCM system.  By this I mean the VG224 was added to the system but not every port was configured on the CUCM (so, some had the ol' "?" icon).  The VG224 did not know this was the case and kept trying to register the unconfigured ports.  This caused a general stability issue with the stcapp and eventually caused the router to start unregistering other ports.  IOW, I would see the exact symptoms you describe.

Now, that isn't to say you have to have the same provisioning discrepency issue I had.  The IOS software was just super buggy and there was more than one way to tickle the bugs.  That being said, the short term solution (in my case) was to go to either configure all of the ports in CUCM so they would register OR shutdown the voice ports on the vg224 so they would stop trying to register.  We did that while we researched and tested a viable IOS replacement.  Even then, the stcapp was still unstable.  It just took longer for the gateway to start having issues.

The long term solution was to deploy 12.4(15)T code (at the time it was T3, today I think they are on T12).  That alleviated the stability issues and it is actually the code I use for other customers now.  There was some dodgy issues in the T7 to T9 release (one I ran into was T.38-CA controlled with MGCP).

So, the question I have is which release of IOS are you running?  How often does this issue occur?  Do you have the same provisioning discrepencies I noted?  Can you/have you tested the gateway with 12.4(15)T?

Oh, in general I recommend that if you have a provisioning discrepency between the CUCM and the VG-224 that you resolve it by configuring all ports in the CUCM or shutting down/disabling the stcapp association in the VG-224.  Even if it isn't causing stability issues, it is murder on the syslog/event log.



Please remember to rate helpful posts.


This Discussion