Outbound Caller ID on T1 CAS

Unanswered Question
Feb 6th, 2007

I have a T1 CAS being used for long distance. I am using MGCP. I am trying to get outbound Caller ID to work. Any thoughts?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Paolo Bevilacqua Tue, 02/06/2007 - 15:57

Can you clarify what is 'outboud caller id' to you ?

In T1 CAS, the terminology is for called and calling number is DNIS and ANI. Only certain types of signaling provides both. What are you using ?

Paolo Bevilacqua Tue, 02/06/2007 - 16:51

ANI in outbound T1 CAS is supported only for FGD-EANA signaling. If you have something like T1 loop-start, you cannot send out the calling number. Check with your telco, but if you want to make your life easier, you should get ISDN PRI, and a DID block.

jgentsch Mon, 02/12/2007 - 08:50

It does not seem like this is supported in MGCP only H323, confirm?

Paolo Bevilacqua Mon, 02/12/2007 - 09:41

The matter is that beside MGCP or H.323, you need E&M Feature Group D to pass ANI. As we are telling you, T1 CAS E&M alone does not supports ANI.

jgentsch Mon, 02/12/2007 - 10:04

I didn't specify. Is E&M-FGD available in MGCP or H323 only?

Murphy1518 Wed, 02/07/2007 - 01:51

We overcome the restriction of Caller ID on CAS by creating an outgoing number translation that sent the main site number out on all dial-peers that connected calls that required the number to be sent. i.e

Translation-rule tag: 1

Rule 1:

Match pattern: .*

Replace pattern: 1234567890

Match type: none Replace type: none

Match plan: none Replace plan: none

Translation Profile: FixANI

Rule for Calling number: 1

Rule for Called number:

Rule for Redirect number:

Obviously this does not send the number of the calling extn but it does at least send the main site number.


This Discussion