In a Jam - Upgrade to 5.0.18 and PRI T1 Incoming Channels

[vtphilk]

I just upgraded to 5.0.18 from 4.2.x. We have a frac PRI from a carrier and we have 10 channels from them. So in IPO we have 10 licenses for channels. So I have channels 1 -> 10 in service and the rest out of service.

Problem is, the carrier randomly round robins the incoming calls to the next available channels. So while outgoing calls ALWAYS will be on a channel 1->10 incoming calls will come in on channel 23, 22, -> 1 etc...

In 4.2 I did not have a problem with this, IPO worked fine for around 52,000 incoming calls in a year according to the system stats. However, now in 5.0.18, it's dropping the incoming call when it is not on a in service channel.

Monitor shows:

624740mS PRN: Chan 13 not in service
624741mS ISDNL3Tx: v=5 peb=5
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=000B(Local)
Message Type = ReleaseComplete
InformationElement = CAUSE


HELP! I don't want to fall back to 4.2 but looks like I am gonna have to. Carrier cannot change the incoming (I think cuz the night tech is too dumb) and I gotta get them up by morning.

I have tried re-flashing the 5.0.18, reboot, power cycle, etc... nothing Also searched high-and low for hours.

Thanks!

 

[vtphilk]

PS: PRI 24 Settings:

NI2
23->1 (I have tried 1->23)
Prefix = <blank>
Never
Test Number = <blank>
Clock: Network
CRC Checking Checked
CSU Operation Unchecked
haul 0-115


Line SubType = PRI
Provider = Local Telco
Framing = ESF
Zero = B8ZS
Line Signaling = CPE
Incoming Routing Digits = 10

 

[tlpeter]

Setup 10 channels with line id 0 and the rest with line id 1 (if possible!0
Then make incoming call routes with 0 and 1

ACSS IP Office
APSS IP Office
APSS UC
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management


______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[amriddle01]

This sounds like something the carrier needs to resolve, so they only use the first 10 channels... man I'm glad we have ETSI/E1 here

ACSS Small and Medium Enterprise (SME) Communications

"What the Crocodile Hat....was that?

 

[mforrence]

I agree that you need to clarify with the carrier exactly which ten channels will be active.
Mike

 

[Textron68]

Definitely a Carrier provisioning issue. For fractional circuits the provider needs to be provisioned to First Available starting at Channel 1. Than you can set your outbound 23-1. Glare is typically not an issue with PRI, but it’s good practice to have your in/out in opposite direction.
You could take it back to 4.2 until you get the circuit sorted with the carrier than go back to 5.x

 

[vtphilk]

Ok..so after about 2 hours of paging out the carriers techs finally got a voice guy that had a clue at provisioning the adtran CSU. He was able to config the channels 1-10 and busy out the rest of the b-channels. After that, the incoming calls only came on 1-10 and avaya IPO was happy.

SOOOO weird that this has worked fine for over a year in IPO 4.2 but in 5.x broke. I know it ain't right way but it was working. Oh well, now it's right.

Thanks!

 

[amriddle01]

It is odd, I don't recall any major changes to ISDN between 4.2 and 5, but at least it's working

ACSS Small and Medium Enterprise (SME) Communications

"What the Crocodile Hat....was that?