I understand. Happy to assist / advise technically (I am a tech at heart) or commercially if needed.
Feel free to make contact via this websire alternatively if you want direct contact the best way to contact me if needed is probably via our company website - www.360-solutions.co.uk
I hope you...
Personally I wouldnt right of the 5000.
Its a powerful bit of kit in my opinion for the sub 50 user market.
It will undoubtedly be more cost effective than a Mitel 3300 and you get alot of out of the box features.
Mivoice Call recording (formally Oaisys) is fully compliant with both the 5000 and...
one thing we have done in the past in large conference rooms with speaker systems is to hook the speaker into the headset port on a standrd IP handset. Activate the headset and the voice routes via the speakers.
If you need to say something private disable the headset / mute the phone and you...
MiVoice Business on Microsoft Hyper-V
MiVoice Business has been available as a virtual appliance on VMware since early 2010 with thousands of successfully deployed systems in the field.
With the technology improvements in recent Microsoft Hyper-V software releases, Mitel is pleased to...
check the engineering guidelines.
you need to create a GARID (group arid), this GARID will contain app records for both the 3300 and MAS.
The licences are then assigned tot eh GARID rather than the individual app records for the 3300 and application.
All details are in the engineering...
Thanks SuperNova, there are no interflows configured.
I have checked the reports and the calls are abondoned between roughly 10 and 30 seconds,
Ideally I would like to be able to get specific CLI details of these calls, so the users can then call back.
I know of no way to do this without IQ/VWF?
Hi
Customer has a 3300 MCD5 and CCM version 6 (no IQ / VWF)
We are seeing a small number of abondoned calls. I have ran reports against all agents and these all show 0 abondoned calls, my thoughts therefore are that the calls are being abondoned before they reach the agents whilst queuing on...
Hi,
We have a 3300 MCD5 sp2
CCM version 6
Customer uses both ISDN30 and SIP trunks
Calls over the ISDN30 can be reported upon within the CCM
Any calls over SIP are not detailled within the reports on the CCM.
If we search using ACD inspector we can identify the calls, if we check the raw data...
we have encountered similar problems to this many times previously, when upgrading pickup groups disappear, multiline set key programming, call re-routes, the list is endless!!!
To recitfy we have to open the backup and view the raw data files in notepad / excel and then we re-program as needed.
From my experience with presentation5 it is not guaranteed to work.
The network/networks need to honour the request however I ahve always found you get mixed results dependant on the numbers you dial / carriers passing the call
Please try the below digitmap and see if it resolves the issue…
‘Digitmap’ *xx|[0-9]xxT|[0-9]xxxT|[0-9]xxxxxxxxxT|[0-9]xxxxxxxxxxT|[00]xxxxxxxxxxT|[00]xxxxxxxxxxxT|[00]xxxxxxxxxxxxT|[00]xxxxxxxxxxxxxT|[0-9]xxxxxxxxxxxxxT|0T
‘Digitmap timeOut’ 3|3|3|3|3|3|3|3|3|3
sure you can also activate this on older releases (pre MCD6 with the schedule via maintenance commands:-
PROGRAMMED SERVICE SCHEDULE NIGHT1 DAILY <hh:mm:ss>
PROGRAMMED SERVICE SCHEDULE NIGHT1 ON/OFF
PROGRAMMED SERVICE SCHEDULE NIGHT2 DAILY <hh:mm:ss>
PROGRAMMED SERVICE SCHEDULE NIGHT2 ON/OFF...
We have roughly 12 x 3300 Mxes in a cluster all SDS sharing. Mixture of MCD4.2 and MCD6 (we are in the process of upgrading)
We are adding another 3300 Mxe MCD6.0
The controller is successfully SDS sharing with 10 out of the 12 sites, however failing to share with 2.
THe IP trunks are showing...
we have hit this issue quiet a few times and always modify the broadcast groups.
touch wood (and without wanting to tempt fate) it has never come back to bite us!
We have used SIP aware routers. The general issue is the SIP carrier will need a specific IP in the SIP header (more than likely the IP the SIP service authenticates with), however with some non SIP aware firewalls the internal IP of the handset / device making the call may be sent in the header...
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.