Topics

16

MiVoice Office 250/Mitel 5000 / MBG or Port Forwarding?

« on: July 27, 2021, 05:48:56 PM »

So I have done many sites with port forwarding for remote phones... but never a site with more than about 10-15 remote phones. Where do you draw the line between doing port forwarding for remote phones and getting a MBG? I have a customer that is going to have, at least initially, about 30 remote phones, and knowing this customer could go to at 40+ within 18 months, is it recommended to go to an MBG or does it really matter.

The driving force behind this isn't work from home though, it is people constantly moving... Right now they have two sites, each with their own MiVO 250, about 60 IP sets at one site and 20 IP + 20 analog extensions, and all trunking for the IP sets goes through the larger site, and trunks for the analog lines (it's rooms in a residential facility) are separate and connect to the smaller MiVO 250. The problem here is the customer has been moving phones from one site to the other, 6-10 a month sometimes for extended periods and sometimes for just a couple weeks, but they want to take their phones, DID number, voicemail, etc with them.

So now they are looking at another facility, adding another 10-15 users, and the plan is to shuffle people around going forward there as well, so our solution is to make all phones not at the main site Teleworker phones so they can just take the phone offsite, hold down the 7 key and enter the IP address and set the emergency CID themselves rather than calling us to tear down the station and rebuild it several times a month as people move around. I am thinking a MBG would be a better solution than port forwarding as they don't have to change the Native/NAT setting in the MiVO250 if I understand correctly, but am I missing something else?

Bandwidth is not an issue, and the cost of a MBG, Teleworker licenses and paying for new Cat-D licenses for all the users to be consolidated at the main location isn't an issue for the customer, as it would largely pay for itself after several months of not having to have us make service calls to move people constantly.

17

MiVoice Office 250/Mitel 5000 / Issues on 6.3.9.108 Software

« on: April 21, 2021, 01:27:36 PM »

Anybody had any weird hunt group issues with this version of software?

We have a client that the every once in while will get a call into a hunt group, and it when they answer it the system just freezes, literally and figuratively... All activity on all phones just freezes for about 30 seconds, no one can make or receive a new call, and a system freeze occurs. This didn't start until after upgrading to 6.3.9.108 (they were previously on 6.3 build, but a year or two older version).

Oddly, this seems to only happen the day of a scheduled reset... It resets every Wednesday at 3am, and then the error occurs sometime during that day. We clear the freeze and it doesn't recur until the next week. Been going on for a couple months now.

Can't open a ticket direct with Mitel anymore, so before I reach out to our supplier's support team, any ideas here.

Freeze info:

-01:971- > -01:510- 07:09 04-21 M3259 INF EG CP Node 1 Enabled Day Mode
-01:971- > -01:511- 10:55 04-21 *** --- message_destination_t:
-01:971- > -01:512- 10:55 04-21 ***      ucd_hunt_device_t (ID(1:'5401'))
-01:971- > -01:513- 10:55 04-21 ***      depth:     0
-01:971- > -01:514- 10:55 04-21 *** --- entity_t:
-01:971- > -01:515- 10:55 04-21 ***      id:     ID(1:'5401')
-01:971- > -01:516- 10:55 04-21 ***      app_device_type:     121
-01:971- > -01:517- 10:55 04-21 *** --- device_entity_t:
-01:971- > -01:518- 10:55 04-21 ***      username:     Incoming
-01:971- > -01:519- 10:55 04-21 ***      pc_description:     ~Incoming HG
-01:971- > -01:520- 10:55 04-21 *** --- devices_queued_onto_me_list_t:
-01:971- > -01:521- 10:55 04-21 ***      is empty
-01:971- > -01:522- 10:55 04-21 *** --- devices_queued_onto_me_list_t end
-01:971- > -01:523- 10:55 04-21 ***      ACD hunt groups logged into []: None
-01:971- > -01:524- 10:55 04-21 ***      ACD hunt groups not logged into []: None
-01:971- > -01:525- 10:55 04-21 *** --- hunt_device_entity_t:
-01:971- > -01:526- 10:55 04-21 ***      hunt_list_extension:     'P4098'
-01:971- > -01:527- 10:55 04-21 ***      hunt_algorithm:     0
-01:971- > -01:528- 10:55 04-21 ***      validate_queue_operations:     FALSE
-01:971- > -01:529- 10:55 04-21 ***      no_answer_advance_timer:     180
-01:971- > -01:530- 10:55 04-21 ***      acd_hunt_group_flag:     FALSE
-01:971- > -01:531- 10:55 04-21 ***      acd_wrap_up_timer:     15
-01:971- > -01:532- 10:55 04-21 ***      priority_level:     0
-01:971- > -01:533- 10:55 04-21 ***      supervisor_list_extension:     'P4096'
-01:971- > -01:534- 10:55 04-21 ***      average_connect_time_per_call:     60
-01:971- > -01:535- 10:55 04-21 ***      hunt_campon_flag:     TRUE
-01:971- > -01:536- 10:55 04-21 ***      group_call_pickup_allowed:     FALSE
-01:971- > -01:537- 10:55 04-21 ***      use_acd_agent_id_flag:     FALSE
-01:971- > -01:538- 10:55 04-21 ***      reset_acd_last_call_time_flag:     FALSE
-01:971- > -01:539- 10:55 04-21 ***      send_campon_notification_to_dnd_members:     FALSE
-01:971- > -01:540- 10:55 04-21 ***      acd_agent_list_extension:     'P4097'
-01:971- > -01:541- 10:55 04-21 ***      audio_for_camped_on_announcement_calls:     0
-01:971- > -01:542- 10:55 04-21 ***      audio_for_calls_ringing_this_device:     2
-01:971- > -01:543- 10:55 04-21 ***      audio_for_calls_ringing_this_device_board_number:     8
-01:971- > -01:544- 10:55 04-21 ***      audio_for_calls_ringing_this_device_audio_source_ number:     0
-01:971- > -01:545- 10:55 04-21 ***      audio_for_calls_camped_onto_this_device:     3
-01:971- > -01:546- 10:55 04-21 ***      audio_for_calls_camped_onto_this_device_board_num ber:     8
-01:971- > -01:547- 10:55 04-21 ***      audio_for_calls_camped_onto_this_device_audio_sou rce_number:     0
-01:971- > -01:548- 10:55 04-21 ***      hunt_group_type:     0
-01:971- > -01:549- 10:55 04-21 *** --- ucd_hunt_device_entity_t:
-01:971- > -01:550- 10:55 04-21 ***      announcement_station:     ''
-01:971- > -01:551- 10:55 04-21 ***      announcement_timer:     18
-01:971- > -01:552- 10:55 04-21 ***      overflow_station:     ''
-01:971- > -01:553- 10:55 04-21 ***      overflow_timer:     72
-01:971- > -01:554- 10:55 04-21 ***      recall_destination:     '5400'
-01:971- > -01:555- 10:55 04-21 ***      recall_timer:     180
-01:971- > -01:556- 10:55 04-21 ***      is_voice_mail_hunt_group:     0
-01:971- > -01:557- 10:55 04-21 ***      mailbox_node_number:     0
-01:971- > -01:558- 10:55 04-21 *** --- device_t:
-01:971- > -01:559- 10:55 04-21 ***      this:     02209394
-01:971- > -01:560- 10:55 04-21 ***      device_class:     HUNT_GROUP_CLASS
-01:971- > -01:561- 10:55 04-21 ***      Hunt Groups Camped onto Me:          None
-01:971- > -01:562- 10:55 04-21 *** --- abstract_mc_device_t:
-01:971- > -01:563- 10:55 04-21 ***      destroy_call_control_on_return_from_process_messa ge:     FALSE
-01:971- > -01:564- 10:55 04-21 ***      destroy_datagram_control_on_return_from_process_m essage:     FALSE
-01:971- > -01:565- 10:55 04-21 *** --- ucd_hunt_call_control_t:
-01:971- > -01:566- 10:55 04-21 *** --- hunt_call_control_t:
-01:971- > -01:567- 10:55 04-21 *** --- abstract_device_call_control_t:
-01:971- > -01:568- 10:55 04-21 *** --- message_destination_t:
-01:971- > -01:569- 10:55 04-21 ***      abstract_device_call_control_t (ID(1:'@1492'))
-01:971- > -01:570- 10:55 04-21 ***      depth:     1
-01:971- > -01:571- 10:55 04-21 ***      parent_message_destination_ptr->get_id ():     ID(1:'5401')
-01:971- > -01:572- 10:55 04-21 ***      creation time: 04-21-21 10:55:39
-01:971- > -01:573- 10:55 04-21 ***       call_ids for this call control:
-01:971- > -01:574- 10:55 04-21 ***         call_id is ID(1:'@025X')
-01:971- > -01:575- 10:55 04-21 ***         call_id is ID(1:'@0260')
-01:971- > -01:576- 10:55 04-21 ***         call_id is ID(1:'@0261')
-01:971- > -01:577- 10:55 04-21 ***     state machine:
-01:971- > -01:578- 10:55 04-21 ***      [1] <merge_wait_hgs_t>
-01:971- > -01:579- 10:55 04-21 ***           u()
-01:971- > -01:580- 10:55 04-21 ***           b()
-01:971- > -01:581- 10:55 04-21 ***      [ 0 ]
-01:971- > -01:582- 10:55 04-21 ***           u()
-01:971- > -01:583- 10:55 04-21 ***           b()
-01:971- > -01:584- 10:55 04-21 *** --- abstract_device_call_control_t end
-01:971- > -01:585- 10:55 04-21 ***      processing_campon:     0
-01:971- > -01:586- 10:55 04-21 ***      most_recent_connect_request_indicated_that_a_merg e_would_follow:     FALSE
-01:971- > -01:587- 10:55 04-21 ***      originating_call_info is null
-01:971- > -01:588- 10:55 04-21 ***      connecting_call_info is null
-01:971- > -01:589- 10:55 04-21 ***      ACD Agents Already Been Rung: NONE
-01:971- > -01:590- 10:55 04-21 ***      Members Who Sent a Setup Reject: NONE
-01:971- > -01:591- 10:55 04-21 ***      Members Who Have Been Redirected: NONE
-01:971- > -01:592- 10:55 04-21 *** --- hunt_call_control_t end
-01:971- > -01:593- 10:55 04-21 ***      announcement_station_status:     0
-01:971- > -01:594- 10:55 04-21 ***      overflow_station_status:     0
-01:971- > -01:595- 10:55 04-21 *** --- ucd_hunt_call_control_t end
-01:971- > -01:596- 10:55 04-21 ***      CALL ID TO CALL CONTROL MAP
-01:971- > -01:597- 10:55 04-21 ***         ID(1:'@025X')
-01:971- > -01:598- 10:55 04-21 ***         ID(1:'@0260')
-01:971- > -01:599- 10:55 04-21 ***         ID(1:'@0261')
-01:971- > -01:600- 10:55 04-21 *** --- hunt_device_t:
-01:971- > -01:601- 10:55 04-21 ***      device_call_info_queue is empty
-01:971- > -01:602- 10:55 04-21 ***      ACD Wrap-Up Hunt Group Members: NONE
-01:971- > -01:603- 10:55 04-21 ***      Removed Hunt Group Members: NONE
-01:971- > -01:604- 10:55 04-21 ***      Hunt Group Members in DND/Offline: NONE
-01:971- > -01:605- 10:55 04-21 ***      Unavailable Hunt Group Members:
-01:971- > -01:606- 10:55 04-21 ***        ID: ID(1:'5308')  Agent ID: ''  ACD Calls: 0  Date/Time: 04-21-2021  03:00:31
-01:971- > -01:607- 10:55 04-21 ***        ID: ID(1:'5306')  Agent ID: ''  ACD Calls: 0  Date/Time: 04-21-2021  03:00:31
-01:971- > -01:608- 10:55 04-21 ***        ID: ID(1:'5303')  Agent ID: ''  ACD Calls: 0  Date/Time: 04-21-2021  03:00:31
-01:971- > -01:609- 10:55 04-21 ***        ID: ID(1:'5301')  Agent ID: ''  ACD Calls: 0  Date/Time: 04-21-2021  03:00:31
-01:971- > -01:610- 10:55 04-21 ***      Available Hunt Group Members: NONE
-01:971- > -01:611- 10:55 04-21 ***      offline_reported_to_status_module: 0
-01:971- > -01:612- 10:55 04-21 *** --- status_msg_t:
-01:971- > -01:613- 10:55 04-21 ***      update_messages_pending:     0
-01:971- > -01:614- 10:55 04-21 ***      current_status:     Busy
-01:971- > -01:615- 10:55 04-21 ***      previously_reported_status:     Busy
-01:971- > -01:616- 10:55 04-21 ***      current_num_secondary_calls:     0
-01:971- > -01:617- 10:55 04-21 ***      previous_num_secondary_calls:     0
-01:971- > -01:618- 10:55 04-21 ***      current_secondary_call_summary:     0
-01:971- > -01:619- 10:55 04-21 ***      previous_secondary_call_summary:     0
-01:971- > -01:620- 10:55 04-21 ***      current_status_for_park_key:     Change to Alerting Status
-01:971- > -01:621- 10:55 04-21 ***      previous_status_for_park_key:     Change to Alerting Status
-01:971- > -01:622- 10:55 04-21 *** --- request_list:
-01:971- > -01:623- 10:55 04-21 *** --- status_msg_t end
-01:971- > -01:624- 10:55 04-21 *** *************************************************************************************************
-01:971- > -01:625- 10:55 04-21 ***                                   F R E E Z E     S U M M A R Y                                 
-01:971- > -01:626- 10:55 04-21 *** **** REASON:   
-01:971- > -01:627- 10:55 04-21 ***                                  SAT Manager Freeze (
-01:971- > -01:628- 10:55 04-21 *** **** SITE INFO:
-01:971- > -01:629- 10:55 04-21 ***                 Company Name:   
-01:971- > -01:630- 10:55 04-21 ***                         Address:
-01:971- > -01:631- 10:55 04-21 ***                                  , 
-01:971- > -01:632- 10:55 04-21 ***                         Phone:   
-01:971- > -01:633- 10:55 04-21 ***                 Service Manager Name: 
-01:971- > -01:634- 10:55 04-21 ***                                 Phone:
-01:971- > -01:635- 10:55 04-21 ***                                 Email:
-01:971- > -01:636- 10:55 04-21 *** **** SYSTEM INFO:
-01:971- > -01:637- 10:55 04-21 ***                 License Number:  50998049
-01:971- > -01:638- 10:55 04-21 ***                 Version:         6.3.9.108
-01:971- > -01:639- 10:55 04-21 ***                 Product:         5000 CP
-01:971- > -01:640- 10:55 04-21 ***                 CPU Type:        MiVoice Office 250
-01:971- > -01:641- 10:55 04-21 *** *************************************************************************************************
-01:971- > -01:642- 10:55 04-21 *** Failed to start ADD post thread!
-01:971- > -01:643- 10:55 04-21 M3001 INF EG CP System History Of Node 1 Has Been Frozen From Node 1

18

Mitel MiVoice Business/MCD/3300 / Display DNIS digits while ringing

« on: November 23, 2020, 04:33:14 PM »

I have a customer who wants their DNIS digits for DID to display on the phones that ring on that number (ring group) so they know it's a call on that number. I copied the existing COS to a new one and applied to those 6 sets and changed "Display ANI/ISDN Calling Number Only" to disabled thinking that would display the DNIS digits before the call is answered, but it still just shows the Caller ID information in the display of all the phones.

What am I missing to make it just show the DNIS until the call is answered, then show the Caller ID/ANI? This is on a PRI with 53xx sets.
 

19

MiVoice Office 250/Mitel 5000 / Backups broken?

« on: August 17, 2020, 03:36:18 PM »

Seems something happened that we cannot backup any Mitel MiVoice Office 250 anymore, fails about 80% through and db Studio just closes... Microsoft Updates? I can't be the only one, it's happening on more than one of our Windows 10 PC's.

20

MiVoice Office 250/Mitel 5000 / Restart E-Mail System

« on: June 24, 2020, 02:40:14 PM »

So I am playing with the "Allow any authorization servers" setting in E-Mail Gateway, but when I change it there is a pop-up that says:

"WARNING: You need to restart E-Mail System or reboot the MiVO-250 system to complete this operation"

Anybody know how to restart the E-Mail system without rebooting the whole system?

21

Mitel Software Applications / Crazy upgrade time...

« on: April 23, 2020, 12:36:54 PM »

Not a question, maybe a little bit of a warning though...

Had MiCollab 8.1 in my test bench and started an upgrade to the latest this morning at like 8:15 with a clean install of MSL. This is the slowest process I can ever remember and it's on a pretty stout machine, Dell PowerEdge server with Xeon E3-1200 CPU, 32GB RAM, and SSD RAID drives. It is now 11:34am and we are just at 50% complete.

Good thing this isn't a production system or I might have people yelling at me. I don't remember this process ever taking long.

22

MiVoice Office 250/Mitel 5000 / On a lighter note... How long have you seen a MiVO running w/o a reboot?

« on: March 26, 2020, 02:18:47 PM »

On the lighter side... How long have you seen a MiVO running without a reboot or hard boot?

Most are under 180 days I run across, some occasionally longer, often with long uptimes but recent scheduled reboots, but saw this one today... 518 days, 20 hours, 24 minutes, last system reset Oct 24, 2018.

Think I have seen some longer, but this one struck me as odd because they have had a complete network changeout in the last year.

23

MiVoice Office 250/Mitel 5000 / Strange log message

« on: March 02, 2020, 12:11:07 PM »

So I have a customer with a MiVO 250 that has been reporting a large number of IP phones repeatedly giving an Alarm 10 that just clears itself after a minute or two, but in the logs, this message is repeated over and over:

-02:305- > -02:277- 10:57 03-02 *** CP_TEST asai_first_party_state_t::process_vm_transfer_info_message enter
-02:305- > -02:278- 10:57 03-02 *** CP_TEST asai_first_party_state_t::process_vm_transfer_info_message enter
-02:305- > -02:279- 10:57 03-02 *** CP_TEST asai_first_party_state_t::process_vm_transfer_info_message enter
-02:305- > -02:280- 10:57 03-02 *** CP_TEST asai_first_party_state_t::process_vm_transfer_info_message enter
-02:305- > -02:281- 10:57 03-02 *** CP_TEST asai_first_party_state_t::process_vm_transfer_info_message enter
-02:305- > -02:282- 10:57 03-02 *** CP_TEST asai_first_party_state_t::process_vm_transfer_info_message enter
-02:305- > -02:283- 10:57 03-02 *** CP_TEST asai_first_party_state_t::process_vm_transfer_info_message enter
-02:305- > -02:284- 10:57 03-02 *** CP_TEST asai_first_party_state_t::process_vm_transfer_info_message enter
-02:305- > -02:285- 10:59 03-02 *** CP_TEST asai_first_party_state_t::process_vm_transfer_info_message enter
-02:305- > -02:286- 10:59 03-02 *** CP_TEST asai_first_party_state_t::process_vm_transfer_info_message enter
-02:305- > -02:287- 10:59 03-02 *** CP_TEST asai_first_party_state_t::process_vm_transfer_info_message enter
-02:305- > -02:288- 10:59 03-02 *** CP_TEST asai_first_party_state_t::process_vm_transfer_info_message enter
-02:305- > -02:289- 10:59 03-02 *** CP_TEST asai_first_party_state_t::process_vm_transfer_info_message enter
-02:305- > -02:290- 11:00 03-02 *** CP_TEST asai_first_party_state_t::process_vm_transfer_info_message enter
-02:305- > -02:291- 11:00 03-02 *** CP_TEST asai_first_party_state_t::process_vm_transfer_info_message enter
-02:305- > -02:292- 11:00 03-02 *** CP_TEST asai_first_party_state_t::process_vm_transfer_info_message enter
-02:305- > -02:293- 11:00 03-02 *** CP_TEST asai_first_party_state_t::process_vm_transfer_info_message enter
-02:305- > -02:294- 11:00 03-02 *** CP_TEST asai_first_party_state_t::process_vm_transfer_info_message enter
-02:305- > -02:295- 11:00 03-02 *** CP_TEST asai_first_party_state_t::process_vm_transfer_info_message enter
-02:305- > -02:296- 11:00 03-02 *** CP_TEST asai_first_party_state_t::process_vm_transfer_info_message enter
-02:305- > -02:297- 11:00 03-02 *** CP_TEST asai_first_party_state_t::process_vm_transfer_info_message enter
-02:305- > -02:298- 11:01 03-02 *** CP_TEST asai_first_party_state_t::process_vm_transfer_info_message enter
-02:305- > -02:299- 11:01 03-02 *** CP_TEST asai_first_party_state_t::process_vm_transfer_info_message enter
-02:305- > -02:300- 11:01 03-02 *** CP_TEST asai_first_party_state_t::process_vm_transfer_info_message enter
-02:305- > -02:301- 11:01 03-02 *** CP_TEST asai_first_party_state_t::process_vm_transfer_info_message enter
-02:305- > -02:302- 11:02 03-02 *** CP_TEST asai_first_party_state_t::process_vm_transfer_info_message enter


Any thoughts? The system was rebooted in the last 24 hours...

24

Mitel MiVoice Business/MCD/3300 / MXeII emergency replacement with MXe?

« on: September 19, 2019, 05:49:51 PM »

Does anyone know if you could use an MXe controller as an emergency replacement for an MXeII? And by that I mean, could I just pull the HDD and SysID module from the MXeII and swap them into an MXe controller and go (assuming all other necessary hardware)?

The system isn't very large... maybe 60 or 70 phones with embedded VM, but it looks like the 2-port LAN switch in the MXeII controller is failing and they are going go to an MXeIII soon, but we don't have a II or III in stock at the moment due to other issues in the last few months.

25

Non-Mitel Chatter / Area Code and Exchange app for Android

« on: April 23, 2019, 10:09:29 AM »

So for many years I had this great little ad-free app called "Zip Code Tools" that had a feature where you could enter the area code and exchange (NPANXX) into one of the tabs, and it would return the city/state it serves, the LATA code, Rate Center name, OCN, Switch code, Vert and Horiz, and a ton of stuff about the area... Like it was doing a dip to NANPA database for that NPANXX. But when I switched phones a couple weeks ago it didn't restore, and it doesn't seem to be in Play Store any longer.

LocalCallingGuides.com has most of this information, but not all of it.

Since my Google-foo seems to be failing me, does anyone know of an Android app that can do that? I am not opposed to paying for it either if it does what I need. This isn't very relevant to Mitel, but I used this app a lot in our Broadsoft system to add NPANXX to the network server manually when needed and it worked great.

26

MiVoice Office 250/Mitel 5000 / Upload audio file to Audiotex or VM Greeting

« on: November 02, 2018, 12:45:08 PM »

Has anyone found a reasonably easy way to upload a custom MP3/WAV file as either a mailbox greeting or Audiotex recording? I seem to remember a discussion about this not long ago, but can't seem to find it.

27

Mitel MiVoice Business/MCD/3300 / Upgrade CXi II with VLANs

« on: October 12, 2018, 09:26:16 AM »

I have a site with MCD6 on a CXi II controller I need to upgrade to the 8.0 but the last time I tried it failed the upgrade but recovered fully.

I realized after the fact that for 6.0 I must do a Full Install upgrade and not just an Upgrade in the software installer, at least according to the help file:

A full install is required on controllers with Release 7.x or earlier software.

But I have never done an upgrade where multiple VLANs are being handled by the CXi. The data VLAN is 10 and voice VLAN is 6, and I have a PC setup on the voice VLAN. Could this cause an issue with connectivity when the controller reboots, or will it just "know" it needs to use VLAN 6 for the upgrade?

28

Mitel MiVoice Business/MCD/3300 / MXe III/CX II 1GB RAM upgrade

« on: September 19, 2018, 09:49:02 AM »

Hmm... Was going to order the 1GB RAM upgrade for my "new" MXe III for the test bench, but it is out of stock at our authorized distributor.

So we need 1GB of RAM for the MXe III or CX II controller, looks like right now it has a simple Hynix 512MB DDR2-667 (PC2-5300) SODIMM non-ECC, regular old-school laptop RAM module... for 10% of the cost I can get what appears to be correct module from Crucial http://www.crucial.com/usa/en/ct12864ac667

Can anyone verify the 1GB RAM module used in the newer controllers? Maybe attach a pic?

Anybody try to go this route in the past?

Looks like a 2GB module is actually less... I wonder...

29

MiVoice Office 250/Mitel 5000 / Database Reporting issue

« on: June 06, 2018, 09:34:27 AM »

In System Administration and Diagnostics, under Reporting, Database Reporting, is anyone else having an issue where you try to generate any report it fails with "There is a problem generating the report. Please try running DB Test and Repair on the database. If the problem persists, save the logs and contact Technical Support." then after about 15 seconds Sys Admin closes automatically?

EDIT: Another technician in my office is having the same issue, and we have tried it on a few remote access machines, all of them have the same issue.

I am getting it on all sites (tried about 5) and system versions. I am using the latest SysAdmin (6.3.21.0-64bit) on Windows 10.

30

Mitel Software Applications / MiVoice Call Recording IP address change

« on: May 28, 2018, 10:29:12 AM »

Anyone have much experience with changing IP's in MiVCR (Oaisys)? I am putting one together on the bench as part of system to be installed in a couple weeks, but I don't know what the subnet is going to be yet, so I am just going to put it on my test VLAN.

I know in some Mitel servers, changing the IP address can be "troublesome" sometimes... This is my first MiVCR installation, I really don't have to reinstall onsite when doing the cut-over. Can I just setup a static IP and then change it easily later on the interface in Windows, then in Network Config?