CenturyLink PRI Configuration.

[RedTech443]

Looking for some answers or a "second" pair of eyes on something.

I am migrating a PRI trunk group from an old Nortel system to an Avaya g450 with 3 mm710/PRI cards in it on CM 6.3

The trunk group is this.

Primary DS1 (which has a D channel)
Secondary DS1 (Also D Channel)
and a DS1 with no D channel

Thse are all one trunk group, I have tried adding them to the PBX in the following format.

Created a DS1 with b8zs esf
Protocol C (verified by vendor)
Everything else is mostly default here as not much is needed to change usually.

The signaling group is setup with Associated Signaling "N"and the primary DS1 as the Primary and the secondary as the secondary, I also add the 3rd No D channel PRI to the list and give them the ID of 0, 1, 2
2.
Sorry no screenshots, So basically...

Priamry D-Channel = 001v224
Secondary D-Channel = 001v324

Trunk board 1 = 001v224 - ID 0
Trunk board 2 = 001v324 - ID 1
Trunk board 3 = 001v424 - ID 2


The Signaling groups come up in service as well as the trunk members. I have checked that the ports are all open for testing 1000 - 65535 in the network region, and checked codecs as well as network mapping, all good so far.

Problem is I have no Audio Path being created, I can call and receive calls but not audio either direction.,
I am trying to figure out what could be the cause but still stumped. If these are indeed 3 ds1's all in one trunk group this setup should be correct I believe, can someone possibly enlighten me on any suggestions or any questions I can answer to help get better answers Thank you in advance for your help.

 

[avayaguy23]

did you create your route pattern to go out that new trunk you created? Also, this is how I learned my first time doing this:

http://rogerthephoneguy.com/?m=201412

 

[RedTech443]

Thanks for the response Avayaguy23, Magically when I went in on monday it was all working. My configuration was all correct as I had knew it was.

The issue was on the Carrier side, they had to change the setting NTNAPRI (SL1PROFL) to be Null is what I was told, that setting has something to do with Nortel only equipment and since we were no longer on Nortel removing that fixed the problems, they also mentioned something about fixing some transport issues that were also fixed, I am not s sure what it was but it is all working now.