Unknow/unknown Call type

[Volguy7]

I'm turning up an LD NI1 PRI in which the carrier says I need to flag outbound calls as Unknown. I'm connected to an NSU through IMAT. Where is this configured?


///////
| 0 0 |
----0000---0000------------------------

You can't fix stupid, you can only work around it.

 

[kwbMitel]

NI-1 does not have the option. The option for unknown call type is for NI-2 protocol. Ignore the request and move on.

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

 

[Volguy7]

Thanks. They actually stated I need to be configured for DMS-100, so if that option doesn't support that call type then I will move on. When I dial out,I get "invalid" on my display. The carrier's Q.931 messages (according to them) mean I should turn on unknown.


///////
| 0 0 |
----0000---0000------------------------

You can't fix stupid, you can only work around it.

 

[kwbMitel]

I suspect they are actually using NI-2 Protocol (Also possible with a (DMS-100).

Set your protocol to DMS-250 with the Varient set to Bellcore. Select the unknown call type box and proceed exactly as you would with NI-1.

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

 

[Volguy7]

I have option to choose a Variant with DMS-250, only with NI2.


///////
| 0 0 |
----0000---0000------------------------

You can't fix stupid, you can only work around it.

 

[kwbMitel]

Yes, use DMS-250. As I said before.

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

 

[Volguy7]

I meant to say, no Variant with DMS-250, only NI-2. IMAT 7.6.0.4, software release 7.x.


///////
| 0 0 |
----0000---0000------------------------

You can't fix stupid, you can only work around it.

 

[kwbMitel]

I have been basing my responses on your questions. I am going to go a little left field here and assume the issue has nothing to do with NI-1 or NI-2.

First, can you dial a local number?

If not, the issue is elsewhere. Most likely in your call by call settings.

Please post what you have set for the outgoing Characteristics for:

Bearer Type:
Network Varient:
CLID:

Also post what you have inserted in your Modified digits for ARS.

It would also help to know PBX type 3300 or SX200 at this point.

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

 

[Volguy7]

No, I can't make an local call, as I said it's an LD carrier.

Below if the database.txt file from IMAT on my NSU. The link in question is Link #2.


Site Options
--------------------------------------------------------------------------------
Connected Platform: 3300 ICP
PLATFORM: PRI Card
Options:: CLIP / CLIR / Data / CBC / DDI /
Created with IMAT Version "7.6.0.4"
Database Version "NSU 1.6"




===============================================================================

Link Mapping
PBX MVIP PRI Card PRI PRI Physical
Link* Link Card Variant link # logical # Type
--------------------------------------------------------------------------------
1 4 1 Dual link card 1 1 T1/DSX1
2 5 1 Dual link card 2 2 T1/CSU


===============================================================================



PRI Link Characteristics
PRI Protocol Protocol Test
logical# Type Variant Call Number Physical Characteristics
--------------------------------------------------------------------------------
1 5ESS_NI2 Invert D Channel: Off
Network Side Interface: Off
Enbloc-only: Off
Disable Fake Answer Supervision: Off
Qsig Channel Numbering: Off
Line Coding=B8ZS
Framing=ESF
Line Build Out=0-133 feet
Invert Data=Disable
Comment "PAETEC PRI"
2 5ESS_NI2 Invert D Channel: Off
Network Side Interface: Off
Enbloc-only: Off
Disable Fake Answer Supervision: Off
Qsig Channel Numbering: Off
Line Coding=B8ZS
Framing=ESF
Line Build Out=0 dB
Invert Data=Disable
Comment "XO PRI"


===============================================================================



Trunk Data

Incoming Call Characteristics
PBX
link# Trunks* DDI Delivery CPN Delivery
--------------------------------------------------------------------------------
1 01-23 Yes Yes

PRI Link: 1 Calling Party Number Prefix Insertion:

International Prefix =
National Prefix =
Subscriber Prefix =
Unknown Prefix =

PRI Link: 1 Called Party Number Prefix Insertion:

International Prefix =
National Prefix =

2 01-23 Yes Yes

PRI Link: 2 Calling Party Number Prefix Insertion:

International Prefix =
National Prefix =
Subscriber Prefix =
Unknown Prefix =

PRI Link: 2 Called Party Number Prefix Insertion:

International Prefix =
National Prefix =



===============================================================================


CPN Substitutions Setup
--------------------------------------------------------------------------------
DID1: 500-699
CPN1: 2920xxx
DID2:
CPN2:
DID3:
CPN3:
DID4:
CPN4:
DID5:
CPN5:
DID6:
CPN6:
DID7:
CPN7:
DID8:
CPN8:
DID9:
CPN9:
DID10:
CPN10:
DID11:
CPN11:
DID12:
CPN12:
DID13:
CPN13:
DID14:
CPN14:
DID15:
CPN15:
DID16:
CPN16:
DID17:
CPN17:
DID18:
CPN18:
DID19:
CPN19:
DID20:
CPN20:
DID21:
CPN21:
DID22:
CPN22:
DID23:
CPN23:
DID24:
CPN24:
DID25:
CPN25:
DID26:
CPN26:
DID27:
CPN27:
DID28:
CPN28:
DID29:
CPN29:
DID30:
CPN30:
DID31:
CPN31:
DID32:
CPN32:
DID33:
CPN33:
DID34:
CPN34:
DID35:
CPN35:
DID36:
CPN36:
DID37:
CPN37:
DID38:
CPN38:
DID39:
CPN39:
DID40:
CPN40:
DID41:
CPN41:
DID42:
CPN42:
DID43:
CPN43:
DID44:
CPN44:
DID45:
CPN45:
DID46:
CPN46:
DID47:
CPN47:
DID48:
CPN48:
DID49:
CPN49:
DID50:
CPN50:
DID51:
CPN51:
DID52:
CPN52:
DID53:
CPN53:
DID54:
CPN54:
DID55:
CPN55:
DID56:
CPN56:
DID57:
CPN57:
DID58:
CPN58:
DID59:
CPN59:
DID60:
CPN60:
DID61:
CPN61:
DID62:
CPN62:
DID63:
CPN63:
DID64:
CPN64:
DID65:
CPN65:
DID66:
CPN66:
DID67:
CPN67:
DID68:
CPN68:
DID69:
CPN69:
DID70:
CPN70:
DID71:
CPN71:
DID72:
CPN72:
DID73:
CPN73:
DID74:
CPN74:
DID75:
CPN75:
DID76:
CPN76:
DID77:
CPN77:
DID78:
CPN78:
DID79:
CPN79:
DID80:
CPN80:
DID81:
CPN81:
DID82:
CPN82:
DID83:
CPN83:
DID84:
CPN84:
DID85:
CPN85:
DID86:
CPN86:
DID87:
CPN87:
DID88:
CPN88:
DID89:
CPN89:
DID90:
CPN90:
DID91:
CPN91:
DID92:
CPN92:
DID93:
CPN93:
DID94:
CPN94:
DID95:
CPN95:
DID96:
CPN96:
DID97:
CPN97:
DID98:
CPN98:
DID99:
CPN99:
DID100:
CPN100:


===============================================================================


Outgoing Call Characteristics
PBX
link# Trunks*
--------------------------------------------------------------------------------
1 01-23 Fixed Bearer Capability:
Voice Null, Data Null
Fixed Network Specific Facilities: Unassigned (len=0)
Network: NI-2
Fixed CLIR: Voice Null, Data Null
Per Call Network Specific Facilities:
call by call on per call: Yes
Network: NI-2
0: Unassigned (len=0)
1: Unassigned (len=0)
2: Unassigned (len=0)
3: Unassigned (len=0)
4: Unassigned (len=0)
5: Unassigned (len=0)
6: Unassigned (len=0)
7: Unassigned (len=0)
8: Unassigned (len=0)
CPN Value:
Voice
Default CPN:
CPN Substitutions: 1
Data
Default CPN:
CPN Substitutions:

Numbering Plan Id:
Calling Number Plan Id: 1
Called Number Plan Id: 0

Type of Number:
Calling Number Type: 0

2 01-23 Fixed Bearer Capability:
Voice Null, Data Null
Fixed Network Specific Facilities: Default (len=0)
Network: NI-2
Fixed CLIR: Voice Null, Data Null
Per Call Network Specific Facilities:
call by call on per call: No
Network: NI-2
0: Unassigned (len=0)
1: Unassigned (len=0)
2: Unassigned (len=0)
3: Unassigned (len=0)
4: Unassigned (len=0)
5: Unassigned (len=0)
6: Unassigned (len=0)
7: Unassigned (len=0)
8: Unassigned (len=0)
CPN Value:
Voice
Default CPN:
CPN Substitutions:
Data
Default CPN:
CPN Substitutions:

Numbering Plan Id:
Calling Number Plan Id: 1
Called Number Plan Id: 0

Type of Number:
Calling Number Type: 0



===============================================================================


PBX Trunk Range Assignments
Starting Ending
TRA Id Link Trunk Link Trunk AssocTRLs TRA Description Protocol
--------------------------------------------------------------------------------


===============================================================================

Min/Max Limits Definitions

TRL Id AssocISLs Counts CxC Service Protocol/
/RejCause AssocSGLs /RejCause Min Max /Param Description
--------------------------------------------------------------------------------



///////
| 0 0 |
----0000---0000------------------------

You can't fix stupid, you can only work around it.

 

[Volguy7]

Forgot to add, I'm absorbing 1 digit.

7NXXXXXXX is to Route 1, Route 1 is a TDM trunk group with 23 channels which are my PRI channels, the Digit Mod is absorb 1. SDMR Trace shows the following

07/01 04:07P 562 1562 13214346049 T78
100 100562 G1005907A


Switch type is 3300 ICP LX


///////
| 0 0 |
----0000---0000------------------------

You can't fix stupid, you can only work around it.

 

[kwbMitel]

This is the first that you have mentioned more than 1 PRI.

You also suggest that only 1 is failing? Confirm please.

The Protocols are both set up as NI-2 with varient 5ESS which is not what you have indicated earlier.

The Call by Call settings are set to fixed but the network settings are different. The setting for #2 looks correct but not for #1.

The SMDR trace shows Trunk T78 is selected. You say this is part of your first PRI? If so your numbering system is beyond me.

Suffice it to say, nothing matches with your statements to date. Please correct where necessary.

I won't be able to respond for much longer so I'll give you a method to eliminate ARS.

Set up a Feature code for Direct trunk access.

Dial the code, then 4 digit trunk, then outbound digits.

Trunk 78 would be 0078 in this instance.

This method will simplify testing. Good luck.

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

 

[Volguy7]

I didn't mention it because I didn't think it was relevant. I listed on the post with the DB from IMAT that the link is #2. It is configured for NI2-Bellcore, because that was your suggestion and was a change from my initial post. Strange that you say #1 is wrong because that's my DID circuit which has been in use for 3 years.
Anyway, the FAC was already configured and I used it plus the trunk showing up in SMDR (0078) and received 4 rings and then "invalid". I'm not 100% sure what this means. Thanks.


///////
| 0 0 |
----0000---0000------------------------

You can't fix stupid, you can only work around it.

 

[pandabear1]

which phone switch are you working on?

 

[Volguy7]

3300 ICP LX, R.7.


///////
| 0 0 |
----0000---0000------------------------

You can't fix stupid, you can only work around it.