Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Sending ANI to ATT

I am having problems sending the Caller ID info to ATT. Can anyone tell me if the following settings are correct for sending the ANI? FYI. I masked the real number with XXXX in the gateway config.

Gateway config

3825#debug isdn q931
debug isdn q931 is              ON.
3825#
001948: Oct 28 10:06:24.501 EDT: ISDN Se0/2/0:23 Q931: TX -> DISCONNECT pd = 8  callref = 0x8552
        Cause i = 0x82A9 - Temporary failure
001949: Oct 28 10:06:24.641 EDT: ISDN Se0/2/0:23 Q931: RX <- RELEASE pd = 8  callref = 0x0552
001950: Oct 28 10:06:24.661 EDT: ISDN Se0/2/0:23 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x8552
3825#
001951: Oct 28 10:06:27.141 EDT: ISDN Se0/2/0:23 Q931: RX <- DISCONNECT pd = 8  callref = 0x0DA4
        Cause i = 0x8290 - Normal call clearing
001952: Oct 28 10:06:27.213 EDT: ISDN Se0/2/0:23 Q931: TX -> RELEASE pd = 8  callref = 0x8DA4
001953: Oct 28 10:06:27.241 EDT: ISDN Se0/2/0:23 Q931: RX <- RELEASE_COMP pd = 8  callref = 0x0DA4
001954: Oct 28 10:06:28.093 EDT: ISDN Se0/2/0:23 Q931: RX <- SERVICE pd = 67  callref = 0x0000
        Change Status i = 0xC0 - in-service
        Channel ID i = 0xE9808382
                Exclusive, Interface 0, Channel 2
3825#
001955: Oct 28 10:06:28.097 EDT: ISDN Se0/2/0:23 Q931: TX -> SERVICE ACKNOWLEDGE pd = 3  callref = 0x8000
        Change Status i = 0xC0 - in-service
        Channel ID i = 0xA98382
                Exclusive, Channel 2
3825#
001956: Oct 28 10:06:30.373 EDT: ISDN Se0/2/0:23 Q931: TX -> DISCONNECT pd = 8  callref = 0x94E2
        Cause i = 0x8290 - Normal call clearing
001957: Oct 28 10:06:30.541 EDT: ISDN Se0/2/0:23 Q931: RX <- RELEASE pd = 8  callref = 0x14E2
001958: Oct 28 10:06:30.565 EDT: ISDN Se0/2/0:23 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x94E2
3825#
001959: Oct 28 10:06:57.092 EDT: ISDN Se0/2/0:23 Q931: RX <- SETUP pd = 8  callref = 0x0742
        Bearer Capability i = 0x8090A2
                Standard = CCITT
                Transfer Capability = Speech
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA98381
                Exclusive, Channel 1
        Progress Ind i = 0x8283 - Origination address is non-ISDN
        Calling Party Number i = 0x2183, '912XXXXXXX'
                Plan:ISDN, Type:National
        Called Party Number i = 0xA1, '912XXXXXXX'
                Plan:ISDN, Type:National
001960: Oct 28 10:06:57.108 EDT: ISDN Se0/2/0:23 Q931: TX -> CALL_PROC pd = 8  callref = 0x8742
        Channel ID i = 0xA98381
                Exclusive, Channel 1
3825#
001961: Oct 28 10:06:57.144 EDT: ISDN Se0/2/0:23 Q931: TX -> ALERTING pd = 8  callref = 0x8742
3825#
001962: Oct 28 10:07:02.740 EDT: ISDN Se0/2/0:23 Q931: TX -> CONNECT pd = 8  callref = 0x8742
001963: Oct 28 10:07:02.788 EDT: ISDN Se0/2/0:23 Q931: RX <- CONNECT_ACK pd = 8  callref = 0x0742
3825#
001964: Oct 28 10:07:13.512 EDT: ISDN Se0/2/0:23 Q931: TX -> SETUP pd = 8  callref = 0x0050
        Bearer Capability i = 0x8090A2
                Standard = CCITT
                Transfer Capability = Speech
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA98396
                Exclusive, Channel 22
        Calling Party Number i = 0x2081, '912XXXXXXX'
                Plan:Unknown, Type:National
        Called Party Number i = 0xA0, 'XXXXXXX'
                Plan:Unknown, Type:National
001965: Oct 28 10:07:13.940 EDT: ISDN Se0/2/0:23 Q931: RX <- CALL_PROC pd = 8  callref = 0x8050
        Channel ID i = 0xA98396
                Exclusive, Channel 22
3825#
001966: Oct 28 10:07:14.640 EDT: ISDN Se0/2/0:23 Q931: RX <- ALERTING pd = 8  callref = 0x8050
        Progress Ind i = 0x8288 - In-band info or appropriate now available
3825#
001967: Oct 28 10:07:35.140 EDT: ISDN Se0/2/0:23 Q931: RX <- CONNECT pd = 8  callref = 0x8050
001968: Oct 28 10:07:35.148 EDT: ISDN Se0/2/0:23 Q931: TX -> CONNECT_ACK pd = 8  callref = 0x0050
3825#
001969: Oct 28 10:07:38.196 EDT: ISDN Se0/2/0:23 Q931: RX <- SETUP pd = 8  callref = 0x12D7
        Bearer Capability i = 0x8090A2
                Standard = CCITT
                Transfer Capability = Speech
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA98386
                Exclusive, Channel 6
        Calling Party Number i = 0x4080, '904XXXXXXX'
                Plan:Unknown, Type:Subscriber(local)
        Called Party Number i = 0xA1, '912XXXXXXX'
                Plan:ISDN, Type:National
001970: Oct 28 10:07:38.212 EDT: ISDN Se0/2/0:23 Q931: TX -> CALL_PROC pd = 8  callref = 0x92D7
        Channel ID i = 0xA98386
                Exclusive, Channel 6
3825#
001971: Oct 28 10:07:38.212 EDT: ISDN Se0/2/0:23 Q931: TX -> ALERTING pd = 8  callref = 0x92D7
001972: Oct 28 10:07:38.956 EDT: ISDN Se0/2/0:23 Q931: TX -> DISCONNECT pd = 8  callref = 0x0050
        Cause i = 0x8290 - Normal call clearing
001973: Oct 28 10:07:39.188 EDT: ISDN Se0/2/0:23 Q931: RX <- RELEASE pd = 8  callref = 0x8050
3825#
001974: Oct 28 10:07:39.212 EDT: ISDN Se0/2/0:23 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x0050
3825#
001975: Oct 28 10:07:51.759 EDT: ISDN Se0/2/0:23 Q931: TX -> DISCONNECT pd = 8  callref = 0x8ADE
        Cause i = 0x8290 - Normal call clearing
001976: Oct 28 10:07:51.939 EDT: ISDN Se0/2/0:23 Q931: RX <- RELEASE pd = 8  callref = 0x0ADE
001977: Oct 28 10:07:51.975 EDT: ISDN Se0/2/0:23 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x8ADE

Gateway config in call manager

Device Information
Cisco MGCP T1 Port
2811
Digital Access PRI
RegistrationRegistered with Cisco Unified Communications Manager 10.10.0.9
IP Address10.10.0.16
S0/SU0/DS1-0@2811

Required Field
Required Field
Required Field
Required Field
Required Field

Multilevel Precedence and Preemption (MLPP)  Information

Interface Information
Required Field
Required Field
Required Field
Required Field
Required Field
Required Field
Required Field

Call Routing Information - Inbound Calls
Required Field

Call Routing Information - Outbound Calls
Required Field
Required Field
Required Field
Required Field
Required Field
Required Field
Required Field
Required Field

PRI Protocol Type Specific Information
Required Field
Required Field

UUIE Configuration
Required Field

Route Group Membership
RG_Hammond_HallRG_Hammond_Hall

Incoming Calling Party Settings
If the administrator sets the prefix to Default this indicates  call processing will use prefix at the next level setting (DevicePool/Service  Parameter). Otherwise, the value configured is used as the prefix unless the  field is empty in which case there is no prefix assigned.

Product Specific Configuration Layout
Help

2 ACCEPTED SOLUTIONS

Accepted Solutions
Cisco Employee

Re: Sending ANI to ATT

If you see the right info in the debug then call your telco as they're overriding your CLID.

HTH

java

If this helps, please rate

www.cisco.com/go/pdihelpdesk

HTH

java

if this helps, please rate

www.cisco.com/go/pdi
Silver

Re: Sending ANI to ATT

First I would try unknown/unknown.

After that I would call the carrier and ask to speak with a CO tech so they can work with you to correct.

The fact that they are not rejecting the call nor are they sending cause codes will make it difficult to reverse engineer from your end....

7 REPLIES
Silver

Re: Sending ANI to ATT

According to your debug it appears you are sending CLID:

Calling Party Number i = 0x2183, '912XXXXXXX'

Do you want to replace that with the billing number (ANI) or your main number?

If you are seeing only the main number now it is likely because the carrier is masking it in.

HTH,

Art

New Member

Re: Sending ANI to ATT

No I dont want to replace the number. I just want to make sure we are sending the number out to the PRI. I thought that as long as the Calling Party is valid sent and the number is valid for that PRI, ATT would display to the called party. Do you see any configuration errors in my config?

Cisco Employee

Re: Sending ANI to ATT

You need to properly explain what the problem is.

Are they rejecting the call?

As mentioned, called party sees other CLID info?

Some telcos ask for specific parameters here:

Plan:ISDN, Type:National

But you need to explain what the problem is.

HTH

java

If this helps, please rate

www.cisco.com/go/pdihelpdesk

HTH

java

if this helps, please rate

www.cisco.com/go/pdi
New Member

Re: Sending ANI to ATT

Caller ID is not displaying to the called Party, the PRI heading number shows instead.

Cisco Employee

Re: Sending ANI to ATT

If you see the right info in the debug then call your telco as they're overriding your CLID.

HTH

java

If this helps, please rate

www.cisco.com/go/pdihelpdesk

HTH

java

if this helps, please rate

www.cisco.com/go/pdi
Silver

Re: Sending ANI to ATT

First I would try unknown/unknown.

After that I would call the carrier and ask to speak with a CO tech so they can work with you to correct.

The fact that they are not rejecting the call nor are they sending cause codes will make it difficult to reverse engineer from your end....

Re: Sending ANI to ATT

I would start with setting the hardcoded caller ID on the gateway, instead of using XXXXXXXXXX set it to a number that is part of your DID block. If that does not work then ATT could have an issue. If that does work, then change the caller ID on your gateway back to the X's, then set the 10 X's on your Route Pattern and make sure you are setting the mask on the individuals extension to 505865XXXX or whatever your NPA-NXX is of your DID block.

912
Views
0
Helpful
7
Replies
CreatePlease login to create content