routing by CLID

[oldtech]

I think I see how to route by CLID in dial plan to a specific FXS card for output to a receiving device. If I have a routing plan that deals with a specific CLID number then is that aforementioned FXS card removed from capability for ALL other CLID, or does dial plan just route the specific CLID to ONLY that FXS not any other. I tried getting to "Patrick" I believe you helped me years ago on another issue.

Old Tech

[Anonymous]

In order to route by CLID, you need to have a PRI in the NETWORK TERM, and under its IFCE CONFIG set "Swap ANI/DNIS" to ENABLED. The ATLAS literally swaps the ANI and DNIS information in the SETUP message it receives on the PRI, so the call is then routed based on the original Calling Party Number (or Calling Line Identification - CLID).

If you ENABLE the "Swap ANI/DNIS" option on the Network PRI, then you will need to configure your USER TERM entries to accept either specific CLID or with wild-cards that will include the inbound CLID. So if the CLID is 256-963-8000 then you can either have the IN#ACCEPT on the FXS accept "256-963-8000," or "NXX-NXX-XXXX," or "XXX-XXX-XXXX," or "$". The ATLAS routes based on the "most specific match" so if you have 256-963-8000 as the IN#ACCEPT on one FXS port then that is the only FXS port that inbound call can use, but if that one FXS port not only has "256-963-8000" but also has "$" or "NXX-NXX-XXXX" then it can accept other inbound calls (as long as the other USER TERM entries aren't more specific so as to prevent an inbound number from going to the less specific match with wild-cares).

I hope this makes sense,

Patrick

[oldtech]

Patrick

I just got back to my desk. I was prepping for an onslaught tomorrow by management. I am dealing with an Adtran 550 set up in rabbit hole for an alarm receiver. Recently we have been getting hit hard with broken signals arriving for a five state area.

I wanted to limit my incoming call by ANI to one particular FXS card so I could record the data arriving. I know by the logs that are created that digits of the DTMF string are going missing. We are trying to determine where. As I stated, I am concerned that the dial plan would limit the card to only the number I am looking for taking the card out of the game for the other 19999 possible callers.

I will have to review the dial plan set up and your email again before I try this. I suppose I could set it up when I am sure the call is expected, tech on site, then change the dial plan back after I catch what I want.

Delivery of ANI/DNIS is currently AAAEEENNNNDNIS* out of the FXS cards to the receiving equipment.

Kevin J. Andres

NICET #90660

Fire Alarm System, Level II

EPS Security

(616) 459-3764

KAndres@EpsSecurity.com<mailto:KAndres@EpsSecurity.com>

Visit our Web Site: www.EpsSecurity.com<http://www.EpsSecurity.com>

[Anonymous]

If you are doing a rabbit-hole setup to an alarm receiver then I don't recommend setting the "Swap ANI/DNIS" to ENABLED. This literately exchanges the CALLING PARTY NUMBER with the CALLED PARTY NUMBER. So a call FROM "256-963-8000" to "1234" becomes a call from "1234" to "256-963-8000". So if you are passing 4-digit DID out the Feature Group D T1, then you typically should receive *2569638000*1234*, but with SWAP ANI/DNIS enabled, you will get *1234*8000*. You cannot swap ANI/DNIS for only certain calls so it will be swapped for all inbound calls.

[oldtech]

Patrick

Thanks for reply. Yes the Adtran 550 delivers 26945912455778* as ANI/DNIS currently.

So unfortunately, a trap for recording purposes directing to a certain FXS port on in incoming CLID is not going to work. Back to the drawing board.

Kevin J. Andres

NICET #90660

Fire Alarm System, Level II

EPS Security

(616) 459-3764

KAndres@EpsSecurity.com<mailto:KAndres@EpsSecurity.com>

Visit our Web Site: www.EpsSecurity.com<http://www.EpsSecurity.com>