I think I knew that IP-IP calls no longer touch the 3300 after setup. There is a very nice PDF document showing exactly how different types of calls work. I just need to find it amongst all the other very nice PDF documents and make a shortcut to it. I was actually looking at it a week or so ago before the next crises came up.
Yeah, I am whining a little here but will get it all sorted out eventually. Management is having a little problem wrapping their heads around telephones growing from an additional duty requiring 5% of one techs time to a job requiring 25% of five team members time. Some of that time is spent actually implementing the work arounds necessary to get the system to do what is required. A lot is spent chasing problems until told not to until the problem comes up again. Then back to the original work around. One of the largest problems has been the Oasis voice recorder. It was advertised as being able to record any Dn or trunk we wanted. Turns out it will not record an individual trunk using DTS and you have to fool it in to thinking the trunk is a Dn. Since users insist that an individual button on an IP phone ring when a call comes in on a trunk and be used to make outgoing calls on that trunk, it requires trunk intercept Dns and doing a directory translation from the intercept Dn to the speed dial that does a ARD route select through a trunk group of one trunk. All to make Oasis record. We would be better off running copper to an analog recorder except that we need to buy more hardware for that.
That 25% of the team member's time is spent as needed depending on the crisis de jour. Plus no one is sure who is working on what problem.
I believe that a ticket has been opened with Mitel but it has probably been buried under many other tickets opened with our tech support person about issues that are "in the book". I would have to check to see who opened the ticket and what the status is.
The switches are all Cisco and the local ones were upgraded to PoE in anticipation of the switch to VoIP. QoS is supposed to be implemented but every so often we find a switch was overlooked. There are at least 10 switches involved in the local facility. One of the the solutions to individual problems has been to reboot the phone (mostly 5360s) which can cure a problem that may no longer be there as this noise comes and goes seemingly randomly. I think users are getting used to the problem and just accepting that this is the way magic jack is going to work. I also suspect looking at logs that they are rebooting their own phones. Maintenance logs don't show E2T errors, lost packets and/or jitter. At least I don't think so but the logs are huge as this system has many many problems.
Well, thanks for pointing me back to the network and for listening. Assuming anyone still is reading at this point. I am newly motivated to make a list of all the problems and confront those in charge with making some priorities.
TD
