Author Topic: Mitel 3300 outbound cli issue  (Read 7093 times)

jamesm

  • Guest
Mitel 3300 outbound cli issue
« on: September 07, 2010, 09:13:59 AM »
Hi there, i am new to the forum and wondering if you can help.

we currently look after a mitel 3300 system that has been working fine for a number of years but after a recent power cut the system no longer outputs users DDI numbers instead it only shows the main circuit number of the ISDN 30.

I have double checked the programming under DID Ranges for CPN Substitution and have done an additional reboot just incase something has stuck during bootup but still not luck.

Is there something else i should look at? Am i doing something wrong? or are there any known issues that can cause this?

Thank you for your time and if any additional info is required please let me know!


« Last Edit: September 07, 2010, 09:22:10 AM by jamesm »


Online ralph

  • Mitel Forums Admin
  • Hero Member
  • *****
  • Posts: 5767
  • Country: us
  • Karma: +469/-0
  • Published Author: http://amzn.to/2dcYSY5
    • View Profile
Re: Mitel 3300 outbound cli issue
« Reply #1 on: September 07, 2010, 11:14:24 AM »
Very Bizzar that it would start after a power outage.
Here's some questions:
What version of 3300?
Embedded PRI or NSU?

Here's a couple of things to try:
1- In the "associated Directory" form, see if you can change 1 number.
2- turn on call trace, make a call, copy the details and post it here so we can look at it.
3- Call your carrier and ask for a switchman to test with you to see what you're actually showing for CLID.  It might not be your issue.

Ralph
« Last Edit: April 22, 2014, 04:04:46 PM by ralph »

jamesm

  • Guest
Re: Mitel 3300 outbound cli issue
« Reply #2 on: September 09, 2010, 10:01:49 AM »
Hi thanks for the reply.

The system is a mitel 3300 icp using IP phones.
i think its an embedded PRI

1) In "associated Directory" there are no entrys
2) please see call trace at the end of the post, "Number Called" represents the mobile phone the client has called for testing purposes
3) As far as the line suppliers are concerned there is nothing wrong with the lines - but they always say that! -

Hope this Helps

The extention making the test calls is 2997. We made two test calls, it should output the DDI ending in 2997 but does not instead it outputs 2950

CCS Message Trace Table                                                        
-----------------------                                                        
                                                                                
14:49:25 RI101 DPN 2A ISRM_I  ;10;*3#*233*`IBc#*58*CI*W6a#*50*ISDN Number#      
14:49:25 RI101 DPN 7  SSRM_C  522999                                            
14:49:25 RO101 DPN 23 NAM     *1#*50*2999#*166*6#*100*M.Gavin*1#                
14:49:38 RO101 DPN 24 CCM     *1#*50*2997#*166*6#*100*M.Petkov*1#              
14:50:06 RO101 DPN 2  CRM/CIM ;30;                                              
14:50:06 RI101 DPN 2  CRM/CIM ;30;                                              
14:50:07 RO101 DPN 1E ISRM_I  ;10;*1#*50*2997#*100*M.Petkov*1#                  
14:50:07 RO101 DPN 2D SSRM_I  *58*CW*Wwdg@@@@@A^]z@#*58*C6*001#Number Called      
14:50:07 RI101 DPN 7  NIM     *51*3#                                            
14:50:12 RI101 DPN F  NIM     *4*4#*240*aX`#                                    
14:50:12 RI101 DPN 13 NAM     *4*4#*166*1 2 3 4#                                
14:50:12 RI101 DPN A  CCM     *58*CP*G#                                        
14:50:16 RI101 DPN A  CCM     *58*CP*G#                                        
14:50:25 RO101 DPN 2  CRM/CIM ;30;                                              
14:50:25 RI101 DPN 2  CRM/CIM ;30;                                              
14:50:26 RO101 DPN 1E ISRM_I  ;10;*1#*50*2997#*100*M.Petkov*1#                  
14:50:26 RO101 DPN 2D SSRM_I  *58*CW*Wwdg@@@@@A^_WP#*58*C6*001#Number Called      
14:50:26 RI101 DPN 7  NIM     *51*3#                                            
14:50:32 RO102 DPN 20 ISRM_I  ;10;*1#*50*2958#*100*C.McDonald*1#                
14:50:32 RO102 DPN 2D SSRM_C  *58*CW*Wwdg@@@@@A^_tp#*58*C6*001#    
14:50:33 RI102 DPN 7  NIM     *51*3#                                            
14:50:36 RO101 DPN 1  SSRM_C                                                    
14:50:37 RI102 DPN F  NIM     *4*4#*240*aX`#                                    
14:50:37 RI102 DPN 13 NAM     *4*4#*166*1 2 3 4#                                
14:50:37 RI102 DPN A  CCM     *58*CP*G#                                        
14:50:37 RI101 DPN F  NIM     *4*4#*240*aX`#                                    
14:50:37 RI101 DPN 13 NAM     *4*4#*166*1 2 3 4#                                
14:50:37 RI101 DPN A  CCM     *58*CP*G#                                        
14:50:38 RI101 DPN A  CCM     *58*CP*G#                                        
14:50:40 RO101 DPN 2  CRM/CIM ;30;                                              
14:50:40 RI101 DPN 2  CRM/CIM ;30;                                              
14:50:41 RO101 DPN 1E ISRM_I  ;10;*1#*50*2997#*100*M.Petkov*1#                  
14:50:41 RO101 DPN 2D SSRM_I  *58*CW*Wwdg@@@@@A^``P#*58*C6*001#Number Called      
14:50:41 RI101 DPN 7  NIM     *51*3#                                            
14:50:43 RI102 DPN A  CCM     *58*CP*G#                                        
14:50:50 RI101 DPN F  NIM     *4*4#*240*aX`#                                    
14:50:50 RI101 DPN 13 NAM     *4*4#*166*1 2 3 4#                                
14:50:50 RI101 DPN A  CCM     *58*CP*G#                                        
14:50:51 RI101 DPN A  CCM     *58*CP*G#                                        
14:50:59 RI102 DPN F  CRM/CIM ;30;*166*1 2 3 4#                                
14:51:01 RO101 DPN 2  CRM/CIM ;30;                                              
14:51:01 RI101 DPN 2  CRM/CIM ;30;                                              
14:51:01 RO101 DPN 1E ISRM_I  ;10;*1#*50*2997#*100*M.Petkov*1#                  
14:51:01 RO101 DPN 2D SSRM_I  *58*CW*Wwdg@@@@@A^bHP#*58*C6*001#Number Called      
14:51:01 RI101 DPN 7  NIM     *51*3#                                            
14:51:07 RI101 DPN F  NIM     *4*4#*240*aX`#                                    
14:51:07 RI101 DPN 13 NAM     *4*4#*166*1 2 3 4#                                
14:51:07 RI101 DPN A  CCM     *58*CP*G#                                        
14:51:13 RI101 DPN A  CCM     *58*CP*G#                                        
14:51:25 RO101 DPN 2  CRM/CIM ;30;                                              
14:51:25 RI101 DPN 2  CRM/CIM ;30;
« Last Edit: September 09, 2010, 10:12:58 AM by jamesm »

Online ralph

  • Mitel Forums Admin
  • Hero Member
  • *****
  • Posts: 5767
  • Country: us
  • Karma: +469/-0
  • Published Author: http://amzn.to/2dcYSY5
    • View Profile
Re: Mitel 3300 outbound cli issue
« Reply #3 on: September 09, 2010, 10:24:24 AM »
Well I don't see 2950 in the traces.  This suggest to me that it's not happening in your system.
Open a ticket with your carrier.  Tell then you're getting the wrong CLDI and ask them to assign a switch tech to see what you are sending them.

Ralph

jamesm

  • Guest
Re: Mitel 3300 outbound cli issue
« Reply #4 on: September 09, 2010, 10:37:14 AM »
Thanks for the quick reply. I'll give that a shot and thanks for all your help!

Offline bobcheese

  • Sr. Member
  • ****
  • Posts: 435
  • Karma: +3/-0
    • View Profile
Re: Mitel 3300 outbound cli issue
« Reply #5 on: September 09, 2010, 02:20:22 PM »
I think we have jumped a couple of steps here. I have a couple of quetsions:

1, How is your PRI connected to the system? Module in the 3300 chasis or external NSU?

2, Before the system lost power when was the last time it was reset?

You see, it is quite possible that a change has been made to the CPN setup and has been waiting for a reboot to take effect.


 

Sitemap 1 2 3 4 5 6 7 8 9 10