Anyone run into an issue with an AVAYA IP Office 406 (ver 3.2) and analog lines not working with it? The analog lines are coming from an ADIT 600 (CAC). We've checked the voltage on the lines coming out of the ADIT and we're getting a steady 48 volts. Tech can place his test set on the 66 block coming off of the ADIT 600 and receive/make calls no problem. The issue is getting the calls to complete to the AVAYA IP Office 406. We've even messed with the jumpers in the ADIT 600 to try to play with the acutal signal/wavelength with no luck. Any ideas?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
AVAYA IP Office 406 ver 3.2 analog lines not working with an ADIT 600 1
- Thread starter JimGJr
- Start date
- Thread starter
- #3
JimGR,
any good news on your IPO on the Adit 600? I have one with the same problem. Catalyst post sales support, no help. I have e-mailed Avaya to no avail. Hate to call TSO, they'll bill me. We had to put a Partner ACS in for Temp service.
I get 72 VAC on the ring pulse (analog meter), the carrier gets 80 VAC with digital Fluke. Connect ext. 201 to a trunk port, works like a champ. I put 1000 ft. cross connect in between demarc and IPO, worked once. How do we escalete from here to Tier 3?
If ANYBODY has an idea, I'll try anything once
any good news on your IPO on the Adit 600? I have one with the same problem. Catalyst post sales support, no help. I have e-mailed Avaya to no avail. Hate to call TSO, they'll bill me. We had to put a Partner ACS in for Temp service.
I get 72 VAC on the ring pulse (analog meter), the carrier gets 80 VAC with digital Fluke. Connect ext. 201 to a trunk port, works like a champ. I put 1000 ft. cross connect in between demarc and IPO, worked once. How do we escalete from here to Tier 3?
If ANYBODY has an idea, I'll try anything once
- Thread starter
- #5
Hey Wannabe1,
No luck yet...I had the actual customer call his AVAYA guys and they said he's all up to date, as far as his patchs/firmware went. They said that 3.2 was the most current version, so he should be good. We are actually going to try to swap the ADIT 600 with a CAC to see that helps resolve the problem(s). Could be a compadiablity issue with the ADIT 600 and the AVAYA IP Office 406, as far as analog lines go? Digital service (i.e. PRI, Digital Trunks) work just fine (just had one of those turn-up today), but the one that is needing analog lines passed to it from the ADIT 600 is still not happy? Still looking for a solution. Keep me posted if you hear of a fix and I'll do the same.
Thanks,
~Jim~
No luck yet...I had the actual customer call his AVAYA guys and they said he's all up to date, as far as his patchs/firmware went. They said that 3.2 was the most current version, so he should be good. We are actually going to try to swap the ADIT 600 with a CAC to see that helps resolve the problem(s). Could be a compadiablity issue with the ADIT 600 and the AVAYA IP Office 406, as far as analog lines go? Digital service (i.e. PRI, Digital Trunks) work just fine (just had one of those turn-up today), but the one that is needing analog lines passed to it from the ADIT 600 is still not happy? Still looking for a solution. Keep me posted if you hear of a fix and I'll do the same.
Thanks,
~Jim~
kristiandg
Programmer
Yeah, that was bad info. There won't be a 3.3. I saw that post too.
However, check this out and see if it helps:
Kris G.
However, check this out and see if it helps:
Kris G.
- Thread starter
- #8
-
1
- #9
We have the same setup here.
Our system has one of each (was a demo unit until we sold off our magix) The newer "universal" card will not work on the Adit 600 but the older version does.
I seem to recall seeing a post here a few months ago about the same exact problem. I never saw a solution then either. The best answers I saw were, 1) Have provider check specs on the lines and 2) Make sure the IP Office is properly grounded.
I haven't gotten around to checking with our provider since we only need 4 lines at the moment and so far all of our analog line customers have service providers that do not use Adit 600's
Would be nice to see a solution one of these days though.
Our system has one of each (was a demo unit until we sold off our magix) The newer "universal" card will not work on the Adit 600 but the older version does.
I seem to recall seeing a post here a few months ago about the same exact problem. I never saw a solution then either. The best answers I saw were, 1) Have provider check specs on the lines and 2) Make sure the IP Office is properly grounded.
I haven't gotten around to checking with our provider since we only need 4 lines at the moment and so far all of our analog line customers have service providers that do not use Adit 600's
Would be nice to see a solution one of these days though.
- Thread starter
- #10
Both the newer and older versions work in the IP Office (406V2 in my case)
The new universal ones have not worked with the Adit 600 for me and others. YMMV
The part number for the old card is SAP# 700185192 and has been discontinued. If you see one, the plate will say "Analog Trunk" Model name was "IP400 Analog 4 (LS) Expansion Kit".
The newer 700359938 "IPO MC ANLG 4 UNI (LS) Expansion Kit" is what is sold now and is the version this topic is about and seems to have trouble with Adit 600's
The new universal ones have not worked with the Adit 600 for me and others. YMMV
The part number for the old card is SAP# 700185192 and has been discontinued. If you see one, the plate will say "Analog Trunk" Model name was "IP400 Analog 4 (LS) Expansion Kit".
The newer 700359938 "IPO MC ANLG 4 UNI (LS) Expansion Kit" is what is sold now and is the version this topic is about and seems to have trouble with Adit 600's
- Thread starter
- #13
Thanks for the info, kmefford...We'll see if we can locate an "older" version of the analog trunk card for the AVAYA IPO 406 to see if that makes a difference with getting the analog lines coming from the ADIT 600/66 block to work with the AVAYA IPO 406. We're also going to try to swap out the FXS card in the ADIT 600 with an "older" version of the FXS card to see if that makes any difference (might as well try it on both pieces of equipment). I'll post an update if that works...
Thanks,
~Jim~
Thanks,
~Jim~
IP Office Technical Tip 59
"The objective for all trunks should be an NMSa Reading (dBrnc) of less than 20 dBrnc, with a gain of -3.5 db within +/- 1dB. Loop, or trunk noise of 21-30 dBrnc is marginal as 30 dBrnc is approached and requires investigation and possible intervention by the service provider. Noise above 30 dBrnc is unacceptable, and will almost certainly lead to issues like those mentioned above – the service provider will need to investigate these trunks, and provide a remedy."
There are also requirements loop current, loss, etc.
This is really an issue with the ADIT. A POTS line is an electrical circuit that must meet certain specifications. The ADIT isn't producing a circuit that falls within the standard specs of a POTS line.
"The objective for all trunks should be an NMSa Reading (dBrnc) of less than 20 dBrnc, with a gain of -3.5 db within +/- 1dB. Loop, or trunk noise of 21-30 dBrnc is marginal as 30 dBrnc is approached and requires investigation and possible intervention by the service provider. Noise above 30 dBrnc is unacceptable, and will almost certainly lead to issues like those mentioned above – the service provider will need to investigate these trunks, and provide a remedy."
There are also requirements loop current, loss, etc.
This is really an issue with the ADIT. A POTS line is an electrical circuit that must meet certain specifications. The ADIT isn't producing a circuit that falls within the standard specs of a POTS line.
Thanx to kmefford for the part number.
I went out to the site today with a Oscope. The ring pulse is not a sign wave, looks like it has gone thru some sort of a rc time constant and chopped of the bottom half on the negative side of the wave/pulse. I get to meet with an engineer tomorrow and I'm taking my scope. I'm sure I won't get anywhere as one as mentioned, but maybe some satisfaction.
From what I got from a Tier 3guy today is that the signal-noise issue in Tip 59 will cause the trunks not to work in and outbound. Who knows, just make it work!
Thanx for help
I went out to the site today with a Oscope. The ring pulse is not a sign wave, looks like it has gone thru some sort of a rc time constant and chopped of the bottom half on the negative side of the wave/pulse. I get to meet with an engineer tomorrow and I'm taking my scope. I'm sure I won't get anywhere as one as mentioned, but maybe some satisfaction.
From what I got from a Tier 3guy today is that the signal-noise issue in Tip 59 will cause the trunks not to work in and outbound. Who knows, just make it work!
Thanx for help
- Thread starter
- #16
Found a solution on this...Turns out that the power supply on the ADIT 600 must be jumpered to pins J5 & J6, this will increase the signal strength (known as a Long Rise) on the analog lines going to the AVAYA IPO 406. We tried this before, but that was before the AVAYA IP Office 406 was completly upgraded to ver 3.2 (with all the latest patches installed/downloaded). Once the AVAYA IPO 406 was upgraded all the way to 3.2 and all patches had been installed/downloaded in the AVAYA IPO 406, the change on the ADIT's jumpers in the power supply did the trick. We are now able to have inbound and outbound calls complete successfully. Hope this helps everyone in the future, should you run across this issue.
Thanks,
~Jim~
Thanks,
~Jim~
Avaya Tier 4 gave a private buidl to me for a customer with this issue Adit 600. It was 3.1.56, and Avaya said it was the Adit 600 but they rewrote the code to accept the Adit 600 out of national standard output. Call for support, get it escalated, but if they can not recieve calls, Avaya will respond more quickly. They said 3.2.17 has this fix built in.
No I do not have the bin file.
You do not always get what you pay for, but you never get what you do not pay for.
No I do not have the bin file.
You do not always get what you pay for, but you never get what you do not pay for.
I work for a CLEC and heard about this problem today. The Adit presents the line with 26ma current, as does most muxes (note: This is within the spec of 23ma-120ma for a loop start line). The IP Office system requires at least 28ma current. Monday I will find the resolution to up the current on an Adit and post it here. I come from the PBX world and share your frustration...so beat on Avaya(Lucent) to resolve "their" issue. Until then I will help my local vendor and I hope your LEC or CLEC will be as accomodating.
krug, I did say that Avaya said this clearly, so i do not have my opinion stated, but Avayas, or as I was told by tier 4.
The specific i was told was something about the ring voltage wave, but I did not write it down. Although, i have only had troubles with the adit 600, out of the many, many units I have interfaced with.
You obviously care about your cutomers as I do, I spent many hours working on trying to get this issue fixed, and the CLEC would not even send a tech out for a week to check their equipment, so I just kept at Avaya until they gave me a solution. I personaly do not wish to or begin to say I could resolve the entire question of who has the responsibility for the issue. I do know I found a resolution for my customer, and that satisfied me.
be well
You do not always get what you pay for, but you never get what you do not pay for.
The specific i was told was something about the ring voltage wave, but I did not write it down. Although, i have only had troubles with the adit 600, out of the many, many units I have interfaced with.
You obviously care about your cutomers as I do, I spent many hours working on trying to get this issue fixed, and the CLEC would not even send a tech out for a week to check their equipment, so I just kept at Avaya until they gave me a solution. I personaly do not wish to or begin to say I could resolve the entire question of who has the responsibility for the issue. I do know I found a resolution for my customer, and that satisfied me.
be well
You do not always get what you pay for, but you never get what you do not pay for.
- Status