Author Topic: Route DID to external number  (Read 1771 times)

Offline tjcurcio

  • Contributer
  • *
  • Posts: 25
  • Country: us
  • Karma: +1/-0
    • View Profile
Route DID to external number
« on: July 22, 2015, 11:30:19 AM »
I have a DID coming over a PRI.  Carrier is sending me the last 4 digits, in this case 2790.

In the system speedcall form I can program 2790 > 3000(voicemail hunt group) and when I call the DID I reach voicemail

If I program a speedcall pointed to an external number regardless of format 2790 > 7262116... or 2790 > 9726211... or 2790 > 99257262116... or 2790 > 919257262116.. my call does not go through.

What is the easiest way to accomplish this?


Offline x-man

  • Hero Member
  • *****
  • Posts: 1129
  • Country: gb
  • Karma: +25/-0
    • View Profile
Re: Route DID to external number
« Reply #1 on: July 22, 2015, 11:55:20 AM »
tick overides toll control. you will probably need the full number including the 9 if you ahve to dial 9 for an outside line.
« Last Edit: July 22, 2015, 11:58:43 AM by x-man »

Online ralph

  • Mitel Forums Admin
  • Hero Member
  • *****
  • Posts: 5767
  • Country: us
  • Karma: +469/-0
  • Published Author: http://amzn.to/2dcYSY5
    • View Profile
Re: Route DID to external number
« Reply #2 on: July 22, 2015, 12:05:04 PM »
There are several things that can stop those calls.
As X-man say Tick Toll Override to bypass COR.
If that doesn't work then it could be the carrier blocking it.   Turn on CCS traces to see if the call is trying to go out.
If the call is trying to go out then the problem could be that the carrier is blocking based on the caller ID source.  There's a tick box in the PRI settings for caller ID replacement.   You could turn that off or you could have the carrier allow it.

Ralph

Offline tjcurcio

  • Contributer
  • *
  • Posts: 25
  • Country: us
  • Karma: +1/-0
    • View Profile
Re: Route DID to external number
« Reply #3 on: July 22, 2015, 02:44:26 PM »
Thank you very much X-man & Ralph

CCS trace did show the call trying to go out.  So you nailed it Ralph.. carrier blocking due to caller ID source, ticking CLID replacement resolved the issue.


 

Sitemap 1 2 3 4 5 6 7 8 9 10