Sort callerid on inbound route

yes its possible, no it isn't simple. We wrote one for a call company that had different groups or queues based on the region that the customer is located. The AGI script compares the callerid information to matches in the table and selects the most specific match. It did not use patterns, basically one loads the entire NPA structure into a flat-file database and it returns what extension to direct the call to. Those 'extensions' can be feature codes that route to ivr's or queues or hunt lists for that matter.

If your interested I could sell you what we wrote fairly cheap, save you on programming time etc. The customer we did the work for wanted a low-cost solution so there's no gui to load the table data, instead its done in excel and exported to a flat file.

Hello

Hmmm ok sounds very complicated, shouldn´t something like this work?

exten => 206,1,GotoIf($["${CALLERID(num)}" = "303"]?dial1)
exten => 206,n,GotoIf($["${CALLERID(num)}" != "304"]?moh:dial2)
exten => 206,n(dial1),Dial(${SPHONE1},15,rt)
exten => 206,n,Hangup()
exten => 206,n(dial2),Dial(${PHONE2},15,rt)
exten => 206,n,Hangup()
exten => 206,n(moh),MusicOnHold(default)

but instead of 303 i use _+46X. dial Swedish IVR and instead of != 304 i use != _+46X. dial English IVR.

Those patterns dont apply to conditionals, only to extensions.

You should be able to do something like exten => 206,1,GotoIf($["${CALLERID(num):0:3}" = "+46"]?dial1) as long as you want to match all callerids starting with +46.

diffen

Did you get it working?

Hello jimellis,

I haven´t had time to try this out yet but i will do that this weekend. We have a couple of new installations this week so all my time will go to doing that. But i will get back to you when I have tested it.

This has a general value, so I would consider implementing it. Would anyone be interested in sponsoring this so we could split the development costs and give it a priority?

Hello,

I will have a look and see if we might do some sponsoring regarding this.