Ground start trunk ports not answering calls after network outage - CS1000E 7l5

[curtismo]

Has anyone experienced an issue where after a network switch outage for code update ground start trunks will not answer incoming calls until the card or port is "waked up" by seizing it using a maintenance telephone or disabling and reenabling the card?

Synopsis: Recently upgrading Ethernet switch code at locations throughout the network, which causes the MGC card in cabinet(s) to unregister from the CS then reregister as the Ethernet switch reboots. Today get a call that a particular ground start hunt group is not answering calls. Calling in I know I have the first line in the hunt group but STAT shows the trunk is not going busy. Using a maintenance phone I am able to seize that trunk and make an outgoing call. After this the particular trunk takes calls as normal.

I have multiple cabinets (12) on two different CS1000E systems and I have seen this occur on both systems. Sort of now seeing conincidence between the Ethernet switch reboots and these strange trunk issues. Today's issue happened in old 11c wall cabinets; also have had this occur in CS1000E chassis systems too. I've seen it affect single and multiple trunk ports on the same card. Sometimes all I do is go through and seize dial tone on each port and never hear any more problems.

CS1000E patches are through last fall.

 

[curtismo]

BTW, I am fairly sure it was not a CO issue because as soon as I made that first trunk busy by calling it, calls to following trunks in the hunt group receieved incoming calls (from me listening to ringing on the first member).

 

[KCFLHRC]

I wonder if the dsp resources were down when this was happening? Call set up was there but no audio?

 

[curtismo]

This issue has been found hours after the IP outage, and other items in the cabinet (digital sets) are getting DSP resources. I haven't run a TRAC on the incoming trunk channel, but STAT of that unit show it to be IDLE instead of BUSY during the attempt to call in.