Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - consta

Pages: [1] 2
1
Mitel MiVoice Business/MCD/3300 / Re: Analog Server Unit Configuration fail to update.
« on: November 17, 2016, 03:26:31 PM »
Thanks (mszodiac) for reaching out..

I got it sorted out after two long days of going through the system.
Really thought it was a plug and play case where the system would recognize the new 24port card and assign it, but no no no... The  >>System Configuration >>Unit/Modules would allow me to update the installed card.
1. all extensions assigned to the Circuit 4 1 1 had to be removed , due to the fact that it wouldn't allow to be Busied them out (all 16).
2. run Busy on circuit 4 1 1 .  >>System Configuration >>Unit/Modules >> ASU configuration then allow to change the old 16port to the 24port ons card and  all smilesssssss :D Well apart from creating the extensions again

Minor error gone and got tone every extension...



2
Mitel MiVoice Business/MCD/3300 / Re: Analog Server Unit Configuration fail to update.
« on: November 16, 2016, 11:38:58 AM »
Yes  i did and got:
MC286AA 24 Port ONSP at location 4 1 1 1  Busy Failed                           
Reason - Circuit is unassigned                                                 
MC286AA 24 Port ONSP at location 4 1 1 2  Busy Failed                           
Reason - Circuit is unassigned                                                 
MC286AA 24 Port ONSP at location 4 1 1 3  Busy Failed                           
Reason - Circuit is unassigned                                                 
MC286AA 24 Port ONSP at location 4 1 1 4  Busy Failed                           
Reason - Circuit is unassigned                                                 
MC286AA 24 Port ONSP at location 4 1 1 5  Busy Failed                           
Reason - Circuit is unassigned                                                 
MC286AA 24 Port ONSP at location 4 1 1 6  Busy Failed                           
Reason - Circuit is unassigned                                                 
MC286AA 24 Port ONSP at location 4 1 1 7  Busy Failed                           
Reason - Circuit is unassigned                                                 
MC286AA 24 Port ONSP at location 4 1 1 8  Busy Failed                           
Reason - Circuit is unassigned                                                 
MC286AA 24 Port ONSP at location 4 1 1 9  Busy Failed                           
Reason - Circuit is unassigned                                                 
MC286AA 24 Port ONSP at location 4 1 1 10  Busy Failed                         
Reason - Circuit is unassigned                                                 
MC286AA 24 Port ONSP at location 4 1 1 11  Busy Failed                         
Reason - Circuit is unassigned                                                 
MC286AA 24 Port ONSP at location 4 1 1 12  Busy Failed                         
Reason - Circuit is unassigned                                                 
MC286AA 24 Port ONSP at location 4 1 1 13  Busy Failed                         
Reason - Circuit is unassigned                                                 
MC286AA 24 Port ONSP at location 4 1 1 14  Busy Failed                         
Reason - Circuit is unassigned                                                 
MC286AA 24 Port ONSP at location 4 1 1 15  Busy Failed                         
Reason - Circuit is unassigned                                                 
MC286AA 24 Port ONSP at location 4 1 1 16  Busy Failed                         
Reason - Circuit is unassigned                                                 

3
Mitel MiVoice Business/MCD/3300 / Analog Server Unit Configuration fail to update.
« on: November 16, 2016, 10:57:51 AM »
We're working on a Mitel 3300 icp with an ASU2 attached to it where one of the 16ONS card failed. We got a replacement 24port ons card from Mitel in which we were told that the 16port has been discontinued. The card was installed and got a minor alarm;

cab Shelf Slot     Card Description          total faults
4      1      1   | MC284AX 16 port ONS |  16

we have gone into >>System Configuration >>Unit/Modules.. to try changing/delete the ASU configuration of the programmed card slot 1 where the new 24port ons card is installed which then gives an error (Device is not deassigned).

I have checked the >>Maintenance commands>> STATE 4 1 1
----------------------------------------------------------------------------   
  Location    | Device               | State          |  Owner  | ID  |Status   
----------------------------------------------------------------------------   
 4 1  1   1   | ONS on ASU II/PER    | Unassigned     |         |     |         
 4 1  1   2   | ONS on ASU II/PER    | Unassigned     |         |     |         
 4 1  1   3   | ONS on ASU II/PER    | Unassigned     |         |     |         
 4 1  1   4   | ONS on ASU II/PER    | Unassigned     |         |     |         
 4 1  1   5   | ONS on ASU II/PER    | Unassigned     |         |     |         
 4 1  1   6   | ONS on ASU II/PER    | Unassigned     |         |     |         
 4 1  1   7   | ONS on ASU II/PER    | Unassigned     |         |     |         
 4 1  1   8   | ONS on ASU II/PER    | Unassigned     |         |     |         
 4 1  1   9   | ONS on ASU II/PER    | Unassigned     |         |     |         
 4 1  1  10   | ONS on ASU II/PER    | Unassigned     |         |     |         
 4 1  1  11   | ONS on ASU II/PER    | Unassigned     |         |     |         
 4 1  1  12   | ONS on ASU II/PER    | Unassigned     |         |     |         
 4 1  1  13   | ONS on ASU II/PER    | Unassigned     |         |     |         
 4 1  1  14   | ONS on ASU II/PER    | Unassigned     |         |     |         
 4 1  1  15   | ONS on ASU II/PER    | Unassigned     |         |     |         
 4 1  1  16   | ONS on ASU II/PER    | Unassigned     |         |     |         

Really thought this was a PNP card since there was a card there before and that it would utilize the first 16port of the 24port ons card.

Any ideas are welcomed!!!
thanks mcuh..

4
Mitel MiVoice Business/MCD/3300 / Re: Mitel 3300 cx keeps rebooting
« on: June 18, 2016, 12:32:27 AM »
Sorry team for the late repost. the system is up and running,  indeed it was a faulty E1 card. soon as I replaced it system is fine.
Thanks once again for this great team work.!!!

5
Mitel MiVoice Business/MCD/3300 / Mitel 3300 cx keeps rebooting
« on: June 15, 2016, 10:00:18 PM »
Good day team i'm having an issue with this 3300 cx which keeps booting, it has one E1/T1 and a 4 CIM port card on there.
 here's a copy of the captured log..



Appying the Default Dsp Business Option
copying file /sysro/DspConfig/DSP_Default/DSPType3300.txt -> /sysro/DspConfig//DSPType3300.txt
copying file /sysro/DspConfig/DSP_Default/DSPTypeCX.txt -> /sysro/DspConfig//DSPTypeCX.txt
copying file /sysro/DspConfig/DSP_Default/DSPTypeEmerald.txt -> /sysro/DspConfig//DSPTypeEmerald.txt
copying file /sysro/DspConfig/DSP_Default/DSPTypeMXe.txt -> /sysro/DspConfig//DSPTypeMXe.txt
Dsp Config Filename: "/sysro/DspConfig/dspConfig3XXX.txt"
Dsp Card Type Filename: "/sysro/DspConfig/DspCardTypeCx.txt"
Dsp Type Filename: "/sysro/DspConfig/DSPTypeCX.txt"
Dsp Static Loading Filename: "/sysro/DspConfig/Loading3XXX.txt"
StartUp - Booting DSP card in slot 1 (1-based)

machine check
Exception next instruction address: 0x0019906c
Machine Status Register: 0x0004b030
Condition Register: 0x20000848
Task: 0x3a9d000 "tAppStartup"

ignore dup exception

machine check
Exception next instruction address: 0x0019906c
Machine Status Register: 0x0004b030
Condition Register: 0x20000848

program
Exception current instruction address: 0x00000000
Machine Status Register: 0x0008b032
Condition Register: 0x40000048
Task: 0x3a9a900 "SysPreMort0"

ignore dup exception

program
Exception current instruction address: 0x00000000
Machine Status Register: 0x0008b032
Condition Register: 0x40000048
Task SysPreMort0 being deleted while ACTIVE
Raised Critical Alarm on Stale Tasks
RaiseAlarm alarm severity critical, forcing machine shutdown
WARNING-System shutdown requested by task: tTMonitor
Critical Alarm being raised upon detecting the following task suspended: tAppStartup taskId 0x3a9d000 crash time WED JUN 15 16:36:43 2016

6
Mitel MiVoice Business/MCD/3300 / Database Question!!
« on: January 24, 2014, 10:46:12 AM »
Question Guys,
can the mitel 3300  database be exported and be imported onto a mitel 5000 system.  New to the 5000,really dont want to reconfigure, please let me know if this is possible.

7
Mitel MiVoice Business/MCD/3300 / Re: Multiline Appearance Group Error
« on: December 05, 2013, 12:24:00 PM »
 :D
Thanks guys, it did work!!!

8
Mitel MiVoice Business/MCD/3300 / Re: Multiline Appearance Group Error
« on: November 28, 2013, 08:43:55 PM »
Do i use the same backup to do the restore or from a previous backup.

9
Mitel MiVoice Business/MCD/3300 / Re: Multiline Appearance Group Error
« on: November 27, 2013, 03:53:51 PM »
DBMS info: Lab Default DB is off                                               
DBMS CHECK has commenced.                                                       
DBMS info: DBMS_INITIALIZED is on                                               
DBMS info: Journal is on                                                       
DBMS info: Debug is off                                                         
DBMS info: Cab: 24 Dim: 17 Traffic: 20                                         
DBMS info: Check is off                                                         
DBMS info: DBMS CHECK has not been performed.                                   
Machine Variant: IP                                                             
Installation ID: Local_71                                                       
Time           : 2013-NOV-27 16:50:40.00    WED                                 
Plane          : A - active                                                     
File Redundancy: enabled                                                       
Mate Link      : manbusy                                                       
                                                                               
View:   1  cor               Tuples (Max):  32767   (Current):     75           
View:   2  cos               Tuples (Max):    110   (Current):    110           
View:   3  fac               Tuples (Max):  32767   (Current):    118           
View:   4  pickup_group      Tuples (Max):  15000   (Current):      0           
View:   5  pickup_group_for  Tuples (Max):    200   (Current):      0           
View:  11  station_assign    Tuples (Max):    764   (Current):      8           
View:  12  speed_call        Tuples (Max):   1000   (Current):      1           
View:  13  trunk_ans         Tuples (Max):    500   (Current):    150           
View:  14  interconnect_res  Tuples (Max):     75   (Current):     75           
View:  15  system_config     Tuples (Max):   3072   (Current):    119           
View:  17  misc_equip        Tuples (Max):      1   (Current):      1           
View:  18  trunk_assign      Tuples (Max):    629   (Current):     13           
View:  20  station_hunt_cop  Tuples (Max):    176   (Current):      0           
View:  21  station_hunt_dat  Tuples (Max):  11264   (Current):      0           
View:  22  station_hunt_inf  Tuples (Max):    176   (Current):      2           
View:  23  corp_dir          Tuples (Max):  19999   (Current):     25           
View:  24  trunk_hunt_copy   Tuples (Max):    112   (Current):      0           
View:  25  trunk_hunt_data   Tuples (Max):  19600   (Current):      8           
View:  26  trunk_hunt_info   Tuples (Max):    112   (Current):      4           
View:  27  route_assign      Tuples (Max):    200   (Current):    200           
View:  28  ext_data          Tuples (Max):   1546   (Current):     27           
View:  29  change_attribute  Tuples (Max):  32767   (Current):     27           
View:  40  ss4_line_info     Tuples (Max):    756   (Current):     24           
View:  44  form_access       Tuples (Max):  32767   (Current):    128           
View:  45  attendant_consol  Tuples (Max):     24   (Current):      0           
View:  46  attendant_line_d  Tuples (Max):    144   (Current):      0           
View:  47  attendant_line_i  Tuples (Max):     24   (Current):      0           
View:  48  user_auth         Tuples (Max):     64   (Current):      4           
View:  49  ac13_trk_hw       Tuples (Max):     32   (Current):      0           
View:  50  scdc_trk_hw       Tuples (Max):     32   (Current):      0           
View:  51  call_progress_co  Tuples (Max):    100   (Current):      0           
View:  52  call_progress_da  Tuples (Max):    600   (Current):      0           
View:  53  call_progress_in  Tuples (Max):    100   (Current):      1           
View:  54  call_rerouting_1  Tuples (Max):   1000   (Current):    336           
View:  55  call_rerouting_2  Tuples (Max):    100   (Current):     32           
View:  56  call_rerouting    Tuples (Max):  65535   (Current):     29           
View:  58  intercept         Tuples (Max):     45   (Current):     45           
View:  62  smdr_option_assi  Tuples (Max):  32767   (Current):      1           
View:  63  system_option_as  Tuples (Max):  32767   (Current):      1           
View:  65  default_acc_code  Tuples (Max):    600   (Current):    225           
View:  66  day_time_zone_da  Tuples (Max):      4   (Current):      4           
View:  67  day_time_zone_ti  Tuples (Max):      4   (Current):      4           
View:  68  system_acc_code   Tuples (Max):    100   (Current):     24           
View:  69  modem_elm_ass     Tuples (Max):      2   (Current):      2           
View:  70  assoc_dn          Tuples (Max):   1546   (Current):      0           
View:  71  route_plan_data   Tuples (Max):     96   (Current):     96           
View:  72  route_plan_info   Tuples (Max):     32   (Current):     32           
View:  73  ss4_status_msg_d  Tuples (Max):     60   (Current):      0           
View:  74  ss4_status_msg_i  Tuples (Max):      3   (Current):      0           
View:  86  ss4_group_info    Tuples (Max):   1875   (Current):     27           
Next key error ***                                                             
Return Code is Failure                                                         
Key is                                                                         
56003433363320202000000000000000                                               
00000000000000000000000000000000                                               
00000000000000000000000000000000                                               
 00                                                                             
Offset is 1                                                                     
Tuple Number (one based) is 0                                                   
View:  95  configuration_se  Tuples (Max):      1   (Current):      1           
View:  96  configuration_di  Tuples (Max):      1   (Current):      1           
View:  97  digital_co_trk_h  Tuples (Max):     32   (Current):      0           
View:  98  digital_did_trk_  Tuples (Max):     32   (Current):      0           
View:  99  digital_em_trk_h  Tuples (Max):     32   (Current):      0           
View: 100  hotel_stn_data    Tuples (Max):   1520   (Current):      0           
View: 101  hotel_ss4_data    Tuples (Max):      0   (Current):      0           
View: 102  max_dialled_digi  Tuples (Max):    110   (Current):    110           
View: 103  traffic_options   Tuples (Max):  32767   (Current):      1           
View: 104  msg_link_assignm  Tuples (Max):      0   (Current):      0           
View: 105  system_port       Tuples (Max):    100   (Current):      3           
View: 106  logical_port      Tuples (Max):  32767   (Current):     17           
View: 107  call_forwarding   Tuples (Max):  14075   (Current):      1           
View: 120  remote_directory  Tuples (Max): 435455   (Current):      0           
View: 121  rem_agt_subgrp_i  Tuples (Max):     32   (Current):      0           
View: 122  rem_agt_subgrp_d  Tuples (Max):     32   (Current):      0           
View: 123  rem_busy_lamp_in  Tuples (Max):    439   (Current):     24           
View: 124  rem_busy_lamp_da  Tuples (Max):  28096   (Current):      0           
View: 125  ss4_blg           Tuples (Max):  71820   (Current):    310           
View: 126  is_info           Tuples (Max):      1   (Current):      1           
View: 127  is_data           Tuples (Max):     64   (Current):     64           
View: 128  page_group_info   Tuples (Max):     16   (Current):      0           
View: 129  page_group_data   Tuples (Max):   4000   (Current):      0           
View: 130  page_group_copy   Tuples (Max):     16   (Current):      0           
View: 131  snmp_config_info  Tuples (Max):      1   (Current):      1           
View: 132  snmp_config_data  Tuples (Max):     30   (Current):     30           
View: 133  snmp_trap_commun  Tuples (Max):      1   (Current):      1           
View: 134  snmp_trap_commun  Tuples (Max):     10   (Current):     10           
View: 141  vid_mac_address   Tuples (Max):   1544   (Current):     24           
View: 142  vid_customer_eme  Tuples (Max):      1   (Current):      1           
View: 143  vid_customer_eme  Tuples (Max):   1544   (Current):     27           
View: 144  vid_psc_dsp       Tuples (Max):     10   (Current):      0           
View: 145  vid_linked_suite  Tuples (Max):    500   (Current):      0           
View: 146  vid_linked_suite  Tuples (Max):  16000   (Current):      0           
View: 168  vid_make_busy     Tuples (Max):   2639   (Current):     27           
View: 169  vid_auto_answer   Tuples (Max):   1875   (Current):     24           
View: 170  vid_fwding_end_c  Tuples (Max):   2639   (Current):     27           
View: 171  vid_active_statu  Tuples (Max):   1875   (Current):     24           
View: 172  vid_user_data     Tuples (Max):   1875   (Current):     24           
View: 173  vid_mls_noise_se  Tuples (Max):   2639   (Current):     26           
View: 174  vid_reminder      Tuples (Max):      0   (Current):      0           
View: 175  vid_message_wait  Tuples (Max):   2639   (Current):     27           
View: 176  vid_hot_desk_pin  Tuples (Max):   2639   (Current):      0           
View: 177  vid_call_park_in  Tuples (Max):      1   (Current):      1           
View: 178  vid_call_park_da  Tuples (Max):  14062   (Current):      0           
View: 179  vid_ring_group_i  Tuples (Max):    176   (Current):      3           
View: 180  vid_ring_group_d  Tuples (Max):   5632   (Current):     20           
View: 181  vid_guest_room    Tuples (Max):  20021   (Current):      0           
View: 182  vid_guest_room_d  Tuples (Max):  20021   (Current):      0           
View: 183  vid_nt_info       Tuples (Max):    999   (Current):    999           
View: 185  vid_pbx_zone      Tuples (Max):    999   (Current):      0           
View: 187  vid_phone_lock    Tuples (Max):   1520   (Current):     27           
View: 188  vid_user_login    Tuples (Max):    755   (Current):      0           
View: 189  vid_personal_rin  Tuples (Max):    350   (Current):      0           
View: 190  vid_personal_rin  Tuples (Max):   2800   (Current):      0           
View: 192  vid_acdx_group_i  Tuples (Max):    999   (Current):      0           
View: 193  vid_acdx_group_d  Tuples (Max): 149850   (Current):      0           
View: 198  vid_call_coverag  Tuples (Max):    255   (Current):    255           
View: 199  vid_location_bas  Tuples (Max):    200   (Current):      0           
Internal level audit starting.                                                 
DBMS info: DBMS CHECK completed 2013-NOV-27 16:53:19.00 .                       
Internal level audit finished successfully.                                     
2 view error(s), 0 table error(s) detected.                                     

10
Mitel MiVoice Business/MCD/3300 / Multiline Appearance Group Error
« on: November 27, 2013, 03:34:44 PM »
For some reason I went to check out the Multiline Appearance Group form and received (Generic Forms Error: An unidentified error has occurred.).  After clicking the option OK the same same error pops up.
If i were to change any of the Group Directory Number another Error comes up stating ( A system error has occured. Please note the following information and contact Technical Support. The parameter is incorrect.

Here's a log of the error:

Log Type   :   Software
Log Number :  490
Severity  :      Warning
Date  :           2013/Nov/27
Time   :          16:20:30
Source :         GenericForms
Description:   getCachedDetailData()->c73n5UjLvb-71Rf3PB_3DA, cm error 30, req 7.86
Module:          Main
File Name and Line Number:   GF_DataActions.cpp;4637
 


         
Log Type :        Software
Log Number:    491
Severity :         Error
Date  :             2013/Nov/27
Time :              16:24:38
Source :           DBA Adaptor
Description:     Error getting next tuple in view->86: Can not read view tuple.
Module:            Main
File Name and Line Number:   DBA_Adaptor.cpp;3426


ANY IDEAS?

11
Mitel MiVoice Business/MCD/3300 / Re: Busy lines/locked lines
« on: November 18, 2013, 08:21:10 AM »
Hey guys still no luck with this. Question my Boss is crazy to go install a 5000 controller on there to see where this would fix the issue. What is your take on this?

note: 3300 has 3 analog lines,1 smart cell terminal which works fine when it comes to disconnecting.
          3 extensions lines coming from nortel  PXB into the 3300 system which always busy/locks up  one or all of the  3 analog lines.

Any one cares to have a look through the configs
Other ideas are welcome.

12
Mitel MiVoice Business/MCD/3300 / Re: Busy lines/locked lines
« on: October 21, 2013, 09:52:38 AM »
Hey Tomj, the system dose  not have voice mail configured on the system.

I will try out Ralph trick and see whats happens.

13
Mitel MiVoice Business/MCD/3300 / Re: Busy lines/locked lines
« on: October 20, 2013, 10:50:39 PM »
Hey Guys still no luck!
 I'm fighting this battle of "Busy trunks" any other ideas  or does anyone wants to over see whats going on the controller to get a better understanding of my battle?
 

14
Mitel MiVoice Business/MCD/3300 / Re: Busy lines/locked lines
« on: October 16, 2013, 01:37:09 PM »
Thanks much for the support.

Tomj, i have  monitor these analogue lines, and receives  a tone when the far end clears down. also Ralph i have set Public Network to Public Network Connections allowed" to 'No', but stilling have the same issue.

My question is do i configure a separate COS  and  CO Trunk Circuit Descriptors for the Nortel extensions  going into the controller or use the same setting already configured for the analog lines.





15
Mitel MiVoice Business/MCD/3300 / Busy lines/locked lines
« on: October 10, 2013, 03:59:32 PM »
Good day team.

I have been working with this Mitel 3300 system and have been having problems with busy trunks, there are three analog hunt grouped lines going to the controller from the service provider and three other lines which they are extension from a Nortel pbx.
 we have found out , when the three extensions are plugged to the controller and calls are made from the Nortel pbx to any of the mitel extensions or the other way round once the call hangs up, it busy out which ever trunk is active, analog lines / ext lines from  Nortel pbx.
Also we went on removing those extension lines for two day from the controller and did not have not one busy trunk but once the extension lines are place onto the controller this is where the complications begins.
There's no one on  busy lines 2 1 1 7 and 2 1 2 9.

  Location    | Device               | State         |  Owner  | ID   |Status   
----------------------------------------------------------------------------   
 2 1  1   1   | ONS on Embedded ASU  |Idle           |         |      |         
 2 1  1   2   | ONS on Embedded ASU  |Unassigned     |         |      |         
 2 1  1   3   | ONS on Embedded ASU  |Idle           |         |      |         
 2 1  1   4   | ONS on Embedded ASU  |Idle           |         |      |         
 2 1  1   5   | LS on Embedded ASU   |Idle           |         |      |         
 2 1  1   6   | LS on Embedded ASU   |Idle           |         |      |         
 2 1  1   7   | LS on Embedded ASU   |Busy           |Call Proc|1 032B|Wait     
 2 1  1   8   | LS on Embedded ASU   |Idle           |         |      |         
 2 1  1   9   | LS on Embedded ASU   |Idle           |         |      |         
 2 1  1  10   | LS on Embedded ASU   |Idle           |         |      |         
----------------------------------------------------------------------------
 Location    | Device               | State         |  Owner  | ID   |Status   
----------------------------------------------------------------------------   
 2 1  2   1   | ONS on Embedded ASU  |Unassigned     |         |      |         
 2 1  2   2   | ONS on Embedded ASU  |Unassigned     |         |      |         
 2 1  2   3   | ONS on Embedded ASU  |Unassigned     |         |      |         
 2 1  2   4   | ONS on Embedded ASU  |Unassigned     |         |      |         
 2 1  2   5   | LS on Embedded ASU   |Idle           |         |      |         
 2 1  2   6   | LS on Embedded ASU   |Idle           |         |      |         
 2 1  2   7   | LS on Embedded ASU   |Idle           |         |      |         
 2 1  2   8   | LS on Embedded ASU   |Idle           |         |      |         
 2 1  2   9   | LS on Embedded ASU   |Busy           |Call Proc|3 0326|Wait     
 2 1  2  10   | LS on Embedded ASU   |Idle           |         |      |         
----------------------------------------------------------------------------   
we then have go to the command line, amazingly which ever circuit  we busy and rts command automatically the trunk on the other circuit which was busy would released and go back to normal state. Say we busy and rts 2 1 2 9 , 2 1 1 7 will automatically release and go back to normal state. Help needed ASAP.

Any ideas of my dilemma .
Thanks much.
http://www.mitelforums.com/forum/Smileys/default/smiley.gif

Pages: [1] 2