You could Export the users, then block delete on the MCD. Then import the users to the vMCD with the MCD as the secondary element on the import form...simple, and should only take about an hour or so for 100 users. Since the removal of Ops Manager and the TASMAC form, I think this is the only...
This is now resolved... I got the SIP provider to add G.711A to the codec set and the uncompressed music now plays as it should.
Thanks for all the replies.
Thanks Bobcheese, that a great idea!! I'll check this out today. I suspect it will be a-law, which could explain the issue. I've noticed from looking at old pcaps that during the interop testing with the SIP provider, they offered a-law in the invite SDP...but in the now 'live' environment, they...
Thanks Craig, this option is required and is already enabled on the peer. Without this the MOH is provided by the SIP provider. The MOH works fine if G729 but not G711.
We have a vMCD running MCD 5.0, which is connected to SIP trunks. It's currently working well, but we have one issue with uncompressed calls and music on hold. Compressed calls with music on hold work fine (we have compression licenses), but as one of the controllers in the cluster is a contact...
I've just remembered another point which may be worth mentioning... The site I was installing these handsets had a couple of vMCD user controllers and two MXe III trunking gateways. When I initially registered the 5624 handset on the vMCD, it seemed to work ok, but when I made an external call...
Yes, I did manage to get them working in the end. We actually purchased the programming cradle/cable and set them up using the WinPDM software. This was a much better way of doing it and allowed for the amending of a lot more of the handset features and settings. It also allowed us to create...
Does anyone know the requirements/processes to get a 5624 WiFi handset working on a 3300.
I have a site running an MXe III with MCD 5.0 SP1 PR1. They have purchased a few Mitel 5624 handsets and although I can get past the WiFi authentication and pick up a DHCP lease from the voice VLAN, I...
Thanks for the response, but this is actually an issue experienced on the PrairieFyre Contact Centre Client, where the real-time queue screens are not updating in a decent amount of time. An example is the 'Queue Now' or 'Queue Group Now' take 15 seconds to update for any queue specified.
I have a Mitel 3300 running MCD 5.0 SP1 PR1, with PrairieFyre CIS running 6.0 Fix Pack 2.
When running a real-time queue monitor on CCC, it has about a 15 second delay on updating the queue status for Calls Waiting, longest waiting, etc...
'Agent' real-time monitors are fine and update very...
I have a customer running UCA 4.1 on MAS 3.0 UR1, with UCA Deskphone and smartphone, all is working fine. They have asked if the call history logs which are available for each client via the application, could be made available centrally for a system administrator. At present I have found that...
Yes, tried that. Same thing applies. I had to turn off SDS on both vMCD1 and trunking gateways then on again to allow this. I have also tried dropping back to default configs on both vMCD's with the minimum programming required, but still the same. The only thing I haven't tried is changing the...
I have an issue where I cannot get SDS to start sharing from one vMCD(#1) to another vMCD(#2). There are also another 2 x MXe controller's on which SDS works fine from the first vMCD(#1). It's just a vMCD to vMCD issue. The vMCD's are each on a different VMware server, one in the office and one...
login to the 3300, navigate to "Voicemail"\"VM Network servers"...then amend the time zone by either + or - 1 on the element you created previously. That should do it.
Just wondering if someone can tell me a simple way of renumbering my NuPoint huntgroup and port numbers? Obviously I'm fine with amending these on the 3300 (MCD 4.1 by the way), but not certain of the complete steps to take on the NuPoint/MAS server.
Mitelmatt: Tried the busy/rts, but still the same. LoopyLou: public trunk is set in the COS of the trunks, but I my mind this would need to be on?
I'll keep looking...
many thanks
Hi Mitelmatt. The end solution will be Personal ring groups, but I didn't want to throw that in there when the problem is just with the EHDU at the moment. The personal ring groups work fine with other test numbers as secondary members, but they don't work with EHDU numbers due to the main issue...
There is a pretty standard COR policy for all devices/trunks on this site; that is that only premium numbers are barred. All other call types are allowed on all other devices.
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.