Paging extension "stuck", can't disconnect

[tjamro]

For some reason our paging extension is "stuck" and I can't disconnect it. We page overhead and to a few extensions, and I reset the extensions that seemed stuck but the paging extension itself I can't find anywhere to reset it. About the same time there was the following error :

Faulting application WorkgroupServer.exe, version 13.24.2504.0, faulting module CPMediaServices.dll, version 13.24.2504.0, fault address 0x000017bf.

I stopped and started the ShoreWare Workgroup Server service with no errors but that didn't fix the problem.

Any ideas?

[tjamro]

Not sure if this is the correct way to fix it, but I went into Sites and clicked the site for which Paging is under, then next to "Paging Switch" I switched the switch to a different one, clicked Save, then changed it back to the original switch and it fixed the problem.

[flyingdutchmanVa]

Reset the switches. That will clear it. Had problem last week and it fixed it.

[aclelland]

Paging button

We have the exact same issue and resetting the switch only fixes the issue temporarily. After a switch reset, it will take a few days and the issue returns. Does anyone know what service controls that on the phones?

[b7j7s7]

we had this before as well, apparently there's a registry hack that you can perform on switch to tell it from now on to disconnect paging extension after x amount of time idle. Our shoretel reseller helped me and got the registry hack from shoretel. after hack, all was well

[aholmes11]

Registry to set timeout for Paging Extension

Can you share this registry modification?

[aholmes11]

aclelland. How did you guys fix this issue? thanks

We have the exact same issue and resetting the switch only fixes the issue temporarily. After a switch reset, it will take a few days and the issue returns. Does anyone know what service controls that on the phones?

How did you guys fix this issue? thanks

[mousenut]

Please share as I have this issue also on a new install.

[aclelland]

We got a patch from Shoretel TAC to fix it

[GALuser]

Did you get the registry entry?

[jeremy]

This should do it.

--

There is a registry hack to set a timer on the overhead paging to avoid an eternal call from locking up the system if the user doesn't hang up.

*

The Siebel defect number is: 1-19427901

*

[HKEY_LOCAL_MACHINE\SOFTWARE\Shoreline Teleworks\Telephony Management Server\Settings]

String: SwitchDebug – “debug_options timeout_overhead_paging 60.”

*

Where 60 is the number of seconds for the timeout.* The customer may find that there is some number between the granularity of 60, 120, 180 that is what they really want, so let’s let it be specifiable in seconds.

*

Zero or missing is equal to “no timeout” which is the default.

*

The syntax of this string is important: e.g. the terminating period must be present.

*

If a timeout/termination occurs, the event is logged in the IPBX log as a diagnostic w/ the text “overhead page by XXXX timed out after NN seconds.”

*

Remember: this is not something that QA is regression testing.

The following screen shot shows how to use the Overhead Paging Timer registry setting combined with the Reminder Ring Timer registry setting

[saimike]

I've got the same issue, the registry hack or TAC fix would be appreciated. Our problem specifically occurs when we page to the handsets and users log-into a different handset. The page group forces the switch/handset over the limit of 16 which then hangs paging. the Timeout setting sounds very appealing

[Miersk]

There is a registry setting to reset it when it get's stuck, however, I would instead recommend upgrading and getting the fix so it doesn't get stuck in the first place.

[wrx7m]

I was having this issue and was not able to access all of the phones due to locked offices. I was able to reset the phones by going to the paging group and changing the extension to one that was not in use, saving it, changing back to original extension and saving it again.

This way I didn't have to down the entire phone system.

[jpv8220]

Has anyone noticed this issue in 12.1 build 17.21.9592.0?