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!

 

[bartshandle]

kwbMitel and LoopyLou thank you both for your thoughts. You have helped me understand this in a better way than the manuals.


I know that the Trunk Service Number for the "DID" in question is 17 as I discovered in the Trunk Service Assignment form.

Going back to the starting point, I knew that this system uses an analog DID card in an peripheral cabinet and this was once an SX2000 system, I referred to the SX2000 handbook on Analog Dial-In Trunk programming:

PAGE 62 of the SX2000 Technician Handbook (copied and pasted)

"Analog Dial-in Trunk
Before You Begin
Program Class of Service, Interconnect Restriction, and Intercept
Handling (see page 47).
1. Trunk Circuit Descriptor Assignment form
• There are several Trunk Circuit Descriptor Assignment forms. Use
the specific form for the type of trunk that you are programming, to
create a Trunk Circuit Descriptor.
2. Trunk Service Assignment form
• Create a trunk service number: <--- <--- <--- <--- <---
- Assign a class of service.
- Assign a class of restriction.
- Leave the Answer Points columns blank.
- To absorb no incoming digits, set the Absorb column to 0. Do
not leave it blank.
- To absorb n digits, enter n (n =a whole number) in the Absorb
column.
- To insert no digits, leave the Insert column blank.
- To insert digits, enter the actual digits to be inserted in the Insert
column.
- (Optional) Assign a trunk label to appear on display telephones
and attendant consoles during incoming and outgoing calls.
3. Trunk Assignment form
• Assign the trunk a trunk number, trunk service number, and trunk
circuit descriptor number.
• Assign the trunk an interconnect number.
4. Trunk Group Assignment form
• For an outgoing trunk, enter the trunk number in the desired trunk
group."


I started at the Analog Trunk Assignment form since the 3300 does not have the plain old "Trunk Assignment" form and proceeded to scroll through all analog trunks and look for Trunk Service Number 17.

I found Trunk Service Number 17 is being used ONLY for LS/GS Trunk on PLID 3193. I have to agree with kwbMitel that this most likely an analog POTS line and not an analog DID.

I have a tech scheduled to go to site tomorrow and I will find out if there is a POTS line that has the "DID"'s phone number.

Results to be posted tomorrow.

 

[bartshandle]

RESULTS:

When calling the line in question the telephone rings and appears to hang up, then rings and appears to hang up. This is repeated over and over again on every ring cycle. In fact the phone can only be answered during when the set is actually ringing. Between ring cycles the phone looks like it is idle.

Trunk is actually a ground start line and not an analog DID as thought(thank you kwbMitel for your persistance and direction [to quote Darth Vader on his deathbed "...you were right about me Luke, you were right."])

Based on what LoopyLou had described I was able to determine that there is no way this was a DID because there were Day and Night answer points listed and no speed dials to do the routing.

With my tech onsite we were able to physically swap the line in question with a known to be good line at the analog trunk port on the 66 block.

We then called the line in question to see if the trouble follows the line or remains at the trunk port.

The trouble stays at the line itself. So ultimately, this is a LEC issue.

Off to call the LEC...thanks to all!!!

 

[kwbMitel]

Ground Start Trunk might be the next issue.

The symptoms look like it is connected to a loop start cct.

What type of equipment is this trunk connected to?

Embedded modules and ASU's only support Loop Start Trunks.

If it is a trunk card in a per node, does the circuit descriptor define "line start type" as Ground Start?

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

 

[nytalkin]

an analog DID trunk supplies battery to the CO. Put a buttset on the switch side and dial the ext (use rotary) does the ext ring? If it does you are nit receiveing the correct digits from the CO. If it doesn't check for battery on the trunk. Trunk service should have nothing programmed for N1 N2 and should have a zero programmed in absorb unless you have a translation issue.

NO GOOD DEED GOES UNPUNISHED!

 

[bartshandle]

It is a ground start trunk and is correctly defined as Ground Start in the CO Circuit Descriptor.

The trunk was slated to be disconnected in the past by the customer...something that would have been helpful to know at the beginning. Substituting a known to be good Ground Start line on the trunk port proved that the MXe is OK. The phone re-routed correctly, this is truly a telco/LEC problem.

The root cause of this problem was incorrect documentation for the customer's site. They reported a problem with a DID without knowing that the line was actually a ground start trunk.

Thanks again, I would not have been able to solve this without reading all of your thoughts on the issue.

 

[kwbMitel]

This one was definitely a challenge.

FYI based on your last post, I would try a pair reversal to correct the issue.

If it is slated for removal however, doesn't really matter.

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