Mitel Forums - The Unofficial Source
Mitel Forums => Mitel SX200, SX2000, and older SX platforms => Topic started by: Adam Akers on February 07, 2022, 04:48:49 PM
-
I am working on a Mitel SX2000 and I am trying to setup it up so that dialing 911 will automatically go out so that 9 911 doesn't have to get dialed. When I go into ARS and try to create a route for leading digit 9 with 11 as digits following and number of digits to follow it returns "the digits already exist" when I look at all the routes with 9 being the leading digit there are no routes that actually have 11 following. If I do a dgt trace 911 it shows up as a hunt group (38) but I can not find it in the hunt group form. Also in Call Rerouting Assignment I show 911 is a number like all my other extensions, but it is not a extension number. Any help would be appreciated.
Adam Akers
-
might be location based number. why block 9911 if 9 is your outbound dial digit? I always make sure any emergency dial is sent out-
-
John,
Thanks for the reply. 9911 is not being blocked. If I dial 9911 I get outside to the 911 call center. What I am trying to do is create a route so that if someone is to dial 911 it will route out as well.
Adam
-
you could easily create a speedcall 911 that dials 9911
-
If I create a system speed call with 911 as the speedcall number and 9911 as the actual number it returns "Unable to translate the key data"
-
what doesd loc num 911 return in maintenance commands?
-
The Number refers to a hunt group.
and when i do dgt trace 911 is returns 911 : Hunt group (38).
yet when I go to hunt groups and look for a hunt group with the pilot number of 911 it shows up as a blank hunt group, the same as if I search for a hunt group with a pilot number of any random number that I know is not a hunt group
-
The Number refers to a hunt group.
and when i do dgt trace 911 is returns 911 : Hunt group (38).
yet when I go to hunt groups and look for a hunt group with the pilot number of 911 it shows up as a blank hunt group, the same as if I search for a hunt group with a pilot number of any random number that I know is not a hunt group
And what happens if you call said hunt group?
-
I get a fast busy.
-
I get a fast busy.
What displays on the phone? Invalid, or Out Of Service? Invalid would tell you the system doesn't know how to route the call (the DN doesn't exist), while Out Of Service would tell you that the destination exists, but is out of service.
-
Is this system networked to other Mitel systems, or was it at one time?
-
I would look at members of the hunt group, if empty, check rerouting. also would like to know if networked before saying delete and re-add as a speedcall
-
When I dial 911 it shows "out of service" on the phones. The system has never been networked to another system.
-
So that tells me that the dialed digit string exists, but the destination is out of service. Check the Hunt Groups form again, if it's still not there, check for database corruption as that's a possiblity.
-
... check for database corruption as that's a possiblity.
This is kind of what I was leaning towards... A decent idea would be to find a maintenance window (depending on size, could be 1-2 hours) and perform a backup and restore to clean up any invalid data. Been more than 10 years since I have touched a SX2000 though, not sure I remember the process but I think it varies depending on platform and version.
-
Is there a way to check for database corruption. I will be very honest. I am concerned about doing a backup and restore for fear that it will fail to restore and end up losing everything.
Adam
-
"DBMS Check Full" from the maintenance terminal, then wait a while. Also check "DMBS Status", there should be an automated check running at 5am daily.
-
Doing DBMS Status I get
DBMS info: Lab Default DB is off
DBMS info: DBMS_INITIALIZED is on
DBMS info: Journal is on
DBMS info: Debug is off
DBMS info: Cab: 12 Dim: 12 Traffic: 15
DBMS info: Check is off
DBMS info: DBMS CHECK completed 2022-FEB-17 16:56:44.70 .
0 view error(s), 0 table error(s) detected.
This is what I get when I do DBMS Check Full
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: 12 Dim: 12 Traffic: 15
DBMS info: Check is off
DBMS info: DBMS CHECK has not been performed.
Machine Variant: SX2000FD
Installation ID: BETHEL
Time : 2022-FEB-17 16:53:00.40 THU
Plane : B - active
File Redundancy: enabled
Mate Link : closed
View: 1 cor Tuples (Max): 32767 (Current): 64
View: 2 cos Tuples (Max): 96 (Current): 96
View: 3 fac Tuples (Max): 32767 (Current): 100
View: 4 pickup_group Tuples (Max): 60000 (Current): 17
View: 5 pickup_group_for Tuples (Max): 800 (Current): 200
View: 6 route_list Tuples (Max): 128 (Current): 128
View: 7 digit_mod Tuples (Max): 32767 (Current): 800
View: 8 station_hw Tuples (Max): 16 (Current): 16
View: 9 department Tuples (Max): 5000 (Current): 700
View: 10 location Tuples (Max): 5000 (Current): 70
View: 11 station_assign Tuples (Max): 2568 (Current): 528
View: 12 speed_call Tuples (Max): 600 (Current): 600
View: 13 trunk_ans Tuples (Max): 500 (Current): 150
View: 14 interconnect_res Tuples (Max): 64 (Current): 64
View: 15 system_config Tuples (Max): 1536 (Current): 202
View: 16 dataset_circuit_ Tuples (Max): 32 (Current): 32
View: 17 misc_equip Tuples (Max): 1 (Current): 1
View: 18 trunk_assign Tuples (Max): 629 (Current): 86
View: 19 data_line_asgt Tuples (Max): 400 (Current): 0
View: 20 station_hunt_cop Tuples (Max): 176 (Current): 0
View: 21 station_hunt_dat Tuples (Max): 22528 (Current): 16
View: 22 station_hunt_inf Tuples (Max): 176 (Current): 24
View: 23 corp_dir Tuples (Max): 3604 (Current): 51
View: 24 trunk_hunt_copy Tuples (Max): 112 (Current): 0
View: 25 trunk_hunt_data Tuples (Max): 19600 (Current): 55
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): 3748 (Current): 298
View: 29 change_attribute Tuples (Max): 32767 (Current): 297
View: 30 change_attribute Tuples (Max): 32767 (Current): 297
View: 31 ars_data Tuples (Max): 65535 (Current): 255
View: 32 ars_info Tuples (Max): 65535 (Current): 7
View: 33 ac15_trk_hw Tuples (Max): 32 (Current): 0
View: 34 co_trk_hw Tuples (Max): 32 (Current): 2
View: 35 did_trk_hw Tuples (Max): 32 (Current): 1
View: 36 em_trk_hw Tuples (Max): 32 (Current): 0
View: 37 loop_trk_hw Tuples (Max): 32 (Current): 0
View: 38 ss4_asgt Tuples (Max): 756 (Current): 144
View: 39 ss4_line_data Tuples (Max): 17388 (Current): 214
View: 40 ss4_line_info Tuples (Max): 756 (Current): 17
View: 41 data_hunt_copy Tuples (Max): 45 (Current): 0
View: 42 data_hunt_data Tuples (Max): 2250 (Current): 0
View: 43 data_hunt_info Tuples (Max): 45 (Current): 0
View: 44 form_access Tuples (Max): 32767 (Current): 119
View: 45 attendant_consol Tuples (Max): 24 (Current): 1
View: 46 attendant_line_d Tuples (Max): 144 (Current): 6
View: 47 attendant_line_i Tuples (Max): 24 (Current): 1
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): 3
View: 53 call_progress_in Tuples (Max): 100 (Current): 3
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): 325
View: 57 dte_profile Tuples (Max): 16 (Current): 16
View: 58 intercept Tuples (Max): 32 (Current): 32
View: 59 modem_hunt_copy Tuples (Max): 15 (Current): 0
View: 60 modem_hunt_data Tuples (Max): 600 (Current): 0
View: 61 modem_hunt_info Tuples (Max): 15 (Current): 0
View: 62 smdr_option_assi Tuples (Max): 32767 (Current): 1
View: 63 system_option_as Tuples (Max): 32767 (Current): 1
View: 64 dte_session_prof Tuples (Max): 32767 (Current): 0
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): 40 (Current): 40
View: 70 assoc_dn Tuples (Max): 3748 (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): 20
View: 74 ss4_status_msg_i Tuples (Max): 3 (Current): 1
View: 75 loudspkr_pager_a Tuples (Max): 16 (Current): 0
View: 76 per_speedcall_as Tuples (Max): 3324 (Current): 297
View: 77 per_speedcall_di Tuples (Max): 10000 (Current): 51
View: 78 per_speedcall_di Tuples (Max): 501 (Current): 28
View: 79 independent_acc_ Tuples (Max): 1000 (Current): 762
View: 80 cable_assignment Tuples (Max): 0 (Current): 0
View: 81 apnss_group Tuples (Max): 60 (Current): 0
View: 82 call_rerouting_a Tuples (Max): 250 (Current): 175
View: 83 node_id_info Tuples (Max): 1 (Current): 1
View: 84 dts_service Tuples (Max): 300 (Current): 64
View: 85 ss4_group_data Tuples (Max): 45000 (Current): 46
View: 86 ss4_group_info Tuples (Max): 1875 (Current): 22
View: 87 ss4_bsc Tuples (Max): 17388 (Current): 33
View: 88 dpnss_trk_hw Tuples (Max): 32 (Current): 3
View: 89 network_sync Tuples (Max): 1 (Current): 1
View: 90 link_desc Tuples (Max): 16 (Current): 4
View: 91 dig_link_assign Tuples (Max): 60 (Current): 2
View: 92 data_line_locati Tuples (Max): 400 (Current): 0
View: 93 hotel_options_as Tuples (Max): 32767 (Current): 1
View: 94 dni_circuit Tuples (Max): 2369 (Current): 48
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): 1
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): 3324 (Current): 0
View: 101 hotel_ss4_data Tuples (Max): 0 (Current): 0
View: 102 max_dialled_digi Tuples (Max): 96 (Current): 96
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): 4
View: 106 logical_port Tuples (Max): 32767 (Current): 17
View: 107 call_forwarding Tuples (Max): 23095 (Current): 6
View: 108 hci_session Tuples (Max): 16 (Current): 16
View: 109 applic_profile Tuples (Max): 16 (Current): 16
View: 110 did3_trk_hw Tuples (Max): 32 (Current): 0
View: 111 node_id_data Tuples (Max): 50 (Current): 50
View: 112 cabinet_assignme Tuples (Max): 11 (Current): 11
View: 123 rem_busy_lamp_in Tuples (Max): 439 (Current): 0
View: 124 rem_busy_lamp_da Tuples (Max): 7024 (Current): 0
View: 125 ss4_blg Tuples (Max): 17388 (Current): 0
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): 10 (Current): 10
View: 133 snmp_trap_commun Tuples (Max): 1 (Current): 1
View: 134 snmp_trap_commun Tuples (Max): 10 (Current): 10
View: 142 vid_customer_eme Tuples (Max): 1 (Current): 1
View: 143 vid_customer_eme Tuples (Max): 3348 (Current): 298
View: 144 vid_psc_dsp Tuples (Max): 10 (Current): 5
View: 151 pbx_signalling_i Tuples (Max): 999 (Current): 0
View: 152 pbx_signalling_d Tuples (Max): 999 (Current): 0
View: 153 comp_zone Tuples (Max): 128 (Current): 127
View: 154 ip_address Tuples (Max): 80 (Current): 80
View: 155 path_interflow Tuples (Max): 32 (Current): 32
View: 156 real_tenant Tuples (Max): 64 (Current): 64
View: 157 dev_reslt Tuples (Max): 1 (Current): 1
View: 160 vid_security_opt Tuples (Max): 32767 (Current): 1
View: 161 vid_lb_info Tuples (Max): 1 (Current): 1
Total Number of MANBUSY circuits in system = 0
Total Number of Cancelled courtesy down requests = 0
-
Plenty of times I have seen a dbms check full show fine, but the database has invalid data... In fact, don't think I have ever seen it show an error. :/
-
The Number refers to a hunt group.
and when i do dgt trace 911 is returns 911 : Hunt group (38).
yet when I go to hunt groups and look for a hunt group with the pilot number of 911 it shows up as a blank hunt group, the same as if I search for a hunt group with a pilot number of any random number that I know is not a hunt group
What does show up as blank mean? Is it a hunt group with no members?, or can it not be found?
-
Yes when I search for a hunt group with pilot number 911 it displays this
Pilot Number : 911 Name : │
│ Hunt Mode : Circular Priority : 64 │
│ Group Type : Voice 1st Threshold (%) : │
│ RAD1 : 2nd Threshold (%) : │
│ RAD2 : Alert Device : │
│ NIGHT RAD : Phase Timer : │
│ Member │ Directory Number │ Name │
┌───────────────┌────────────────────┌─────────────────────────────────────────│
│ 1 │ │ │
│ 2 │ │ │
│ 3 │ │ │
│ 4 │ │ │
│ 5 │ │ │
│ 6 │ │ │
│ 7 │ │ │
│ 8 │ │ │
│ 9 │ │ │
This is also the same thing that it displays if I search for a hunt group with the pilot number of any directory number. So it seems to me that it really isnt a hunt group, or if it is it does not have any members.
-
Delete the hunt group and reprogram per requirement?
-
I deleted the hunt group and created a new route with digit modification and it is now working both dialing 9911 and 911. Thanks so much for all the help. I really appreciate it.
Adam