AT&T Business Voice over Internet Protocol (BVoIP) IP Flexible Reach Service PRI connection

[busster]

Customer had a cutover last night, converting from one carrier to another.

The existing carrier and the new carrier, AT&T, using the exact same protocols, NI2/ESF/B8zs.

Incoming calls came in and processed without a problem. All outgoing calls failed. Using status and monitor, the outgoing calls were attempted on 23rd channel, but AT&T never saw the call attempts.

Each user is currently set to send their DID as outgoing callerid. This could be seen in the call trace. Per AT&T, they were setup to accept all of these callerid's, the entire 100 block.

Has anyone else had difficulty with an AT&T IP Flex pri?

Thanks.

 

[Telecomboy]

For testing purposes you could send out the main number to see if that is why they are blocking the call. I know they are saying they are not, but I've had that happen before.

 

[Telecomboy]

I would also run monitor as it should tell you why the call is being denied.

 

[busster]

Did both.

Changed computer room phone to send out main number, same result.

Also used monitor, kept getting a reject message from AT&T, "cause = 100". Per AT&T, not a valid message.

 

[joe2938]

trust me this is a provider issue no matter what they say

 

[teletechman]

are you sure that they are giving you all 23 channels? Try to limit the channels in the IPO to say 10 and see if it works. Also post the monitr trace that you are getting. The clue is that they are not seeing it try to hit their PRI.
Mike

 

[busster]

Had the same thought. Busied out all but the first channel, which we saw the incoming calls hit. Made test calls out, same result. AT&T rejected the call.

 

[TouchToneTommy]

You can change your Channel Allocation to 1 -> 23 so your outbound starts with 1, then you can leave all the channels in service

Avaya's explanation of cause codes is here:

https://downloads.avaya.com/elmodoc...mergedProjects/monitor/cause_codes_(isdn).htm

They seem to have made up some of their own, Avaya says cause code 100 is
100 - Invalid information element contents.

It's easier to see the cause codes in SSA, but Monitor will give you ALL the info you need.

Be that as it may, it's AT&T

 

[joe2938]

I agree again, It's an AT&T issue for sure

 

[amriddle01]

Until you ask them to explain why they reject it you will be nowhere, you have evidence they are. Why don't they just deliver VoIP direct? Seems silly to convert

 

[sizbut]

The Avaya DevConnect team regularly produce application notes for AT&T services with IP Office. So look at the app notes on their site:

https://www.devconnectprogram.com/s...gsp?item=da4e975a-6ca2-40c3-9e6b-9e62a8ef3c3b

Stuck in a never ending cycle of file copying.

 

[IPGuru]

kept getting a reject message from AT&T, "cause = 100". Per AT&T, not a valid message

AT&T had just admitted they are the cause of the problem !

Ask WHY are they sending an invalid message?


Do things on the cheap & it will cost you dear