Author Topic: Routing based on Source  (Read 3836 times)

Offline mattwilsonuk

  • Contributer
  • *
  • Posts: 23
  • Karma: +0/-0
    • View Profile
Routing based on Source
« on: April 27, 2010, 01:45:23 AM »
Hi

Is there a way to route calls based on the source number as opposed to Digits Dialled?

Cheers

Matt


Offline Mitel100

  • Sr. Member
  • ****
  • Posts: 262
  • Country: gb
  • Karma: +6/-0
    • View Profile
Re: Routing based on Source
« Reply #1 on: April 27, 2010, 01:52:54 AM »
Not with the 3300 alone, but if you had a Nupoint with Call director enabled or the 6160 (IQ) then yes.

Offline mattwilsonuk

  • Contributer
  • *
  • Posts: 23
  • Karma: +0/-0
    • View Profile
Re: Routing based on Source
« Reply #2 on: April 27, 2010, 02:03:56 AM »
I have both, what im trying to do is route calls over 2 new PRI trunks.

All calls which withhold CLI to be routed over one, and a small subset (those who send out CLI using CPN substitution) to be routed over the other.


Offline Mitel100

  • Sr. Member
  • ****
  • Posts: 262
  • Country: gb
  • Karma: +6/-0
    • View Profile
Re: Routing based on Source
« Reply #3 on: April 27, 2010, 04:13:22 AM »
Apologies, I mis-understood your question. So you want to route calls based on outgoing not incoming. In that case, if you know the extensions in both cases, then this can be achieved via Class of Restriction.

Basically, you create two new COR for both groups, let say COR20 for group 1 (Withheld) and COR21 for group 2 (CLI). and then follow these programmig steps:

1 - Ensure that COR 20 blocks COR 21 and vise versa.
2 - Create 2 trunk groups (Trunk grp 1 for withheld and Trunk grp 2 for CLI)
3 - Create routes (however many are needed) each route details the Trunk with the relevant COR (so Route 20 with TG1 and COR 20 and route 21 with TG2 and COR 21)
4 - Create a route list with the route just created (RL 20 1st route 20 , 2nd route 21)
5 - change your Digits dialled to point to this Route List

What will happen if set-up correctly is that when the extensions with COR 21 hit route list 20, then they will be barred from the 1st route and therefore cannot use that TG, but will still be able to dial out via the 2nd route. and this will be the same but in reverse for users with COR 30.

I hope this helps

Offline mattwilsonuk

  • Contributer
  • *
  • Posts: 23
  • Karma: +0/-0
    • View Profile
Re: Routing based on Source
« Reply #4 on: April 27, 2010, 03:08:39 PM »
Ahh perfect.. Never thought of that ;-)

Ill let you know how I get on..!!

Thanks muchly..!

Matt

Offline hsearson

  • Jr. Member
  • **
  • Posts: 78
  • Karma: +0/-0
    • View Profile
Re: Routing based on Source
« Reply #5 on: April 28, 2010, 04:02:01 PM »
In addition to this, at my site we already have route lists going to a choice 1 and 2. Now we want to route calls from two phones to go out on only a specific analog trunk.

I create two cors 25 and 26 and two trunk groups 25 and 26, i blocked cor 25 and 26 from default cor 1, also blocked cor 1/26 from cor 25, and 1 and 25 from cor 26. then i create two more routes 25 - 26 to go out the correct trunks accordingly (tg 25/26).

so in the route lists first choice goes to route 1, second to route 2 (local/long distance routes). for 3rd i placed route 25, and 4th route 26.  thinking that any phone in cor 25 will skip past route 1, 2 and hit route 25, and cor 26 will bypass the first 3 and go out 26.  But I am getting a access denied when pressing start digit 9. Is there anything I am missing?

Offline Mattmayn

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1069
  • Country: vi
  • Karma: +14/-0
    • View Profile
Re: Routing based on Source
« Reply #6 on: April 29, 2010, 09:05:31 AM »
Sounds like you need to check the COR assigned to those sets.


 

Sitemap 1 2 3 4 5 6 7 8 9 10