So odd. You'd think that changing the tag, on the way out, would give them what they are looking for. Did you confirm through debug that the calls are being tagged that way? May 12 15:57:59.460: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8 callref = 0x6E1F 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 = 0x8183 - Origination address is non-ISDN Calling Party Number i = 0x2183, '813XXXXXXX' Plan:ISDN, Type:National Called Party Number i = 0x80, '1855XXXXXXX' Plan:Unknown, Type:Unknown May 12 15:57:59.928: ISDN Se0/0/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0xEE1F Channel ID i = 0xA98381 They "say" that's what they want, but when you give it to them, no go. Service providers, UGH!
... View more
Rob~ We found a way to put a global command in the gateway to send the calls out as 0x2183, which is (Screening indicator - Network provided). We are testing to see if this workaround helps. The bad news is that it affects some land lines too, so you get reports of intermittent Caller ID showing "UNKNOWN" which, we ALL know, is impossible to troubleshoot with providers. This is only a workaround, but you might want to give it a shot: voice service voip clid network-provided To back out, just do "config t > voice service voip > No CLID network-provided" AT&T said it has something to do with the new 5ESS switches not liking the "not screened" or "verified and failed" tags, so depending on what path the calls end up going, you could see this with landlines too.
... View more