Anyone have experience changing from AT&T PRI to AT&T IP Flex on a CS1000E?

[captnamo]

We cant seem to get calls to go. IFC (protocol) is D100. We have two sites with IFC ESS5 working on IP Flex. PBX seems to cancel outgoing calls before SIP can reply. Incoming calls get a busy SIP message. Outgoing calls go to fast busy.

AT&T is also our CPE support. So far, no answers from them.

What, oh what, might I want to check in this loop's programming?

Accountant turned telecom guy,

--Steve

 

[captnamo]

Loop 221
Route 4
Dialing ACOD 6720004 first to be on the PRI we're changing

DCH 221 OMSG SETUP REF 00000016 CH 221 22 TOD 19:52:55
CALLING #:6163926991 NUM PLAN: E164/NATIONAL / NPA
CALLED #:6164029341 NUM PLAN: E164/NATIONAL / NPA

PRI222 DCH: 221 DATA: 00000016

DCH 221 OMSG RELEASE REF 00000016 CH 0 TOD 19:52:55
CAUSE :INVALID IE CONTENTS

DCH 221 IMSG CALLPROC REF 00008016 TOD 19:52:55

DCH 221 IMSG REL COMP REF 00000016 CH 221 22 TOD 19:52:55

DCH 221 OMSG SETUP REF 00000015 CH 221 21 TOD 19:53:23
CALLING #:6163926991 NUM PLAN: E164/NATIONAL / NPA
CALLED #:15173677837 NUM PLAN: E164/NATIONAL / NPA

PRI222 DCH: 221 DATA: 00000015

DCH 221 OMSG RELEASE REF 00000015 CH 0 TOD 19:53:23
CAUSE :INVALID IE CONTENTS

DCH 221 IMSG CALLPROC REF 00008015 TOD 19:53:23

DCH 221 IMSG REL COMP REF 00000015 CH 221 21 TOD 19:53:23

DCH 221 OMSG SETUP REF 00000014 CH 221 20 TOD 19:53:33
CALLING #:6163926991 NUM PLAN: E164/NATIONAL / NPA
CALLED #:16164942200 NUM PLAN: E164/NATIONAL / NPA

PRI222 DCH: 221 DATA: 00000014

DCH 221 OMSG RELEASE REF 00000014 CH 0 TOD 19:53:33
CAUSE :INVALID IE CONTENTS

DCH 221 IMSG CALLPROC REF 00008014 TOD 19:53:33

DCH 221 IMSG REL COMP REF 00000014 CH 221 20 TOD 19:53:33

 

[phones1]

I had a similar issue between a M1 81c & cisco gateway

when you see CAUSE "INVALID IE CONTENTS" I think it was a call type mismatch, your identifying your call as "E164/NATIONAL / NPA" if that either doesn't match theirs or isn't mapped to ignore this (on their box) the call fails during the setup.

it's probably easier to get them top play around with their end for the call type mapping if your not familiar with the ESN blocks (ld 86,87,90) mind you I resolved it by setting both the outgoing call type from the 81c to "UNKNOWN" & got the cisco guy to ignore the call type on the router

Remember if it doesn't work hit it harder

Scott UK

 

[janaya]

ugh. So many things you can try here.

First, I would change the IFC. It's weird to see anything other than ESS4/ESS5 for ATT. I would try to change the IFC to either ESS4/ESS5 or even NI2. I just had this happen over New Years weekend. Carrier stated it was D100. "We have a D100 and that is what it should be on your side". Got the same errors and changed to NI2, and what do you know. It all came up and worked. Now that was a normal PRI.

In your environment, is ATT dropping off the IP Flex to equipment at your site and providing you with a T1 interface? I'm just curious here as we are about to go full SIP service with about 400 SIP trunks.

On the dial out, do you have a DMI built on the RLB data? If so you can try different options there. In the CTYP field start with NCHG, or UKWN to see if the call works. If that doesn't you may need to separate the NPA/NXX dialing and use NPA or NXX in the CTYP field to match their E.164 requirements for dialing. If IP Flex, I don't think they need to see the 1+ in the number, just 10 digits.

Hope this helps.

John Anaya
Amdocs Inc.
ACSS/ACIS - CS1000 Rls 7.5/Call Pilot 5
ACSS/ACIS - SME - IP Office 8.0
APSS/APDS - Avaya UC Services

Public Profile

http://www.linkedin.com/pub/john-anaya/25/1b9/a9b/

 

[KCFLHRC]

Try turning off TRMB in the route. I'm also making a guess the IFC should be NI2 instead of D100