- I am using AMTMitel for call details.
My TNG is configured to send of an alarm if no call details for trunk INTERNAL for more than an hour.
My TNG has an error message on the log in page that trunk INTERNAL has not had call details for over an hour.
- If an internal call is made (extension to extension) then no trunk/line is used. The line will then have the value INTERNAL.
If the PABX is not sending off call details for internal, TNG will never receive call details where the trunk/line is INTERNAL. This will then cause the alarm message on the login page.
Suggestion:
Make a test call: Let one internal extension phone another. Check if you receive call details for this test call. If not, check the AMTMitel logs after AMTMitel was restarted. On restart it will load all the device and list errors if any occurred when trying to load them for monitoring.
Example of AMTMitel error entries:
- Code: Select all
2012-12-05 16:33:40.098 [1.6.4.4] Error in MiTAI_DN.Open: SXMonitor 7663: SXERR_PRIVILEDGE_VIOLATION
2012-12-05 16:33:42.383 [1.6.4.4] Error in MiTAI_DN.Open: SXMonitor 7669: SXERR_PRIVILEDGE_VIOLATION
2012-12-05 16:33:55.896 [1.6.4.4] DEBUG: 7663 noanswer internal forwarding_on = 0 destination
2012-12-05 16:33:58.653 [1.6.4.4] DEBUG: 7669 noanswer internal forwarding_on = 0 destination
For these entries you need to check the Extensions Class of Service configuration on the Mitel PABX. Please ask your Mitel support to assist. Here are some screen shots to guide them: