sundance-communications.com/forum Forums TDM Business Telephone Systems NEC Telephones & Systems XO dropping calls on my 2000IPS

I have A 2000IPS with 2 PRIs with XO as the carrier. The problem is some outbound calls are droped. XO did a call trace and here is what they found we are not providing e164 formating. Can anyone tell me how I implement this in the switch?

HERE IS CALL TRACE:

INCOMING 13:37:54.761 NODE TYPE= LTC_NODE SCP_X_ORIGINATE_MSG

NN= 00AB TN= 0218 MSGTAG= 00 ROUTE= 4000 ERROR= 00 LENGTH= 1F

AGENT= CKT CREDIT_PRI2 23

6C 02 01 00 10 00 02 01 01 08 FF FF 0B 00 80 23 31 31 35 18 2A AA 00

Message Type : SCP_X Originate MSG

Progress Indicator: NOT_END_TO_END_ISDN

Prog_Ind Location : PVT_NETWORK_SERV_LOCAL

BC_NAME : SPEECH

CDN_Digits : 13135381020

CDN_TON : UNKNOWN CDN_NPI : UNKNOWN------------------------------> This needs to be e164
CGN_TON : NETWORK CGN_NPI : Undefined-------------------------> This needs to be e164

CGN_SI : NETWORK_PROVIDED CGN_PI : NOT_SUPPLIED

NI-PRI CGN_SI_PI : SI_PI_COMBINATION_SPARE_2

Did you follow the NEC cheat sheet to setup this PRI? Very quick & easy, not to many settings. Are only some calls failing? What do the have in common? I think the PRI provider is blowing a little smoke up your arse.

I second Dr. PBX. Very likely you're getting "smoke signals" from the provider. Is it a small "Mom & Pop?"

If it's not the provider, the most likely cause of unreliability in a PRI is that the it's set to the wrong ISDN protocol in CM AA06. This should be set to 20 for AT&T, 21 for Northern/DMS, and 28 for NI2.

Northern is sometimes called DMS, and ST&T is sometimes called National, but some providers will argue with you on it. Let them win, it's not important, just find out what they're set to, and match it.

If it's set incorrectly -- i.e. you've got AA06>xxxx>28 and they need AA06>xxxx>20, it may "sort of" work, because, as a certain mildly-famous NTAC tech is rumored to have once said, "The switch is just a bit slutty. Sometimes it'll go with whatever's there."

But as Dr. PBX so wisely points out, if you follow the cheat sheet, you'll almost always nail down the issue.

Thanks for the feed back let me add to what my problem is and I don’t think it’s a miss-match of switch type. The carrier XO, which I have to say, is not a Mom & Pop operation is the carrier.
XO is saying all calls gets setup at their end but when they have to hand it off to another carrier the call gets drop because we are not sending our telephone number xxx.xxx.xxx
What they are telling me is this is required in the e164 formatting. So the bottom lime is i have to get this 2000 to send office information (xxx.xxx.xxxx) with each call.

'Office Information' is known as Calling Party Number. This is programmed as:

Assume outbound number is 202-555-1212 and extension number is 1000.

5005>00>202555 (first 6 digits of phone number)
1212>1000>1212 (Last 4 digits of phone number)
1213>1000>00 (Associate this ext. w\ 5005 table 00)

stephensnet,

If you don't provide outgoing ANI on the PBX, the carrier sends the BILLING number out, that means YOU have no control over that part. Basically you do not have to provide outgoing caller ID if you didn't want to. Sounds like a case of not wanting to take responsibility for a problem by carrier.


Scott

Yep, but don't forget that the BTN is often a fictitious number that can't be dialed. If that is what is being sent, it may get rejected during the hand-off. Most carriers will allow you to have them change this to something that is valid if you don't want to have your switch send this information.

Been running into the small mom and pop dialtone provider FORCING the pbx to sen ANI or the call outbound is rejected. Oh and You must be sending one of the numbers that actually arrives on your circuit.... oy!

D