SX2000 Absorbed Digits and PRI Outbound Caller ID 2

[MightyGorilla]

We have a mostly-functional connection between our SX2000 and an Asterisk box, but I still have 2 problems:

1. The Mitel is stripping 3 digits from the extension number before passing it out the PRI card, and I haven't been able to locate where this is configured.

2. Calls from the Asterisk side show caller ID on the Mitel, but calls from the Mitel do not show any caller ID on the Asterisk. Is there something that must be turned on in IMAT for the PRI card to send the calling extension?

Thanks!

 

[SXWizard]

1. Digit striping is done by the Digit Modification form index number assigned to the ARS route that is being used to make the calls to the Asterisk.

2. Yes, the CPN is controlled by a table in the PRI card that is programmed using IMAT.

 

[MightyGorilla]

Thanks for the info SXWizard,

Unfortunately, that leads to some follow-up questions

I've already created a Digit Modification Number (2) with 0 digits to absorb and no digits to insert, and assigned that in Route Assignment to my route. Is there somewhere else this can occur?

I don't have a current support contract anymore. And I'm not sure there is even a Mitel vendor in my state (Arkansas). We were using a vendor from Oklahoma previously. I wasn't provided with the IMAT software when they installed the PRI a few years ago. Would it be possible for you to assist? Can you remotely connect with IMAT or sell us a copy? I'm happy to pay for assistance - but I'm not sure our old vendor will do service calls without an annual contract, and I'm not interested in going there...

Thanks-

 

[mitelmitel]

Are you sure that the Asterisk is not absorbing 3 digits?

 

[MightyGorilla]

The diagnostics logs on the server show only the 4th digit + being passed in.

Furthermore, I'm not aware of any DAHDI configuration options that absorb digits. The entire dialed number is passed into the dialplan via ${EXTEN}, and if you want to ignore the first 3 digits and use the next 4, you just shave them off like ${EXTEN:3:4}.

At the moment, I'm all but certain it must be another setting in IMAT. I've looked through every form in the Mitel, and I don't see any other relevant configuration options.

Anyone interested in working on my switch? Looks like I'm stuck without that stupid IMAT utility.

 

[SXWizard]

Connect a laptop to the RS232 port on the PRI card adaptor on the rear of the DSU. Set your ProComm or Hyperterminal to 38400. Type "option +dispcall" (do not type the ") and press Return. Make a call from the SX2000 to the Asterisk. You should see on the screen exactly what was sent by the SX2000 to the Asterisk. When done testing type "option -dispcall" to turn off the trace.

 

[kwbMitel]

Most likely the IMAT configuration is set up for call-by-call selection. When setup this way, the first 3 digits are used to select options for transmission (bearer, facilities, and CLID).

You can either use IMAT to turn off call by call by designating the call types or you can add digits to select the appropriate types.

sending a 000 will select Voice/Default network/Send CLID

Simplest test would be to insert 000 in the modified digit string.

001 would block CLID

surronding the digits with brackets {000} will remove the digits from being reported in SMDR.

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

 

[MightyGorilla]

I'm on the road for a week, but thanks for the info, and I'll post back my findings as soon as I get back to the office.

 

[MightyGorilla]

I had a coworker run the option +dispcall command on the PRI card and perform some test calls.

When dialing from extension 7795 on the Mitel to extension 3660 on Asterisk:

>>>OUT: 10/04/15 12:13:39 @ 0

When dialing from extension 3661 on Asterisk to extension 7795 on the Mitel:

>>>IN: 10/04/15 12:20:47 7795 @ 3661

This seems to indicate that the Mitel is not sending the digits, but does this assist in any way to pointing to why?

I'll have to wait until I get back to try the other suggested test.

Thanks-

 

[kwbMitel]

Check the Call by Call settings in the PRI card as I mentioned earlier.

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

 

[MightyGorilla]

I created a digit modification plan to absorb no digits and insert 000 and assigned that to the route - but this had no effect on the caller ID. It is still blank. It did "fix" the stripped digits issue on the dialed extension in a hacked sort of way by just inserting some sacrificial digits, so that was good - but I know that wasn't the real intent.

Should I conclude from this that IMAT is my only way to solve the issue?

Thanks-

 

[kwbMitel]

It is a reasonable assumption that Call by Call is enabled. The only way to modify the Call by Call settings is with IMAT.

The digits are not "Sacrificial". The digits are processed by the PRI card to choose the call by call settings. In the process the digits are absorbed.

IMAT is also used to designate and enable outbound caller ID.

So... Yes, Imat is the only way to resolve your issue(s).


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

 

[MightyGorilla]

Well, I got a copy of IMAT, and found the second port on the card was completely unconfigured (most fields were set to null). After the basic settings were configured, it stopped absorbing the first 3 digits, and I was able to set the CPN substitution list so that the card outputs the caller ID.

So that's some great progress, but I'm still left with a few things to scratch my head about...

1.) Do you really *have* to use the CPN substitution list to get the card to output caller ID? The term "substitution" implies (to me anyway) that normally the card would output the calling party's extension number. However, if you don't define a substitution, it uses the default CPN. Did I overlook something?

2.) Where in IMAT is the D-channel identified? Or is it permanently set to channel 24?

Thanks

 

[kwbMitel]

The CPN Substitution is modifying the Extension (typically 4 Digits) to an external number (typically 10 digits in NA) so yes the word subtitution applies. On the 3300, they have recently enabled the ability to use the associated device field to substitute CLID. I don't think the SX-2000 has the equivalent ability so Yes IMAT must be used.

The D-Channel is not defined anywhere. It is channel 24 always.

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

 

[MightyGorilla]

Thanks for the info, but this still isn't quite clear, so let me rephrase a bit. For example, I have entered the following into the CPN Substitution list:

Default CPN: 1234567890

DID Substituted CPN
1234 1234
5678 5678

Is this our only way to get the CPN passed on outbound calls? It sure doesn't make much sense to me if so, considering how redundant it is, and how very limited with the substitution list only allowing 100 entries, and we have many more DIDs than that.

We don't need a 10 digit number to be substituted for a 4 digit extension number, because the PRI is only acting as a trunk between internal systems. We just want the extension that dialed the number to be passed as the CPN. We have a different PRI connected to the PSTN.

Thanks for your patience...

 

[kwbMitel]

The The Substitution table should be set up like

DID Sub
1234 2012221234
5678 2012235678
4000-4099 201320XXXX
6222,6225 201321XXXX
2345 2012221234

The default Number is sent if the DID is not found in the DID table. The substituted number MUST be the full dialable number for the digits to be sent. Wildcards are allowed in the substitution to allow for range entries or entries with identical prefixes. The substituted number does not need to match the DN in any way.

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

 

[MightyGorilla]

Thanks for everyone's help - these problems are resolved.

In review:
The 3 digits that were absorbed by the PRI card were related to the "Per Call" setting in IMAT as kwbMitel said, which apparently is the default.

The calling party ID not being passed on outbound calls was pretty confusing. The IMAT documentation seems to have some mistakes in it in the Outgoing CPN Substitutions section where it states, "Rather than sending the actual directory number, you may want to send a substitute or default CPN value." This is apparently incorrect - you MUST enter substitution entries for the card to output any digits. (at least I could not find a setting that would output the directory number, and I tried several.) The substituted number does not actually need be the full dialable number for the digits to be sent. The card is working properly with the substitution list set as follows:

DID Sub
2000-2999 2XXX
3000-3999 3XXX
4000-4999 4XXX

IMAT forces you to start the Substitution list with a number, so you can't just make one entry for all of them like this:

DID Sub
2000-4999 XXXX

 

[kwbMitel]

Your statements below are not correct:

"you MUST enter substitution entries for the card to output any digits"
-If a DN is not in the CPN table and the Default CPN is configured then the default CPN will be sent for that DN.

"The substituted number does not actually need be the full dialable number for the digits to be sent"
- The Telco will not accept anything less than a fully dialable number as the CLID. Your statement might be true if you are connected to something other than the telco and that device is configured to accept any length of digits but your statement is incorrect for general usage.

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

 

[MightyGorilla]

If a DN is not in the CPN table and the Default CPN is configured then the default CPN will be sent for that DN."

-That's right. I didn't state it clearly, but what I meant was, you HAVE to populate the Substitutions Form to get the card to output digits (whether they are specific or the default).

"Your statement might be true if you are connected to something other than the telco and that device is configured to accept any length of digits but your statement is incorrect for general usage."

-Ok. I wasn't trying to be smart, I just wanted to clarify that it would output fewer digits. I had already stated this PRI was not connected to the PSTN.

Thanks for your help.

 

[kwbMitel]

Cool, By this point I had forgotten what you were connected to and I'm sure others might have been mislead by your post.

I now understand what you meant regarding the CPN tables. Yes, at a minimum the Default CPN must be defined to output any digits. Optionally, the ranges can be used for substitution on a DN basis if the CLID is differnt than default.

I only delved into the specifics due to your claim that the manual had "Mistakes". In my opinion, the documentation is correct.

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