TIM Plus/SMDR locking up 2

[daveinwearside]

Has anyone had any issues with the SMDR stop outputting on IP500 V1 8.0(42).

I've had Tri-line check the TIM, that seems ok.

The issue sorts itself after a re-boot but I've lost 2 days of calls from the buffer



ACSS SME
APSS SME
A word to the wise ain't necessary - it's the stupid ones that need the advice.

 

[hairlessupportmonkey]

Have you tried reversing who receives and who sends? (sounds grubby I know )

So, if the IPO is sending to Tims, then change the IPO to 0.0.0.0 and make is a listening server or vies-versa and in turn change Tims to either be a host or client.



ACSS - SME
General Geek

 

[AJFrancis]

Hi Dave,

Give what hairlessupportmonkey a go. It won't be too bad to change in TIM Plus either. To change from listening to active within TIM Plus change the following bits:

1. Change "Listen for connections from PBX" to "Actively connect to PBX".
2. Put the IP address of your IP Office.
3. Select "IP Office" from the connection script drop-down ("Simple" if you don't see the IP Office script).
4. Save changes.
5. Change IP Office IP to 0.0.0.0.

If you are having network problems you can also enable the Inactivity timer/reset on the connection so it doesn't leave the IP Office buffer filling for too long, forcing TIM Plus to reconnect if it lingers too long.

If you have any questions or need a hand with the config of TIM Plus call our Tech Support again.

Best regards,
Andy
Tri-Line

 

[daveinwearside]

cheers guys, just made the changes.

i'll see how it goes and let you know

ACSS SME
APSS SME
A word to the wise ain't necessary - it's the stupid ones that need the advice.

 

[hairlessupportmonkey]

Dave,

I take it the customer doesnt have support with Tri-Line? If not, Advise taking it out, they arent too bad down there for support

ACSS - SME
General Geek

 

[IPOfficeIreland]

we have seen this before - if IPO looses connection to the logger, event briefly, it starts to buffer the call logs (you can set it to 3000 last time I checked). IPO strangely stops even trying to connect to the logger after the connection is restored which is where the problem is. a reboot is the only fix. You can set an alarm in Tim that if no data is received after X seconds on Y days to send you an email. We thought originally it might have been a Tim problem so we set an alarm to restart the Tim service if no data received but the problem is avaya side. Nothing you can do but make sure the connection between the 2 is 100%.

 

[daveinwearside]

that seem to have sorted it chaps, thanks for your help!

ACSS SME
APSS SME
A word to the wise ain't necessary - it's the stupid ones that need the advice.