IP Office Analog 4 Trunk incoming call detection

[catalinbalan]

Hi,

i have a problem with an IP Office 500, Analog 4 trunk: when receiving calls, in the System Status they appear as Prealerting and tehy are not changing to Incoming Alert. So the IP Office doesn't recognize as an incoming call.

I've tried changing the parameters for analog lines, changig locale settings, system frequency, but i can't get a solved problem.

Can anybody help me, please?

 

[aarenot]

Are the analog trunks off of a channel bank? Possibly an Adit600?

 

[aarenot]

try sending me the config at same user name as on here AT My Special Network DO Try to COMe
I will take a look and see if I can find anything.

 

[AZJeepGirl]

I had the same issue on 4.0 (5). Upgraded to 4.0.(7) all was well. Lines were coming off a channel bank.

____________________________________
I'd rather be jeepin'! 0|||||||0

 

[catalinbalan]

I have already upgraded to 4.0(7). I didn't test this issue on 4.0(5). The problem i see is only with 2 providers of 3. One trunk is connected with an Ericcson FCT251m - GSM, 2 trunks with an voip provider (i have an equipment - Tainet which converts ip telephony into analog trunks) and one connected to our legacy provider - analog trunk.

On trunk connected to our legacy provider everything works fine.

 

[PlatinumGuy]

Try setting them (i dont know the US market) to none CLI trunks.

It sounds like the IPO is waiting for a CLI to decide if it can route based upon that, but not seeing one and getting stuck somehow?

ACA - IP Office Implement
ACS - IP Office Implement
ACE - IP Office Implement
ACI - IP Office Implement

 

[catalinbalan]

That's my first tought and i've tested with LoopStart without CLI and with GroudStart Lines. It remains the same problem.

I think there is a problem with frequency, Tx/Rx gains and ring duration min and max in miliseconds.

 

[aarenot]

I am not familiar with the specific units you are using to convert VOIP etc. to analog trunks. I would suggest you get the manuals out on these devices, and learn how to configure, and adjust them.
I have a few times been called in to help when channel banks like the Adit 600 have caused issues which caused the line ringing not to be recognized by the IPO. I have done a lot of testing with the Adit 600, and adjustiments to it, and had success with making the IPO recognize the Adit 600 ringing. This was done by adjusting the settings on the Adit 600 which reportedly is slightly out of standard in the ringing(so I have been told). I have been able to find settings which create a ring which the IPO can pick up on. I would hope these units have some ability to adjust the outputs to do the same. I would try looking there if all else fails. Expect to take some time to read up on the equip., then with field testing, and do not expect the manuals to spell out how to fix it, you will have to play with it until you win. If you have tech support for the units, you might want to give them a call, and ask how to adjust the ringing outputs.
I hope this helps if only to let you know that it may be something that you can research a bit, and fix. This ringing recognition issue has been a re-occuring subject across multiple releases with patches for multiple software levels in the past. Rather than having to deal with the uncertainty of the next upgrade being able to handle the ring recognition I just learned to change the ring from the Adit 600, so i don't have to deal with it. I have seen the ring recognition issue raised with multiple releases of software over the past few years, so don't count on it being a past tense issue.