T Codes being displayed on Handsets 5312 IP Phones

[dyls]

Hi

Hoping you can help. We have a new issue where when a employee is dialing out a T code comes up on there phone, its a random different code every time something like T551, T1938 or T1156. It comes up after dialling the number then the handset goes dead and you have to redial. Its totally intermittent but is happening fairly regularly to any user on an ACD extension. I am rattling my brain and cant identify whats causing this , have any of you MITEL experts seen this before? We have a MITEL 3300 System, 1 box is hosted using ISDN lines for inbound calls and the other is a VMCD using SIP trunks. All our outgoing calls are being routed through SIP at the moment. Thats about as much as I can tell you from my knowledge of the system. Many thanks in advance for any help. Cheers, Dylan. 

[ralph]

My 1st thought is that the T code is a trunk. 
If you don't have a label applied to a trunk in the trunk attributes form then it will show T<trunk number> when calling out.

The next thing I would do to verify that thought is to check the smdr logs for outbound call on that trunk number.   So I would do a match on '551',  '1938', or '1156' to see if you get a hit.
If yes then you'll need to verify your ARS routing to see how you're getting to those trunks.

Ralph

[dyls]

Thanks for the reply, really appreciate the response. Apologies but my technical knowledge on the MITEL is not that great. The numbers are seemingly random and our Trunk numbers would be for example T101 to T120 we dont have that many. Where can I check the SIP info on the MCD? Is there any Maintenance commands I can run to look at the information I need to check? Thanks again.

[ralph]

Easiest thing to try next is when the next time it happens, go to maintenance commands and enter this:
"logs re smdr new 500 ma <last 7 digits the user dialed>"
That may show you where the call went out.
Copy and paste that info here and we'll see if we can explain what we see.

This assumes that SMDR is turned on in both the COS of the user and the SMDR form.

Ralph

[dyls]

Hi

I appreciate your continued help. Thank you so much. Apologies for the delayed reply.

I typed in as you said:

LOGSYS READ smdr NEWEST 500 MATCH <2291854>

and got back...

LOGSYS warning: No more entries for SMDR log.                                   
LOGSYS info: READ completed for SMDR log with 0 entries.

I know you mentioned to check a few things namely SMDR is turned on for both COS of the user and SMDR form, where can I check this?   

[dyls]

Just to add some more info I ran the same command on our Hosted Box and got back this:

LOGSYS READ smdr NEWEST 500 MATCH <2291854>

and got back:

LOGSYS info: READ completed for SMDR log with 500 entries.   

The previous result was from our virtual box which is where the SIP is configured. We are dialling out using 9 which all calls go out over the SIP.

[ralph]

The forms you need to check are:
SMDR Options
Class of Service  (Enable SMDR for both the trunks and the devices)

Ralph

[dyls]

Thanks for you continued help.

We will enable SMDR Options on the virtual box to the same as the hosted box as they are currently all set to NO. Then we should be able to run the command again.

[dyls]

Hi, OK so we had the following code displayed on a users handset....

Date:29/01/2015   
Code: T1916      
Number Dialed:020 77272326   
Time Dialled: 14:12

I went onto the maintenance commands and did: LOGSYS READ SMDR ALL MATCH 7272326

The results were:

 01/29 14:33:38  0000:00:56 X9999   0011 902077272326                           
                           002   1192                                    U001468
1 B                                                                             
 01/29 14:33:38  0000:00:59 X9999        02077272326               A           
                           002   1192                                    U001468
1 C                                                                             
 01/29 14:12:50             X9999        02077272326                           
                           002   1192                                    S001304
7 C                                                                             
 01/29 14:12:50  0000:00:04 X9999   **** 902077272326              B           
                           002   1192                                    S001304
7 B                                                                             
 01/29 14:11:41             X9999        02077272326                           
                           002   1178                                    Q001724
9 C                                                                             
 01/29 14:11:40  0000:00:05 X9999   **** 902077272326              B           
                           002   1178                                    Q001724
9 B                                                                             
 01/29 14:11:08             X9999        02077272326                           
                           002   1192                                    U001712
3 C                                                                             
 01/29 14:11:07  0000:00:04 X9999   **** 902077272326              B           
                           002   1192                                    U001712
3 B                                                                             
 01/29 14:08:33             X9999        02077272326                           
                           002   1199                                    E001025
9 C                                                                             
 01/29 14:08:33  0000:00:06 X9999   **** 902077272326              B           
                           002   1199                                    E001025
9 B                                                                             
 01/29 14:08:17             X9999        02077272326                           
                           002   1192                                    Y001144
9 C                                                                             
 01/29 14:08:17  0000:00:04 X9999   **** 902077272326              B           
                           002   1192                                    Y001144
9 B                                                                             
 01/29 13:10:41  0000:00:14 X9999   0017 902077272326                           
                           002   1192                                    Q001778
5 B                                                                             
 01/29 13:10:41  0000:00:16 X9999        02077272326               A           
                           002   1192                                    Q001778
5 C                                                                             
LOGSYS warning: No more entries for SMDR log.                                   
LOGSYS info: READ completed for SMDR log with 482 entries.           

[ralph]

 

  01/29 14:33:38  0000:00:56 X9999   0011 902077272326                           
                         002   1192                                    U001468
1 B                                                                             
 01/29 14:33:38  0000:00:59 X9999        02077272326               A           
                           002   1192                                    U001468

What this appears to show is the call coming into this pbx from another PBX (X9999) and then dialing back out.
What I'm not seeing is the destination trunk so I am a bit confused here.   The "A" at the end tells me there was answer supervision so this call appears to have been answered where the ones with the "B" I suspect the user got a busy tone back.

I expected to see at the end of the call record something like "T1111" or "X1111" that would show the destination trunk.  I'm not seeing that.
Hopefully other eyes on this will have a better explanation.

Ralph

[dyls]

Thanks for all your help ralph that's some good info none the less and helps me understand it a bit better. Cheers