is it possible for DID based routing?

[jamessmitty]

about to start testing a ta908, i want to plug in an inbound pri and route SIP to specific IP's based on the DNIS

is this even possible to do with a ta908? and how would i go about routing specific DNIS to specific SIP IP's

[apenichet]

I am currently also trying to figure this out. I have a 908E.. I am trying to route specific calls with specific caller id's through a specific SIP TRUNK already built in the IAD.

[jayh]

You would create a voice trunk type SIP for each target IP that you have.

Then create a voice grouped-trunk and accept the DID(s) matching a specific trunk, and include that trunk in the grouped-trunk.  You may have to truncate the DID if the PRI doesn't send all digits.

Repeat as needed.

[jayh]

apenichet wrote:

I am currently also trying to figure this out. I have a 908E.. I am trying to route specific calls with specific caller id's through a specific SIP TRUNK already built in the IAD.

Are you trying to route the call to a different destination based on the phone number of the caller (ANI) or the digits dialed on the trunk (DNIS)? 

[apenichet]

Exactly... Here is a current config that I have which I got to work in my lab but cannot get it to work at customer prem. Trying to get call with ani 239XXX3900 or outpulsing 239XXX3900 to route out to T05. And at the same time we want call with ani 239XXX5022 to route out T01..

voice ani-list 911-PD

  ani 239XXX3900

!

!

voice trunk T01 type sip

  description "Metaswitch"

  sip-server primary x.x.x.x

  outbound-proxy primary iad.myt3voip.com

  authentication username "adtran" password encrypted XXXXXXXXXXXXX

  max-number-calls 60

  codec-group Trunk

!

voice trunk T02 type isdn

  description "PRI 1"

  resource-selection linear ascending

  caller-id-override number-inbound 239XXX5000 if-no-cpn

  connect isdn-group 1

  no early-cut-through

  rtp delay-mode adaptive

  rtp dtmf-relay inband

  codec-group Trunk

!

voice trunk T04 type isdn

  description "PRI 2"

  resource-selection linear ascending

  caller-id-override number-inbound 239XXX5000 if-no-cpn

  caller-id-override emergency-outbound 239XXX5000

  connect isdn-group 2

  no early-cut-through

  modem-passthrough

  t38

  no nls

  no echo-cancellation

  rtp delay-mode adaptive

  codec-group Fax

!

voice trunk T05 type sip

  description "Metaswitch911"

  sip-server primary x.x.x.x

  outbound-proxy primary iad.myt3voip.com

  authentication username "adtran911" password encrypted XXXXXXXXXX

  codec-group Trunk

!

!

voice grouped-trunk METASWITCH

  description "MetaSwitch"

  trunk T01

  accept $ cost 0

  accept NXX-XXXX cost 0

  accept 1-NXX-NXX-XXXX cost 0

  accept 1-800-NXX-XXXX cost 0

  accept 1-888-NXX-XXXX cost 0

  accept 1-877-NXX-XXXX cost 0

  accept 1-866-NXX-XXXX cost 0

  accept 1-855-NXX-XXXX cost 0

  accept 011-$ cost 0

  accept 411 cost 0

  accept 611 cost 0

  accept 911 cost 0

  accept NXX-NXX-XXXX cost 0

  reject 976-XXXX

  reject 1-900-NXX-XXXX

  reject 1-976-NXX-XXXX

  reject NXX-976-XXXX

  reject 239XXX3900$

!

!

voice grouped-trunk PRI

  description "PRI"

  trunk T02

  trunk T04

  accept 239XXX5022 cost 0

  accept 239XXX3900 cost 0

!

!

voice grouped-trunk METASWITCH911

  description "Metaswitch911"

  accept 239XXX3900 cost 0

  reject NXX-976-XXXX

  permit list 911-PD

  !deny all other trunks

  !deny all other ani

!

!

!

[apenichet]

I was able to get this working fine... Still having some other issues which I will create a different discussion... Thanks to all.

[Anonymous]

Jamessmitty,

I wanted to check in with you to make sure you had been able to resolve this issue.  Generally, the "accept" statement in the grouped-trunk determines which DNIS is routed to the associated trunk.  If you were able to resolve the issue with the assistance of one of the responses, you may want to mark them as "Correct" or "Helpful" so that other users can find them quickly.  If the problem is still not resolved, feel free to add an update or additional questions on this post.  We would be glad to continue working with you.

Thanks!

David

[apenichet]

I was able to get this to work just fine. Took alow of testing and tweaks but all in all its working now.