Hi!
I'm looking for an external opinion on a specific problem one of our customer is having right now. I can't say if it's a new problem or if it has always been there because the customer don't call often in the areas where it's not working right now.
Customer has Mitel 3300 MCD v6.0 with embedded PRI card. PRI is NI-2.
Long distance calls go through ARS rule 91+10 route 2 digit mod 1.
Route 2 is the PRI.
Digit mod 1 absorb 1 digit (9).
The customer is in Quebec province and when they call long distance inside Quebec, it works fine.
When they call long distance outside Quebec but inside Canada, it doesn't work. Telco returns one of two messages depending on the area called. It is either "You need to dial the area code before the number dialed." or "You need to dial 1 or 0 in front of long distance calls." Some areas, like Toronto in 647 give the first message and other areas like Mitel Corp in Kanata (613) give the second message.
When they call long distance outside Canada in US, it works fine.
The telco first said that the 3300 didn't send the area code (regarding the first error message) and then said it didn't send the "1" for long distance calls (regarding the second message). Which is ludicrous since it is the same ARS route for all long distance calls!
I asked the customer to do Individual Trunk Access on the PRI and they get the exact same error messages with the exact same numbers. (nothing changed)
The telco sent me his Q.931 trace from CO for a call made in the 647 area with error message #1 :
See error code 81 "Call is not End-to-End ISDN" generated from equipment code 82 (local telco switch). Sounds to me like it's a routing problem at the telco level, isn't it? I'm not a Q.931 guru so I'm trying to interpret this logically as best as I can. The telco says that error code 81 doesn't matter and is not relevant to the problem we're facing... which I think is baffling...
I took my information from there :
SMDR logs and CCS Trace logs show the full number with "1" in front going out on the PRI for all long distance calls without any exception. Are there some parameters for the PRI itself that could be wrong and screw the digits sent that even the CCS Trace would be wrong?? Am I crazy or isn't it a telco problem as I think it is?
Note that the customer switched telco a couple of months ago (was working fine with the other telco for years as far as I know).
I'm looking for an external opinion on a specific problem one of our customer is having right now. I can't say if it's a new problem or if it has always been there because the customer don't call often in the areas where it's not working right now.
Customer has Mitel 3300 MCD v6.0 with embedded PRI card. PRI is NI-2.
Long distance calls go through ARS rule 91+10 route 2 digit mod 1.
Route 2 is the PRI.
Digit mod 1 absorb 1 digit (9).
The customer is in Quebec province and when they call long distance inside Quebec, it works fine.
When they call long distance outside Quebec but inside Canada, it doesn't work. Telco returns one of two messages depending on the area called. It is either "You need to dial the area code before the number dialed." or "You need to dial 1 or 0 in front of long distance calls." Some areas, like Toronto in 647 give the first message and other areas like Mitel Corp in Kanata (613) give the second message.
When they call long distance outside Canada in US, it works fine.
The telco first said that the 3300 didn't send the area code (regarding the first error message) and then said it didn't send the "1" for long distance calls (regarding the second message). Which is ludicrous since it is the same ARS route for all long distance calls!
I asked the customer to do Individual Trunk Access on the PRI and they get the exact same error messages with the exact same numbers. (nothing changed)
The telco sent me his Q.931 trace from CO for a call made in the 647 area with error message #1 :
Code:
==========================================
08 Q.931 Call Control Message
Call Reference Value Orig 25230
M 05 Message Type SETUP
I 04 Bearer Capability Length = 3
80 Coding Standard CCITT
Info Transfer Cap. Speech
90 Transfer Mode Circuit
Transfer Rate 64 kbit/s
A2 Layer 1 Protocol G.711 u-law
I 18 Channel Identification Length = 3
A9 Interface ID Implicitly Defined
Interface Type Primary
Preferred/Exclusive Exclusive
D Channel Indicator Not D Channel
Channel Selection As Indicated
83 Coding Standard CCITT
Coding Type Number
Channel Type B Channel
84 Channel Number 4
I 70 Called Party Number Length = 11
A1 Type of Number National Number
Numbering Plan ISDN/Telephony E.164/E.163
Number 647497XXXX
Raw Hex Data
08 02 62 8E 05 04 03 80 90 A2 18 03 A9 83 84 70
0B A1 36 34 37 34 39 37 39 34 31 36
------------------------------------------------
Event 8 15/11/26 09:31:17 TEI 0
08 Q.931 Call Control Message
Call Reference Value Dest 25230
M 02 Message Type CALL PROCEEDING
I 18 Channel Identification Length = 3
A9 Interface ID Implicitly Defined
Interface Type Primary
Preferred/Exclusive Exclusive
D Channel Indicator Not D Channel
Channel Selection As Indicated
83 Coding Standard CCITT
Coding Type Number
Channel Type B Channel
84 Channel Number 4
Raw Hex Data
08 02 E2 8E 02 18 03 A9 83 84
------------------------------------------------
Event 9 15/11/26 09:31:17 TEI 0
08 Q.931 Call Control Message
Call Reference Value Dest 25230
M 03 Message Type PROGRESS
I 08 Cause Length = 2
82 Coding Standard CCITT
Location Local Public Network
9F Class Normal Event
Value #31, Normal, Unspecified
I 1E Progress Indicator Length = 2
82 Coding Standard CCITT
Location Local Public Network
81 Value Call is not End-to-End ISDN
Raw Hex Data
08 02 E2 8E 03 08 02 82 9F 1E 02 82 81
------------------------------------------------
Event 10 15/11/26 09:31:20 TEI 0
08 Q.931 Call Control Message
Call Reference Value Orig 25229
M 45 Message Type DISCONNECT
I 08 Cause Length = 2
80 Coding Standard CCITT
Location User
90 Class Normal Event
Value #16, Normal Call Clearing
Raw Hex Data
08 02 62 8D 45 08 02 80 90
------------------------------------------------
Event 11 15/11/26 09:31:20 TEI 0
08 Q.931 Call Control Message
Call Reference Value Dest 25229
M 4D Message Type RELEASE
Raw Hex Data
08 02 E2 8D 4D
------------------------------------------------
08 Q.931 Call Control Message
Call Reference Value Orig 25229
M 5A Message Type RELEASE COMPLETE
Raw Hex Data
08 02 62 8D 5A
==========================================I took my information from there :
SMDR logs and CCS Trace logs show the full number with "1" in front going out on the PRI for all long distance calls without any exception. Are there some parameters for the PRI itself that could be wrong and screw the digits sent that even the CCS Trace would be wrong?? Am I crazy or isn't it a telco problem as I think it is?
Note that the customer switched telco a couple of months ago (was working fine with the other telco for years as far as I know).
