I have analogue trunks connected to the on-board/ embedded card of a controller.
The problem is that when the trunks are called they do not ring the answer point defined in the trunk attribute form.
What might be causing this?
What is the make, model and software version of the system you're working with?
How do you know the calls are reaching the PBX? Have you tried changing the answer points to see if it will ring somewhere else or reach another destination? For example, change the answer points to the voice mail pilot number. Then call your trunks. If you reach VM, you've eliminated the trunks as a cause of the problem. If you don't reach VM, you may have an issue with the service provider.
Or, if your system has monitoring capabilities, try monitoring inbound calls to your trunk ports to see if they're reaching the system.
By monitoring in Crich01's response, I believe he means can you connect a buttset / monitor set to the line in parallel and verify that the line is presenting ringing to the system.
Do you know that the Trunk has the appropriate Class of Service functions
Are you migrating from an old system? Do you know the trunks are loop start? Might they be ground start?
If 3300, have you assigned the correct trunk attribute table to the trunk?
Yes please provide system type and SW level.
**********************************************
What's most important is that you realise ... There is no spoon.
This is a migration from a legacy/ traditional pabx to Mitel.
The trunks ring fine on the old pabx and they are loop start. Yes the trunks have the appropriate COS functions and Trunk Attributes.
Mitel 3300 CXII Release 8.0 PR1. Active Software: 14.0.0.91
Simple test.
[ul]
[li]Program up an analog phone on the AMB[/li]
[li]use a standard line cord to connect the analog phone to the loopstart trunk port[/li]
[li]call the analog phone[/li]
[/ul]
What happens?
**********************************************
What's most important is that you realise ... There is no spoon.
AMB is brand new and I can pick the trunks with the individual trunk access feature code and also the ONS on it are fine.
But when I pick the trunk as above I get a ringing tone instead of a dial tone. I wonder why?
Now you are confusing me. You said "The problem is that when the trunks are called they do not ring the answer point defined in the trunk attribute form"
Do the ONS sets ring when you call them? Are you ringing the analog phone extension number or picking up the handset? Can you dial the destination via an ONS and by an IP phone and it rings?
If you dial a trunk from external and, even if they are not ringing, pick up the call?
You heard the problem correctly. I advised to configure an extension on the embedded ports and connect to the trunk port. I am saying that extension (ONS) is working fine and it shares the same embedded with trunks so the card must be fine and not faultyAMB
It looks like trunk attribute 3, from my quick look at this. You pictures weren't all that helpful and there isn't much detail to go on. Go through each analog trunk and record the truck service number used, if all the same that is the value in the trunk attributes that we need to see full values for.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.