616
Mitel MiVoice Business/MCD/3300 / Re: Peripheral Bays
« on: March 28, 2017, 11:48:10 AM »
So moving forward from 6.0, the supersets are basically being deprecated? You couldn't hook a superset up to an ASU II for instance, correct?
Welcome to Mitel Forums. The Mitel resource - by techies, for techies...
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.
The second single line key with CPN substitution might not be a bad idea. Base user 2003 could have a single line appearance of 20#03 and label it "Office B". They could press Office B to make an outgoing call from Office B with CPN substitution to reflect that location.
It's not automatic, but then it also gives users the flexibility of calling from "either office" no matter which office they are physically located.
Just to be clear - if the user from ControllerA is logged in at SiteB, then all their calls will use the ControllerA trunks? Or not?
Because it sounds to me like you are suggesting that a call travelling to the carrier across ControllerA's trunks could be claiming a callerID that doesn't belong to those trunks. My understanding is - where I am - the carrier is pretty much legally bound to not honour that fake CallerID.
Thanks for the feedback.
I also schedule DBMS check every night.
Daily exporting of SMDR data might be also a good idea.
If a DMBS Check results in an issue, it will put the controller in to alarm to let you know.
When you schedule the DBMS check does that export it's findings to an FTP server or can it email you the results?
Thanks,
What advantage will the key system key give me over the other (2) types?
Thank you