atcomsystems.ca/forum Forums TDM Business Telephone Systems Mitel Telephones & Systems Mitel SX200 - how to view debug logs

You must get into the maintenance side and pull a status report of the bay, slot and circuit of the PRI module to get the debug.

First off, your wink timer should be the same for incoming and outgoing. It isn't.

Second, you are inserting a *1 along with the 4 digits coming in. What does *1 do?

The T1 SIP is missing any timer data.

The channels are all COS 10. What do you have enabled in COS 10?

Too many questions and not enough answers.

Rcaman

Hi Panda,

Yes, thank you, I figured that out after reading what I believe was a post from yourself "pandabear1" on the Tek-Tips forums where you included the part about putting the string in the comments. It never even occurred to me to enter it there; to me a comment is a comment, apparently Mitel thinks differently.

Anyway, I was able to get a trace of the call and confirm that the Mitel is rejecting the call. The question then is why?

I played around with different N/M/X values in Form 15, and found the following:

N - "should" work with a value of 4, but doesn't seem to make any difference
M - "should" work with a value of 0, but 6 is the only number than yields a result, though not the correct result
X - "should" be *1, but that doesn't seem to make any difference

The combination of M = 6, with N and X set to any value or no value, results in incoming calls ringing to the front desk (again, this is a hotel). Theoretically with N = 4, M = 0, and X = *1, the Digit Translation Table should then direct the call to extension 6002 (yes, this is a valid internal extension). If I use those settings for N, M, and X, the incoming call fails. If I set M = 6, the call rings through to the front desk.

The trace shows the following on an incoming call:

1 01101100 Information Element: Calling Party Number:
2 IE Length : 12 octets
3 0------- Extension bit : Continued
-000---- Type of number : unknown
----0000 Numbering plan : unknown
3a 1------- Extension bit : Not Continued
-00----- Presentation : Allowed
---000-- Spare
------00 Screening : User provided, not screened
4 ******** Phone number : [XXXXXXXXXX]
1 01110000 Information Element: Called Party Number:
2 IE Length : 5 octets
3 1------- Extension bit : Not Continued
-000---- Type of number : Unknown
----0000 Numbering plan : Unknown
4 ******** Phone number : [8682]

In the above trace sample, I replaced my number with XXXXXXXXXX for security reasons, but it did show the correct number I was calling from. The Called Party Number of 8682 is the correct last four digits of the DID on the T1, so it appears the gateway is passing the correct four digits.

So why are the calls not following the intended path?

Any insights are greatly appreciated.

Thanks.

I only see one setting for a Wink timer? Also, from what I've been told by tech support for the T1 SIP gateway, Wink does not apply to a PRI circuit?

The *1 makes use of the Digit Translation Table to the route the DID to the intended extension, correct?

COS 10 is configured, is there a particular item I should be checking in there?

I should also mention that this PBX was previously configured for a "regular" T1 circuit from the telco, we then switched to POTs lines, now switching it to a PRI from a VoIP provider via a gateway device. Of course the PBX vendor is blaming the gateway device, and vice versa.

Thanks.

try this:
N - 10
M - 6
X - *1

so a number of the hotel is 613-592-2122 so you would expect 10 absorb 6 and be left with 4, the 2122
In form 55 you would have incoming digits are 2122 DiD prefix is 1 and your day mode night modes would be where you want to terminate the call, say a LDN on a console in day mode for example.
remember to turn the debug off in the comments field of form 43

See, this is where it is like banging my head against a wall.....E&M requires some type of start signalling. It DOES NOT matter if it's a special circuit E&M, a T-1 E&M or a PRI E&M. Every E&M MUST have a start type. It may be immediate, or delay or Wink. The MOST common is wink. Your "provider" MUST provide a wink signal somewhere between 200 ms and 300 ms as that is what you have the E&M programmed for in the Mitel. Any other signal will yield goofy results like you are experiencing.

Look....a vendor meet is required here. Have the provider send a tech out with a Tberd or some other span tester that can tell you, without a doubt, if there is wink start and how many milliseconds the duration is. Have the Mitel dealer there to make sure all the forms are set up correctly, including form 3 and COS 10, form 15, form 19, form 45, etc.

You can't just arbitrarily assign a value to form 15 M. It MUST BE the exact number of digits the provider is sending. Just plugging in random values is making one very large and very dumb rabbit hole. How many digits are being sent? Usually, DIDs are sold in blocks. So, if, as an example, your room numbers are floored, meaning every floor has the exact same number of rooms and they all start with 00 and end with 29. So, floor 1 would have rooms 100-129. 30 rooms. Floor 7 would have rooms 700-729. See the pattern. Let's say, as an example, you purchase a block of DIDs from (AC)-XXX-2100-2730. M=4 digits, N=1 digit and x is blank. Believe me, the Mitel will route every call to the proper room, without fail. BUT....this is an example. What is the block that was purchased?

Rcaman

looks like from the trace you are receiving 10 digits, I would guess the start types are correct or you would not be able to make outgoing calls. Trying something is better than doing nothing at all if you cannot receive any calls.
Good luck

Actually, the key is in the wink timers. Outgoing is set to 300. Incoming is set to 200. If it works outgoing but not incoming, that may be a good place to start. The sent digits is the other area that needs addressed. Sending 10 digits is not necessary nor is it normal.

Rcaman

The *1 would be to send the calls to the Form 55 Digit Translation Table so I would hope that it has been programmed correctly. Without an entry there the calls would route just on the 4 digits received. If they match a number in the system then the call should complete. Are your extensions different than the DID numbers?

The problem here is the OP may not know enough about the programming or system to provide us with proper answers. He thinks the Mitel debug logs will lead him in the right direction. Little does he know Mitel's debug logs are next to meaningless as Mitel does not use standard notation and many of the values found in debug have to be translated even when Mitel's own engineers read them. They have some kind of "on the fly" compiler that allows them to make some sense of the logs. This problem is actually an easy problem to resolve IF the person working on the problem is a telephone crafts person.

Rcaman

The issue is now resolved.

COS option 801 Incoming Trunk Call Rotary was disabled. Apparently this is required for PRI trunks. I enabled it and calls are now coming through.

Thanks to everyone for your feedback.