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.


Topics - Tech Electronics

Pages: 1 2 [3] 4 5 ... 7
31
MiCollab Guys,

So, I have been tasked with figuring out why this isn't working after the person who installed is no longer available to talk to. If I go through the normal process of putting in the following.

https:\\{micollab server}\ucs\micollab

I get to an invalid SSL Certificate page; easy fix there.

I click on the link to continue and get to a EULA page; Click Accept

I then get to a Login Page where I put in the username and password of a three different valid users with [Entry, Standard, and Premium] licensing.

After that I get an Error that states, "Can't connect to the server"

Didn't I just connect to the server?

What could be the duh thing here as I suspect this wasn't configured completely or correctly in the first place?

If I go to the following URI

https:\\{micollab server}\portal

I am get to the login page with no issue

I put in the username and password and it required me to change the password to meet the security limits

Then it brings me to a MiCollab End User Portal page that will allow me to change the following.

Settings
-User Information
--Email Address
-Preferences
--Prompt Language
--Default Page: Settings

Portal Password
-Use Password to log into this web-based interface and access your Mitel applications

Passcode
-You use your telephone login passcode to access applications, such as voice mail, from your phone. It is also used as your Hot Desk User login PIN. The default passcode is set by your administrator.

That is all I get access to at this point since the AWV is not setup at all.

Thanks,

TE

32
Mitel MiVoice Business/MCD/3300 / Hunt Group Automatic Failover?
« on: May 08, 2019, 12:55:08 PM »
Guys,

I know this must be a trivial thing to most of you, but I am not sure how to approach this scenario within the 3300.

I have an MiCC IVR setup to answer calls via a Voice Hunt Group filled with Message Ports [2000].
I  also have a Voice Mail Hunt Group Pilot for the NuPoint [2500] and within the NuPoint I created Call Director boxes to emulate the Workflows in the MiCC IVR.

Now, let's say the MiCC goes down for whatever reason; planned or otherwise.

What can I do, or what would be best practice, to create an automatic failover of the MiCC Voice Hunt Group to the Voice Mail Hunt Group of the NuPoint.

Thanks,

TE

33
Guys,

I have setup a Basic Resilient Hunt Group, with no members, that Call Reroutes to different ACD Paths when the Primary Controller Fails.

I see that the Hunt Group has been imported into the MiCC when I look under Hunt Groups.

When I try to use a Transfer Action to transfer calls to that Hunt Group it doesn't show up as an option to transfer to. How do you perform a transfer to a Hunt Group within a Work Flow?

Thanks,

TE

34
Guys,

I get this error, "page error occurred on /CCMWeb/webforms/errorhandler_noheader.aspx" when trying to access My Role and Wallboard inside of YSE.

Has anyone else run into this issue?

Thanks,

TE

35
Guys,

What is the best way to send calls to multiple workflows in the MiCC via multiple call flows from the MCD. For instance I have 43 sites that each have a different main incoming DID as well as users from those sites forwarding calls on a No Answer condition to the MiCC.

They currently have 50 - 5020 Messaging Ports going to a single Hunt Group that goes to a single Workflow.

They now want to add more site workflows with different ways to get them [DID and NA condition].

What would be the best way to handle this?

Thanks,

TE

36
Mitel Software Applications / MiCC - 5020 Programming
« on: April 12, 2019, 12:23:28 PM »
Guys,

How do you translate the Golden Rules to the different types of ports to work with the IVR portion of this product?

For instance there are the following 5020 extension types:

1. RAD Port 5020 IP
2. Messaging Port 5020 IP
3. Outbound Port 5020 IP
4. UPiQ Port 5020 IP

In the Golden Rules it doesn't state anything about how to configure these ports specifically. How does the CoS and CoR have to be for each type of 5020 IP Port? It is pretty straight forward on making sure you set the Licensing to Trusted IP, but that is the only clear piece of information that I can find on how to setup the 5020 ports.

The Golden Rules seem to break it down into 3 different columns, but these are specific to the type of ports you are using.

1. CCM & CA PBX Options
2. VMW PBX Options
3. IQ PBX Options

Which one of these setups would be used for each type of port? I am not sure why they need to make this so confusing to setup since it is a simple extension that goes inside of a Hunt Group.

Once I am past this hurdle I believe the remainder of the IVR programming will be simple in comparison since they actually trained on how to create Workflows and Subroutines, but they didn't teach anything about how to program the 3300 it was attached to.

Thanks,

TE

37
Mitel MiVoice Business/MCD/3300 / 69xx Series Phones: Issues
« on: March 08, 2019, 11:17:34 AM »
Guys,

It seems that lately we are having a lot of issues with the 69xx series phones with the combination of their Month, Week,  Revision and Firmware installed.

For instance
phones made in 2018 48 with Revision: B14(03) with FW: 1.4.0.73 will upgrade, but not downgrade.
phones made in 2018 49 with Revision: B14(03) with FW: 1.4.0.73 will upgrade, but not downgrade.
phones made in 2018 48 with Revision: B16(15)  FW: 1.4.0.73 will neither upgrade or downgrade.

Previous phones made in 2018 22 with Revision: 28(24), original FW: Unknown, will upgrade and downgrade, but if they have firmware 1.3.0.112 they seem to have issues.

Mitel's answer to some issues we were having on an 8.0 SP3 PR2 system was to upgrade them all to firmware 1.4.0.80 as that is the firmware that will work on a 8.0 system to resolve issues with firmware itself, but not the hardware issues the phones may have.

I also know previously if you had a phone that was below 1.0.0.148 it had to be manually upgraded to that version and then it would download the latest version from the system. This obviously is no longer a problem unless the issue of firmware updates has returned for phones issued towards the end of 2018.

So, my question is does anyone know of any other hardware/firmware/combinations that have issues?

Thanks,

TE

38
Non-Mitel Chatter / Personal Knowledge Base
« on: January 11, 2019, 11:06:39 AM »
Guys,

Does anyone have any recommendations for a personal knowledge base application? I am currently using the free version of TheBrain, but I think there could be others out there that might be better.

Thanks,

Steven

39
Mitel Software Applications / MBG Version Issues
« on: December 07, 2018, 10:14:16 AM »
Guys,

So, I know that when clustering MBGs together they have to be the exact same version; for instance 9.2.0.22 will not work with 9.2.0.23.

The question I have is what about the version of the MBG versus the MiCollab or the MCD; is there an issue there?

I know the MBG built into the MiCollab would have to be the same version if it were to be clustered in, but what about the remainder of the software?

The scenario I have run into is that we have a site that is running MCD 7.2 SP1 PR2 and the current Teleworker MBG is running 9.2.0.22, but that version is not available for download anymore. The customer is adding a new hosted site and wants to add SIP Trunks to the new vMBG and the carrier uses DNS SRV so we are going to the latest version of MBG 10.1.0.244 to support that, but we are going to install the vMCD at 7.2 SP1 PR2 so we don't have to upgrade all of the remaining sites. I need to know if there will be an issue with the MCDs version no longer communicating properly once we upgrade their current Teleworker MBG to 10.1.0.244; Mitel wasn't very clear with their answer.

Thanks,

TE

40
Guys,

Does anyone know where the OAI Stream information is stored on a MiContact Center Office Server or is it not stored at all?

Thanks,

TE

41
MiVoice Office 250/Mitel 5000 / Exim Template Access
« on: August 28, 2018, 02:29:07 PM »
Guys,

Does anyone know how to access and export the exim.sat_template on the system?

Thanks,

TE

42
MiVoice Call Recorder and MiContact Center Office Integration Issue with Exporting Calls to Audio File

I have an issue with getting calls to exports after following these steps.

1. Open MiCCO Reporter
2. Double Left-Click Call List All Calls
3. Find a Valid Recorded Call
4. Right-Click or Double Click on the Call Entry and Select Play
5. It opens up a connection to the MiV-CR and logs in with an account that can listen to and export calls
6. Listen to the call
7. Right-Click on the Call in MiV-CR and select Export Audio to Disk...
8. I get an error box, "The email integration module has failed to initialize; (0),
9. Click OK
10. I get another error box, "Retrieving the COM class factory for component with CLSID (61f89f0E-7DD2-4D11-A556-4501D4F0d612) failed due to the following error; 80040154 Class not registered (Exception from HRESULT: 0x8004D154 (REGDB_E_CLASSNOTREG)).
11. Click OK
12. It opens up the Export Audio to Disk box, but although I can select a Format I am not able to select a Bit Rate so it fails.

Has anyone else ran into this issue before?

The catch-22 is that if I manually open up Management Studio and list All Calls I can View I am able to Export Calls with no problem. Also, if I have already manually started Management Studio prior to using MiContact Center Office Reporter to link over there it works just fine. This only happens if MiContact Center Office Reporter tries to open up Management Studio itself, while still using the same credentials, that this problem happens.

I have been looking up the 80040154 Class not registered (Exception from HRESULT: 0x8004D154 (REGDB_E_CLASSNOTREG)) COM error and have not found anything that is helpful. This is happening on Windows 7, 10, and 2012 so it is not limited to any one OS, but I have not been able to successfully utilize regsrv32.exe to register the service the CLSID is associated with; which happens to be the CTSAudioConvert.dll and my hunch would also be the CTSMail.dll as well since I get the first error that the email integration module has failed to initialize.

I have attached an export of it failing from the Problem Step Recorder off the customer machine in case my explanation wasn't too clear.

Thanks,

TE

43
Mitel MiVoice Business/MCD/3300 / Packet Capture on MCD
« on: May 29, 2018, 01:25:46 PM »
I remember Mitel Tech support doing a packet capture via the MCD and then using FileZilla to download it from the MCD, but I can’t remember how they did it.

Does anyone know how this is done? I need to trace calls on a Console phone.

Thanks,

TE


Sent from my iPhone using Tapatalk

44
Guys,

How are you settings up your 6900 environments?

1. How is it getting an IP Address? [MiVO-250 or Server or Manual]
2. Do the 6900 series phones come up as Mitel Phone with a Vendor ID 1027?
3. Does LLDP-MED/CDP and IP Helper work with these phones?
4. Do you have to manually configure any settings?

What have you found that works and doesn't work?

Thanks,

TE

45
Guys,

Does anyone know what port or ports is required to be opened on a firewall to allow the creation of new connections to external MBGs or does it use an ephemeral port? I have a MiCollab server in LAN Mode and [2] MBGs in the DMZ in Custom LAN Mode [LAN Mode with Public IP on Set-Side Streaming].

I was told I needed to go to MiCollab Client Deployment > Configuration > Connection to MBGs > Create new connection to setup the deployment properly. When I put in the Description and IP Address and press the Save and Send AuthRequest it just times out with the following message.

Configuration was not saved!
Could not connect to MBG: timed out 


I have all of the ports opened up that the MiCollab Engineering Guidelines say need to be opened for the applications I am going to run.

From DMZ [MBG] to LAN [MiCollab]
Source TCP: ANY
Destination TCP: 6800,6801,6802,6809,3998,3999,6880,443,4443,80,36008,5024-5026,5030,7001,7003,8083,8084,4244,8188,1433
UDP: Any

From LAN [MiCollab] to DMZ [MBG]
Source TCP: 6800,6801,6802,6809,3998,3999,6880,443,4443,80,36008,5024-5026,5030,7001,7003,8083,8084,4244,8188,1433
Destination TCP: ANY
UDP: ANY

Thanks,

TE

Pages: 1 2 [3] 4 5 ... 7