Trunk Ports Hanging

[Board4aLiving]

I have multiple BCM50's installed and from time to time I have the issue of trunk ports hanging and not disconnecting after a user hangs up the phone. After checking monitor sometimes they say connected to ? and could be as long as 78 hours. A simple reset of the trunk module in telephony resources corrects the issue, but it's kinda a pain. Anyoone else have this issue, and if so, is there a patch for it?

Board4aLiving

 

[biv343]

Could be a disconnect supervision issue. I've had that problem before, usually on systems that have analog trunks that come out of a channel bank.

 

[Board4aLiving]

This is on OSNA circuits from our carrier, which is pretty damn close to a normal POTS line. Have had the issue on normal POTS lines too, but mostly on the OSNA's.

Board4aLiving

 

[madwok]

Has you applied this patch which did fix the hung sympton on my BCM50 v1


BCM050.085-MODEM-1.4-1.2
------------------------
The following issues are addressed:

1. This patch introduces a new feature. It is now possible to route an incoming call to the modem based on the calling number (CLID/ANI). Via the Element Manager in the Modem Dial-In panel, a calling number can be programmed. This field will accept a phone number up to 26 digits in length. The BCM50 will redirect calls from this number to the Modem after the number of rings specified in the 'Number of rings' field.

The system will redirect an incoming call to the Modem DN if either:

- The call is presented on the line specified by the 'Line' field. In this case, the call will be redirected after the system has counted the number of rings specified by the 'Number of Rings' field.
- The calling number (CLID/ANI) of the call matches the 'Calling Number' field and the calling Number field is not blank. In this case the call will be redirected after the system ha s counted the number of rings specified by the 'Number of Rings' field where the counting starts once the calling number has been received. The calling number maybe received from the network at different times depending on the type of trunks and/or the market.

The line that the modem call is on may "AppearOnly" or "Appear&Ring" or "RingOnly" at one or more sets. These sets will ring (if "Appear&Ring" or "RingOnly" is set) and will show the line in use (if "AppearOnly" or "Appear&Ring" is set) after the call is redirected to the modem DN and the modem answers the call.

If Auto-Attendant is configured to answer the line, the number of rings in the CallPilot lines table should be set high enough such that Auto-Attendant will not answer the call before it is redirected to the Modem.

2. The following issues are resolved as part of the BCM050.076-CTI-1.2-1.0 patch included in this patch:
A. Call Pilot and Call Centre can stop working if a Hunt Group Call is being bounced between one of those applications and the Hunt Group Queue. An example would be an incoming call being answered by Auto-Attendant and transferred to a Hunt Group which has no agents available to answer the call. In this case, the call will bounce back to the Auto-Attendant and it can be transferred back again to the Hunt Group.
Q01096293

B. Lines are not automatically released when disconnected at the far end when connected to a voice port or a Control DN. Voice Ports and Control DN are under the control of Voice Mail and Call Centre. Certain types of lines will not disconnect immediately when a caller disconnects the call. This feature is to allow the far-end of the call to play a message to the caller (eg. Thank you for calling us...). When a voice port or a Control DN is connected to that type of lines, the call should be released immediately as there those applications don't have the capability to play messages in such cases.
Q01137108