Analog dedicated line problems

[jabial]

We have an analog dedicated line for transferring calls from one building to the other. We had Telic 1600 systems that we are replacing with OXOs. Our installer is having lots of trouble making it work like it did.

The dedicated line is seen as an analog line on one end, and as an analog extension at the other end, which allows to call arbitrary extensions from the "line" end without using the public network.

However, at that "line" end, we have plenty of problems, from a one-way buzzing that was never seen before to that extent, to seemingly random hangups we can't determine which OXO hang up to the other. Without changing any settings, it suddenly works then doesn't then works again.

The installer temporarily connected the line to an old analog extensions directly, which totally deletes the buzzing but it is obviously not what we want. Anybody has any experience with this kind of setup?

[tuxalize]

I need more details about this line to connect both sites.
At Line end, where it is going to ? (PSTN, MUX, Router.....)
At Extension end, where it is coming from.

I want to understand it better, if everything is connected correct (FXO and FXS) the buzzing is due to different ground potencial.
How old is this OXO ?

I have experienced diferent buzzing issues.

Let me know,
Regards,
Tux

[jabial]

At the "line" end it is plugged into a line port (mixed card) and declared as an analog line.
At the "extension" end it is plugged into an extension port and declared as an analog extension.

The OXOs are new, R7, yadda yadda. Hey, at the "line" end we even had license problems ("you have 30 days, blah blah") because the guys installed it in R61 when the license was for R7. I updated it late in the evening, the installer (which has had woes trying the same using LOLA the day before) was quite happy when he came back next day.

It is a dedicated line, it doesn't ever go into the PSTN. It's exactly as if you put two OXOs in a room, and then use a pair of wires to link the first analog line port of OXO1 to an analog extension port of OXO2 - except the cable is a hundred meters long, not just a meter or five.

I have to say that now the buzzing has been solved. However, we have magnificient new woes : now, at the "line" end, if we pick up the line using a line resource key and then type an extension number, it will :
- wait something like 5 seconds before ringing it, whatever the extension we are calling
- and then hang up saying extension 11 has hanged up, if and only if we are calling extension 11

However, if we pick up the line using a trunk group resource key (the trunk group ONLY CONTAINS the SAME line as the line resource key, we checked something like 10 times), not only we don't have to wait for the extension to start to ring, but also extension 11 is ringed and answers perfectly. And no, the discrimination is set exactly the same in the line as in the trunk group. And we forbid nothing in the discrimination rules. And anyway if it was :
- a discrimination problem at the "line" end it would just reject the number outright
- a discrimination problem at the "extension" end it would not work perfectly when we pick up the dedicated line using a trunk group at the "line" end

I'm just going to go crazy with this stupid setup.

[jabial]

By the way, CLI doesn't seem to survive passing through the analog line. The extension end is configured as a class extension with CLI and name display on, the line end is connected to an AMIX card and is configured with CLIP on, but no number appears. I wonder if I need a CLIDSP, but normally it shouldn't be necessary. Maybe the dedicated line is just too bad for frequency shift signaling to work.

[tuxalize]

- Well, without CLIDSP you will never have Number / Name detected on OXO. You are using.

- The other problem you are facing is related to end of dialing table and timers at Analog Protocols.
if you are dialing 11, you must set the End of Dialing Table to prefix 11 closed to 2 digits.
and at Analog Protocols, on protocol you are using, reduce the timers for :
minimum before send first digit (to 200ms)
Off Hook simulation MF Closed (to 200ms)
It will reduce the timer for OXO before send digits.

Regards,
Tux

[jabial]

Outside the USA, the CPU card can detect CLI. It's described in the expert manual. Anyway, I was wrong : the installer had declared the extension end as a normal extension. I changed it to a class extension, and yadda! CLI works.

I'll try your solution for numbering, but it doesn't tell me why it does work when I use the 1-member trunk group resource key instead of the line resource key.