3300 MXE with a DID that will not reroute

[bartshandle]

I have a 3300 ICP Mxe running 7.1.4.9_1 and it uses some analog DID trunks.

I have one DID number in particular that will ring without answering (for 3 minutes) and then disconnect the call.

There is rerouting assigned to the Superset 4025 telephone, it is supposed to send calls to the embedded voicemail extension for all types of calls. (all set to "THIS")

Call forwarding at the set has been disabled but the DID still just rings, and rings...

How do I get the DID to ring the phone properly and then forward/reroute to voicemail?

Thank you in advance!

 

[kwbMitel]

Analog DID on a 3300???

I don't think so.

By Analog do you mean 2 wire copper trunk with dialtone?

If so, please elaborate what you mean by DID.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[mitelmitel]

kwbMitel - why not? have installed many 3300's with an LS/GS card running analogue trunks. [CXi]

I dont think this person is though due to the low SW level, they would have all sorts of problems with trunk call quality, etc.

To the OP - you need to run a CCS Trace to ascertain where this call is going.

Is this station definately the DID you think it is? Press Superkey and then first line key to prove. Has it got any lcal forwarding setup? Loc Fe Ext _____ to see what features are setup.

 

[bartshandle]

KwbMitel, Yes it is using analog DID trunks: 2 wire without dialtone. (old-time original DID trunks)

chrismit, I will try the CCS trace as you suggest. I am sure that the DID is going to the correct phone (it worked before) the rerouting seemed to stop without any obvious indication as to why.

Thank you!

 

[kwbMitel]

Learned something today.

Mitel has always required specific hardware for Analog DID's on previous systems. The subject never came up for me on a 3300 so I assumed it was not avail.

My appologies.

With my newfound knowledge I would apply the same trouble shooting techniques as on Digital Trunks.

What happens when you dial the digits internally that you are expecting.

If internal dial works then issue is with trunk or trunk programming, if internal call fails then issue is with Dialed Number (DN)

Typical issues with trunk side:
- Digits expected and Digits received do not match (quantity of digits and/or number)
- Digit modification via Trunk Service Assignment (digits absorbed/inserted not accounted for)
- Wrong Trunk Service Assignment applied to trunk (Unlikely for only 1 instance)
- Digits never received (when elsewhere in your case)
- Wrong CCT descriptor applied to trunk (Unlikely for only 1 instance)

Typical issues with station side:
- DN is forwarded (locate feature ext XXX)
- DN is Out of Service (State Ext XXX)
- DN is invalid (Locate Number XXX)
- DN is routed elsewhere (call rerouting forms)
- DN conflicts with another number on system (XXX0,XXX1,XXX2, Etc.)

There's probably more but try the test and report and I can get more specific.




*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[bartshandle]

When dialed internally or from the auto attendant the call reroutes into the voicemail box as it should. This is only an issue with the DID where it does not reroute.

Thank you for the list of commands.

I am about an inch away from deleting and rebuilding the phone.

 

[kwbMitel]

You have proven that the internal DN is working. Rebuilding the phone would not likely accomplish anything.

You need to prove the trunk is receiving the digits next.

I would use a buttset to monitor the trunk, call a working DID and listen to the digits. Then call the non-working Number.

CCS trace might display digits, I've never used it with analog.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[bartshandle]

Maybe I am missing something here...but could someone explain to me which form(s) are where the DID digits are received and then translated into the extension they are supposed to ring?

The manuals are not very descriptive on this subject.

Thank you.

 

[bartshandle]

The phone does ring when the DID is called so I know that the DID is good. It does not reroute.

 

[kwbMitel]

OK then, When you said it rang in your original post I was assuming for the outside caller.

The Trunk programming with respect to digits are ok then.

Is this ringing a key on the phone or the prime line?

If a key you need to verify the rerouting is set specifically for that key.

If a primeline then try using forwarding instead of rerouting and see what happens.



*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[drsmith45]

look at the call reroute assignment form and then
the first call reroute form to make sure all the columns have "this

 

[kwbMitel]

DRsmith - if you read from the beginning you will discover that the original post covers your suggestion.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[mitelmmaniac]

What happens if you just do the feature access code for cwfd na ext?

Desk Jockey Lunacy

 

[bartshandle]

I have deleted the telephone and I still am getting RNA.

Next, in the Trunk Service Assignment form I went to the Trunk Service Number that is associated with the DID and gave it a different Non-dial in Trunks Answer Point for Day, Night 1, and Night 2 but the new answer point will not ring.

This is beginning to look more like a problem with the internal routing of the DID than a station problem.

Could someone shed some light on how DID's enter the 3300 and what forms are used to assign them to a Trunk Service Number. I am having difficulty locating this point in the system?

 

[mitelmmaniac]

Go to the maint command line, type locate number ****

Does it give you anything?

The calls hit the individual trunk, this trunk then is assigned a trunk service number.

Desk Jockey Lunacy

 

[kwbMitel]

For a DID there should not be any entries in the Day, NT1 or NT2 field of the trunk service assignment.

The DID should deliver digits to the system.

In the absorb digits field you can strip off unnecessary digits.

In the insert digits field you can add digits if necessary to modify the digits to match your dialing plan.

A typical value would be:
Day - Blank
Night1 - Blank
Night2 - Blank
Absorb - 0
insert - Blank

Can we go back to the beginning for a moment:

You originally stated that you have "one DID number in particular" that had an issue.

Please indicate how many you have that are working properly.

The changes you've made would have caused all DID's to fail leading me to this question.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[bartshandle]

The way this box is configured, the incoming DID is completely different than the actual extension number.

Specifically, DID 436-4378 which rings to telephone 407.

Filling in the Day, NT1, and NT2 fields are mandatory or else the call is RNA. I tried deleting the fields as suggested and went into RNA.

I chose a known to be working DID and changed the Day, NT1, and NT2 fields to ext 407.

The call rang the phone 407 and was rerouted to the 407 user's mailbox just like the programming fields indicated.

NOW, when I reversed the programming and took the suspicious DID 436-4378 and assigned its Day NT1, and NT2 fields to location that was for the known to be working DID, the condition was RNA.

I am getting closer to the root cause here.

If someone would elaborate in detail how the DID to trunk service number connection works I think it will help tremendously.

Thanks.

 

[kwbMitel]

I am sorry but I am back to questioning whether these are actually DID trunks.

A DID trunk is a single pair trunk that is capable of receiving digits from multiple terminating numbers.

A standard Analog trunk has only 1 terminating number per trunk.

I am going to assume you are actually talking about the latter as nothing else you have said makes sense otherwise.

This being the case, you need to look for a difference in the trunk programming other than the termination point.

In Trunk service assignment check:
- COS
- COR

In Trunk Assignment check:
- Circuit Descriptor
- Interconnection




*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[kwbMitel]

Another thought.

Still assuming standard analog trunk and not DID.

When the Non-working trunk is ringing the phone does it ring the prime line or a key on the phone. The trunk might be programmed as a DTS (direct trunk select) key on the phone which would act as you have described.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[LoopyLou]

Ok if you are using the old SX2000 DID analog trunk card it expects talk battery from the CO and digits to determine what extension it rings. As other point out the Trunk Service assignment form is used with this type of analog DID trunk card. As other have pointed out you don't program anything for day, night one or night 2 becuase you should be receiving enough digits to route the call. There is an absorb and insert field. This is to manipulate the digits received to help match the extension number. The insert is to add digits to match the extension number. I typically absorb when the centeral office sends 5 digits and my extensions are 4 digits ( absorb one ) If they send 4 and the extensions are 4 its absorb 0. You can insert to build or alter the received digits from the CO. If the received digits are drastically different then the extemsion number then use a speed dial to direct them. From what I see using Day or night means you are not using the analog DIDs as they are intended.