Hi All,
We had a working Meridian opt 61 running 25.40b, with a genesys dialler (7.2) connected by a single E1 lineside card.
Provider recently upgraded us to Meridian 5.5, and we have had a few 'stuck port' issues since.
When the dialler was running, occasionally the odd few 500 set configured on the e1 card would show as offhook in Genesys, but meridian show them as idle. The only way to combat this was to physically dial the 500 set to clear it down.
After some analysis, we found a few settings which we thought wrong:
Line tone disconnect was set to LDTD instead of LDTA, and 2 FTR were missing, these were OSP 1, and ISP 75.
Making these changes has made a VAST improvement, but we are still getting just the 1 stuck port ever few hours. Nothing drastic, but not working as it should be.
The odd thing is that after exactly 30 mins, the post will go back onhook of its own accord, and doesn’t have to be manually dialled.
Any ideas where to check next?
Thanks
We had a working Meridian opt 61 running 25.40b, with a genesys dialler (7.2) connected by a single E1 lineside card.
Provider recently upgraded us to Meridian 5.5, and we have had a few 'stuck port' issues since.
When the dialler was running, occasionally the odd few 500 set configured on the e1 card would show as offhook in Genesys, but meridian show them as idle. The only way to combat this was to physically dial the 500 set to clear it down.
After some analysis, we found a few settings which we thought wrong:
Line tone disconnect was set to LDTD instead of LDTA, and 2 FTR were missing, these were OSP 1, and ISP 75.
Making these changes has made a VAST improvement, but we are still getting just the 1 stuck port ever few hours. Nothing drastic, but not working as it should be.
The odd thing is that after exactly 30 mins, the post will go back onhook of its own accord, and doesn’t have to be manually dialled.
Any ideas where to check next?
Thanks
