03-26-2010 09:46 AM - edited 03-19-2019 12:41 AM
Hello Friends!!!
I have a problem with my VG224; some extensions doesn´t work; the state of some extension are: INIT.
How can i fix that???
I have attached the "show stcapp device summary"
I dont know what happen with my VG224.
Regards!!!
03-26-2010 12:15 PM
Roberto,
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
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:
CSCsf02998
Externally found moderate defect: Duplicate (D)
VG224 issues fast busy tone on going offhook
CSCse77760
Internally found moderate defect: Resolved (R) No dialtone on VG224 endpoint when more than one line configured
CSCeh74347
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
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.
HTH.
Regards,
Bill
Please remember to rate helpful posts.
Please remember to rate helpful responses and identify
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide