Mitel Forums - The Unofficial Source
Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: saliou-ab on November 17, 2016, 05:40:39 AM
-
Hi all,
I am using an MXe III controller, I am using TMS iCharge billing system. My billing system is working for local calls. But it is charging the long distance calls as local calls. The TMS guy explained me that the TMS is not receiving the "00" so even though the number of digit are diffrent the long distance numbers are considered as local ones.
Can someone help? how to sort out this trouble?
Thanks in advance.
-
Can you post some outbound call records from your PBX so we can see if it's sending?
Make an outbound call where you would need to dial the 00.
Then go to maintenance commands and enter "Logs read smdr new 10" to capture the last 10 call records.
You should see your outbound call. Post it here so we can see it.
If not, then we'll need to know if you're using a different trunk group for the call.
Ralph
-
Yes of course. Thanks for the reply. Going to site this afternoon, will do it and come back to you.
-
I have done the capture on the smdr interface as below:
11/18 16:41:42 0000:00:30 2521 0007 2513 I 2513 001
11/18 16:41:02 0000:00:52 5901 *0003 2000 ISGSC 2000 001
11/18 16:41:03 0000:00:43 3001 3001 002348068893092 A T114 001 13001 A001208 1A
11/09 13:31:52 0000:00:46 GSC *0002 2610 I 2610 001
11/09 13:31:46 0000:00:04 GSC *0001 1026 IF4205 001
For admin network.
and
11/18 17:16:17 8110 8110 002348068893092 T124 001 18110 A001217
6A
11/18 17:15:22 0000:00:51 2607 *0003 I 2300 001
11/18 17:15:52 0000:00:17 2513 0003 2517 IF2512 001
For the Guest network.
The 00 appares here. So I don't know why the iCharge can't see it.
-
Your system is sending out the 00. No question.
If you see it here, that's what's being sent to their server.
Ralph
-
Thanks very much Ralph. I am reassured.
-
Thanks to all of Mitel Forum visitors and contributors. Special thanks to the site manager and the moderator.
The TMS guy had seen that the problem was on his side and corrected it after he received my captures. So this ticket can be closed. It is working fine now, all outgoing calls are correctly charged.
Once more thanks to everybody.