Troubleshooting Dual T1 Framer. 4

[troymatt]

I recently upgraded our 3300 to new hardware and MCD 4.2. Our old setup used an ASU and NSU, and I was able to connect to the maintenence port (using ProComm) on the NSU to see what was being sent the the PSTN/Carrier. Nothing was upgraded, I programmed the 3300MXe from scratch, so I may having programming issues as well, but to start with I would like to see what it is sending out. I have been able to make local, and LD calls (digits dialed and digit modification settings) but my logic isn't working for over seas (9,011 44 203 xxx xxx) it results in an Allstream recording and before I call the carrier, I wanted to know what was being sent was correct.
Thank you in advance

Troy

 

[nytalkin]

try cc trace from the maintenance command line

NO GOOD DEED GOES UNPUNISHED!

 

[brewski6666]

the exact command name is: CCS TRACE ENABLE CONTINIOUS.
do not forget to disable after the troubleshouting with: CCS TRACE DISABLE

 

[Supernova99]

I suspect the NSU has not upgraded and has now lost it's settings.
You need to use the IMAT tool to upgrade it and restore it's config.


Share what you know - Learn what you don't

 

[Supernova99]

If the NSU has not upgraded and does not have a config you can make it dial out manually by adding {000} to your outgoing digit mod

Share what you know - Learn what you don't

 

[troymatt]

Supernova, maybe I wasn't clear. I am no longer using the ASU or the NSU since the new hardware has an embedded analog card which was all i needed (3 analog extensions and 1 analog trunk). I also replaced the NSU with a dual T1 framer because I was sick of having the NSU IMAT database get FUBARed with upgrades (I always forgot to disconnect it which corrupted the IMAT programming) Any ways, I have never programmed a 3300 from the ground up (although I have been using them since ver 5), and I am unsure how to see what the dual T1 framer was sending to the PSTN so I can troubleshoot the overseas calling problem I am having.
NYtalking and brewski .... I will try it now to see if it is what i need. Thanks,

Troy

 

[troymatt]

Thanks Brewski,
So here is what I see:

07:38:11 RO1 DPN 24 ISRM_I ;10;*1#*50*5322#*100*Troy#*19*Z#
07:38:11 RO1 DPN 2D SSRM_I *58*CW*fwPs@@@@@Ek]g`#*58*C6*001#*58*C4*4*1#
07:38:11 RO1 DPN B SSRM_C 6169924278
07:38:11 RI1 DPN 7 NIM *51*3#
07:38:15 RI1 DPN F NIM *4*4#*240*`X`#
07:38:15 RI1 DPN 13 NAM *4*4#*166*1 2 3 4#
07:38:15 RI1 DPN A CCM *58*CP*G#
07:38:16 RO1 DPN 2 CRM/CIM ;30;
07:38:16 RI1 DPN 2 CRM/CIM ;30;

07:47:37 RO1 DPN 27 ISRM_I ;10;*1#*50*5627#*100*Peter#*19*Z#
07:47:37 RO1 DPN 2D SSRM_I *58*CW*fwPs@@@@@ElI_p#*58*C6*001#*58*C4*4*1#
07:47:37 RO1 DPN D SSRM_C 114053304667
07:47:37 RI1 DPN 7 NIM *51*3#
07:47:46 RI1 DPN F NIM *4*4#*240*`H`#
07:47:46 RI1 DPN 13 NAM *4*4#*166*1 2 3 4#
07:47:46 RI1 DPN A CCM *58*CP*G#
07:47:52 RO1 DPN 2 CRM/CIM ;30;
07:47:52 RI1 DPN 2 CRM/CIM ;30;

07:50:08 RO1 DPN 24 ISRM_I ;10;*1#*50*5322#*100*Troy#*19*Z#
07:50:08 RO1 DPN 2D SSRM_I *58*CW*fwPs@@@@@ElTrP#*58*C6*001#*58*C4*4*1#
07:50:08 RO1 DPN C SSRM_I 01144207005
07:50:08 RO1 DPN 5 SSRM_C 4670
07:50:08 RI1 DPN 7 NIM *51*3#
07:50:08 RI1 DPN F NIM *4*4#*240*`H`#
07:50:08 RI1 DPN 13 NAM *4*4#*166*1 2 3 4#
07:50:08 RI1 DPN A CCM *58*CP*G#
07:50:11 RO1 DPN 2 CRM/CIM ;30;
07:50:12 RI1 DPN 2 CRM/CIM ;30;

Here is what I tested.
1) First call is local 6169924278, I dial 9 before hand and get dial tone. Digit mod strips 1 digit (the 9) and it works.
2) Dial LD 14053304667 with the leading 9. My digit mod is '91' and it strips the first digit, and adds a '1'. I can see it is passing 114053304667, and I dont understand why it works. I tried the digit mod without adding the extra 1, but it didn't work. The dial string looked good (ie 14053304667), but the carrier returned that I needed to add a '1' to dial long distance! Any ideas?
3) Dialed internationally to UK 011442070054670 with the leading '90' digit mod set to strip the first digit and to expect an unknown number of digits and also a fixed number (14). The carrier returns 'The call could not be completed as dialed' and I see via the trace it appears to truncate the dial string to 11 digits and I do not know why. The rest of the digits are on the following line. Any ideas here?

 

[Supernova99]

Your international call is not being truncated The trace is normal behaviour.
07:50:08 RO1 DPN C SSRM_I 01144207005 (Supplementary Service Request Message_Incomplete)
07:50:08 RO1 DPN 5 SSRM_C 4670 (Supplementary Service Request Message_Complete)
I have tried dialling this number from the UK and it is not a valid number
Try this number 020 7008 1500 which should be 011442070081500


Share what you know - Learn what you don't

 

[troymatt]

Supernova,
I changed 1 digit in all posted numbers. The thing that is still messing with me, is regular LD is sending 1,1,405,xxx-xxxx and it is working, but if I dont send both "1's" the LD doesn't connect. Why does it need the extra digit there, and what could be messing up the UK calls ??

Troy

 

[Supernova99]

Have you tried sending a 1 in from the 011442070081500
e.g. 1011442070081500
Perhaps your carrier requires you to use a leading 1 to breakout to the ID exchange
or do not send the 0 just 11442070081500

The problem is I am the UK and unfamiliar with NA dialling plans
but these would be what I would try if I was having difficulties connecting.

Share what you know - Learn what you don't

 

[troymatt]

here is the first reply of what I got from our carrier:

{This is what I got back from our TAC team.

"Cst's calls are not getting to our network, traced and found no calls. please have cst check the dialing procedure for their equipment and retest"}

The carrier for LD is Primus, can any one enlighten me regarding what they are referring to before I call back? I can't find any 'tech speak' to tip me off regarding it.

Thanks

Troy

 

[Supernova99]

have you tried to trunk select and then outpulse the digits without using ARS?
find the individual trunk select feature access code
(normally **2)
find the trunk number you are going to use
(e.g. T101)
make sure the phone you are going to use has individual trunk select allowed.
make the call
e.g. if the ITS is **2 and the trunk is 101 dial **2 0101 01144207xxxxxxx
dailling this way will ensure that you can dial out on the trunk and will take the ARS out of te equation.
If you can dial out then it is probably an ARS CoR problem or some other programming issue.

Share what you know - Learn what you don't

 

[kwbMitel]

I changed 1 digit in all posted numbers. The thing that is still messing with me, is regular LD is sending 1,1,405,xxx-xxxx and it is working, but if I dont send both "1's" the LD doesn't connect. Why does it need the extra digit there, and what could be messing up the UK calls ??

This symptom is strongly indicative of the telco not understanding NI-2 Protocols. (Please confirm that you are using NI-2)

With NI-2, the Mitel uses the protocol to send a call flag to indicate the type of call and the digits required to identify the call.

For LD, Operator, and Overseas calls, the call type flag replaces the steering digits for these areas. (1, 0, and 01 or 011) and the system only sends the remaining digits.

When the Telco understands the protocol, everything works.

When the Telco does not understand, it only acts on the digits received and the call fails.

One fix is the one you have discovered whereby you add an additional 1 for LD. Adding an additional 011 would likewise work for overseas.

Fortunately, the Mitel has accounted for Telcos that don't understand the protocol and have a protocal option for "Unknown Call Type". When this option is selected, all of the digits for all call types are sent to the Telco with an unknown call type flag (again the flag is probably ignored by Telco). What matters is that the Telco receives all of the digits.

Form = ISDN Protocol
Option = Enable Unknown TON/NP

Description:
True or False. Check the box to change to True. This option is only available when NI-2 protocol variant is selected. When checked, this option modifies the NI-2 protocol to send "unknown/unknown" as the Type of Number (TON)/Numbering Plan (NP) in the Called Party Number Identifier of an outgoing call.

Default Value = False

**********************************************
What's most important is that you realise ... There is no spoon.

 

[troymatt]

So...
I tried the direct trunk access, and I can see the digits come out just fine .... the carrier is doing crazy stuff..... local calls dialed perfectly... LD still required me to put the extra '1' in and international just tells me I dialed wrong. I am sure it is a config that needs to be fixed at the carrier side... problem is our Pri is from vendor A, and LD is vendor B, and while they cash our cheques quickly, helping us out is a slower process

Keep u updated

Troy

 

[troymatt]

kwbMitel ....

That is an awesome explination (I am using NI2), and i will check it out to see if I can get a call out. Thanks a bunch

T

 

[troymatt]

I made the change to ISDN protocol, and changed the digit mods and viola, all is working.

kwbMitel, thanks for the straight to the end answer, and thanks to those who helped me learn a few simple diagnostic commands that will be most useful.

Troy

 

[kwbMitel]

I don't usually make it a habit to ask but in this case, I feel my contribution is worthy of a Star. You have the ability to grant one by clicking the option at the bottom of any post from a user that has provided useful information.

I typically give stars to those that put in a significant effort as well, regardless of the content. In this case I believe Supernova99 also deserves credit for his efforts.

I would also note that Stars attract attention to users that might not otherwise know how to help. I ALWAYS look at threads with stars to see what useful information has been provided as this is a way that I can learn things that I may not already know.

Don't feel obligated, I am only making a recommendation. I have more stars than I care to mention but it always feels nice to get one anyway. I've gotten a star for a simple 1 word answer "No", which I would not normally expect, so it all balances out in the end.

As to my detailed explaination, I have considered writing a FAQ for this scenario. As you may be able to tell, this is not the first time I've had to mention this option. I would like to ask the following:

1) - Do you check the FAQ page before asking questions?
2) - How would you title a FAQ for this scenario.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[Supernova99]

Thanks both for the recognition

Share what you know - Learn what you don't

 

[troymatt]

Arg.... typed a lot and browser crashed!!!

Thanks, I added stars.

1) I did check, but didn't really know what to search for. I got my initial answer right away... I saw I was sending the right digits. It continued until you recognized the problem. Up until then, I was learning to trouble shoot the system.

2) I would title a new thread "3300 cannot make LD or international calls on PRI" Extra tags: PRI NI2 configuration mitel 3300.

 

[kwbMitel]

Supernova99 - Does E1 have the same type of protocols as T1?

Would the solution above apply to the world at large or only to NA?

**********************************************
What's most important is that you realise ... There is no spoon.