PRI CHANNELS BUSY

[pea123]

Greetings.

I have an Mxe 111 on release MCD 5. I have one port of E1 connected to PRI. The problem is that all the PRI channels frequently become busy on their own whilst there will be no users on it. As a result there will be no incoming or outgoing calls.Disconnecting and reconnecting the PRI does not change the busy condition neither does changing the E1 port. This persists until Telco resets their side only to reoccur later.(There will be no alarm on the Mxe and the E1 port led is always GREEN)
Whenever the channels are free calls are cut-off at just under 3mins. Telco has said the problem is with the Mxe.
Could you please advise on what I can check to correct this situation.

Thank you.

 

[wireman50]

Have you tried to manually un busy them from maintenance? Mainteance commands all / RTS <unit> <shelf> <slot> <circuit or hybrid> <channel> or if they are all out then RTS <unit> <shelf> <slot> should do it. You may have to manbusy them first.


It sounds like the Telco is not seeing a call clear from the MXe for some reason (if it were analog then you would look at disconnect clear time) but I'm not sure where to look for PRI lines with regard to clear conditions.

Perhaps KWBMitel or one of the other guys can help here.

 

[wireman50]

Oh as an after thought I would also check Program Embedded PRI/QSIG Trunks as well.

and finally are these new trunks or has it just started happening? If its just started happening it could well be something has changed at the telco despite their protestations.

 

[danramirez]

Do a RESOURCE <PLID> of one of the PRI Channels, that will tell you what's the channel is connected to.

It happened to me in a Cruise with an SX2000, all channels were busy and apparently no one was on the phone, the result I found after issuing the RESOURCE command was that the channels for some reason were conferencing to each other. I didn't have enough time to find out why this was happening as I had to unboard the cruise. To fix it, I Interconnect restricted all channels on the PRI, but I made them aware that they were not going to be able to make conferences. (That was not an issue for the, those were the trunks that the passengers used for making call using phone cards.

Hope this helps, Cheers,

Daniel

http://www.hatkana.com

http://www.wtelecom.com

 

[jrgood0852]

It could be you are not getting the correct handshake on the E1. Settings may need to be tweaked.

Always look out for the next guy because it may be you!

 

[pea123]

The PRI is a new installation.

 

[wireman50]

Then I would check the programming as a first step using the help file to assist if need be."Program Embedded PRI/QSIG Trunks

 

[pea123]

wireman50
Then I would check the programming as a first step using the help file to assist if need be."Program Embedded PRI/QSIG Trunks"

Im not sure what you mean me to check as the trunks do come up at some point and the Mxe never give an alarm. Please clarify.
Thank you.

 

[wireman50]

There are settings that may be wrong in the programming of the trunks that will not bring up an alarm but may cause issues with operations. (see danremirez comment above). Most alarms on PRI links have to do with BER and slips and actual synch problems. Slips will only bring up an alarm after a a while and so will BER. Too many slips will eventually force the system to take the link out of service and it will not come back in till you do it manually or reboot the switch even after you have cleared the fault buffer. Busy trunks will not bring up an alarm for instance since it is a normal state for the trunk (busy that is in its basic function). If you manbusy all the trunks you will not get an alarm just system busy if you try to seize a trunk.

Short bit again There are settings that may be wrong in the programming of the trunks that will not bring up an alarm but may cause issues with operations.

How did you program the trunks? manually or through the tool?

 

[danramirez]

pea, where are you deploying that? can you name the service provider?

If you are in the UK you must use Euro ISDN as your protocol, have you donde that?

http://www.hatkana.com

http://www.wtelecom.com