" *ANI*DNIS* " Signaling on T1 CAS with MGCP Gateway

Unanswered Question
Oct 16th, 2008

Has anyone figured out a way to implement the " *ANI*DNIS* " signaling when you are managing your T1 Gateways via MGCP with CallManager.

It appears there is a way to accomplish it using a TCL script, but then we would need to convert the gateways to H.323 which we would rather not do.

CallManager 6.x

Gateways 2811 and 2821 (Each have one of these T1 CAS terminated on it along with other circuits and FXO's)

These were working fine on their Avaya PBX but we moved them to the routers we had to have the carrier convert the signaling to DNIS only in order to complete inbound calls. Thus losing the ANI.

The customer is going to convert to PRI service, but until then we would like to see if we could get the " *ANI*DNIS* " signalling working with the MGCP gateways.

Any ideas or thoughts would be appreciated.

Thanks,

Dan

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
didyap Wed, 10/22/2008 - 08:35

This feature is only functional in a T1 CAS configured for E&M-feature group b (wink start). E&M signaling is typically used for trunks. It is normally the only way that a central office (CO) switch can provide two-way dialing with direct inward dialing.

Actions

This Discussion