3300 Cannot dial in to analog #; can dial out though

[tundranugget]

When I call this analog extension, I get one-half of a ring; followed by one-half a second of static; then it hangs up.

The users are able to dial out with no difficulty.

I have replaced the telephone with a new one, but the issue remains.

Has anyone run across this before?

I am off tomorrow to troubleshoot, but wanted to see if anyone has any suggestions. The line pair follows a very convoluted path back to the Mitel cabinet (the phone is underground in a mine). I am not even sure I will be able to follow the whole path, although I have identified several intermediate junction boxes. If this is a cabling issue, it could be a long day. I can try a different PLID, but I am severely restricted as to spare line pairs (as in none available). Runing fresh cable would be an onerous task, requiring lift equipment; three bodies and a couple of days.

Here is hoping . . . .

 

[sarond]

I would hazard a guess that it is a cable fault, probably a partial short. Could be caused by dirt/lint etc... or breaking down of cable.
Can you change the cable pair?

 

[kwbMitel]

Depending on the age of the equipment it might be the line card. The old 200 Superswitches were particularily bad for this.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[LoopyLou]

So the phone can dial out no issue. Ring in trips. Does it trip in all cases ie internal to internal?

Question, where is the analog port? A per node, ASU or embedded card? Have seen this on a faulty embedded card. To test that, pull the jumper off the field ( ASU& per node ) or disconnect the RJ11 and see if it still ring trips. Basically you are removing the cable from the equation. If the problem goes its cabling. If it stays its equipment.


I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[tundranugget]

kwbMitel: We could change the line pair, but at this location to run new cable is a major problem. We might be able to narrow the section down that needs replacing. If we have to do it, we have to do it - just not looking forward to it.

LoopyLou: Thanks for the ideas. The card is in a per node. There could well be a fault there - the environment is not the cleanest. Now, if I could just call them and ask them to unplug the phone .... I will go there and test your suggestion.

I will report back.

 

[tundranugget]

OK. LoopyLou, I went to the phone, unplugged it and had a colleague call the #. The problem stayed. We traveled to the cabinet and moved to a different PLID. Now we can dial in again. Thanks.

HOWEVER - I now have a different problem with the same phone. See thread1329-1690290

http://www.tek-tips.com/viewthread.cfm?qid=1690290

.

 

[LoopyLou]

If you use the resource command what does it say for the PLID? Even though you are hung up does it still show the PLID connnected to somet thing. My guess is whatever the fault is with the line is not passing on the condition that would tell the 3300 that the user has hung up. Again from the MDF, diconnect the cross connect for the port and use your butt set to test if it still remains connected to VM when you hang up. Again if issue still present then its hardware. If issue gone but returns when you re cross connect then its cable.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[tundranugget]

LoopyLou:

I will check the Resource command next week when I have an opportunity to visit that extension. I will also check again with the butt set at the MDF. This is a two person job - one on the surface, one underground.

 

[tundranugget]

I never got a chance to check the Resouce command.

from thread1329-1690290

I visited the site and connected the butt set at the node. Again, if the call went to voice mail, the set wouldn't hang up. Shorting the line pair did not hang up the call. Putting the butt set to 'Mute' did hang up the call. I tried calling another analog set, but the results were inconclusive.

Then I noticed that the butt set was reading 18 mA instead of the normal 26 mA. I swapped the extension to a different PLID (this was the fourth alternative PLID that we tried!). The new PLID read 26 mA and the problem disappeared.

Case closed. Sort of. I still have a handful of bad PLIDS.