Hi
My client says that when they trying to pull call records from the Amethyst it only shows the name and Extension number, it no longer shows the outgoing number or incoming number.
Please advise how i can resolve this.
Client Outgoing Number
Moderators: Leon van Heerden, Luanda_Junzi, Belinda Frick, Lee Hendricks
9 posts
• Page 1 of 1
Client Outgoing Number
by CMVAS Support » Thu Feb 06, 2014 12:14 pm
- CMVAS Support
- Posts: 18
- Joined: Wed Aug 01, 2012 1:01 pm
Re: Client Outgoing Number
by CMVAS Support » Thu Feb 06, 2014 2:49 pm
Please advise if anyone has looked at this fault?
I have phoned in to Support and left a voicemail as nobody was available!
I have phoned in to Support and left a voicemail as nobody was available!
- CMVAS Support
- Posts: 18
- Joined: Wed Aug 01, 2012 1:01 pm
Re: Client Outgoing Number
by Belinda Frick » Thu Feb 06, 2014 3:23 pm
Different recording solutions has different options for call details.
I assume you are using AMETHYST with the Mitel PABX and thus AMTMitelCRE recording.
The recording soft ware receives some call details from the PABX, but we also use the call string the PABX provides for the phone number. Please check that your AMTMitel is running and receiving call details. For more details refer to forum post: How do I know AMTMitel is receiving call details?
If you are using a different recording solution and PABX, please provide more details.
I assume you are using AMETHYST with the Mitel PABX and thus AMTMitelCRE recording.
The recording soft ware receives some call details from the PABX, but we also use the call string the PABX provides for the phone number. Please check that your AMTMitel is running and receiving call details. For more details refer to forum post: How do I know AMTMitel is receiving call details?
If you are using a different recording solution and PABX, please provide more details.
- Belinda Frick
- Posts: 3808
- Joined: Fri Nov 12, 2010 4:25 pm
Re: Client Outgoing Number
by CMVAS Support » Fri Feb 07, 2014 11:20 am
Please see below the errors im getting i the AMTMitel log file
2014-02-07 11:17:04.181 [1.6.4.23] Error in MiTAI_DN.GetDNUsername: SXLineInformation: SXERR_CONGESTION
2014-02-07 11:17:18.184 [1.6.4.23] Error in MiTAI_DN.GetDNUsername: SXLineInformation: SXERR_CONGESTION
2014-02-07 11:17:32.187 [1.6.4.23] Error in MiTAI_DN.GetDNUsername: SXLineInformation: SXERR_CONGESTION
2014-02-07 11:17:46.190 [1.6.4.23] Error in MiTAI_DN.GetDNUsername: SXLineInformation: SXERR_CONGESTION
2014-02-07 11:18:00.193 [1.6.4.23] Error in MiTAI_DN.GetDNUsername: SXLineInformation: SXERR_CONGESTION
2014-02-07 11:18:14.197 [1.6.4.23] Error in MiTAI_DN.GetDNUsername: SXLineInformation: SXERR_CONGESTION
2014-02-07 11:18:28.200 [1.6.4.23] Error in MiTAI_DN.GetDNUsername: SXLineInformation: SXERR_CONGESTION
2014-02-07 11:18:42.203 [1.6.4.23] Error in MiTAI_DN.GetDNUsername: SXLineInformation: SXERR_CONGESTION
2014-02-07 11:18:56.205 [1.6.4.23] Error in MiTAI_DN.GetDNUsername: SXLineInformation: SXERR_CONGESTION
- CMVAS Support
- Posts: 18
- Joined: Wed Aug 01, 2012 1:01 pm
Re: Client Outgoing Number
by Belinda Frick » Fri Feb 07, 2014 12:39 pm
Your PABX is giving congestion errors:
You can stop/start AMTMitel to see if the PABX allows the connection:
Allow time for devices to be monitored to load and then check if you have START/STOP message in the AMTMitel logs. The STOP message is used as call details.
- Code: Select all
2014-02-07 11:18:56.205 [1.6.4.23] Error in MiTAI_DN.GetDNUsername: SXLineInformation: SXERR_CONGESTION
You can stop/start AMTMitel to see if the PABX allows the connection:
- Log into Webadmin.
In the top right-hand block it will have a link 'Stop AMTMitel'.
Once stopped, it will toggle to 'Start AMTMitel'.
Click on the 'Start AMTMitel' to start it.
Once started, it will toggle to 'Stop AMTMitel'.
Allow time for devices to be monitored to load and then check if you have START/STOP message in the AMTMitel logs. The STOP message is used as call details.
- Belinda Frick
- Posts: 3808
- Joined: Fri Nov 12, 2010 4:25 pm
Re: Client Outgoing Number
by CMVAS Support » Fri Feb 07, 2014 2:43 pm
Good Afternoon
Please see attached the log file, i do not see and STOP messages on the first 2 pages and there is still no dialed number being displayed.
Please could you login and assist, I have been struggling for 3 days trying to fix this.
http://s000.tinyupload.com/index.php?file_id=03906235726911247813
Login Details:
Admin
https://197.157.88.116:3080/
Supervisor
https://197.157.88.116 (admin/secure123)
Please see attached the log file, i do not see and STOP messages on the first 2 pages and there is still no dialed number being displayed.
Please could you login and assist, I have been struggling for 3 days trying to fix this.
http://s000.tinyupload.com/index.php?file_id=03906235726911247813
Login Details:
Admin
https://197.157.88.116:3080/
Supervisor
https://197.157.88.116 (admin/secure123)
- CMVAS Support
- Posts: 18
- Joined: Wed Aug 01, 2012 1:01 pm
Re: Client Outgoing Number
by Belinda Frick » Fri Feb 07, 2014 5:18 pm
Please note that we do not have an SLA in place. If you require us to log into Client system a call out quote must first be accepted.
You can contact us with the client name. If we have remote access we can do a remote call out, else a site visit will be required.
Before a remote call out can be scheduled, you will need to accept a quote for the call out.
The Support Centre number is 086 111 4351 for telephone support.
To request a quote for a call out you can contact Sales on 021 592 4033.
You can contact us with the client name. If we have remote access we can do a remote call out, else a site visit will be required.
Before a remote call out can be scheduled, you will need to accept a quote for the call out.
The Support Centre number is 086 111 4351 for telephone support.
To request a quote for a call out you can contact Sales on 021 592 4033.
- Belinda Frick
- Posts: 3808
- Joined: Fri Nov 12, 2010 4:25 pm
Re: Client Outgoing Number
by CMVAS Support » Tue Mar 18, 2014 3:43 pm
Good Afternoon Belinda
IT seems this problem has started again. I checked the AMTMitel logs and found the same congestion errors.
I rebooted the AMTMitel service but now it seems as though the AMTMitel initialization is in a loop. See an extract from the logs when i stopped and started the AMTMitel
IT seems this problem has started again. I checked the AMTMitel logs and found the same congestion errors.
I rebooted the AMTMitel service but now it seems as though the AMTMitel initialization is in a loop. See an extract from the logs when i stopped and started the AMTMitel
2014-03-18 15:16:27.018 [1.6.4.23] Error in MiTAI_DN.GetDNUsername: SXLineInformation: SXERR_CONGESTION
2014-03-18 15:16:41.022 [1.6.4.23] Error in MiTAI_DN.GetDNUsername: SXLineInformation: SXERR_CONGESTION
2014-03-18 15:16:55.025 [1.6.4.23] Error in MiTAI_DN.GetDNUsername: SXLineInformation: SXERR_CONGESTION
2014-03-18 15:17:09.029 [1.6.4.23] Error in MiTAI_DN.GetDNUsername: SXLineInformation: SXERR_CONGESTION
2014-03-18 15:17:23.033 [1.6.4.23] Error in MiTAI_DN.GetDNUsername: SXLineInformation: SXERR_CONGESTION
2014-03-18 15:17:37.036 [1.6.4.23] Error in MiTAI_DN.GetDNUsername: SXLineInformation: SXERR_CONGESTION
2014-03-18 15:17:51.040 [1.6.4.23] Error in MiTAI_DN.GetDNUsername: SXLineInformation: SXERR_CONGESTION
2014-03-18 15:18:05.042 [1.6.4.23] Error in MiTAI_DN.GetDNUsername: SXLineInformation: SXERR_CONGESTION
2014-03-18 15:18:19.045 [1.6.4.23] Error in MiTAI_DN.GetDNUsername: SXLineInformation: SXERR_CONGESTION
2014-03-18 15:18:33.048 [1.6.4.23] Error in MiTAI_DN.GetDNUsername: SXLineInformation: SXERR_CONGESTION
2014-03-18 15:18:47.051 [1.6.4.23] Error in MiTAI_DN.GetDNUsername: SXLineInformation: SXERR_CONGESTION
2014-03-18 15:19:01.053 [1.6.4.23] Error in MiTAI_DN.GetDNUsername: SXLineInformation: SXERR_CONGESTION
2014-03-18 15:19:15.056 [1.6.4.23] Error in MiTAI_DN.GetDNUsername: SXLineInformation: SXERR_CONGESTION
2014-03-18 15:19:29.060 [1.6.4.23] Error in MiTAI_DN.GetDNUsername: SXLineInformation: SXERR_CONGESTION
2014-03-18 15:19:43.063 [1.6.4.23] Error in MiTAI_DN.GetDNUsername: SXLineInformation: SXERR_CONGESTION
2014-03-18 15:19:53.114 [1.6.4.23] Stopping Amethyst Mitel Interface
2014-03-18 15:19:57.066 [1.6.4.23] Error in MiTAI_DN.GetDNUsername: SXLineInformation: SXERR_CONGESTION
2014-03-18 15:21:04.723 [1.6.4.23] TLogThread Thread ID: 19305
2014-03-18 15:21:04.724 [1.6.4.23] Starting Amethyst Mitel Interface
2014-03-18 15:21:04.724 [1.6.4.23] Main thread ID: 3073783504
2014-03-18 15:21:04.747 [1.6.4.23] Settings: Amethyst/iRecall host: 127.0.0.1
2014-03-18 15:21:04.747 [1.6.4.23] Settings: Amethyst/iRecall host: 27000
2014-03-18 15:21:04.747 [1.6.4.23] Settings: CTI host:
2014-03-18 15:21:04.747 [1.6.4.23] Settings: CTI port: 0
2014-03-18 15:21:04.747 [1.6.4.23] Settings: CTI key: 0
2014-03-18 15:21:04.747 [1.6.4.23] Settings: SMDR listen po: 27982
2014-03-18 15:21:04.747 [1.6.4.23] Settings: Keepalive interval: 30
2014-03-18 15:21:04.747 [1.6.4.23] Settings: Send Virtual: False
2014-03-18 15:21:04.747 [1.6.4.23] Settings: Debug logs: False
2014-03-18 15:21:04.747 [1.6.4.23] Settings: SendCTI: True
2014-03-18 15:21:04.747 [1.6.4.23] Settings: Controller: 172.17.7.2
2014-03-18 15:21:04.747 [1.6.4.23] Settings: extensions: 200-299=,500-500=,600-600=,1100-1101=,
2014-03-18 15:21:04.747 [1.6.4.23] Settings: trunks: 1-91=,91-92=,92-93=,93-94=,94-95=,95-96=,96-97=,97-98=,98-99=,99-105=,
2014-03-18 15:21:04.747 [1.6.4.23] Settings: skill groups:
2014-03-18 15:21:04.750 [1.6.4.23] Debugging logs disabled
2014-03-18 15:21:04.775 [1.6.4.23] MiTAI libraries loaded - version MITEL Telephony Application Interface - Version 13.0.1.9_SP9 REMOTE. Initialising...
2014-03-18 15:21:04.776 [1.6.4.23] TSRCHandler Thread ID : 19305
2014-03-18 15:21:09.817 [1.6.4.23] TLogThread Thread ID: 19329
2014-03-18 15:21:09.817 [1.6.4.23] Starting Amethyst Mitel Interface
2014-03-18 15:21:09.817 [1.6.4.23] Main thread ID: 3073201872
2014-03-18 15:21:09.832 [1.6.4.23] Settings: Amethyst/iRecall host: 127.0.0.1
2014-03-18 15:21:09.832 [1.6.4.23] Settings: Amethyst/iRecall host: 27000
2014-03-18 15:21:09.832 [1.6.4.23] Settings: CTI host:
2014-03-18 15:21:09.832 [1.6.4.23] Settings: CTI port: 0
2014-03-18 15:21:09.832 [1.6.4.23] Settings: CTI key: 0
2014-03-18 15:21:09.832 [1.6.4.23] Settings: SMDR listen po: 27982
2014-03-18 15:21:09.832 [1.6.4.23] Settings: Keepalive interval: 30
2014-03-18 15:21:09.832 [1.6.4.23] Settings: Send Virtual: False
2014-03-18 15:21:09.832 [1.6.4.23] Settings: Debug logs: False
2014-03-18 15:21:09.832 [1.6.4.23] Settings: SendCTI: True
2014-03-18 15:21:09.832 [1.6.4.23] Settings: Controller: 172.17.7.2
2014-03-18 15:21:09.832 [1.6.4.23] Settings: extensions: 200-299=,500-500=,600-600=,1100-1101=,
2014-03-18 15:21:09.832 [1.6.4.23] Settings: trunks: 1-91=,91-92=,92-93=,93-94=,94-95=,95-96=,96-97=,97-98=,98-99=,99-105=,
2014-03-18 15:21:09.832 [1.6.4.23] Settings: skill groups:
2014-03-18 15:21:09.835 [1.6.4.23] Debugging logs disabled
2014-03-18 15:21:09.857 [1.6.4.23] MiTAI libraries loaded - version MITEL Telephony Application Interface - Version 13.0.1.9_SP9 REMOTE. Initialising...
2014-03-18 15:21:09.858 [1.6.4.23] TSRCHandler Thread ID : 19329
2014-03-18 15:21:14.880 [1.6.4.23] TLogThread Thread ID: 19341
2014-03-18 15:21:14.880 [1.6.4.23] Starting Amethyst Mitel Interface
2014-03-18 15:21:14.880 [1.6.4.23] Main thread ID: 3073472208
2014-03-18 15:21:14.900 [1.6.4.23] Settings: Amethyst/iRecall host: 127.0.0.1
2014-03-18 15:21:14.900 [1.6.4.23] Settings: Amethyst/iRecall host: 27000
2014-03-18 15:21:14.900 [1.6.4.23] Settings: CTI host:
2014-03-18 15:21:14.900 [1.6.4.23] Settings: CTI port: 0
2014-03-18 15:21:14.900 [1.6.4.23] Settings: CTI key: 0
2014-03-18 15:21:14.900 [1.6.4.23] Settings: SMDR listen po: 27982
2014-03-18 15:21:14.900 [1.6.4.23] Settings: Keepalive interval: 30
2014-03-18 15:21:14.900 [1.6.4.23] Settings: Send Virtual: False
2014-03-18 15:21:14.900 [1.6.4.23] Settings: Debug logs: False
2014-03-18 15:21:14.900 [1.6.4.23] Settings: SendCTI: True
2014-03-18 15:21:14.900 [1.6.4.23] Settings: Controller: 172.17.7.2
2014-03-18 15:21:14.900 [1.6.4.23] Settings: extensions: 200-299=,500-500=,600-600=,1100-1101=,
2014-03-18 15:21:14.900 [1.6.4.23] Settings: trunks: 1-91=,91-92=,92-93=,93-94=,94-95=,95-96=,96-97=,97-98=,98-99=,99-105=,
2014-03-18 15:21:14.900 [1.6.4.23] Settings: skill groups:
2014-03-18 15:21:14.903 [1.6.4.23] Debugging logs disabled
2014-03-18 15:21:14.926 [1.6.4.23] MiTAI libraries loaded - version MITEL Telephony Application Interface - Version 13.0.1.9_SP9 REMOTE. Initialising...
2014-03-18 15:21:14.927 [1.6.4.23] TSRCHandler Thread ID : 19341
2014-03-18 15:21:19.948 [1.6.4.23] TLogThread Thread ID: 19354
2014-03-18 15:21:19.949 [1.6.4.23] Starting Amethyst Mitel Interface
2014-03-18 15:21:19.949 [1.6.4.23] Main thread ID: 3074676432
2014-03-18 15:21:19.965 [1.6.4.23] Settings: Amethyst/iRecall host: 127.0.0.1
2014-03-18 15:21:19.965 [1.6.4.23] Settings: Amethyst/iRecall host: 27000
2014-03-18 15:21:19.965 [1.6.4.23] Settings: CTI host:
2014-03-18 15:21:19.965 [1.6.4.23] Settings: CTI port: 0
2014-03-18 15:21:19.965 [1.6.4.23] Settings: CTI key: 0
2014-03-18 15:21:19.965 [1.6.4.23] Settings: SMDR listen po: 27982
2014-03-18 15:21:19.965 [1.6.4.23] Settings: Keepalive interval: 30
2014-03-18 15:21:19.965 [1.6.4.23] Settings: Send Virtual: False
2014-03-18 15:21:19.965 [1.6.4.23] Settings: Debug logs: False
2014-03-18 15:21:19.965 [1.6.4.23] Settings: SendCTI: True
2014-03-18 15:21:19.965 [1.6.4.23] Settings: Controller: 172.17.7.2
2014-03-18 15:21:19.965 [1.6.4.23] Settings: extensions: 200-299=,500-500=,600-600=,1100-1101=,
2014-03-18 15:21:19.965 [1.6.4.23] Settings: trunks: 1-91=,91-92=,92-93=,93-94=,94-95=,95-96=,96-97=,97-98=,98-99=,99-105=,
2014-03-18 15:21:19.965 [1.6.4.23] Settings: skill groups:
2014-03-18 15:21:19.968 [1.6.4.23] Debugging logs disabled
2014-03-18 15:21:19.991 [1.6.4.23] MiTAI libraries loaded - version MITEL Telephony Application Interface - Version 13.0.1.9_SP9 REMOTE. Initialising...
2014-03-18 15:21:19.992 [1.6.4.23] TSRCHandler Thread ID : 19354
2014-03-18 15:21:25.017 [1.6.4.23] TLogThread Thread ID: 19366
2014-03-18 15:21:25.017 [1.6.4.23] Starting Amethyst Mitel Interface
2014-03-18 15:21:25.017 [1.6.4.23] Main thread ID: 3074627280
2014-03-18 15:21:25.028 [1.6.4.23] Settings: Amethyst/iRecall host: 127.0.0.1
2014-03-18 15:21:25.028 [1.6.4.23] Settings: Amethyst/iRecall host: 27000
2014-03-18 15:21:25.028 [1.6.4.23] Settings: CTI host:
2014-03-18 15:21:25.028 [1.6.4.23] Settings: CTI port: 0
2014-03-18 15:21:25.028 [1.6.4.23] Settings: CTI key: 0
2014-03-18 15:21:25.028 [1.6.4.23] Settings: SMDR listen po: 27982
2014-03-18 15:21:25.028 [1.6.4.23] Settings: Keepalive interval: 30
2014-03-18 15:21:25.028 [1.6.4.23] Settings: Send Virtual: False
2014-03-18 15:21:25.028 [1.6.4.23] Settings: Debug logs: False
2014-03-18 15:21:25.028 [1.6.4.23] Settings: SendCTI: True
2014-03-18 15:21:25.028 [1.6.4.23] Settings: Controller: 172.17.7.2
2014-03-18 15:21:25.028 [1.6.4.23] Settings: extensions: 200-299=,500-500=,600-600=,1100-1101=,
2014-03-18 15:21:25.028 [1.6.4.23] Settings: trunks: 1-91=,91-92=,92-93=,93-94=,94-95=,95-96=,96-97=,97-98=,98-99=,99-105=,
2014-03-18 15:21:25.028 [1.6.4.23] Settings: skill groups:
2014-03-18 15:21:25.032 [1.6.4.23] Debugging logs disabled
2014-03-18 15:21:25.058 [1.6.4.23] MiTAI libraries loaded - version MITEL Telephony Application Interface - Version 13.0.1.9_SP9 REMOTE. Initialising...
- CMVAS Support
- Posts: 18
- Joined: Wed Aug 01, 2012 1:01 pm
Re: Client Outgoing Number
by Belinda Frick » Wed Mar 19, 2014 4:16 pm
If the stop/start of AMTMitel did not resolve the issue, you must log a call out with Datatex to investigate the issue.
I will ask Yvonne to send you a quote. Once accepted, the call out will be scheduled.
I will ask Yvonne to send you a quote. Once accepted, the call out will be scheduled.
- Belinda Frick
- Posts: 3808
- Joined: Fri Nov 12, 2010 4:25 pm
9 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 1 guest