Analog calls go out PRI but IP phone calls will not

[johnattechoptics]

Okay folks, got a weird one. Out of the blue (yeah, right), a customer called and said that their phones stopped working, but nothing changed. There was no power issues or programming changes. We took a look and found the following;
3300 MXe running 4.2 SP 2 PR1
1) IP to IP phone calls work
2) Analog to analog and analog calls out or in work.
3) IP to out, or in, just gets a fast busy when call connects.
4)Analog to IP and vice versa = fast busy.

They don't have software assurance and I don't want to call tech support (and use five tech credits yet).
We have swapped out the 3300, loaded a new HDD with same software, restored from backup and synced with AMC. Still using the same T1 card for now (as the analog calls come and go fine, I doubt that is the issue). Logs show CSC errors to the fact that audio resources not available, terminating. when a out-bound call is attempted. Any ideas? Oh, no other cards in system, T! is the only one.

 

[Billz66]

so you loaded the software onto a new Mxe chassis ?
and you also have swapped the HDD
- only remaining card is T1 ?
T1E1's also have other resources on the card , it could still be faulty .

analogs wont require the dsp resources to change from an - an but Ip phones may be trying to use something on the card which isn't working

I would change the T1 as well
what does the IP phone screen say when making a call ?

i wouldnt beleive the ' i didnt change anything '
only programming thing i can think of would be something like COR groups or interconnect restrictions

If I never did anything I'd never done before , I'd never do anything.....

 

[augustD2]

May be you have a problem with the E2T card

 

[johnattechoptics]

p)11406, There is no E2t card in the MXe's. I know the 3300 uses E2T, but Mitel no longer requires a seperate card in 3300. I believe it's all part of the RTC board now. Basically it's invisible to the technician. Thanks to both you and Billz66 for the input. Gonna try replacing the T1 card and will probably try a different 3300 as well.

 

[12345kevin]

We had a similar problem recently when we changed out an MXe chassis for what turned out to be a very early one which we had previously used with only a Peripheral Cab and PRI. We needed to add an echo canceller card to enable calls between TDM and IP.

Calls were ringing OK but getting "busy" tone when answered.

 

[augustD2]

The E2t is built in, but if defectctive, you won't have ip to tdm connection. I don't think the PRI card will change anything since you cannot call from analog to ip.

 

[LoopyLou]

Johnattechoptis, actually depending on the controller and the number of channels there can still be a separate E2T card. The basic chassis has 64 E2T channels however if you wish to bump that up on an MXe you can add the expansion kit which adds 64 more E2T channels ( and 64 more echo cancellors ) for a total of 128 E2T channels ( and 128 echo cancellors ). Sounds like you have a basic MXe with only 64 Channels.

If analog to analog and analog to PRI ( T1 )are fine, neither uses the E2T and would suggest the T1 is fine. If you can't call the analog sets from IP it would use the E2T so it might suggest the problem is there. You did say you swapped the controller so that should have addressed the E2T issues ( i.e you basically replaced it ). Calling analog extensions doesn't use the T1 card so replacing it doesn't necessarily help as already stated by p011406.

Can you conference two analog sets? Conferencing uses the E2T. Is there embedded voicemail? Reaching the embedded VM from an analog set would require the E2T. Like Billz66 says I never believe the old "nothing has changed" statement because to me it sounds like the E2T isn't the issue although 1234kevin brings up an interesting point.



You can't duct tape stupid.

 

[danramirez]

I have had a similar issue with an old MXe Controller (only one Processor). When calling from IP to TDM device, users got fast busy when answering the call. At that time I raised a ticket with the support guys and sent sys diagnostic file. They found out that there was a lack of echo canceller resouces therefore the embeded echo canvellers where not working. I had two options, to replace the controller or to add a 128 echo canceller. I chose to add a 128 echo canceller and I haven't heard again of that customer complaintning about it.

What I don't like is that you have changed controller and continue having issues.

Try adding a 128 echo canceller if you have one in your stock room.

keep us posted, we'd like to see the end of this one

cheers,

daniel

http://www.hatkana.com

http://www.wtelecom.com

 

[kwbMitel]

This will definitely either be a defective expansion processor or defective Echo Canceller.

E2T resources are not available.

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