What type of MiVoice?
- MiVoice Office 400
- MiVoice Business
It's confusing but there are 53xx series phones on both systems but they are completely different.
6800 series phones will not be MINET FW so limited features as they will be SIP only on a MiVB.
If you login as 1st-tenant-admin and check System Configuration, Recording Planner > Compliance.
There could be a few rules in there regarding what to record and what not too. There is a Call Duration option so I would look there first.
The install document has the "Preparing the server before installation" section.
https://www.mitel.com/document-center/applications/contact-center/micontact-center-business/micontact-center-business-for-mivb/101/en/micontact-center-business-installation-and-administration-guide-for-mivb-platform...
You can change the CallerID displayed on inbound calls using "Inward Dialing Modification", then apply that to the SIP Trunk (Assuming SIP)
We use this to display the correct number coming in so that we can call back a missed call.
e.g. in Australia (Telstra) a call usually come in with 9...
The problem is that if you try and use an i-button that is in use on a customers system that you don't manage, you can't clear it.
e.g. If you buy a system from eBay, you won't be able to use the i-button because it will be locked to an existing ARID.
As an FYI I have tried one of these that were linked from jrpuder a few years ago. It registered on the AMC fine and licensed the system.
As it was new there was no risk of the ID being used by a previous system. I did not put it in to production but it appeared to work fine.
@Billz66
Yes it's...
Correct, it is a timer for Unsupervised CO (Limits the duration of outside calls transferred or forwarded to outside numbers before recalling the primary attendant.)
System > Timers and Limits > Unsupervised CO (Value from 1 - 255 minutes)
We do something similar to Billz66.
- Backup existing system
- Restore into lab environment
- Change IP addresses in lab to suit new environment
- Backup lab systems
- Restore into new environment
It's a little more stuffing around but works well for us.
Even though MiVB on an EX controller is technically virtual I don't believe you need a virtualisation license.
As DoubleUT mentioned any TDM stuff will need to be reprogrammed. If restoring from a backup you will need to remove non IP programming, i.e. trunks/extensions/MOH/paging etc...
The naming conventions are getting even more confusing now...
My understanding is that MiVoice Connect is the on premise Shoretel product. MiCloud Connect was the old Shoretel Sky product and that is what's migrating to RingCentral.
Mitel now publish all their documentation publicly...
I assume internal calls have two-way audio.
I would check your MBG routing to the SIP provider. If your MBG is in gateway mode it may be trying to route incorrectly.
Can you elaborate on your SIP trunk. i.e. networking
You won't need to add the server as a proxy as it is the server sitting on the public side. The remote proxy's are any servers behind the MBG that you want publicly accessible.
You should be able to add your public IP address in the Remote Access list and go to the https://{FQDN or...
I have only seen this when the IP/XNET trunk address hasn't been changed.
Have you rebooted the controller after changing the IP/XNET address? Pretty sure it needs a reboot.
Also noticed your call server address in option 125 is .111 not .11 I assume you want it to be .111
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.