DID Configs not working (HELP) 2

[TriniTech87]

So I have an Issue with a DID programming
I'm getting the calls going to my auto attendant rather than going to the programmed extension via the command incoming call handling treatment trunk group


I'm getting 7 digits from my provider and deleting 7 and inserting the extension xxxx

 

[kyle555]

What's your autoattendant? A VDN? Voicemail?

Typically, you'd never answer if you didn't know how to deal with the digits, so you must be matching something in that ICHT table.

 

[TriniTech87]

None of the above it's a OS Avaya one X but I checked did/tie/isdn/sip intercept treatment in system para features page 1 the intercept treatment says attendant

 

[4merAvaya]

Try putting a trace on the trunk group (list trace tac [trunk access code]) and dial a DID number. Post the results here.

Kevin

 

[TriniTech87]

so it shows no activity

 

[4merAvaya]

TAC 7151 is the tac for the trunk group in question?

Kevin

 

[TriniTech87]

YEP TAC 7151 TRUNK 151

 

[mattKnight]

I suggest the calls are not arriving on that trunk group.

No activity, no call

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[TriniTech87]

I'm thinking the same but when the number is dialed it still manages to hit out Operator it does not go to a VDN or extension my services provider is insisting that is PBX issue on my end

 

[TriniTech87]

I uploaded an image of my system parameters do you think the section with the did/tie/isdn/sip intercept treatment has anything to do with the calls being routed to the attendant

 

[joe2938]

do you have another trunk that it may be coming in on, your trace confirms that is is not coming in on that trunk group

 

[DAVIDPAYNE]

How many inbound trunks groups do you have?
What type of trunks are they?

 

[AvayaTier3]

make a test call and when your attendant answers, status the attendant or station where the call is answered to identify the trunk port connected to the call. This will tell you which trunk-group your DID's are coming in on.

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[TriniTech87]

@David

We have One mainly for inbound calls
The rest are in and out trunks additionally we only have one ISDN Trunk the rest are copper CO Trunks
The DID Trunk has been programmed with a Channel from the ISDN TRUNK

I'm not sure if this may be an issue

 

[joe2938]

do as avayatier3 has suggested, this will tell you what trunk the call came in on

 

[TriniTech87]

So guys I traced the att st 1500 and this was the results
I did not show a connected port

 

[joe2938]

no status the attendant

 

[janni78]

status attendant x"

"Trying is the first step to failure..." - Homer

 

[TriniTech87]

This is a bit odd it's connected to CO Trunk which is assinged to all Incoming calls however the number I'm calling is A DID WHICH IS NOT in that group

 

[joe2938]

wanna bet you just proved yourself wrong, contact line provider and have number ported onto your pri, as number comes in on your copper trunk group