We know that as soon as you plug a analog trunk into an IPO PORT the trunk port tries determine the line characteristics by sending out all kinds of tones etc on the line before it actually goes idle.
Here's my problem.
I'm migrating a Viking C2000 Advanced Door Entry Controller from a Partner.
When connected to IPO,this is what happens:
o Press button on door phone
o The Viking rings in on IPO trunk and alerts a Hunt Group
o User answers call and hits ### to unlock door at which time the Viking disconnects.
O All good
Now the problem:
o If you press the door phone button again within up to about 20 seconds of first call....you hear (atthe door phone) the IPO doing testing on the trunk.
o The call doesn't ring thru to the IPO and everything's in a state of confusion.
o If you do NOT push the door phone button to soon, everything normals up and the next call works fine...because the IPO has had time to reset its Trunk Port
So.....can this situation be avoided in any way?
Here's my problem.
I'm migrating a Viking C2000 Advanced Door Entry Controller from a Partner.
When connected to IPO,this is what happens:
o Press button on door phone
o The Viking rings in on IPO trunk and alerts a Hunt Group
o User answers call and hits ### to unlock door at which time the Viking disconnects.
O All good
Now the problem:
o If you press the door phone button again within up to about 20 seconds of first call....you hear (atthe door phone) the IPO doing testing on the trunk.
o The call doesn't ring thru to the IPO and everything's in a state of confusion.
o If you do NOT push the door phone button to soon, everything normals up and the next call works fine...because the IPO has had time to reset its Trunk Port
So.....can this situation be avoided in any way?