Using # in extenstion number

[johnven]

Has any one ever had any issues with using # in an extenstion number?
Got a 3300 (8.0.8.8) and keep getting the database locked up after a DBMS check, needs reboot to clear. We've recently had somebody putting # extenstions as reroutes and only thing that has changed.

 

[TheMitelGuy]

There should be no problem with that (anything on the keypad is valid character).

I would encourage you NOT to use # in the DN as new features coming down (specific to the 5302) will not allow you to dial an extension number with # in it.

 

[johnven]

Thanks for that, knew it 'could' be used, but wasn't sure if it caused any problems. Specially with the end of dialing character.
We are getting the DBMS check starting in the morning and completing, but then the database is locked out until the next reboot. Trying to think of what might be causing it.

 

[TheMitelGuy]

What makes you say your database is locked out?

 

[johnven]

Get the following after doing a DBMS Client:

DBMS Info: Current database client list:
dbvcheck is a reader

 

[TheMitelGuy]

Can you posted your DMBS check f?

 

[johnven]

Copy of the DBMS Check:

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: 20 Dim: 17 Traffic: 20
DBMS info: DBMS CHECK scheduled for 2008-FEB-18 23:00:00.00 .
DBMS info: DBMS CHECK completed 2008-FEB-18 10:37:00.00 .
0 view error(s), 0 table error(s) detected.
Machine Variant: IP
Installation ID: Ukfa3300
Time : 2008-FEB-18 15:16:30.00 MON
Plane : A - active
File Redundancy: enabled
Mate Link : manbusy

View: 1 cor Tuples (Max): 32767 (Current): 64
View: 2 cos Tuples (Max): 96 (Current): 96
View: 3 fac Tuples (Max): 32767 (Current): 103
View: 4 pickup_group Tuples (Max): 15000 (Current): 57
View: 5 pickup_group_for Tuples (Max): 200 (Current): 6
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): 2000
View: 10 location Tuples (Max): 5000 (Current): 2000
View: 11 station_assign Tuples (Max): 764 (Current): 60
View: 12 speed_call Tuples (Max): 1000 (Current): 424
View: 13 trunk_ans Tuples (Max): 500 (Current): 150
View: 14 interconnect_res Tuples (Max): 64 (Current): 64
View: 15 system_config Tuples (Max): 2560 (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): 75
View: 19 data_line_asgt Tuples (Max): 2 (Current): 0
View: 20 station_hunt_cop Tuples (Max): 176 (Current): 0
View: 21 station_hunt_dat Tuples (Max): 11264 (Current): 47
View: 22 station_hunt_inf Tuples (Max): 176 (Current): 4
View: 23 corp_dir Tuples (Max): 19999 (Current): 1234
View: 24 trunk_hunt_copy Tuples (Max): 112 (Current): 0
View: 25 trunk_hunt_data Tuples (Max): 19600 (Current): 78
View: 26 trunk_hunt_info Tuples (Max): 112 (Current): 10
View: 27 route_assign Tuples (Max): 200 (Current): 200
View: 28 ext_data Tuples (Max): 1546 (Current): 446
View: 29 change_attribute Tuples (Max): 32767 (Current): 446
View: 30 change_attribute Tuples (Max): 32767 (Current): 446
View: 31 ars_data Tuples (Max): 65535 (Current): 51
View: 32 ars_info Tuples (Max): 65535 (Current): 9
View: 33 ac15_trk_hw Tuples (Max): 32 (Current): 0
View: 34 co_trk_hw Tuples (Max): 32 (Current): 1
View: 35 did_trk_hw Tuples (Max): 32 (Current): 0
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): 391
View: 39 ss4_line_data Tuples (Max): 71820 (Current): 4598
View: 40 ss4_line_info Tuples (Max): 756 (Current): 390
View: 41 data_hunt_copy Tuples (Max): 2 (Current): 0
View: 42 data_hunt_data Tuples (Max): 100 (Current): 0
View: 43 data_hunt_info Tuples (Max): 2 (Current): 0
View: 44 form_access Tuples (Max): 32767 (Current): 125
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): 0
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): 476
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): 30 (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): 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: 75 loudspkr_pager_a Tuples (Max): 16 (Current): 1
View: 76 per_speedcall_as Tuples (Max): 1520 (Current): 446
View: 77 per_speedcall_di Tuples (Max): 10000 (Current): 0
View: 78 per_speedcall_di Tuples (Max): 501 (Current): 0
View: 79 independent_acc_ Tuples (Max): 11000 (Current): 0
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): 60000 (Current): 544
View: 86 ss4_group_info Tuples (Max): 1875 (Current): 406
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): 6
View: 91 dig_link_assign Tuples (Max): 60 (Current): 6
View: 92 data_line_locati Tuples (Max): 2 (Current): 0
View: 93 hotel_options_as Tuples (Max): 32767 (Current): 1
View: 94 dni_circuit Tuples (Max): 3319 (Current): 1166
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): 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): 3
View: 106 logical_port Tuples (Max): 32767 (Current): 17
View: 107 call_forwarding Tuples (Max): 14075 (Current): 61
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): 19 (Current): 11
View: 113 dimension_select Tuples (Max): 32767 (Current): 1
View: 114 acd2_agent_id Tuples (Max): 1181 (Current): 21
View: 115 acd2_agent_group Tuples (Max): 64 (Current): 9
View: 116 acd2_agent_group Tuples (Max): 9600 (Current): 40
View: 117 acd2_path_info Tuples (Max): 256 (Current): 10
View: 118 acd2_path_data Tuples (Max): 256 (Current): 10
View: 119 cluster_element_ Tuples (Max): 254 (Current): 30
View: 120 remote_directory Tuples (Max): 18501 (Current): 326
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): 3
View: 124 rem_busy_lamp_da Tuples (Max): 7024 (Current): 0
View: 125 ss4_blg Tuples (Max): 71820 (Current): 7
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: 135 vid_nal_info Tuples (Max): 2 (Current): 0
View: 136 vid_nal_data Tuples (Max): 40 (Current): 0
View: 137 vid_network_sign Tuples (Max): 2 (Current): 2
View: 138 vid_xnet_vc_chan Tuples (Max): 2 (Current): 2
View: 139 vid_xnet_trk_gro Tuples (Max): 81 (Current): 81
View: 140 vid_xnet_trk_pro Tuples (Max): 81 (Current): 81
View: 141 vid_mac_address Tuples (Max): 1544 (Current): 20
View: 142 vid_customer_eme Tuples (Max): 1 (Current): 1
View: 143 vid_customer_eme Tuples (Max): 1544 (Current): 446
View: 144 vid_psc_dsp Tuples (Max): 10 (Current): 2
View: 145 vid_linked_suite Tuples (Max): 500 (Current): 0
View: 146 vid_linked_suite Tuples (Max): 16000 (Current): 0
View: 147 vid_suite_info Tuples (Max): 364 (Current): 0
View: 148 vid_suite_data Tuples (Max): 2184 (Current): 0
View: 149 xnet_voice_info Tuples (Max): 999 (Current): 4
View: 150 xnet_voice_data Tuples (Max): 19980 (Current): 0
View: 151 pbx_signalling_i Tuples (Max): 999 (Current): 6
View: 152 pbx_signalling_d Tuples (Max): 999 (Current): 6
View: 153 comp_zone Tuples (Max): 250 (Current): 250
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): 701 (Current): 23
View: 160 vid_security_opt Tuples (Max): 32767 (Current): 1
View: 161 vid_lb_info Tuples (Max): 1 (Current): 1
View: 162 vid_lb_data Tuples (Max): 23 (Current): 23
View: 163 personal_skey_in Tuples (Max): 756 (Current): 0
View: 164 personal_skey_da Tuples (Max): 4536 (Current): 0
View: 165 call_logs_info Tuples (Max): 756 (Current): 0
View: 166 call_logs_data Tuples (Max): 14000 (Current): 0
View: 167 vid_dnd Tuples (Max): 3135 (Current): 469
View: 168 vid_make_busy Tuples (Max): 2639 (Current): 446
View: 169 vid_auto_answer Tuples (Max): 1875 (Current): 390
View: 170 vid_fwding_end_c Tuples (Max): 2639 (Current): 446
View: 171 vid_active_statu Tuples (Max): 1875 (Current): 390
View: 172 vid_station_lang Tuples (Max): 1875 (Current): 390
View: 173 vid_mls_noise_se Tuples (Max): 2639 (Current): 394
View: 174 vid_reminder Tuples (Max): 0 (Current): 0
View: 175 vid_message_wait Tuples (Max): 2639 (Current): 446
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): 11253 (Current): 0
View: 179 vid_ring_group_i Tuples (Max): 176 (Current): 0
View: 180 vid_ring_group_d Tuples (Max): 5632 (Current): 0
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): 250 (Current): 250
View: 184 vid_nt_data Tuples (Max): 1500 (Current): 1500
View: 185 vid_pbx_zone Tuples (Max): 999 (Current): 6
View: 186 vid_dn_service_d Tuples (Max): 18501 (Current): 326
Internal level audit starting.
DBMS info: DBMS CHECK completed 2008-FEB-18 15:22:47.00 .
Internal level audit finished successfully.
0 view error(s), 0 table error(s) detected.

 

[TheMitelGuy]

So your issues is the 3300 is locking up after doing this?

 

[johnven]

Yes every day last week it happened, took out the #xxxx ext's and now ok. Have put some back to see if i could replicate it but ok now.

 

[TheMitelGuy]

In your logs, the ServiceOverLord should have generated a result before rebooting. See anything in the logs?

 

[johnven]

Exported the logs and cannot find that in them.

 

[TheMitelGuy]

You don't see where the 3300 rebooted?

 

[johnven]

Not on auto reboot ATM, can see where it's been rebooted. Cannot see ServiceOverLord.

 

[TheMitelGuy]

You will not see anything that states "ServerOverLord."

So you see the reboot?
What line items are before that?

 

[johnven]

10:42:54 Call Control - Maintenance Maintenance: Category(General); msgFormatId(0)Restart information from hardware status register was power up
10:42:54 Call Control - Software LOGSYSRTR is ready to route entries Log name: maintenance
10:42:54 Call Control - Software LOGSYSRTR is ready to route entries Log name: security
10:42:54 Call Control - Software LOGSYSRTR is ready to route entries Log name: mobility
10:42:51 Call Control - Software GPAGEMGR: Initializing data structures
10:42:45 HALDbUtil Maintenance: Category(General); msgFormatId(0)DBMS Status flag set. DB Download Complete..
10:42:38 Call Control - Software DBASRV created: PID = ($0006,$0035)
10:42:38 Call Control - Software DBASRV created: PID = ($0005,$0034)
10:42:38 Call Control - Software DBASRV created: PID = ($0004,$0033)
10:42:38 Call Control - Software DBASRV created: PID = ($0003,$0032)
10:42:38 Call Control - Software DBASRV created: PID = ($0002,$0031)
10:42:38 Call Control - Software DBASRV created: PID = ($0001,$0030)
10:42:38 Call Control - Software DBASRV created: PID = ($0008,$002F)
10:42:38 Call Control - Software DBASRV created: PID = ($0007,$002E)
10:42:24 IP Networking - MIPS Maintenance: Category(General); msgFormatId(0)Internal L2 Switch IP address is 10.7.160.59.
10:42:22 IP Networking - NVS Maintenance: Category(General); msgFormatId(0)nvs_BerkConvert: Recovering existing IP Networking database.
10:42:22 ResourceMonitor Maintenance: Category(General); msgFormatId(0)Progress Monitor->ResourceAlarmStartupResourceAlarmStartup ready
10:42:22 AppStartup Progress Monitor->SysServices::appStartupPart2 (10.7.160.58)appStartup successful. appStartup Task will exit.
10:42:22 ProcessorCoordinator Progress Monitor->ProcessorCoordinator:rocessorCoordinatorProcessor Coordinator source Logs initialized.
10:42:22 AppStartup Maintenance: Category(General); msgFormatId(0)Progress Monitor->SysServices::appStartupPart2 (10.7.160.58)Boot Device: ata=0Host Name: Target Name: Target IP address: 10.7.160.58:fffffc00Host IP address: 10.7.160.65Gateway IP address: 10.7.160.1Boot File: /partition1/Rtc8260Boot Flag: 0x0
10:42:22 AppStartup Unexpected Result->SysServices::appStartupPart2 (10.7.160.58)Abnormal reset, cause: (0x103) SOFTWARE_RESET
10:42:22 AppStartup Maintenance: Category(General); msgFormatId(0)Progress Monitor->SysServices::appStartupPart2MXe Platform (10.7.160.58) Booting Software version: 8.0.8.8System Relink: No relink has been applied.Call Control Relink: No relink has been applied.Abnormal reset, cause: (0x103) SOFTWARE_RESET
10:42:07 OtpLogsClient Progress Monitor - SubscribeNewLogSubscribed to * for Error
10:42:07 OtpLogsClient Progress Monitor - SubscribeNewLogSubscribed to * for Warning
10:40:37 Login/Logout Security Audit Maintenance: Category(General); msgFormatId(0)Action: login, User: system, IP Address: 10.31.152.72, Login Access: Telnet RTC, User Validated: true, Session Available: true, Session ID: 1, Comments:
10:40:29 TELNET Maintenance: Category(General); msgFormatId(0)Progress Monitor->telnetdtTnetShelld accepting telnet request from 10.31.152.72 on Port 2002

 

[TheMitelGuy]

What controller do you have? What port is your controller using to connect to the network?

 

[johnven]

It's an MXe and connected via the first port