Caller ID Number to AT&T Wireless 2

[telecomtekperson]

I have a 406 at 4.0.8
2 PRI's (NI2) from ATT

doing some outgoing CID manipulation for the users.

If you call out, number shows fine. If you call Sprint wireless, Verizon or any land line, all is well.

If you call AT&T Wireless, the number comes up as "Unknown".

Customer opened a ticket with AT&T wireless, and they called me. They pulled a trace and said the following:

MT: IAM
Called Party Number Length: 7 octets
Nature of Address Indicator: National (significant) number
Address Signal: ***5340001
Calling Party Number Id
Nature of Address Indicator: Undefined (Undefined needs to be changed to National)
Address Signal: ***3732330
Charge Number Id
Nature of Address Indicator: ANI of the Calling party; national number
Address Signal: ***7540460
Generic Address Parameter Id
Type of Address: Ported dialed number
Nature of Address Indicator: National (significant number)
Address Signal: ***42347527

I did some searching and saw tech tip 212, but I think that is the opposite of what I need.

Has anyone experienced this?

In regards to tech tip 212, could I change:
NI2_CALLED_PARTY_TYPE=UNKNOWN
to use "National" instead of "unknown"????

http://www.telemanuals.com

http://www.telemanuals.com/forum

 

[mattKnight]

Set your outbound Cli using Si instead of S

i - National
Both the S and SS characters can be followed by an i, that is Si and SSi. Doing this sets the calling party number plan to ISDN and number type to National. This may be required for some network providers.

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[telecomtekperson]

Some users are showing their DID (DDI) as the outgoing caller ID. SO I am not inserting the "s" anywhere.

I will try that "i" for the users that are going through ARS and sending a custom number.

http://www.telemanuals.com

http://www.telemanuals.com/forum

 

[telecomtekperson]

OK. THat did work, thank you Matt. But not for the users sending their DDI as CID.

Those users are going to their own ARS table, with just generic short codes (1N;, 1N, Dial 3K1, 0). Am I out of luck with those users?

http://www.telemanuals.com

http://www.telemanuals.com/forum

 

[pepsisparky]

Can you put it in the incoming route(ddi) table? I dont think ipo will use it to match incoming with, but will for out going. I may be wrong though. Never did this.

 

[mattKnight]

as pepsisparky points out...

Incoming Number: Default = Blank (Match any unspecified)
Matches to the digits presented by the line provider. A blank entry matches all calls that do not match other entries. By default this is a right-to-left matching.

• – = Left-to-Right Exact Length Matching
Using a - in front of the number causes a left-to-right match. When left-to-right matching is used, the number match must be the same length. For example -96XXX will match a DID of 96000 but not 9600 or 960000.

• X = Single Digit Wildcard
Use X's to enter a single digit wild card character. For example 91XXXXXXXX will only match DID numbers of at least 10 digits and starting with 91, -91XXXXXXXX would only match numbers of exactly 10 digits starting with 91. Other wildcard such as N, n, * and ? cannot be used.

• Where the incoming number potentially matches two incoming call routes with X wildcards and the number of incoming number digits is shorter than the number of wildcards, the one with the shorter overall Incoming Number specified for matching is used.

• i = ISDN Calling Party Number 'National'
The i character does not affect the incoming number matching. It is used for Outgoing Caller ID Matching, see notes below.

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[telecomtekperson]

Yes, that worked.

As a side not. The customers system is on 4.0.14. I had to put the "i" before the number on the ICR. On my system (5.0.8) I had to put it at the end of the number.

Does that sound normal?

http://www.telemanuals.com

http://www.telemanuals.com/forum

 

[spe1996]

I had the exact same issue while moving from old Definity to IPO. I had AT&T trap the calls and got the same reply from AT&T. I asked AT&T to rebuild the PRI circuits from custom to NI2 and the problem was fixed, traps afterwords showed no issues with CLID.